Professional Documents
Culture Documents
SDN QM Idi Interface
SDN QM Idi Interface
SDN QM Idi Interface
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(s): Aveek Ghose
Company: IBM India
Created on: 23 May 2006
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
Table of Contents
Define QM-IDI Subsystem ............................................................................................................... 2
Define a Work Center ...................................................................................................................... 3
Create an Inspection Plan ............................................................................................................... 5
Create the Inspection Lot................................................................................................................. 8
Ready to transfer data? ................................................................................................................. 11
Sample Communication Program.................................................................................................. 14
Run the interface ........................................................................................................................... 19
Disclaimer and Liability Notice....................................................................................................... 20
2006 SAP AG
2006 SAP AG
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
The work center category has been defined in order to have a work center without additional data.
In the QDR system enter the subsystem ID previously defined.
2006 SAP AG
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
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
At Characteristic level (under the operation) a simple inspection characteristic is defined as follow:
2006 SAP AG
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
2006 SAP AG
10
2006 SAP AG
11
The inspection lot is ready to receive the result. The inspection lot has been correctly created.
2006 SAP AG
12
2006 SAP AG
13
The table contains the control record for the operation defined for the subsystem for the Inspection lot just
created.
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.
To create the sample source file proceed as follow:
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.
2006 SAP AG
20