SAP ISU_EVENT_140 Function Module for Example 0140: Determine Additional Industry Data for Down Payment/Charge
ISU_EVENT_140 is a standard isu event 140 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Example 0140: Determine Additional Industry Data for Down Payment/Charge 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 event 140 FM, simply by entering the name ISU_EVENT_140 into the relevant SAP transaction such as SE37 or SE38.
Function Group: E31C
Program Name: SAPLE31C
Main Program: SAPLE31C
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_EVENT_140 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_EVENT_140'"Example 0140: Determine Additional Industry Data for Down Payment/Charge.
EXPORTING
I_FKKKO = "Document header being generated
I_FKKCL = "Statistic items to be cleared
IMPORTING
E_FKKOPZF = "Industry-Specific Additional Data
E_FORCE_GSBER = "
E_FORCE_PRCTR = "
E_FORCE_SEGMENT = "
CHANGING
C_FKKOPSF = "
IMPORTING Parameters details for ISU_EVENT_140
I_FKKKO - Document header being generated
Data type: FKKKOOptional: No
Call by Reference: No ( called with pass by value option)
I_FKKCL - Statistic items to be cleared
Data type: FKKCLOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISU_EVENT_140
E_FKKOPZF - Industry-Specific Additional Data
Data type: FKKOPZFOptional: No
Call by Reference: No ( called with pass by value option)
E_FORCE_GSBER -
Data type: XFELDOptional: No
Call by Reference: No ( called with pass by value option)
E_FORCE_PRCTR -
Data type: XFELDOptional: No
Call by Reference: No ( called with pass by value option)
E_FORCE_SEGMENT -
Data type: XFELDOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for ISU_EVENT_140
C_FKKOPSF -
Data type: FKKOPSFOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_EVENT_140 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_i_fkkko | TYPE FKKKO, " | |||
| lv_c_fkkopsf | TYPE FKKOPSF, " | |||
| lv_e_fkkopzf | TYPE FKKOPZF, " | |||
| lv_i_fkkcl | TYPE FKKCL, " | |||
| lv_e_force_gsber | TYPE XFELD, " | |||
| lv_e_force_prctr | TYPE XFELD, " | |||
| lv_e_force_segment | TYPE XFELD. " |
|   CALL FUNCTION 'ISU_EVENT_140' "Example 0140: Determine Additional Industry Data for Down Payment/Charge |
| EXPORTING | ||
| I_FKKKO | = lv_i_fkkko | |
| I_FKKCL | = lv_i_fkkcl | |
| IMPORTING | ||
| E_FKKOPZF | = lv_e_fkkopzf | |
| E_FORCE_GSBER | = lv_e_force_gsber | |
| E_FORCE_PRCTR | = lv_e_force_prctr | |
| E_FORCE_SEGMENT | = lv_e_force_segment | |
| CHANGING | ||
| C_FKKOPSF | = lv_c_fkkopsf | |
| . " ISU_EVENT_140 | ||
ABAP code using 7.40 inline data declarations to call FM ISU_EVENT_140
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