SAP ISU_SAMPLE_3090 Function Module for Reads Application-Specific Additional Criteria
ISU_SAMPLE_3090 is a standard isu sample 3090 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Reads Application-Specific Additional Criteria 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 sample 3090 FM, simply by entering the name ISU_SAMPLE_3090 into the relevant SAP transaction such as SE37 or SE38.
Function Group: E311
Program Name: SAPLE311
Main Program: SAPLE311
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_SAMPLE_3090 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_SAMPLE_3090'"Reads Application-Specific Additional Criteria.
EXPORTING
I_FKKOP = "Business Partner Items in Contract Account Document
IMPORTING
E_CRITERIA = "
E_FIELDNAME = "
IMPORTING Parameters details for ISU_SAMPLE_3090
I_FKKOP - Business Partner Items in Contract Account Document
Data type: FKKOPOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISU_SAMPLE_3090
E_CRITERIA -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_FIELDNAME -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_SAMPLE_3090 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_fkkop | TYPE FKKOP, " | |||
| lv_e_criteria | TYPE FKKOP, " | |||
| lv_e_fieldname | TYPE FKKOP. " |
|   CALL FUNCTION 'ISU_SAMPLE_3090' "Reads Application-Specific Additional Criteria |
| EXPORTING | ||
| I_FKKOP | = lv_i_fkkop | |
| IMPORTING | ||
| E_CRITERIA | = lv_e_criteria | |
| E_FIELDNAME | = lv_e_fieldname | |
| . " ISU_SAMPLE_3090 | ||
ABAP code using 7.40 inline data declarations to call FM ISU_SAMPLE_3090
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