SAP PRGN_APPEND_TRANSPORT_ENTRY Function Module for









PRGN_APPEND_TRANSPORT_ENTRY is a standard prgn append transport entry 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 prgn append transport entry FM, simply by entering the name PRGN_APPEND_TRANSPORT_ENTRY into the relevant SAP transaction such as SE37 or SE38.

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



Function PRGN_APPEND_TRANSPORT_ENTRY 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 'PRGN_APPEND_TRANSPORT_ENTRY'"
EXPORTING
TASK = "
PGMID = "
OBJECT = "
OBJ_NAME = "
* TABKEY = "

EXCEPTIONS
TRANSPORT_PROBLEM = 1
.



IMPORTING Parameters details for PRGN_APPEND_TRANSPORT_ENTRY

TASK -

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

PGMID -

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

OBJECT -

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

OBJ_NAME -

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

TABKEY -

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

EXCEPTIONS details

TRANSPORT_PROBLEM -

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

Copy and paste ABAP code example for PRGN_APPEND_TRANSPORT_ENTRY 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_task  TYPE E071-TRKORR, "   
lv_transport_problem  TYPE E071, "   
lv_pgmid  TYPE E071-PGMID, "   
lv_object  TYPE E071-OBJECT, "   
lv_obj_name  TYPE E071-OBJ_NAME, "   
lv_tabkey  TYPE E071K-TABKEY. "   

  CALL FUNCTION 'PRGN_APPEND_TRANSPORT_ENTRY'  "
    EXPORTING
         TASK = lv_task
         PGMID = lv_pgmid
         OBJECT = lv_object
         OBJ_NAME = lv_obj_name
         TABKEY = lv_tabkey
    EXCEPTIONS
        TRANSPORT_PROBLEM = 1
. " PRGN_APPEND_TRANSPORT_ENTRY




ABAP code using 7.40 inline data declarations to call FM PRGN_APPEND_TRANSPORT_ENTRY

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 E071 INTO @DATA(ld_task).
 
 
"SELECT single PGMID FROM E071 INTO @DATA(ld_pgmid).
 
"SELECT single OBJECT FROM E071 INTO @DATA(ld_object).
 
"SELECT single OBJ_NAME FROM E071 INTO @DATA(ld_obj_name).
 
"SELECT single TABKEY FROM E071K INTO @DATA(ld_tabkey).
 


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!