Hierarchy
⤷ AP-RC-BOF-CFN (Application Component) Business Object Processing Framework Configuration
⤷ /BOBF/CONFIGURATION (Package) Business Object Processing Configuration
Basic Data
Data Element | /BOBF/ACT_CONF_KEY |
Short Description | Action Configuration |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | /BOBF/CONF_KEY | |
Data Type | RAW | Uninterpreted sequence of bytes |
Length | 16 | |
Decimal Places | 0 | |
Output Length | 32 | |
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 | 0 | |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
The action configuration defines which actions are valid (enabled) for a node category.
Use
If more than one node category exists the action configuration can be used to enable and disable actions for different node categories.
If a disabled action is called for an instance the business object processing framework will not allow the execution of this action for this instance.
Dependencies
If the business object refers to a proxy business object the model information of action configuration is used to set the properties of this action per node instance depending on the node category of this instance.
Example
An object has versions where the version could be 'active' and 'inactive'. An action ACTIVATE is defined to activate an inactive version.
It should be prevented that the action 'activate' is called for an active version as this clearly makes no sense (in this particular example).
Solution (with two node categories):
- Define for the root node two node categories ACTIVE and INACTIVE
- Enable the action ACTIVATE only for the node category INACTIVE
- The action ACTIVATE will be disabled for instances with node category ACTIVE. If the action ACTIVATE is called nevertheless for an 'active' version the action will not be executed
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 702 |