SAP GRPC_ESA_ATTRIBUTE_VALUE Function Module for Obsolete: PC Get attribute values
GRPC_ESA_ATTRIBUTE_VALUE is a standard grpc esa attribute value SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Obsolete: PC Get attribute values 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 grpc esa attribute value FM, simply by entering the name GRPC_ESA_ATTRIBUTE_VALUE into the relevant SAP transaction such as SE37 or SE38.
Function Group: GRPC_ESA
Program Name: SAPLGRPC_ESA
Main Program: SAPLGRPC_ESA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function GRPC_ESA_ATTRIBUTE_VALUE 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 'GRPC_ESA_ATTRIBUTE_VALUE'"Obsolete: PC Get attribute values.
EXPORTING
I_ATTR_NAME = "Attribute
IMPORTING
ET_ATTRIBUTE_VALUE = "Attribute values
IMPORTING Parameters details for GRPC_ESA_ATTRIBUTE_VALUE
I_ATTR_NAME - Attribute
Data type: GRPC_ATTRNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for GRPC_ESA_ATTRIBUTE_VALUE
ET_ATTRIBUTE_VALUE - Attribute values
Data type: GRPC_ESA_T_ATTR_VALUEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GRPC_ESA_ATTRIBUTE_VALUE 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_attr_name | TYPE GRPC_ATTRNAME, " | |||
| lv_et_attribute_value | TYPE GRPC_ESA_T_ATTR_VALUE. " |
|   CALL FUNCTION 'GRPC_ESA_ATTRIBUTE_VALUE' "Obsolete: PC Get attribute values |
| EXPORTING | ||
| I_ATTR_NAME | = lv_i_attr_name | |
| IMPORTING | ||
| ET_ATTRIBUTE_VALUE | = lv_et_attribute_value | |
| . " GRPC_ESA_ATTRIBUTE_VALUE | ||
ABAP code using 7.40 inline data declarations to call FM GRPC_ESA_ATTRIBUTE_VALUE
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