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.)
IMG Activity
| ID | _CRD_VCRD_REQATT | Configure Requirement Assignment Types |
| Transaction Code | S_PRN_53000405 | (empty) |
| Created on | 20070103 | |
| Customizing Attributes | _CRD_VCRD_REQATT | Configure Requirement Assignment Types |
| Customizing Activity | _CRD_VCRD_REQATT | Configure Requirement Assignment Types |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | _CRD_VCRD_REQATT |
Use
In this IMG activity you configure requirement assignment types that are identified by a rule. These are only relevant for requirements that are used as items in requirements lists or combinations and that are, strictly speaking, assigned to the items.
- Requirement assignment types determine which partners of the requirement are assigned in the item at runtime. The assigned partners are always considered to be a list of assigned partners for which the particular requirement is to be checked. These lists can also be empty or they can contain only one partner.
- Requirements that occur in a requirements list as an item, can themselves in turn be interpreted as a list or a combination.
- Requirements that occur in a combination as an item can only be sorted as an item. If the list that is created is used as a combination, a combination algorithm must be assigned in any event by assigning a combination type. The combination type is used as a BAdI filter and controls the call of the algorithm that is used.
In this IMG activity you can also define parameters that affect the selection of partners who are to be assigned to the requirement. To do so, you enter the name of the fields used. The values to be used are defined in the items of the requirements lists in question. This makes it possible for requirements only to be assigned to partners in certain roles.
Requirements
- If you use a combination type, an implementation of the BAdI Factory for Combination Algorithms for Partner Lists (CRD_COMBALG_PLIST_FACTORY) must exist for it.
- You must also define the combination type in the implementation as a filter.
- The parameters used must be listed in the structure that describes the members of the partner group. This is the structure <APPL>_S_PARTY, which can be enhanced during the application construction. A parameter serves as a simple filter. If you use a second parameter, only those partners are assigned that fulfill both conditions.
Standard settings
An AND and OR operation are included in the standard delivery.
Activities
Define the required parameters that are to serve as filters.
Note that this construction only provides a simple version of a frequently expected restriction.
For complicated assignment rules, we recommend that you implement your own assignment algorithms. To do so, you can use the BAdI Create Class for Requirement Assignment Rule (CRD_ATTALG_FACTORY).
Example
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | _CRD_VCRD_REQATT | 0 | PRN0000071 | Credentialing (CRD) |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| VCRD_REQATT | V - View | SM30 |
History
| Last changed by/on | SAP | 20070515 |
| SAP Release Created in | 700 |
