SAP ECOP_UTILS_ORGOBJECTS_ENGINE Function Module for NOTRANSL: Generische Benhandlung von Orgobjekten
ECOP_UTILS_ORGOBJECTS_ENGINE is a standard ecop utils orgobjects engine 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: Generische Benhandlung von Orgobjekten 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 ecop utils orgobjects engine FM, simply by entering the name ECOP_UTILS_ORGOBJECTS_ENGINE into the relevant SAP transaction such as SE37 or SE38.
Function Group: ECOP_UTILS
Program Name: SAPLECOP_UTILS
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ECOP_UTILS_ORGOBJECTS_ENGINE 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 'ECOP_UTILS_ORGOBJECTS_ENGINE'"NOTRANSL: Generische Benhandlung von Orgobjekten.
EXPORTING
IV_BUSINESS_OBJECT = "DE-EN-LANG-SWITCH-NO-TRANSLATION
* IV_ACTION = 'COPY' "DE-EN-LANG-SWITCH-NO-TRANSLATION
IV_SOURCE_ENTITY = "Source Value
* IV_TARGET_ENTITY = "Target Value
* IV_DIALOGUE = 'X' "Online
* IV_TR_ORDER = "
* IV_TR_TASK = "
* IV_LEAVE_ENGINE = 'X' "
IMPORTING
RET_CODE = "Return Code
EV_TARGET_ENTITY = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EV_TR_ORDER = "
EV_TR_TASK = "
IMPORTING Parameters details for ECOP_UTILS_ORGOBJECTS_ENGINE
IV_BUSINESS_OBJECT - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: SWO_OBJTYPOptional: No
Call by Reference: No ( called with pass by value option)
IV_ACTION - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: CHAR4Default: 'COPY'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_SOURCE_ENTITY - Source Value
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IV_TARGET_ENTITY - Target Value
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_DIALOGUE - Online
Data type: CHAR1Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_TR_ORDER -
Data type: E070-TRKORROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_TR_TASK -
Data type: E070-TRKORROptional: Yes
Call by Reference: No ( called with pass by value option)
IV_LEAVE_ENGINE -
Data type: CHAR1Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ECOP_UTILS_ORGOBJECTS_ENGINE
RET_CODE - Return Code
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
EV_TARGET_ENTITY - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EV_TR_ORDER -
Data type: E070-TRKORROptional: No
Call by Reference: No ( called with pass by value option)
EV_TR_TASK -
Data type: E070-TRKORROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ECOP_UTILS_ORGOBJECTS_ENGINE 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_ret_code | TYPE SY-SUBRC, " | |||
| lv_iv_business_object | TYPE SWO_OBJTYP, " | |||
| lv_iv_action | TYPE CHAR4, " 'COPY' | |||
| lv_ev_target_entity | TYPE CHAR4, " | |||
| lv_ev_tr_order | TYPE E070-TRKORR, " | |||
| lv_iv_source_entity | TYPE E070, " | |||
| lv_ev_tr_task | TYPE E070-TRKORR, " | |||
| lv_iv_target_entity | TYPE E070, " | |||
| lv_iv_dialogue | TYPE CHAR1, " 'X' | |||
| lv_iv_tr_order | TYPE E070-TRKORR, " | |||
| lv_iv_tr_task | TYPE E070-TRKORR, " | |||
| lv_iv_leave_engine | TYPE CHAR1. " 'X' |
|   CALL FUNCTION 'ECOP_UTILS_ORGOBJECTS_ENGINE' "NOTRANSL: Generische Benhandlung von Orgobjekten |
| EXPORTING | ||
| IV_BUSINESS_OBJECT | = lv_iv_business_object | |
| IV_ACTION | = lv_iv_action | |
| IV_SOURCE_ENTITY | = lv_iv_source_entity | |
| IV_TARGET_ENTITY | = lv_iv_target_entity | |
| IV_DIALOGUE | = lv_iv_dialogue | |
| IV_TR_ORDER | = lv_iv_tr_order | |
| IV_TR_TASK | = lv_iv_tr_task | |
| IV_LEAVE_ENGINE | = lv_iv_leave_engine | |
| IMPORTING | ||
| RET_CODE | = lv_ret_code | |
| EV_TARGET_ENTITY | = lv_ev_target_entity | |
| EV_TR_ORDER | = lv_ev_tr_order | |
| EV_TR_TASK | = lv_ev_tr_task | |
| . " ECOP_UTILS_ORGOBJECTS_ENGINE | ||
ABAP code using 7.40 inline data declarations to call FM ECOP_UTILS_ORGOBJECTS_ENGINE
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 SUBRC FROM SY INTO @DATA(ld_ret_code). | ||||
| DATA(ld_iv_action) | = 'COPY'. | |||
| "SELECT single TRKORR FROM E070 INTO @DATA(ld_ev_tr_order). | ||||
| "SELECT single TRKORR FROM E070 INTO @DATA(ld_ev_tr_task). | ||||
| DATA(ld_iv_dialogue) | = 'X'. | |||
| "SELECT single TRKORR FROM E070 INTO @DATA(ld_iv_tr_order). | ||||
| "SELECT single TRKORR FROM E070 INTO @DATA(ld_iv_tr_task). | ||||
| DATA(ld_iv_leave_engine) | = 'X'. | |||
Search for further information about these or an SAP related objects