Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ VTRA (Package) Shipment costs
Basic Data
Data Element | VF_TDLNR_FA |
Short Description | Carrier Number |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | LIFNR | |
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table | LFA1 |
Further Characteristics
Search Help: Name | F4_CARRIERS | |
Search Help: Parameters | LIFNR | |
Parameter ID | LIF | |
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Carrier |
Medium | 15 | Carrier |
Long | 20 | Carrier |
Heading | 12 | Carrier |
Documentation
Definition
Number that uniquely identifes the transportation service agent (vendor).
Use
At the shipment header level, you can specify the service agent either manually or indirecty through specification of a route.
At the shipment stage level, this service agent is then automatically copied to all shipment stages if the service agent in the shipment stage is empty or is the same as the old service agent of the shipment header.
This also applies for manual creation of stages, for copying stages from the route, or for leg determination.
Procedure
Enter the number of the transportaton service agent.
You can search for the number using a matchcode. To do this, press F4=Input help, and enter the selection specifications of the field.
If the status 'Planned' is set, the forwarding agent is copied from the respective deliveries as transportation service agent into the shipment header (and thus also into the shipment stages, see above) if the forwarding agent is identical in all the deliveries and the fowarding agent field is not already filled.
Examples
The forwarding agent in the shipment header can thus be filled in several ways (specifications in descending priority):
- Manual entry
- Indirect entry through specification of a route
- Copy from the deliveries (if unique and if the Customizing setting is configured accordingly)
- From the route that was copied from the deliveries into the shipment header.
Dependencies
History
Last changed by/on | SAP | 19991209 |
SAP Release Created in | 46C |