Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
ICM (Application Component) Incentive and Commission Management (ICM)⤷
CACS71 (Package) ICM: Integration Credentialing
IMG Activity
| ID | _CACS_CACS_CRD | BAdI: Credentials Check |
| Transaction Code | S_AER_95000323 | (empty) |
| Created on | 20060613 | |
| Customizing Attributes | _CACS_CACS_CRD | BAdI for Credentialing |
| Customizing Activity | _CACS_CACS_CRD | BAdI for Credentialing |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | _CACS_CACS_CRD |
Use
This Business Add-In (BAdI) is used in Incentive and Commission Management (ICM). You can use the methods in BAdI definition Credentials Checks in ICM (CACS_CRD_CHECK) to influence the credentials checks.
In the standard delivery, credentials checks take place in the following processes: Create Commission Case, Create Manual Commission Document and Execute Entitlement and Liability Transfer.
Requirements
Methods CONFIRM_CRD_CHECK and POSTPROCESS_CRD_CHECK must be implemented and activated if you intend to use them.
Standard settings
The BAdI implementation CACS_CRD_CHECK_DIRECT is activated in the standard system. Methods CONFIRM_CRD_CHECK and POSTPROCESS_CRD_CHECK are delivered without an implementation. Method EXECUTE_CRD_CHECK calls SAP Credentialing as the default implementation, and checks the credentials.
The default implementation uses the direct call of a credentialing application by a method (not RFC-enabled). In the default implementation, you can use the copy services to map commission data to message data. When you do so, the system uses events 4000, 4001, and 4002 at runtime.
In addition to the default implementation, there is also a standard BAdI implementation CACS_CRD_CHECK for calling a credentials check through a message-based interface (eSOA, XI). The implementation of the mapping of commission case data to message data forwards data to SAP Credentialing. You may have to activate this implementation.
The BAdI is not designed for multiple use. The BAdI is filter-dependent; the filter value of the BAdI definition is the commission application.
Activities
Create a BAdI implementation that contains the following methods (as required):
- CONFIRM_CRD_CHECK - checks whether the credentials are to be checked.
Method CONFIRM_CRD_CHECK can be used to switch off the credentials check during runtime. Whether the credentials need to be checked is determined by the data in the commission document header and the remuneration lines that have been created up to this point. If the method of CHANGING parameter CV_EXECUTE_CRD_CHECK is set to SPACE, the subsequent credentials check is not executed. The check can only be switched off completely; it is not possible to switch off the check for individual remuneration lines. If the credentials check is switched off, a warning message is written to the log.
- EXECUTE_CRD_CHECK - checks the credentials
Method EXECUTE_CRD_CHECK carries out the actual check. You can specify any credentialing system due to the encapsulation in a BAdI method. SAP Credentialing is called by default. Each remuneration line that does not pass the credentials check is identified by the FLG_BLOCKECK_CRD indicator in the remuneration meta-line. The importing parameters of the method are the commission document header and the remuneration lines (only DB fields).
- POSTPROCESS_CRD_CHECK - Postprocesses the credentials check.
You can use method POSTPROCESS_CRD_CHECK to influence the result of the credentials check. You can postprocess the result of the credentials check as you require by transferring the checked remuneration lines (DB fields) that have set the FLG_BLOCKED_CRD indicator, and by reading and changing the process log.
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 IF_CACS_CRD_CHECK interface. For more information, display the interface in the Class Builder.
Example
Business Attributes
| ASAP Roadmap ID | 105 | Define functions and processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-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 | _CACS_CACS_CRD | 0 | KK40000031 | Incentive and Commission Management (ICM) |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20070816 |
| SAP Release Created in | 700 |
