SAP FM_CHANGE_AA_FILL_FMZUCH Function Module for









FM_CHANGE_AA_FILL_FMZUCH is a standard fm change aa fill fmzuch 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 fill fmzuch FM, simply by entering the name FM_CHANGE_AA_FILL_FMZUCH 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): Normal Function Module
Update:



Function FM_CHANGE_AA_FILL_FMZUCH 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_FILL_FMZUCH'"
EXPORTING
I_ENV = "
I_TABLENAME = "Characteristic Derivation: Parameter
I_STEPID = "Step identifier
I_TAB_NEW_ENTRIES = "ABADR: Table Type Rule Entries (Internal)
I_TAB_DELETED_ENTRIES = "ABADR: Table Type Rule Entries (Internal)

CHANGING
E_REJECT = "Indicator
.




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_FILL_FMZUCH

I_ENV -

Data type: ABADR_ENV
Optional: No
Call by Reference: Yes

I_TABLENAME - Characteristic Derivation: Parameter

Data type: ABADRPARAM
Optional: No
Call by Reference: Yes

I_STEPID - Step identifier

Data type: ABADRSTEPID
Optional: No
Call by Reference: Yes

I_TAB_NEW_ENTRIES - ABADR: Table Type Rule Entries (Internal)

Data type: ABADR_TAB_RULE_ENTRIES
Optional: No
Call by Reference: Yes

I_TAB_DELETED_ENTRIES - ABADR: Table Type Rule Entries (Internal)

Data type: ABADR_TAB_RULE_ENTRIES
Optional: No
Call by Reference: Yes

CHANGING Parameters details for FM_CHANGE_AA_FILL_FMZUCH

E_REJECT - Indicator

Data type: ABADR_FLAG
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FM_CHANGE_AA_FILL_FMZUCH 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_env  TYPE ABADR_ENV, "   
lv_e_reject  TYPE ABADR_FLAG, "   
lv_i_tablename  TYPE ABADRPARAM, "   
lv_i_stepid  TYPE ABADRSTEPID, "   
lv_i_tab_new_entries  TYPE ABADR_TAB_RULE_ENTRIES, "   
lv_i_tab_deleted_entries  TYPE ABADR_TAB_RULE_ENTRIES. "   

  CALL FUNCTION 'FM_CHANGE_AA_FILL_FMZUCH'  "
    EXPORTING
         I_ENV = lv_i_env
         I_TABLENAME = lv_i_tablename
         I_STEPID = lv_i_stepid
         I_TAB_NEW_ENTRIES = lv_i_tab_new_entries
         I_TAB_DELETED_ENTRIES = lv_i_tab_deleted_entries
    CHANGING
         E_REJECT = lv_e_reject
. " FM_CHANGE_AA_FILL_FMZUCH




ABAP code using 7.40 inline data declarations to call FM FM_CHANGE_AA_FILL_FMZUCH

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!