SAP CMS_UI_PCN_BDT_GET_PARAM Function Module for Fetch BDT Parameters from common event handler buffer

Search SAP Function Modules

CMS_UI_PCN_BDT_GET_PARAM is a standard cms ui pcn bdt get param SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fetch BDT Parameters from common event handler buffer 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 cms ui pcn bdt get param FM, simply by entering the name CMS_UI_PCN_BDT_GET_PARAM into the relevant SAP transaction such as SE37 or SE38.

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

Function CMS_UI_PCN_BDT_GET_PARAM 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 'CMS_UI_PCN_BDT_GET_PARAM'"Fetch BDT Parameters from common event handler buffer
 IMPORTING
   E_OBJECT_ID =  "CMS Object Identifier
   E_OBJ_PROC_GUID =  "Object Identification Number
   E_STR_CUR_ACTVT =  "Process object
   E_UI_ACT =  "UI activity
   E_FSTAT_VAR =  "Field Status Variant
   E_APPL_OBJ =  "BDT: Application Object
   E_STATE =  "Indicator

.

EXPORTING Parameters details for CMS_UI_PCN_BDT_GET_PARAM

E_OBJECT_ID - CMS Object Identifier

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

E_OBJ_PROC_GUID - Object Identification Number

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

E_STR_CUR_ACTVT - Process object

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

E_UI_ACT - UI activity

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

E_FSTAT_VAR - Field Status Variant

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

E_APPL_OBJ - BDT: Application Object

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

E_STATE - Indicator

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

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

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