SAP ECOP_TRANSPORT_ORGUNIT_DATA Function Module for NOTRANSL: Tranportiert die Daten einer oder mehrerer Orgeinheiten (ohne Nu
ECOP_TRANSPORT_ORGUNIT_DATA is a standard ecop transport orgunit data 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: Tranportiert die Daten einer oder mehrerer Orgeinheiten (ohne Nu 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 transport orgunit data FM, simply by entering the name ECOP_TRANSPORT_ORGUNIT_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: ECOP
Program Name: SAPLECOP
Main Program: SAPLECOP
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ECOP_TRANSPORT_ORGUNIT_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 'ECOP_TRANSPORT_ORGUNIT_DATA'"NOTRANSL: Tranportiert die Daten einer oder mehrerer Orgeinheiten (ohne Nu.
EXPORTING
DARK_TRANSPORT = "Background transport
WE_ORDER = "Transport Request
WE_TASK = "Transport Task
ORGUNIT_NAME = "
WE_OBJ_APP = "
KEY_FROM = "
* KEY_TO = "
ACTION = "Action
* USE_APPL_DATA = ' ' "
IMPORTING
SELECTED_ORDER = "
SELECTED_TASK = "
TABLES
WT_KO200 = "Tranport table
WT_E071K = "Tranport table
EXCEPTIONS
CANCELLED = 1
IMPORTING Parameters details for ECOP_TRANSPORT_ORGUNIT_DATA
DARK_TRANSPORT - Background transport
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WE_ORDER - Transport Request
Data type: E070-TRKORROptional: No
Call by Reference: No ( called with pass by value option)
WE_TASK - Transport Task
Data type: E070-TRKORROptional: No
Call by Reference: No ( called with pass by value option)
ORGUNIT_NAME -
Data type: DD03P-DOMNAMEOptional: No
Call by Reference: No ( called with pass by value option)
WE_OBJ_APP -
Data type: TRPARI-S_CHECKEDOptional: No
Call by Reference: No ( called with pass by value option)
KEY_FROM -
Data type: SVAL-VALUEOptional: No
Call by Reference: No ( called with pass by value option)
KEY_TO -
Data type: SVAL-VALUEOptional: Yes
Call by Reference: No ( called with pass by value option)
ACTION - Action
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
USE_APPL_DATA -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ECOP_TRANSPORT_ORGUNIT_DATA
SELECTED_ORDER -
Data type: E070-TRKORROptional: No
Call by Reference: No ( called with pass by value option)
SELECTED_TASK -
Data type: E070-TRKORROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ECOP_TRANSPORT_ORGUNIT_DATA
WT_KO200 - Tranport table
Data type: KO200Optional: No
Call by Reference: No ( called with pass by value option)
WT_E071K - Tranport table
Data type: E071KOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CANCELLED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ECOP_TRANSPORT_ORGUNIT_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.| DATA: | ||||
| lt_wt_ko200 | TYPE STANDARD TABLE OF KO200, " | |||
| lv_cancelled | TYPE KO200, " | |||
| lv_dark_transport | TYPE KO200, " | |||
| lv_selected_order | TYPE E070-TRKORR, " | |||
| lv_we_order | TYPE E070-TRKORR, " | |||
| lt_wt_e071k | TYPE STANDARD TABLE OF E071K, " | |||
| lv_selected_task | TYPE E070-TRKORR, " | |||
| lv_we_task | TYPE E070-TRKORR, " | |||
| lv_orgunit_name | TYPE DD03P-DOMNAME, " | |||
| lv_we_obj_app | TYPE TRPARI-S_CHECKED, " | |||
| lv_key_from | TYPE SVAL-VALUE, " | |||
| lv_key_to | TYPE SVAL-VALUE, " | |||
| lv_action | TYPE SVAL, " | |||
| lv_use_appl_data | TYPE SVAL. " SPACE |
|   CALL FUNCTION 'ECOP_TRANSPORT_ORGUNIT_DATA' "NOTRANSL: Tranportiert die Daten einer oder mehrerer Orgeinheiten (ohne Nu |
| EXPORTING | ||
| DARK_TRANSPORT | = lv_dark_transport | |
| WE_ORDER | = lv_we_order | |
| WE_TASK | = lv_we_task | |
| ORGUNIT_NAME | = lv_orgunit_name | |
| WE_OBJ_APP | = lv_we_obj_app | |
| KEY_FROM | = lv_key_from | |
| KEY_TO | = lv_key_to | |
| ACTION | = lv_action | |
| USE_APPL_DATA | = lv_use_appl_data | |
| IMPORTING | ||
| SELECTED_ORDER | = lv_selected_order | |
| SELECTED_TASK | = lv_selected_task | |
| TABLES | ||
| WT_KO200 | = lt_wt_ko200 | |
| WT_E071K | = lt_wt_e071k | |
| EXCEPTIONS | ||
| CANCELLED = 1 | ||
| . " ECOP_TRANSPORT_ORGUNIT_DATA | ||
ABAP code using 7.40 inline data declarations to call FM ECOP_TRANSPORT_ORGUNIT_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.| "SELECT single TRKORR FROM E070 INTO @DATA(ld_selected_order). | ||||
| "SELECT single TRKORR FROM E070 INTO @DATA(ld_we_order). | ||||
| "SELECT single TRKORR FROM E070 INTO @DATA(ld_selected_task). | ||||
| "SELECT single TRKORR FROM E070 INTO @DATA(ld_we_task). | ||||
| "SELECT single DOMNAME FROM DD03P INTO @DATA(ld_orgunit_name). | ||||
| "SELECT single S_CHECKED FROM TRPARI INTO @DATA(ld_we_obj_app). | ||||
| "SELECT single VALUE FROM SVAL INTO @DATA(ld_key_from). | ||||
| "SELECT single VALUE FROM SVAL INTO @DATA(ld_key_to). | ||||
| DATA(ld_use_appl_data) | = ' '. | |||
Search for further information about these or an SAP related objects