Sap QM IDI Interface With LIMS
Sap QM IDI Interface With LIMS
Sap QM IDI Interface With LIMS
Summary
A description of the steps needed to activate a communication between Quality
management and an
external system using the QM-IDI protocol.
This document contains only the mandatory actions and definition to have the system
working. For complex
problem this is only the start point.
The major effort should be spent on the external system creating the application
program needed to interface
the functionality of the external system (usually a LIMS system).
This document shows how to configure the QM-IDI interface in release 4.6C.
Author Bio
Aveek Ghose has 12 years of IT experience and has worked across the globe in SAP
Implementations.
Aveek has an MS in Information Systems from George Mason University in USA and a MS
in Economics
from Virginia Tech in USA and is currently working for IBM India.
© 2006 SAP AG 1
Table of Contents
Define QM-IDI
Subsystem .........................................................................
...................................... 2
Define a Work
Center ............................................................................
.......................................... 3
Create an Inspection
Plan ..............................................................................
................................. 5
Ready to transfer
data? .............................................................................
.................................... 11
Sample Communication
Program............................................................................
...................... 14
Run the
interface .........................................................................
.................................................. 19
© 2006 SAP AG 2
Make the described choice
If this is the first subsystem in the environment, the following screen appear.
In the same inspection plan or routing it is possible to define more than a single
subsystem.
In this way you can identify as many external systems as you need.
© 2006 SAP AG 3
In the following example a simple work center, without confirmation or cost
accounting is defined. The only
purpose is to identify the subsystem itself for the operation.
© 2006 SAP AG 4
The work center category has been defined in order to have a work center without
additional data.
© 2006 SAP AG 5
In our example a simple Inspection plan is needed. Only an header, an operation and
a characteristic are
described in the example that follow
© 2006 SAP AG 6
In the header enter the mandatory info: Inspection plan description, usage, status
and Unit of Measure.
Add an Operation using the Work Center previously defined and QM01 control key.
© 2006 SAP AG 7
At Characteristic level (under the operation) a simple inspection characteristic is
defined as follow:
© 2006 SAP AG 8
The inspection results take place in the inspection lot.
For the material test roh the standard inspection type 01 is active so the
Inspection lot with origin 01 can be
created.
© 2006 SAP AG 9
Complete the required information.
© 2006 SAP AG 10
Ready to transfer data?
Now the environment should be ready to transfer data. In the first step data should
be transferred from SAP
to sub-system and than the relevant results should be transferred back.
First it is possible to check if the inspection lot has been correctly created:
© 2006 SAP AG 11
The inspection lot is ready to receive the result. The inspection lot has been
correctly created.
© 2006 SAP AG 12
A second check should be carried out.
The QM-IDI interface use a log file to register the operation un uploading and
downloading data between
SAP and subsystems.
©
2006 SAP AG 13
The table contains the control record for the operation defined for the subsystem
for the Inspection lot just
created.
The subsystem can use two types of function modules: a set for downloading data and
a set for uploading
data through RFC technique.
It’s possible to create a sample communication program using SAP utilities. The
sample program is
© 2006 SAP AG 14
For this reason a C or VisalBasic compiler is needed on the client system. The file
needed to compile the
sample program and the necessary Dynamic Link Library are in the SAPGUI CD-Rom and
have to be
installed on the subsystem running the sample program.
© 2006 SAP AG 15
Choose a QM-IDI function module. These function modules can be easily identified
because of the prefix
QIRF_.
©
2006 SAP AG 16
Display the function module and select UtilitiesÆ RFC Interface Æ Generate
Repeat this operation for all the function module you need in the sample source
file.
© 2006 SAP AG 17
Select the language of the example source file you need. In the example below the
ANSI C client version has
been selected.
When you decide to download the source code the destination directory must be
defined:
©
2006 SAP AG 18
The source and the include files are downloaded to the defined directories.
©
2006 SAP AG 19
If the PC is connected to a LAN and the SAP application server is available it is
possible to start immediately
the communication.
The user interface is of char type (line command) and run in a ‘DOS’ window. A
valid logon is required to
start the communication.
All the detail about the interface can be found in the documentation; both the on-
line and the Print files.
All the function modules and the communication structures are described in detail.
SAP will not be held liable for any damages caused by using or misusing the
information, code or methods
suggested in this document, and anyone using these methods does so at his/her own
risk.
© 2006 SAP AG 20