SAP ISU_SAMPLE_R610 Function Module for Sample: Set Document Type
ISU_SAMPLE_R610 is a standard isu sample r610 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Sample: Set Document Type 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 r610 FM, simply by entering the name ISU_SAMPLE_R610 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_SAMPLE_R610 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_R610'"Sample: Set Document Type.
EXPORTING
X_RE31B = "
IMPORTING
Y_BLART = "Document Type
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_SAMPLE_R610
X_RE31B -
Data type: RE31BOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISU_SAMPLE_R610
Y_BLART - Document Type
Data type: RE31B-BLARTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_SAMPLE_R610 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_x_re31b | TYPE RE31B, " | |||
| lv_y_blart | TYPE RE31B-BLART. " |
|   CALL FUNCTION 'ISU_SAMPLE_R610' "Sample: Set Document Type |
| EXPORTING | ||
| X_RE31B | = lv_x_re31b | |
| IMPORTING | ||
| Y_BLART | = lv_y_blart | |
| . " ISU_SAMPLE_R610 | ||
ABAP code using 7.40 inline data declarations to call FM ISU_SAMPLE_R610
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 BLART FROM RE31B INTO @DATA(ld_y_blart). | ||||
Search for further information about these or an SAP related objects