SAP CUPM_PMS_GET_VARIABLE Function Module for NOTRANSL: Ermittelt Detailinfos zu Variable im PMS
CUPM_PMS_GET_VARIABLE is a standard cupm pms get variable SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Ermittelt Detailinfos zu Variable im PMS 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 cupm pms get variable FM, simply by entering the name CUPM_PMS_GET_VARIABLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CUPM
Program Name: SAPLCUPM
Main Program: SAPLCUPM
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CUPM_PMS_GET_VARIABLE 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 'CUPM_PMS_GET_VARIABLE'"NOTRANSL: Ermittelt Detailinfos zu Variable im PMS.
EXPORTING
RULE_MAIN_ID = "Reference to rule group (constraint)
VARNAME = "Variable description
IMPORTING
VARTYPE = "
OBJ = "Object reference
VIRTUAL_CNT = "Secondary identifier of object reference
ATINN = "
RFLAG = "Type of variable
FORM = "Input form
EXCEPTIONS
FAIL = 1 INTERNAL_ERROR = 2
IMPORTING Parameters details for CUPM_PMS_GET_VARIABLE
RULE_MAIN_ID - Reference to rule group (constraint)
Data type: PMST_INT_KEYOptional: No
Call by Reference: No ( called with pass by value option)
VARNAME - Variable description
Data type: PMST_VARNAMEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CUPM_PMS_GET_VARIABLE
VARTYPE -
Data type: PMST_VARTYPEOptional: No
Call by Reference: No ( called with pass by value option)
OBJ - Object reference
Data type: PMST_OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
VIRTUAL_CNT - Secondary identifier of object reference
Data type: PMST_INTEGEROptional: No
Call by Reference: No ( called with pass by value option)
ATINN -
Data type: PMST_INT_KEYOptional: No
Call by Reference: No ( called with pass by value option)
RFLAG - Type of variable
Data type: PMST_VAL-RFLAGOptional: No
Call by Reference: No ( called with pass by value option)
FORM - Input form
Data type: PMST_VAR_FORMOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FAIL - Variable not in buffer (only FORCE_FLAG=FALSE)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CUPM_PMS_GET_VARIABLE 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_fail | TYPE STRING, " | |||
| lv_vartype | TYPE PMST_VARTYPE, " | |||
| lv_rule_main_id | TYPE PMST_INT_KEY, " | |||
| lv_obj | TYPE PMST_OBJECT, " | |||
| lv_varname | TYPE PMST_VARNAME, " | |||
| lv_internal_error | TYPE PMST_VARNAME, " | |||
| lv_virtual_cnt | TYPE PMST_INTEGER, " | |||
| lv_atinn | TYPE PMST_INT_KEY, " | |||
| lv_rflag | TYPE PMST_VAL-RFLAG, " | |||
| lv_form | TYPE PMST_VAR_FORM. " |
|   CALL FUNCTION 'CUPM_PMS_GET_VARIABLE' "NOTRANSL: Ermittelt Detailinfos zu Variable im PMS |
| EXPORTING | ||
| RULE_MAIN_ID | = lv_rule_main_id | |
| VARNAME | = lv_varname | |
| IMPORTING | ||
| VARTYPE | = lv_vartype | |
| OBJ | = lv_obj | |
| VIRTUAL_CNT | = lv_virtual_cnt | |
| ATINN | = lv_atinn | |
| RFLAG | = lv_rflag | |
| FORM | = lv_form | |
| EXCEPTIONS | ||
| FAIL = 1 | ||
| INTERNAL_ERROR = 2 | ||
| . " CUPM_PMS_GET_VARIABLE | ||
ABAP code using 7.40 inline data declarations to call FM CUPM_PMS_GET_VARIABLE
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 RFLAG FROM PMST_VAL INTO @DATA(ld_rflag). | ||||
Search for further information about these or an SAP related objects