De Ventas

Monitoring Guide
SAP Applications
for Mobile Business
SAP Mobile Direct
Store Delivery 3.0
Document Version 1.0 February 20, 2008
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 24
F +49/18 05/34 34 20
www.sap.com
Copyright 2008 SAP AG. All rights reserved.
companies. Data contained in this document serves

information purposes only. National product specifications
may vary.
SAP Library document classification: PUBLIC
These materials are subject to change without notice. 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.
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, Outlook, and PowerPoint 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, and Informix are trademarks or
registered trademarks of IBM Corporation in the United States
and/or other countries.
Disclaimer
Some components of this product are based on Java. Any
code change in these components may cause unpredictable and
severe malfunctions and is therefore expressively prohibited,
as is any decompilation of these components.
Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of
the Open Group.
Any Java Source Code delivered with this product is only to

be used by SAPs Support Services and may not be modified
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
or altered in any way.
HTML, XML, XHTML, and W3C are trademarks or registered

trademarks of W3C, World Wide Web Consortium,
Massachusetts Institute of Technology.
Documentation on SAP Service Marketplace
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.
MaxDB is a trademark of MySQL AB, Sweden
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP
NetWeaver, 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
You can find this documentation at

service.sap.com/instguides.
Typographic Conventions
Icons
Type Style
Represents
Icon
Example Text
Words or characters that appear

on the screen. These include
field names, screen titles,
pushbuttons as well as menu
names, paths and options.
Cross-references to other
documentation
Example text
Emphasized words or phrases in

body text, titles of graphics and
tables
EXAMPLE TEXT
Names of elements in the

system. These include report
names, program names,
transaction codes, table names,
and individual key words of a
programming language, when
surrounded by body text, for
example, SELECT and
INCLUDE.
Example text
Screen output. This includes file

and directory names and their
paths, messages, names of
variables and parameters,
source code as well as names of
installation, upgrade and
database tools.
Example text
Exact user entry. These are

words or characters that you
enter in the system exactly as
they appear in the
documentation.
<Example text>
Variable user entry. Pointed

brackets indicate that you
replace these words and
characters with appropriate
entries.
EXAMPLE TEXT
Keys on the keyboard, for

example, function keys (such as
F2) or the ENTER key.
Meaning
Caution
Example
Note
Recommendation
Syntax
Monitoring Guide: SAP Mobile Direct Store Delivery 3.0
Contents
1 Introduction .............................................................................................5
1.1 Scope......................................................................................................................5
1.2 Target Groups........................................................................................................5
1.3 System Requirements...........................................................................................5
2 Monitoring and Verification Procedure .................................................7

2.1 Preliminary Tasks..................................................................................................7
2.2 Procedure.............................................................................................................13
2.2.1 Monitoring Concepts .........................................................................................................13
2.2.2 Business Process Monitoring in DSD Server Landscape ..............................................14
2.2.3 Back-End System Monitoring ...........................................................................................15
2.2.4 Middleware Server Monitoring..........................................................................................17
2.2.5 Client Monitoring ...............................................................................................................19
2.2.6 DSD Administration Console............................................................................................23
3 Further Information ...............................................................................25

3.1 Data Resets ..........................................................................................................25
3.1.1 Reset the Client Database.................................................................................................25
3.1.2 Remove Tour......................................................................................................................25
3.1.3 Resend Tour to Device ......................................................................................................25
3.2 Synchronization Error Recovery........................................................................26

3.2.1 Sending Shipment from Backend to DSD Connector.....................................................26
3.2.2 Sending Shipment from DSD Connector to Middleware ................................................27
3.2.3 Polling from Device ...........................................................................................................27
3.2.4 Download from Middleware to Device .............................................................................27
3.2.5 Upload from the Device to the DSD Connector...............................................................28
3.3 Troubleshooting ..................................................................................................29

3.3.1 Problem Diagnosis ............................................................................................................29
3.3.2 Problem Descriptions........................................................................................................29
3.4 Problem Reporting Procedure...........................................................................39
Appendix A: Sample Output of Data Viewer Tool .................................40
February 20, 2008
1 Introduction
1.1 Scope
This document provides information for efficient monitoring of SAP Mobile Direct Store Delivery (MDSD) 3.0.
It does not include information about installing or configuring the application.
For information about installing the application, see the MDSD 3.0 Installation Guide at SAP
Service Marketplace (service.sap.com/instguides). For information about configuring the
application, see SAP Solution Manager Direct Store Delivery Configuration Guide.
To monitor the application, you should be able to:
Detect errors
Use reliable procedures for handing errors
This document provides procedures for:
Identifying system conditions that can lead to a business process standstill, loss of production, or
inefficient system operations and troubleshooting system problems
Facilitating good system operations practices
1.2 Target Groups
System Administrators
Solution Consultants
Technical Consultants
Support Specialists
We recommend that the target groups consider attending the SAP Direct Store Delivery
(including MDSD) and SAP Mobile Infrastructure trainings.
1.3 System Requirements

To run SAP MDSD 3.0, you need to install the following components:
SAP ERP 6.0 (Enhancement Pack 3) with SAP Direct Store Delivery 3.0
SAP NetWeaver 7.0 AS SP 12 (or above)
SAP Mobile Infrastructure 7.0 SP 12 with IBM DB2 Everyplace 8.2.4
The following graphic shows how the various SAP components work together.
February 20, 2008
Figure 1: MDSD 3.0 System Landscape
February 20, 2008
2 Monitoring and Verification Procedure

2.1 Preliminary Tasks
Before using this guide, ensure that you perform the following preliminary tasks and checks in the system:
a. Complete all the installation and post-installation actions and procedures including customizing
according to the Installation Configuration Checklist below.
b. Ensure that the initial download has been successfully executed.
c.
Apply all the SAP recommendations from SAP Service Sessions and any SAP recommendations
resulting from customer problem messages.
d. Implement all the current SAP Support Packages as and when they become available.
e. Search and apply all the related notes on a specific issue.
Installation Configuration Checklist

No.
Check Category
No.
Check Item
Refer to
Item Content
System Connections
1
Connections of the DSD Backend

with the DSD Connector
Defining Logical System
DSD Configuration Guide
Assigning Client to Logical System
Defining RFC Destination for the DSD

Backend/Connector. Verified RFC
works with correct authorization.
Defining Port in DSD Backend/DSD

Connector
Maintaining Cross-System Company

Codes for Global Organization Units
Defining ISO Codes for Currencies
Defining ISO Codes for Units of

Measurement
Maintaining Distribution Models and

Distribute Views
Defining Inbound Process Codes
10
Defining Outbound Process Codes
11
Maintaining Partner Profiles in the

DSD Backend/DSD Connector
12
Assigning IDoc Type and Message

Type
Connections of the DSD Connector

with the Mobile Infrastructure
Server Component
Defining RFC Destination on the DSD

Connector. Verified RFC works with
correct authorization.
Connections of the Mobile

Infrastructure Server Component
with the DSD Connector
Defining RFC Destination on the

Mobile Infrastructure Server
Component. Verified RFC works with
correct authorization.
Configuring SyncBO DSD in the

Mobile Server Component
Establishing Polling Function on the

Mobile Server Component
February 20, 2008
No.
Check Category
No.
Check Item
Refer to
Item Content
4
Connection of the DSD

Administration Console with the
SAP Web AS and the DSD
Connector
Connection of the DSD Administration

Console with the SAP Web AS and the
DSD Connector
Defining Allowed Route Transaction

Types
Logical System Connectivity
Defining Mobile Engine Servers
Maintaining Destinations of Mobile

Engine Server
Maintaining EDI Port Definitions
Connectivity Objects
Defining Connectivity Objects
Assigning Function Modules to

Assigning Message Types to

Mobile Client Connectivity

5
Upload
DSD Connector Settings
Mapping Rules
1
Defining Function Modules for

Mapping
Defining Mapping Rules
Types Assignments
Assigning Material Types to DSD

Connectivity Material Types
Assigning Document Types to DSD
Connectivity Document Types
Assigning Invoice Document Types as

Criteria for Open Items
Definition of Reasons
Defining Reasons for Differences for

Check-in and Check-out
Defining Reasons for Changing
Deliveries and Orders on the
Connector
Defining Customer Visit Reasons
Administration of Mobile Devices
Defined Group-Specific Roles
Defined Mobile Device Groups
Assigned Group-Specific Roles to

Mobile Device Groups
Administration of Mobile Device

Settings
Defining Global Mobile Device

Settings
Defining Payment Methods
Defining Expense Types
10
11
12
13

Administration of Mobile Device
Settings
February 20, 2008
Definition of General Settings
No.
Check Category
No.
Check Item
Refer to
Item Content
Defining Allowed Payment / Credit
Card Types
Assigning Shipment / Visit Plan Types
to Tour Scenarios
Assigning Delivery Document Types to

Delivery Scenarios
Assigning Sales Document Types to

Order Scenarios
Link Mobile Device to Driver/Vehicle
DSD Implementation Guide (IMG)
Displaying Driver Master Data
DSD Implementation Guide
Displaying Vehicle Master Data
3
4
14
15
Configuration of the DSD

Connector Cockpit
Configuration to Enable Pricing on

the Mobile Device
Configuration of the Pricing Data

Extractor
1
Defining General Settings for the

Pricing Data Extractor
Defining Pricing Procedure
16

the Mobile Device
Setting Pricing Readiness Status for

BAdI
17

the Mobile Device
Enhancing Pricing Selection Criteria

for the Pricing BAdI
18
Configuration of Basic Functions
Activating Direct Store Delivery
Activating Vehicle Space Optimization
19
20
21
Master Data Configuration
Driver Master Data Configuration

1
Defining Drivers License Categories
Creating Number Ranges for

Customer Accounts
Defining Account Groups and Field

Selection for Customers
Assigning Number Ranges to

Customer Account Groups
Specifying Allowed Account Group for

Drivers
Setting Up Partner Determination for

Customer Master
February 20, 2008
Vehicle Master Data / Fleet Objects

Configuration
1
Defining Technical Objects types
Defining Usage Types for Fleet

Objects
Setting View Profiles for Technical

Objects
Maintaining an Equipment Category
Defining Number Ranges
Assigning View Profile and Equipment

Categories to Fleet Object Types
Assigning Means-of-Transportation
Types to Equipment Category /
Vehicle Types
Material Master Data Configuration
No.
Check Category
No.
Check Item
Refer to
Item Content
22
23
24
Visit Control Configuration
Transportation Planning
Configuration
Configuration
Determining Categories for Totals

Fields
Assigning Screen Sequences
Defining Calendar Types
Defining Visit Groups
Defining DSD Groupings
Maintaining Number Ranges for Visit

Plans
Maintaining Number Ranges for Visit

Lists
Defining Visit Plan Types
Specify Allowed Sales Document

Types
Assigning Sales Activity

Types/Outcome to Customer Visit
Status
Route Definition
1
Defining Modes-of-Transport
Defining Shipping Types
Defining Routes and Stages
Route Determination Definition

1
Defining Transportation Zones
Maintaining Country and

Transportation Zones for Shipping
Point
Defining Transportation Groups
Defining Weight Groups
Defining Shipping Conditions
Maintaining Route Determination
Defining Loading Groups
25
Configuration
Maintaining Transportation Relevance
26
Configuration
Defining Shipment Types
27
Configuration
Defining Transportation Planning Point
28
Configuration
Determining Allowed Delivery Types

for Dynamic Transportation Planning
29
Configuration
Determining Capacity Limits for

Dynamic Transportation Planning
30
Configuration
Loading Unit Configuration
Checking Units of Measurement
Defining Permissible Document Types

- Order
Defining Permissible Document Types

- Delivery
Defining Units of Measure and

Tolerances
February 20, 2008
10
No.
Check Category
No.
Check Item
Refer to
Item Content
31
32
33
34
35
36
37
Download / Data Replication

Configuration
Download / Data Replication

Configuration
Output Control
ConfigurationOutput Control for
Visit Lists
Output Control
Visit Lists
Output Control
Visit Lists
Setting Unit of Measure Divisor for

Loading Units
Defining Table for LU Groups for

Material Master
Sending Customer Master Data
Sending Material Master Data
Distributing Material BOM Information
Sending Credit Data (Open Items)
Sending Driver Text Settings
Sending DSD-Specific Customer Data
Data Replication Modification

1
Activating Change Pointers - Generally
Activating Change Pointers for

Message Types
Generating IDocs from Change

Pointers: Defining Variants
Generating IDocs from Change

Pointers: Scheduling Jobs
Scheduling Jobs for Collected IDocs
Output Determination for Visit Lists

1
Maintaining Condition Tables
Maintaining Access Sequences
Maintaining Message Types
Maintaining Message Types for EDI
Maintaining Message Types Used by

ALE Distribution
Maintaining Message Types for

Collective Print Output
Maintaining Message Types for the

Visit List
Maintaining Output Determination

Procedure
Assigning Output Determination

Procedure
Print Output and Download from Visit

List
Define Message Types
Download: Defining Scope of Data

Transfer
Print Output: Determining Messages

for Processing
Output Control Configuration
Output Control
Visit Lists
Output Control
Visit ListsMaintaining Output
February 20, 2008
Output Control for Shipments

1
Maintaining Condition Tables
Maintaining Access Sequences
Maintaining Output Types for EDI
Maintaining Output Types Used for

ALE Distribution
11
No.
Check Category
No.
Check Item
Refer to
Item Content
38
39
Types
Maintaining Output Types for

Collective Print Output
Output Control
Visit ListsAssigning Output types
to Partner Functions
Assigning Output types to Partner

Functions
Output Control
Visit ListsMaintaining Output
Determination Procedure
Maintaining Output Determination

Procedure
Output Control
Visit ListsAssigning Output
Determination Procedure
Assigning Output Determination

Procedure
Output Control
ConfigurationOutput Control
Configuration
Print Output and Download from

Shipment
1
Defining Message Types
Specifying volume of Transmitted

Shipping Data
Print Output: Determining Individual

Messages to be Processed
Valuated Delivery Note
Assigning Shipping Messages and

Billing Types
Basic Function Configuration
Application Log Configuration:

Maintaining General Settings
Application Log Configuration:

Maintaining Treatment of Messages
per Object
Defining Route Transaction Types
Defining Distance Types
Defining Time Types
Defining Payment Methods
Defining Reasons for Differences for

Check-Out and Check-In
Defining Reasons for Changing

Deliveries and Orders
Defining Customer Visit Reasons
10
Maintaining Number Range Intervals
11
Assigning Number Range Intervals
Output Control Configuration

1
40
41
Route Accounting
Route AccountingRoute
Settlement
Route Accounting Settlement

Type Configuration
February 20, 2008
Settlement Office
1
Defining Settlement Office
Setting Determination of Settlement

Office
Defining Settlement Types
Setting Determination of Settlement

Types
Assigning Allowed Settlement Types

to Settlement Office
12
No.
Check Category
No.
Check Item
Refer to
Item Content
Route Accounting Collection
Processing
Maintaining Setting for Automatic

Clearing
Maintaining Settings for Manual

Clearing
Posting Control of Driver Receipts and

Expenditures
Defining Customer Sales Transaction

Types
10
Documenting Controls for Each

Customer Sales Transaction Type
Route Accounting Settlement

Cockpit
11
Maintaining Transaction Screens
12
Activating Transaction Types
Enable Copying Control from the

Mobile Client Invoice to R/3 Billing
Docs
Activating the Copying Routine
Assigning the Copying Routine to Item

Categories
43
Middleware
Installed the DSD Administration

Console
MDSD 3.0 Component Installation

Guide
44
Middleware
Installed SAP MDSD 3.0 SyncBOs

Guide
45
Middleware
Uploaded Client Components

Guide
46
Device
Installed SAP MDSD 3.0

Guide
Route Accounting Final

Settlement/Document Control
42
2.2 Procedure
2.2.1 Monitoring Concepts
Monitoring in the Mobile Direct Store Delivery environment can be divided into the following areas:
Monitoring the end-to-end message flow from the mobile clients to the backend system
Monitoring transactional RFC requests
Downloading objects, log files, queues, and requests
Analyzing errors
The following table lists the MDSD server components and the associated monitoring functions.
Server Component
Associated Monitoring Functions
Mobile Client
Analyze Client Trace File

Perform Sync Service Test
Use Data Viewer Tool
Analyze Pricing Log
Simulate Mobile Client on Desktop
View Downloaded XML
View Uploaded XML
February 20, 2008
13
Server Component
Associated Monitoring Functions
Middleware Server
Queue status (SMQ1)

Queue contents (MEREP_DISP_DQ for download
queues and MEREP_DISP_UQ for upload queues)
Verify RFC Connection to Backend system and
DSD Connector(SM59)
Backend System
Monitor Status of ALE Messages (BD87)

View Contents of DSD Connector Database
Verify RFC Connection between Backend System
and DSD Connector (SM59)
Test Mass Download Function Module (SE37)
DSD Administration Console
Synchronization Status Overview

Application Log
IDOC Process Status
Queue Status (qRFC Monitoring)
View Downloaded XML Document
View Uploaded XML Document
System Log
Dump Analysis
2.2.2 Business Process Monitoring in DSD Server Landscape

The figure below shows the SAP DSD server system landscape and the monitoring interface points on each
server.
February 20, 2008
14
2.2.3 Back-End System Monitoring

The table below shows the transactions for monitoring the Backend System. Certain types of monitoring are
specific to MDSD, some use a combination of MDSD and generic monitoring methods, and others are
generic SAP system performance monitors.
Backend System Monitoring Activities/Functions
Access
Monitoring
Frequency
(Periods and
Events)
View contents of DSD Connector Database
Transaction SE16
On error
MDSD
Administration
Console
Daily
Can be used to track data issues
Data is delivered to the DSD connector from the backend via

IDocs
Monitor Status of ALE Messages
Monitor the IDocs in outbound processing from back-end

system
Monitor the IDocs in inbound processing to the DSD connector
IDocs should be processed automatically
Check for errors
or
Transaction BD87
Verify RFC Connection between Backend System and DSD

Connector
Perform this check first, in case of data synchronization

problems
Verify that the user ID and password are valid for the RFC
connection
Test Mass Download Function Module
On error
SM59
On error
SE37
On error
MDSD
Administration
Console
On Error
Execute the Mass Download Function Module in test mode in

case of data errors
Application Log (DSD connector)
or
Transaction SLG1
View Contents of the DSD Connector Database

The DSD Connector Database contains the data passed to the connector from the backend system via
IDocs. The data is stored in tables, so that the BAPI wrappers for the SyncBOs can retrieve the information
from the DSD Connector system. After you verify that the inbound IDocs have been processed successfully,
you can use the SE16 transaction to verify whether the tables have been updated with the appropriate data.
All the tables are in the /DSD/ME development class; so, you can search for relevant tables within this
development class. The useful tables are listed below.
Table
Description
/DSD/ME_COCI_ITM
Check-Out Check-In Items
February 20, 2008
This table lists the items to be verified within the

Check-Out and Check-In processes. It contains
the material, unit of measure, planned quantity,
and actual quantities by the Tour ID (prefix S
15
Table
Description
followed by shipment number or prefix V followed
by visit list number).
/DSD/ME_COCI_PAY
Check-Out Check-In
Payments
This table lists the payments to be verified within

the Check-Out and Check-In processes. It
contains the payment type and the actual and
planned quantities of the payments.
/DSD/ME_CONTACT
DSD Connector: Contact

Person
This table contains the contact person

information for customers. It includes the
customer number, the contact person number,
and the contact persons contact information.
/DSD/ME_CUST_HD
Customer Data
This table contains the customer data, including

customer number, name, and address.
/DSD/ME_DDR_STAT
DSD Connector: Data

Readiness
This table assigns the current tour with a driver to

a ME-User and an overview of the status of this
assignment. There can be just one assignment
between a driver and a dedicated ME-User.The
DATA STATUS field shows the status of the data
(ready, not ready, and so on).
The TRANDAT STATUS field shows the

status of the shipment (downloaded, ready,
and so on).
The PRCDAT STATUS shows the status of

the pricing data (ready, not ready, and so
on).
/DSD/ME_DEL_HD
Delivery Header Data
This table provides the delivery header data,

along with the Tour_ID ( prefix S followed by
shipment number or prefix V followed by visit list
number), visit ID, and activity ID.
/DSD/ME_DEL_ITM
Delivery Items
This table provides the item level details for the

delivery, corresponding to the deliveries in the
/DSD/ME_DEL_HD table.
/DSD/ME_MAT_HD
Material Data for

Downloading to HH
This table includes the material master data,

including the material number, description and
other attributes.
/DSD/ME_MSG_HD
Message
This table includes messages of documents

related to a tour assigned to the visits, and the
activity levels.
/DSD/ME_OPIM_HD
Open Items
This table contains the details of the customers

open items.
/DSD/ME_ORD_HD
Order Header Data
This table contains the order header data.
/DSD/ME_ORD_ITM
Order Item Data
This table contains the item level detail for orders

corresponding to the entries in the
/DSD/ME_ORD_HD table.
/DSD/ME_TOUR_HD
Tour Header Data
This table contains tour ( prefix S followed by

shipment number or prefix V followed by visit list
number) header data.
/DSD/ME_VISIT_ACT
Activities during the

Customer Visit
This table contains the planned activities for the

tour (that is, delivery, invoice, and payment
collection)
February 20, 2008
16
Table
Description
/DSD/ME_VISIT_HD
Customer Visit Header
This table contains the visit level details

corresponding to the customers to be visited in
accordance with the shipment.
Monitor Status of ALE Message

IDocs are outbound from the backend system and inbound to the DSD connector. The master data IDocs
are all sent together during installation. Change pointers should be set up so that new master data IDocs are
generated on creation/update of customers. Transactional IDocs are sent on completion of shipments.
To monitor the status of ALE Messages, use the DSD Administration Console (Synchronization Monitor
IDoc Process Status) or access the transaction BD87 directly.
Verify RFC Connection Between the Back-End System and the DSD Connector
If there are issues with data synchronization, first, verify the RFC connections. Ensure that the user ID and
password for the connection are valid and that the user has the appropriate authorization to execute the
required transactions. This may not be apparent when testing the connection.
Test Mass Download Function Module

All data for a shipment is collected via the function module /DSD/ME_MS_DOWNLOAD from Function Group
/DSD/ME_MOB_MS_INTERFACE. To view the data that will be converted into a XML document, execute
this function module in transaction SE37 in test mode. You will need to enter the user id, the mobile id or the
shipment id as an import parameter.
You can use this function module if there are data errors, or to verify that the data return is what is expected.
Verify that no errors are returned when executing the function module.
Verify that the expected data is returned.
Application Log
When the IDocs are passed to the DSD connector from the backend system, the DSD connector parses the
IDocs and places the data in the DSD connector tables. Any errors that occur during this process are logged
in the Application Log for the /DSD/ME object.
If the inbound IDoc to the DSD connector has been processed without errors and yet there seem to be
issues with the data in the DSD connector, check the Application Log for errors.
2.2.4 Middleware Server Monitoring

The table below shows the transactions for monitoring the Middleware Server. Certain types of monitoring
are specific to MDSD, some use a combination of MDSD and generic monitoring methods, and others are
generic SAP system performance monitors.
Middleware Server Monitoring Activities/Functions
Access
Monitoring
Frequency
(Periods, Events)
DSD
Administration
Console
On error
Check Inbound and Outbound Queues
or
Transaction SMQ1
February 20, 2008
17
Middleware Server Monitoring Activities/Functions
Access
Monitoring
Frequency
(Periods, Events)
View contents of Queues
MEREP_DISP_DQ
or
On error
The data is shown in XML format
MEREP_DISP_UQ
Verify RFC Connection to Backend system
Perform this check first in case of data synchronization

problems.
Verify that the user ID and password are valid for the RFC
connection.
Verify that the SyncBOs are using the correct RFC

connection.
Verify that the correct RFC Destinations are maintained in

the table MEREP_DSD007 for the mass upload/download
function modules
Verify that the RFC user has the proper authorizations.
SM59
On error

The data to be sent to the device from the backend, and the data to be uploaded from the backend, is first
maintained as a queue on the middleware. A download request from the device checks for availability of a
download queue for the user performing the sync. After a successful download, the download queue is
deleted from the middleware. The queues are prepared with the following naming convention
DSDMI_<Username>_<Queue Identifier>_OUT. E.g. a download queue for user TESTER would be
available with the name DSDMI_TESTER_C_OUT. The possible values of the queue identifier are
C : Implies that the queue is a download queue
B : Implies that the queue is an upload queue
N : Implies that the queue is being prepared, or there have been errors
The details of the queue can be viewed by selecting the queue and choosing Edit Display Selection from
the Menu. The Status column would give more details about the status of the queue.
View Queue Contents

The queue data can be viewed from the middleware using the transaction MEREP_DISP_DQ or
MEREP_DISP_UQ. The download queue can be viewed using the transaction MEREP_DISP_DQ. The
upload queue data can be viewed using the transaction MEREP_DISP_UQ. The download queue is deleted
after the device downloads the queue data. Hence, the download queues can only be viewed before the
devices start the download process. In the case of Upload, the upload queues are deleted after the upload is
executed successfully.
Check Entries in DSD-Specific Tables

You have to maintain entries in the following 3 tables before synchronization can start:
1. MEREP_DSD001 : Maintain the Sync Types here
2. MEREP_DSD002 : Maintain the Sync BOs relevant for the different Sync Types
3. MEREP_DSD007 : Maintain the function modules to be called in the backend/connector
February 20, 2008
18
Check RFC Connection to Back-End System

In case of data synchronization problems, check the RFC connections to your backend system. Verify that
the user ID and password are valid for the RFC connection, and that the SyncBOs are using the correct RFC
connection and that the RFC user has proper authorizations.
2.2.5 Client Monitoring

The table below lists the methods to monitor the client device.
Client Monitoring Activities/Functions
Monitoring
Frequency
Periods and
Events
Analyze Client Trace File: Allows you to see the log generated by the Mobile
Infrastructure client
On error
Perform Sync Service Test: Verifies whether the synchronization service is working
properly
On error
Use Data Viewer Tool: Allows you to view the downloaded SyncBO data on device
On error
Simulate on Desktop: When analyzing a device issue, you can speed up reproduction
and analysis by simulating the same data set on the desktop
On error
Analyze Pricing Log: Allows you to view detailed pricing calculation on the device
On error
View Downloaded XML Document: Allows you to view the XML document
downloaded to the handheld
On error
View Uploaded XML Document: Allows you to view the XML document uploaded to
the backend system
On error
Analyze Client Trace File

The client trace file allows you analyze the log generated by the Mobile Infrastructure client. The default
trace file is 200K. You may increase the file size limit or set the trace file to have no size limit by adding the
following line in the <MIfolder>\settings\MobileEngine.config file:
MobileEngine.Trace.Filesize = <size>
Replace <size> with the number of bytes or with -1 for no limit.
To analyze the trace file, first, search for the text: Synchronization started for user..
Now, the Mobile Infrastructure client attempts to connect to the backend server. The client sends the User
ID, password, and a list of the applications that have been registered for this user.
The installation information, the User ID, and password are sent to the MI server. The password is
validated and the installation information is compared with the user information on the server.
February 20, 2008
19

If the synchronization fails due to the clients inability to make a connection, the trace file indicates this
failure. Two indicators can be used to ascertain this failure as shown in the screenshot below.
The trace file will usually contain a string which clearly indicates that a connection could not be made.
The trace file would show a java exception.
The actual information that is sent to the server in the package.out container is dumped in the trace file so
that the data can be visually confirmed.
The next step is the call to the server to retrieve any data that has been accumulated for the user. This can
be done via the httpPost command. The inbound.sync container is used to transport client information
and retrieve server data.
The local MI registry file is updated with information about any new applications/user information.
February 20, 2008
20

After the registry is updated, processing of the outbound container starts. The container contains either
synchronization data or commands for the client to download applications or device drivers (the actual
application or driver is not brought back in the container). In this example, the client downloads a driver to
the device. The key string in the trace file is APP_INSTALL. When the Mobile Infrastructure client installs an
application, this is one of the commands that will be processed from the outbound.sync container. If an
application has been downloaded but this string can not be found in the trace, this could indicate a problem
on the MI server. This problem can be solved by executing the MEREP_PD transaction. Calling this
transaction in the GUI will solve this problem. For more information, see SAP Note 592284.
The last step is completion of the application registration and dumping of the inbound.sync container.
Perform Sync Service Test

Perform this test to check whether synchronization between the client device and the server is working
properly without having to install the SAP MI Client Component
Follow the below steps in the Mobile Infrastructure middleware system.
1. Execute the transaction:SICF
2. Choose the Hierarchy Type as SERVICE and execute.
3. Go to default_host sap bc MJC mi_host.
4. Right click on mi_host and select the Test Service
5. A IE browser will be launched with a url : http://<server>:<port>/sap/bc/mjc/mi_host?sapclient=<client no> with the test result.
If the test fails, an error message 404 Not Found appears.
Use the Data Viewer Tool

The Data Viewer tool allows you to check all the downloaded SyncBO data on the client device.
To start the tool, perform the following steps.
1. Start the MDSD application on the device.
2. Choose 5-other from the main menu.
3. Choose 7 on the Other menu.
4. Select any SyncBO from the list and choose View. A data file (named Report.txt) of the selected
SyncBO named is generated under the root folder of the device.
5. Open the data file to view the downloaded SyncBO data.
A SyncBO is a structure with a maximum of two layers: the TOP structure and child structures (it is possible
to have multiple child structures on the same layer). For an example of the output of the Data Viewer tool,
see Appendix A: Sample Output of Data Viewer Tool on page 40.
Simulate on Desktop
When analyzing a device issue, you can speed up reproduction and analysis of the issue by simulating the
same data set on the desktop.
February 20, 2008
21
Prerequisite
Install the Mobile Infrastructure client desktop version and download the same version patches, add-ons and
DSD application as on the mobile client. This precondition is valid regardless of whether or not you download
tour data. You can use your own user ID/password for this process.
Procedure
1. Copy the following folders from the mobile client to the desktop version of MI. Before you replace
these folders in the desktop version of MI, you may copy the original folders to another location as a
backup.
- eventListeners
- data
- settings
- sync folder
2. Now, you can reproduce and analyze the device problems by running <MI Installation
Directory on Desktop>/startup.bat.
3. Log on to MI client with the user ID and password from the mobile client device.
Do not synchronize from the desktop simulation.
Analyze Pricing Log

You can check the pricing log that is generated by the DSD Pricing Engine on the client when calculating the
price, by performing the following steps:
1. Maintain the entry : DSD.Pricing.PERFORM_PRICING_ANALYSIS=true in the
MobileEngine.config file in the settings directory of Mobile Infratructure installation.
2. Start the MDSD application on the device.
3. Go to the Invoice detail or Priced Order detail screen.
4. Press 6 on the keyboard.
5. A log file (named report.txt) of the pricing steps and a pricing line item log (named
<NUMBER>.xml is generated under the root folder of the device. You can find the <NUMBER>
under Analysis in the report.txt file.
The two types of pricing logs overview and detail are equivalent to the backend conditions and pricing
analysis screens in order creation. Further, if the Trace option is enabled before the application starts, all the
pricing engine calls made during the application startup to fill the pricing buffer are logged in the trace.txt
file with the SPE: prefix.
View Downloaded XML Document

You can configure the MI client to persist the downloaded XML document into the dsdSyncIn folder of the
root SAP Mobile Infrastructure directory. To enable this, set com.sap.ip.me.dsdSync.SavingInbound=true in the
MobileEngine.config file (available in the settings folder of the root Mi directory). Files will be saved with the
file name InboundData-#.dsdSync, where # corresponds to the number of download synchronizations (for
example, InboundData-1.dsdSync).
To view the contents of the XML document:
1.
Append the suffix .zip to the end of the file name (for example InboundData-1.dsdSync.zip)
2.
Extract the file inside the zip and append .xml to the end of the file name.
3.
Open the XML file in a text editor (WordPad for example) and delete any characters before <?xml
version="1.0" encoding="utf-8"?>.
4.
Save the XML file.
5.
Open the XML file in Internet Explorer or any XML viewer or editor.
February 20, 2008
22
View Uploaded XML Document

Similarly, you can configure the MI client to persist the uploaded XML document into the dsdSyncOut folder
of the root SAP Mobile Infrastructure directory. To enable this, set com.sap.ip.me.dsdSync.SavingOutbound=true in
the MobileEngine.config file (available in the settings folder of the root Mi directory). Files will be saved with
the file name OutboundData-#.dsdSync, where # corresponds to the number of download synchronizations
(for example, OutboundData-1.dsdSync).
To view the contents of the XML document:
1.
Append the suffix .xml to the end of the file name (for example OutboundData-1.dsdSync.xml)
2.
Open the XML file in Internet Explorer or any XML viewer or editor.
2.2.6 DSD Administration Console

While the DSD Administration Console is physically located on the SAP Web AS J2EE engine, it provides
access to transactions on the middleware as well as the backend system. These transactions can also be
accessed in the respective systems with the proper transaction codes. The DSD Administration Console
simply provides a single location to access many of the commonly used transactions associated with the
DSD Business Process; it includes Customizing and other transactions that are not required for monitoring
and troubleshooting.
The table below shows only the transactions related to monitoring and troubleshooting within the DSD
Administration Console.
DSD Administration Console Activities/Functions
Corresponding
Transaction Code
(BE=Backend
MW=Middleware)
Monitoring
Frequency
Periods and
Events
N/A
Daily
Synchronization Monitor
On Error
Application Log (DSD Connector)
SLG1 (BE)
On Error
IDoc Process Status (Monitor Status of ALE Messages)
BD87 (BE)
Daily
On error
Queue Status
SMQ1
Daily
On Error
MEREP_DISP_DQ
On Error
MEREP_DISP_UQ
On Error
System Log
SM21
On Error
Dump Analysis
ST22
On Error
View Messages in the download queues

View Messages in the Upload Queue
Other Tools

This transaction provides an overview of the synchronization status for the mobile client devices. From the
detail screen, you can:
View the synchronization status details, including the download ,upload and reload status of the tour
View/change the tour
Maintain driver
February 20, 2008
23
Maintain vehicle
View IDoc
Remove a tour from a device
Download a tour again to a device
Perform a manual upload
To view the details of the synchronization status for a mobile client device:
1. Log on to the DSD Administration Console.
2. Open the Synchronization Monitor tree in the navigation pane.
3. Start the Sync. Status Overview transaction.
4. Enter the appropriate selection criteria for the mobile client device.
5. Click
(Action) for the appropriate mobile client device to view the detail information.
System Log
The System Log is used to point out and correct errors in your system and its environment. This transaction
is not specific to MDSD.
View Download XML Message

You can view the contents of the downloaded XML Message via this transaction. The contents can only be
viewed while a download queue exists in the middleware. This transaction can be used when you want to
track down possible data issues.
View Upload XML Message

You can view the contents of the uploaded XML Message via this transaction. The contents can only be
viewed while a upload queue exists in the middleware, so it is only available in the case of an upload error.
Dump Analysis
This transaction allows you to administer short dumps. It is not specific to MDSD.
February 20, 2008
24
3 Further Information
3.1 Data Resets
Data can be reset in the following ways:
Reset the Client Database
Remove Tour: The tour can be removed on the DSD Administration Console (in conjunction with the
device reset).
Resend Tour to Device
3.1.1 Reset the Client Database

This functionality allows you to refresh the database on the device as well as the replica database on the MI
server. When you encounter a data issue on the device, you can remove it manually (tour data as well as
master data).
To refresh the data on the device, perform the following steps:
1. From the main menu of the application, choose 5-Other.
2. Choose 4-Sync Admin.
3. Enter the supervisors User ID and password.
4. S elect the Reset button.
5. Select the OK button to confirm.
6. After synchronization, a Reset completed message appears.
3.1.2 Remove Tour

This functionality allows you to remove a shipment and all the related data from the DSD connector table.
When you use this functionality, you must also execute a reset on the device as described in
section 3.1.1 Reset the Client Database.
To remove a tour from the DSD Administration Console, perform the following steps:
1. Log on to the DSD Administration Console.
2. Go to the Sync. Status Overview transaction.
3. Enter the appropriate selection criteria for the device for which the tour should be removed.
4. Select the Start button.
5. Select the
(Action) button for the appropriate device.
6. Select the Remove Tour link at the top of the detail screen.
7. Reset the device as described in section 3.1.1 Reset the Client Database.
3.1.3 Resend Tour to Device

This functionality enables you to again download a shipment that was previously downloaded to a device.
Downloading a tour again to a device sets the status of the downloaded shipment back to R from S and gets
the shipment ready for the new download. Downloading a tour again to a device does not trigger the
download synchronization process; it is triggered from the device.
To download a tour again to a device:
1. Logon to the DSD Administration Console.
February 20, 2008
25

2. Go to the Sync. Status Overview transaction.
3. Enter the appropriate selection criteria for the device for which the tour should be removed.
4. Select the Start button.
5. Select the
(Action) button for the appropriate device.
6. Select the Re-download Tour to Device link at the top of the detail screen.
7. Reset the device as described in section 3.1.1 Reset the Client Database.
3.2 Synchronization Error Recovery

MDSD provides the error messages to the user during the synchronization process. Depending on the error
messages, the user and/or the administrator can check the messages on the mobile device screen and/or
the application log (transaction: SLG1), and also within the Queue Status (transaction: SMQ1).
This section lists the error messages that appear on the mobile client device and describes the procedures
to recover from the errors. Some of the messages are technical messages that are transferred from the MI
server; they describe the error in detail.
3.2.1 Sending Shipment from Backend to DSD Connector

After a new shipment is parsed by the DSD connector, a new entry is created in the /DSD/ME_DDR_STAT
table.
If a shipment is already assigned to the device or if a driver-device assignment does not exist, the status
changes to:
DATA_STATUS:
TRANDAT_STATUS:
PRCDAT_STATUS:
If no shipment is assigned to the device, the new shipment is assigned to the device and the status is set
to:
DATA_STATUS:
TRANDAT_STATUS:
PRCDAT_STATUS:
After this, the Pricing Data Extractor is started to select the pricing data; the status changes to:
DATA_STATUS:
TRANDAT_STATUS:
PRCDAT_STATUS:
If the Pricing Data Extractor ends with an error, the status will change to:
DATA_STATUS:
TRANDAT_STATUS:
PRCDAT_STATUS:
If the Pricing Data Extractor ends successfully, the status changes to:
DATA_STATUS:
TRANDAT_STATUS:
R
S
PRCDAT_STATUS:
The middleware is then notified of the readiness of data, and the queue preparation begins. Once the queue
is prepared, the status changes to the following:
DATA_STATUS:
February 20, 2008
26

TRANDAT_STATUS:
PRCDAT_STATUS:
Error Message
Displayed On
Solution
Planning start date of tour XXX is

empty
Application log
(transaction: SLG1)
Fill the planning start date of the shipment on

the backend system and send it again from
the backend to the DSD connector.
Information of driver XXX is not

complete in DSD Connector
Application log
(transaction: SLG1)
Send the driver master from the backend to

the DSD connector via the customer IDoc.
Then, send the shipment again from the
backend to the DSD connector.
3.2.2 Sending Shipment from DSD Connector to Middleware

The middleware is then notified of the readiness of data, and the queue preparation begins. Once the queue
is prepared, the status changes to the following:
DATA_STATUS:
TRANDAT_STATUS:
PRCDAT_STATUS:
3.2.3 Polling from Device

Error Message
Displayed On
Solution
Polling did not finish successfully.

Please check the connection
between DSD Connector server
and the middleware and try again.
Mobile device screen
Check whether the connection between the

DSD connector server and the middleware
server is established correctly. Trigger the
polling function on the device again.
No data for the driver
Check if the shipment was successfully

sent to the connector, and the middleware
was notified.
Check if the queue is prepared on the
middleware without any errors.
This message is displayed only on the mobile device screen.
3.2.4 Download from Middleware to Device

Error Message
Displayed On
Solution
Download of XXX did not finish

successfully due to unrecoverable
errors. Please check Middleware
Worklist Monitor and/or connector
application log (SLG1)
Check the log of the I-Partial or I-Waiting

message within the MI worklist monitor and
resolve the problems.
Download of tour XXX failed due to

I-Error in MI server; please check
the MI Worklist Monitor
Reset the device by clicking Reset on the

sync screen; then, download the shipment
again as described in section 3.1.3 Resend
Tour to Device.
Middleware
Resolve the I-Error message in the MI

worklist monitor, reset the device, and
download the shipment again.
DSD connector
application log
Sync transaction end SyncBO
February 20, 2008
Resolve the I-Error message in the MI
27
Error Message
validation failed. Please check MI
Worklist Monitor
Displayed On
Solution
worklist monitor, reset the device, and
download the shipment again.
Error during Synchronization.

Please check the MI trace for
details
Mobile Device
Screen
Check the MI Trace for details of the error

Check the data downloaded to the device
3.2.5 Upload from the Device to the DSD Connector

Error Message
Displayed On
Solution
Upload of XXX did not finish

successfully due to unrecoverable
errors. Please check Middleware
Worklist Monitor and/or connector
application log (slg1)
Check the log of the I-Partial or I-Waiting

message in the MI worklist monitor
(transaction MEREP_MON) and resolve the
problem. Manual reprocessing of the
message might solve the problem.
To continue the upload process:
1. Reprocess the pending messages
2. Reprocess the upload from the DSD
connector to the backend via the DSD
Administration Console
Upload of tour XXX failed due to

errors in DSD Connector table,
please check the application log

Middleware
DSD connector
application log
Upload of tour XXX failed due to IError in MI server; please check the
MI Worklist Monitor

Middleware
DSD connector
application log
Sync transaction end SyncBO

validation failed. Please check MI
Worklist Monitor
Correct the data in the DSD connector and

upload the tour manually from the DSD
connector via DSD Administration Console.
If the next shipment is ready in the DSD
connector, it will be downloaded without
interruption. The old shipment with the error
status will remain in the DSD connector for
error recovery; it will not block the next
download and upload.
Correct and reprocess the I-Error message
in the MI worklist monitor, and then upload
the tour manually from the DSD connector
using the DSD Administration Console.
Reprocess the I-Error message in the MI
worklist monitor; when the message is
resolved, the upload from the DSD
connector is triggered automatically.
February 20, 2008
28
3.3 Troubleshooting
This chapter describes problems that can arise in the MDSD environment and the standard procedures for
handling and solving these problems.
3.3.1 Problem Diagnosis

For diagnosing a problem, the first step is to determine the source of the problem. You can use the following
steps to find the source of a problem.
First, verify the system connections:
Verify whether the RFC connections (bi-directional) are working between the MI server and DSD
connector, between the DSD connector and the backend system and between the MI server and the
backend system.
Check the MI server error messages and SLG1 messages to make sure that were no system connection
issues (RFC-related messages) when the problem occurred.
Verify that the RFC connection is maintained in the DSD Customizing Cockpit on the Mobile Engine ID
tab.
If a problem is reported to have occurred on the mobile client (for example, process stopped), check in this
order: Client Middleware.
Client: Check the trace file. Verify that the related data for this process is downloaded correctly.
Connector: Check whether the related data for this process is correct in the Connector Database
tables..
If a problem is reported to occur in the settlement cockpit (for example, incorrect data uploaded), check in
this order: Middleware Client.
Check the connector tables to verify that the uploaded data was correct.
3.3.2 Problem Descriptions

This section describes the problems in the following structure:
Condition: Problem description and symptoms
Analysis: Possible causes of the problem, background information, and so on
Handling: Procedure/s to solve the problem
The table below lists the problem conditions described in this section.
Problem Condition
Go to page
After uploading the first shipment, the sync screen continues to show the S status,
though the next shipment is ready for downloading in the connector
30
Pricing exception, price does not appear, price shows all zeroes, or price differs from
the backend system
31
RFC error
31
Client error: Transport layer exception raised, error writing to server
31
Transport-layer (http) sync exception error message is displayed on the mobile client
device during polling
32
device during download
32
device during upload
32
February 20, 2008
29
Problem Condition
Go to page
Tied empties appear on a normal delivery/order line item screen on the client device
33
A reason code (damage return, normal return, free-of-charge, and so on) does not
work as expected
33
10
No (or incorrect) tied empty explosions for delivery/order on the client device
33
11
Error occurs on creating one-time CPD customer on the client device
34
12
While processing a delivery, the user always gets a Not Enough Inventory error on
the client device
34
13
Materials that are not included in a shipment are not downloaded
34
14
Driver information is not downloaded
35
15
Incorrect language is displayed on the mobile client
35
16
No authorization error appears while uploading to the settlement cockpit
35
17
The error message reply: 178,ERROR,MEREP_01,RFC system error is displayed on

the mobile device during download
35
18
The payment method (Cash, Credit, Check) is not shown in the mobile client device
as expected
36
19
No pricing data on the mobile client during invoice creation
37
20
Document numbering prefix logic is implemented. However, the document

numbering logic (example: last number or prefix) is not updated as expected.
Sync error, Error processing the data on the client; check the MI trace for details
37
21
39
Condition 1
After uploading the first shipment, the sync screen continues to show the S status, though the next shipment
is ready for downloading in the connector.
Analysis
This condition can occur due to problems in the upload of the first shipment.
Handling
1. On the MI server, use the SMQ1 transaction to check errors in the uploaded message queues.
Check the status of the upload queues to see if errors have occurred during the upload.
2. If the status of the upload queue shows SYSFAIL, check for short dumps in the middleware and
the backend/connector. A basic analysis of the reason for the short dump can be obtained by
double-clicking on the status column of the queue details. Detailed analysis should be done on the
middleware, backend or the connector system depending on the reason of the error.
If errors are caused due to Compare Error During Execution of a Simple Transformation, check if
the generation of the function modules have been completed. This error normally occurs if the XML
transformations and function modules on the middleware are not regenerated after changes made to
mapping of Sync BO fields. Regenerate the function modules using the transaction, and reprocess
the upload queue.
If the error occurs in the backend/connector, the data of the queue can be viewed using the
transaction MEREP_DISP_UQ. Detailed analysis should be performed on the backend/connector
based on the upload data viewed in the queue.
3. View the settlement cockpit uploading logs using the SLG1 transaction in the backend. If the log
shown an error, you can fix it manually in the DSD connector tables and trigger the upload manually
to the settlement cockpit again as described in step 3.
February 20, 2008
30

4. If the first shipment is already in settlement cockpit without any error, but you still get an S status on
the device, you can remove the first shipment manually by running the
DSD/ME_RA_PREPARE_DATA function module in test mode (in the DSD connector) with the first
shipment number as the inbound parameter.
Condition 2
Pricing exception, price does not appear, price shows all zeroes, or price differs from the backend system.
Analysis
This condition could indicate errors in the pricing calculation or missing data on the device.
Handling
1. Check the client trace file to for pricing exceptions or warnings just after the initial download.
2. Execute the function module /DSD/PE_MS_DWNLD on the backend for the user, and verify if the
pricing data was downloaded properly.
3. Check whether pricing works as expected on the backend with the customer and materials on the
specific pricing date (for order: delivery date; for invoice: invoice date).
4. Check the device clock. Check the delivery date or invoice date field of the order on the mobile client
by using the Data Viewer. The pricing date affects determination of the backend pricing condition. If
the pricing conditions for the pricing date are not downloaded, pricing can be incorrect.
5. Check the pricing log (both overall and line item detail) on the device. To perform this, you must
have basic knowledge about SAP Pricing Conditions. Compare the pricing overview log with the
backend order condition screen. Compare the item detail log with the backend price analysis screen
by checking each pricing access to find a difference. Check the related master data and the
condition data using the Data Viewer to find out the reason for the access being determined
differently from the backend.
Condition 3
RFC error.
Analysis
This condition could be due to problems with the RFC connections.
Handling
See the Problem Diagnosis section on page 29.
Condition 4
Client error: Transport layer exception raised, error writing to server.
Analysis
This problem is usually related to a connection issue or incorrect settings either on the device side or the
server side. To analyze this problem, consider the following questions:
Is there a fixed test path that can always reproduce the problem?
Is the problem reproducible on the device only or can it be reproduced on the desktop as well?
Is the problem reproducible on other devices, other shipments, and different scenarios?
Since when does this error occur on the system? Were there any changes done on the system from that
time?
Handling
1. Verify whether a restart or a sync solves the problem.
February 20, 2008
31

2. Perform the Sync Service Test to ensure that the Sync Service is working correctly.
3. Check the Java virtual machine version using the JVM cab file name. It must be JVM Crme 3.25.
4. Check the MI release and patch level on the client in the <MIfolder>\buildno.txt file.
5. If you are using Crme as the JVM, make sure that the version should be 3.27.
6. Analyze the client trace file: trace.txt.
Condition 5
Transport-layer (http) sync exception error message is displayed on the mobile client device during polling
Analysis
This condition can occur if the network connection between the MI server and the mobile client device fails.
Handling
Stop polling, restore the connection between the MI server and mobile client device, and then restart polling.
Condition 6
Transport-layer (http) sync exception error message is displayed on the mobile client device during
download.
Analysis
This condition can occur if the network/RFC connection between MI server and mobile client device or
between the MI server and the backend system fails.
Handling
1. On mobile client device, if pricing data is not downloaded but if the Download completed message is
displayed, go to step 2; otherwise, proceed to step 3.
2. Restore the connection between the MI server and mobile client device.
3. On the DSD Administration Console, view the details of the synchronization status by following the
procedure described in the Synchronization Status Overview section.
4. If the status is S, use the MEREP_MON transaction to monitor the SyncBO status on the MI server.
5. If a message is in the O-waiting status, perform the procedure described in section 3.1.3 Resend
Tour to Device.
6. Perform the procedure described in section 3.1.2 Remove Tour.
Condition 7
Transport-layer (http) sync exception error message is displayed on the mobile client device during upload
Analysis
This can occur if the network connection has failed between MI Server and mobile client device.
Handling
1. Restore the connection between the MI server and the mobile client device.
2. On the MI server, use the MEREP_MON transaction to monitor the SyncBO status.
3. If a message is in the O-waiting status, monitor the status of shipment in the DSD Administration
Console by following the procedure described in the Synchronization Status Overview section.
4. If the status is S, restart upload on mobile client device.
5. If the status for the next shipment is R or N, reset the mobile client device.
February 20, 2008
32
Condition 8
Tied empties appear on a normal delivery/order line item screen on the client device.
Analysis
This could be a data or customizing issue.
Handling
1. Check whether you have applied all the related notes regarding tied empties (for example: 742481).
You can find the full list of related note numbers in the MDSD 3.0 Installation Guide or SAP Note
755712 (DSD Central Note).
2. Verify that the UEPOS field of the downloaded delivery/order line items is set to a correct parent item
number (a number other than 0).
3. Verify that the IMP_EMPTY fields of the downloaded delivery/order tied empty line items are marked
correctly as X.
4. Check the MAT_TYPE EMP entry in DSD Customizing Cockpit (Not INV_TYPE EMP entry). This
field must be set to the same value as the empty material type in the backend.
Condition 9
A reason code (damage return, normal return, free-of-charge, and so on) does not work as expected.
Analysis
This condition can occur if the behavior codes of the reason code have not been mapped properly.
Handling
1. In the client Data Viewer, check the DSD_CHCUST SyncBO. Search the reason code and reason
code source (example: CHG_REAS). Check the BEHAVIOR field to see whether the correct
behavior code is downloaded in the reason code.
2. In the DSD Connector Customizing Cockpit (transaction /DSD/ME_CPT), search the reason code
and reason code source (example: CHG_REAS). Check the BEHAVIOR field to see whether the
correct behavior code is mapped to the reason code.
3. Currently the following behavior codes are supported:
0: No special logic, same as leave blank
1: No penalty to customer
2: Damage return
3: Normal return
4: Free of charge goods
7: Sales effective
8: Reload
9: Empty allocation
Condition 10
No (or incorrect) tied empty explosions for delivery/order on the client device.
Analysis
Handling
1. Check whether tied empty line items are downloaded.
February 20, 2008
33

2. Check the MAT_TYPE EMP entry in DSD Customizing Cockpit (Not INV_TYPE EMP entry). This
field must be set to the same value as the empty material type in backend.
Condition 11
Error occurs on creating a one-time CPD customer on the client device.
Analysis
On a device, only one reference customer must be a template for creating other CPD customers. This
problem could be because no (or multiple) CPD reference customers are downloaded to the device.
Handling
1. In the DSD_CUST SyncBO, verify, using the client Data Viewer, that only one SyncBO record exists
with REF_CPD=X.
2. Check the implementation strategy for downloading CPD customer.
Certain DSD deployment projects may choose an automatic approach by implementing a BADI
to send a dummy visit of a CPD reference customer automatically while sending itinerary
IDocs. Verify that a visit is in the /DSD/ME_VISIT_HD table with EXTFLD1=X for this shipment
and the customer of this visit is in the /DSD/ME_CUST_HD DSD connector table with
REF_CPD=X and that UPDFLG is not equal to X.
Condition 12
While processing a delivery, the user always gets a Not Enough Inventory error on the client device.
Analysis
This condition is due to insufficient inventory on the device.
Handling
Perform the following steps:
1. Check whether the user delivered more quantity than planned in previous deliveries resulting in
insufficient inventory should not exist.
2. Check whether the downloaded check-out data for the DSD_COCI SyncBO is correct. This can be
verified via the Data Viewer tool on the device. Initial on-truck inventory is built up by accumulating
downloaded check out items.
Condition 13
Materials that are not in a shipment are downloaded.
Analysis
Any materials to be downloaded must already exist in the DSD Connector tables before the shipment is
downloaded.
Handling
1. Implement BADI: /DSD/IF_EX_ME_DE_TRIGGER_E~SEL_CRI_EXTRA_PROCESS as shown
below:
Clear t_material[]
Select mat_no from /DSD/ME_MAT_HD into lv_material
Move lv_material to ls_material-matnr
Append ls_material to t_material
End select
February 20, 2008
34

2. Ensure that you have sent IDocs for all the materials (including empty materials) that you want to
download to the mobile client, and verify that they exist in the /DSD/ME_MAT_HD connector table.
Condition 14
Driver information is not downloaded.
Analysis
This condition can occur if the customer master for the driver has not been sent when the shipment is
downloaded.
Handling
1. Drivers are considered as customers in the customer master. Send the customer master IDoc using
the BD12 transaction and make sure that it is available in the /DSD/ME_CUST_HD connector table.
2. Send the shipment IDoc, and verify that the driver information is in the /DSD/ME_TOUR_HD tour
header table in the DSD connector.
Condition 15
Incorrect language is displayed on the mobile client.
Analysis
This condition can occur if language entries in the customizing cockpit have not been customized correctly.
The DLANG entry determines the language used in the client user interface; the LANG1 entry determines
the first language used in retrieving texts for downloaded data (example: descriptions of customers and
materials).
Handling
1. Using the Client Data Viewer tool, check the DLANG and LANG1 records in the DSD_CHCUST
SyncBO.
DLANG should be customized to ISO code (example: EN for English, DE for German, and ES
for Spanish).
LANG1 should be customized to SAP code (example: E for English, D for German, and S for
Spanish).
2. Check the DLANG and LANG1 entries in the customizing cockpit (transaction: /DSD/ME_CPT).
Condition 16
No authorization error appears while uploading to the settlement cockpit.
Analysis
This condition can occur if the user for the connectorbackend RFC connection does not have the
necessary authorization to run the /DSD/ME_RA_PREPARE_DATA upload function module.
Handling
1. Log on with the RFC connection user.
2. Run /DSD/ME_RA_PREPARE_DATA, manually.
3. Verify whether the RFC connection user has appropriate authorization to run the function module.
Condition 17
The reply: 178,ERROR,MEREP_01,RFC system error message is displayed on the mobile device during
download or upload.
February 20, 2008
35
Analysis
This condition can occur if the network/RFC connection between the MI server and the DSD connector or
between the backend system and the DSD connector fails.
Handling
1. Restore the connection between the MI server and the DSD connector or between the backend
system and the DSD connector.
2. Restart the download/upload process on the mobile device.
Condition 18
The payment method (Cash, Credit, or Check) is not shown in the mobile client device as expected.
Analysis
Handling
1. Using the client Data Viwer tool, verify that the DSD_CUST SyncBo that is sent to the mobile client
device contains the correct value for the PYMT_METHOD attribute in the middleware.
For example, to allow a customer to pay only cash, set the PYMT-METHOD attribute to 1).
February 20, 2008
36
PYMT-METHOD
Credit
Check
Cash
Bank Transfer
1
2
3
x
x
x
6
F
2. In the /DSD/ME_CUST_HD table of the DSD connector, verify, using the SE16 transaction code,
whether the setting is as expected.
Condition 19
No pricing data on the mobile client during invoice creation.
Analysis
This is most likely a data or customizing issue.
Handling
1. Verify that the PSTART_DATE field is filled in the /DSD/ME_TOUR_HD table of the DSD connector,
using the SE16 transaction.
2. The material UOM used in documents must exist in the physical unit conversion table. If the table is
empty, check the corresponding USE_ISOCODE setting.
Condition 20
A document numbering prefix logic is implemented; but, the logic (example: last number or prefix) is not
updated as expected.
Analysis
This can occur if the BADI implementation (/DSD/IF_EX_ME_BAPI method DOCNM_GET_PREFIX) is not
implemented correctly, causing a conflict between the get-list BAPI wrapper (/DSD/ME_GL_NUMBERING)
and the get-detail BAPI wrapper (/DSD/ME_GD_NUMBERING).
Handling
1. Unit test /DSD/ME_GL_NUMBERING using the SE37 transaction.
a. Enter the ME user in the I_MEUSER field.
b. Enter the mobile ID in I_MEMBLID field.
c. Leave the I_DOCTYPE field empty.
2. Unit test /DSD/ME_GD_NUMBERING using the SE37 transaction.
a. Enter the ME user in the I_MEUSER field.
b. Enter the mobile ID in I_MEMBLID field.
c. Enter D, O, I and C (separately) in the I_DOCTYPE field.
3. Compare the results of steps 1 and 2. If there is a conflict, the BADI implementation
(/DSD/IF_EX_ME_BAPI method DOCNM_GET_PREFIX) needs to be corrected.
February 20, 2008
37
Condition 21
Sync error
Error processing the data on the client; check the MI trace for details
Analysis
This can occur when you implement a BADI on the backend system. The synchronization keys are
generated in the middleware, so even though the mass download function module returns all data without
errors it is possible for duplicate keys to be generated by the middleware.
To determine if this is the cause of the error, turn the trace level to All and download the shipment again. If
you see an SQL exception, follow the handling steps below.
Handling
1. Examine the trace file, youll see something similar to the following:
(0001310689,0001121644,'0000101540','0000000157','','FRANCIS SOEHNLEIN=AP','','','',5)
[20060621 13:50:38:906] E [MI/Persistence
] java.sql.SQLException: [SQLState:23505, error code:-803]
java.sql.SQLException: [SQLState:23505, error code:-803]
at com.ibm.db2e.jdbc.DB2eError.<init>(DB2eError.java:77)
at com.ibm.db2e.jdbc.DB2eStatement.executeSql(DB2eStatement.java:270)
at com.ibm.db2e.jdbc.DB2eStatement.executeUpdate(DB2eStatement.java:313)
at com.sap.ip.me.persist.jdbc.IPersistenceWriterImpl.execute(IPersistenceWriterImpl.java:228)
at com.sap.ip.me.persist.jdbc.IPersistenceWriterImpl.end(IPersistenceWriterImpl.java:119)
at com.sap.ip.me.smartsync.syncIn.SmartSyncDataImporter.endElement(SmartSyncDataImporter.java:292)
at com.sap.ip.me.xmlParser.MIXMLParser$ElementParser.parse(MIXMLParser.java:638)
at com.sap.ip.me.xmlParser.MIXMLParser.parse(MIXMLParser.java:215)
at com.sap.ip.me.smartsync.syncIn.SmartSyncDataImporter.importDeltas(SmartSyncDataImporter.java:259)
at com.sap.ip.me.smartsync.syncIn.SyncInRuntimeImpl.importDeltas(SyncInRuntimeImpl.java:142)
at com.sap.ip.me.smartsync.core.SmartSyncRuntimeImpl.importDeltas(SmartSyncRuntimeImpl.java:743)
at com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager.importDeltas(SmartSyncRuntimeManager.java:242)
at com.sap.ip.me.dsd.DSDSyncManagerImpl.processInboundMessage(DSDSyncManagerImpl.java:1387)
at com.sap.ip.me.dsd.DSDSyncManagerImpl.processInboundMessages(DSDSyncManagerImpl.java:1574)
at com.sap.ip.me.dsd.DSDSyncManagerImpl.downloadData(DSDSyncManagerImpl.java:1737)
at com.sap.dsd.buslogic.sync.SyncManagerNewImpl$SyncThread.poll(Unknown Source)
at com.sap.dsd.buslogic.sync.SyncManagerNewImpl$SyncThread.run(Unknown Source)
[20060621 13:50:38:906] E [MI/Persistence
] char processor: - error code: -803 SQL state: 23505 Message:
2. The above message indicates that the failure occurred at sync key 0001310689.
3. Extract the XML document as described in View Downloaded XML Document.
4. Search for the duplicate sync key 0001310689 in the XML document.
February 20, 2008
38
5. As you can see in the above example, the sync key 0001310689 is displayed twice.
6. Review the BADI implementation to remove duplicate entries.
3.4 Problem Reporting Procedure

If you encounter an issue that is not covered in this guide and it appears to be a client-related issue, include
the following information when you create an OSS message.
The Mobile ID of the device
The tour (shipment) number downloaded to the device
Copy the complete MI25 (on a device) or the SAP Mobile Infrastructure (on a desktop) folder
Copy the jscp.out file in the root directory (if you are using a device)
Username and password to log on to the client
Username and password to log on to each system
Problem description and reproducing steps
Ensure that the connections between the middleware, DSD Connector, and backend systems
are functioning properly.
February 20, 2008
39
Appendix A: Sample Output of Data Viewer Tool

This appendix includes a sample output of the Data Viewer tool, which allows you to check all the
downloaded SyncBO data on the client device. For more information about using the Data Viewer tool, see
the Data Viewer section on page 21.
A SyncBO is a structure with a maximum of two layers: the TOP structure and child structures (it is possible
to have multiple child structures on the same layer). The sample below is the data of the DSD_DELIV
delivery SyncBO. The TOP structure is the delivery header. It has one child structure: 010, the delivery item.
The output shows three DSD_DELIV SyncBO records, followed by the contents of each SyncBO (TOP
record, followed by the 010 structure; there are about 30 line items each). For each TOP or 010 structure,
the data is displayed as field name followed by value.
The sample included here is only intended to help you understand the structure and format of
the output; so, it shows only the first few line items of the output.
DSD_DELIV
SyncBO instances:3
[TOP]
State: G
SYNC_KEY: 0001886671 TOUR_ID: S0000004806
VISIT_ID: 000003 ACTI_ID: 000001
DELV_NO: 0080008492 DOCTYP: ZLF
CUST_NO: CP_KON1003 HH_CREATE:
DELV_PRIO: 00 DELV_DATE: NULL
PO_NO: 20050317 DAT: NULL
TIME: 12:00:00 STATUS: 3
CANCEL: CAN_REAS:
MOD: INVOICED:
TOT_AMT: 0.0000 OFFICIAL_DELV_NO: 0080008492
CURRCY: EXTFLD1:
EXTFLD2: EXTFLD3:
BSTDK: NULLPLANT:
BE_DELIVERY: 0080008492
Child SyncBOs
[ITEMs]
010 instances: 30
SYNC_KEY: 0001886699 DELV_NO: 0080008492
ITM_NO: 000280 TOUR_ID: S0000004806
PSTYV: UEPOS: 000270
IMP_EMPTY: X RTN_FLAG:
HH_CREATE: MOD:
CHG_REAS: MAT_NO: MDSD_90001
MAT_NO_R (Related: DSD_MAT): 0001647882 [Parent exists]PLANT_CODE: 0001
STORAGE_LOC: DPLN_QTY: 1.000
February 20, 2008
40

DPLN_UOM: ST DACT_QTY: 1.000
DACT_UOM: ST SCALE_QTY: 1.000
BILL_QTY: 1.000 BILLING_FLAG: X
PROMO_NO: NET_PRICE: 0.0000
EXT_ITEM_VALUE: 0.0000 CURRCY:
CONDTYPE: TAX: 0.0000
EXTFLD1: EXTFLD2:
EXTFLD3: BATCH:
BWTAR: PLANT:
SPEC_RETURN: TAX_RATE: 0.00
SYNC_KEY: 0001886698 DELV_NO: 0080008492
ITM_NO: 000270 TOUR_ID: S0000004806
IMP_EMPTY: RTN_FLAG:
HH_CREATE: MOD:
STORAGE_LOC: D001 DPLN_QTY: 1.000
EXTFLD1: EXTFLD2:
EXTFLD3: BATCH:
BWTAR: PLANT:
SYNC_KEY: 0001886679 DELV_NO: 0080008492
ITM_NO: 000080 TOUR_ID: S0000004806
IMP_EMPTY: X RTN_FLAG:
HH_CREATE: MOD:
STORAGE_LOC: DPLN_QTY: 1.000
EXTFLD1: EXTFLD2:
EXTFLD3: BATCH:
BWTAR: PLANT:
February 20, 2008
41

De Ventas

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

De Ventas

Diunggah oleh

Hak Cipta:

Format Tersedia

Monitoring Guide

Document Version 1.0 February 20, 2008

Copyright 2008 SAP AG. All rights reserved.

companies. Data contained in this document serves

SAP Library document classification: PUBLIC

These materials are subject to change without notice. These

No part of this publication may be reproduced or transmitted in

Oracle is a registered trademark of Oracle Corporation.

Any Java Source Code delivered with this product is only to

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

or altered in any way.

HTML, XML, XHTML, and W3C are trademarks or registered

Documentation on SAP Service Marketplace

Java is a registered trademark of Sun Microsystems, Inc.

You can find this documentation at

Words or characters that appear

Emphasized words or phrases in

Names of elements in the

Screen output. This includes file

Exact user entry. These are

Variable user entry. Pointed

Keys on the keyboard, for

Monitoring Guide: SAP Mobile Direct Store Delivery 3.0

2 Monitoring and Verification Procedure .................................................7

3 Further Information ...............................................................................25

3.2 Synchronization Error Recovery........................................................................26

3.3 Troubleshooting ..................................................................................................29

3.4 Problem Reporting Procedure...........................................................................39

Appendix A: Sample Output of Data Viewer Tool .................................40

February 20, 2008

Monitoring Guide: SAP Mobile Direct Store Delivery 3.0

Use reliable procedures for handing errors

This document provides procedures for:

Facilitating good system operations practices

1.2 Target Groups

1.3 System Requirements

SAP NetWeaver 7.0 AS SP 12 (or above)

SAP Mobile Infrastructure 7.0 SP 12 with IBM DB2 Everyplace 8.2.4

February 20, 2008

Monitoring Guide: SAP Mobile Direct Store Delivery 3.0

Figure 1: MDSD 3.0 System Landscape

February 20, 2008

Monitoring Guide: SAP Mobile Direct Store Delivery 3.0

2 Monitoring and Verification Procedure

Installation Configuration Checklist

Connections of the DSD Backend

Defining Logical System

DSD Configuration Guide

Assigning Client to Logical System

DSD Configuration Guide

Defining RFC Destination for the DSD

DSD Configuration Guide

Defining Port in DSD Backend/DSD

DSD Configuration Guide

Maintaining Cross-System Company

DSD Configuration Guide

Defining ISO Codes for Currencies

DSD Configuration Guide

Defining ISO Codes for Units of

DSD Configuration Guide

Maintaining Distribution Models and

DSD Configuration Guide

Defining Inbound Process Codes