SAP OM_API_INIT_EDITOR_DARK Function Module for NOTRANSL: API f. dunkle Initialisierung Beziehungswisseneditor









OM_API_INIT_EDITOR_DARK is a standard om api init editor dark 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: API f. dunkle Initialisierung Beziehungswisseneditor 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 om api init editor dark FM, simply by entering the name OM_API_INIT_EDITOR_DARK into the relevant SAP transaction such as SE37 or SE38.

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



Function OM_API_INIT_EDITOR_DARK 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 'OM_API_INIT_EDITOR_DARK'"NOTRANSL: API f. dunkle Initialisierung Beziehungswisseneditor
EXPORTING
* IN_OBJECT_ID = 'IPPE' "
* IN_DATE = SY-DATUM "
* IN_APPLOBJ = 'CMP' "
IN_PNGUID = "
* IN_CLINT = "
* IN_AENNR = "
* IN_COLLECT_MSG = 'X' "Checkbox
* IN_BUFFER_REFRESH = ' ' "Checkbox

IMPORTING
OUT_INSTANCES = "
OUT_LOGHANDLE = "Application Log: Log Handle

EXCEPTIONS
INTERNAL_ERROR = 1 MSG_COLLECTOR_ERROR = 2
.



IMPORTING Parameters details for OM_API_INIT_EDITOR_DARK

IN_OBJECT_ID -

Data type: CO000_COMMON-OBJECT_ID
Default: 'IPPE'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IN_DATE -

Data type: CO000_COMMON-DATE
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

IN_APPLOBJ -

Data type: CO000_IPPE-APPLOBJ
Default: 'CMP'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IN_PNGUID -

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

IN_CLINT -

Data type: CO000_IPPE-CLINT
Optional: Yes
Call by Reference: No ( called with pass by value option)

IN_AENNR -

Data type: CO000_IPPE-AENNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

IN_COLLECT_MSG - Checkbox

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

IN_BUFFER_REFRESH - Checkbox

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

EXPORTING Parameters details for OM_API_INIT_EDITOR_DARK

OUT_INSTANCES -

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

OUT_LOGHANDLE - Application Log: Log Handle

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

EXCEPTIONS details

INTERNAL_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

MSG_COLLECTOR_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OM_API_INIT_EDITOR_DARK 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_in_object_id  TYPE CO000_COMMON-OBJECT_ID, "   'IPPE'
lv_out_instances  TYPE CO001_INSTANCES, "   
lv_internal_error  TYPE CO001_INSTANCES, "   
lv_in_date  TYPE CO000_COMMON-DATE, "   SY-DATUM
lv_out_loghandle  TYPE BALLOGHNDL, "   
lv_msg_collector_error  TYPE BALLOGHNDL, "   
lv_in_applobj  TYPE CO000_IPPE-APPLOBJ, "   'CMP'
lv_in_pnguid  TYPE CO000_IPPE-PNGUID, "   
lv_in_clint  TYPE CO000_IPPE-CLINT, "   
lv_in_aennr  TYPE CO000_IPPE-AENNR, "   
lv_in_collect_msg  TYPE XFELD, "   'X'
lv_in_buffer_refresh  TYPE XFELD. "   ' '

  CALL FUNCTION 'OM_API_INIT_EDITOR_DARK'  "NOTRANSL: API f. dunkle Initialisierung Beziehungswisseneditor
    EXPORTING
         IN_OBJECT_ID = lv_in_object_id
         IN_DATE = lv_in_date
         IN_APPLOBJ = lv_in_applobj
         IN_PNGUID = lv_in_pnguid
         IN_CLINT = lv_in_clint
         IN_AENNR = lv_in_aennr
         IN_COLLECT_MSG = lv_in_collect_msg
         IN_BUFFER_REFRESH = lv_in_buffer_refresh
    IMPORTING
         OUT_INSTANCES = lv_out_instances
         OUT_LOGHANDLE = lv_out_loghandle
    EXCEPTIONS
        INTERNAL_ERROR = 1
        MSG_COLLECTOR_ERROR = 2
. " OM_API_INIT_EDITOR_DARK




ABAP code using 7.40 inline data declarations to call FM OM_API_INIT_EDITOR_DARK

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.

"SELECT single OBJECT_ID FROM CO000_COMMON INTO @DATA(ld_in_object_id).
DATA(ld_in_object_id) = 'IPPE'.
 
 
 
"SELECT single DATE FROM CO000_COMMON INTO @DATA(ld_in_date).
DATA(ld_in_date) = SY-DATUM.
 
 
 
"SELECT single APPLOBJ FROM CO000_IPPE INTO @DATA(ld_in_applobj).
DATA(ld_in_applobj) = 'CMP'.
 
"SELECT single PNGUID FROM CO000_IPPE INTO @DATA(ld_in_pnguid).
 
"SELECT single CLINT FROM CO000_IPPE INTO @DATA(ld_in_clint).
 
"SELECT single AENNR FROM CO000_IPPE INTO @DATA(ld_in_aennr).
 
DATA(ld_in_collect_msg) = 'X'.
 
DATA(ld_in_buffer_refresh) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!