SAP FKK_PAYMENT_ORDER_GET_PAYDOC Function Module for









FKK_PAYMENT_ORDER_GET_PAYDOC is a standard fkk payment order get paydoc 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 get paydoc FM, simply by entering the name FKK_PAYMENT_ORDER_GET_PAYDOC 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_GET_PAYDOC 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_GET_PAYDOC'"
EXPORTING
I_PYORD = "Payment Order

IMPORTING
E_OPBEL = "Payment Document
E_STILL_OPEN = "
.



IMPORTING Parameters details for FKK_PAYMENT_ORDER_GET_PAYDOC

I_PYORD - Payment Order

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

EXPORTING Parameters details for FKK_PAYMENT_ORDER_GET_PAYDOC

E_OPBEL - Payment Document

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

E_STILL_OPEN -

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

Copy and paste ABAP code example for FKK_PAYMENT_ORDER_GET_PAYDOC 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_e_opbel  TYPE FKKKO-OPBEL, "   
lv_i_pyord  TYPE DFKKPOH-PYORD, "   
lv_e_still_open  TYPE BOOLE-BOOLE. "   

  CALL FUNCTION 'FKK_PAYMENT_ORDER_GET_PAYDOC'  "
    EXPORTING
         I_PYORD = lv_i_pyord
    IMPORTING
         E_OPBEL = lv_e_opbel
         E_STILL_OPEN = lv_e_still_open
. " FKK_PAYMENT_ORDER_GET_PAYDOC




ABAP code using 7.40 inline data declarations to call FM FKK_PAYMENT_ORDER_GET_PAYDOC

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 OPBEL FROM FKKKO INTO @DATA(ld_e_opbel).
 
"SELECT single PYORD FROM DFKKPOH INTO @DATA(ld_i_pyord).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_still_open).
 


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!