SAP ABAP Data Element RLMFW_CHGIND (Change Process)
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷ PLM-PPM (Application Component) Product and Process Modeling
⤷ RLMFW (Package) Release Management for Engineering Processes
⤷ PLM-PPM (Application Component) Product and Process Modeling
⤷ RLMFW (Package) Release Management for Engineering Processes
Basic Data
Data Element | RLMFW_CHGIND |
Short Description | Change Process |
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 | Change |
Medium | 15 | Change |
Long | 20 | Change Process |
Heading | 16 | Change Process |
Documentation
Definition
Ensures that the previous release is still considered to be active until the next release is carried out for a release object that was reset. If you have defined protected fields for the release target, then these are no longer protected against changes when this reset is released.
Use
If you want to change release objects as release-relevant, you must reset the release. Depending on the application, it may be useful to consider the valid release status as required until the object is released again. The system then marks the reset as successful in the release history of the release object. When the release orders are evaluated, it is possible to reconstruct the release status as long as all required data are stored in the release order.
Dependencies
Example
History
Last changed by/on | SAP | 20050409 |
SAP Release Created in | 600 |