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_CRD_SIMPLERQMNT | BAdI: Enhance Simple Requirements |
| Transaction Code | S_PRN_53000399 | (empty) |
| Created on | 20070102 | |
| Customizing Attributes | _CRD_CRD_SIMPLERQMNT | BAdI: Enhance Simple Requirements |
| Customizing Activity | _CRD_CRD_SIMPLERQMNT | BAdI: Enhance Simple Requirements |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | CRD_SIMPLERQMNT |
Use
Business Add-In (BAdI) Enhancement of Simple Requirements enhances the standard functions to define and check requirements.
Requirements
Standard settings
There is no standard implementation. The BAdI is not for multiple use; it is filter-dependent. The following filters are available:
- APPL - Credentialing application
- REQ - Requirement
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
See also
This BAdI uses the interface IF_CRD_SIMPLERQMNT_ENH. For more information, display the interface in the Class Builder.
Example
The standard permits the definition of simple requirements along the lines of credential descriptions. Fixed values can be defined or attributes filled using MOVE-CORRESPONDING. This covers a large area of feasible tests, but many special requirements cannot be described in such general terms.
For instance, in the USA certain requirements make it necessary to have a credential assignment that is specific for a particular federal state, and in certain cases it is a requirement that a business partner living in another state shows proof of owning this credential
In other cases, a specific license is required by a federal state but the place where the partner lives is irrelevant. In the BAdI, depending on the context data a 'resident' attribute in the requirement can be set.
Another example is the need for a mapping that is not covered by MOVE-CORRESPONDING, if for instance values for attributes of the requirement have to be calculated from process data.
Apart from the specification of a requirement, the BAdI lets you influence the check result. Checks that are not supported by the structure of the credential descriptions can be carried out in this way, such as a check for reaching the age of legal majority for credentials that have no age information.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20070515 |
| SAP Release Created in | 700 |
