Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-MAP (Application Component) Merchandise and Assortment Planning⤷
WIS_PLAN (Package) Retail: Planning
Basic Data
| Data Element | WISP_PLINT |
| Short Description | Planning Step Interface |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | WISP_PLINT | |
| Data Type | CHAR | Character String |
| Length | 20 | |
| Decimal Places | 0 | |
| Output Length | 20 | |
| Value Table | TWISPC_PLINT |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | WXP48 | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Interface |
| Medium | 15 | PlStepInterface |
| Long | 21 | Planning Interface |
| Heading | 21 | Planning Interface |
Documentation
Definition
Planning interfaces describe how to transfer or exchange planning data with applications outwith MAP. An interface is created for a planning step. Characteristics and key figure for the planning step can be assigned to the interface so that the data that is to be transferred can be defined. If planning data only exists on an aggregated planning level (for example, merchandise category), but data on a lower level is required (for example, material) before any data can be transferred, a suitably defined group break-down can be assigned to the interface.
It is also possible to define the plan version from which data is taken for the interface.
The plan version is entered or the Use active plan version key figure is set.
Depending on the interface category, additional settings can be made. The following interface categories are presently supported:
History
| Last changed by/on | SAP | 19991209 |
| SAP Release Created in |
