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

Function J_1A_UPDATE_J1AMACOF 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_UPDATE_J1AMACOF'"Update of table J_1A002.
EXPORTING
I_J1AMACOF = "
I_CHANGE = "
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLJ1AF_001 User exit for Report J_1AF007 (Data of sender and recipient)
EXIT_SAPLJ1AF_002 User Exit for J_1AF012
EXIT_SAPLJ1AF_003 User Exit für J_1AF011
IMPORTING Parameters details for J_1A_UPDATE_J1AMACOF
I_J1AMACOF -
Data type: J_1AMACOFOptional: No
Call by Reference: No ( called with pass by value option)
I_CHANGE -
Data type: CDPOS-CHNGINDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for J_1A_UPDATE_J1AMACOF 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_j1amacof | TYPE J_1AMACOF, " | |||
| lv_i_change | TYPE CDPOS-CHNGIND. " |
|   CALL FUNCTION 'J_1A_UPDATE_J1AMACOF' "Update of table J_1A002 |
| EXPORTING | ||
| I_J1AMACOF | = lv_i_j1amacof | |
| I_CHANGE | = lv_i_change | |
| . " J_1A_UPDATE_J1AMACOF | ||
ABAP code using 7.40 inline data declarations to call FM J_1A_UPDATE_J1AMACOF
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 CHNGIND FROM CDPOS INTO @DATA(ld_i_change). | ||||
Search for further information about these or an SAP related objects