SAP CE_I_GET_STATUS Function Module for NOTRANSL: Statusinformation der vorliegenden Konfiguration

Search SAP Function Modules

CE_I_GET_STATUS is a standard ce i get status 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: Statusinformation der vorliegenden Konfiguration 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 ce i get status FM, simply by entering the name CE_I_GET_STATUS into the relevant SAP transaction such as SE37 or SE38.

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

Function CE_I_GET_STATUS 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 'CE_I_GET_STATUS'"NOTRANSL: Statusinformation der vorliegenden Konfiguration
  EXPORTING
   INSTANCE =  "
*  IV_RAISE_INCONSISTENCY = ' ' "Checkbox
*  IV_CUTRC = ' ' "

 IMPORTING
   EV_LOAD_ERROR =  "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

EXCEPTIONS
   FREE = 1    INCOMPLETE = 2    INCONSISTENT = 3    LOCKED = 4    INSTANCE_NOT_FOUND = 5    STATUS_NOT_FOUND = 6 

.

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_SAPLCEI0_001 User Exit: SD Customer Fields in a Configurable Instance
EXIT_SAPLCEI0_010 User Exit: Customer Pushbutton 01
EXIT_SAPLCEI0_011 User Exit: Customer Pushbutton 02
EXIT_SAPLCEI0_012 User Exit: Customer Pushbutton 03
EXIT_SAPLCEI0_013 User Exit: Customer Pushbutton 04
EXIT_SAPLCEI0_014 User Exit: Customer Pushbutton 05
EXIT_SAPLCEI0_015 User Exit: Customer Pushbutton 06
EXIT_SAPLCEI0_016 User Exit: Customer Pushbutton 07
EXIT_SAPLCEI0_017 User Exit: Customer Pushbutton 08
EXIT_SAPLCEI0_018 User Exit: Customer Pushbutton 09
EXIT_SAPLCEI0_019 User Exit: Customer Pushbutton 10
EXIT_SAPLCEI0_020 Switch Off Standard Batch-Input Screen 0109
EXIT_SAPLCEI0_021 Assigned Values Files and Object Characteristics
EXIT_SAPLCEI0_022 Change presentation of F4 help
EXIT_SAPLCEI0_023 Activate Search for Material Variant with Same Values

IMPORTING Parameters details for CE_I_GET_STATUS

INSTANCE -

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

IV_RAISE_INCONSISTENCY - Checkbox

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_CUTRC -

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

EXPORTING Parameters details for CE_I_GET_STATUS

EV_LOAD_ERROR - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

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

EXCEPTIONS details

FREE -

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

INCOMPLETE -

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

INCONSISTENT -

Data type:
Optional: No
Call by Reference: Yes

LOCKED -

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

INSTANCE_NOT_FOUND -

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

STATUS_NOT_FOUND -

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

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

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