Kontakt

Ansicht
Dokumentation

CRMUT_CHECK_CPIT_IMP - Implementation: Define Customer Checks

CRMUT_CHECK_CPIT_IMP - Implementation: Define Customer Checks

Vendor Master (General Section)   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

Call center agents can use the check cockpit to make regular consistency checks on the replication of utility contracts and points of delivery.

SAP provides predefined checks to ensure consistency in production systems and allow any inconsistencies to be dealt with.

These checks are for known problems regarding the document error statistics and the distribution status.

You can schedule the user interface checks and execute them immediately, periodically, or at specific times.

Standard Checks

The standard checks provided are implemented as classes in the system and be viewed using the Object Navigator transaction (SE80).

They are subclasses of class CL_CRM_ISU_CM_CHECK.

The checks are split into the following two classes:

  • Class CL_CRM_ISU_CM_ORDER_CHECK for contract checks
  • Class CL_CRM_ISU_CM_TECHOBJ_CHECK for technical object checks

In this document, we refer to these as check groups.

Customer Checks

You can also integrate your own checks by creating your own classes deriving from class CL_CRM_ISU_CM_ORDER_CHECK or CL_CRM_ISU_CM_TECHOBJ_CHECK.

Once they have been activated, the checks appear automatically on the user interface and can be scheduled.

No Customizing is necessary.

Interface IF_CRM_ISU_CM_CHECK must be implemented in the generated classes. For more information, see the section Interface IF_CRM_ISU_CM_CHECK.

Customer Check Groups

To have your own visualization of any problems found, or to distinguish between your own checks and the standard checks, you can create a new class with a grouping function as a subclass to CL_CRM_ISU_CM_CHECK.

  • In the class, you also have to implement methods GET_CATEGORY and GET_CATEGORY_DESCRIPTION for interface IF_CRM_ISU_CM_CHECK_CAT.
  • You can enter any description you want. It is used for the selection of check groups on the user interface.
  • The category is a technical grouping and is used for controlling the user interface.

Note

The following categories are delivered with the standard system:

  • 'UORD' for the standard visualization of contract-related problems
  • 'USLO' for problems relating to technical objects

You can use your own values beginning with "Z". However, you also have to configure the user interface accordingly.

For check runs, make sure that you always select checks from one check group only.

Interface IF_CRM_ISU_CM_CHECK

Interface IF_CRM_ISU_CM_CHECK contains the following methods:

  • EXECUTE_CHECK
This method contains the actual check.
First, all of the data is checked without any controlling parameters.
If an error is found, you have to generate a message by calling method ADD_MESSAGE. You can use as many messages as you want.
Not further steps are necessary for implementing the check.
When using the review function on the user interface, the table of objects to be checked is transferred to parameter IT_OBJECT_GUIDS. In this case, you have to restrict the selection to this object.
If the review is successful, the problem is set to Completed and is given the COMPLETED_AT time stamp.
  • IS_CORRECTION_SUPPORTED
This method determines whether automatic correction is supported.
If it is, the Automatic Correction function is available on the user interface.
  • CORRECT
In this check you enter the program requiring correction.
The import parameter IT_ISSUE_TAB contains the table of the objects to be corrected. Only the objects listed in this table can be corrected.
Call method ADD_MESSAGE with value IV_CORRECTED = 'X' and a descriptive message number.
This fills the time stamp CORRECT_EXE_AT. The value COMPLETED_AT is only set by the subsequent new check.

Method ADD_MESSAGE

You need method add_message in order to edit messages in the check cockpit. It is called to create error messages from the method execute_check (for a check ), or from the method correct (for a correction).

You must provide a message number.

You can also include field ISSUE_LEVEL to display the relevance of the problem.

You should include a reference object such as a contract item or point of delivery.

If you do not include a reference object, the message is used as a text for the check and no problem entry is generated.

If you do not include a reference object, a problem entry is created and therefore a correction is possible if available.

Example:

CALL METHOD ADD_MESSAGE

EXPORTING

IV_ISSUE_LEVEL = '3'

IV_REF_GUID = -guid

IV_REF_TYPE = 'B'

IV_MSGNO = '024'

IV_MSGV1 = -guid

IV_MSGV2 = -a4isucontr.

Check Run and Jobs

Checks for a check run are selected and scheduled on the user interface. A check run consists of one or more jobs.

The names of the jobs are compiled from the code "IUCM" and the check run number. This make them easy to find in the job monitor.

The jobs can be executed immediately, periodically, or at a specific time.

If a job is scheduled more than once, the job name stays the same, but new results lists are created with a different version number and job number. The search only takes the latest results into account. Once you have selected a check run, you can navigate to older versions in order to compare them.

If you do not want to execute a job immediately, or if this is not possible, a job is created for each check run.

The job contains a step for each check.

Each step contains the same program (CRM_ISU_CM_CHECK). The checks to be carried out are not visible from the job; you can only view them in the Utilities Check Cockpit. To do this, search for the job name.

You enter the job description on the user interface. The description should be as informative as possible.






ROGBILLS - Synchronize billing plans   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 7241 Date: 20240606 Time: 094007     sap01-206 ( 44 ms )