SAP J_1A_SET_LOCK_DATE Function Module for Set locked dates for inflation indexes
J_1A_SET_LOCK_DATE is a standard j 1a set lock date SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set locked dates for inflation indexes 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 j 1a set lock date FM, simply by entering the name J_1A_SET_LOCK_DATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: J1A7
Program Name: SAPLJ1A7
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function J_1A_SET_LOCK_DATE 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 'J_1A_SET_LOCK_DATE'"Set locked dates for inflation indexes.
EXPORTING
APPLICATION_CALL = "
* I_BUKRS = "
IMPORTING Parameters details for J_1A_SET_LOCK_DATE
APPLICATION_CALL -
Data type: J_1AINFT26-J_1AAPPLKPOptional: No
Call by Reference: No ( called with pass by value option)
I_BUKRS -
Data type: T001-BUKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for J_1A_SET_LOCK_DATE 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_application_call | TYPE J_1AINFT26-J_1AAPPLKP, " | |||
| lv_i_bukrs | TYPE T001-BUKRS. " |
|   CALL FUNCTION 'J_1A_SET_LOCK_DATE' "Set locked dates for inflation indexes |
| EXPORTING | ||
| APPLICATION_CALL | = lv_application_call | |
| I_BUKRS | = lv_i_bukrs | |
| . " J_1A_SET_LOCK_DATE | ||
ABAP code using 7.40 inline data declarations to call FM J_1A_SET_LOCK_DATE
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.| "SELECT single J_1AAPPLKP FROM J_1AINFT26 INTO @DATA(ld_application_call). | ||||
| "SELECT single BUKRS FROM T001 INTO @DATA(ld_i_bukrs). | ||||
Search for further information about these or an SAP related objects