SAP CMS_UI_OMS_PCN_ON_DISPLAY Function Module for Event handler for 'Display in release'
CMS_UI_OMS_PCN_ON_DISPLAY is a standard cms ui oms pcn on display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Event handler for 'Display in release' 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 oms pcn on display FM, simply by entering the name CMS_UI_OMS_PCN_ON_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMS_UI_OMS_PCN
Program Name: SAPLCMS_UI_OMS_PCN
Main Program: SAPLCMS_UI_OMS_PCN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CMS_UI_OMS_PCN_ON_DISPLAY 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_OMS_PCN_ON_DISPLAY'"Event handler for 'Display in release'.
EXPORTING
I_REL_OBJECT_KEY = "Object Key (Chain of Object Key Fields)
EXCEPTIONS
NO_SUCCESS = 1
IMPORTING Parameters details for CMS_UI_OMS_PCN_ON_DISPLAY
I_REL_OBJECT_KEY - Object Key (Chain of Object Key Fields)
Data type: BCA_DTE_OBJECT_KEYOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_SUCCESS -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CMS_UI_OMS_PCN_ON_DISPLAY 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_no_success | TYPE STRING, " | |||
lv_i_rel_object_key | TYPE BCA_DTE_OBJECT_KEY. " |
  CALL FUNCTION 'CMS_UI_OMS_PCN_ON_DISPLAY' "Event handler for 'Display in release' |
EXPORTING | ||
I_REL_OBJECT_KEY | = lv_i_rel_object_key | |
EXCEPTIONS | ||
NO_SUCCESS = 1 | ||
. " CMS_UI_OMS_PCN_ON_DISPLAY |
ABAP code using 7.40 inline data declarations to call FM CMS_UI_OMS_PCN_ON_DISPLAY
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