SAP CBCM_IPPE_SUBSCREEN_EXPORT_APO Function Module for Classification: Subscreen Fields Return to Basic Screen
CBCM_IPPE_SUBSCREEN_EXPORT_APO is a standard cbcm ippe subscreen export apo SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Classification: Subscreen Fields Return to Basic Screen 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 cbcm ippe subscreen export apo FM, simply by entering the name CBCM_IPPE_SUBSCREEN_EXPORT_APO into the relevant SAP transaction such as SE37 or SE38.
Function Group: CPPEAPO_CLASS
Program Name: SAPLCPPEAPO_CLASS
Main Program: SAPLCPPEAPO_CLASS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CBCM_IPPE_SUBSCREEN_EXPORT_APO 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 'CBCM_IPPE_SUBSCREEN_EXPORT_APO'"Classification: Subscreen Fields Return to Basic Screen.
EXPORTING
ERMCBC = "Übergabe von Feldern für die Bildbausteine
* MODIFY = ' ' "Speziell CL20N: Modifizieren Bildbausteine 1xx
* OK_CODE = ' ' "Speziell CL20N: OK-Code OBJA für Anzeige Objekt
* READ_OBJECT = ' ' "Speziell CL20N: Kennzeichen lesen Objekt
* TABLE = ' ' "Tabellenname des zu klassifizierenden Objekts
IMPORTING Parameters details for CBCM_IPPE_SUBSCREEN_EXPORT_APO
ERMCBC - Übergabe von Feldern für die Bildbausteine
Data type: RMCBCOptional: No
Call by Reference: No ( called with pass by value option)
MODIFY - Speziell CL20N: Modifizieren Bildbausteine 1xx
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OK_CODE - Speziell CL20N: OK-Code OBJA für Anzeige Objekt
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
READ_OBJECT - Speziell CL20N: Kennzeichen lesen Objekt
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLE - Tabellenname des zu klassifizierenden Objekts
Data type: TCLT-OBTABDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CBCM_IPPE_SUBSCREEN_EXPORT_APO 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_ermcbc | TYPE RMCBC, " | |||
| lv_modify | TYPE RMCBC, " SPACE | |||
| lv_ok_code | TYPE RMCBC, " SPACE | |||
| lv_read_object | TYPE RMCBC, " SPACE | |||
| lv_table | TYPE TCLT-OBTAB. " SPACE |
|   CALL FUNCTION 'CBCM_IPPE_SUBSCREEN_EXPORT_APO' "Classification: Subscreen Fields Return to Basic Screen |
| EXPORTING | ||
| ERMCBC | = lv_ermcbc | |
| MODIFY | = lv_modify | |
| OK_CODE | = lv_ok_code | |
| READ_OBJECT | = lv_read_object | |
| TABLE | = lv_table | |
| . " CBCM_IPPE_SUBSCREEN_EXPORT_APO | ||
ABAP code using 7.40 inline data declarations to call FM CBCM_IPPE_SUBSCREEN_EXPORT_APO
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_modify) | = ' '. | |||
| DATA(ld_ok_code) | = ' '. | |||
| DATA(ld_read_object) | = ' '. | |||
| "SELECT single OBTAB FROM TCLT INTO @DATA(ld_table). | ||||
| DATA(ld_table) | = ' '. | |||
Search for further information about these or an SAP related objects