SAP ISU_REFVALUE_SET_PROPERTY Function Module for Module for Set Property
ISU_REFVALUE_SET_PROPERTY is a standard isu refvalue set property SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Module for Set Property 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 refvalue set property FM, simply by entering the name ISU_REFVALUE_SET_PROPERTY into the relevant SAP transaction such as SE37 or SE38.
Function Group: E20D
Program Name: SAPLE20D
Main Program: SAPLE20D
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_REFVALUE_SET_PROPERTY 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_REFVALUE_SET_PROPERTY'"Module for Set Property.
EXPORTING
X_OPERAND = "Operand
X_OPLFDNR = "Sequence Number of an Operand
* X_BETRART = "
* X_NEW_TRE = "
* X_AB = "
X_PROPERTY = "Field Name
X_VALUE = "Input line
* X_ANLAGE = "Installation
* X_SUPPRESS = ' ' "
CHANGING
XY_FACTS_AUTO = "
* XY_TRE_LINE = "
EXCEPTIONS
GENERAL_FAULT = 1 INVALID_PROPERTY_FOR_TYPE = 2 INVALID_PROPERTY = 3 INVALID_VALUE = 4
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_SAPLE20D_001 IS-U: PAI Checks for Customer Fields in the Reference Values
EXIT_SAPLE20D_002 Preassigned Reference Values
EXIT_SAPLE20D_003 Called Before the Customer Subscreen for Reference Values is Called
EXIT_SAPLE20D_004 Called after Calling Up Customer Subscreen for Reference Values
IMPORTING Parameters details for ISU_REFVALUE_SET_PROPERTY
X_OPERAND - Operand
Data type: E_OPERANDOptional: No
Call by Reference: Yes
X_OPLFDNR - Sequence Number of an Operand
Data type: OPLFDNROptional: No
Call by Reference: Yes
X_BETRART -
Data type: BETRARTOptional: Yes
Call by Reference: Yes
X_NEW_TRE -
Data type: BOOLE-BOOLEOptional: Yes
Call by Reference: Yes
X_AB -
Data type: ABZEITSCHOptional: Yes
Call by Reference: Yes
X_PROPERTY - Field Name
Data type: DYNFNAMOptional: No
Call by Reference: Yes
X_VALUE - Input line
Data type: ANYOptional: No
Call by Reference: Yes
X_ANLAGE - Installation
Data type: ANLAGEOptional: Yes
Call by Reference: Yes
X_SUPPRESS -
Data type: AUTO_MERGEDefault: SPACE
Optional: Yes
Call by Reference: Yes
CHANGING Parameters details for ISU_REFVALUE_SET_PROPERTY
XY_FACTS_AUTO -
Data type: ISU20_INSTLN_FACTS_AUTOOptional: No
Call by Reference: Yes
XY_TRE_LINE -
Data type: TABIXOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
GENERAL_FAULT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_PROPERTY_FOR_TYPE -
Data type:Optional: No
Call by Reference: Yes
INVALID_PROPERTY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_VALUE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_REFVALUE_SET_PROPERTY 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_operand | TYPE E_OPERAND, " | |||
| lv_general_fault | TYPE E_OPERAND, " | |||
| lv_xy_facts_auto | TYPE ISU20_INSTLN_FACTS_AUTO, " | |||
| lv_x_oplfdnr | TYPE OPLFDNR, " | |||
| lv_xy_tre_line | TYPE TABIX, " | |||
| lv_invalid_property_for_type | TYPE TABIX, " | |||
| lv_x_betrart | TYPE BETRART, " | |||
| lv_invalid_property | TYPE BETRART, " | |||
| lv_x_new_tre | TYPE BOOLE-BOOLE, " | |||
| lv_invalid_value | TYPE BOOLE, " | |||
| lv_x_ab | TYPE ABZEITSCH, " | |||
| lv_x_property | TYPE DYNFNAM, " | |||
| lv_x_value | TYPE ANY, " | |||
| lv_x_anlage | TYPE ANLAGE, " | |||
| lv_x_suppress | TYPE AUTO_MERGE. " SPACE |
|   CALL FUNCTION 'ISU_REFVALUE_SET_PROPERTY' "Module for Set Property |
| EXPORTING | ||
| X_OPERAND | = lv_x_operand | |
| X_OPLFDNR | = lv_x_oplfdnr | |
| X_BETRART | = lv_x_betrart | |
| X_NEW_TRE | = lv_x_new_tre | |
| X_AB | = lv_x_ab | |
| X_PROPERTY | = lv_x_property | |
| X_VALUE | = lv_x_value | |
| X_ANLAGE | = lv_x_anlage | |
| X_SUPPRESS | = lv_x_suppress | |
| CHANGING | ||
| XY_FACTS_AUTO | = lv_xy_facts_auto | |
| XY_TRE_LINE | = lv_xy_tre_line | |
| EXCEPTIONS | ||
| GENERAL_FAULT = 1 | ||
| INVALID_PROPERTY_FOR_TYPE = 2 | ||
| INVALID_PROPERTY = 3 | ||
| INVALID_VALUE = 4 | ||
| . " ISU_REFVALUE_SET_PROPERTY | ||
ABAP code using 7.40 inline data declarations to call FM ISU_REFVALUE_SET_PROPERTY
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 BOOLE FROM BOOLE INTO @DATA(ld_x_new_tre). | ||||
| DATA(ld_x_suppress) | = ' '. | |||
Search for further information about these or an SAP related objects