SAP BPAR_R_PAYMENT Function Module for NOTRANSL: Lesen Zahlungsdaten









BPAR_R_PAYMENT is a standard bpar r 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 Zahlungsdaten 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 payment FM, simply by entering the name BPAR_R_PAYMENT into the relevant SAP transaction such as SE37 or SE38.

Function Group: BPR0
Program Name: SAPLBPR0
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BPAR_R_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_PAYMENT'"NOTRANSL: Lesen Zahlungsdaten
EXPORTING
PAYMENT_IN = "BP Structure Payment Data (Company Code)
* ZGP = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
* I_XMEMORY = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
* I_XWA = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')

IMPORTING
PAYMENT_OUT = "BP Structure Payment Data (Company Code)

EXCEPTIONS
PAYMENT_NOT_FOUND = 1
.



IMPORTING Parameters details for BPAR_R_PAYMENT

PAYMENT_IN - BP Structure Payment Data (Company Code)

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

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)

I_XMEMORY - 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)

I_XWA - 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)

EXPORTING Parameters details for BPAR_R_PAYMENT

PAYMENT_OUT - BP Structure Payment Data (Company Code)

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

EXCEPTIONS details

PAYMENT_NOT_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_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.

DATA:
lv_payment_in  TYPE BPDZAHL, "   
lv_payment_out  TYPE BPDZAHL, "   
lv_payment_not_found  TYPE BPDZAHL, "   
lv_zgp  TYPE BOOLE-BOOLE, "   
lv_i_xmemory  TYPE BOOLE-BOOLE, "   
lv_i_xwa  TYPE BOOLE-BOOLE. "   

  CALL FUNCTION 'BPAR_R_PAYMENT'  "NOTRANSL: Lesen Zahlungsdaten
    EXPORTING
         PAYMENT_IN = lv_payment_in
         ZGP = lv_zgp
         I_XMEMORY = lv_i_xmemory
         I_XWA = lv_i_xwa
    IMPORTING
         PAYMENT_OUT = lv_payment_out
    EXCEPTIONS
        PAYMENT_NOT_FOUND = 1
. " BPAR_R_PAYMENT




ABAP code using 7.40 inline data declarations to call FM BPAR_R_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.

 
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_zgp).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xmemory).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xwa).
 


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!