SAP RHNT_NOTE_TRANSPORT_EXPORT Function Module for INTERNAL: Transport Connection Export

Search SAP Function Modules

RHNT_NOTE_TRANSPORT_EXPORT is a standard rhnt note transport export SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Transport Connection Export 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 rhnt note transport export FM, simply by entering the name RHNT_NOTE_TRANSPORT_EXPORT into the relevant SAP transaction such as SE37 or SE38.

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

Function RHNT_NOTE_TRANSPORT_EXPORT 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 'RHNT_NOTE_TRANSPORT_EXPORT'"INTERNAL: Transport Connection Export
  EXPORTING
   INFOTYPE =  "Infotype for which note should be edited
   TRKORR =  "Number of Customizing request
   AS4POS =  "Item number in Customizing request
*  DIRECT_DB_CHANGE = 'X' "Direct database change (no buffering)
*  TRANSPORT_DIRECT = ' ' "X = Transport not via plan version:

TABLES
   TRANS_E071 =  "Table of transport entries
   TRANS_E071K =  "Table of transport entries

EXCEPTIONS
   INTERNAL_ERROR = 1    ILLEGAL_INFOTYPE = 2    NO_CORR_PARAMS = 3    COPY_FAILED = 4    COMMIT_FAILED = 5 

.

IMPORTING Parameters details for RHNT_NOTE_TRANSPORT_EXPORT

INFOTYPE - Infotype for which note should be edited

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

TRKORR - Number of Customizing request

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

AS4POS - Item number in Customizing request

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

DIRECT_DB_CHANGE - Direct database change (no buffering)

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

TRANSPORT_DIRECT - X = Transport not via plan version:

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

TABLES Parameters details for RHNT_NOTE_TRANSPORT_EXPORT

TRANS_E071 - Table of transport entries

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

TRANS_E071K - Table of transport entries

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

EXCEPTIONS details

INTERNAL_ERROR - System error

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

ILLEGAL_INFOTYPE - Note is not allowed for this infotype

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

NO_CORR_PARAMS - TRKORR or AS4POS is empty

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

COPY_FAILED - Error when saving note

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

COMMIT_FAILED - Database-Commit failed

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

Copy and paste ABAP code example for RHNT_NOTE_TRANSPORT_EXPORT 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.

ABAP code using 7.40 inline data declarations to call FM RHNT_NOTE_TRANSPORT_EXPORT

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