SAP ISU_CREATE_DOWN_PAYM_REQUEST Function Module for Post: down payment request









ISU_CREATE_DOWN_PAYM_REQUEST is a standard isu create down paym request SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Post: down payment request 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 isu create down paym request FM, simply by entering the name ISU_CREATE_DOWN_PAYM_REQUEST into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_CREATE_DOWN_PAYM_REQUEST 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 'ISU_CREATE_DOWN_PAYM_REQUEST'"Post: down payment request
EXPORTING
* X_FKKKO = "Document header
* X_UPDATE_TASK = "
* X_RESOB = "
* X_RESKEY = "
* X_FKKOP = "
X_VKORG = "
* X_VBELN = "Quotation Number

IMPORTING
Y_OPBEL = "Assigned Document Number
Y_OKCODE = "

TABLES
* T_FKKOP = "Line Items (Open Items)
* T_FKKOPK = "Line Items (Offsetting Items)
* T_FKKOPW = "Line Items (Repetition Specifications)
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLE31B_100 User Exit: Determine Amount of Down Payment Request

IMPORTING Parameters details for ISU_CREATE_DOWN_PAYM_REQUEST

X_FKKKO - Document header

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

X_UPDATE_TASK -

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

X_RESOB -

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

X_RESKEY -

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

X_FKKOP -

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

X_VKORG -

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

X_VBELN - Quotation Number

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

EXPORTING Parameters details for ISU_CREATE_DOWN_PAYM_REQUEST

Y_OPBEL - Assigned Document Number

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

Y_OKCODE -

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

TABLES Parameters details for ISU_CREATE_DOWN_PAYM_REQUEST

T_FKKOP - Line Items (Open Items)

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

T_FKKOPK - Line Items (Offsetting Items)

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

T_FKKOPW - Line Items (Repetition Specifications)

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

Copy and paste ABAP code example for ISU_CREATE_DOWN_PAYM_REQUEST 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:
lt_t_fkkop  TYPE STANDARD TABLE OF FKKOP, "   
lv_x_fkkko  TYPE FKKKO, "   
lv_y_opbel  TYPE FKKKO-OPBEL, "   
lt_t_fkkopk  TYPE STANDARD TABLE OF FKKOPK, "   
lv_y_okcode  TYPE SY-UCOMM, "   
lv_x_update_task  TYPE BOOLE-BOOLE, "   
lv_x_resob  TYPE DFKKSUMC-RESOB, "   
lt_t_fkkopw  TYPE STANDARD TABLE OF FKKOPW, "   
lv_x_reskey  TYPE DFKKSUMC-RESKY, "   
lv_x_fkkop  TYPE FKKOP, "   
lv_x_vkorg  TYPE VBAK-VKORG, "   
lv_x_vbeln  TYPE VBAK-VBELN. "   

  CALL FUNCTION 'ISU_CREATE_DOWN_PAYM_REQUEST'  "Post: down payment request
    EXPORTING
         X_FKKKO = lv_x_fkkko
         X_UPDATE_TASK = lv_x_update_task
         X_RESOB = lv_x_resob
         X_RESKEY = lv_x_reskey
         X_FKKOP = lv_x_fkkop
         X_VKORG = lv_x_vkorg
         X_VBELN = lv_x_vbeln
    IMPORTING
         Y_OPBEL = lv_y_opbel
         Y_OKCODE = lv_y_okcode
    TABLES
         T_FKKOP = lt_t_fkkop
         T_FKKOPK = lt_t_fkkopk
         T_FKKOPW = lt_t_fkkopw
. " ISU_CREATE_DOWN_PAYM_REQUEST




ABAP code using 7.40 inline data declarations to call FM ISU_CREATE_DOWN_PAYM_REQUEST

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_y_opbel).
 
 
"SELECT single UCOMM FROM SY INTO @DATA(ld_y_okcode).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_x_update_task).
 
"SELECT single RESOB FROM DFKKSUMC INTO @DATA(ld_x_resob).
 
 
"SELECT single RESKY FROM DFKKSUMC INTO @DATA(ld_x_reskey).
 
 
"SELECT single VKORG FROM VBAK INTO @DATA(ld_x_vkorg).
 
"SELECT single VBELN FROM VBAK INTO @DATA(ld_x_vbeln).
 


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!