Professional Documents
Culture Documents
Copyright 2003 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix and Informix Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE is a registered trademark of ORACLE Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.
Contents
1. 1.1. 1.2. 2. 2.1. 2.2. 3. 3.1. 3.2. Introduction .................................................................................................4 Objective ..................................................................................................4 Definition of Terms..................................................................................4 Scenario Overview ......................................................................................6 IS-U / CRM Integration Data Model .....................................................6 Accelerated Move-In, Move-Out, Move-In/Out Entry: Data Model.......7 The IS-U Contract Monitor..........................................................................8 Calling Transaction ECRMREPL............................................................8 List Display for Replications Containing Errors ................................10
3.3. Detailed Display for Replication Containing Errors ...........................11 3.3.1. Menu and Toolbar for Detailed Display ..............................................12 3.3.2. Detailed Display for CRM Contract Replication ..................................13 3.3.3. Detailed Display for CRM Replication of a Connection Object ...........14 3.3.4. Detailed Display for CRM Replication of a Point of Delivery ..............15 3.3.5. Detailed Display for Parked Document...............................................16 3.4. 3.5. 3.6. 3.7. 4. Restart for Replication Containing Errors ..........................................17 Automatic Restart of Dependent Entries ............................................18 Workflow ECRMINFAILED ....................................................................19 Example: Restart Function Module ISU_CRMQ_RESTART_SAMPLE20 Appendix ....................................................................................................22
4.1. Use..........................................................................................................22 4.1.1. Prerequisites.......................................................................................23 4.1.2. Task: Edit Container with Parameters ................................................24 4.1.3. Task: Trigger Change Run .................................................................27
1. Introduction
1.1. Objective
This cookbook describes the handling and interface of the IS-U error monitor (transaction ECRMREPL). The error monitor is used for processing incorrect replications of CRM utility contracts in an IS-U system. It is also used for processing incorrect parked documents during the accelerated entry of move-ins, move-outs and move-in/outs. This document focuses mainly on the following contexts: Technical objects in CRM and IS-U Contract items in CRM and contracts in IS-U Parked documents in IS-U
You are given an overview of the fundamental functions and the various options for accessing the error handling interface. The new error processing functions are delivered with Add-On Support Package 13 for IS-U/CCS Release 4.64. The following applies for replications of CRM utility contracts and technical objects: The error monitor replaces the previous error handling through the two workflows WS20500133 Workflow for application log products and WS20500160 Replication CRM -> ISU incorrect. See unit 4 for information on the previous error handling process.
IBase components
Accelerated move-in, move-out, move-in/out entry The new transaction (EC70) for accelerated move-in, move-out and move-in/out entry, which is provided within the increased efficiency project (IS-U/CCS Release 4.64+)
Template that defines which master data is to be created automatically. The master data generator then generates master data from the master data template. Example: If products are sold during a sales promotion, the necessary master data is automatically created in the background using the master data template (for example, business partner and contract). Program that generates master data from the master data template (such as, business partner and contract). Agreement between business partner and utility company, which refers to exactly one division. The document created for the selected action, using the accelerated move-in, move-out, movein/out entry Location at which a utility service for a customer is supplied or determined. Generally, it is a customer apartment. The point of delivery is division-specific. The point of delivery is division-specific. A point of delivery has an external number (point of delivery ID) for an event. A point of delivery serves the following purposes: o communication during automatic data exchange (deregulation PoD) o the exchange of meter reading results (technical PoD) The following point of delivery categories exist for technical points of delivery during the exchange of meter reading results: o normal point of delivery category o virtual point of delivery category
2. Scenario Overview
2.1. IS-U / CRM Integration Data Model
Figure 1 explains the connection between objects in IS-U and the corresponding objects in CRM. The integration solution ensures consistency between the objects in both systems. In this way, for example, changes to an IS-U contract lead to changes to the corresponding contract item in CRM, and vice versa.
mySAP CRM
Business Partner
Contract Account
Bill
Business Agreement
Contract
Billing
Installation
Premise
PoD
Figure 1: Integration Data Model Graphic 2 shows how our integration supports the replication. Workflow WS20500160 ECRMINFAILED manages the agent determination for processing a replication in which an error has occurred. The trigger event for the workflow is CRMIN_FAILED, from the BOR object ISUCRMCNT. The event is triggered if an error occurs whilst the system is processing the master data template. This guarantees that precisely one work item exists for a replication process. Workflow WS20500160 places a work item with the text Error Handling for CRM Transaction <Transaction Number> in the SAP Business Workplace. You can access the error handling interface via the corresponding work item. You can also use the transaction ECRMREPL (IS-U error monitor) to manually call the error handling. Other functions are available via the transaction ECRMREPLM.
Interface ECRMREPL
Error
Yes
Workflow 20500160 Restart Successful Restart and delete DB product parameter entries and log
Yes
Yes
Error
Workflow 20500160 Restart and delete DB MDG parameter entries and log Restart Successful No Yes
End
The new interface is particularly intended for the entry of frequently occurring standard situations in move-in/out processing, such as call center operations. Unlike the present interface (transaction Move-out (EC60)), the new interface does not cover all specific actions in move-in/out processing. In cases such as complicated move-in/outs for commercial and industrial customers, we recommend that you continue to use the present interface for example, to map individual agreements with commercial and industrial customers in contract account. The new interface only contains those fields that the agent must complete manually when entering a move-in, move-out or move-in/out. You can use Customizing to determine which fields are included. For more information, see the cookbook Efficient Processes IS-U/CCS New Developments for Release IS-U/CCS 4.64 and 4.71, unit 8 Customer Service.
The interface is configured as following for the different system usages: Only accelerated move-in, move-out, move-in/out entry: Only CRM connection: Figure 3 Figure 4 Figure 5
Fig. 5: Initial Interface for CRM Connection and Accelerated Move-In, Move-Out, Move-In/Out Entry
10
Figure 6: List Display for Replications Containing Errors The system shows the following information in the list columns: 1. Column: Status of CRM transaction replication or parked document replication (Status) A red traffic light indicates that an error occurred during the replication. A yellow traffic light indicates that a replication attempt already exists for the replication, and that this transaction was inserted in the queue without starting the master data generator. Transaction No. The transaction number is either the transaction number created during the replication of CRM transaction items, or the parked document number. Item (Item) The item for the transaction number created when replicating CRM contract items. This column is only completed if a CRM transaction exists. Transaction A short text in the Transaction column specifies for which object the replication is being executed. Error date The date of the replication attempt that contains errors Error time The time of the replication attempt that contains errors Queue Number (QueueNo) The current entry in the queue for this replication. The entry with the lowest number in the queue is displayed with a yellow traffic light. Installation The installation created in IS-U is displayed in the Installation column.
2. Column:
3. Column:
4. Column:
8. Column:
Header Data
Error Log
11
The system displays the general data for the replication in the header data, such as the status of the replication, the queue number within the transaction, the IS-U product (the master data template), and error time information. In the case of contract replications, the CRM product and contract details are included in addition to the CRM transaction. For a parked document, the business partner, contract account and premise are also specified. If it is possible to restart the replication, the master data template parameters can be changed. For all other queue entries for the corresponding transaction, they are only shown in display mode. In the lower area of the detailed display, the error log is displayed. This is loaded after each unsuccessful restart.
Figure 7: Menu and Application Toolbar for Detailed Display The following prerequisites apply for the availability of buttons and menu entries for replication objects: Restart This button is only displayed if a restart is possible for the current entry. This is, for example,
12
only the case for the last entry for a replication (the highest queue number for the transaction). If a dependent entry exists for the highest queue number, then the Restart button is displayed. Dependency This button is only displayed if a dependent entry exists for the current entry. For a CRM transaction this applies, for example, if a contract and a connection object were replicated together and an error occurred during the replication of the connection object. In this case, the contract can only be replicated when the dependent connection object has been successfully replicated. This is the case for a parked document when, for example a move-out and/or business partner changes exist for a move-in. (SAP Business Workplace) This button is always displayed. It takes you to the SAP Business Workplace. Installation This button is displayed if a CRM contract replication or a parked document exists. When replicating technical objects, it is only displayed when precisely one installation can be allocated. This button takes you to the data environment for the installation. Premise This button is displayed if a CRM contract replication or a parked document exists. When replicating technical objects, it is only displayed when precisely one premise can be allocated. This button takes you to the data environment for the premise. Billing Reversal This button is only displayed for contract replication. You can use this button to reverse a billing or invoicing document that exists for a move-in or move-out. (Scroll to Previous Entry) This button is always displayed. You can, however, only scroll to the previous entry if an entry with a lower queue number exists. (Scroll to Next Entry) This button is always displayed. You can, however, only scroll to the next entry if an entry with a higher queue number exists.
(SAP Business Workplace) to go to the SAP Business Workplace Restart is available for the last queue entry, as long as no dependent entries exist (in this case, the button is displayed for dependent entries). the status of the replication containing errors
13
CRM transaction and item CRM product IS-U product (the master data template) Queue number within the transaction Contract account Contract specifications (contract start and end dates) Error time data
14
Restart is available for the last queue entry, as long as no dependent entries exist (in this case, the button is displayed for dependent entries). the status of the replication containing errors Queue number within the transaction IS-U product (the master data template) Error time data
(SAP Business Workplace) to go to the SAP Business Workplace Restart is available for the last queue entry, as long as no dependent entries exist (in this case, the button is displayed for dependent entries). the status of the replication containing errors
15
Queue number within the transaction IS-U product (the master data template) Error time data
(SAP Business Workplace) to go to the SAP Business Workplace Installation or Premise to go to the data environment for the installation or premise
Restart: The Restart button is available for the last queue entry, as long as no dependent entries exist (in this case, the button for dependent entries is displayed).
16
The status of the replication containing errors Parked document Master data template Queue number within the transaction Installation Error time data
17
EVER_CRMQ-MQ_ORIGOBJ. The function module ISU_CRMQ_RESTART_POD is called via this entry during the restart. If the table in the IS-U system is initial, it is initialized with the values from table 1 for the first restart attempt. The table ECRM_FBREST has the delivery class E, which allows customer-specific maintenance. This allows the customer to develop his/her own function module, which , for example, supports a device installation during replication. The function module ISU_CRMQ_RESTART_SAMPLE acts as a template for the development of customer-specific restart function modules. The syntax of the function module is specified in section 3.7. When a restart is successful, the detailed display is changed into a pure display transaction. Menu bars and push buttons are hidden. It is still possible to return (select F3) to the list of replications containing errors. When you call the detailed display from a workflow, the workflow is exited. If the restart is not successful, then the current replication transaction is reloaded in the detailed display.
MD_ORIGOBJ
FB_RESTART
ISU_CRMQ_CONTRACT_RESTART ISU_CRMQ_RESTART_SAMPLE ISU_CRMQ_CONTRACT_RESTART ISU_CRMQ_RESTART_POD ISU_CRMQ_RESTART_RGEN ISU_ECAMIO_RESTART_MVIN ISU_ECAMIO_RESTART_MOUT ISU_ECAMIO_RESTART_BUCA Table 1: Contents of Table ECRM_FBREST
18
Parked Document: For a move-in entry, the business partner must be changed / created, as well as the installations being changed. You must change / create the business partner before you change the installation. Parked Document: During a move-in/out for a premise, a move-out and a move-in are entered for the premise. The move-out must occur before the move-in. The move-in is dependent upon the move-out. Parked Document: During a business partner move-in/out a move-out, move-in and a business partner change are entered. The move-out and business partner change must take place before the move-in. The move-in is dependent upon the move-out and business partner change. The move-out and business partner changes are, on the other hand, independent of each other.
If dependent entries exist for a replication containing errors, then they too are restarted following a successful restart. The detailed display of the IS-U Navigator then switches to the dependent entry. If the dependent entry is successfully restarted, the detailed display changes to a purely display transaction for the dependent entry.
19
Start Event
ISUCRMCNCT.CRMIN_FAILED
Workflow Complete
20
CL_EZLOG.
* * * *
* *
IF x_debug = 'X'. BREAK-POINT. ENDIF. CLEAR y_restart_ok. CALL FUNCTION 'ISU_CRMQ_RESTART_BEGIN' EXPORTING x_object_guid = x_object_guid IMPORTING y_ever_crmq = l_ever_crmq y_container = l_container Y_CONTRACT_STATUS = y_new_keys_tab = l_new_keys_tab EXCEPTIONS action_failed = 1 OTHERS = 2. IF sy-subrc <> 0. queue-entry not found: handled by empty y_ever_crmq ELSE. y_ever_crmq = l_ever_crmq. IF NOT l_ever_crmq-prodid IS INITIAL. l_mdg_container[] = l_container[]. CALL FUNCTION 'ISU_PRODUCT_IMPLEMENT' EXPORTING x_prodid = l_ever_crmq-prodid x_container = l_mdg_container x_raise_no_event = 'X' X_NO_BPCONTACT = X_CONTRACTDATA = X_NO_ENV_SELECT = X_INDUSTRY = IMPORTING y_logid = y_ever_crmq-mdg_log Y_SCRIPT_INFO_TAB = Y_IDE_STARTED = y_mdg_completed = y_restart_ok CHANGING xy_new_keys_tab = l_new_keys_tab XY_DONE_NODE_TAB = EXCEPTIONS general_fault = 1 input_error = 2 ambiguous_environment = 3 OTHERS = 4. IF sy-subrc <> 0. input or processing error
21
* *
CLEAR y_restart_ok. ENDIF. IF NOT l_new_keys_tab IS INITIAL. y_new_keys_tab[] = l_new_keys_tab[]. ENDIF. IF NOT l_ever_crmq-prodid IS INITIAL. y_ever_crmq-prodid = l_ever_crmq-prodid. ENDIF. ENDIF. ELSE. "IF NOT l_ever_crmq-prodid IS INITIAL. ENDIF. ENDIF. "CALL FUNCTION 'ISU_CRMQ_RESTART_BEGIN'
ENDFUNCTION.
4. Appendix
4.1. Use
The system activates this function if an error occurs when processing an MDT . Firstly, the system triggers the FollowUpNecessary event (additional processing required for log) of the ISUPRODLOG BOR object type (product log for IS-U). FollowUpNecessary is the triggering event for the workflow template 20500133. This workflow template contains the activities Edit Container with Parameters and Trigger Change Run. For more information, see the units on the individual activities. The figure below shows the context.
22
An error occurred when processing within the master data generator Triggering Events: Object cat.: ISUPRODLOG Event: FollowUpNecessary
4.1.1. Prerequisites
Once the FollowUpNecessary event from BOR object type ISUPRODLOG has been activated, and subsequent processing triggered, you must activate the event linkage in workflow template 20500133. To do this, proceed as follows:
...
23
2. In the Task Type field, select Workflow-Muster. In the Task field, enter the name of the workflow template. Select (Display).
3. To activate the event you must first select it and then choose Edit Event Activate /
Deactivate Linkage By activating the event linkage, you guarantee that the workflow starts if an error occurs within the master data generator. You must also ensure that the activities contained in the workflow have been allocated to an agent.
24
Figure 16: Screen displaying the application log Once the agent knows why the system canceled processing, he/she can then change the unprocessed MDT parameters in a second session. This ensures that no errors occur when processing is rerun. The agent can also make parallel changes to data in the IS-U. This ensures that errors do not occur during processing.
25
Figure 17: Screen showing parameters When the agent has ensured that no other errors can occur, he/she must save the parameters.
26
Figure 18: Completion of Processing This interim enquiry was inserted to allow the agent to interrupt the processing and to continue at a later date. To do this, choose Cancel.
27