Hierarchy
⤷ PLM-RM (Application Component) Recipe Management
⤷ RMSFRMCST (Package) RMS-FRM: RMS Formula - Customizing
Basic Data
Data Element | FRMLE_NO_MOD_FLG |
Short Description | Change Not Permitted |
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 changes |
Medium | 20 | Change Not Permitted |
Long | 20 | Change Not Permitted |
Heading | 20 | Change Not Permitted |
Documentation
Definition
Specifies that changes to formula data are not permitted. The system response depends on whether the data records can be assigned a usage:
- Data records with usage (identifiers, value assignments):
Changes are not permitted if on at least one day of the validity period of the active usage that belongs to it, an entry for the scope of application exists that:
- Has a status with this indicator
- Has the same rating as the active usage
- Overlaps with the validity area of the active usage
- Data records without usage (for example, formula header, inputs and outputs)
Changes are not permitted if at least one entry for the scope of application exists on at least one day of the validity period of the formula header that has a status with this indicator.
Use
Dependencies
You can distinguish between data records with usage and without usage:
- Data records with usage (identifiers, value assignments):
See the Product Safety component documentation on the change not permitted indicator, section: Dependencies.
Note: In the Product Safety component the concept status entry is used, which refers exclusively to data records with usage. However, in the Recipe Management component, the concept scope of application is used, to which a status is assigned that can refer to data records with and without usage.
- Data records without usage (for example, formula header, inputs and outputs)
The individual data records of a formula each have their own change states whose validity periods may deviate from those of the scope of application, or overlap each other.
When you edit a data record on a key date, the system performs the status check for the entire validity period of the formula header change state in question. The data record cannot be changed if the formula has at least one entry on at least one day of the validity period for the scope of application whose status prohibits changes.
Example
History
Last changed by/on | SAP | 20031212 |
SAP Release Created in | 461 |