SAP ABAP Data Element TRAEND (Controlling for changes to externally planned shipments)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM-BF (Application Component) Basic Functions
⤷ VTR (Package) SD R/3 transport processing
⤷ CRM-BF (Application Component) Basic Functions
⤷ VTR (Package) SD R/3 transport processing
Basic Data
Data Element | TRAEND |
Short Description | Controlling for changes to externally planned shipments |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | TRAEND | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
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 | Change shp |
Medium | 16 | Change shipment |
Long | 20 | Change shipment |
Heading | 2 | CS |
Documentation
Definition
Controlling the options for changing externally planned shipments
Use
Only restricted changes should be allowed to shipments that have been planned in an external system in order to keep the two systems as consistent as possible.
In this case, the following shipment data are changed in the external system and not in the SAP system:
- Assigning the deliveries to a shipment
- Legs, routes, shipping type
- Service agent
If you allow changes in the SAP system, these changes are not transferred into the external system.
Procedure
You can use this indicator to control which data of an externally planned shipment should not be changed in the SAP System. These changes should be carried out in the transporation planning system. From this system, they are transferred into the SAP system.
Examples
Dependencies
History
Last changed by/on | SAP | 19970130 |
SAP Release Created in |