Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
OIG (Package) TD Transport and Distribution
Basic Data
| Data Element | OIG_N_SLC |
| Short Description | TD Fixed in-transit store locations per shipment |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | OIG_N_SLC | |
| 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 | Fix.StLoc. |
| Medium | 15 | Fixed StLoc. |
| Long | 20 | Fixed intr.st.loc |
| Heading | 3 | FSL |
Documentation
Definition
The flag is evaluted to set the intransit storage location with regard to the underlying documents of a TD bulk shipment:
blank:
Multiple intransit storage locations per material / plant are allowed.
In general the system uses the customised storage location. But in case of load relevant reservations or inbound deliveries the intransit storage location is set from the document. Thus one can have several intransit storage locations per material and plant.
'1':
The system allows different intransit storage locations but tries to use the sending storage location at loading.
This value has only influence if the customising of the shipment type (table TOIGS) in the field Bypass In-transit Storage Location allows to bypass the intransit storage location (additional flag in customising) otherwise the system behaves like for value blank.
At loading the system uses the loading storage location as the intransit storage location as far as possible. Thus the transfer movement between the loading and the intransit storage locations is avoided. E. g. the system does not use the sending storage location in case of rebrands or for loading relevant reservations (intransit storage location = receiving storage location of the reservation).
'X':
The intransit storage location is set from customising (table TOIGS1).
At scheduling there is a check whether the underlying document (storage location of inbound deliveries or receiving storage location of reservations) fits to the customising. If the storage locations are different the system sends an error message.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
