SAP CCM_APPL_AREA_PBO Function Module for Application Area PBO
CCM_APPL_AREA_PBO is a standard ccm appl area pbo SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Application Area PBO 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 ccm appl area pbo FM, simply by entering the name CCM_APPL_AREA_PBO into the relevant SAP transaction such as SE37 or SE38.
Function Group: CCM14
Program Name: SAPLCCM14
Main Program: SAPLCCM14
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CCM_APPL_AREA_PBO 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 'CCM_APPL_AREA_PBO'"Application Area PBO.
EXPORTING
X_HANDLE = "
IMPORTING
Y_SUB_REPID = "
Y_SUB_DYNNR = "
EXCEPTIONS
INVALID_HANDLE = 1
IMPORTING Parameters details for CCM_APPL_AREA_PBO
X_HANDLE -
Data type: CIC0_HANDLEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CCM_APPL_AREA_PBO
Y_SUB_REPID -
Data type: SY-REPIDOptional: No
Call by Reference: No ( called with pass by value option)
Y_SUB_DYNNR -
Data type: SY-DYNNROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_HANDLE - invalid handle
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CCM_APPL_AREA_PBO 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_x_handle | TYPE CIC0_HANDLE, " | |||
| lv_y_sub_repid | TYPE SY-REPID, " | |||
| lv_invalid_handle | TYPE SY, " | |||
| lv_y_sub_dynnr | TYPE SY-DYNNR. " |
|   CALL FUNCTION 'CCM_APPL_AREA_PBO' "Application Area PBO |
| EXPORTING | ||
| X_HANDLE | = lv_x_handle | |
| IMPORTING | ||
| Y_SUB_REPID | = lv_y_sub_repid | |
| Y_SUB_DYNNR | = lv_y_sub_dynnr | |
| EXCEPTIONS | ||
| INVALID_HANDLE = 1 | ||
| . " CCM_APPL_AREA_PBO | ||
ABAP code using 7.40 inline data declarations to call FM CCM_APPL_AREA_PBO
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 REPID FROM SY INTO @DATA(ld_y_sub_repid). | ||||
| "SELECT single DYNNR FROM SY INTO @DATA(ld_y_sub_dynnr). | ||||
Search for further information about these or an SAP related objects