SAP ASH_RL_TB_READ Function Module for NOTRANSL: Datenbeschaffung WM Transportbedarfe
ASH_RL_TB_READ is a standard ash rl tb read 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: Datenbeschaffung WM Transportbedarfe 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 ash rl tb read FM, simply by entering the name ASH_RL_TB_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: ASH6
Program Name: SAPLASH6
Main Program: SAPLASH6
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ASH_RL_TB_READ 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 'ASH_RL_TB_READ'"NOTRANSL: Datenbeschaffung WM Transportbedarfe.
EXPORTING
* I_ARCHIVEKEY = "Key for Archive File
* I_OFFSET = "Offset of data object in archive file
* I_BORIDENT = "Object Relationship Service: BOR Object Identifier
TABLES
* ET_LTBK = "Transfer requirement header
* ET_LTBP = "Transfer Requirement Item
EXCEPTIONS
NOT_IN_INFOSTRUCTURE = 1 NOT_IN_ARCHIVE = 2 NO_INSTRUCTURE_DEFINED = 3
IMPORTING Parameters details for ASH_RL_TB_READ
I_ARCHIVEKEY - Key for Archive File
Data type: ADMI_FILES-ARCHIV_KEYOptional: Yes
Call by Reference: Yes
I_OFFSET - Offset of data object in archive file
Data type: ARCH_IDX-OFFSETOptional: Yes
Call by Reference: Yes
I_BORIDENT - Object Relationship Service: BOR Object Identifier
Data type: BORIDENTOptional: Yes
Call by Reference: Yes
TABLES Parameters details for ASH_RL_TB_READ
ET_LTBK - Transfer requirement header
Data type: LTBKOptional: Yes
Call by Reference: Yes
ET_LTBP - Transfer Requirement Item
Data type: LTBPOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NOT_IN_INFOSTRUCTURE - Does not exist in the info structure
Data type:Optional: No
Call by Reference: Yes
NOT_IN_ARCHIVE - Does not exist in the archive
Data type:Optional: No
Call by Reference: Yes
NO_INSTRUCTURE_DEFINED - No infostructure defined for the deliveries
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ASH_RL_TB_READ 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_ltbk | TYPE STANDARD TABLE OF LTBK, " | |||
| lv_i_archivekey | TYPE ADMI_FILES-ARCHIV_KEY, " | |||
| lv_not_in_infostructure | TYPE ADMI_FILES, " | |||
| lt_et_ltbp | TYPE STANDARD TABLE OF LTBP, " | |||
| lv_i_offset | TYPE ARCH_IDX-OFFSET, " | |||
| lv_not_in_archive | TYPE ARCH_IDX, " | |||
| lv_i_borident | TYPE BORIDENT, " | |||
| lv_no_instructure_defined | TYPE BORIDENT. " |
|   CALL FUNCTION 'ASH_RL_TB_READ' "NOTRANSL: Datenbeschaffung WM Transportbedarfe |
| EXPORTING | ||
| I_ARCHIVEKEY | = lv_i_archivekey | |
| I_OFFSET | = lv_i_offset | |
| I_BORIDENT | = lv_i_borident | |
| TABLES | ||
| ET_LTBK | = lt_et_ltbk | |
| ET_LTBP | = lt_et_ltbp | |
| EXCEPTIONS | ||
| NOT_IN_INFOSTRUCTURE = 1 | ||
| NOT_IN_ARCHIVE = 2 | ||
| NO_INSTRUCTURE_DEFINED = 3 | ||
| . " ASH_RL_TB_READ | ||
ABAP code using 7.40 inline data declarations to call FM ASH_RL_TB_READ
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 ARCHIV_KEY FROM ADMI_FILES INTO @DATA(ld_i_archivekey). | ||||
| "SELECT single OFFSET FROM ARCH_IDX INTO @DATA(ld_i_offset). | ||||
Search for further information about these or an SAP related objects