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_VRSAC |
| Short Description | Active Plan Version for a Planning Step |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | WISP_VRSIO | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table | TWISPC_VRSIO |
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 | Active PV |
| Medium | 15 | Active PVersion |
| Long | 20 | Active plan version |
| Heading | 3 | APV |
Documentation
Definition
Specific plan version within a planning step.
Normally, plan versions are used to execute target / actual data comparisons or Controlling in general for current business or the current season.
Use
Only one active plan version can be assigned to each planning step. You are, however, not forced to flag an active plan version.
The active plan version must have previously been defined as the plan version.
This means that neither automatic planning (with the exception of specific automatic planning activity 1 (see below)), nor planning step links can be used to generate planning data.
You can only generate planning data by releasing planning data from other plan versions of the same planning step and sending it to the active plan version.
The release can be executed either directly from plan version maintenance or as automatic planning with planning activity 1 (release data for the active plan version).
History
| Last changed by/on | SAP | 19990301 |
| SAP Release Created in |
