SAP BPAR_R_BPCENTRAL_CUSTOMER Function Module for NOTRANSL: Lesen der Debitordaten eines G-Partners aus dem globalem Memory
BPAR_R_BPCENTRAL_CUSTOMER is a standard bpar r bpcentral customer 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: Lesen der Debitordaten eines G-Partners aus dem globalem Memory 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 r bpcentral customer FM, simply by entering the name BPAR_R_BPCENTRAL_CUSTOMER 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:
Function BPAR_R_BPCENTRAL_CUSTOMER 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_R_BPCENTRAL_CUSTOMER'"NOTRANSL: Lesen der Debitordaten eines G-Partners aus dem globalem Memory.
EXPORTING
* PARTNER = ' ' "Partner number
* PROCCESSING_MODE = ' ' "Business partner: Interface flag
* CUSTOMER = ' ' "Customer number
* ZGP = ' ' "Single-Character Indicator
IMPORTING
FLG_FIRST_LOAD = "DE-EN-LANG-SWITCH-NO-TRANSLATION
KNA1_OUT = "General Data in Customer Master
EXCEPTIONS
NO_ENTRY_FOUND = 1
IMPORTING Parameters details for BPAR_R_BPCENTRAL_CUSTOMER
PARTNER - Partner number
Data type: BP000-PARTNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PROCCESSING_MODE - Business partner: Interface flag
Data type: BPIB0-BP_FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CUSTOMER - Customer number
Data type: BP000-CUSTOMERDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
ZGP - Single-Character Indicator
Data type: CHAR1Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BPAR_R_BPCENTRAL_CUSTOMER
FLG_FIRST_LOAD - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
KNA1_OUT - General Data in Customer Master
Data type: KNA1Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_ENTRY_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BPAR_R_BPCENTRAL_CUSTOMER 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_partner | TYPE BP000-PARTNR, " SPACE | |||
lv_flg_first_load | TYPE BP000, " | |||
lv_no_entry_found | TYPE BP000, " | |||
lv_kna1_out | TYPE KNA1, " | |||
lv_proccessing_mode | TYPE BPIB0-BP_FLAG, " SPACE | |||
lv_customer | TYPE BP000-CUSTOMER, " SPACE | |||
lv_zgp | TYPE CHAR1. " SPACE |
  CALL FUNCTION 'BPAR_R_BPCENTRAL_CUSTOMER' "NOTRANSL: Lesen der Debitordaten eines G-Partners aus dem globalem Memory |
EXPORTING | ||
PARTNER | = lv_partner | |
PROCCESSING_MODE | = lv_proccessing_mode | |
CUSTOMER | = lv_customer | |
ZGP | = lv_zgp | |
IMPORTING | ||
FLG_FIRST_LOAD | = lv_flg_first_load | |
KNA1_OUT | = lv_kna1_out | |
EXCEPTIONS | ||
NO_ENTRY_FOUND = 1 | ||
. " BPAR_R_BPCENTRAL_CUSTOMER |
ABAP code using 7.40 inline data declarations to call FM BPAR_R_BPCENTRAL_CUSTOMER
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). | ||||
DATA(ld_partner) | = ' '. | |||
"SELECT single BP_FLAG FROM BPIB0 INTO @DATA(ld_proccessing_mode). | ||||
DATA(ld_proccessing_mode) | = ' '. | |||
"SELECT single CUSTOMER FROM BP000 INTO @DATA(ld_customer). | ||||
DATA(ld_customer) | = ' '. | |||
DATA(ld_zgp) | = ' '. | |||
Search for further information about these or an SAP related objects