SAP CK50_PROCESS_DISPLAY_2 Function Module for Display Business Process
CK50_PROCESS_DISPLAY_2 is a standard ck50 process display 2 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 Business Process 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 ck50 process display 2 FM, simply by entering the name CK50_PROCESS_DISPLAY_2 into the relevant SAP transaction such as SE37 or SE38.
Function Group: CK50
Program Name: SAPLCK50
Main Program: SAPLCK50
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CK50_PROCESS_DISPLAY_2 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 'CK50_PROCESS_DISPLAY_2'"Display Business Process.
EXPORTING
KOKRS_IMP = "
PRZNR_IMP = "
DATE_IMP = "
IMPORTING Parameters details for CK50_PROCESS_DISPLAY_2
KOKRS_IMP -
Data type: CKKALKTAB-KOKRS_HRKOptional: No
Call by Reference: No ( called with pass by value option)
PRZNR_IMP -
Data type: CKKALKTAB-PRZNROptional: No
Call by Reference: No ( called with pass by value option)
DATE_IMP -
Data type: CKKALKTAB-STEASOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CK50_PROCESS_DISPLAY_2 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_kokrs_imp | TYPE CKKALKTAB-KOKRS_HRK, " | |||
| lv_prznr_imp | TYPE CKKALKTAB-PRZNR, " | |||
| lv_date_imp | TYPE CKKALKTAB-STEAS. " |
|   CALL FUNCTION 'CK50_PROCESS_DISPLAY_2' "Display Business Process |
| EXPORTING | ||
| KOKRS_IMP | = lv_kokrs_imp | |
| PRZNR_IMP | = lv_prznr_imp | |
| DATE_IMP | = lv_date_imp | |
| . " CK50_PROCESS_DISPLAY_2 | ||
ABAP code using 7.40 inline data declarations to call FM CK50_PROCESS_DISPLAY_2
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 KOKRS_HRK FROM CKKALKTAB INTO @DATA(ld_kokrs_imp). | ||||
| "SELECT single PRZNR FROM CKKALKTAB INTO @DATA(ld_prznr_imp). | ||||
| "SELECT single STEAS FROM CKKALKTAB INTO @DATA(ld_date_imp). | ||||
Search for further information about these or an SAP related objects