SAP BPAR_R_BPCENTRAL_PAYMENT Function Module for NOTRANSL: Lesen der Zahlungsdaten eines G-Partners aus dem globalem Memory

Search SAP Function Modules

BPAR_R_BPCENTRAL_PAYMENT is a standard bpar r bpcentral payment 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 Zahlungsdaten 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 payment FM, simply by entering the name BPAR_R_BPCENTRAL_PAYMENT 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_PAYMENT 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_PAYMENT'"NOTRANSL: Lesen der Zahlungsdaten eines G-Partners aus dem globalem Memory
  EXPORTING
*  PARTNER = ' ' "Partner number
*  PROCCESSING_MODE = ' ' "Business partner: Interface flag
*  BUKRS = ' ' "Company Code
*  CUSTOMER = ' ' "Customer Number

 IMPORTING
   FLG_FIRST_LOAD =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
   BPDZAHL_OUT =  "BP Structure Payment Data (Company Code)

TABLES
*  T_BPDZAHL_OUT =  "BP Structure Payment Data (Company Code)

EXCEPTIONS
   NO_ENTRY_FOUND = 1 

.

IMPORTING Parameters details for BPAR_R_BPCENTRAL_PAYMENT

PARTNER - Partner number

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

PROCCESSING_MODE - Business partner: Interface flag

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

BUKRS - Company Code

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

CUSTOMER - Customer Number

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

EXPORTING Parameters details for BPAR_R_BPCENTRAL_PAYMENT

FLG_FIRST_LOAD - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

BPDZAHL_OUT - BP Structure Payment Data (Company Code)

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

TABLES Parameters details for BPAR_R_BPCENTRAL_PAYMENT

T_BPDZAHL_OUT - BP Structure Payment Data (Company Code)

Data type: BPDZAHL
Optional: Yes
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_PAYMENT 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 BPAR_R_BPCENTRAL_PAYMENT

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