Hierarchy
⤷ BC-BMT-OM (Application Component) Organizational Management
⤷ SP00 (Package) Organization and Planning
Basic Data
Data Element | HRROLETYPE |
Short Description | Rule Category |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | HRROLETYPE | |
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 | Category |
Medium | 20 | Rule category |
Long | 30 | Rule category |
Heading | 3 | Cat |
Documentation
Definition
The following rule categories are supported:
Agent Determination: Responsibilities
If you use responsibilities, you can define the rule container using any table fields or object types.
The Responsibilities tab page enables you to define any number of responsibilities. You can then assign agents to them.
You can also define criteria for each responsibility. The responsibility is then valid for the criteria.
For example, you can define an invoiced amount or customer name in the rule container. Each responsibility is then valid for particular customers or invoiced amounts, such as one responsibility for invoiced amounts above a certain limit and another for all other invoiced amounts.
When you define responsibilities, you do not necessarily have to define all criteria. Empty fields are ignored by rule resolution.
Agent Determination: Organizational Data
If you select this option, rule resolution is executed using business object types related in the organizational model.
For example, you can relate organizational units to the country object type. A value for the country must then be written to the rule container at runtime.
Rule resolution then returns all of the organizational units assigned to this country.
Agent Determination: Function to be Executed
You can execute any rule resolutions using a function module. Some function modules are supplied by SAP.
Agent Determination: Organization Model
This rule category can be used together with general attribute maintenance. Agents are determined using data stored generically in the organizational model.
Currently, this rule category is only used in CRM. Resolution is effected using function modules with interfaces like function module RH_OM_ATTRIBUTE_ORGOBJ_FIND
. As well as specifying the function module, you must specify the scenario for which this rule must be used.
The rule container is generated automatically using the attributes defined for the scenario.
WebFlow: URL Determination
With this rule category you define the URL address to which you want to send an XML document.
WebFlow: XML Format
With this rule category you define the structure of the XML document.
WebFlow: Authentication
With this rule category you specify the user and the password that are used to log on to the target system. The system transfers the user and the password along with the XML document.
WebFlow: Sending
With this rule category you can modify the sending procedure for the XML document. This can be useful, for example, if you do not want to use SAP Business Connector.
Additional Notes
The WebFlow categories allow you to define the sending of XML documents in a Web application for SAP WebFlow. For further information, see the WebFlow documentation. The documentation is in the SAP Library under SAP Business Workflow (BC-BMT-WFM) -> Reference Documentation -> BC - SAP Business Workflow - Navigation -> Workflow Builder -> Maintenance of a Web Activity.
History
Last changed by/on | SAP | 20010130 |
SAP Release Created in |