Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions⤷
VZ (Package) Application development R/3 RV central functions
Basic Data
| Data Element | S3LIKP_NO_TRANSPORT_PLANNING |
| Short Description | Indicator: Do Not Check Transportation Planning |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | No TrnsPlg |
| Medium | 15 | No Trans. Plng |
| Long | 20 | No Check Trns.Plng |
| Heading | 40 | Do Not Check Transportation Planning |
Documentation
Definition
This indicator controls whether the system should ignore the transportation planning status when checking the delivery for archivability.
Use
As standard, a delivery cannot be archived if it is relevant for transportation planning and has not been assigned to a transport. If your business process supports that deliveries are not included in a transport document, even a long time after they have been completed, it makes sense to use this indicator.
Set this indicator if you do not want the system to check the transportation planning status when checking for archivability. Any deliveries relevant for transportation planning can be archived if there are no reasons for not doing so.
Dependencies
Separately from this indicator, a delivery can only be archived once an assigned transportation document (if one exists) has already been archived.
When you use this indicator, choose a suitably long residence time, in order to ensure that no deliveries are accidentally archived that might be required for planning transports.
Example
History
| Last changed by/on | SAP | 20030327 |
| SAP Release Created in | 470 |
