Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BF (Application Component) Basic Functions⤷
VTR (Package) SD R/3 transport processing
Basic Data
| Data Element | TRSTA |
| Short Description | Transportation planning status |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TRSTA | |
| 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 | TrnsPlnSta |
| Medium | 15 | Trns.plan.stat. |
| Long | 20 | Trns.plan.status |
| Heading | 2 | TS |
Documentation
Definition
Indicates the extent to which transportation planning has been performed.
Use
This characteristic controls the selection of deliveries to make up shipments in transportation planning. It is used a selection criterion for finding deliveries.
The indicator is set by the system on the basis of the leg indicator (preliminary, subsequent, direct, return) in the headers of the shipment documents to which the delivery has been assigned.
- Blank - Not relevant
Delivery is not to be processed in transportation
planning. This is the case when:
- the delivery type is not relevant for transportation, or
- the route is not relevant for transportation (only for
outbound deliveries; not required for
inbound deliveries), or
- a shipment block has been set in the delivery (only for
outbound deliveries: not required for inbound deliveries)
A - Not yet planned
Delivery is to be processed in transportation planning.
It has not yet been assigned to a shipment document.
B - Partially planned
Delivery is to be processed in transportation
planning. The delivery has already been
assigned to at least one shipment document but the
transportation chain is not complete (see status C).
C - Completely planned
Delivery has been assigned to one or more
shipment documents in transportation planning. Depending
on the leg indicator in each shipment header, the delivery is
considered to be completely planned if
- it exists in a direct leg or a return leg or
- it exists in a preliminary, main, subsequent leg or
- each stage assigned to the delivery connects to a
subsequent stage, thus connecting the point
of departure with the destination of the delivery with
no gaps in transportation (as of Release 4.6A).
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 19991102 |
| SAP Release Created in |
