SAP ASH_SD_VTTK_READ Function Module for NOTRANSL: Datenbeschaffung Transporte









ASH_SD_VTTK_READ is a standard ash sd vttk 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 Transporte 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 sd vttk read FM, simply by entering the name ASH_SD_VTTK_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_SD_VTTK_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_SD_VTTK_READ'"NOTRANSL: Datenbeschaffung Transporte
  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_VTTK =  "Shipment Header
*  ET_VTTP =  "Shipment item
*  ET_VTTS =  "Stage of Shipment
*  ET_VTSP =  "Stage of Transport / Item Allocation
*  ET_VTPA =  "Shipping Partner
*  ET_VTFA =  "Shipment Document Flow
*  ET_NAST =  "Message status
*  ET_ADDR1_VAL =  "Address Return Structure
*  ET_SADR =  "Address Management: Company data

EXCEPTIONS
   NOT_IN_INFOSTRUCTURE = 1    NOT_IN_ARCHIVE = 2    NO_INSTRUCTURE_DEFINED = 3
.



IMPORTING Parameters details for ASH_SD_VTTK_READ

I_ARCHIVEKEY - Key for Archive File

Data type: ADMI_FILES-ARCHIV_KEY
Optional: Yes
Call by Reference: Yes

I_OFFSET - Offset of data object in archive file

Data type: ARCH_IDX-OFFSET
Optional: Yes
Call by Reference: Yes

I_BORIDENT - Object Relationship Service: BOR Object Identifier

Data type: BORIDENT
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for ASH_SD_VTTK_READ

ET_VTTK - Shipment Header

Data type: VTTK
Optional: Yes
Call by Reference: Yes

ET_VTTP - Shipment item

Data type: VTTP
Optional: Yes
Call by Reference: Yes

ET_VTTS - Stage of Shipment

Data type: VTTS
Optional: Yes
Call by Reference: Yes

ET_VTSP - Stage of Transport / Item Allocation

Data type: VTSP
Optional: Yes
Call by Reference: Yes

ET_VTPA - Shipping Partner

Data type: VTPA
Optional: Yes
Call by Reference: Yes

ET_VTFA - Shipment Document Flow

Data type: VTFA
Optional: Yes
Call by Reference: Yes

ET_NAST - Message status

Data type: NAST
Optional: Yes
Call by Reference: Yes

ET_ADDR1_VAL - Address Return Structure

Data type: ADDR1_VAL
Optional: Yes
Call by Reference: Yes

ET_SADR - Address Management: Company data

Data type: SADR
Optional: 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_SD_VTTK_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_vttk  TYPE STANDARD TABLE OF VTTK, "   
lv_i_archivekey  TYPE ADMI_FILES-ARCHIV_KEY, "   
lv_not_in_infostructure  TYPE ADMI_FILES, "   
lt_et_vttp  TYPE STANDARD TABLE OF VTTP, "   
lv_i_offset  TYPE ARCH_IDX-OFFSET, "   
lv_not_in_archive  TYPE ARCH_IDX, "   
lt_et_vtts  TYPE STANDARD TABLE OF VTTS, "   
lv_i_borident  TYPE BORIDENT, "   
lv_no_instructure_defined  TYPE BORIDENT, "   
lt_et_vtsp  TYPE STANDARD TABLE OF VTSP, "   
lt_et_vtpa  TYPE STANDARD TABLE OF VTPA, "   
lt_et_vtfa  TYPE STANDARD TABLE OF VTFA, "   
lt_et_nast  TYPE STANDARD TABLE OF NAST, "   
lt_et_addr1_val  TYPE STANDARD TABLE OF ADDR1_VAL, "   
lt_et_sadr  TYPE STANDARD TABLE OF SADR. "   

  CALL FUNCTION 'ASH_SD_VTTK_READ'  "NOTRANSL: Datenbeschaffung Transporte
    EXPORTING
         I_ARCHIVEKEY = lv_i_archivekey
         I_OFFSET = lv_i_offset
         I_BORIDENT = lv_i_borident
    TABLES
         ET_VTTK = lt_et_vttk
         ET_VTTP = lt_et_vttp
         ET_VTTS = lt_et_vtts
         ET_VTSP = lt_et_vtsp
         ET_VTPA = lt_et_vtpa
         ET_VTFA = lt_et_vtfa
         ET_NAST = lt_et_nast
         ET_ADDR1_VAL = lt_et_addr1_val
         ET_SADR = lt_et_sadr
    EXCEPTIONS
        NOT_IN_INFOSTRUCTURE = 1
        NOT_IN_ARCHIVE = 2
        NO_INSTRUCTURE_DEFINED = 3
. " ASH_SD_VTTK_READ




ABAP code using 7.40 inline data declarations to call FM ASH_SD_VTTK_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



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!