SAP ISU_OPVALUE_INPUT Function Module for INTERNAL: Check Operand Values for an Operand

Search SAP Function Modules

ISU_OPVALUE_INPUT is a standard isu opvalue input SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Check Operand Values for an Operand 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 opvalue input FM, simply by entering the name ISU_OPVALUE_INPUT into the relevant SAP transaction such as SE37 or SE38.

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

Function ISU_OPVALUE_INPUT 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_OPVALUE_INPUT'"INTERNAL: Check Operand Values for an Operand
  EXPORTING
   X_OBJTYPE =  "
*  X_EANL =  "
*  X_RTPIFACEDATA =  "RTP Interface Data
*  X_NO_RT_CHECK =  "Indicator
   X_OPKEY =  "
*  X_BEGFACTS =  "
*  X_BEGABRPE =  "
*  X_BEGNACH =  "
*  X_BEGEND =  "
   X_IAKLASSE =  "
   X_IRATECAT =  "
*  X_ETRF_OPERAND =  "

TABLES
   T_OPHIST =  "
   T_COMP_OPHIST =  "

EXCEPTIONS
   SYSTEM_ERROR = 1    INPUT_ERROR = 2 

.

IMPORTING Parameters details for ISU_OPVALUE_INPUT

X_OBJTYPE -

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

X_EANL -

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

X_RTPIFACEDATA - RTP Interface Data

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

X_NO_RT_CHECK - Indicator

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

X_OPKEY -

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

X_BEGFACTS -

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

X_BEGABRPE -

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

X_BEGNACH -

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

X_BEGEND -

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

X_IAKLASSE -

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

X_IRATECAT -

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

X_ETRF_OPERAND -

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

TABLES Parameters details for ISU_OPVALUE_INPUT

T_OPHIST -

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

T_COMP_OPHIST -

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

EXCEPTIONS details

SYSTEM_ERROR -

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

INPUT_ERROR -

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

Copy and paste ABAP code example for ISU_OPVALUE_INPUT 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.

ABAP code using 7.40 inline data declarations to call FM ISU_OPVALUE_INPUT

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