SAP ABAP IMG Activity SIMG_TD_TAS_0004 (Define TAS relevance for pickup and shipment)
Hierarchy
☛ IS-OIL (Software Component) IS-OIL
   ⤷ IS-OIL-DS-TAS (Application Component) Interface to Terminal Automation System
     ⤷ OIK_I (Package) TAS (Terminal Automation System)
IMG Activity
ID SIMG_TD_TAS_0004 Define TAS relevance for pickup and shipment  
Transaction Code S_SO5_65000262   IMG activity: SIMG_TD_TAS_0004 
Created on 19990913    
Customizing Attributes SIMG_TD_TAS_0004   Define TAS relevance for pickup and shipment 
Customizing Activity SIMG_TD_TAS_0004   Define TAS relevance for pickup and shipment 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_TD_TAS_0004    

Description

To set up TAS relevance for pickup and shipment, the following must be defined:

  • Hierarchy for pickup relevance
  • TAS relevance pickup
  • Hierarchy for shipment relevance
  • TAS relevance shipment

Hierarchy for Pickup Relevance

The hierarchy for pickup relevance determines the access sequence of TAS relevance fields based on data from the SD document to determine TAS relevance. Except for the field Document Type, the user can freely define the sequence of fields that are assigned to the control structure type. Through the hierarchy it is possible to control the relevance based on the values entered. The access sequence goes from the highest level in the hierarchy (1) to the lowest (10). The following are valid fields:

AUART - sales document type
VKORG - sales organization
VTWEG - distribution channel
SPART - division
VSTEL - shipping point
WERKS - plant
LGORT - storage location
MBRSH - industry sector
MTART - material type
MTKL - material group
MATNR - material
VSBED - shipping condition
OIC_MOT - mode of transport

If the Stay on Wildcard flag is set, values with an asterisk are not deleted during the determination of TAS relevance. Instead these values remain valid for the next hierarchy level.

Example

The following hierarchy is defined:

Material
Plant
Storage location

The following values are entered as relevant:

1. MAT1 GPO1 *
2. * * G1L1
3. * GP01 G1L1

The following values are taken from the document and document item:

MAT1
GP01
G1L1

The settings result in the following processing:

G1L1 -> fields 1, 2, and 3 remain
GP01 -> fields 1, 2, and 3 remain, while field 2 is active because it
is the best match
MAT1 -> field 1 remains, because the highest valid value in the
hierarchy was found

Without active settings the following processing occurs:

G1L1 -> fields 2 and 3 remain, because a value was found for G1L1 and
all asterisks are cleared
GP01 -> field 3 remains, because a value was found for GP01
MAT1 -> field 3 remains, because no value was found for MAT1 and the
asterisk setting is valid

TAS Relevance Pickup

Here the values for the fields defined in the hierarchy are designated as TAS relevant, and are assigned to a valid Load ID type.

An asterisk can be entered in the fields, which is treated by the system as valid for all fields. For an example of the access sequence, see the Example section.

Hierarchy for Shipment Relevance

The hierarchy for shipment relevance controls the access sequence for determining TAS relevance using the shipment data. Except for the field Shipment Type, it is possible to define the sequence for the fields assigned to the control structure type. By setting up a hierarchy, it is possible to control the relevance based on the defined values. The access sequence goes from the highest hierarchy level (1) to the lowest level (5). The most appropriate value within this access sequence determines the relevance and returns the Load ID type.

The following fields can be designated:

TPPOINT - transport planning point
VEH_TYPE - vehicle type
VEHICLE - vehicle number
CARRIER - carrier
SHIFT - driver shift

If the Stay on Wildcard flag is set, values with an asterisk are not deleted during the determination of TAS relevance. Instead these values remain valid for the next hierarchy level.

TAS Relevance Shipment

Here the values for the fields defined in the hierarchy are designated as TAS relevant, and are assigned to a valid Load ID type. An asterisk can be entered in the fields, which is treated by the system as valid for all fields. For an example of the access sequence, see the Example section.

Example

Requirements

Standard settings

Recommendation

Activities

Further notes

Business Attributes
ASAP Roadmap ID 201   Make global settings 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_TD_TAS_0004 0 I400022111 Interface to Terminal Automation System 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
VC_TOIKTRV C - View cluster SM34 OIK_000001 TAS Relevance Maintenance 
History
Last changed by/on SAP  20030617 
SAP Release Created in