SAP BPAR_M_BPCENTRAL_UPDATE Function Module for NOTRANSL: Sichern eines G-Partners in der Datenbank









BPAR_M_BPCENTRAL_UPDATE is a standard bpar m bpcentral update 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: Sichern eines G-Partners in der Datenbank 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 bpcentral update FM, simply by entering the name BPAR_M_BPCENTRAL_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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



Function BPAR_M_BPCENTRAL_UPDATE 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_BPCENTRAL_UPDATE'"NOTRANSL: Sichern eines G-Partners in der Datenbank
EXPORTING
PARTNER = "Business Partner Number

EXCEPTIONS
ERROR = 1
.



IMPORTING Parameters details for BPAR_M_BPCENTRAL_UPDATE

PARTNER - Business Partner Number

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

EXCEPTIONS details

ERROR -

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

Copy and paste ABAP code example for BPAR_M_BPCENTRAL_UPDATE 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_error  TYPE STRING, "   
lv_partner  TYPE BP000-PARTNR. "   

  CALL FUNCTION 'BPAR_M_BPCENTRAL_UPDATE'  "NOTRANSL: Sichern eines G-Partners in der Datenbank
    EXPORTING
         PARTNER = lv_partner
    EXCEPTIONS
        ERROR = 1
. " BPAR_M_BPCENTRAL_UPDATE




ABAP code using 7.40 inline data declarations to call FM BPAR_M_BPCENTRAL_UPDATE

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 PARTNR FROM BP000 INTO @DATA(ld_partner).
 


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!