SAP FM_CHANGE_AA_P Function Module for
FM_CHANGE_AA_P is a standard fm change aa p SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fm change aa p FM, simply by entering the name FM_CHANGE_AA_P into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMCH
Program Name: SAPLFMCH
Main Program: SAPLFMCH
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function FM_CHANGE_AA_P 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 'FM_CHANGE_AA_P'".
EXPORTING
* I_HRDCHG = ' ' "Checkbox
* I_AVC = ' ' "Checkbox
* I_BLCDOC = 'X' "Checkbox
* I_CHGDOC = 'X' "Checkbox
* I_RWIN = 'X' "Checkbox
* I_SIMUL = 'X' "Checkbox
* I_TCODE = SY-TCODE "Current Transaction Code
* I_BUDAT = SY-DATUM "Posting Date in the Document
IMPORTING
E_T_RETURN = "FM: Return Parameter for Commitment Documents
TABLES
C_T_FMCHA1 = "Work List for Reassignment Tool
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_SAPLFMCH_001 Determine FM Account Assignment from Coding Block
EXIT_SAPLFMCH_002 Own Table Updates During Reassignment
EXIT_SAPLFMCH_003 Change of Account Assignment, Reject Reassignment
IMPORTING Parameters details for FM_CHANGE_AA_P
I_HRDCHG - Checkbox
Data type: FMDY-XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_AVC - Checkbox
Data type: FMDY-XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_BLCDOC - Checkbox
Data type: FMDY-XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_CHGDOC - Checkbox
Data type: FMDY-XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_RWIN - Checkbox
Data type: FMDY-XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SIMUL - Checkbox
Data type: FMDY-XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_TCODE - Current Transaction Code
Data type: SY-TCODEDefault: SY-TCODE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_BUDAT - Posting Date in the Document
Data type: BUDATDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FM_CHANGE_AA_P
E_T_RETURN - FM: Return Parameter for Commitment Documents
Data type: FM_T_OIRETURNOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FM_CHANGE_AA_P
C_T_FMCHA1 - Work List for Reassignment Tool
Data type: FMCHA1Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FM_CHANGE_AA_P 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_hrdchg | TYPE FMDY-XFELD, " SPACE | |||
lt_c_t_fmcha1 | TYPE STANDARD TABLE OF FMCHA1, " | |||
lv_e_t_return | TYPE FM_T_OIRETURN, " | |||
lv_i_avc | TYPE FMDY-XFELD, " SPACE | |||
lv_i_blcdoc | TYPE FMDY-XFELD, " 'X' | |||
lv_i_chgdoc | TYPE FMDY-XFELD, " 'X' | |||
lv_i_rwin | TYPE FMDY-XFELD, " 'X' | |||
lv_i_simul | TYPE FMDY-XFELD, " 'X' | |||
lv_i_tcode | TYPE SY-TCODE, " SY-TCODE | |||
lv_i_budat | TYPE BUDAT. " SY-DATUM |
  CALL FUNCTION 'FM_CHANGE_AA_P' " |
EXPORTING | ||
I_HRDCHG | = lv_i_hrdchg | |
I_AVC | = lv_i_avc | |
I_BLCDOC | = lv_i_blcdoc | |
I_CHGDOC | = lv_i_chgdoc | |
I_RWIN | = lv_i_rwin | |
I_SIMUL | = lv_i_simul | |
I_TCODE | = lv_i_tcode | |
I_BUDAT | = lv_i_budat | |
IMPORTING | ||
E_T_RETURN | = lv_e_t_return | |
TABLES | ||
C_T_FMCHA1 | = lt_c_t_fmcha1 | |
. " FM_CHANGE_AA_P |
ABAP code using 7.40 inline data declarations to call FM FM_CHANGE_AA_P
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 XFELD FROM FMDY INTO @DATA(ld_i_hrdchg). | ||||
DATA(ld_i_hrdchg) | = ' '. | |||
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_avc). | ||||
DATA(ld_i_avc) | = ' '. | |||
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_blcdoc). | ||||
DATA(ld_i_blcdoc) | = 'X'. | |||
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_chgdoc). | ||||
DATA(ld_i_chgdoc) | = 'X'. | |||
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_rwin). | ||||
DATA(ld_i_rwin) | = 'X'. | |||
"SELECT single XFELD FROM FMDY INTO @DATA(ld_i_simul). | ||||
DATA(ld_i_simul) | = 'X'. | |||
"SELECT single TCODE FROM SY INTO @DATA(ld_i_tcode). | ||||
DATA(ld_i_tcode) | = SY-TCODE. | |||
DATA(ld_i_budat) | = SY-DATUM. | |||
Search for further information about these or an SAP related objects