SAP RM_AGGR_BACKFLUSH Function Module for NOTRANSL: Aggregierter Sammelbackflush

Search SAP Function Modules

RM_AGGR_BACKFLUSH is a standard rm aggr backflush SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Aggregierter Sammelbackflush 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 rm aggr backflush FM, simply by entering the name RM_AGGR_BACKFLUSH into the relevant SAP transaction such as SE37 or SE38.

Function Group: RMAG
Program Name: SAPLRMAG
Main Program: SAPLRMAG
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RM_AGGR_BACKFLUSH 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 'RM_AGGR_BACKFLUSH'"NOTRANSL: Aggregierter Sammelbackflush
  EXPORTING
*  WAKZD_IMP = ' ' "Indicator: Post Goods Issue
*  FLKZD_IMP = ' ' "
*  KAPKZD_IMP = ' ' "Indicator: Reduce capacity requirements
*  NO_DIALOG_IMP = 'X' "
*  EXT_COMMIT_IMP = ' ' "
*  COMMIT_WAIT_IMP = 'X' "
*  PZPKT_IMP = '2' "

TABLES
   MDBPRX =  "
*  MSGPROT =  "Message Table

EXCEPTIONS
   INIT_ERROR = 1    GI_ERROR = 2    ACTIVITY_ERROR = 3    CAPA_ERROR = 4    PLANNED_ORDER_ERROR = 5    OT_ERROR = 6 

.

IMPORTING Parameters details for RM_AGGR_BACKFLUSH

WAKZD_IMP - Indicator: Post Goods Issue

Data type: RM61A-WAKZD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

FLKZD_IMP -

Data type: RM61A-FLKZD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

KAPKZD_IMP - Indicator: Reduce capacity requirements

Data type: RM61A-KAPKZD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_DIALOG_IMP -

Data type: RM61F-SELEKT
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXT_COMMIT_IMP -

Data type: RM61F-SELEKT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

COMMIT_WAIT_IMP -

Data type: RM61F-SELEKT
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PZPKT_IMP -

Data type: TPARU-PZPKT
Default: '2'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for RM_AGGR_BACKFLUSH

MDBPRX -

Data type: MDBPR
Optional: No
Call by Reference: No ( called with pass by value option)

MSGPROT - Message Table

Data type: CMFMSG
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

INIT_ERROR - Error During Initialization

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

GI_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ACTIVITY_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CAPA_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

PLANNED_ORDER_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

OT_ERROR - Other errors

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RM_AGGR_BACKFLUSH 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.

ABAP code using 7.40 inline data declarations to call FM RM_AGGR_BACKFLUSH

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