SAP ABAP Data Element RCP_TXT30 (System Status of a Recipe)
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷ PLM-RM-REC (Application Component) Recipe
⤷ RMSRCPMSC (Package) RMS-RCP: Miscellaneous
⤷ PLM-RM-REC (Application Component) Recipe
⤷ RMSRCPMSC (Package) RMS-RCP: Miscellaneous
Basic Data
Data Element | RCP_TXT30 |
Short Description | System Status of a Recipe |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | TEXT30 | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | SY_ST_DSCR | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Status |
Medium | 15 | System Status |
Long | 20 | System Status |
Heading | 30 | System Status |
Documentation
Definition
Key that describes the current processing status of the change state you selected. The status influences whether recipe data can be changed and which transactions are allowed (see Status Network for Recipes).
Use
Dependencies
Depending on your Customizing settings, note the following for the different recipe types:
- In addition to the system statuses, you can assign customer-defined user statuses from a status profile defined in Customizing to your recipes. The user statuses serve to visually reproduce enterprise-specific processes in the SAP system.
- When you change the status in the recipe, the system not only checks the status of the change state you changed but also the preceding or subsequent change states. It checks whether status changes that affect the changeability of recipe data are allowed (see the documentation for the Depend.Chge States indicator).
Example
History
Last changed by/on | SAP | 20031212 |
SAP Release Created in | 461 |