SAP CLD2UPS_DISPLAY Function Module for Display object dependency
CLD2UPS_DISPLAY is a standard cld2ups 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 Display object dependency 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 cld2ups display FM, simply by entering the name CLD2UPS_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: CLD2UPS
Program Name: SAPLCLD2UPS
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CLD2UPS_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 'CLD2UPS_DISPLAY'"Display object dependency.
EXPORTING
IM_OBJID = "ALE Distribution Packet : Object Key
IM_OBJVAL = "ALE Distribution Packet: Object Validity
* IM_MESCOD = 'MOD' "
* IM_DIRECT = '1' "
IMPORTING Parameters details for CLD2UPS_DISPLAY
IM_OBJID - ALE Distribution Packet : Object Key
Data type: UPS_C_OBJIDOptional: No
Call by Reference: Yes
IM_OBJVAL - ALE Distribution Packet: Object Validity
Data type: UPS_C_OBJVALOptional: No
Call by Reference: Yes
IM_MESCOD -
Data type: UPS_C_MESCODDefault: 'MOD'
Optional: Yes
Call by Reference: Yes
IM_DIRECT -
Data type: UPS_C_DIRECTDefault: '1'
Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for CLD2UPS_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_im_objid | TYPE UPS_C_OBJID, " | |||
| lv_im_objval | TYPE UPS_C_OBJVAL, " | |||
| lv_im_mescod | TYPE UPS_C_MESCOD, " 'MOD' | |||
| lv_im_direct | TYPE UPS_C_DIRECT. " '1' |
|   CALL FUNCTION 'CLD2UPS_DISPLAY' "Display object dependency |
| EXPORTING | ||
| IM_OBJID | = lv_im_objid | |
| IM_OBJVAL | = lv_im_objval | |
| IM_MESCOD | = lv_im_mescod | |
| IM_DIRECT | = lv_im_direct | |
| . " CLD2UPS_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM CLD2UPS_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.| DATA(ld_im_mescod) | = 'MOD'. | |||
| DATA(ld_im_direct) | = '1'. | |||
Search for further information about these or an SAP related objects