SAP CMIG_CUST_READ_OTYPES_ACT Function Module for NOTRANSL: Customizing: Objekttypen Arbeitsplan lesen
CMIG_CUST_READ_OTYPES_ACT is a standard cmig cust read otypes act 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: Customizing: Objekttypen Arbeitsplan lesen 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 cmig cust read otypes act FM, simply by entering the name CMIG_CUST_READ_OTYPES_ACT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMIG_CUST
Program Name: SAPLCMIG_CUST
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CMIG_CUST_READ_OTYPES_ACT 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 'CMIG_CUST_READ_OTYPES_ACT'"NOTRANSL: Customizing: Objekttypen Arbeitsplan lesen.
IMPORTING
EX_OTYPES_ACT = "Customizing for iPPE Migration: Routing Object Types
EXCEPTIONS
GENERAL_ERROR = 1
EXPORTING Parameters details for CMIG_CUST_READ_OTYPES_ACT
EX_OTYPES_ACT - Customizing for iPPE Migration: Routing Object Types
Data type: CMIG_OTYPES_ACTOptional: No
Call by Reference: Yes
EXCEPTIONS details
GENERAL_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CMIG_CUST_READ_OTYPES_ACT 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_ex_otypes_act | TYPE CMIG_OTYPES_ACT, " | |||
| lv_general_error | TYPE CMIG_OTYPES_ACT. " |
|   CALL FUNCTION 'CMIG_CUST_READ_OTYPES_ACT' "NOTRANSL: Customizing: Objekttypen Arbeitsplan lesen |
| IMPORTING | ||
| EX_OTYPES_ACT | = lv_ex_otypes_act | |
| EXCEPTIONS | ||
| GENERAL_ERROR = 1 | ||
| . " CMIG_CUST_READ_OTYPES_ACT | ||
ABAP code using 7.40 inline data declarations to call FM CMIG_CUST_READ_OTYPES_ACT
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.Search for further information about these or an SAP related objects