Hierarchy
BBPCRM (Software Component) BBPCRM⤷
PP-MP-DEM (Application Component) Demand Management⤷
MDPB (Package) Application development R/3 purchasing
Basic Data
| Data Element | VERSB |
| Short Description | Version number for independent requirements |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | VERSB | |
| Data Type | CHAR | Character String |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| Value Table | T459V |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | VES | |
| Default Component name | PIR_VERSION | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Version |
| Medium | 16 | Version |
| Long | 20 | Version |
| Heading | 2 | DV |
Documentation
Definition
Alphanumeric description of a demand program, also known as the (demand) version number.
Use
The version number is used for organizational purposes for the creation and further use of the demand program.
Versions can be set to active and inactive. Only active versions are included in the planning run.
Using the version compare function, you can compare various versions of a demand program with each other.
Example
With the version number various planned independent requirements can be indicated according to their origin. For example, whether the demand program results from SOP or from the material forecast.
You can also create versions for long-term planning.
Supplementary Documentation - VERSB 0001
Use
By entering one or more version numbers for a demand program, you can use the version management function.
The system uses the version number that you enter here as a default value for the items which are to be created.
Procedure
Examples
By using versions, you can distinguish, for example, between planned independent requirements which have different references (sales plan, production plan, and so on).
Dependencies
Supplementary Documentation - VERSB 0002
Use
By entering one or more version numbers for a demand program, you can use the version maintenance.
Procedure
Examples
Dependencies
Supplementary Documentation - VERSB 0003
Use
The version number you enter here is used for batch input, in case no version was entered per material.
Procedure
Examples
Dependencies
Supplementary Documentation - VERSB 0004
Use
The source version is the version from which a copy is to be made.
The target version is the version that is created as a result of the copy procedure.
Procedure
Examples
Dependencies
In long-term planning, the source version is the operative version that is used as the basis for the version of the long-term planning.
The version number for the long-term planning is defined in the field target version.
History
| Last changed by/on | SAP | 20040223 |
| SAP Release Created in |
