oap 3_17 user guide rev b

Object Analysis ProgramUser guide

flexible solution for accurate and consistent copying of data

Object Analysis Program — User guide

ii

OAP version 3.17

Document revision: b

July 2010

Information in this document is subject to change without notice. Companies, names, and data used in

examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or

transmitted in any form or by any means, whether electronic or mechanical, or for any purpose, without the

express written permission of EPI-USE Systems Limited, 4th Floor, Harbour Centre, PO Box 613, Grand

Cayman, Cayman Islands.

© 2002 EPI-USE Systems Limited and its related entities, herein referred to as EPI-USE. All rights reserved.

EPI-USE and Data Sync Manager are either registered trademarks or trademarks of EPI-USE in the United

States and/or other countries.

EPI-USE may have patents or pending patent applications, trademarks, copyrights, or other intellectual

property rights covering subject matter in this document. The furnishing of this document does not give you

any license to these patents, trademarks, copyrights, or other intellectual property rights except as expressly

provided in any written license agreement from EPI-USE.

Acrobat is a trademark of Adobe Systems Incorporated and may be registered in various jurisdictions. Excel,

Windows and Word are trademarks of Microsoft Corporation. The following are trademarks or registered

trademarks of SAP AG: ABAP/4, R/2, R/3 and the word SAP. The SAP logo and all other SAP products,

services, logos, or brand names that may be included herein are also trademarks or registered trademarks of

SAP AG.

Text and artwork copyright © 2002 – 2010 by EPI-USE. All rights reserved.

Other products, services, logos, brand names and company names mentioned herein may be trademarks or

registered trademarks of their respective owners.


Contents

iii

Contents Contents .......................................................................................................................................................... iii 1. Introduction ..........................................................................................................................................1

1.1. Welcome .........................................................................................................................................1 1.2. Product description..........................................................................................................................1 1.3. About the manual ............................................................................................................................1 1.4. Icons used in this manual................................................................................................................1

2. Downloading the OAP transport ..........................................................................................................2 3. Importing the transport ........................................................................................................................4

3.1. File-name conventions ....................................................................................................................4 3.2. Copy the transport to the R/3 server ...............................................................................................4

3.2.1. WinNT .........................................................................................................................................4 3.2.2. UNIX............................................................................................................................................5

3.3. Import procedure using the STMS transaction ...............................................................................5 3.3.1. Import transports.........................................................................................................................5 3.3.2. View Transport Log.....................................................................................................................6

3.4. Import procedure using the command line......................................................................................7 3.4.1. WinNT .........................................................................................................................................7 3.4.2. UNIX............................................................................................................................................8

4. Execution instructions..........................................................................................................................9 4.1. Step 1: Start OAP............................................................................................................................9 4.2. Step 2: Schedule an OAP run .........................................................................................................9 4.3. Step 3: Download the OAP result .................................................................................................10 4.4. Step 4: Send the results to EPI-USE Labs....................................................................................10

5. Advanced Options .............................................................................................................................11 5.1. Schedule OAP run: Advanced options..........................................................................................11 5.2. Completed OAP runs: Advanced options......................................................................................12

6. Product support information ..............................................................................................................13 6.1. Registering an account..................................................................................................................13 6.2. Submitting a ticket .........................................................................................................................14 6.3. Additional EPI-USE Labs products ...............................................................................................14 6.4. Contacting us ................................................................................................................................14


1

Introduction

1. Introduction

1.1. Welcome Welcome to the Object Analysis Program, a product developed by EPI-USE Labs to be used in conjunction

with Data Sync Manager. The OAP is valid for ERP, SRM, CRM, and GTS environments.

1.2. Product description The Object Analysis Program (OAP) has been developed to retrieve and analyze application tables on your

SAP® system in order to determine which of your business objects are supported by Data Sync Manager,

and which tables that contain data are not linked to any supported objects.

This information allows for a proactive technical-gap analysis that determines whether there are objects that

we do not yet support. The results assist EPI-USE Labs to position the various products in the suite, and to

identify requirements during implementation, such as customer-specific enhancements.

No actual business data is accessed by the OAP. The downloaded results are stored as a Comma-

Separated-Values (CSV) file, and can be viewed using standard spreadsheet viewers.

1.3. About the manual This manual provides you with the knowledge to install and configure the product successfully onto your

SAP system.

Section 1 – Introduction

Section 2 – Downloading the OAP transport

Section 3 – Importing the transport

Section 4 – Execution instructions

Section 5 – Advanced options

Section 6 – Product support information

1.4. Icons used in this manual

This important information will help you use this product better.

It is essential that you implement the given instructions.

Follow the systematic instructions to complete the process.


Downloading the OAP transport

2

2. Downloading the OAP transport The OAP transports are available on the EPI-USE Labs Support Web site: http://support.epiuse.com

1. Go to Downloads.

2. Using the tree in the left-hand panel under Support Downloads, open the folders:

Data Sync Manager 3 > DSM 3.1x.

3. Select the relevant DSM 3.16 folder according to whether you have ERP, SRM or CRM.

For ERP:

o Select the relevant ERP version

o Download the OAP transport:

http://support.epiuse.com/


Downloading the OAP transport

3

For SRM:

o Go to the relevant SRM version

o Download the Object Analysis Program transport:

For CRM (similar to SRM above):

o Go to the relevant CRM version

o Download the Object Analysis Program transport.

For GTS (similar to SRM above):

o Go to the relevant GTS version

o Download the Object Analysis Program transport.


Importing the transport

4

3. Importing the transport

This section describes how to copy and import the client-independent transport on Windows NT and UNIX,

and the transaction codes. Please note that the recommended method of installation is to make use of the

STMS transaction.

3.1. File-name conventions The OAP product is shipped as one zip file. The zip file comprises:

one cofile: K<TP-number>.<SID>

one data file: R<TP-number>.<SID>

The zip file contains the product software transport, with the file-name convention as follows:

<PRODUCT NAME><VERSION>_<SAP RELEASE>.zip

An example of this convention for OAP would be:

OAP100_47x110.zip (Product Software transport)

3.2. Copy the transport to the R/3 server Assume you want to copy the following transport: <SID>K<TP-number>.

3.2.1. WinNT

Since a transport consists of 2 files (a Data and a Control file), both need to be copied to the server:

C:\temp\K<TP-number>.<SID> (cofile)

C:\temp\R<TP-number>.<SID> (datafile)

Step 1 Extract the transport files from the zip file to the c:\temp directory.

Step 2 Open Windows Explorer, and go to ‘c:\temp’.

Step 3 Select K<TP-NUMBER>.<SID>, select copy from the ‘Edit’ menu.

Step 4 Open a new Windows Explorer window, and go to

\\SAPTRANSHOST\sapmnt\trans\cofiles.

Step 5 Select Paste from the Edit menu.

Step 6 Go back to the first Windows Explorer window.

Step 7 Select R<TP_NUMBER>.<SID>, select Copy from the Edit menu.

Step 8 Go to \\SAPTRANSHOST\sapmnt\trans\data.

Step 9 Select Paste from the Edit menu.

Result The transports will now have been copied onto the R/3 server.



5

3.2.2. UNIX

The UNIX method of copying transports to the server is done via FTP (File Transfer

Protocol).

Step 1 Extract the transport from the zip file to c:\temp

Step 2 Go to Start Menu → RUN → Type in cmd.

Step 3 Change the directory to the c:\temp directory.

Step 4 Type in: ftp <name of R/3 server>.

Step 5 A popup screen will then appear. Type in your user name and password.

Step 6 The ftp> prompt will then appear.

Step 7 At the ftp prompt, type in the following command: ftp>mode bin, and

press Enter. This changes the File Transfer mode from text mode to binary

mode.

Step 8 To copy the cofiles, type the following command and press Enter: ftp>put

K9<TP-number>.<SID> /usr/sap/trans/cofiles

Step 9 To copy the data files, type the following command and press Enter:

ftp>put R9<TP-number>.<SID> /usr/sap/trans/data

Result The transports will now have been copied onto the R/3 server.

3.3. Import procedure using the STMS transaction

3.3.1. Import transports

Step 1 Log onto the SAP system and go to the Transport Management System

(transaction STMS).

Step 2 Click on the IMPORT OVERVIEW button (F5). This will give the list of

import buffers.

Step 3 Double click on the chosen system to import the transport.

Step 4 Select [EXTRAS] menu → OTHER REQUESTS → ADD.

Step 5 Type in the name of the transport, e.g. <SID>K<TP-number>

Step 6 Click on ‘Continue’ , which will add the transport to the buffer.

Step 7 Find the transport that was added to the buffer and select it.



6

Step 8 Go to [REQUEST] menu →IMPORT. This will open a pop-up screen

where you can fill in the client number.

Step 9 Fill in the client number

Step 10 Go to the Options tab and select the following Import Options:

Import transport request again

Overwrite originals

Overwrite objects in unconfirmed repairs

Step 11 Click on ‘Continue’.

Step 12 The transports will now have been imported onto the R/3 server.

3.3.2. View Transport Log

Click on ‘Logs’ button (Cntrl F4). This will display a tree view of the steps involved in the

import.

Next to each step is a return code to indicate whether any errors occurred or not.

Double click on the return code to view the details of each step.



7

3.4. Import procedure using the command line

3.4.1. WinNT

Adding the Transports to the Buffer

Step 1 Change to the following directory:

\\SAPTRANSHOST\sapmnt\trans\bin

Step 2 To add the transports to the buffer, type in the following command line:

tp addtobuffer <SID>K9<TP-number> <CUSTSID>

Where: <SID> is the system ID where transports were created

<CUSTSID> is the customer system ID

Result The transports will now have been added to the buffer.

Importing the Transports onto the SAP System

Step 1 To import the transports onto the SAP system, type in the following

command:

tp import <SID>K9<TP-number> <CUSTSID> client= <CLNT> U126

Where: <CLNT> is the name of the SAP Client

U126 - U = Unconditional code

1 = Import transport request again.

2 = Overwrite originals

6 = Overwrite objects in unconfirmed pairs

Result The transports will now have been imported onto the SAP system.

View Transport Log

Go to the directory: \usr\sap\trans\log

View the list of the text files <SID>K9<TP-number>.<SID>



8

3.4.2. UNIX

Adding the Transports to the Buffer

Step 1 Logon to the following SAP system: SAPTRANSHOST with the user

<SID>adm.

Step 2 Change the directory to the following: cd /usr/sap/trans/bin.

Step 3 To add the transports to buffer, type in the following command:

tp addtobuffer <SID>K9<TP-number> <CUSTSID>

Where: <SID> is the system ID where transports were created

<CUSTSID> is the customer system ID

Result The transports will now have been added to the buffer.

Importing the Transports onto the SAP System

Step 1

Go to the directory: cd /usr/sap/trans/bin

Step 2 To import the transports onto the SAP system, type in the following

command:

tp import <SID>K9<TP-number> <CUSTSID> client= <CLNT> U126

Where: <CLNT> - is the name of the SAP Client

U126 - U = Unconditional code

1 = Import transport request again.

2 = Overwrite originals

6 = Overwrite objects in unconfirmed pairs

Result The transports will now have been imported onto the SAP system.

View Transport Log

Go to the directory: /usr/sap/trans/log

View the list of the text files <SID>K9<TP-number>.<SID>


9

. Use the ’Schedule run’ button to open the standard SAP scheduling screens, where you can schedule

. After the job has been scheduled, a status message will be displayed at the bottom of the screen,

Execution instructions

4. Execution instructions The OAP program will run in the background, because of the amount of processing and time required for executing

the program. To schedule the program to execute, follow these steps:

4.1. Step 1: Start OAP The Object Analysis Program’s transaction code is /USE/OAP.

Type /n/use/oap in the command box. The following screen will appear.

4.2. Step 2: Schedule an OAP run 1. Enter the name of your company in the input field provided.

2

the OAP run (background processing is forced).

3

confirming that the job was scheduled successfully.


10

Execution instructions

4. Once the job has run, you will be prompted to download the result.

4.3. Step 3: Download the OAP result 1. Select the completed OAP run from the ‘Completed runs’ list box.

When multiple Object Analysis results exist, the latest Object Analysis run will be the default

selection after refreshing.

2. Use the ’Download results’ button to save the file containing the Object Analysis results to your local

computer. A ‘Save as’ dialog box will allow you to select the location you prefer.

3. Once the download is complete, the status message at the bottom of the page will display the total

number of bytes that have been transferred.

On ERP version 4.6C the message differs: ‘Download successfully completed’.

If you wish to review the information of the OAP, open the file using a spreadsheet program that

can open comma-separated value files, such as Microsoft Excel, OpenOffice.org Calc or StarOf

Calc.

fice

Please do not edit the downloaded CSV file or save it as any other file type before sending it to EPI-

USE Labs.

4.4. Step 4: Send the results to EPI-USE Labs Attach the downloaded Object Analysis results file to an email (or preferably to a ticket, if you are already a

customer) and send it to EPI-USE Labs or the EPI-USE partner for analysis.


Advanced options

11

5. Advanced Options You can access the advanced options of the ‘Schedule OAP run’ and ‘Completed OAP runs’ sections

by clicking on the ‘Advanced options’ buttons in the individual sections.

5.1. Schedule OAP run: Advanced options This ‘Advanced options’ field should be ignored for standard OAP runs.

Please do not change these options unless EPI-USE Labs requests it. Changing these will affect

the results of the OAP run, which might misrepresent your system implementation details.

If requested to do so, select the Analysis type from the dropdown. The analysis types are:

Complete Analysis: Determine the Business Object coverage of DSM Object Sync and DSM Client

Sync.

Simple Database Analysis: Determine the record count for all tables on the system.


Advanced options

12

If so instructed, select the tables to be included in the analysis. This ‘Table selection’ function may be used

to exclude a specific set of tables if there is a known issue with them on your SAP system. These issues

might cause long OAP execution times or prevent the program from running correctly.

5.2. Completed OAP runs: Advanced options

The ‘Scheduled runs’ function displays all scheduled, current and completed runs, using SAP’s ‘Job overview’ function.

The ‘Delete Results’ function permanently deletes all the results stored in the OAP results database.


13

13

Product support information

6. Product support information

duct support information

6. Product support information EPI-USE Labs provides customers with support through our Support Portal for almost 24 hours per working

day: from Monday 8am Singapore time (Sunday 8pm EST) through to Friday 5pm PDT, excluding regional

public holidays. However, tickets can be logged 24/7.

EPI-USE Labs provides customers with support through our Support Portal for almost 24 hours per working

day: from Monday 8am Singapore time (Sunday 8pm EST) through to Friday 5pm PDT, excluding regional

public holidays. However, tickets can be logged 24/7.

You can enter the Support Portal from our website: You can enter the Support Portal from our website:

www.epiuselabs.comwww.epiuselabs.com

or directly via

http://support.epiuse.com

6.1. Registering an account If this is the first time you are accessing the EPI-USE Labs Support Portal, you will need to register and

obtain an account. This will enable you to communicate with the EPI-USE Labs Support team.

Request an account by selecting the ‘Request a new Account’ button and complete all the required fields.

This request/information will be sent to EPI-USE Labs Support who will register your account within a few

minutes to a few hours (excluding weekends and holidays). You will then receive an email notification

containing your login details for access to the Support website.

Once you have logged in, you can download the latest releases for upgrades, download related user

documentation or submit a ticket from the home page, simply by clicking on the appropriate link.

http://www.epiuselabs.com/

http://support.epiuse.com/


14

Product support information

6.2. Submitting a ticket When submitting a ticket, you will be required to provide the following information:

1. The version of DSM you are using, e.g. version 3.16

2. The update level of DSM (if applicable), e.g. update 4

3. The SAP R/3 release you are on, e.g. ECC6;

4. The operating system being used; and

5. A short but detailed description of the problem, including screen prints and the resulting error

message or unusual output. If you wish to send more than one attachment, please zip them into

one file and then attach the zip file.

When you have submitted the requested details, the system will issue a ticket number, display it in the web

browser, and return an email message to you with the ticket number, acknowledging the problem. An EPI-

USE Labs Support representative will be notified by e-mail and begin to assist with a solution. Keep your

ticket number and use it in all correspondence as it allows you instant access to the status of or feedback

related to your question or problem.

Tickets are usually responded to within a few hours to 24 hours, though you can specify the urgency of a

ticket by selecting the applicable priority.

6.3. Additional EPI-USE Labs products Additional SAP-enhancing products in the EPI-USE Labs range include:

Query Manager: for complex query creation and reporting

Variance Monitor: to measure and identify SAP data discrepancies

Advanced Time Process Manager: for easy access to Time & Attendance data

CATS Time Workbench: for easy access to various time functionalities

Payroll Reconciliation Workbench: for Payroll and tax reconciliation in USA

Tax Analyser: for tax reconciliation in South Africa.

Visit http://www.epiuse.com/Products for more information on these products.

6.4. Contacting us We appreciate all comments and suggestions for improvement from our customers, about our products,

support, documentation and manuals. You are welcome to contact us via the above support site with such

comments. We are happy that our customers contribute to the growth of our products by making

suggestions that we can incorporate. In this way our products grow in power, ease of use, and value.

http://www.epiuse.com/Products/QueryManager.aspx

http://www.epiuse.com/Products/VarianceMonitor.aspx

http://www.epiuse.com/Products/AdvanceTimeProcessManager.aspx

http://www.epiuse.com/Products/CATSTimeWorkbench.aspx

http://www.epiuse.com/Products/PayrollReconcilliationWorkbench.aspx

http://www.epiuse.com/Products/TaxAnalyser.aspx

http://www.epiuse.com/Products

oap 3_17 user guide rev b

Documents