Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
FS-CMS-MD (Application Component) Master Data⤷
CMS_OMS_COMMON (Package) Collateral Management: Common Services for Object Systems
IMG Activity
| ID | SIMG_CMS_COB_PL_CHK | Define Plausibility Checks |
| Transaction Code | S_PLN_62000719 | (empty) |
| Created on | 20040507 | |
| Customizing Attributes | SIMG_CMS_COB_PL_CHK | Define Plausibility Checks |
| Customizing Activity | SIMG_CMS_COB_PL_CHK | Define Plausibility Checks |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CMS_COB_PL_CHK |
In this IMG activity, you define additional plausibility checks to extend the business checks delivered in the standard system. These include all necessary checks that need to be triggered in the process control.
By assigning checks to plausibility processors, you determine checks that will be implemented for each plausibility processor. Since the Business Add-In CMS_AST_CHECK is implemented per plausibility processor, the checks for a processor are coded in this implementation.
This activity is a client-independent activity, hence plausibility checks are applicable for all clients in the system. The checks defined in the implementation must start with a Y or Z.
Additionally, you must specify the messages that each check would use to return the outcome of the check to the user. For each message, you must also specify the message (error, warning, information, etc.) that would be applicable whenever the check is run.
Note: The system uses the message type from the checks This can, however, be overridden by the message type defined at the activity level. This is because the message type is an activity-dependent attribute of the check.
Example
The standard system has some plausibility checks defined. Some plausibility checks that the standard system
- To ensure that the lending rates are in ascending order. Your implementation team can determine its requirements and create a new plausibility check accordingly.
- To ensure that business partner function is a mandatory for each business partner.
Requirements
Standard settings
The standard system delivers a set of commonly used plausibility checks that can be used in the processes. These checks can be used with customer-specific checks, to form check sets, that are assigned to business activities.
Recommendation
Activities
Determine the plausibility checks that you need for your business requirements. Also, create messages and assign a message type to these messages.
Further notes
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 | SIMG_CMS_COB_PL_CHK | 0 | (ALN0000077 O PLN0000002 O PLN0000003 O PLN0000004) |
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 |
| VCV_VC_CMS_PCN_PL_OMS | C - View cluster | SM34 | Plausi Checks for all other Collateral Objects |
History
| Last changed by/on | SAP | 20040512 |
| SAP Release Created in | 500 |
