Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-GBT-ALM (Application Component) Alert Framework⤷
SALERT_CORE (Package) Central Alert Server
Basic Data
| Data Element | SALERTDRULETYPE |
| Short Description | ALM: Rule Type |
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 | 30 | Rule Category |
Documentation
Definition
The following rule types are supported:
Agent Determination: Responsibilities
You can use responsibilities to define the rule container with any table fields or object types.
On the Responsibilities tab page, you can then define as many responsibilities as you want, which you can then assign to processors.
For each responsibility, you can also define criteria for which it has to be valid.
For example, you can define an invoiced amount or customer name in the rule container. Each responsibility can then be valid for certain customers or invoiced amounts; for example, one responsibility for invoiced amounts above a certain limit, and another for all other invoices.
When defining responsibilities, you do not have to define every single criteria. Empty fields are simply ignored during the rule resolution.
Agent Determination: Organizational Data
If you select this option, the rule resolution is performed using the business object types that are linked in the organization model.
For example, you can link organizational units to the object type Country. A value for country then has to be transferred in the rule container at runtime.
The rule resolution then returns all organizational units that have been assigned to this country.
Agent Determination: Function Being Executed
You can use a function module to perform as many rule resolutions as you want. Some function modules are delivered by SAP.
Agent Determination: Organizational Model
You can use this rule type in connection with general attribute maintenance. An agent determination is conducted using data stored generically in the organizational model.
This rule type is currently used exclusively in CRM. Resolution occurs by way of a function module with interfaces analogous to function module RH_OM_ATTRIBUTE_ORGOBJ_FIND. In addition to the function module, the scenario for which this rule is to be used must also be specified.
The rule container is automatically generated from the attributes defined for the scenario.
WebFlow: URL Determination
You use this rule type to define the URL address that you want an XML document to be sent to.
WebFlow: XML Formatting
You use this rule type to define the structure of the XML document.
WebFlow: Authentification
You use this rule type to define the use and password used to log on to the target system. The user and password are included when the XML document is sent.
WebFlow: Sending
You can use this rule type to modify the send process for the XML document. You can do this, for example, if you want to implement the SAP Business Connector.
Additional Information
The WebFlow rules are used to define the sending of XML documents in a Web application for SAP WebFlow. For more information, refer to the WebFlow documentation. You can find this in SAP Library under SAP Business Workflow (BC- BMT - WFM) -> Reference Documentation -> SAP Business Workflow - Navigation -> Workflow Builder -> Maintaining a Web Activity.
History
| Last changed by/on | SAP | 20041219 |
| SAP Release Created in | 700 |
