Show TOC

Example documentationExample: A Guided Procedure for Cross-Database Comparison

 

In Cross-Database Comparison (CDC), you can use guided procedures to document procedures to investigate inconsistencies you have identified, and to execute these procedures on a regular basis.

Background: Cross-Database Comparison (CDC) is a function of the Business Process Operation work center to setup consistency checks between systems and to execute and monitor these checks. You define the data to be compared using graphical modeling. From an overview of comparisons made, you can navigate into the detailed results.

In this simplified example of a comparison of business partners between CRM and ECC, we explain how you can set up and use guided procedures in this context.

Note Note

This document is just an example of how guided procedures can be used in this context. It is not a troubleshooting guide for CRM data exchange.

End of the note.

Prerequisites

  • To check the consistency of customer master data, you have created a comparison check between an SAP CRM system and an SAP ECC system.

    In our example, both the comparison object and a comparison instance are called ZTHOS_BUSINESS_PARTNER.

  • You are in the Data Consistency view of the Business Process Operations work center.

Activities

You create a guided procedure which allows the user to perform two steps to investigate typical reasons for business partner inconsistencies between ECC and CRM databases. Each contains two activities.

  1. In the first step, the user ensures that no BDocs of type BUPA_MAIN are in error state or pending.

  2. In the second step, to verify that no business partners are in backlog for data exchange, the user checks the status of the initial load and the qRFC inbound queue.

Creating a Guided Procedure
  1. Choose Cross Database Comparison.

  2. On the Comparison Run Overview tab page, select the ZTHOS_BUSINESS_PARTNER comparison instance for which you want to create a guided procedure, and choose the Show Last Result pushbutton.

  3. Choose the Guided Procedures pushbutton.

    Based on the selected comparison run, the Quick Criteria search parameters are pre-filled

  4. To start the creation of a guided procedure for the selected combination of comparison object and comparison instance, choose Create.

    A dialog box appears.

  5. In the Choose step, enter the following data:

    • Name: ZCDC_GP_BUSINESS_PARTNERS

    • Short Description: Investigate Business Partner Inconsistencies

    • Initial steps: 02

  6. In the Transport step, select a package to be used to store texts, and specify a local transport.

  7. Choose Create.

  8. Select step 1 and enter the following data:

    • Title: Check erroneous BDocs

    • Description: Ensure that no BDocs of type BUPA_MAIN are in error state

    • Type: Manual

  9. Add a help text:

    1. Under Step Help Text Name, choose New.

      A dialog box appears.

    2. In the Name field, enter: ZSTP_BUPA_BDOC, and choose OK.

    3. Enter the following text: In this step, you check a typical reason for business partner inconsistencies between ECC and CRM databases: BDocs that are not processed correctly.

    4. Save your entries.

  10. Add a manual activity:

    1. Under Activities, choose New.

      A dialog box appears.

    2. In the Activity Name field, enter BUPA_MAIN in error state and confirm.

    3. Save your entries.

  11. Add a help text for the manual activity:

    1. Under Activity Help Text Name, choose New.

      A dialog box appears.

    2. In the Name field, enter: ZACT_MAIN_ERRORS, and choose OK.

    3. Enter the following text: In this step, you check whether BDocs are not processed correctly:

      1. Log on to source system 1 and call transaction SMW02.

      2. Enter the following data:

      • BDoc type: BUPA_MAIN

      • BDOC state: E01 to E09

      3. Choose Execute.

      The status of Bdocs is displayed.

    4. If there are erroneous Bdocs, do the following:

      1. To display the Bdoc, double-click on its line.

      2. To check the reason for the error state, choose Show Bdoc Msg Errors/Receivers.

      3. Resolve the issue and reprocess the BDocs.

    5. Save your entries.

  12. To add a second activity, perform steps 10 to 11 with the following parameters

    • Activity Name: BUPA_MAIN pending

    • Activity Help Text Name: ZACT_BUPA_MAIN_PEND

    • Activity help text:

      1. Log on to source system 1 and call transaction SMW02. Enter the following data:

      • BDoc type: BUPA_MAIN

      • BDOC state: I01 to I04

      2. Choose Execute.

      3. In the result, ensure that no Bdocs are pending for a long time.

      4. If Bdocs are pending for a long time, check the status of the corresponding qRFC queues. If a queue is in error state, correct the error and restart the queue-processing.

  13. To edit the second step of the guided procedure, perform steps 8 to 9 with the following parameters:

    • Step description:

      • Title: Check qRFC queues

      • Description: Verify that no business partners are in backlog for data exchange

      • Type: Manual

    • Step help text:

      • Name:ZSTP_BUPA_QUEUES

      • Step help text: In this step, you check whether queues related to business partners are in error state.

  14. To add two activities, perform steps 10 to 11 with the following parameters

    • First activity:

      • Activity Name: ZACT_CHECK_BUPA_IL

      • Activity Help Text Name: ZACT_CHECK_BP_IL_HLP

      • Activity help text:

        Check the overall status of the initial load:

        1. In the CRM system, call transaction R3AM1.

        2. Specify the object type, for example, BUPA_MAIN, CUSTOMER_MAIN, or CUSTOMER_REL, which is the type corresponding to the CRM BUSINESS PARTNER object.

        3. Enter selection criteria, and choose Execute.

        The system returns the status of the initial load for the selected object.

        4. Verify that the status is a green traffic light.

        If the status is yellow, verify that the load is still running and the number of objects is increasing.

        If the number of objects does not increase for a long period of time, or if the overall status is red, check the initial load queue R3AI_BUPA_MAIN. If the queue is in error state, resolve the issue and restart the processing.

    • Second activity:

      • Activity Name: ZACT_CHECK_QRFC

      • Activity Help Text Name: ZACT_CHECK_QRFC_HLP

      • Activity help text:

        Check the qRFC inbound queue from the ERP system to the connected CRM system:

        1. In the ERP system, call transaction SMQ2.

        2. As the queue name, enter the prefix R3AI*, which is the common prefix for delta downloads from the ERP system's R/3 adapter to a connected CRM system. If possible, restrict the prefix by entering a part of the business object name, for example, R3AI_CUSTOME* for customer masters.

        3. Choose Execute.

        4. Ensure that there are no queues in error state.

  15. Save the guided procedure.

  16. Choose Activate.

    The guided procedure can be executed and transported into the production system.

Executing the Guided Procedure and Logging Activities
  1. Choose Cross-Database Comparison.

  2. On the Comparison Run Overview tab page, select the comparison instance for which you have created the guided procedure, and choose the Show Last Result pushbutton.

  3. Choose the Guided Procedures pushbutton.

    Your guided procedure, ZCDC_GP_BUSINESS_PARTNERS, is displayed. It consists of two steps, Check erroneous BDocs and Check qRFC queues.

  4. Select the guided procedure and choose Execute.

  5. To display the documentation of a manual activity, in the Documentation column, choose Display.

    A dialog box with your instructions appears.

  6. To enter a comment, expand the Comment area of the dialog box.

    In our example, you document which step resolved the error. You can describe the error in detail, for later reference and for traceability of the error reasons and correction procedures.

    User comments appear in the log table.