Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-MD-PRO (Application Component) Products⤷
CS (Package) R/3 Application development: PP Bills of Material
Basic Data
| Data Element | CS_HISNA |
| Short Description | Indicator: History requirement new variant / alternative |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CS_HISNA | |
| 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 | HiReqVar |
| Medium | 15 | HistReq.Variant |
| Long | 20 | Hist. reqmt. variant |
| Heading | 5 | HReqV |
Documentation
Definition
Indicator specifying that a history is required when a bill of material of a BOM group is created.
If you enter a value for history requirement, each new alternative or variant must be created with reference to a change number.
Procedure
History requirement for the following values:
- Blank
History required if at least one alternative or variant has been created or changed with reference to an order number
- Value 1
History required if a BOM status with history requirement has been specified for at least one alternative or variant
(See IMG activity Configure history requirement)This does not require that a BOM of the BOM group has been processed with reference to a change number.
No history requirement
- Value 2
Irrespective of existing alternatives or variants, you can always create new BOMs without reference to a change number.
Examples
Dependencies
The setting is irrelevant if the History reqmt indicator has been set.
History
| Last changed by/on | SAP | 19970708 |
| SAP Release Created in |
