SAP FI_PAYMENT_REQUEST_GET_ZBUKR Function Module for

Search SAP Function Modules

FI_PAYMENT_REQUEST_GET_ZBUKR is a standard fi payment request get zbukr SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fi payment request get zbukr FM, simply by entering the name FI_PAYMENT_REQUEST_GET_ZBUKR into the relevant SAP transaction such as SE37 or SE38.

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

Function FI_PAYMENT_REQUEST_GET_ZBUKR 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 'FI_PAYMENT_REQUEST_GET_ZBUKR'"
  EXPORTING
   I_BUKRS =  "Company Code
*  I_ZBUKR =  "Paying Company Code for this Payment Request
*  I_ABSBU =  "Sending Company Code for Payment Requests
   I_ORIGIN =  "Origin Indicator
*  I_T042 =  "Parameters for payment transactions

 IMPORTING
   E_ZBUKR =  "
   E_ABSBU =  "

EXCEPTIONS
   ENTRY_NOT_FOUND = 1    ORIGIN_NOT_EXIST = 2    ZBUKR_NOT_VALID = 3 

.

IMPORTING Parameters details for FI_PAYMENT_REQUEST_GET_ZBUKR

I_BUKRS - Company Code

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

I_ZBUKR - Paying Company Code for this Payment Request

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

I_ABSBU - Sending Company Code for Payment Requests

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

I_ORIGIN - Origin Indicator

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

I_T042 - Parameters for payment transactions

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

EXPORTING Parameters details for FI_PAYMENT_REQUEST_GET_ZBUKR

E_ZBUKR -

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

E_ABSBU -

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

EXCEPTIONS details

ENTRY_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

ORIGIN_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

ZBUKR_NOT_VALID -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FI_PAYMENT_REQUEST_GET_ZBUKR 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 FI_PAYMENT_REQUEST_GET_ZBUKR

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