VOFM output control routine for VT01N

Question

I need to know what the temporary strucutre or internal table is that SAP uses for deliveries.  The values eventually get stroed in table VTTP.  But when using VT01N they are not there of course until it is actually saved to the DB.  The output control routine that was created gets invoked or called before it is saved so I have to read from the temp or internal table SAP uses to load these values for the deliveries.  Does anyone know what this table might be?  I am allowing or preventing output based on some detail concerning the delieveries but none of it is stored until it is saved so I need this temp table to get to the values.

Answer 1

Look in INCLUDE VTTPDATA.
This is where the internal tables are defined for VT01N.
*   INCLUDE VTTPDATA                                                   *
TABLES:  VTTP,   *VTTP,
         VTTPD,  *VTTPD,
         VTTPVB, *VTTPVB.
DATA:    BEGIN OF COMMON PART VTTPCOM.
*   shipment items
* Data base contents
DATA:    BEGIN OF DBVTTP OCCURS 0.
           INCLUDE STRUCTURE VTTP.
DATA:    END OF DBVTTP.
* New table contents
DATA:    BEGIN OF XVTTP OCCURS 0.         "Sortiert nach:
           INCLUDE STRUCTURE VTTPVB.      " MANDT TKNUM TPNUM VBELN
DATA:    END OF XVTTP.
* Old table contents
DATA:    BEGIN OF YVTTP OCCURS 0.         "Sortiert nach:
           INCLUDE STRUCTURE VTTPVB.      " MANDT TKNUM TPNUM
DATA:    END OF YVTTP.
* Temporary table contents
DATA:    BEGIN OF LVTTP OCCURS 0.
           INCLUDE STRUCTURE VTTPVB.
DATA:    END OF LVTTP.
* Definition of keys
DATA:    BEGIN OF VTTP_KEY,
           MANDT LIKE VTTP-MANDT,
           TKNUM LIKE VTTP-TKNUM,
           TPNUM LIKE VTTP-TPNUM,
         END   OF VTTP_KEY.
* Internal table for screen processing
DATA:    BEGIN OF IVTTP OCCURS 0,        "Sortierkriterium wechselt !
           TKNUM LIKE VTTP-TKNUM,
           TPRFO LIKE VTTP-TPRFO,
           TPNUM LIKE VTTP-TPNUM,
           VBELN LIKE VTTP-VBELN,
           VSTEL LIKE VTRLK-VSTEL,
           WERKS LIKE VTTPVB-WERKS,
           LAND1 LIKE VTRLK-LAND1,
           PSTLZ LIKE VTRLK-PSTLZ,
           KUNNR LIKE VTRLK-KUNNR,
           LIFNR LIKE VTTPVB-LIFNR,
           CONADDR LIKE V56IDLNT-CONADDR,
           TABIX LIKE SY-TABIX,
           XTRLK LIKE SY-TABIX,
           BTGWC LIKE VTRLK-BTGEW,
           GSGWC LIKE VTRLK-BRGEW,
           VOLMC LIKE VTRLK-VOLUM,
*        fields below will be updated during tree processing
           BTGWD LIKE V56IQUA-BTGWD,
           GSGWD LIKE V56IQUA-GSGWD,
           VOLMD LIKE V56IQUA-VOLMD,
           DTMEG LIKE TVTK-DTMEG,
           DTMEV LIKE TVTK-DTMEV,
           TKNEW LIKE VTTP-TKNUM,
           SELKZ LIKE RV56A-SELTSTP,
         END   OF IVTTP.
*   deliveries in process
DATA: BEGIN OF XTRLK OCCURS 0.         "delivery headers
        INCLUDE STRUCTURE VTRLK.       "Sortiert nach MANDT VBELN
DATA: END OF XTRLK.
DATA: BEGIN OF XTRLP OCCURS 0.         "delivery items
        INCLUDE STRUCTURE VTRLP.       "Sortiert nach VBELN POSNR
DATA: END OF XTRLP.
DATA:    END OF COMMON PART.
If you put a breakpoint in you VOFM routine, you should be able to examine which of these has the data that you need.
If you need more info, such as header data etc
Look at these others:
*        Internal tables for shipment data base
SET EXTENDED CHECK OFF.
INCLUDE vttkdata.                      "shipment header
INCLUDE vttpdata.                      "shipment item
INCLUDE vttsdata.                      "shipment segment
INCLUDE vbpadata.                      "partner
INCLUDE vtfadata.                      "flow
INCLUDE sadrdata.                      "address
This is from the top include MV56ATOP for the program run by VT01N, SAPMV56A.
You can access all of this through SE84, Information System.
Good luck
Brian