SAP CO_IH_GET_EXECUTION_FLAGS Function Module for NOTRANSL: Lesen der Struktur 'ORDERS', Rückgabe der Flags

Search SAP Function Modules

CO_IH_GET_EXECUTION_FLAGS is a standard co ih get execution flags 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: Lesen der Struktur 'ORDERS', Rückgabe der Flags 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 co ih get execution flags FM, simply by entering the name CO_IH_GET_EXECUTION_FLAGS into the relevant SAP transaction such as SE37 or SE38.

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

Function CO_IH_GET_EXECUTION_FLAGS 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 'CO_IH_GET_EXECUTION_FLAGS'"NOTRANSL: Lesen der Struktur 'ORDERS', Rückgabe der Flags
  EXPORTING
   IV_AUFNR =  "Order Number

 IMPORTING
   EV_CA_ASS =  "Screens, display user entry
   EV_PSP_ASS =  "Screens, display user entry
   EV_PC_ASS =  "Screens, display user entry
   EV_PMSDO_ASS =  "Screens, display user entry
   EV_KOSTV_ASS =  "Screens, display user entry
   EV_FUNC_AREA_ASS =  "Screens, display user entry
   EV_KREDERROR =  "Return Value, Return Value after ABAP Statements
   EV_FM_AA_OC_LV_ACTIVATED =  "

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLCOIH_001 Create Maintenance Sub-Order: Customer-Specific Additions for Order Header
EXIT_SAPLCOIH_002 PM Order: Customer Exit Before Release
EXIT_SAPLCOIH_003 PM Order: USER-Specific Determination of Task Lists for PM Order
EXIT_SAPLCOIH_004 PM Order: Customer Exit for Technical Completion Event
EXIT_SAPLCOIH_005 PM Order: Customer Enhancement to Determine Profit Center
EXIT_SAPLCOIH_006 PM Order: Customer Enhancement for Exclusion of Function Codes
EXIT_SAPLCOIH_007 PM Order: Customer Enhancement for Permits
EXIT_SAPLCOIH_008 PM Order: Customer Enhancement to Determine Tax Jurisdiction Code
EXIT_SAPLCOIH_009 PM Order: Customer Check for 'Save' Event
EXIT_SAPLCOIH_010 PM Order: Customer Enhancement for Determination of WBS Element
EXIT_SAPLCOIH_012 Maintenance Order: Priority Handling on Central Header
EXIT_SAPLCOIH_014 Maintenance Order: Priority Handling on Central Header
EXIT_SAPLCOIH_015 PM Order: F4 Help for User Fields on Operation
EXIT_SAPLCOIH_016 PM Order: Check Entry of User Fields on Operation
EXIT_SAPLCOIH_017 PM Order: Determine External Order Number by Customer Logic
EXIT_SAPLCOIH_018 PM Order: User Fields for Order Header PBO
EXIT_SAPLCOIH_019 PM Order: Customer Enhancement for User Fields for Order Header PAI
EXIT_SAPLCOIH_020 PM Order: Automatic Inclusion of Task List Using IW31, IW34, IW36
EXIT_SAPLCOIH_021 PM: Automatic Task List Transfer when Order Generated from Notification
EXIT_SAPLCOIH_025 Customer Determination of Cost Center Responsible
EXIT_SAPLCOIH_026 Customer Check Status 'Not Performed'
EXIT_SAPLCOIH_030 Transfer User Fields from Maintenance Plan to Order
EXIT_SAPLCOIH_031 Hide personnel number in PM/SM order
EXIT_SAPLCOIH_032 Transfer User Fields from Notification to Order
EXIT_SAPLCOIH_100 Create Service Order: Customer Enhancements of Order Header

IMPORTING Parameters details for CO_IH_GET_EXECUTION_FLAGS

IV_AUFNR - Order Number

Data type: AUFNR
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CO_IH_GET_EXECUTION_FLAGS

EV_CA_ASS - Screens, display user entry

Data type: SY-DATAR
Optional: No
Call by Reference: No ( called with pass by value option)

EV_PSP_ASS - Screens, display user entry

Data type: SY-DATAR
Optional: No
Call by Reference: No ( called with pass by value option)

EV_PC_ASS - Screens, display user entry

Data type: SY-DATAR
Optional: No
Call by Reference: No ( called with pass by value option)

EV_PMSDO_ASS - Screens, display user entry

Data type: SY-DATAR
Optional: No
Call by Reference: No ( called with pass by value option)

EV_KOSTV_ASS - Screens, display user entry

Data type: SY-DATAR
Optional: No
Call by Reference: No ( called with pass by value option)

EV_FUNC_AREA_ASS - Screens, display user entry

Data type: SY-DATAR
Optional: No
Call by Reference: No ( called with pass by value option)

EV_KREDERROR - Return Value, Return Value after ABAP Statements

Data type: SY-SUBRC
Optional: No
Call by Reference: No ( called with pass by value option)

EV_FM_AA_OC_LV_ACTIVATED -

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

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

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