SAP BPAR_M_CENTRAL_MODIFY_EXECUTE Function Module for NOTRANSL: Geschäftspartner: Durchführung der Verbuchung der zentralen Date









BPAR_M_CENTRAL_MODIFY_EXECUTE is a standard bpar m central modify execute 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: Geschäftspartner: Durchführung der Verbuchung der zentralen Date 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 bpar m central modify execute FM, simply by entering the name BPAR_M_CENTRAL_MODIFY_EXECUTE into the relevant SAP transaction such as SE37 or SE38.

Function Group: BPM0
Program Name: SAPLBPM0
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1



Function BPAR_M_CENTRAL_MODIFY_EXECUTE 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 'BPAR_M_CENTRAL_MODIFY_EXECUTE'"NOTRANSL: Geschäftspartner: Durchführung der Verbuchung der zentralen Date
  EXPORTING
   N_BP000 =  "Business Partner Master (General Data)
   O_BP000 =  "Business Partner Master (General Data)
*  I_ZGP =  "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

TABLES
   N_BP011 =  "Change Document Structure; Generated by RSSCD000
   N_BP021 =  "Change Document Structure; Generated by RSSCD000
   O_BP011 =  "Change Document Structure; Generated by RSSCD000
   O_BP021 =  "Change Document Structure; Generated by RSSCD000
.



IMPORTING Parameters details for BPAR_M_CENTRAL_MODIFY_EXECUTE

N_BP000 - Business Partner Master (General Data)

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

O_BP000 - Business Partner Master (General Data)

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

I_ZGP - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

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

TABLES Parameters details for BPAR_M_CENTRAL_MODIFY_EXECUTE

N_BP011 - Change Document Structure; Generated by RSSCD000

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

N_BP021 - Change Document Structure; Generated by RSSCD000

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

O_BP011 - Change Document Structure; Generated by RSSCD000

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

O_BP021 - Change Document Structure; Generated by RSSCD000

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

Copy and paste ABAP code example for BPAR_M_CENTRAL_MODIFY_EXECUTE 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_n_bp000  TYPE BP000, "   
lt_n_bp011  TYPE STANDARD TABLE OF DBP011, "   
lt_n_bp021  TYPE STANDARD TABLE OF DBP021, "   
lv_o_bp000  TYPE BP000, "   
lv_i_zgp  TYPE BOOLE-BOOLE, "   
lt_o_bp011  TYPE STANDARD TABLE OF DBP011, "   
lt_o_bp021  TYPE STANDARD TABLE OF DBP021. "   

  CALL FUNCTION 'BPAR_M_CENTRAL_MODIFY_EXECUTE'  "NOTRANSL: Geschäftspartner: Durchführung der Verbuchung der zentralen Date
    EXPORTING
         N_BP000 = lv_n_bp000
         O_BP000 = lv_o_bp000
         I_ZGP = lv_i_zgp
    TABLES
         N_BP011 = lt_n_bp011
         N_BP021 = lt_n_bp021
         O_BP011 = lt_o_bp011
         O_BP021 = lt_o_bp021
. " BPAR_M_CENTRAL_MODIFY_EXECUTE




ABAP code using 7.40 inline data declarations to call FM BPAR_M_CENTRAL_MODIFY_EXECUTE

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 BOOLE FROM BOOLE INTO @DATA(ld_i_zgp).
 
 
 


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!