How-To Guide

SAP Cloud for Customer

Document Version: .2.0

Last Update: June, 2015

How to Monitor Messages across SAP on-premise and SAP Cloud for Customer via Integration

Document History

Document Version Description

1.0 First official release of this guide

2.0 Updated with new HCI monitoring features

Table of Contents

1 Business Scenario ............................................................................................................... 3

2 Background Information ......................................................... Error! Bookmark not defined.

3 Prerequisites ........................................................................................................................ 3

4 Monitoring Message Flow ................................................................................................... 3

4.1 Monitoring in HCI .......................................................................................................... 3 4.2 Error Resolution in HCI ............................................................................................... 15

4.2.1 Retrieving payload from on-premise system ................................................. 15 4.2.2 Retrieving payload from cloud for customer tenant ....................................... 16

4.3 Monitoring in PI ........................................................................................................... 19 4.4 Error Resolution in PI ................................................... Error! Bookmark not defined. 4.5 Monitoring in SAP on-premise (SAP CRM/SAP ERP) ............................................... 29 4.6 Monitoring in SAP Cloud for Customer ...................................................................... 32

1 Business Scenario During Data Loads and Go-Lives, monitoring of messages plays a crucial aspect in figuring out incorrect data in messages, narrowing down on the component where the message has failed and whether there are any connectivity issues between the components.

2 Prerequisites

Technical connectivity between SAP CRM or SAP ERP and SAP Cloud for Customer and

vice-versa.

Integration Configuration settings specified in the Configuration guide for the SAP CRM or SAP ERP, SAP middleware such as NetWeaver Process Integration or HANA Cloud Integration, and Cloud Systems.

Data Loads and Code list mapping

3 Monitoring Message Flow This section describes the monitoring and error resolution in HCI, PI, SAP on-premise, and SAP Cloud for Customer.

3.1 Monitoring in HCI

Monitoring in HCI can be done using the WebUI or the Eclipse UI. It is recommended to start with the WebUI.

Under Monitor Menu there are two options:

1. Message Monitor 2. Integration Content Monitor

3.1.1 Message Monitor

Select the Message Monitor to view Message Monitor Details

The message can be viewed for specific Status, Time, for an integration flow and Message/Application ID.

Select the message use the Action column and Show Details to view the message process log (MPL).

Show Details navigates to the log.

The Search option is available to lookup in the message log. You can also download the Message Processing Log (MPL).

The Message GUID from the Message Processing Log can be selected from the main search screen

The URL for the specific message can be bookmarked.

The Tiles on message monitor can be configured as per your requirement with the edit option on every tile, similarly it can be deleted with the X available on the Tile

Users can create, modify and delete the Tiles.

The Tile can be dragged and dropped within the pane.

3.1.2 Integration Content Monitor

The Integration Content monitor is used to view the details of the artifacts on the specific tenant. Views are based on status, type and artifacts.

User can view the details from the Action → Show Details.

The status of the deployed artifact should be “started”.

The integration artifacts displays the status of the deployed iFlow projects visible under My Projects.

For example, if there is an error it is visible in the dashboard. You can drill down to the error directly by clicking on the Error hyperlink.

You can further drill down by clicking on the hyperlink to see the error details.

Ideally, all your iFlows should have the status “Started” for successful message execution.

To filter to the exact iFlow you are looking for, select the desired status and the integration artifact.

Depending on the type of error message, you can raise a ticket using the following components:

LOD-HCI : If it is a SAP HANA Cloud Integration issue

LOD-CRM-INT-ERP/CRM: If it is a ERP/CRM Integration package that is being used.

3.1.3 Message Tracing Scenario 1: Replication from ERP to C4C

Open transaction WE02 /WE05 to view the IDOC and select an IDOC.

Notice the control record of the IDOC.

Open the Web UI Monitor.

Copy the IDOC number in the ID field, the message records will be visible only for IDOC number.

Till this point we have traced the message from ERP to HCI based on IDOC number which is very simple to identify.

Open the message and copy the message ID as highlighted in the screen shot below .

Now we need to check the message ID reaches the C4C system.

In your SAP Cloud for Customer Tenant, use the Silverlight UI and navigate to the Web Service Message Monitoring in the Administration work center.

Open the Advanced search option and pass the message ID copied from HCI message.

This shows the message has reached C4C and completes end-to-end tracing from ERP to C4C.

3.1.4 Message Tracing Scenario 2 – Replication from C4C to ERP

In the SAP Cloud for Customer tenant go to the Web Service Monitor.

Copy a message ID.

In the HCI Web UI monitor, paste in the message ID from C4C to view the details of that particular message.

Open the message and copy the IDOC number from the message, it will be visible as highlighted in the screen.

Use this IDOC number in the SAP CRM/SAP ERP idoc monitor to find the IDOC.

This completes the tracing of message from C4C to HCI to ERP.

Note

To view detailed error logs on HCI runtime tenant, it is possible via HCI Eclipse. Go to Window Show View and select Tail Log.

Click on the IFLMAP node in Operations perspective. Enter log size.

3.2 Error Resolution in HCI

When performing error resolution you often need to review the payload. This can be done in ERP, HCI, and SAP Cloud for Customer.

3.2.1 Retrieving payload from on-premise system

1. Use XML file port to generate IDoc XML Provide a directory path that is accessible from AL11.

2. Go to transaction code WE19 and use previously created port to generate IDoc XML. (Remove Archive key from control record if present).

3. Use function module ARCHIVFILE_SERVER_TO_CLIENT to download the file to your desktop.

3.2.2 Retrieving payload from C4C tenant

1. Go to Administrator work center and click on Web Service Message Monitoring.

2. View all incoming/outgoing messages in the monitoring UI.

3. Select the incoming message that you are interested in and click on View Payload

4. Download the payload xml file on your desktop.

3.2.3 Retrieving payload from HCI

In order to view the payload in HCI you first must create a ticket to request authorization. The role ESBDataStore.readPayload (which is part of authorization group AuthGroup.BusinessExpert) must be assigned to your user.

Once tracing is enabled, select Trace Configuration in the property of the iFlow. Select the Trace Level to be Message Body and Header.

Once the MPL is fetched, select the envelope for the step where you want to see the payload. The details of the properties will show the payload.

This blog describes in detail the tracing capability in HCI: http://scn.sap.com/community/pi-and-soa-middleware/blog/2014/11/28/blog-1-tracing-capability-in-sap-hana-cloud-integration-hci-pi

3.3 Monitoring in PI

3.3.1 Scenario1: C4C to On Prem ERP via PI as middleware

Open the Web Service Message Monitor in C4C.

Select the Message and copy the Message ID –

00163E0BCFA51EE584E95B2F2964CF65

Go to transaction SXMB_MONI in the PI system -

Pass the message ID in the tab Advanced Selection Criteria and press F8

On execution the message will be visible -

Double click the message –

Click on the response –> payload -> Maindocument and search CTRL+F with the message ID (sample

00163E0BCFA51EE584E95B2F2964CF65) as ARCKEY

Go to transaction code WE02 and select the EDI tab.

Pass the ARCKEY with * i.e. *00163E0BCFA51EE584E95B2F2964CF65, the key corresponds to IDOC

number.

This completes the cycle from C4C to On Prem ERP.

3.3.2 Scenario 2: On Prem ERP to C4C via PI as middleware

Go to transaction WE02 and pick an IDOC number to track the message –

Go to Transaction IDX5 in PI – pass the IDOC Number

Relevant message against the IDOC will be displayed

Double click the message ID and scroll to the right

Copy the messge ID - FA163ED10E711EE584EB63C091A8D4BD and pass it in the message monitor

in C4C –

3.4 Monitoring in SAP on-premise (SAP CRM/SAP ERP)

SAP ALE offers standard IDoc monitoring capabilities through transactions WE02 or

WE05.

1. Go to SM59 to check the connectivity between SAP on-premise and SAP

Middleware

2. Go to transaction we02/we05 to select the IDocs you wish to monitor.

3. In the details view select from the left tree the IDoc type you wish to monitor.

4. Check we20 partner profile configuration to see if the configuration settings are

maintained correctly.

5. Double click on the Message Type and verify that the correct Port is assigned to

the respective idoc message type. This port should point to either the PI or HCI

server depending your middleware provider. Output Mode should be set to

“Transfer Idoc immediately”.

Knowing the various status codes of IDocs in SAP on-premise can also assist in

narrowing down and resolving the error. Here are some of the most frequent error

codes,

Outbound IDocs

Status/Error Message IDoc Status

Further Checks to Resolve the Error

Error passing data to port - Problem with SOAP class

02 This error can occur for several reasons, such as missing Web service configuration or a process error in the Internet Communication framework. Check the details as described above.

A yellow light might indicate that an IDoc has been created, but has not been sent to the cloud solution, yet. In this case, check the outbound parameters of the partner profile in transaction WE20. If the output mode is set to Collect IDocs, use the report RSEOUT00 to send the IDocs to the cloud solution.

Inbound IDocs

Status/Error Message IDoc Status

Further Checks to Resolve the Error

Application document not posted - Material is not defined for sales org. <…>

51 Maintain the sales organization data for the material and restart the message.

Application document not posted – Postal code must have length <…>

51 Correct the document in SAP Cloud for Customer.

Application document not posted – Specify the account group

51 Correct the document in SAP Cloud for Customer.

Application document not posted – Fill all required fields

51 Correct the document in SAP Cloud for Customer.

Application document not posted – Sales are does not exist

51 Make sure that you only send documents for which the sales organization is maintained in SAP Cloud for Customer and SAP ERP.

Application document not posted - The region <…> is not defined for country <…>

51 Correct the document in SAP Cloud for Customer.

Application document not posted – Invalid key <…> for <…>

51 Correct the document in SAP Cloud for Customer.

A yellow light might indicate that an IDoc has arrived in SAP ERP, but has not been posted to the application, yet. In this case, check the inbound parameters of the partner profile in transaction WE20. If the inbound option is set to Trigger by background program, use the report RBDAPP01 to send the IDocs to the application.

3.5 Monitoring in SAP Cloud for Customer

1. You can monitor incoming/outgoing messages from the WS Monitor within the Administration Workcenter

2. View the complete list of messages within the ws monitor.

3. You can further filter the messages based on different filter criteria.

4. To view the detailed error message, select the entry in the ws monitoring table

and go to View Error Log

5. To view the payload, go to View Payload

© 2015 SAP AG or an SAP affiliate company. 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. National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such

products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP 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 other countries.

Please see http://www.sap.com/corporate-en/legal/copyright/ index.epx for additional trademark information and notices.

www.sap.com/contactsap