Data Import of Master Data (Parent Records) From A SAP System

Download as pdf or txt
Download as pdf or txt
You are on page 1of 2

Data import of master data (parent records) from a SAP system

Introduction:
Master data and parent records of a SAP system can be potentially used in a Condition
Monitoring system. Therefore it is of advantage to have an automatic import of parent
records into OMNITREND® (SAP is always the Master database). This would reduce the
effort of preparing the master data tremendously.

SAP has to be seen as Master database in this case. If changes need to be made then
those would have to be done in SAP. Because of these changes a certain replication
mechanism would be needed. In order to simplify the process there should be a relative
loose replication schedule like every other week. This would be more than enough as the
master data does not change very fast.

Certain fields are not needed to be assigned. An example would be the ALIAS names in
OMNITREND®. Only the ID has to be identical in both systems. Because of this
identification a data exchange between OMNITREND® and SAP is possible. Messages
can be exchanged very easily when both system do use a similar code for standardized
messages, which can be interpreted by both systems. Using this mechanism work order
requests for machine or ‘equipment’ can be given to SAP. There it would be screened and
could trigger work orders after acknowledgement.

General functional description


Step 1:
An export file is created out of SAP. Ideally it should be an Excel spread sheet with a
table identifier. In this case those headers can be read and ‘import templates’ can be
made and reused under the assumption that the file structure is always the same.

Step 2:
Relevant field headers are read by OMNITREND®.

Step 3:
An Editor does read relevant database field names from OMNITREND® and SAP
export file headers. In the editor related fields are linked manually, but certain fields
are also ignored. The relations are stored in the format of an ALIAS table. Using this
import template makes it possible, that the relation has not to be made with every
synchronization. If new data types are added, it is also possible to add and edit the field
relations.

Step 4:
The Import Editor does generate a XML file based on the relations template and the data
coming from the SAP export file. The XML file is then imported into OMNITREND®.

Step 5:
Import of the XML-file into OMNITREND®.
See also functional diagram on next page.

PRÜFTECHNIK Condition Monitoring GmbH 1/2


Technical Place – Equi-No
An open point is if the data is organized according the Equi-No or Technical places.
OMNITREND® is oriented according to technical places, but of course there are good
reasons for both views.

Diagram

OMNITREND Editor Window Excel


® Database Export
structure It is a split window and building of relations is done using files
Drag and Drop. Already assigned fields are visibly
Display of marked. …should
database field always be
names and OMT – Linked fields Import coming stored
‚real’ names available fields in a list form a SAP- under the
in the user format Excel-Export same
interface of file format directory.
OMNITREND® The fields
can be
unlinked
using a right
mouse key
menu

Function bar for base functions like Load, edit etc.

PRÜFTECHNIK Condition Monitoring GmbH 2/2

You might also like