Integration Framework of SAP Business One Introduction to
Integration Framework of SAP Business One Introduction to Scenario Monitoring and Debugging 03 2015 INTE RNA L
Objectives After completing this course, you will know how to: ● Monitor events from SAP Business One ● Perform general monitoring of a running scenario step using the message log ● Display error messages and exceptions ● Debug and retry a scenario step from the message log ● Use the monitoring tools to monitor internal queues and processing calls ● Monitor the internal process steps and processing flow of the integration framework © 2015 SAP SE or an SAP affiliate company. All rights reserved. 2
Introduction to Various Monitoring Tools Goal Tool Monitor events coming from SAP Business One B 1 Event Monitor and B 1 Event Sender Monitoring and debugging messages in the integration framework Message Log Managing and monitoring the internal process steps of the integration framework Process Control Monitoring internal queues and calls of the integration framework Queue Monitor, Call Monitor Detailed debugging of the internal process steps of the integration framework Message Log, Process Control and Control Center © 2015 SAP SE or an SAP affiliate company. All rights reserved. 3
Cockpit Tab Cockpit tab provides a quick overview of: § Scenario package stats § System errors § Blocked queues § Activation conflicts § Biz. Store resource usage Click the widget to see more information such as the error message © 2015 SAP SE or an SAP affiliate company. All rights reserved. 4
SAP Business One Event Monitoring
SAP Business One Events Imagine that you have a scenario that uploads sales orders daily from SAP Business One to a SAP ERP system. You get a call that no sales orders have been received from SAP Business One. Where do you start to look? © 2015 SAP SE or an SAP affiliate company. All rights reserved. § Events from SAP Business One are held in the SEVT table of the common database § The SAP Business One event sender, the DI Proxy and the SLD are all involved in the exchange of the event from the event table to the integration framework. § On the SAP Business One server, make sure all services are running 6
SAP Business One Event Monitor Path: Monitoring → B 1 Event Monitor § B 1 Event Monitor displays events from the SAP Business One event sender § You can display events by status: success, failure, or filtered. Choose the Refresh icon to refresh the display. § The log entry shows the company database, object ID, document number, timestamp, target host and the internal processing step Refresh icon © 2015 SAP SE or an SAP affiliate company. All rights reserved. 7
Filtered Event A filtered event indicates one of the following: § The SAP Business One system is not defined in any active scenario sender list § The SAP Business One system does not meet any event filtering conditions § There are no active scenario packages for the event, or a scenario package has been deactivated © 2015 SAP SE or an SAP affiliate company. All rights reserved. 8
B 1 Event Monitor Actions Path: Monitoring → B 1 Event Monitor § If the event is displayed with the failure status, you will see an error message in the entry § For events with the failure or success status, there action icons to edit the target B 1 i application field and retry the event Action icons: • Edit • Retry © 2015 SAP SE or an SAP affiliate company. All rights reserved. 9
SAP Business One Event Sender Troubleshooting Path: Tools → Troubleshooting → Functional Group: B 1 Event Sender § The Event Sender troubleshooting tool allows you to check for errors or inconsistencies in the event sender configuration and SAP Business One notification settings § Select the B 1 Event Sender from the list of functional groups § The tool provides five checks that you can run individually © 2015 SAP SE or an SAP affiliate company. All rights reserved. 10
SAP Business One Event Sender Checks Path: Tools → Troubleshooting → Functional Group: B 1 Event Sender The event sender displays: 1. General system information 2. Configuration information for the event sender 3. Status of the notification mechanism for each SAP Business One company database. 4. Events from the SEVT table for each company database. 5. A summary of all information, with an overview for each company database © 2015 SAP SE or an SAP affiliate company. All rights reserved. 11
Monitoring Messages using the Message Log
Message Log Path: Maintenance → Cfg Msg. Log The Message Log shows all messages being processed through the integration framework: § To enable the Message Log, select the checkbox § With daily deletion, message log entries are removed each day § To see detailed debugging information, select “Full message” as the Log Level and set the log level parameter to CONFIG in the configuration file 'xcellerator. cfg‘ © 2015 SAP SE or an SAP affiliate company. All rights reserved. 13
Filtering the Message Log Path: Monitoring → Message Log n n n You can filter message log information using various filters, such as date, sender or receiver system, package, step, or object The status filters are Success, Failure, Processing or Filtered Search Keys can be defined in scenario package definitions and used here Filtering fields Message with Success status © 2015 SAP SE or an SAP affiliate company. All rights reserved. 14
Viewing Message Log Information recorded in the log includes: scenario package and step, sender and receiver system, trigger, date and time, and result message Message log icons allow you to delete and export messages, and change the columns displayed in the log by: § Manually resizing the column width using a mouse, or § Using the Show/Hide columns icon Delete selected message(s) Delete imported message(s) Export selected message(s) Show/hide columns © 2015 SAP SE or an SAP affiliate company. All rights reserved. 15
Status and Actions for a Message § The Status icons indicate the message status, and if this is a local or imported message § The Actions icons allow you to start debugging the internal XML message Message status Local or imported message Debug message Open message Retry message © 2015 SAP SE or an SAP affiliate company. All rights reserved. 16
: Open Action § Use the Open icon to view the current XML message. This enables you to analyze the sender trigger and payload © 2015 SAP SE or an SAP affiliate company. All rights reserved. 17
Debug Action § Use the Debug icon to see the internal process steps that the integration framework performs when running the step § Note: this information shows ONLY if you have selected CONFIG as the level of debugging. You should also enable “Full message” logging in the message log © 2015 SAP SE or an SAP affiliate company. All rights reserved. 18
Retry Action Use the Retry icon to resend the message (in a test environment) from different points of execution: § From the start § From the step processing § From the outbound phase © 2015 SAP SE or an SAP affiliate company. All rights reserved. 19
Message Log – Error Inbox of Receiver Systems § The Error Inbox button displays the error inbox for each receiver system § Typical errors include connectivity problems to the receiver system, system availability, or incorrect data mappings § Select the receiver system to open the error § You can resend the message or delete it © 2015 SAP SE or an SAP affiliate company. All rights reserved. 20
Message Log - Last Exception § The Last Exception button displays a list of IPO process steps that have ended with an exception § The application link contains the system ID and the step name § The TID link opens a panel for further debugging § Option to deactivate or reactivate step © 2015 SAP SE or an SAP affiliate company. All rights reserved. 21
Debugging a Message from the Message Log
Debug Action – Graphical View § Debug action in message log allows you to drill-down to debug panel § Graphical View link shows a graphical representation of the integration framework step processing Incoming B 1 Event SAP Business One Sender System Framework retrieves data matching the event from SAP Business One Distribution for outbound Internal Queues © 2015 SAP SE or an SAP affiliate company. All rights reserved. Outbound to File System 23
Debug Action – Processing Flow Debugging § Click the step to open the Biz. Flow processing window § Select red arrows to check atom parameters, XML, and configuration Note: To see flow debugging arrows, you must first enable debugging in Process Control © 2015 SAP SE or an SAP affiliate company. All rights reserved. 24
Debug Panel Buttons - 1 The debug panel buttons for each IPO step: IPO-Log displays detailed processing information Msg. Flow Inq. displays the flow of the message, starting with the first step and moving from successor to successor Msg. Proc. Tmng displays timing information Important: To see full debug information, set the log level to CONFIG in xcellerator. cfg, and enable detailed log information. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 25
Debug Panel Buttons - 2 The debug panel buttons for each IPO step: Exec. Details displays all processing step details in one document Debug opens the Biz. Flow processing flow debugging window Profiler allows checking potential performance issues on different levels Delete removes the log entry © 2015 SAP SE or an SAP affiliate company. All rights reserved. 26
Process Control
Process Control Path: Monitoring → Process Control Shows all systems and scenario steps of the integration framework categorized by processing phase (inbound, processing, and outbound) Displays the number of transactions that are: § Started or running § Have INCOMMIT status § Have INROLLBACK status § Cancelled § Completed successfully © 2015 SAP SE or an SAP affiliate company. All rights reserved. Use the Clear INCOMMIT Transactions button to force transaction completion Started INCOMMIT INROLLBACK Cancelled Completed 28
Process Control Buttons and Actions Path: Monitoring → Process Control allows you to manage troubleshooting for all steps or for a single step: § Exception checkbox: if marked, select the Debug button on row to open debug panel § Debug checkbox: switch on/off production of detailed debug information in the debug panel § Active checkbox: activate or deactivate process step © 2015 SAP SE or an SAP affiliate company. All rights reserved. 29
Configuring the Process Control WIndow § Option to configure the sections displayed in the Process Control report © 2015 SAP SE or an SAP affiliate company. All rights reserved. 30
Additional Monitoring Tools
Queue Monitor Path: Monitoring → Queue Monitor § The integration framework uses internal queues for asynchronous scenario step processing § The Queue Monitor displays all existing queues which contain at least one message § Typically this log will be empty, since messages do not stay in the queue for long © 2015 SAP SE or an SAP affiliate company. All rights reserved. 32
Call Monitor Path: Monitoring → Call Monitor § The Call Monitor shows a report of all calls made by transactions, regardless of scenario § You can select the types of calls, for example, email, HTTP, queue, SQL, Void, etc. § In the report you can view and optionally debug call issues including SQL errors © 2015 SAP SE or an SAP affiliate company. All rights reserved. 33
Control Center Path: Tools → Control Center § Control Center cockpit shows overall status of IPO process steps and transaction execution status © 2015 SAP SE or an SAP affiliate company. All rights reserved. 34
Quiz 1 Why would a message be displayed in the filtered section of the message log? Take a moment to decide your answer then advance to the next slide. A. One of the internal process steps ended in an error B. No scenario step has subscribed to the message C. The message threw an exception during IPO step processing D. A search key was set up for the scenario step © 2015 SAP SE or an SAP affiliate company. All rights reserved. 35
Quiz 1 Answer Why would a message be displayed in the filtered section of the message log? A. One of the internal process steps ended in an error B. No scenario step has subscribed to the message (correct) C. The message threw an exception during IPO step processing D. A search key was set up for the scenario step © 2015 SAP SE or an SAP affiliate company. All rights reserved. 36
Quiz 2 What do the three icons in the Actions column of the message log entry allow you to do? Take a moment to decide your answers then advance to the next slide. A. Debug the message B. Open the flow analysis diagram C. Retry the message though step processing D. Open the message XML file E. Clear a transaction with INCOMMIT status F. Print the log message © 2015 SAP SE or an SAP affiliate company. All rights reserved. 37
Quiz 2 Answer What do the three icons in the Actions column of the message log entry allow you to do? A. Debug the message (correct) B. Open the flow analysis diagram C. Retry the message though step processing (correct) D. Open the message XML file (correct) E. Clear a transaction with INCOMMIT status F. Print the log message © 2015 SAP SE or an SAP affiliate company. All rights reserved. 38
Thank You! For more information visit SDN at http: //sdn. sap. com
© 2015 SAP SE 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 SE or an SAP affiliate company. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http: //global 12. sap. com/corporateen/legal/copyright/index. epx for additional trademark information and notices. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company 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. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forwardlooking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions. © 2015 SAP SE or an SAP affiliate company. All rights reserved. 40
- Slides: 40