SAP ISU_SAMPLE_R388 Function Module for









ISU_SAMPLE_R388 is a standard isu sample r388 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 isu sample r388 FM, simply by entering the name ISU_SAMPLE_R388 into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_SAMPLE_R388 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_R388'"
EXPORTING
I_TE432 = "
I_ERCHZ = "
I_BILL_DOC = "
* I_ZEITANT = "

TABLES
T_MONAT = "
.



IMPORTING Parameters details for ISU_SAMPLE_R388

I_TE432 -

Data type: TE432
Optional: No
Call by Reference: Yes

I_ERCHZ -

Data type: ERCHZ
Optional: No
Call by Reference: Yes

I_BILL_DOC -

Data type: ISU2A_BILL_DOC
Optional: No
Call by Reference: Yes

I_ZEITANT -

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

TABLES Parameters details for ISU_SAMPLE_R388

T_MONAT -

Data type: ISU_BW_MONTH
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_SAMPLE_R388 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_te432  TYPE TE432, "   
lt_t_monat  TYPE STANDARD TABLE OF ISU_BW_MONTH, "   
lv_i_erchz  TYPE ERCHZ, "   
lv_i_bill_doc  TYPE ISU2A_BILL_DOC, "   
lv_i_zeitant  TYPE E_ZEITANT_L. "   

  CALL FUNCTION 'ISU_SAMPLE_R388'  "
    EXPORTING
         I_TE432 = lv_i_te432
         I_ERCHZ = lv_i_erchz
         I_BILL_DOC = lv_i_bill_doc
         I_ZEITANT = lv_i_zeitant
    TABLES
         T_MONAT = lt_t_monat
. " ISU_SAMPLE_R388




ABAP code using 7.40 inline data declarations to call FM ISU_SAMPLE_R388

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



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!