SAP CMT_PFOLDER_PBO_INIT Function Module for NOTRANSL: Initialisierung der Funktionsgruppe zu PBO
CMT_PFOLDER_PBO_INIT is a standard cmt pfolder pbo init SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Initialisierung der Funktionsgruppe zu 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 cmt pfolder pbo init FM, simply by entering the name CMT_PFOLDER_PBO_INIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMT_PFOLDER
Program Name: SAPLCMT_PFOLDER
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CMT_PFOLDER_PBO_INIT 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 'CMT_PFOLDER_PBO_INIT'"NOTRANSL: Initialisierung der Funktionsgruppe zu PBO.
EXPORTING
I_SCREEN = "CM: Screen Proxy for Field Transport, OK Code Processing
* I_OBJECT_INDEX = 1 "DE-EN-LANG-SWITCH-NO-TRANSLATION
* I_EDIT_STATUS = '02' "Status of a Configuration Management Object
* I_VALID_FROM = "Valid-from Time
IMPORTING
E_REPID = "ABAP Program: Current Main Program
E_DYNNR = "ABAP Program, Current Screen Number
IMPORTING Parameters details for CMT_PFOLDER_PBO_INIT
I_SCREEN - CM: Screen Proxy for Field Transport, OK Code Processing
Data type: CL_GCM_SCREENOptional: No
Call by Reference: Yes
I_OBJECT_INDEX - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: IDefault: 1
Optional: Yes
Call by Reference: Yes
I_EDIT_STATUS - Status of a Configuration Management Object
Data type: DE_CM_STATUSDefault: '02'
Optional: Yes
Call by Reference: Yes
I_VALID_FROM - Valid-from Time
Data type: TIMESTAMPOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CMT_PFOLDER_PBO_INIT
E_REPID - ABAP Program: Current Main Program
Data type: SYST-REPIDOptional: No
Call by Reference: No ( called with pass by value option)
E_DYNNR - ABAP Program, Current Screen Number
Data type: SYST-DYNNROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CMT_PFOLDER_PBO_INIT 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_e_repid | TYPE SYST-REPID, " | |||
| lv_i_screen | TYPE CL_GCM_SCREEN, " | |||
| lv_e_dynnr | TYPE SYST-DYNNR, " | |||
| lv_i_object_index | TYPE I, " 1 | |||
| lv_i_edit_status | TYPE DE_CM_STATUS, " '02' | |||
| lv_i_valid_from | TYPE TIMESTAMP. " |
|   CALL FUNCTION 'CMT_PFOLDER_PBO_INIT' "NOTRANSL: Initialisierung der Funktionsgruppe zu PBO |
| EXPORTING | ||
| I_SCREEN | = lv_i_screen | |
| I_OBJECT_INDEX | = lv_i_object_index | |
| I_EDIT_STATUS | = lv_i_edit_status | |
| I_VALID_FROM | = lv_i_valid_from | |
| IMPORTING | ||
| E_REPID | = lv_e_repid | |
| E_DYNNR | = lv_e_dynnr | |
| . " CMT_PFOLDER_PBO_INIT | ||
ABAP code using 7.40 inline data declarations to call FM CMT_PFOLDER_PBO_INIT
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 SYST INTO @DATA(ld_e_repid). | ||||
| "SELECT single DYNNR FROM SYST INTO @DATA(ld_e_dynnr). | ||||
| DATA(ld_i_object_index) | = 1. | |||
| DATA(ld_i_edit_status) | = '02'. | |||
Search for further information about these or an SAP related objects