SAP VALIDATE_YEAR Function Module for Joint Venture Validate Year
VALIDATE_YEAR is a standard validate year SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Joint Venture Validate Year processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for validate year FM, simply by entering the name VALIDATE_YEAR into the relevant SAP transaction such as SE37 or SE38.
Function Group: GJVV
Program Name: SAPLGJVV
Main Program: SAPLGJVV
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function VALIDATE_YEAR pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'VALIDATE_YEAR'"Joint Venture Validate Year.
EXPORTING
I_YEAR = "Fiscal Year
IMPORTING
E_RECORD = "Export: Record - Returns Valid Year
E_VALID = "Export: Valid Flag - 1=Valid, 0 =Invalid
EXCEPTIONS
INCOMPLETE = 1
IMPORTING Parameters details for VALIDATE_YEAR
I_YEAR - Fiscal Year
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for VALIDATE_YEAR
E_RECORD - Export: Record - Returns Valid Year
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_VALID - Export: Valid Flag - 1=Valid, 0 =Invalid
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INCOMPLETE - Input Parameters Invalid or Incomplete
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for VALIDATE_YEAR Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_i_year | TYPE STRING, " | |||
| lv_e_record | TYPE STRING, " | |||
| lv_incomplete | TYPE STRING, " | |||
| lv_e_valid | TYPE STRING. " |
| CALL FUNCTION 'VALIDATE_YEAR' "Joint Venture Validate Year |
| EXPORTING | ||
| I_YEAR | = lv_i_year | |
| IMPORTING | ||
| E_RECORD | = lv_e_record | |
| E_VALID | = lv_e_valid | |
| EXCEPTIONS | ||
| INCOMPLETE = 1 | ||
| . " VALIDATE_YEAR | ||
ABAP code using 7.40 inline data declarations to call FM VALIDATE_YEAR
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects