SAP CTO_ORDERS_GET_AIM_META_DATA Function Module for

Search SAP Function Modules

CTO_ORDERS_GET_AIM_META_DATA is a standard cto orders get aim meta data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 cto orders get aim meta data FM, simply by entering the name CTO_ORDERS_GET_AIM_META_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: SCTO
Program Name: SAPLSCTO
Main Program: SAPLSCTO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CTO_ORDERS_GET_AIM_META_DATA 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 'CTO_ORDERS_GET_AIM_META_DATA'"
  EXPORTING
   IT_REQUESTS =  "
*  IT_SKIP_METHODS =  "
   IV_IS_UPGRADE =  "
   IT_START_RELEASES =  "
*  IV_CHECK_START_RELEASES =  "
*  IV_ADJ_LOCK_MODE_TO_START_REL = ' ' "
*  IT_FORCED_XPRAS =  "
*  IV_IGNORE_TP7_AIMS = ABAP_FALSE "

 IMPORTING
   ET_METHODS_BRIDGE =  "
   ET_XPRAS_POST_PROC =  "
   ET_XPRAS_SHADOW =  "
   ET_XPRAS_BRIDGE =  "
   ET_TAB_XPRAS =  "
   ET_METHODS_POST_PROC =  "
   ET_METHODS_DOWNTIME =  "
   ET_METHODS_SHADOW =  "
   ET_TABLES =  "
   ET_TABLES_ERR =  "
   ET_MESSAGES =  "
   ET_TAB_METHS_BRIDGE =  "
   ET_XPRAS_DOWNTIME =  "

.

IMPORTING Parameters details for CTO_ORDERS_GET_AIM_META_DATA

IT_REQUESTS -

Data type: E070_T
Optional: No
Call by Reference: Yes

IT_SKIP_METHODS -

Data type: TRMTD_METHOD_CALLS
Optional: Yes
Call by Reference: Yes

IV_IS_UPGRADE -

Data type: BOOLE_D
Optional: No
Call by Reference: Yes

IT_START_RELEASES -

Data type: CVERSS
Optional: No
Call by Reference: Yes

IV_CHECK_START_RELEASES -

Data type: ABAP_BOOL
Optional: Yes
Call by Reference: Yes

IV_ADJ_LOCK_MODE_TO_START_REL -

Data type: ABAP_BOOL
Default: SPACE
Optional: Yes
Call by Reference: Yes

IT_FORCED_XPRAS -

Data type: SCTS_XPRA_RESULTS
Optional: Yes
Call by Reference: Yes

IV_IGNORE_TP7_AIMS -

Data type: ABAP_BOOL
Default: ABAP_FALSE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CTO_ORDERS_GET_AIM_META_DATA

ET_METHODS_BRIDGE -

Data type: TRMTD_METHOD_CALLS
Optional: No
Call by Reference: Yes

ET_XPRAS_POST_PROC -

Data type: SCTS_XPRA_RESULTS
Optional: No
Call by Reference: Yes

ET_XPRAS_SHADOW -

Data type: SCTS_XPRA_RESULTS
Optional: No
Call by Reference: Yes

ET_XPRAS_BRIDGE -

Data type: SCTS_XPRA_RESULTS
Optional: No
Call by Reference: Yes

ET_TAB_XPRAS -

Data type: TRMTD_TAB_XPRAS
Optional: No
Call by Reference: Yes

ET_METHODS_POST_PROC -

Data type: TRMTD_METHOD_CALLS
Optional: No
Call by Reference: Yes

ET_METHODS_DOWNTIME -

Data type: TRMTD_METHOD_CALLS
Optional: No
Call by Reference: Yes

ET_METHODS_SHADOW -

Data type: TRMTD_METHOD_CALLS
Optional: No
Call by Reference: Yes

ET_TABLES -

Data type: OBJMT_TAB
Optional: No
Call by Reference: Yes

ET_TABLES_ERR -

Data type: OB_AIM_TABNAMES
Optional: No
Call by Reference: Yes

ET_MESSAGES -

Data type: SPROT_U_T
Optional: No
Call by Reference: Yes

ET_TAB_METHS_BRIDGE -

Data type: TRMTD_TAB_METHOD_FBS
Optional: No
Call by Reference: Yes

ET_XPRAS_DOWNTIME -

Data type: SCTS_XPRA_RESULTS
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CTO_ORDERS_GET_AIM_META_DATA 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.

ABAP code using 7.40 inline data declarations to call FM CTO_ORDERS_GET_AIM_META_DATA

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