LO750 Quality Management Configuration and

Organization

LO750
Quality Management
Configuration and Organization

SAP AG 2001

Copyright

Copyright 2001 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in
any form or for any purpose without the express permission of
SAP AG. The information contained herein may be changed
without prior notice.

All rights reserved.

SAP AG 2001

Quality Management (QM)

Level 2

Level 3
LO715

3 days

QM in
Procurement
LO170

3 days

Quality Management

LO705

3 days

Quality Inspections

LO710

3 days

Quality Notifications

LO720
2 days
QM in Discrete and
Repetitive
Manufacturing
LO721

3 days

QM in the Process
Industry

LO725
2 days
QM in Sales and
Distribution / Quality
Certificates

SAP AG 1999

LO750

3 days

QM Organization and
Configuration

Prerequisites

Recommended

R/3 Development Environment

IMG Basic Concepts

Required

SAP AG 1999

BC400 - ABAP Workbench: Basics

LO705 - Quality Inspections

Target Group

Participants:
Project team
Employees responsible for the technical
introduction of the QM component
Duration: 3 days

SAP AG 1999

Course Overview

Contents:
Course Goals
Course Objectives
Course Content
Course Overview Diagram

Main Business Scenario

SAP AG 1999

Course Goals

At the conclusion of this course, you will

understand:

The technical settings in Customizing for the

Quality Management (QM) application component
Functions that enable additional customerspecific enhancements without modification
The archiving of QM data

SAP AG 1999

Course Objectives

At the conclusion of this course, you will be able

to define:
Technical Customizing settings
The SAP enhancement concept
SAPscript forms in QM
Interfaces (QM-IDI, QM-STI, BAPIs)
The logical database in QM

Archiving options

SAP AG 1999

Course Content

Preface
Unit 1

Course Overview

Unit 6

SAPscript

Unit 2

Basics

Unit 7

Follow-Up Actions

Unit 3

Customer
Enhancements

Unit 8

Interfaces

Unit 4

Status Management/
User Status

Unit 9

Evaluations

Unit 10

Archiving

Unit 5

Ease of Use

SAP AG 1999

Course Overview Diagram

Course Overview

SAPscript

Basics

Follow-Up Actions

Customer
Enhancements

Interfaces

Status Management/
User Status

Evaluations

Ease of Use

Archiving

10

SAP AG 1999

Main Business Scenario

Our company wants to introduce the Quality

Management component. As a result, the
company's requirements must be defined in
Customizing for the component.

SAP AG 1999

Basics

Contents:
Customizing Projects
QM Customizing Structure

Technical Areas of QM Customizing

SAP AG 1999

Basics: Unit Objectives

At the conclusion of this unit, you will be able to:

Show how Customizing functions are linked to the

IMG
Give an overview of the technical settings in the

QM application component

SAP AG 1999

Basics: Course Overview Diagram

Course Overview

Basics

Follow-Up Actions

Customer
Enhancements

Interfaces

Status Management/
User Status

Evaluations

Archiving

10

Ease of Use

SAP AG 1999

SAPscript

Basics: Business Scenario

Our company wants to gain an impression of the

configuration options in QM through an overview
of the Implementation Guide and Customizing.

SAP AG 1999

Customizing/IMG (Implementation Guide)

SAP Reference IMG
Activity
Documentation for IMG activity

Project IMG
Activity
Documentation for IMG activity
Project documentation

Project Management

SAP AG 1999

Edit Project

Project Analysis

QM Customizing Structure

IMG
Quality Management
Basic Settings
QM in Logistics
Quality Planning
Quality Inspection
Quality Certificates
Quality Notifications
Quality Control
Test Equipment Management

Environment
SAP AG 1999

Technical Areas of QM Customizing (1)

Function Module Assignment

Quality Planning

Inspection points
Follow-up actions for the usage decision
Quality score procedures
Sample types (FM for label printing)
Data origin

Quality Notifications

SPC criteria

Quality Certificates

Valuation rules

Quality Inspection

Rules for sample determination

SAP AG 1999

Follow-up functions
Follow-up actions for tasks

Course component

Technical Areas of QM Customizing (2)

Scheduling a program as a job

Inspection for deadline monitoring

Automatic usage decision

Search helps

Inspection characteristic

Inspection method

Inspection plan

Quality info record

Inspection lot

Certificate profiles

Quality notifications

SAP AG 1999

Technical Areas of QM Customizing (3)

Function enhancements

Subscreens

Function keys

Function modules

Workflow
Archiving

Field selection
Status management
List variants
Condition technique
Partner concept
Interfaces

Distribution of ALE master

data
SAP AG 1999

Course component

Basics: Unit Summary

You are now able to:
Show that the IMG contains documentation for each
activity. You can execute the activities directly.
Explain that functions are available for project
management and project documentation.
Process each Customizing activity using the IMG.
Explain how QM Customizing is structured into Basic
Settings, QM in Logistics, Quality Planning, Quality
Inspection, Quality Certificates, Quality Notifications,
Quality Control, Test Equipment Management, and
Environment

Describe how the QM application component offers a

wide range of options for setting up your system to suit
your needs.

SAP AG 1999

Customer Enhancements

Contents:
Enhancing Functions
SAP Enhancements and Customer
Enhancement Projects
Procedure for SAP and Customers
Processing Components
Activating Enhancement Project

Creating Field Exits

SAP AG 1999

Customer Enhancements: Unit Objectives

At the conclusion of this unit, you will be able to:

Understand the enhancement concept at SAP

Create an enhancement project

SAP AG 1999

Customer Enhancements: Course Overview

Diagram

Course Overview

SAPscript

Basics

Follow-Up Actions

Customer
Enhancements

Interfaces

Status Management/
User Status

Evaluations

Archiving

10

Ease of Use

SAP AG 1999

Customer Enhancements: Business Scenario

Our company wants to create functional

enhancements that are not in the standard system.

SAP AG 1999

Enhancing Functions

Is a similar function
available in the SAP Standard?

Customer development
No

Yes
Can the SAP function be
adapted to suit the customer
using Customizing?

Customizing
Yes

No
Does the SAP application allow
you to add extra functions using
enhancements?
No

Request enhancement
Avoid modification
SAP AG 1999

Enhancement
Yes

Program Enhancements

Menu 1

Menu 2
Function 1
Function 2
Cust. function
Function 3

Field 1

Field exit

Menu 3

Menu exit

Field x
Field y

Function module

Program exit
SAP AG 1999

Screen exit

Customer Enhancement Project

SAP

Customer

Definition of SAP
enhancements

Definition
of
enhancement
projects

SMOD

CMOD

SAP AG 1999

SAP Enhancements and Customer Enhancement

Projects
SAP

Customer

C
C

E
C

Component
SAP AG 1999

SAP enhancement

Customer enhancement projects

SAP Procedure

Define customer exits in

application functions

Program exits
Menu exits
Screen exits

Combine components for

SAP enhancements

E
C

Document
enhancements
SAP AG 1999

SAP documentation:

Customer Procedure
Create enhancement
project using SAP
enhancements

E
P

Function modules

Process components
for enhancement
project

Menu entries

Subscreens

Document
enhancement project

Customer documentation:

Activate enhancement
project

Activate

SAP AG 1999

Creating a Customer Enhancement Project

Project Management

Project

Create

Attribute

Short txt

Save
SAP AG 1999

Assigning SAP Enhancements to Customer Project

Project Management

Project

Change SAP
enhancements

SAP enhancements

Save
SAP AG 1999

Processing Components
Project Management

Project

Change
components
SAP enhancements

Process
components
Dialog box

Editor for
function module
SAP AG 1999

Lang.
Text

Screen Painter

Activating Enhancement Project

Project Management

Project

Activate project

SAP AG 1999

Creating a Field Exit

ABAP Function Library: Initial screen

11

Function module

FIELD_EXIT_<Data element>

22
33
44

55
66
77

88

Create a field exit

Field exit for data element ..?

Create function module

Process function module

Activate function module

Assign program/screen
(for local field exit only)

Activate field exit

SAP AG 1999

Global enhancements

Display FM: Interface

Import parameter
INPUT
Export parameter
OUTPUT

Customer Enhancements: Unit Summary

SAP application programmers plan program

exits, menu exits, and screen exits for the
application and combine them to form SAP
enhancements.

Customers create an enhancement project

using the SAP enhancements.

SAP AG 1999

Data for Exercises

Customer Enhancements Exercises

Customer Enhancements Solutions

Status Management/User Status

Contents:
Using Status Management
Defining and Creating a Status Profile
Assigning Status Profile to Object Types
Defining and Assigning User Status to
Business Transactions

Selection Profile

SAP AG 1999

Status Management: Unit Objectives

At the conclusion of this unit, you will be able to:

Use general status management
Define your own user statuses in addition to

the existing system statuses and assign

them to objects

Create and use selection profiles

SAP AG 1999

Status Management: Course Overview Diagram

Course Overview

SAPscript

Basics

Follow-Up Actions

Customer
Enhancements

Interfaces

Status Management/
User Status

Evaluations

Archiving

10

Ease of Use

SAP AG 1999

Status Management: Business Scenario

Our company wants to create business

transactions using system and user statuses.

SAP AG 1999

Using Status Management in QM

Status profile

Status profile

Status profile

Status profile

SAP AG 1999

Quality info
record
Quality
notification
Quality
certificate
Inspection
lot

Statuses

Performing a
transaction
for example,
- Releasing
- Closing

SAP AG 1999

changes

Number of
active statuses

defines

Number of
executable
transactions

Status Management

System status
INSP:
INSP:

Inspection active

REL:
REL:

Released

RREC:
RREC:

Results confirmed

CALC:
CALC:

Sample calculated

CCTD:
CCTD:

Insp. characteristics created

PASG:
PASG:

Plan/specification assigned

PRII:
PRII:

SAP AG 1999

Inspection instruction printed

User status
XXXX:
XXXX:

Freely defined

Defining Status Profiles

Create
tatus profile
Create sstatus
profile

Assign
Assign status
status profile
profile to
to
object
object types
types

Define
Define user
user status
status

Assign
Assign user
user status
status
to
to business
business
transactions
transactions

SAP AG 1999

Creating Status Profiles

Create
Create
sstatus
tatus profile
profile

New Entry

Status profile
Text

Rel. visual inspection

Maintenance language

SAP AG 1999

LO750_00

EN

Assigning Status Profile to Object Types

Assign
Assign status
status profile
profile to
to
object
object types
types
Permitted object types
Task
Insp. lot with plan w/o chars
Insp. lot with plan and chars
Insp. lot w/o plan or chars
Quality info record
Quality notification
Quality certificate profile

Partial lot
SAP AG 1999

Define User Statuses

Define
Define user
user status
status

User status
Long
text

Status
number

Status

LKD

No visual inspection

CNF

Confirmed

REL

Release

SAP AG 1999

Short text

Init.
status

Lowest
Highest
Position
status no. status no.

Priority

Auth.
code

Assigning User Status to Business Transactions

Assign
Assign user
user status
status
to
to business
business
transactions
transactions
Status
Status profile
profile

LO705-00

Status
Status

LKD

Transaction control
Business transaction
Make usage decision

SAP AG 1999

No influence

Allowed

Warning

Disalld

No action

Set

Delete

Selection Profile
Without status profile

System
System status
status 11

Inclusive
Inclusive

Exclusive
Exclusive

Active
Active

Inactive
Inactive

Never
Never active
active

and / or

System
System status
status 22

Inclusive
Inclusive

Exclusive
Exclusive

Active
Active

Inactive
Inactive

Never
Never active
active

and / or

SAP AG 1999

With status profile

System
System status
status 11 or
or

user
user status
status 11

Inclusive
Inclusive

Exclusive
Exclusive

Active
Active

Inactive
Inactive

Never
Never active
active

and / or

System
System status
status 22 or
or

user
user status
status 22

Inclusive
Inclusive

Exclusive
Exclusive

Active
Active

Inactive
Inactive

Never
Never active
active

and / or

Status Management: Unit Summary

Status management is used in the following QM objects: Quality

info record, inspection lot, quality certificate, quality notification.
The SAP System differentiates between system status and user
status. The system status is defined by SAP, and the user status is
freely defined.
You can define your own status profiles. Each status profile must
be assigned to at least one object. Each status profile contains one
or more allowed statuses. You can define the system response for
each status within the framework of the SAP-defined business
transactions.
You can define a status profile and user status in several
languages.

You can use selection profiles to define status combinations for

selecting objects.

SAP AG 1999

Status Management Exercises

Status Management Solutions

Ease of Use

Contents:
Configuration Using Table Controls
Field Selection
Variable Lists

Results Recording Configuration

SAP AG 1999

Ease of Use: Unit Objectives

At the conclusion of this unit, you will be able to:

Customize the SAP interface to suit a user's

requirements using field selection, list

variants, and table control

Configure results recording

SAP AG 1999

Ease of Use: Course Overview Diagram

SAPscript

Follow-Up Actions

Customer
Enhancements

Interfaces

Status Management/
User Status

Evaluations

Ease of Use

Archiving

10

Course Overview

Basics

SAP AG 1999

Ease of Use: Business Scenario

Our company wants to individually configure its

SAP interfaces.

SAP AG 1999

Configuration Using Table Control

Change column order

Item Req. qty.

Material

Short text

Material

Short text

10
20
30
40

Change column width

Item Req. qty.

10
20
30
40

Create variant

Delete variant

SAP AG 1999

Current setting
Standard setting

Field Selection

Module pool
Screen group

Dependent on values of
influencing fields
Modifiable field

Influencing field

General value
Influencing

SAP AG 1999

Input

1. Upper limit
1. Lower limit
Selected set
Basic sample quantity
Info field 1

Req. Disp.

Hide

Field Selection (Example: Usage Decision)

Module pool

SAPMQEVA

Screen group

Insp. lot: UD

Dependent on values of
influencing fields
Modifiable field

Influencing field
Influencing value

SAP AG 1999

Batch
requirement

Batch status mgmt

Input

Req.

Disp.

Hide

Variable Lists (Basics)

Definition of list variants
1. Field selection

Display variant

2. Object selection

Selection screen

Definition levels

SAP AG 1999

Customizing:

Transaction variant
(generally valid)

Application transaction:

User-specific variant
General variant

Variable Lists (Field Selection)

Line : 1
Column content

SAP AG 1999

Item

Length

Column content

Length

Inspection lot

12

Material document

10

Material

18

Posting date

10

Plant

Dyn. modification

Insp. lot quantity

Insp. stage

...

Hidden fields

...

Variable Lists (Object Selection)

Field name

Type

Selection profile

Lot created

Plant

Lot origin

...
Selected
Not selected
Not supported

T: Table variable from TVARV

D: Dynamic date calculation
B: User-specific variable
Selection criteria

Name of variables
QL_ENSIB
Current date - xxx, current date + yyy

SAP AG 1999

Results Recording Configuration

Inspection lot : 4711

Operation: 10
No.

Status

10

Diameter

20

Surface

30

Color

40

Streaks

...

...

Customizing
recording
configuration

Characteristic

Close on CONTINUE

Close on saving

Skip CH view

SAP AG 1999

User
parameters

Status

Characteristic
closed

Ease of Use: Unit Summary

In QM there are a number of ways to define

(set) fields to suit the needs of every
company and user:

Table control

Field control

Variable lists

By configuring results recording, you can

simplify the recording procedure.

SAP AG 1999

Ease of Use Exercises

Ease of Use Solutions

SAPscript

Contents:
Forms and Print Programs
Processing Sequence: Form Processor

Procedure for Changes

SAP AG 1999

SAPscript: Unit Objectives

At the conclusion of this unit, you will be able to:

Explain the basics of SAPscript
Describe the principle relationship between a print

program and form

Show how you can also read data in a form

SAP AG 1999

SAPscript: Course Overview Diagram

Course Overview

SAPscript

Basics

Follow-Up Actions

Customer
Enhancements

Interfaces

Status Management/
User Status

Evaluations

Archiving

10

Ease of Use

SAP AG 1999

SAPscript: Business Scenario

Our company wants to create forms and print

programs using the SAPscript editor.

SAP AG 1999

SAPscript from User View

User
Maintenance
transactions

Application
transactions

Layout
(forms, styles)

Text editor

Database

ABAP
Workbench

SAP AG 1999

Programming
interface

Form processor

Forms

Form
Form 11

Invoice

Form
Form 22

Document

Form
Form 33

Dear...

SAP AG 1999

The Print Program

Form
Form 11

SAP DB

Form
Form 22
Form
Form 33

Application transaction

Print program

SAP AG 1999

Processing Sequence: Form Processor

SAP DB
Form:
Form:

Document
Document
Invoice

Application transaction
Print program

Form processor

SAP AG 1999

Tasks of the Print Program and Form Processor in

SAPscript

Print program
Application
data

DB

report jh_form_01.

Form:
ABAP
report

tables: scustom.
select * from scustom...
......
call function 'OPEN_FORM'
......
call function WRITE_FORM'
......
call function CLOSE_FORM'
......

this
your
request, and
request, that
3rd June
and Chicago,
Invoicethis
no. 4 meets
hope123-45-556-678
thatyour
this
requirements
request
Type.No.
meets Price
00345your requirements
200.Mr D. Test
7 Old Road
47110 Irving

Form
processor

00379
02378
00458
Total

150.50.300.700.-

Chicago State Bank

Acc. no: 0815 4711
Sort code:000000000

SAP AG 1999

Form Print: Start and Finish

CALL FUNCTION 'OPEN_FORM'

EXPORTING
FORM
= ...
LANGUAGE
= ...
DEVICE
= ...
OPTIONS
= ...
DIALOG
= ...
IMPORTING
LANGUAGE
= ...
EXCEPTIONS ...
= ...

CALL FUNCTION 'CLOSE_FORM'

IMPORTING
RESULT
= ...
EXCEPTIONS ...
= ...

SAP AG 1999

When Do You Modify the Print Program?

Additional data
is required

New text elements

are needed

SAP AG 1999

Structural changes

Using the print

program to print
another form

Change Procedure (1)

Which new fields and

tables are needed?
Are the necessary fields
contained in the existing
tables, or are new
fields and tables required?

Which program and form

are used?

SAP AG 1999

Change Procedure (2)

Does the print program

need to be modified, or
only the form?
Can the missing data be
supplied from another
program using PERFORM?

Do SAP enhancements
already exist in the form of
customer exits?

SAP AG 1999

Change Procedure (3)

Copy the SAP standard form and,

if necessary, the print program in
the customer name space Z or Y
Modify the copies
Define new form and print program in
Customizing

Test your modifications

SAP AG 1999

SAPscript: Unit Summary

When maintaining forms, a form, which contains the

information needed to design the text (formats, fonts,
layout, etc.), is assigned to a document. The print
program retrieves the required data from the form and
the database, and controls the output. Certain
function modules activate the SAPscript form
processor, which is responsible for processing the
form.

The QM application component contains a variety of

forms and print programs. You can modify these
forms and programs to suit your needs.

SAP AG 1999

SAPscript Exercises

SAPscript Solutions

Follow-Up Actions

Contents:
Defining Follow-Up Actions
Follow-Up Actions: Customizing
Follow-Up Actions: Catalog Maintenance
Status for Follow-Up Actions
Follow-Up Actions and Business
Transactions
Action Box

Customizing for the Action Box

SAP AG 1999

Follow-Up Actions: Unit Objectives

At the conclusion of this unit, you will be able to:

Explain the points at which you can define

follow-up actions in QM
Describe the variants, in which you can

create follow-up actions

Show how you can define follow-up actions

for quality notifications

SAP AG 1999

Follow-Up Actions: Course Overview Diagram

Course Overview

SAPscript

Basics

Follow-Up Actions

Customer
Enhancements

Interfaces

Status Management/
User Status

Evaluations

Archiving

10

Ease of Use

SAP AG 1999

Follow-Up Actions: Business Scenario

Our company wants to define follow-up actions for

business transactions.

SAP AG 1999

Defining Follow-Up Actions

ABAP Workbench
Create function module

Customizing
Maintain the follow-up action table

If necessary, assign business transactions

SAP AG 1999

Follow-Up Actions: Customizing

PRINT

for notification task

Z_QM_PRINT_REPORT

SAP AG 1999

Print inspection report

QM90 Print insp. report

Follow-Up Actions: Editing Selected Sets

UD for inspection lots in production

03
03

A
R

Accepted
Rejected

Released

Accepted
Rejected

100
1

Follow-up action Rejection, for example: PRINT, print inspection report

SAP AG 1999

Follow-Up Actions: Setting the User Status

Follow-up action is
triggered
Assigned business
transaction is executed

User status is
automatically set

Applications

Workflow
can be
triggered

SAP AG 1999

Additional
selection
options (lists)

Additional
information for
inspection lot,
notification

Follow-Up Actions and Business Transactions

Business transaction
Trans Text

Change Follow-Up Actions

QM90

Follow-up act. variant 1

...

...
Follow-up act. variant 10

QM99

LO750_01

Status profile

Print inspection report

User status

Status no. Status Short text

LText Init.Transaction
status
Priority
Lowest status
Highest
no.statusPosition
no.
control

PBDR Insp. report printed

Influence
Business transaction
Follow-up act. variant 1

Insp. type

Rec. insp. at goods receipt for purch. order

01

Insp. lot processing

Status profile

SAP AG 1999

LO750_01

Auth. code

Follow-up action
No activity

Activate

Action Box

No. header
Notification
Material

No.

Customer

Action
No.box

Follow-up action

Telephone call

- synchronous -

Notification
8D report

Task /
activity

Business Workflow
- asynchronous -

Customizing
Customizing

SAP
SAP standard
standard examples
examples

Customer
Customer enhancements
enhancements
SAP AG 1999

Customizing for the Action Box (1)

Overview of Customizing steps for

setting up the action box
1

Define individual follow-up functions

Define for each follow-up function,

whether:

Example of a process with dependent

follow-up functions
Send confirmation of
receipt (*)

or
It is dependent on another
It can be executed once or several
times
Possibly define further allowed
follow-up functions for each
follow-up function

Send interim
notice (*)

Send final
notice (*)

END
Send final
notice (*)

END

(*) = Follow-up functions

SAP AG 1999

Customizing for the Action Box (2)

Function
Function module:
Bus. Operation
Task
Activity

QM06_FM_TASK_SEND_PAPER

Activity creates task or

activity

User interface
Icon

ICON_MAIL

Quick info

Send confirmation of receipt

Interface layout

Coding for generated task/activity

Code group
Code

QM-G1

General tasks CC

0010 Confirmation of receipt

Specific details for task

Workflow task
start when saving

Task
FM when saving

QM06_SEND_PAPER_STEP1

Released
Completed

Function module
start when saving

Rules
Dependent follow-up function

Executable only once

SAP AG 1999

Rules

Definition of rules for

execution

Customizing for the Action Box (3)

Dialog Structure
Follow-up funcs

Notif. type:
Function

Q1
0015

Customer complaint
Send confirmation of receipt

Allwd follw-up fns

Allowed follow-up functions
FK

Short text for code

0020

Send interim notice

0023

Send final notice

Send allowed follow-up functions

for the follow-up function "Send
confirmation of receipt"

SAP AG 1999

Customizing for the Action Box (4)

SAP standard system

Function
Function group
group QM06
QM06

Internal note

Creates an activity with a long text

Documentation telephone call

Creates an activity with a long text

Create a new quality notification including the items

Create a repair order
Goods movement for repair order (RMA)

Copy decision to repair order

SAP AG 1999

Customizing for the Action Box (5)

SAP standard system

Adapt the quality level

Return to initial inspection stage

Tighten

Request an 8D report

QM_8D_REPORT form

Send report

Confirmation of receipt

Interim notice

Final notice

QM_REPLY form

SAP AG 1999

Function
Function group
group QM06
QM06

Customizing for the Action Box (6)

SAP standard system

Performing stock postings

Unrestricted-use to inspection stock

Unrestricted-use to blocked

Blocked to unrestricted-use

Scrapped

Assign vendor
Assign purchasing document
Create/edit a return delivery
Create a transport order

SAP AG 1999

Function
Function group
group QMLR
QMLR
Vendor
Vendor complaint
complaint

Customizing for the Action Box (7)

SAP standard system

Function
Function group
group QISD
Link
Link to
to solution
solution DB
DB

Call up/start solution search

Display assigned documents from the solution database

Symptoms

Solutions

SAP AG 1999

Follow-Up Actions: Unit Summary

The QM component allows you to define

automatic follow-up actions in the form of
function modules.
You can define follow-up actions for usage
decisions and tasks.
For each follow-up action, you can determine
how the update is to take place and at which
point the follow-up action should be performed.
You can assign specific business transactions
to a follow-up action.

You can use the action box to define follow-up

functions for quality notifications in
Customizing.
SAP AG 1999

Follow-Up Actions Exercises

Follow-Up Actions Solutions

Interfaces

Contents:
QM-IDI
RFC Function Modules for Upload and
Download
QM-STI
BAPI Definition and Properties

BAPIs in Quality Inspection and Quality

Notifications

SAP AG 1999

Interfaces: Unit Objectives

At the conclusion of this unit, you will be able to:

Explain how interfaces are used in the QM

component

SAP AG 1999

Interfaces: Course Overview Diagram

Course Overview

SAPscript

Basics

Follow-Up Actions

Customer
Enhancements

Interfaces

Status Management/
User Status

Evaluations

Archiving

10

Ease of Use

SAP AG 1999

Interfaces: Business Scenario

The QM component should exchange data with

other systems using interfaces.

SAP AG 1999

QM-IDI: Data Transfer

Data Transfer
SAP Logistics

Quality Management System

Task
list
Basic data

Basic data

- Inspection
catalogs

SAP AG 1999

Q- level

QM Information System

Insp. lot

Results

Insp. lot

Results

Subsystem

Usage decision

Usage decision

QM-IDI: Data Transmission

Data transmission
Method: Remote Function Call
Function modules

Download
Catalog data
Selection from worklist
Operations
Characteristic specifications
Additional master data
Exceptions

SAP AG 1999

Upload
Single results
Sample results
Characteristic results
Inspection points
Usage decision

QM-IDI: Settings in the SAP System

Customizing
Define subsystem IDs
Define mail addresses for transfer logs
Define trace level for application log
Function modules for changes to the
worklist

Work Center
Define IDs for subsystems in the master records
for work centers

Inspection Plan

Assign work center to inspection plan

SAP AG 1999

QM-IDI: Assignment at Operation Level

Inspection Plan
Operation

Work center

Characteristic

10

0001

10
20
30

20

0002

10
20

30

0003

10
20

40

0004

10
20

SAP AG 1999

Sub 1

Sub 2

RFC Function Modules for Downloading

QIRF_SEND_INSP_REQUIRMENTS
Selection of operations to be processed, transfer of the
corresponding worklist

QIRF_SEND_INSP_DATA_FOR_WL
Transfer of characteristic specifications and catalog entries to the
worklist

QIRF_SEND_REQUIRMENTS_GET_DATA
Selection of operations to be processed, transfer of operations,
characteristic specifications, and catalog data

QIRF_SEND_COMMIT_TO_QM
Update of lock entries

QIRF_SEND_CATALOG_DATA
Transfer of catalog entries

QIRF_INSPPOINT_GETLIST

Evaluation of existing inspection points in the SAP System

SAP AG 1999

RFC Function Modules for Uploading

QIRF_GET_ORIGINAL_VALUES
Results confirmation for single results

QIRF_GET_SAMPLE_VALUES
Results confirmation for sample results

QIRF_GET_FEATURE_VALUES
Results confirmation for characteristic results

QIRF_GET_INSP_POINT
Results confirmation for inspection points

QIRF_GET_ALL_DATA_VALUES
Results confirmation for all result types

QIRF_GET_USAGE_DECISION
Confirmation of usage decisions for inspection lots

QIRF_GET_DEFECT_ITEMS

Confirmation of defect items

SAP AG 1999

QM-STI: Statistical Interface

SAP
QM

QM-STI

Evaluation and analysis of R/3 inspection results data using

external statistical software
Flexible data selection in SAP QM
Data transfer via API

Open interface

Advantages:

SAP AG 1999

A company can continue using existing statistical software

(investment protection).

A wide range of statistics software with special functions is

available on the market.

QM-STI: Calling the Interface

Results recording
QM-STI
Control chart

Results history

SAP AG 1999

StatSys:

ST02

Method:

M2

ST01
ST02 M1

M2

QM-STI: Data Structures

Report header
Material_Data
Vendor_Data
Method_Data
Characteristic_Header
Characteristic_Quantitative
Sample_Header
Results_Quantitative

Results_Additional_Data

SAP AG 1999

BAPI: Definition

Business Application Programming Interface

A BAPI is a precisely defined interface for the processes

and data in a business application system. BAPIs are
methods of an object in the Business Object Repository
(BOR).

BAPI

SAP AG 1999

BAPI: Characteristics

Object-based

Access to methods of objects in the BOR

Stable interface

The interface of a BAPI is "frozen"

Can be used internally and externally

BAPIs can be used in the R/3 Systems and in external systems

Functionally independent

Each BAPI can be called up independently

However: BAPIs do not contain a presentation layer

SAP AG 1999

Results can only be viewed externally using the calling program

BAPIs in Quality Management

Quality Planning

Object type MatInspectionControl

(Material inspection control)

Quality Inspection

Object type InspectionLot (inspection lot)

Object type InspLotOperation

(inspection operation)

Object type InspectionLotCharacter

(inspection operation characteristic)

Object type InspectionPoint

(inspection point for an inspection operation)

Quality Notifications

SAP AG 1999

Object type QualityNotification (quality notification)

Interfaces: Unit Summary

The QM-IDI Interface ("Inspection Data Interface in Quality

Management") provides the QM component with an open
interface to external systems and is designed for the exchange of
quality data in inspection processing.
QM provides the external system with specifications for the
quality inspection. The quality inspection is then carried out
using the external system and the results data is transferred back
to the QM System.
The QM-STI Interface ("Statistical Data Interface in Quality
Management") provides QM with an open interface to external
evaluation systems.
QM inspection results are transferred to the external evaluation
system in a format defined by SAP.

SAP business objects are accessed using stable, standardized

methods called BAPIs (Business Application Programming
Interfaces). The SAP business objects and their BAPIs provide an
object-based view of the business functions in the SAP System.

SAP AG 1999

Interfaces Exercises

Interfaces Solutions

Evaluations

Contents:
SAP Business Intelligence
Standard Analyses in QMIS
Information Structures
Update Rules
Logical Databases
ALV in List Output
Ad Hoc Queries Using QuickView

Comparison of SAP Query and QuickView

SAP AG 1999

Evaluations: Unit Objectives

At the conclusion of this unit, you will be able to:

Create info structures in QMIS

Use logical databases to perform evaluations

SAP AG 1999

Evaluations: Course Overview Diagram

Course Overview

SAPscript

Basics

Follow-Up Actions

Customer
Enhancements

Interfaces

Status Management/
User Status

Evaluations

Ease of Use

Archiving

10

SAP AG 1999

Evaluations: Business Scenario

Our company wants to be in a position to use

evaluation functions that are not included in the
SAP standard.

SAP AG 1999

QMIS Standard Analyses

Inspection lots
Notifications

Update

Standard
information structures

Standard analyses
SAP AG 1999

Organization of Information Structures

Time reference

Characteristics

Vendor
Material
Month
Inspection type
Plant

SAP AG 1999

Key figures

398
157

Number of lots...
Quantity...
Rate...

005

Summarization of Inspection Results

Results recording

Inspection
results

Status = 2
Status = 5
Inspection
points

Regeneration
Status = 5

Inspection
operations

Insp.
lot

SAP AG 1999

Characteristics

Key figures

398
398
157
157 005
005

Info Structure for Inspection Results

Characteristics
Material + (vendor/customer)

Work center
Master inspection charac.
Inspection characteristic
Plant

Period

SAP AG 1999

Update Rule (by Origin)

Goods receipt
Update rule: 22/ 52 / 53

Production
Update rule: 21/ 50 / 51
.
.

Stock transfer/
goods issue

.
.
Update rule: 21/ 50 / 51

.
.

.
.

Material
Vendor

Material
.
.
Material
.
.

Delivery
Update rule: 36/ 54 / 55

Customizing
SAP AG 1999

Customer

Update Rule (by Notification Type)

Notification for
vendor F2/Q2
Update rule: 33

Internal problem
notification F3/Q3

Update rule: 34

Notification from
customer F1/Q1
Update rule: 32

Customizing

SAP AG 1999

Material
Vendor

Material

Material
Customer

Key Figures for the Characteristics

Quantitative

All

__
S

Standard deviation

__
X

Mean value

Process capability index

Critical index

P
Pk

n
n

SAP AG 1999

A
R
D
NU
LTol
UTol

No. of

inspected and closed samples

No. of

accepted samples

No. of

rejected samples

No. of

defects in sample

No. of

nonconforming units

No. of

times value exceeded lower

specification limit

No. of

times value exceeded upper

specification limit

Generating Lists Using the LDB

ABAP program
OPEN SQL
(ABAP commands)

ABAP program
GET <node>
Logical
database

Database
SAP AG 1999

ABAP program
NATIVE SQL

Advantages of the Logical Database

ABAP 1

Query 1

ABAP 2

Query 2
Query 3

Logical database
ABAP 4

ABAP 3

- Creates selection screen

- Performs input and authorization checks
- Reads data records

ABAP 5
Query 5

Query 4

SAP AG 1999

ABAP 6

Query 6

Logical Database: Overview

ABAP
ABAP dictionary
dictionary

Logical
Logical view
view

QALS
QALS
QAPO
QAPO
QAMV
QAMV

QAMR
QAMR

SAP AG 1999

PGQ
PGQ

ABAP Events and the Logical Database

INITIALIZATION
Default values can be entered in the selection screen for
the LDB
AT SELECTION-SCREEN
You can program your own input and authorization
checks
START-OF-SELECTION
Start processing (for example, initialize texts)
GET <node>
Processing of individual records

END-OF-SELECTION
End processing (for example, calculate and display totals)
SAP AG 1999

What Is the ALV Classic?

ALV stands for the ABAP List Viewer

ALV Classic is a collective term for several function
modules in the function group SALV

Tool for the standardized output of:

Simple lists

Hierarchically sequential lists with two hierarchy levels

SAP AG 1999

Reasons for Developing ALV

Until the ABAP List Viewer (ALV) was introduced, various

report tools were used in the SAP System.
Each report tool has its own functions and application areas.
The ABAP List Viewer has standardized and simplified how
lists are used in the SAP System.

A standardized data interface and list layout is available for

all lists.

SAP AG 1999

ALV Standard

List layout based on specifications from the usability

group (LIBS)
Generic functions in lists
Only presentation, no selection

Individual list display determined by the user

Technical adjustments

Functional enhancements

SAP AG 1999

Set of Generic Functions

Detail
Filter function
Sort function
Creation of subtotals and
totals
Expand and collapse
Show and hide
fields
Download functions
Change the layout

SAP AG 1999

Basic Principle

Data is displayed in simple lists by calling up the function

module reuse_alv_list_display
Transfer parameters

Internal data table for list output

Field descriptions for data tables (field catalog)

General descriptions for list layout (optional)

ALV sets its own status

Using the callback technique, the standard ALV functions can
be flexibly combined with application-specific logic

SAP AG 1999

Standard Call for ALV

Internal table
Data

Select * from ...

Field catalog or

A B C

< Name >

A B C

A
B
C

Internal
Internal data
data table
table

Structure

Field
Field descriptions
descriptions
Calling
Calling the
the ABAP
ABAP List
List Viewer
Viewer

CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY

List
List output
output

A B C

SAP AG 1999

Field Catalogs

The field catalog describes the fields for the internal data table.
The field catalog is an internal table.
The field catalog contains an entry for each output-relevant
column in the data table.
Output options are defined for each column using the field
catalog.

SAP AG 1999

QuickViewer: Overview

Data source

Create list

Execute

Field sequence
Sorting
Selections
...

Table
Database view
Table join
Functional area
Logical database

SAP AG 1999

Basis or
layout mode

Save list
Link to Word
ABC analysis
Display in ALV control
etc.

QuickViewer: Initial Screen

Welcome to the QuickViewer

1. Enter a name and choose
Create
.
2. Choose a title and remarks.
3. Enter the name of a table, a
logical database, a join or an
SAP Query functional area as
the data source. This can be a
table, a logical database, a
join, or a functional area from
SAP Query.
4. Use layout mode
to
layout your QuickView
graphically. Choose basis
mode
whenever you want
to directly export the report
fields selected.

QuickView

DEMO

Change

SAP Query

Execute

QuickViews for user

TRAINER

LO750_D1

Create

Demo in LO750

Help topics: Selection fields; Output options for the

list: List width

SAP AG 1999

Creating a QuickView

Create QuickView DEMO: Choose data source

QuickView

DEMO

Title

Example in LO750

Comments

Join using tables QALS and QAVE

1. Data source:
Table join

Basis...

SAP AG 1999

Layoutm...

Join Definition: Graphic

Join Definition
Check

Add table

Delete table

INNER or LEFT OUTER link

QALS

QAVE

MANDANT
PRUEFLOS
WERK
ART
...

MANDANT
PRUEFLOS
KZART
ZAEHLER
VKATART
VWERKS
VAUSWAHLMG
...

SAP AG 1999

Table alias

Basis Mode: Basic Structure

Data source

Create QuickView

Information

Online documentation
SAP AG 1999

Creating a QuickView in Basis Mode

QuickView

DEMO

Title

Example in LO750

Comments

Join using tables QALS and QAVE

List fld select.

Fields in list

SAP AG 1999

Sort sequence

Selection fields
Available fields

Data source

Using QuickViews

Ad hoc reports for a user

Each user creates their own QuickViews, which are not
visible to other users
Working with available data quantities
No administrative costs (user group, functional area)
QuickView can be changed into a SAP Query
Link to internal (EIS, ABC, ALV) and external applications
Limited functions in comparison to SAP Query

No transport

SAP AG 1999

Overview: Program and Query

REPORT ...

Program
ABAP

START-OF-SELECTION
...
WRITE ...

Generate program
Describe list
Query painter
Title
Format
Classic

...
SAP AG 1999

Output options
Output options
Line
Field

Organization in the Query

Creates
Functional area
FA1

Plans

Administration

Functional area
FA2
Functional area
FA3

Assigns

User group
UG1

Create
Queries
using
FA1

SAP AG 1999

User group
UG2

Queries
using
FA2

Queries
using
FA3

Creating a Query

Change

User group
UG1

Functional area
FA1

Query

Query

Copy

Functional area
FA2

Query

Query

Create

New query
in FA1
SAP AG 1999

User group
UG2

Functional area
FA1

Query

Copy

Query

Functional area
FA2

Query

Query

Comparison of SAP Query and QuickView

SAP Query
Several partial lists possible
(statistics, ranked lists)

Only basic lists

Local fields can be added

Dataset is limited to the data source

Programs can be linked (report/report

interface)

Report/report interface not available

Query administration required (user

groups, functional areas)

Functional areas must exist

Transport possible

QuickView

SAP AG 1999

No administrative costs since every

user only has access to their own
QuickViews
Easy, quick evaluations possible

Transport not possible

Evaluations: Unit Summary

The standard analyses form an efficient tool for

presenting and analyzing statistical data

effectively in the SAP Business Intelligence
environment.
The logical database provides you with a

selection screen, executes authorization and data

consistency checks, and reads data from the
database according to its hierarchical structure.
You can use the ALV technique to standardize the

output of lists in programs.

You can perform ad hoc evaluations using the

QuickViewer.
SAP Query has more functions than the

QuickView.
SAP AG 1999

Evaluations Exercises

Evaluations Solutions

Archiving

Contents:
Archiving Process
Archiving Objects
Customizing

Organizing the Archiving of QM Data

SAP AG 1999

Archiving: Unit Objectives

At the conclusion of this unit, you will be able to:

Understand the basics of archiving

Give an overview of the archiving options in QM

SAP AG 1999

Archiving: Course Overview Diagram

Course Overview

SAPscript

Basics

Follow-Up Actions

Customer
Enhancements

Interfaces

Status Management/
User Status

Evaluations

Archiving

10

Ease of Use

SAP AG 1999

Archiving: Business Scenario

Our company wants to archive quality data to meet

the requirements set for the storage of such data.

SAP AG 1999

What Can Be Stored?

QM
specialist
Incoming
document

Outgoing
document

Application data
(archive files)

Application data evaluation (print lists)

SAP AG 1999

What Is Data Archiving?

Storing data records from database tables to reduce the number of available
database tables in the system
Reasons for data archiving

Determined by the system

Memory space problems, performance, difficult database administration

Legal specifications and operational requirements

Country-dependent storage requirements, data must be available to
external auditors, potential reusability of data

Data deleted as a record from the tables

Access to archived data controlled by the application

SAP AG 1999

Incorrect Definitions of Data Archiving

Reorganization
The term 'reorganization' is from the time of R/2, when data was downloaded
and then uploaded to optimize the physical distribution of data on the hard
disk. During this operation, data that was no longer needed could be archived
and deleted.
Backup/Restore
By 'backup' we understand a backup of the database contents in case of
breakdown. This enables you to restore the database status to the current
status before the breakdown. As a rule, backups are run at fixed intervals
according to a set procedure. The transfer of data back to the system is known
as the 'restore' procedure.

Archiving Using the SAP ArchiveLink

During archiving, scanned-in, incoming documents are archived in external
systems using the SAP ArchiveLink. This is the same for outgoing documents
created in the SAP System (for example, quality certificates) and print lists.
You can display the archived documents and lists using the SAP ArchiveLink.
In the data archiving function, there is an interface to the SAP
ArchiveLink that you can use to store archive files in an external archive.

SAP AG 1999

Server for Archiving and Deletion Jobs

Frontend:
Administration

Application server:
Deletion

...

...

Background processing
DB server:
Archiving

SAP AG 1999

...

Archiving: Step 1 - Archive

SAP
database

Archiving
program

Archive
file

SAP AG 1999

Archiving: Step 2 - Delete

Archiving
program

SAP
database

SAP
database

Deletion
program

Deletion
program

Deletion
program

SAP AG 1999

Archive
file
Archive
file

Archive
file
Archive
file

Archiving: Step 3 - Options for Storing Archived

Information

Optical archive using ArchiveLink

HSM systems
SAP
database

Deletion
program

SAP AG 1999

Archive
file
Archive
file

Archiving Process

Online

SAP DB

Archiving
object

Archiving session

SAP AG 1999

Archive files

Offline

Archiving Objects

Description of which data should be archived and how it is to

be archived (data model).
Data is bundled into a self-contained business object,
independent of the conditions at the time of archiving.
Programs for creating archive files and deleting data in the
database are contained in these objects.
Further programs are available as required (creating/removing
indices, uploading, evaluating).
Customer settings are assigned to each archiving object.

Accessed from applications- you can define customer-specific

archiving objects for Z tables.

SAP AG 1999

Archiving Objects in Transaction SARA

SARA Archiving
Object name

Schedule initial run

Schedule archiving
Schedule deletion

F4

Schedule postprocessing
Schedule reload

QM_CHARACT

Start evaluation

Manage

SAP AG 1999

Archiving Objects in QM

QM_CHARACT:

QM master inspection
characteristics

QM_CONTROL:

Movement data for quality

inspections

QM_METHOD:

QM inspection methods

QM_PLAN:

QM inspection plan

QM_QMEL:

Quality notification

SAP AG 1999

Customizing

Definition of the logical file names and storage paths

Transaction SARA, up to 4.0 transaction FILE
> Definition of logical file names for all systems
> Definition of logical file paths
> Definition of physical file paths
Settings for general archiving object
Transaction SARA
> Definition of the logical file name
> Size of the archiving file
> Settings for the deletion program
> Variant specifications
Customizing for archiving in external archives

Object-specific Customizing in the application

SAP AG 1999

Organizing the Archiving of QM Master Data (1)

Defining the residence times for inspection methods and

master inspection characteristics in Customizing. There
are no residence times for inspection plans.

Residence time

Valid
from

Defining the deletion sequence.

Recommended sequence:

Task lists

Inspection characteristics

Inspection methods

SAP AG 1999

Archiving
date

Organizing the Archiving of QM Master Data (2)

Prerequisites for deletion:

You must mark task lists with a deletion flag in the task list
header.

There should be no where-used lists for master inspection

characteristics and methods. They should also have status 4.
You can change the status of historical versions for master
records to status 4 within Archiving.

The archiving process:

In the first step, the system automatically changes the status of

the master records from 3 (locked) to 4 (can be archived). This
step, however, only affects historical versions of the master
records; the current versions can only be given status 4
manually.

In the second step, the master records are archived and deleted.

SAP AG 1999

Organizing the Archiving of QM Movement Data

Defining the residence times and deletion times.

You can only delete after archiving.
Residence time
Deletion time
Last change made to the
usage decision

Archiving date
Deletion date

Deletion sequence: Single results

Samples
Characteristics and
operations
Inspection lots

SAP AG 1999

Archiving Session Checklist

Archiving Process
Before the first
archiving session
Coordinate
activities

Before the first session

for a specific archiving object
Coordinate activities

Check Customizing for ADK

Logical file name
Large archive file
ArchiveLink
Deletion program

SAP AG 1999

Coordinate activities

Check dependencies
Check application
Customizing

Check dependencies

Before each archiving

session

Check disk space

Schedule archiving jobs

Check results
Save archiving files

Archiving: Unit Summary

Data archiving is the storage of data records from

database tables. This enables you to reduce the

number of database tables available in the system.
Performance and planning problems escalate

disproportionately relative to the amount of additional

data stored. Therefore, data archiving should be
included in your planning from the outset.

SAP AG 1999