SAP ABAP IMG Activity OLQW-ES (Retrieve Characteristic Results Via PC Interface)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ QI (Package) QM IMG and area menu
IMG Activity
ID OLQW-ES Retrieve Characteristic Results Via PC Interface  
Transaction Code S_ALR_87005390   IMG Activity: OLQW-ES 
Created on 19981222    
Customizing Attributes OLQW-ES   Retrieve characteristic results via PC interface 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name OLQW-ES    

In this step you can set the system to copy characteristic results from subsystems using a PC interface.

You can use the transactions for recording characteristic results to copy data directly from test equipment or PC applications. To do this you must use a function enhancement. The system contains a corresponding model coding for the QEEM0021 user exit.

This model coding allows the data transfer to be planned at characteristic level and to be triggered using an additional pushbutton in the results recording function. The coding provides the structure for calling up the test equipment driver.

Test equipment drivers are function modules with an interface predefined by SAP. They are responsible for copying the data from the subsystem. These drivers can be installed as ABAP programs in the SAP system, or as RFC server programs in the subsystem.

The following test equipment drivers are provided:

  • Model driver for copying quantitative single results from MS-Excel using OLE technology.
  • Model driver for copying qualitative single results (attribute codes) with an inspection description from a PC file.
  • Driver body for copying results from an external system (with the option of generating a framework program in C or Visual Basic to implement the transfer).

Requirements

For the current release the PC interface is not completely integrated in the standard system. The system therefore plans the use of the test equipment drivers with the help of the information fields contained in the task list characteristics. If you need to use these fields for other purposes you must store the information for the drivers elsewhere and alter the model coding accordingly.

Activities

  1. Check whether the ABAP model driver is suitable for your application. If required create copies and adjust these to meet your needs.
    (Transaction SE37)
  2. If you want to link external driver programs, make sure that:
    1. These programs are available in the relevant locations
    2. The data required for calling up these programs is stored in RFC destinations.
      (Transaction SM59)
  3. Activate the function enhancement QEEM0021 with the model coding or the coding you have adjusted.
    (Transaction CMOD)

Overview of test equipment drivers

QINT_GET_PCFILE_DATA

This driver provides the model for a group of drivers that copy inspection results from measurement logs. If you want to use a driver for a specific measurement log, copy the driver and customize the copy for your required data format.
The driver copies catalog entries (code groups and codes) and inspection descriptions (short text) from a PC file. For each record this file contains a line with three fields, separated by commas. The first field contains the code, the second the code group, and the third contains the inspection description.
The driver loads a number of records that correspond to the sample size at once, and you can then select the data containing the codes from a file selection dialog box.
If you want to use this driver, maintain the information fields for the characteristic as follows:

  • Information field 1: Is not used
  • Information field 2: Is not used
  • Information field 3: QINT_GET_PCFILE_DATA

QINT_GET_EXCEL_DATA

This driver is a model for copying inspection results from PC applications into the QM component, with the help of OLE technology.
The driver uses OLE technology to call up a user-defined MS Excel function. You can select the Excel file contained in this function from a file selection dialog box. The name of the Excel function is stored in information field 1 for the characteristic.

Example of a user-defined Excel function:
The function is called GetValue and finds an entry from the table Table 1 using a measured value. This table contains measured values in column B from line 5 onwards.

   Public Function GetValue(Number As Integer) As String 
       Sheets("Tabelle1").Select 
       Range("B"&Number + 4).Select 
       GetValue = Active.Cell.FormulaR1C1 
   End Function

If you want to use this driver, maintain the information fields for the characteristic as follows:

  • Information field 1: GetValue
  • Information field 2: Is not used
  • Information field 3: QINT_GET_EXCEL_DATA

QINT_GET_RFC_DATA

This driver defines the interface for test equipment drivers in external systems. External drivers are configured using RFC destinations that contain all the data necessary for calling up an external program.

You can start the external driver in the following ways:

  1. Front end workstation
    In this option you start the external program from the SAP system on the relevant PC for the external workstation. When you close the SAP transaction, the SAP system also closes the external program.
  2. Registration
    In this option the external program is started independently of the SAP systems. After it has been started, the external program logs on to the SAP gateway and is ready to be contacted by the SAP system. The functions of drivers started in this way are not just limited to one specific front-end PC, but can be called up from several different workstations (sharing of test equipment).

If you want to use an external driver, maintain the information fields for the characteristic as follows:

  • Information field 1: Is not used
  • Information field 2: RFC destination for the driver or NONE
  • Information field 3: QINT_GET_RFC_DATA

Example

The external driver for a set of scales is called 'SC.EXE' and is installed in directory'C:\'. Maintain the RFC destination as follows:

  1. Start transaction 'SM59'
  2. Switch to the 'TCP/IP connections'
  3. Create the RFC destination 'SCALE01'
    Connection type 'T'
    Activation type 'Start'
    Start on 'Front end workstation'
    Program 'C:\SC.EXE'
    Description 'Scale 01'
  4. Save the settings

You can check the settings by testing the connection.

If you want to use this driver for a task list characteristic, enter the RFC destination 'SCALE01' in information field 2. Enter the driver QINT_GET_RFC_DATA in information field 3.

If you want to create your own external programs, you can generate a suitable RFC server program using the C or Visual Basic programming languages. You can then use this program as a copy model for your driver.

Further notes

You can find additional information about drivers in the function group documentation QINT.

You can find a description of the RFC function in the SAP documentation Basis -> Development Workbench -> Remote Communication.

Business Attributes
ASAP Roadmap ID 151   Design interfaces 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG OLQW-ES 0 HLA0001808 Characteristic Results 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  19981222 
SAP Release Created in