SAP ABAP Data Element MIN_STTRG (Minimum overall status of shipment needed)
Hierarchy
BBPCRM (Software Component) BBPCRM
   CRM-BF (Application Component) Basic Functions
     VTR (Package) SD R/3 transport processing
Basic Data
Data Element MIN_STTRG
Short Description Minimum overall status of shipment needed  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type STTRG    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Min.status 
Medium 15 Min. status 
Long 20 Min. status 
Heading
Documentation

Definition

Overall status of the shipment. Minimum level of processing that must be reached before the document can be archived.

The archiving program checks several criteria for each shipment. A shipment can be archived if the following conditions are met:

  • The creation date of the shipment must be at least N days in the past. The residence time of the shipment since creation must therefore equal N days. Set N in archiving control for transportation (column: "Creation").
    Technical: Field VTTK-ERDAT is checked.
  • The last change date fo the shipment must be at least M days in the past. The residence time of the shipment since the last change must therefore equal M days. Set M in archiving control for transportation (column: "Change"). If the shipment has not yet been changed, then the creation date is taken as the last change date.
    Technical: Field VTTK-AEDAT is checked.
  • The overall status of the shipment must be at least X. You set X in archiving control for transportation (column: "Minimum overall status").Technical: Field VTTK-STTRG is checked.
  • All deliveries in the shipment must have transportation planning status 'C' (fully planned).
    Technical: Field VBUK-TRSTA is checked.
  • All deliveries in the shipment must have goods movement status ' ' (not relevant) or 'C' (fully processed ).
    Technical: Field VBUK-WBSTK is checked.
  • The shipment must have the overall shipment costs calculation status
    ' ' (not relevant) or 'C' (completely processed).
    Technical: Field VTTK-FBGST is checked.
  • If the overall shipment costs calculation status of the shipment is 'C' (completely processed), the relevant shipment cost document must already have been archived. This means that is must no longer exist in the system. (During archiving, the document flow must be processed starting with the last document in the list.)
    Technical: The system reads the document flow of the shipment (table VTFA) and checks in table VFKK whether the shipment cost document still exists.
  • All shipments that are included in a transportation chain with the shipment currently being processed must also be fully relevant for archiving. This means, these shipments must also meet preconditions 1-5 and fall within the shipment number range you specified when you started archiving.

The last five criteria are always checked in the program and cannot be altered. The first three criteria, however, can be set in Customizing (archiving control for transportation).

In order to make the archiving control settings in Customizing, choose:
Logistics Execution
--> Archiving
--> Control of Archiving of Shipments
(transaction VORT).

When you create a shipment, you must specify a shipment type. Every shipment in the system has a shipment type. Also, every shipment has a unique transportation planning point assigned to it.

In archiving control for shipments, you can define precisely when a document can be archived for every combination of shipment type and transportation planning point (this means defining residence times after creation or changing and setting the overall status).

To make data entry easier, it is also possible to 'mask' the shipment type, transportation planning point or even both. This means that you can set the shipment type as ' ' (blank), for example.

Example:

The table for archiving control could be laid out as follows:

TrPlPt     ShType     Creation     Change     Min.OStat

0001     0001     100     20     3

0002     0005     180     90     5

    0001     30     30     7

    0002     60     60     3

0001         20     20     6

        270     270     7

For any given document, the following accesses are made to the table (the system stops after the first successful access)

  • First the system accesses the transportaion planning point and the shipment type specified in the document (e.g. with '0002' und '0005'). If an entry exists for this combination (which is the case in this example), then the valid control paramaters have already been determined for this document.
  • If the first access did not discover an entry (e.g. for combination '0009' '0001'), then and entry is searched for. This is carried out with the transportation planning point set at ' ' (blank, therefore masked) and the shipment type agreeing with the entry specified (in the exaple, the entry with key ' ' '0001' would be found)
  • If nothing was found in the previous step (e.g. for combination '0001' '0005'), then an entry is searched for with the correct transporatation planning point but the shipment type set to ' ' (blank)(this would result in the entry with key '0001' ' ' being found).
  • If nothing is found in this step, then both key fields are masked, or set to ' ' ' ' (both blank). When this entry is maintained, then a valid entry should always be found.
  • If even this entry is missing, then the program adopts the following values:
    • Creation = 365 (1 year),
    • Change = 365 (1 year)
    • Min. overall status = 7 (maximaler Status)

NOTE: Archiving runs quicker if the same values are valid for all documents. The easiest way of acheiving this is to maintain only one entry in the table. This entry should leave the shipment type and the transportation planning point as ' ' (blank).

History
Last changed by/on SAP  19970130 
SAP Release Created in