Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
ICM (Application Component) Incentive and Commission Management (ICM)⤷
CRDPRV (Package) Credentialing: Private Objects (DDIC, etc.)
Basic Data
| Data Element | CRDREQATT |
| Short Description | Rule for Requirement Assignments |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CRDREQATTD | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table | TCRD_REQATT |
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 | AssignRule |
| Medium | 15 | Assignment Rule |
| Long | 20 | Req.Assignment Rule |
| Heading | 15 | Assignment Rule |
Documentation
Definition
Identification of the rule for a requirement assignment. It identifies an algorithm that is used to determine to whom the single requirements in a combined requirement or requirements lists is assigned.
Use
A requirements list or combined requirement consists of single requirements that have to be assigned to a member of the group who takes part in the business transaction, in the case of combined or simple requirements. This is done by specifying an algorithm that has to be implemented in the system and is identified by a rule. Rules for requirement assignments are often in the form of all participants or at least one participant and can be differentiated further by assignment parameters, such as a role (see examples).
Note:
Requirements are initially determined by means of the determination in the framework of the credentials check. The result is a list of requirements that is automatically grouped into a special requirements list, referred to as the root requirement . The assignment algorithm for this special requirements list is implemented by implementing BAdI CRD_ATTALG_FACTORY_FOR_ROOT of BAdI CRD_ATTALG_FACTORY.
Dependencies
Example
Participants typically take part in a business transaction or other type of transaction in specific roles. The assignment rule for the requirement depends on this.
- Example 1: A person in a car is (usually) either the driver or the passenger. Another relevant role here is the car owner whose presence need not necessarily be represented.
A (very simple) assignment rule for the requirement Must have valid driver's license could therefore be: The driver must fulfill the requirement. Short form: All participants in role of driver - Example 2: On the signing of an insurance contract, at least one participant usually needs to have a specific qualification (such as a license). It is feasible that all the participants in the role of sales agents additionally need a company-specific appointment. This scenario could be mapped using the following requirements (A1-A5):
- A1 is a single requirement that stipulates:
Business partner must have license (maybe industry-specific) - A2 is a single requirement that stipulates:
Business partner must have appointment - A3 is a combined requirement whose requirements list only contains A1, and its assignment rule states:
A1 is checked for all partners in group, combination algorithm: OR operation - A4 is a requirements list with only one requirement A2, and its assignment rule states:
Assign A2 to all partners with role of sales agent
(without combination algorithm) - A5 (root requirement) consists of requirements A3 and A4 (without combination algorithm), A3 is assigned to the group, A4 is the requirements list and is not assigned to any partner.
Note:
Requirement A4 in the example serves the purpose of 'container" and is not really required, but it allows the requirement to be reused.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 700 |
