SAP FKK_PAYMENT_ORDER_READ Function Module for

Search SAP Function Modules

FKK_PAYMENT_ORDER_READ is a standard fkk payment order read 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 fkk payment order read FM, simply by entering the name FKK_PAYMENT_ORDER_READ into the relevant SAP transaction such as SE37 or SE38.

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

Function FKK_PAYMENT_ORDER_READ 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 'FKK_PAYMENT_ORDER_READ'"
  EXPORTING
*  I_KEY_ITEM =  "Paid items
*  I_PYORD =  "Payment Order
*  I_WITH_ENQUEUE = ' ' "
*  I_ANY_STATUS = ' ' "

 IMPORTING
   E_FKKPOH =  "Payment Order: Header Data
   E_PYORD =  "
   E_NWBTR =  "
   E_DIFFB =  "
   E_WAERS =  "
   E_STAZA =  "
   E_GSBER =  "Business Area
   E_PRCTR =  "
   E_INDPAY =  "Payment Specification: Payment Data

TABLES
*  T_FKKPOP =  "Payment Order: Item Data

EXCEPTIONS
   NOTHING_FOUND = 1    LOCKED = 2 

.

IMPORTING Parameters details for FKK_PAYMENT_ORDER_READ

I_KEY_ITEM - Paid items

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

I_PYORD - Payment Order

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

I_WITH_ENQUEUE -

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

I_ANY_STATUS -

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

EXPORTING Parameters details for FKK_PAYMENT_ORDER_READ

E_FKKPOH - Payment Order: Header Data

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

E_PYORD -

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

E_NWBTR -

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

E_DIFFB -

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

E_WAERS -

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

E_STAZA -

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

E_GSBER - Business Area

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

E_PRCTR -

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

E_INDPAY - Payment Specification: Payment Data

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

TABLES Parameters details for FKK_PAYMENT_ORDER_READ

T_FKKPOP - Payment Order: Item Data

Data type: DFKKPOP
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

NOTHING_FOUND - No payment order found

Data type:
Optional: No
Call by Reference: Yes

LOCKED -

Data type:
Optional: No
Call by Reference: Yes

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

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