Hierarchy
⤷ BC-BMT-OM (Application Component) Organizational Management
⤷ SP0A (Package) HR-OM: General Attribute Maintenance in Org. Management
Basic Data
Data Element | OM_ATTRSCN |
Short Description | General Attribute Maintenance: Application Scenario |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | OM_ATTRSCN | |
Data Type | CHAR | Character String |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 8 | |
Value Table | T77OMATTSC |
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 | Scenario |
Medium | 15 | Scenario |
Long | 35 | Attribute Maintenance Scenario |
Heading | 0 |
Documentation
Definition
Possible application scenarios in which the organizational unit is valid.
Over the scenario you can control which attributes are available and which properties (for example inheritance logic) thay have. You can therefore use an organizational structure for different applications (for example Sales and Service).
Supplementary Documentation - OM_ATTRSCN0040
Use
When you define rules, you use the scenarios as follows:
- In the case of rules of the category Agent Determination: Organization Model, you must enter a scenario when you define the rule. As a result, the system can automatically generate the rule container from the field catalog of the scenario used.
You can either use the button on the Rule Definition title element, or you can use the button on the Container title element.
- In the case of the Agent Determination: Responsibilities rule category, fields in the field catalog can also be used for generating the rule container. These kinds of rule are used by Customer Relationship Management (CRM), for example, to determine agents. Use the button on the Container title element.
Select a scenario from the dialog box (in the case of standard rules of the Agent Determination: Organizational Model category, the scenario is fixed by the rule definition). When you choose Enter, the rule attributes from the scenario are written to the rule container.
Dependencies
Example
History
Last changed by/on | SAP | 20010130 |
SAP Release Created in |