SAP MAP_GOXTRANS_2_E071 Function Module for
MAP_GOXTRANS_2_E071 is a standard map goxtrans 2 e071 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 map goxtrans 2 e071 FM, simply by entering the name MAP_GOXTRANS_2_E071 into the relevant SAP transaction such as SE37 or SE38.
Function Group: GOX_OBJECTS_GENERATE
Program Name: SAPLGOX_OBJECTS_GENERATE
Main Program: SAPLGOX_OBJECTS_GENERATE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MAP_GOXTRANS_2_E071 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 'MAP_GOXTRANS_2_E071'".
EXPORTING
IT_TRANSPORT = "Table with Entries for Transport
TABLES
ET_KO200 = "Interface Structures for Objects in CTS
ET_E071K = "Change & Transport System: Key Entries of Requests/Tasks
IMPORTING Parameters details for MAP_GOXTRANS_2_E071
IT_TRANSPORT - Table with Entries for Transport
Data type: COMT_GOX_TRANS_OBJECTOptional: No
Call by Reference: Yes
TABLES Parameters details for MAP_GOXTRANS_2_E071
ET_KO200 - Interface Structures for Objects in CTS
Data type: KO200Optional: No
Call by Reference: Yes
ET_E071K - Change & Transport System: Key Entries of Requests/Tasks
Data type: E071KOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for MAP_GOXTRANS_2_E071 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_et_ko200 | TYPE STANDARD TABLE OF KO200, " | |||
| lv_it_transport | TYPE COMT_GOX_TRANS_OBJECT, " | |||
| lt_et_e071k | TYPE STANDARD TABLE OF E071K. " |
|   CALL FUNCTION 'MAP_GOXTRANS_2_E071' " |
| EXPORTING | ||
| IT_TRANSPORT | = lv_it_transport | |
| TABLES | ||
| ET_KO200 | = lt_et_ko200 | |
| ET_E071K | = lt_et_e071k | |
| . " MAP_GOXTRANS_2_E071 | ||
ABAP code using 7.40 inline data declarations to call FM MAP_GOXTRANS_2_E071
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