LO750 Quality Management Configuration and Organization

LO750 Quality Management Configuration
and Organization
LO750

Release 46C 13.01.2003

LO750 Quality Management Configuration and Organization.............................................................................. 0-1
Copyright ........................................................................................................................................................... 0-2
Quality Management (QM)............................................................................................................................ 0-3
Prerequisites................................................................................................................................................... 0-4
Target Group.................................................................................................................................................. 0-5
Course Overview................................................................................................................................................ 1-1
Course Goals.................................................................................................................................................. 1-2
Course Objectives .......................................................................................................................................... 1-3
Course Content............................................................................................................................................... 1-4
Course Overview Diagram............................................................................................................................. 1-5
Main Business Scenario ................................................................................................................................. 1-6
Basics ................................................................................................................................................................. 2-1
Basics: Unit Objectives.................................................................................................................................. 2-2
Basics: Course Overview Diagram................................................................................................................ 2-3
Basics: Business Scenario.............................................................................................................................. 2-4
Customizing/IMG (Implementation Guide) ................................................................................................... 2-5
QM Customizing Structure ............................................................................................................................ 2-6
Technical Areas of QM Customizing (1) ....................................................................................................... 2-7
Basics: Unit Summary ................................................................................................................................. 2-10
Customer Enhancements.................................................................................................................................... 3-1
Customer Enhancements: Unit Objectives..................................................................................................... 3-2
Customer Enhancements: Course Overview Diagram................................................................................... 3-3
Customer Enhancements: Business Scenario................................................................................................. 3-4
Enhancing Functions...................................................................................................................................... 3-5
Program Enhancements.................................................................................................................................. 3-6
Customer Enhancement Project ..................................................................................................................... 3-7
SAP Enhancements and Customer Enhancement Projects............................................................................. 3-8
SAP Procedure ............................................................................................................................................... 3-9
Customer Procedure..................................................................................................................................... 3-10
Creating a Customer Enhancement Project.................................................................................................. 3-11
Assigning SAP Enhancements to Customer Project .................................................................................... 3-12
Processing Components ............................................................................................................................... 3-13
Activating Enhancement Project .................................................................................................................. 3-14
Creating a Field Exit .................................................................................................................................... 3-15
Customer Enhancements: Unit Summary .................................................................................................... 3-16
Data for Exercises ........................................................................................................................................ 3-17
Customer Enhancements Exercises.............................................................................................................. 3-18
Customer Enhancements Solutions.............................................................................................................. 3-19
Status Management/User Status......................................................................................................................... 4-1
Status Management: Unit Objectives............................................................................................................. 4-2
Status Management: Course Overview Diagram........................................................................................... 4-3
Status Management: Business Scenario......................................................................................................... 4-4
Using Status Management in QM.................................................................................................................. 4-5
Statuses .......................................................................................................................................................... 4-6
Status Management ........................................................................................................................................ 4-7
Defining Status Profiles ................................................................................................................................. 4-8
Creating Status Profiles.................................................................................................................................. 4-9

Assigning Status Profile to Object Types .................................................................................................... 4-10
Define User Statuses .................................................................................................................................... 4-11
Assigning User Status to Business Transactions.......................................................................................... 4-12
Selection Profile........................................................................................................................................... 4-13
Status Management: Unit Summary ............................................................................................................ 4-14
Status Management Exercises...................................................................................................................... 4-15
Status Management Solutions ...................................................................................................................... 4-16
Ease of Use ........................................................................................................................................................ 5-1
Ease of Use: Unit Objectives ......................................................................................................................... 5-2
Ease of Use: Course Overview Diagram........................................................................................................ 5-3
Ease of Use: Business Scenario ..................................................................................................................... 5-4
Configuration Using Table Control................................................................................................................ 5-5
Field Selection................................................................................................................................................ 5-6
Field Selection (Example: Usage Decision)................................................................................................... 5-7
Variable Lists (Basics) ................................................................................................................................... 5-8
Variable Lists (Field Selection) ..................................................................................................................... 5-9
Variable Lists (Object Selection) ................................................................................................................. 5-10
Results Recording Configuration................................................................................................................. 5-11
Ease of Use: Unit Summary......................................................................................................................... 5-12
Ease of Use Exercises .................................................................................................................................. 5-13
Ease of Use Solutions .................................................................................................................................. 5-14
SAPscript ........................................................................................................................................................... 6-1
SAPscript: Unit Objectives ............................................................................................................................ 6-2
SAPscript: Course Overview Diagram .......................................................................................................... 6-3
SAPscript: Business Scenario ........................................................................................................................ 6-4
SAPscript from User View............................................................................................................................. 6-5
Forms ............................................................................................................................................................. 6-6
The Print Program.......................................................................................................................................... 6-7
Processing Sequence: Form Processor ........................................................................................................... 6-8
Tasks of the Print Program and Form Processor in SAPscript....................................................................... 6-9
Form Print: Start and Finish......................................................................................................................... 6-10
When Do You Modify the Print Program? .................................................................................................. 6-11
Change Procedure (1)................................................................................................................................... 6-12
SAPscript: Unit Summary............................................................................................................................ 6-15
SAPscript Exercises ..................................................................................................................................... 6-16
SAPscript Solutions ..................................................................................................................................... 6-17
Follow-Up Actions............................................................................................................................................. 7-1
Follow-Up Actions: Unit Objectives.............................................................................................................. 7-2
Follow-Up Actions: Course Overview Diagram............................................................................................ 7-3
Follow-Up Actions: Business Scenario.......................................................................................................... 7-4
Defining Follow-Up Actions.......................................................................................................................... 7-5
Follow-Up Actions: Customizing .................................................................................................................. 7-6
Follow-Up Actions: Editing Selected Sets..................................................................................................... 7-7
Follow-Up Actions: Setting the User Status .................................................................................................. 7-8
Follow-Up Actions and Business Transactions.............................................................................................. 7-9
Action Box................................................................................................................................................... 7-10
Customizing for the Action Box (1)............................................................................................................. 7-11

Follow-Up Actions: Unit Summary............................................................................................................. 7-18
Follow-Up Actions Exercises ...................................................................................................................... 7-19
Follow-Up Actions Solutions....................................................................................................................... 7-20
Interfaces............................................................................................................................................................ 8-1
Interfaces: Unit Objectives............................................................................................................................. 8-2
Interfaces: Course Overview Diagram........................................................................................................... 8-3
Interfaces: Business Scenario......................................................................................................................... 8-4
QM-IDI: Data Transfer .................................................................................................................................. 8-5
QM-IDI: Data Transmission .......................................................................................................................... 8-6
QM-IDI: Settings in the SAP System ............................................................................................................ 8-7
QM-IDI: Assignment at Operation Level ...................................................................................................... 8-8
RFC Function Modules for Downloading...................................................................................................... 8-9
RFC Function Modules for Uploading......................................................................................................... 8-10
QM-STI: Statistical Interface....................................................................................................................... 8-11
QM-STI: Calling the Interface ..................................................................................................................... 8-12
QM-STI: Data Structures ............................................................................................................................. 8-13
BAPI: Definition.......................................................................................................................................... 8-14
BAPI: Characteristics................................................................................................................................... 8-15
BAPIs in Quality Management .................................................................................................................... 8-16
Interfaces: Unit Summary ............................................................................................................................ 8-17
Interfaces Exercises...................................................................................................................................... 8-18
Interfaces Solutions...................................................................................................................................... 8-19
Evaluations......................................................................................................................................................... 9-1
Evaluations: Unit Objectives.......................................................................................................................... 9-2
Evaluations: Course Overview Diagram........................................................................................................ 9-3
Evaluations: Business Scenario...................................................................................................................... 9-4
QMIS Standard Analyses............................................................................................................................... 9-5
Organization of Information Structures ......................................................................................................... 9-6
Summarization of Inspection Results............................................................................................................. 9-7
Info Structure for Inspection Results ............................................................................................................. 9-8
Update Rule (by Origin)................................................................................................................................. 9-9
Update Rule (by Notification Type)............................................................................................................. 9-10
Key Figures for the Characteristics.............................................................................................................. 9-11
Generating Lists Using the LDB.................................................................................................................. 9-12
Advantages of the Logical Database............................................................................................................ 9-13
Logical Database: Overview........................................................................................................................ 9-14
ABAP Events and the Logical Database...................................................................................................... 9-15
What Is the ALV Classic?............................................................................................................................ 9-16
Reasons for Developing ALV...................................................................................................................... 9-17
ALV Standard .............................................................................................................................................. 9-18
Set of Generic Functions.............................................................................................................................. 9-19
Basic Principle ............................................................................................................................................. 9-20
Standard Call for ALV................................................................................................................................. 9-21
Field Catalogs .............................................................................................................................................. 9-22
QuickViewer: Overview.............................................................................................................................. 9-23

QuickViewer: Initial Screen......................................................................................................................... 9-24
Creating a QuickView.................................................................................................................................. 9-25
Join Definition: Graphic............................................................................................................................... 9-26
Basis Mode: Basic Structure ........................................................................................................................ 9-27
Creating a QuickView in Basis Mode.......................................................................................................... 9-28
Using QuickViews ....................................................................................................................................... 9-29
Overview: Program and Query .................................................................................................................... 9-30
Organization in the Query............................................................................................................................ 9-31
Creating a Query .......................................................................................................................................... 9-32
Comparison of SAP Query and QuickView................................................................................................. 9-33
Evaluations: Unit Summary ......................................................................................................................... 9-34
Evaluations Exercises .................................................................................................................................. 9-35
Evaluations Solutions................................................................................................................................... 9-36
Archiving ......................................................................................................................................................... 10-1
Archiving: Unit Objectives .......................................................................................................................... 10-2
Archiving: Course Overview Diagram ........................................................................................................ 10-3
Archiving: Business Scenario ...................................................................................................................... 10-4
What Can Be Stored?................................................................................................................................... 10-5
What Is Data Archiving?.............................................................................................................................. 10-6
Incorrect Definitions of Data Archiving ...................................................................................................... 10-7
Server for Archiving and Deletion Jobs....................................................................................................... 10-8
Archiving: Step 1 - Archive ......................................................................................................................... 10-9
Archiving: Step 2 - Delete.......................................................................................................................... 10-10
Archiving: Step 3 - Options for Storing Archived Information ................................................................. 10-11
Archiving Process ...................................................................................................................................... 10-12
Archiving Objects ...................................................................................................................................... 10-13
Archiving Objects in Transaction SARA................................................................................................... 10-14
Archiving Objects in QM........................................................................................................................... 10-15
Customizing ............................................................................................................................................... 10-16
Organizing the Archiving of QM Master Data (1).................................................................................... 10-17
Organizing the Archiving of QM Master Data (2).................................................................................... 10-18
Organizing the Archiving of QM Movement Data .................................................................................... 10-19
Archiving Session Checklist ...................................................................................................................... 10-20
Archiving: Unit Summary.......................................................................................................................... 10-21

SAP AG 1999
LO750 Quality Management Configuration and
Organization
Configuration and Organization
Configuration and Organization

n R/3
n Release 4.6
n August 2000
n Material number 50038677

SAP AG 2001
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.
Copyright

Trademarks:
n Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
n Microsoft
, WINDOWS
, NT
, EXCEL
, Word
, PowerPoint
and SQL Server
are registered
trademarks of Microsoft Corporation.
n IBM
, DB2
, OS/2
, DB2/6000
, Parallel Sysplex
, MVS/ESA
, RS/6000
, AIX
, S/390
,
AS/400
, OS/390
, and OS/400
are registered trademarks of IBM Corporation.

n ORACLE
is a registered trademark of ORACLE Corporation.

n INFORMIX
-OnLine for SAP and INFORMIX
Dynamic Server
TM
are registered trademarks of
Informix Software Incorporated.
n UNIX
, X/Open
, OSF/1
, and Motif
are registered trademarks of the Open Group.

n HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C
, World Wide
Web Consortium, Massachusetts Institute of Technology.
n JAVA
is a registered trademark of Sun Microsystems, Inc.

n JAVASCRIPT
is a registered trademark of Sun Microsystems, Inc., used under license for

technology invented and implemented by Netscape.
n SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow,
SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com
are trademarks or registered trademarks of SAP AG in Germany and in several other countries all
over the world. All other products mentioned are trademarks or registered trademarks of their
respective companies.

SAP AG 1999
Quality Management (QM)
Quality Management
LO170 3 days
Quality Inspections
LO705 3 days
Level 2 Level 3
Quality Notifications
LO710 3 days
QM Organization and
Configuration
LO750 3 days
QM in the Process
Industry
LO721 3 days
QM in Sales and
Distribution / Quality
Certificates
LO725 2 days
QM in
Procurement
LO715 3 days
QM in Discrete and
Repetitive
Manufacturing
LO720 2 days

SAP AG 1999
l Recommended
n R/3 Development Environment
n IMG Basic Concepts
l Required
n BC400 - ABAP Workbench: Basics
n LO705 - Quality Inspections
Prerequisites

SAP AG 1999
l Participants:
n Project team
n Employees responsible for the technical
introduction of the QM component
l Duration: 3 days
Target Group

Notes to the user
n The training materials are not teach-yourself programs. They complement the course instructor's
explanations. On the sheets, there is space for you to write down additional information.

(C) SAP AG LO750 1-1
SAP AG 1999
Course Overview
l Course Goals
l Course Objectives
l Course Content
l Course Overview Diagram
l Main Business Scenario
Contents:

SAP AG 1999
At the conclusion of this course, you will
understand:
l The technical settings in Customizing for the
Quality Management (QM) application component
l Functions that enable additional customer-
specific enhancements without modification
l The archiving of QM data
Course Goals

SAP AG 1999
At the conclusion of this course, you will be able
to define:
l Technical Customizing settings
l The SAP enhancement concept
l SAPscript forms in QM
l Interfaces (QM-IDI, QM-STI, BAPIs)
l The logical database in QM
l Archiving options
Course Objectives

SAP AG 1999
Unit 6 SAPscript
Unit 7 Follow-Up Actions
Unit 8 Interfaces
Unit 9 Evaluations
Unit 10 Archiving
Unit 1 Course Overview
Unit 2 Basics
Unit 3 Customer
Enhancements
Unit 4 Status Management/
User Status
Unit 5 Ease of Use
Preface
Course Content

SAP AG 1999
Course Overview Diagram
Evaluations
9 4
Ease of Use
5
SAPscript
6
Follow-Up Actions
7
Interfaces
8 8
Status Management/
User Status
3
Customer
Enhancements
Archiving
10
Course Overview
1
2
Basics

SAP AG 1999
l Our company wants to introduce the Quality
Management component. As a result, the
company's requirements must be defined in
Customizing for the component.
Main Business Scenario

SAP AG 1999
Basics
Contents:
l Customizing Projects
l QM Customizing Structure
l Technical Areas of QM Customizing

SAP AG 1999
l Show how Customizing functions are linked to the
IMG
l Give an overview of the technical settings in the
QM application component
Basics: Unit Objectives
At the conclusion of this unit, you will be able to:

SAP AG 1999
Basics: Course Overview Diagram
Evaluations
9 4
Ease of Use
5
SAPscript
6
Follow-Up Actions
7
Interfaces
8 8
Status Management/
User Status
3
Customer
Enhancements
Archiving
10
Basics
2
1
Course Overview

SAP AG 1999
l Our company wants to gain an impression of the
configuration options in QM through an overview
of the Implementation Guide and Customizing.
Basics: Business Scenario

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 Edit Project Project Analysis

n The SAP Reference IMG contains all Customizing activities.
n The Project IMG contains the selected Customizing activities.
n The Project IMG can be created in the following ways:
- By selecting application components and countries
- By directly selecting single structure nodes in the SAP Reference IMG (for small projects with
fewer activities)

SAP AG 1999
IMG IMG
Quality Management
Quality Planning
Quality Inspection
Quality Certificates
Quality Notifications
Quality Control
Environment
QM Customizing Structure
Test Equipment Management
QM in Logistics
Basic Settings

n Menu path for Customizing: SAP Easy Access > Tools > AcceleratedSAP > Customizing > Edit
Project
n The Implementation Guide for the QM component is divided into functions. The steps can be
processed in the given order.

SAP AG 1999
l Function Module Assignment
n Quality Planning
w Rules for sample determination
w Valuation rules
w SPC criteria
w Inspection points
n Quality Inspection
w Follow-up actions for the usage decision
w Quality score procedures
w Sample types (FM for label printing)
n Quality Certificates
w Data origin
n Quality Notifications
w Follow-up functions
w Follow-up actions for tasks
Course component
Technical Areas of QM Customizing (1)

SAP AG 1999
l Scheduling a program as a job
n Inspection for deadline monitoring
n Automatic usage decision
l Search helps
n Inspection characteristic
n Inspection method
n Inspection plan
n Quality info record
n Inspection lot
n Certificate profiles
n Quality notifications

SAP AG 1999
l Function enhancements
n Subscreens
n Function keys
n Function modules
l Field selection
l Status management
l List variants
l Condition technique
l Partner concept
l Interfaces
l Distribution of ALE master
data
l Workflow
l Archiving
Course component

(C) SAP AG LO750 2-10
SAP AG 1999
Basics: Unit Summary
l Show that the IMG contains documentation for each
activity. You can execute the activities directly.
l Explain that functions are available for project
management and project documentation.
l Process each Customizing activity using the IMG.
l 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
l Describe how the QM application component offers a
wide range of options for setting up your system to suit
your needs.
You are now able to:

SAP AG 1999
Customer Enhancements
Contents:
l Enhancing Functions
l SAP Enhancements and Customer
Enhancement Projects
l Procedure for SAP and Customers
l Processing Components
l Activating Enhancement Project
l Creating Field Exits

SAP AG 1999
l Understand the enhancement concept at SAP
l Create an enhancement project
Customer Enhancements: Unit Objectives

SAP AG 1999
Customer Enhancements: Course Overview
Diagram
Evaluations
9 4
Ease of Use
5
SAPscript
6
Follow-Up Actions
7
Interfaces
8 8
Status Management/
User Status
2
Basics
Archiving
10
Customer
Enhancements
3
1
Course Overview

SAP AG 1999
l Our company wants to create functional
enhancements that are not in the standard system.
Customer Enhancements: Business Scenario

SAP AG 1999
Is a similar function
available in the SAP Standard?
Can the SAP function be
adapted to suit the customer
using Customizing?
Does the SAP application allow
you to add extra functions using
enhancements?
No
Yes
Yes
No
Yes
No
Customer development Customer development
Customizing Customizing
Enhancement Enhancement
Request enhancement
Avoid modification
Request enhancement
Avoid modification
Enhancing Functions

n Before carrying out a modification, check whether your request can be fulfilled using Customizing or
the enhancement concept.
n You can request enhancements in the SAPNet R/3 Frontend.

SAP AG 1999
Function module
Field 1
Menu 2
Function 1
Function 2
Cust. function
Function 3
Menu 1 Menu 3
Field x
Field y
Program Enhancements
Screen exit
Program exit
Menu exit
Field exit

n You can carry out program enhancements at the following levels:
- In the ABAP module pool (program exit)
- On the Graphical User Interface (GUI) (menu exit)
- In the screen flow logic
- By displaying a subscreen in an area reserved by SAP (screen exit)
- By running a customer-defined code, related to a data element for a field (field exit)
n The following functions are available in the SAP System:
- ABAP statement CALL CUSTOMER-FUNCTION
- Special function codes
- CALL CUSTOMER-SUBSCREEN statement in the screen flow logic
n SAP application programmers must reserve areas for program exits, menu exits, and screen exits.
Field exits, on the other hand, do not need to be planned.

SAP AG 1999
SAP Customer
SMOD
Definition Definition of of SAP SAP
enhancements enhancements
Definition Definition
of of
enhancement enhancement
projects projects
CMOD
Customer Enhancement Project

n SAP application programmers create SAP enhancements using program exits, menu exits, and screen
exits. An administration function is available to the SAP programmer for this purpose (transaction
code SMOD).
n Customers can display a catalog of existing SAP enhancements and can combine the required
enhancements to create an enhancement project. The customer uses an administration function for
this purpose (transaction code CMOD).

SAP AG 1999
SAP
Customer
C
C
C
C
C
E
C
C
C
C
E
E
E
P
E
E
P
C E Component SAP enhancement P Customer enhancement projects
C E
C
SAP Enhancements and Customer Enhancement
Projects

n The components of an SAP enhancement consist of program exits, menu exits, and screen exits.
Each component occurs only once in all SAP enhancements (uniqueness of an SAP enhancement).
n Customer enhancement projects are made up of SAP enhancements. A particular SAP enhancement
can only be used once in all existing customer enhancement projects (uniqueness of a customer
project).

SAP AG 1999
Define customer exits in
application functions
Define customer exits in
application functions
Combine components for
SAP enhancements
Combine components for
SAP enhancements
Document
enhancements
Document
enhancements
Program exits
Menu exits
Screen exits
SAP documentation:
C
C
C
E
SAP Procedure

n SAP application programmers plan possible application enhancements in their applications and
define the required components. They then combine these components to create SAP enhancements.
n Once they have created an SAP enhancement, they document it in such a way that the customer can
later implement the enhancement without extensive analysis of the program and screen sources.

(C) SAP AG LO750 3-10
SAP AG 1999
Create enhancement
project using SAP
enhancements
Create enhancement
project using SAP
enhancements
Process components
for enhancement
project
Process components
for enhancement
project
Document
enhancement project
Document
enhancement project
Function modules
Menu entries
Subscreens
Customer documentation:
E
E
E
P
Activate enhancement
project
Activate enhancement
project
Activate Activate
Customer Procedure

n Customers use the Project Management function to choose the SAP enhancements that they want to
implement. They then process the individual components (also using the Project Management
function) and document the entire enhancement project. Finally they activate the enhancement
project (which in turn activates all components).

(C) SAP AG LO750 3-11
SAP AG 1999
Create Create
Save Save
Creating a Customer Enhancement Project
Project Management
Attribute
Project
Short txt

n First, customers start the Project Management function and give the enhancement project a name.
We recommend you agree on a naming convention. For example, this could be that you include the
name of the transaction or module pool. The project name uniquely identifies the enhancement
project.
n Customers then branch to the project attributes and enter a short text for the enhancement project.
The other attributes (name and time stamp for creating and changing, status) are assigned by the
system.

(C) SAP AG LO750 3-12
SAP AG 1999
Save Save
Assigning SAP Enhancements to Customer Project
Project Management
Project
SAP enhancements
Change SAP Change SAP
enhancements enhancements

n Customers edit the menu exits using Project Management.
n While processing components, customers can open a dialog screen, on which they can enter a
language-dependent, customer-defined description for the additional menu entry.
n Customers cannot change the GUI (Graphical User Interface).

(C) SAP AG LO750 3-13
SAP AG 1999
Change
components
Change
components
Process
components
Process
components
Processing Components
Project Management
Project
SAP enhancements
Editor for
function module
Dialog box Dialog box Dialog box
Lang.
Text
Screen Painter Screen Painter Screen Painter

n Customers process the components in the enhancement project using the Project Management
function.
n Customers branch to the function module editor, a dialog box for text for the menu entry, or the
Screen Painter, depending on whether the component is a function module, menu entry, or
subscreen.

(C) SAP AG LO750 3-14
SAP AG 1999
Activate project Activate project
Activating Enhancement Project
Project Management
Project

n Activating the enhancement project means that all of the components are activated. Once the project
has been successfully activated it has the status active.
n When the project is activated, all programs, screens, and menu interfaces containing components that
belong to the project are regenerated. (Programs are not regenerated until they are started.) Once they
have been activated, the enhancements can been seen in the application functions.
n You can undo the activation of an enhancement project using the deactivation function. Once
deactivated, the project has the status inactive.

(C) SAP AG LO750 3-15
SAP AG 1999
Global enhancements 1
1
Create a field exit
2
2
Create function module
4
4
Field exit for data element ..? 3
3
Activate function module 6
6
Assign program/screen
(for local field exit only)
7
7
Activate field exit
8
8
Process function module 5
5
Display FM: Interface Display FM: Interface Display FM: Interface
Import parameter
Export parameter
INPUT
OUTPUT
ABAP Function Library: Initial screen ABAP Function Library: Initial screen ABAP Function Library: Initial screen
Function module
FIELD_EXIT_<Data element>
Creating a Field Exit

n The function module interface has import parameter INPUT and export parameter OUTPUT. To
transport the field content back to the SAP screen, you have to assign a value to the OUTPUT field
in the source text of the function module.
n Field exits are only considered when a screen is generated, if the profile parameter "abap/fieldexit =
YES" is set on all application servers.
n The following ABAP statements are not allowed in the function modules of field exits:
- BREAK-POINT
- CALL SCREEN, CALL DIALOG, CALL TRANSACTION, SUBMIT
- COMMIT WORK, ROLLBACK WORK
- COMMUNICATION RECEIVE
- EXIT FROM STEP-LOOP
- MESSAGE I, MESSAGE W
- External PERFORM
n Field exits cannot be processed with the debugger.

(C) SAP AG LO750 3-16
SAP AG 1999
l SAP application programmers plan program
exits, menu exits, and screen exits for the
application and combine them to form SAP
enhancements.
l Customers create an enhancement project
using the SAP enhancements.
Customer Enhancements: Unit Summary

(C) SAP AG LO750 3-17
Data for Exercises
Explanation of symbols in the exercises and solutions

Exercises

Solutions

Course Objectives

Business Scenario

Tips & Tricks

Warning or Caution

Data in the exercises
Data type Data in the training system
Status profile ZGR##
Selection profile ZGR1##, ZGR2##
Inspection type Z01GR##
Variant (list/selection screen) ZGR##
Display variant (list/selection
screen)
ZGR##
Form for inspection report ZGR##
Print program ZQDRGR##
Function group: ZQ##
Function module: Z_ZQ##_REPORT
Follow-up action: ZGR##
Selected set: ZGR##
Evaluation program ZQSTAT##
Program (ALV) ZQALV##
Evaluation (QuickView) QV##

(C) SAP AG LO750 3-18
Customer Enhancements Exercises

Unit: Customer Enhancements
Topic: Customer Enhancements

At the conclusion of these exercises, you will be able to:
Create an enhancement project

Users want to enhance a quality notification with another function code.
The enhancement should make it possible to switch to the stock
overview.
1-1 Find the enhancement that you can use to activate an additional function code
within a quality notification.
1-1-1 What is this enhancement called?
_________________________________
1-1-2 Check whether the enhancement is already being used in a project.
______________________________________________________
1-2 Edit the enhancement project in such a way that it enables you to switch from the
quality notification to the stock overview.

1-3 Check whether your enhancement works.

(C) SAP AG LO750 3-19
Customer Enhancements Solutions

Unit: Customer Enhancements
Topic: Customer Enhancements
1-1 Enhancement
1-1-1 QQMA0003.
1-1-2 No, because an enhancement can only be used in one project.
1-2 Text for the function code: Stock overview
Coding in the include for the function module:
SET PARAMETER ID MAT FIELD I_VIQMEL-MATNR.
CALL TRANSACTION MMBE AND SKIP FIRST SCREEN.
1-3 Activate the project, then test the quality notification to see whether the customer
exit has been correctly run.

SAP AG 1999
Status Management/User Status
Contents:
l Using Status Management
l Defining and Creating a Status Profile
l Assigning Status Profile to Object Types
l Defining and Assigning User Status to
Business Transactions
l Selection Profile

SAP AG 1999
l Use general status management
l Define your own user statuses in addition to
the existing system statuses and assign
them to objects
l Create and use selection profiles
Status Management: Unit Objectives

SAP AG 1999
Status Management: Course Overview Diagram
Evaluations
9
2
Ease of Use
5
SAPscript
6
Follow-Up Actions
7
Interfaces
8 8
Basics
3
Customer
Enhancements
Archiving
10
Status Management/
User Status
4
1
Course Overview

SAP AG 1999
l Our company wants to create business
transactions using system and user statuses.
Status Management: Business Scenario

SAP AG 1999
Quality
notification
Quality
certificate
Inspection
lot
Status profile
Quality info
record
Using Status Management in QM
Status profile
Status profile
Status profile

n General status management is used in the following QM objects:
Quality information record (supply relationship)
Inspection lot
Quality certificate
Quality notification

SAP AG 1999
Performing a
transaction
for example,
- Releasing
- Closing
Number of
active statuses
Number of
executable
transactions
changes defines
Statuses

n The current processing status of an object is documented using one or more statuses.
n A status is an indicator with the following functions:
It indicates that a certain condition has been reached (for example, "Usage decision made").
It influences the number of business transactions that can be performed.
n If a business transaction is carried out, it can, in turn, set or delete one or more statuses for the
affected object.
n You can set any number of statuses for an object.

SAP AG 1999
INSP:
INSP:
REL:
REL:
Inspection active
Released
RREC:
RREC:
CALC:
CALC:
CCTD:
CCTD:
PASG:
PASG:
PRII:
PRII:
Results confirmed
Sample calculated
Insp. characteristics created
Plan/specification assigned
Inspection instruction printed
System status
XXXX:
XXXX: Freely defined
User status
Status Management

n A system status is set by the system and informs the user that a certain function has been completed
for an object. You cannot influence this status unless you carry out a transaction that leads to a
change in the system status.
n A user status is defined by the user and can be set for a status object (such as an inspection lot) in
addition to the system status.
You can use only one user status from the status profile (defined in Customizing) assigned to each
status object.
You can extend control of the business transactions by the system status using the user status. The
user status can be set or deleted manually or through business transactions.

SAP AG 1999
Create status profile Create Create s status profile tatus profile
Assign status profile to
object types
Assign Assign status status profile profile to to
object types object types
Define user status Define user status Define user status
Assign user status
to business
transactions
Assign user status Assign user status
to to business business
transactions transactions
Defining Status Profiles

SAP AG 1999
Creating Status Profiles
New Entry
Status profile
Maintenance language
Text
LO750_00
Rel. visual inspection
EN
Create
status profile
Create Create
s status profile tatus profile

n To create a status profile, proceed as follows:
1. Choose Edit -> New entry.
2. Enter any status profile name.
3. Enter a descriptive text.
4. Specify a maintenance language for the status profile. You can only make changes and
additions to the status profile in the maintenance language. These must then be translated into
the required foreign languages. This ensures that entries are complete and unique.
5. Press Enter to add the new status profile to the list.
6. Choose Save.

(C) SAP AG LO750 4-10
SAP AG 1999
Permitted object types Permitted object types
Task Task
Insp Insp. . lot with lot with plan plan and chars and chars
Insp Insp. . lot with lot with plan w/o plan w/o chars chars
Insp Insp. . lot lot w/o plan w/o plan or chars or chars
Quality info record Quality info record
Quality notification Quality notification
Quality certificate profile Quality certificate profile
Partial lot Partial lot
Assigning Status Profile to Object Types
Assign status profile to
object types
Assign status profile Assign status profile to to
object types object types

n To be able to use a status profile for objects of a certain object type, you have to assign the status to
the affected object type:
1. On the screen Change Status Profile: Overview, place the cursor on the status profile
that you want to assign to an object type.
2. Choose Goto -> Object types.
3. Select object types for which the status profile can be used.
4. Choose Save.

(C) SAP AG LO750 4-11
SAP AG 1999
User status User status
Status
number
Status Short text
Long
text
Init.
status
Lowest
status no.
Highest
status no.
Auth.
code
Priority Position
1 LKD No visual inspection 1 3 1 1
2 CNF Confirmed 1 3 1 1
3 REL Release 1 3 1 1
Define User Statuses
Define user status Define user status Define user status

n You must enter a four-character (maximum length) language-dependent ID to identify each user
status.
n For each user status, you can enter the following:
a) Enter a status number in the Status number field. The status number determines the order in
which the status of a status profile can be set.
b) Enter a highest and lowest status number in the relevant columns.
c) Enter a short text. The short text contains a short description of the status.
d) Enter a long text for the user status. To do this, choose Goto -> Long text.
e) Mark one user status as the initial status, if required. It is then set automatically when an
object is created. For each status profile, you may define only one status with a status number as
the initial status, but any number of statuses without a status number.
f) In the Position column, define the item, for which the status is displayed in the toolbar of the
inspection lot.
g) In the Priority column, define the priority of the user status if the same position is specified
for more than one active status.
h) Save your entries.

(C) SAP AG LO750 4-12
SAP AG 1999
Transaction control Transaction control
Business transaction No influence Allowed Warning Disalld No action Set Delete
Status profile
Status profile LO705-00
Status
Status LKD
Make usage decision
Assigning User Status to Business Transactions
Assign user status
to business
transactions
Assign user status
to business
transactions

n To assign business transactions to your user status, proceed as follows:
1. Position the cursor on the user status.
2. Choose Goto -> Business transaction control.
3. Choose Edit -> New entries to display a list of the available business transactions.
4. Assign the appropriate transactions to your user status.
5. By setting the indicators, you can activate the following fields for each transaction: No
influence, Allowed, Warning, Disalld.
The following prerequisites must be fulfilled before a business transaction can be carried out:
- The transaction must be permitted by at least one active status.
- The transaction must not be disallowed by any active status.
6. Using "Follow-up actions" you can determine how a specific transaction affects the
respective status when it is performed.
7. Save your entries.

(C) SAP AG LO750 4-13
SAP AG 1999
and / or
l Inclusive
l Exclusive
l Active
l Inactive
l Never active
l l Inclusive
l l Exclusive
l l Active
l l Inactive
l l Never active
l System status 1 l l System status 1
and / or
and / or
and / or
l Inclusive
l Exclusive
l Active
l Inactive
l Never active
l l Inclusive
l l Exclusive
l l Active
l l Inactive
l l Never active
l System status 2 l l System status 2
Without status profile
l Inclusive
l Exclusive
l Active
l Inactive
l Never active
l l Inclusive
l l Exclusive
l l Active
l l Inactive
l l Never active
l System status 1 or
user status 1
l l System status 1 or
user status 1
With status profile
l Inclusive
l Exclusive
l Active
l Inactive
l Never active
l l Inclusive
l l Exclusive
l l Active
l l Inactive
l l Never active
l System status 2 or
user status 2
l l System status 2 or
user status 2
Selection Profile

n You can use selection profiles to define the status combinations for selecting objects (such as
inspection lots). A selection profile is especially helpful if you want to repeatedly select a large
number of objects according to the same selection criteria.
n You can specify a system status as well as a user status in the selection profile. If you also want to
select objects according to user status, you must specify the corresponding status profile.
n The selection criteria are evaluated top-down. The following rules apply:
Several consecutive lines linked by OR are combined to form a block and are evaluated
together. This block must fulfill at least one of the selection criteria.
AND links these blocks or individual criteria. All blocks or individual criteria linked by AND
must be fulfilled. An order is eliminated from the evaluation if even one block or individual
criterion is not fulfilled.
OR link is stronger than AND link
n For greater efficiency, criteria that greatly limit the selection should be put at the beginning of the
selection profile.

(C) SAP AG LO750 4-14
SAP AG 1999
l Status management is used in the following QM objects: Quality
info record, inspection lot, quality certificate, quality notification.
l The SAP System differentiates between system status and user
status. The system status is defined by SAP, and the user status is
freely defined.
l 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.
l You can define a status profile and user status in several
languages.
l You can use selection profiles to define status combinations for
selecting objects.
Status Management: Unit Summary

(C) SAP AG LO750 4-15
Status Management Exercises

Unit: Status Management
Topic: Status Management/User Status

Create a status profile for an inspection type

When inspecting a goods receipt, a visual inspection is always carried out
first. Only when the visual inspection has been successfully completed
can other inspections take place.
1-1 Create a status profile that enables you to carry out the scenario given above.
Status profile: ZGR##
1-2 Create two selection profiles:
- Released lots
- Lots not yet released
Selection profile: ZGR1##
ZGR2##
1-3 Create your own inspection type for origin 01 and assign your status profile to this
inspection type.
Inspection type: Z01GR##
1-4 Check your status profile.

(C) SAP AG LO750 4-16
Status Management Solutions

Unit: Status Management
Topic: Status Management/User Status
1-1 Status management in Customizing under quality inspection.
Create a status profile for the inspection lot: Release after visual inspection
(transaction BS02).

1-2 Assign object types (pushbutton Object types). Allow the object types "Insp. lot
with plan w/o char.", "Insp. lot with plan and char.", and "Insp. lot w/o plan or
char.".
Define the user statuses (LKD, CNF, and REL).
Make a setting so that the usage decision cannot be made with the LKD status.

1-3 In Customizing, choose Quality Inspection Inspection Lot Creation
Maintain Inspection Types.
Assign the status profile on the detail screen for the inspection type.

1-4 Create an inspection lot whose initial status is "LKD". Perform a visual inspection
and note that a new user status is assigned to the inspection lot etc.

SAP AG 1999
Ease of Use
Contents:
l Configuration Using Table Controls
l Field Selection
l Variable Lists
l Results Recording Configuration

SAP AG 1999
l Customize the SAP interface to suit a user's
requirements using field selection, list
variants, and table control
l Configure results recording
Ease of Use: Unit Objectives

SAP AG 1999
Ease of Use: Course Overview Diagram
Evaluations
9 4
Basics
2
SAPscript
6
Follow-Up Actions
7
Interfaces
8 8
Status Management/
User Status
3
Customer
Enhancements
Archiving
10
Ease of Use
5
1
Course Overview

SAP AG 1999
l Our company wants to individually configure its
SAP interfaces.
Ease of Use: Business Scenario

SAP AG 1999
l Change column order
l Change column width
l Create variant
u Current setting
u Standard setting
l Delete variant
10
20
30
40
Item Req. qty. Material Short text I A
10
20
30
40
Item Req. qty. Material Short text I A
Configuration Using Table Control

n Table control can be set as user-dependent. The width and position of a column can be configured
(using Drag&Drop). The current display can be saved as a variant.
n In addition, there are system variants that apply to all users client-wide. They are edited using the
function "Administrator". This function is linked to the authorization object S_ADMI_FCD.
n The user-dependent variant takes precedence over the system variant.

SAP AG 1999
1. Upper limit
1. Lower limit
Selected set
Basic sample quantity
Info field 1
General General
Dependent on values of Dependent on values of
influencing fields influencing fields
Modifiable field Input Req. Disp. Hide
Module pool
Screen group
Influencing field
Influencing value
Field Selection

n Determine the name of the program, to which the screen belongs. To do this, call up the screen in
question and choose System -> Status.
n To find out which customer-defined field control is planned for which screen groups in a module
pool, enter the name of the module pool in the maintenance function (transaction SFAC) and choose
Display. The system displays a list of all the screen groups. You can display a list of modifiable
fields for each screen group in the list.
n For the modifiable fields, you use indicators to define how each field is displayed on the screen.

SAP AG 1999
Module pool SAPMQEVA
Screen group Insp. lot: UD
Batch status mgmt
Dependent on values of Dependent on values of
influencing fields influencing fields
Modifiable field Input Req. Disp. Hide
Influencing field
Influencing value
Field Selection (Example: Usage Decision)
Batch
requirement

SAP AG 1999
Variable Lists (Basics)
Definition of list variants
1. Field selection Display variant
2. Object selection Selection screen
Definition levels
Customizing: Transaction variant
(generally valid)
Application transaction: User-specific variant
General variant

You define list variants in two steps:
1. Field selection: In this step, you define the fields and the sequence for the list display. You
choose from a selection of fields proposed by the system. You can number the selected fields,
or identify them as hidden.
This field selection has an automatic transport link. Users can also create their own selection list
from within the application transaction. This user-specific field selection does not belong to
Customizing and does not have a transport link. If users do not define their own field selection,
the fields that are selected in this step are displayed.
2. Object selection: You define the selection criteria used to select the objects for the list. For
each function (transaction) that is directly executable from this list, you can define exactly one
general variant with the accompanying selection criteria. The system saves this general variant
as SAP_TCODE_xxxx. (xxxx is the transaction code that generates the respective list.) These
general variants have an automatic transport link. In addition to the general variant, you can also
define a user-specific variant for each executable function. The system saves this variant as
U_<user name>. You can also define any number of other variants for each executable function
and save them under any name (from within the application).

SAP AG 1999
Column content
Inspection lot
Item
Material
Plant
Insp. lot quantity
...
Length
Line : 1
Column content
Material document
Posting date
Dyn. modification
Insp. stage
...
Length
Hidden fields
1
2
3
4
12
18
4
6
10
10
4
5
Variable Lists (Field Selection)

n You can change the list display using display variants.
n The following functions are available:
You can limit the list of hidden fields according to the criteria, as required (field group).
You can hide or show all fields or individual fields.
Using Sort in ascending order or Sort in descending order, you can sort the hidden fields
according to column content.
The order of the columns in the list is defined by the item number in the Item field.
In the Length column, you can change the required length of a field if this should differ from the
standard setting.
If it is possible to calculate totals and subtotals in a column, in the display fields beneath Total you
can define whether totals and subtotals are to be shown in the display variant above this Total
column.
You can use a clipboard to cut a field from the display fields or the hidden fields and paste it in the
required place in the display fields.
The columns can be grouped together in up to three rows.

(C) SAP AG LO750 5-10
SAP AG 1999
Selection profile
Lot created
Plant
Lot origin
...
Field name Type P I N L P L O
T: Table variable from TVARV
D: Dynamic date calculation
B: User-specific variable
Selection criteria T D B
Name of variables
QL_ENSIB
Current date - xxx, current date + yyy
Selected
Not selected
Not supported
T: Table variable from TVARV
D: Dynamic date calculation
B: User-specific variable
Variable Lists (Object Selection)
P
S
S
S

n Type
The Type field shows whether the type is a parameter (P) or a select option (S).
n P (Protect field) selected:
The corresponding selection criterion cannot be entered at the start of the program using this variant.
n I (Hide field) selected:
The corresponding selection criterion is not displayed at the start of the program using this variant.
However, the selection criterion can still be supplied with values in the variant.
n N (Hide field until)
n L (Selection variable) selected:
The selection criterion is supplied with values from the variant variables at the start of the program.
To select variant variables, choose SELECTION VARIABLES.
n P (Save field without values) selected:
The value of the corresponding selection criterion is not changed in the program at the start using the
variant or by getting a variant.
n L (Switch SPA/GPA off)
n O (Required field)

(C) SAP AG LO750 5-11
SAP AG 1999
No.
10
Status
20
30
40
...
1
1
1
1
...
Characteristic
Diameter
Streaks
Color
Inspection lot
Operation
:
:
4711
10
Status
Characteristic
closed
Surface
Close on CONTINUE
Close on saving
Skip CH view
Results Recording Configuration
Customizing
recording
configuration
Customizing
recording
configuration
5
User
parameters
User
parameters

n Results recording can be made easier by configuring the recording procedure.
n You can predefine the recording configuration in a table (Customizing).
n You can configure user-dependent specifications and store them in the user values (for example,
close on saving results data).

(C) SAP AG LO750 5-12
SAP AG 1999
l In QM there are a number of ways to define
(set) fields to suit the needs of every
company and user:
n Table control
n Field control
n Variable lists
l By configuring results recording, you can
simplify the recording procedure.
Ease of Use: Unit Summary

(C) SAP AG LO750 5-13
Ease of Use Exercises

Unit: Ease of Use
Topic: Ease of Use

Adapt table controls, field selection, and list views
Configure results recording

A user should only have certain elements displayed on their screen.
1-1 Select a screen with table control (for example, results recording or usage decision)
and change the settings so that the screen corresponds to your company
requirements.

1-2 Find an example for field selection and test it out.

1-3 Select a worklist (for example, results recording or inspection) and change the
selection screen and list according to your requirements.
Variant: ZGR##
Display variant: ZGR##
1-4 Try and optimize results recording using the results recording configuration. Do
this according to your company requirements.

(C) SAP AG LO750 5-14
Ease of Use Solutions

Unit: Ease of Use
Topic: Ease of Use
1-1 Table control
Set the table control directly in the application transaction, for example, in
transaction QA12 (Change usage decision with history).
1-2 Field selection
Example: The pushbutton Batch status should be hidden for materials that do not
have to be managed in batches.
Customizing: System Modification Adapt Field Selection (transaction SFAC)
Module pool: SAPMQEVA
Change
Influencing fields
Double-click on batch management (QALSXCHPF)
Influencing value:
Set Batch status to hidden.
Save.
1-3 List variants
Define transaction variants in Customizing (Quality Inspection
List Definition)
Also define display variants here.
Define user variants, general variants, and other display variants in the application
transaction.
1-4 Results recording configuration
Define the results recording configuration in Customizing:
Quality Inspection Results Recording Define Recording Configuration
Define the configuration key in Customizing for plant settings.
You can make user-specific settings directly in results recording by switching to the
user parameters.

SAP AG 1999
SAPscript
Contents:
l Forms and Print Programs
l Processing Sequence: Form Processor
l Procedure for Changes

SAP AG 1999
l Explain the basics of SAPscript
l Describe the principle relationship between a print
program and form
l Show how you can also read data in a form
SAPscript: Unit Objectives

SAP AG 1999
SAPscript: Course Overview Diagram
Evaluations
9 4
Ease of Use
5
Basics
2
Follow-Up Actions
7
Interfaces
8 8
Status Management/
User Status
3
Customer
Enhancements
Archiving
10
SAPscript
6 1
Course Overview

SAP AG 1999
l Our company wants to create forms and print
programs using the SAPscript editor.
SAPscript: Business Scenario

SAP AG 1999
Text editor
Layout
(forms, styles)
Programming
interface Form processor
Database
Maintenance
transactions
Application
transactions
ABAP
Workbench
ABAP
Workbench
User
SAPscript from User View

n SAPscript consists of 5 basic components:
- An editor for the entry and editing of text lines. This component is called up from the
application transactions, if a user wants to maintain texts for an application object.
- Styles and forms for structuring printouts. They are created independently of individual texts
using the appropriate maintenance transactions, and then assigned to individual texts.
- The form processor (composer) is the main component for output formatting. It is used to
prepare a text with the appropriate formatting information for a particular output device. This
information is taken from the style and form that have been defined.
- A programming interface that allows the integration of SAPscript components in customer
application programs and the program-controlled creation of output using forms.
- Various database tables for storing texts, styles, and forms.

SAP AG 1999
Form 2
Form 2
Form 1
Form 1
Form 3
Form 3
Dear...
Invoice
Document
Forms

n A form defines the appearance and the layout of a document.
n A form is used for each SAPscript text printout.
n Forms can already contain standardized text modules with placeholders for variable data. The
application can call up and print the modules as necessary.
n For layout changes, such as moving a printed area of text, changing the font, paragraph formatting,
and tab settings, you simply change the form.
n The SAPscript transaction used to edit forms can be reached from the SAP initial screen by choosing
Tools-> SAPscript -> Form.
n The best way to create your own forms is to copy an existing form and then make the necessary
changes to your copy (Customizing of forms).

SAP AG 1999
Print program
Application transaction
Form 2
Form 2
Form 1
Form 1
Form 3
Form 3
The Print Program
SAP DB SAP DB

n The print program:
- Controls the actual text output on the printer, screen, or fax machine
- Selects data from the database or from user entries
- Selects a form and controls the texts to be printed on this form, together with the order and
frequency in which they are to be printed
- Determines the print characteristics, such as the output device, immediate printout, and copies

SAP AG 1999
Invoice
Document
Document
Print program
Application transaction
Form:
Form:
Form processor
I n v o i c e
Processing Sequence: FormProcessor
SAP DB SAP DB

n The interaction of the print program and form help you to create documents to suit your needs.
n The printing of the form is initiated by the print program. Each command sent by the function
modules of the SAPscript programming interface is relayed to the form processor.
n The form processor retrieves layout information from the form selected by the print program. Texts
identified by the print program to be issued are prepared by the form processor according to this
layout.
n If the texts contain variables, the form processor replaces these either with values from the system
(for example, the current date) or with application data selected by the program.
n The completion of the form is controlled by the print program. Once the form has been completed,
the form processor transfers the finished document, for example, to the spool.

SAP AG 1999
Form
processor
this
request, and
that
this meets
your
requirements
your
request,
and
hope that
this
request
meets
your requirements
Chicago StateBank
Acc. no: 08154711
Sort code:000000000
Mr D. Test
7 Old Road
47110 Irving Chicago, 3rd June
Invoice no. 4
123-45-556-678
Type.No. Price
00345 200.-
00379 150.-
02378 50.-
00458 300.-
Total 700.-
Print program
report jh_form_01.
tables: scustom.
select * from scustom...
......
call function 'OPEN_FORM'
......
call function WRITE_FORM'
......
call function CLOSE_FORM'
......
ABAP ABAP
report report
Application
data
Form:
DB
Tasks of the Print Program and Form Processor in
SAPscript

n The interaction of the print program and form template allows you to issue printed documents within
the SAP System. The print program is either an ABAP report or a module pool.
n The print program:
- Is responsible for retrieving SAP application data from the database. It also defines how the
form is to be processed, that is the order and repetition of text elements (flow logic), selects a
form template for the printout and determines the output medium (for example, printer, screen,
fax, e-mail), together with special print characteristics (immediate print, copies, page selection,
etc.)
n The SAPscript form processor is responsible for formatting the document for printing, for example:
- Line/page breaks on the form, formatting of SAPscript control commands and symbol variables,
integration of long texts, generation of the page description for the spool request (final format
and OTF).

(C) SAP AG LO750 6-10
SAP AG 1999
CALL FUNCTION CALL FUNCTION 'OPEN_FORM' 'OPEN_FORM'
EXPORTING EXPORTING
FORM FORM = . = . . . . .
LANGUAGE LANGUAGE = . = . . . . .
DEVICE DEVICE = . = . . . . .
OPTIONS OPTIONS = . = . . . . .
DIALOG DIALOG = . = . . . . .
IMPORTING IMPORTING
LANGUAGE LANGUAGE = . = . . . . .
EXCEPTIONS ... EXCEPTIONS ... = . . . = . . .
CALL FUNCTION CALL FUNCTION 'CLOSE_FORM' 'CLOSE_FORM'
IMPORTING IMPORTING
RESULT RESULT = . = . . . . .
EXCEPTIONS ... EXCEPTIONS ... = . . . = . . .
Form Print: Start and Finish

n Function module OPEN_FORM initializes the form print. This function must be called before other
form functions can be used.
n The FORM and LANGUAGE parameters specify the form and requested language.
n The DEVICE parameter controls the output medium (PRINTER, TELEFAX, SCREEN).
n The OPTIONS parameter (Structure ITCPO) allows you to specify attributes for the printer or fax
control, for example, number of copies or immediate print.
n The DIALOG parameter allows you to suppress an entry screen for device parameters (for example,
device names: DEVICE = PRINTER, DEVICE = TELEFAX).
n The form print must be ended with CLOSE_FORM so that the output can be carried out.
n Once the form print has been completed, the RESULT parameter (Structure ITCPP) contains status
information and print or fax parameters.

(C) SAP AG LO750 6-11
SAP AG 1999
Structural changes Structural changes
New New text elements text elements
are needed are needed
Additional data Additional data
is required is required
Using Using the the print print
program program to to print print
another another form form
When Do You Modify the Print Program?

n Changes to SAP objects are called modifications.
n The modified object is not protected against change during an upgrade. Therefore, you use a copy of
the print program supplied by SAP to make your modifications.
n However, you should consider whether modifications to the print program are absolutely necessary.

(C) SAP AG LO750 6-12
SAP AG 1999
Which new fields and
tables are needed?
Which new fields and
tables are needed?
Which program and form
are used?
Which program and form
are used?
Are the necessary fields
contained in the existing
tables, or are new
fields and tables required?
Are the necessary fields
contained in the existing
tables, or are new
fields and tables required?
Change Procedure (1)

n In addition to the standard data that is available, you occasionally need other data.
n Find out which additional fields are required. Are these fields available in existing tables, or are
other tables required? Do the required table fields contain data?
n Look in Customizing for the application component and check which form and program are
currently used for this.

(C) SAP AG LO750 6-13
SAP AG 1999
Does the print program
need to be modified, or
only the form?
Does the print program
need to be modified, or
only the form?
Do SAP enhancements
already exist in the form of
customer exits?
Do SAP enhancements
already exist in the form of
customer exits?
Can the missing data be
supplied from another
program using PERFORM?
Can the missing data be
supplied from another
program using PERFORM?

n Determine whether you only need to modify the form, or whether the print program also has to be
modified.
n Ensure that the PERFORM command in SAPscript can also be used to retrieve data.
n Insert the PERFORM command in the form and define the called subprogram as your own program
in the customer name space. The subroutine then retrieves the required data.
n In some cases, SAP application developers have planned includes that you can use to integrate
enhancements. These customer exits are not changed in the event of an upgrade. They do not have to
be modified.

(C) SAP AG LO750 6-14
SAP AG 1999
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

n Make as few modifications as possible. Use the SAP standard as a template for enhancements.
n Use the SAP standard form to modify a form and copy it to the customer name space Z or Y. Modify
the copied form.
n When making structural changes to the form, you must also adjust the print program accordingly.
n Copy the print program to the customer name space Z or Y. Modify the copied program.
n Define the new form and, if required, the print program in Customizing.
n Test your modifications.

(C) SAP AG LO750 6-15
SAP AG 1999
l 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.
l The QM application component contains a variety of
forms and print programs. You can modify these
forms and programs to suit your needs.
SAPscript: Unit Summary

(C) SAP AG LO750 6-16
SAPscript Exercises

Unit: SAPscript
Topic: Forms and Print Programs

Create forms and the corresponding print programs

You want to create company-specific reports, for example, inspection
reports, and then print them.
1-1 Create the form for an inspection report. Do this by copying the existing form and
then changing the copy to meet your specifications.
Form: ZGR##
1-2 Create a print program specifically for your form.
Program: ZQDRGR##

(C) SAP AG LO750 6-17
SAPscript Solutions

Unit: SAPscript
Topic: Forms and Print Programs
1-1 Form
Transaction SE71 (Tools SAPscript Form
Utilities Copy from Client)
Use form QM_INSP_RESULT as a copy model.

Text elements in the form
/E HEADER
/* This text element contains the header information for an inspection lot
U1 Inspection report
S1 Inspection lot,,&QALS-PRUEFLOS&,,&QALS-KTEXTLOS&
/S1 Material,,&QALS-MATNR&,,&QALS-KTEXTMAT&
/*
/E CHARACTERISTIC
/* Only print rejected characteristics
/: IF &QAMR-MBEWERTG& = 'R'
TX Characteristic,,&QAMV-MERKNR&,,&QAMV-
KURZTEXT&,,valuation,,&QAMR-MBEWERTG&
/: ENDIF
/* End of form

1-2 Print program
REPORT ZQDRGR00.

TABLES:
QALS,
QAMV,
QAMR.

(C) SAP AG LO750 6-18
PARAMETERS:
P_LOS LIKE QALS-PRUEFLOS OBLIGATORY.

DATA:
G_QAMV_TAB LIKE QAMV OCCURS 0,
G_QAMV_TAB LIKE QAMV OCCURS 0,

* Data procurement

* Inspection lot
SELECT SINGLE * FROM QALS
WHERE PRUEFLOS = P_LOS.

CHECK SY-SUBRC EQ 0.

* Characteristic specifications
SELECT * FROM QAMV INTO TABLE G_QAMV_TAB

IF SY-SUBRC EQ 0.
* Results
SELECT * FROM QAMR INTO TABLE G_QAMR_TAB

ENDIF.

(C) SAP AG LO750 6-19
* Output

CALL FUNCTION 'OPEN_FORM'
EXPORTING
* APPLICATION = 'TX'
* ARCHIVE_INDEX = ' '
* ARCHIVE_PARAMS = ' '
* DEVICE = 'PRINTER'
* DIALOG = 'X'
FORM = 'ZGR00'
* LANGUAGE = SY-LANGU
* OPTIONS = ' '
* MAIL_SENDER = ' '
* MAIL_RECIPIENT = ' '
* MAIL_APPL_OBJECT = ' '
* RAW_DATA_INTERFACE = '*'
* IMPORTING
* LANGUAGE =
* NEW_ARCHIVE_PARAMS =
* RESULT =
EXCEPTIONS
CANCELED = 1
DEVICE = 2
FORM = 3
OPTIONS = 4
UNCLOSED = 5
MAIL_OPTIONS = 6
OTHERS = 7.

*----------- Print
* Header
CALL FUNCTION 'WRITE_FORM'
EXPORTING
ELEMENT = 'HEADER'

(C) SAP AG LO750 6-20
* FUNCTION = 'SET'
* TYPE = 'BODY'
* WINDOW = 'MAIN'
* IMPORTING
* PENDING_LINES =
EXCEPTIONS
ELEMENT = 1
FUNCTION = 2
TYPE = 3
UNOPENED = 4
UNSTARTED = 5
WINDOW = 6
BAD_PAGEFORMAT_FOR_PRINT = 7
OTHERS = 8.

* Characteristics
LOOP AT G_QAMV_TAB INTO QAMV.
READ TABLE G_QAMR_TAB INTO QAMR
WITH KEY PRUEFLOS = QAMV-PRUEFLOS
VORGLFNR = QAMV-VORGLFNR
MERKNR = QAMV-MERKNR.

(C) SAP AG LO750 6-21
IF SY-SUBRC EQ 0.
CALL FUNCTION 'WRITE_FORM'
EXPORTING
ELEMENT = 'CHARACTERISTIC'
* FUNCTION = 'SET'
* TYPE = 'BODY'
* WINDOW = 'MAIN'
* IMPORTING
* PENDING_LINES =
EXCEPTIONS
ELEMENT = 1
FUNCTION = 2
TYPE = 3
UNOPENED = 4
UNSTARTED = 5
WINDOW = 6
OTHERS = 8.
ENDIF.
ENDLOOP.
*---------------
CALL FUNCTION 'CLOSE_FORM'
* IMPORTING
* RESULT =
* RDI_RESULT =
* TABLES
* OTFDATA =
EXCEPTIONS
UNOPENED = 1
OTHERS = 3.

(C) SAP AG LO750 6-22
Printing the material group (MARA-MATKL).
Enhance the form by PERFORM ENDPERFORM.

Create program: ZQDRGF00
REPORT ZQDRGF00.
TABLES:
MARA.
*----------------------------------------------------------------------*
* FORM .......
*----------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM MARA_LESEN
TABLES IN_PAR_TAB STRUCTURE ITCSY
OUT_PAR_TAB STRUCTURE ITCSY.
READ TABLE IN_PAR_TAB
WITH KEY NAME = 'QALS-MATNR'.
CHECK SY-SUBRC EQ 0.
SELECT SINGLE * FROM MARA
WHERE MATNR = IN_PAR_TAB-VALUE.
IF SY-SUBRC EQ 0.
MOVE 'MARA-MATKL' TO OUT_PAR_TAB-NAME.
MOVE MARA-MATKL TO OUT_PAR_TAB-VALUE.
APPEND OUT_PAR_TAB.
ENDIF.

ENDFORM.

Adding a call in the form

/E HEADER
/* This text element contains the header information for an inspection lot
/*

(C) SAP AG LO750 6-23
/: PERFORM MARA_LESEN IN PROGRAM ZQDRGF00
/: USING &QALS-MATNR&
/: CHANGING &MARA-MATKL&
/: ENDPERFORM
U1 Inspection report
S1 Inspection lot,,&QALS-PRUEFLOS&,,&QALS-KTEXTLOS&
S1 Material,,&QALS-MATNR&,,&QALS-KTEXTMAT&
S1 Material group,,&MARA-MATKL&
/*

SAP AG 1999
Follow-Up Actions
Contents:
l Defining Follow-Up Actions
l Follow-Up Actions: Customizing
l Follow-Up Actions: Catalog Maintenance
l Status for Follow-Up Actions
l Follow-Up Actions and Business
Transactions
l Action Box
l Customizing for the Action Box

SAP AG 1999
l Explain the points at which you can define
follow-up actions in QM
l Describe the variants, in which you can
create follow-up actions
l Show how you can define follow-up actions
for quality notifications
Follow-Up Actions: Unit Objectives

SAP AG 1999
Follow-Up Actions: Course Overview Diagram
Evaluations
9 4
Ease of Use
5
SAPscript
6
Basics
2
Interfaces
8 8
Status Management/
User Status
3
Customer
Enhancements
Archiving
10
Follow-Up Actions
7
1
Course Overview

SAP AG 1999
l Our company wants to define follow-up actions for
business transactions.
Follow-Up Actions: Business Scenario

SAP AG 1999
Defining Follow-Up Actions
ABAP Workbench
Create function module
Customizing
Maintain the follow-up action table
If necessary, assign business transactions

n In QM, there are follow-up actions for the usage decision and for tasks within the quality
notification.
n When the usage decision is made, a follow-up action is assigned to a code during maintenance of the
selected set code.
n For a quality notification, a follow-up action is assigned to a code during maintenance of the task
catalog.

SAP AG 1999
Follow-Up Actions: Customizing
PRINT for notification task Print inspection report
1 Z_QM_PRINT_REPORT QM90 Print insp. report

n A chain of function modules or business transactions can be performed as follow-up actions.
n The function module example can be used as a copy model.
n You can call up the follow-up action before or after the transaction is updated.
n You can make a setting for whether the update operation should be executed synchronously or
asynchronously.

SAP AG 1999
Follow-Up Actions: Editing Selected Sets
03 A Accepted Accepted 100
03 R Rejected Rejected 1
Released
Follow-up action Rejection, for example: PRINT, print inspection report
UD for inspection lots in production

n A follow-up action is assigned to the codes of a selected set at the usage decision.

SAP AG 1999
Follow-up action is
triggered
Follow-up action is
triggered
User status is
automatically set
User status is
automatically set
Workflow
can be
triggered
Additional
selection
options (lists)
Additional
information for
inspection lot,
notification
Follow-Up Actions: Setting the User Status
Assigned business
transaction is executed
Assigned business
transaction is executed
Applications

n A predefined business transaction can be assigned to a follow-up action. This involves transactions
QM90 to QM99 when the usage decision is made. For the tasks, this includes transactions QN90 to
QN99.
n Statuses can be assigned to these business transactions.
n The statuses are set when you execute such a transaction.

SAP AG 1999
Status profile LO750_01 Print inspection report
User status
Status Short text
Insp. report printed
Highest status no. Position Priority Auth. code Lowest status no. Status no. Init. status LText
PBDR
Business transaction Business transaction
Trans Text
QM90
...
Follow-up act. variant 1
...
QM99
Business transaction No activity Activate
Insp. lot processing
Status profile LO750_01
Rec. insp. at goods receipt for purch. order Insp. type 01
Influence Follow-up action
Transaction control
Follow-Up Actions and Business Transactions
Change Follow-Up Actions

(C) SAP AG LO750 7-10
SAP AG 1999
Action Box
Business Workflow
- asynchronous -
No. Notification header
Material
Customer
No. No. Action box
Telephone call
Notification
8D report
Customizing Customizing Customizing
SAP standard examples SAP SAP standard examples standard examples
Customer enhancements Customer enhancements Customer enhancements
Follow-up action
- synchronous -
Task /
activity
Task /
activity

n In the action box, follow-up functions are defined for each notification type in Customizing. By
using the pushbutton in the action box, the relevant follow-up functions are executed and
documented in the form of an activity or task in the notification header.
n The function is executed directly after the selection, in other words, not when the notification is
saved.
n After the follow-up function has been implemented successfully, a task or an activity is created.
n You can also use a follow-up function to trigger a Workflow task.
n The required Customizing entries can be copied from client 000. These are follow-up functions,
follow-up actions, and basic data from the catalog of tasks and activities.
n Examples of follow-up functions:
Tightening/resetting quality level
Sending reports
Requesting 8D report
Generating notifications from existing notifications

(C) SAP AG LO750 7-11
SAP AG 1999
Customizing for the Action Box (1)
Example of a process with dependent
follow-up functions
Send final
notice (*)
END
or
Overview of Customizing steps for
setting up the action box
END
(*) = Follow-up functions
Send confirmation of
receipt (*)
Send interim
notice (*)
Send final
notice (*)
Define individual follow-up functions 1
Define for each follow-up function,
whether:
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
2
3

n You can use the action box to execute several functions, which are required during notification
processing, with a mouse click. These functions are integrated as single follow-up functions in the
action box and are documented as tasks or activities in the notification after being executed.
n In the standard system, some follow-up functions are already defined for each notification type.
n In Customizing for task definition, you can define the follow-up functions that should be displayed
in the action box.
n You can define follow-up functions in the following way:
As simple functions that can be executed more than once and are independent of other follow-up
functions
As subfunctions in a higher-level process that are dependent on the execution of other follow-up
functions and can be run only once
n If you define several follow-up functions that are linked to a process and should be performed in a
certain sequence, you must define appropriate rules for these follow-up functions.

(C) SAP AG LO750 7-12
SAP AG 1999
Icon
Quick info Send confirmation of receipt
ICON_MAIL
Code group
Code
General tasks CC
Confirmation of receipt
QM-G1
0010
Dependent follow-up function
Executable only once
Task
FM when saving
QM06_SEND_PAPER_STEP1
Released
Completed
Function
Function module:
Bus. Operation
QM06_FM_TASK_SEND_PAPER
Coding for generated task/activity
Specific details for task
Rules
User interface
Task
Activity
Rules
Activity creates task or Activity creates task or
activity activity
Interface Interface layout layout
Workflow task Workflow task
start when saving start when saving
Function module Function module
start when saving start when saving
Definition Definition of rules for of rules for
execution execution

n You can use the New entries function in Customizing for task definition to define a new follow-up
function.
n On the detail screen, you define:
The function module that is called up when the follow-up function is executed
Whether the follow-up function is documented as a task or activity in the notification
How the follow-up function is displayed in the action box (icon and/or text)
Which code group and code are entered for the generated task or activity in the notification
Workflow tasks that should be generated in connection with the follow-up function
Name of the function module that is accessed when saving the notification. For example, you can
use this function module to enter or edit data in the Workflow container.
The status that should be set for the generated task (for example, released or completed)

(C) SAP AG LO750 7-13
SAP AG 1999
Allwd follw-up fns
Follow-up funcs
Dialog Structure
Function Send confirmation of receipt
Notif. type: Customer complaint
0015
Q1
FK
Allowed follow-up functions
0020
0023
Short text for code
Send interim notice
Send final notice
Send allowed follow-up functions
for the follow-up function "Send
confirmation of receipt"

n You must define the allowed follow-up functions for each dependent follow-up function
n In our example, you must specify for the first follow-up function ("Send confirmation of receipt")
which follow-up functions should follow (for example, "Send interim notice" or "Send final notice").

(C) SAP AG LO750 7-14
SAP AG 1999
SAP SAP standard system standard system Function group QM06
Function group QM06
l Internal note
n Creates an activity with a long text
l Documentation telephone call
n Creates an activity with a long text
l Create a new quality notification including the items
l Create a repair order
l Goods movement for repair order (RMA)
l Copy decision to repair order

(C) SAP AG LO750 7-15
SAP AG 1999
SAP SAP standard system standard system Function group QM06
Function group QM06
l Adapt the quality level
n Return to initial inspection stage
n Tighten
l Request an 8D report
n QM_8D_REPORT form
l Send report
n Confirmation of receipt
n Interim notice
n Final notice
n QM_REPLY form

(C) SAP AG LO750 7-16
SAP AG 1999
SAP SAP standard system standard system
Function group QMLR
Vendor complaint
Function group QMLR
Vendor complaint
l Performing stock postings
n Unrestricted-use to inspection stock
n Unrestricted-use to blocked
n Blocked to unrestricted-use
n Scrapped
l Assign vendor
l Assign purchasing document
l Create/edit a return delivery
l Create a transport order

(C) SAP AG LO750 7-17
SAP AG 1999
SAP SAP standard system standard system Function group QISD
Link to solution DB
Function group QISD
Link to solution DB
l Call up/start solution search
l Display assigned documents from the solution database
n Symptoms
n Solutions

(C) SAP AG LO750 7-18
SAP AG 1999
l The QM component allows you to define
automatic follow-up actions in the form of
function modules.
l You can define follow-up actions for usage
decisions and tasks.
l 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.
l You can assign specific business transactions
to a follow-up action.
l You can use the action box to define follow-up
functions for quality notifications in
Customizing.
Follow-Up Actions: Unit Summary

(C) SAP AG LO750 7-19
Follow-Up Actions Exercises

Unit: Follow-Up Actions
Topic: Follow-Up Actions

Create a follow-up action for a usage decision

An inspection report should be printed automatically when you make a
certain usage decision.
1-1 Create a function module for your follow-up action. Use an existing standard
module as a copy model.
Function group: ZQ##
Function module: Z_ZQ##_REPORT
1-2 Include your print program in the function module for the follow-up action.

1-3 Create a follow-up action.
Follow-up action: ZGR##
1-4 Create a selected set and include your follow-up action.
Selected set: ZGR##
1-5 Assign the selected set to the inspection type that you created in a previous
exercise.

1-6 Test the new function.

(C) SAP AG LO750 7-20
Follow-Up Actions Solutions

Unit: Follow-Up Actions
Topic: Follow-Up Actions
1-1 Follow-up action
Create your own function module using a copy of the function module
QFOA_COPY_REFERENCE_FORM. New function group is ZQ00.
Create the new function group ZQ00 as a copy of the function group QFOA
(transaction SE80, right mouse-click).
Only copy the copy module QFOA_COPY_REFERENCE_FORM to
Z_ZQ00_REPORT (transaction SE37).

FUNCTION Z_ZQ00_REPORT.
*"----------------------------------------------------------------------
*"*"Local interface:
*" IMPORTING
*" VALUE(I_QALS) LIKE QALS STRUCTURE QALS
*" VALUE(I_QAVE) LIKE QAVE STRUCTURE QAVE
*" EXPORTING
*" VALUE(E_SUBRC) LIKE SY-SUBRC
*" TABLES
*" E_PROTOCOL STRUCTURE RQEVP
*"----------------------------------------------------------------------

SUBMIT ZQDRGR00 "Print program
WITH P_LOS = I_QALS-PRUEFLOS
AND RETURN.

ENDFUNCTION.

1-2 Include print program in function module (see SUBMIT ZQDRGR00 in the local
interface).

(C) SAP AG LO750 7-21
1-3 Create the follow-up action in Customizing (Quality Management Quality
Inspection Inspection Lot Completion Define Follow-Up Actions).
Set the indicators AftrPst and SyncUpdt and assign the function module.

1-4 Assign the follow-up action to the selected set (transaction QS52, catalog type "2"
or "3"), follow-up action as code for the selected sets.

1-5 Create a selected set and assign it to the corresponding inspection type.
Customizing: Quality Inspection Inspection Lot Creation. Maintain the
inspection type, enter a selected set (field: "UD selected set").

1-6 Test the function
Change the previous status profile: Add the new status IRPR (inspection report
printed) without a status number. Assign operation "QM90". Select the indicator
"Set".
Add a second entry for the previous follow-up action. Assign a dummy function
module (same interface as before, but no content). Assign operation "QM90", the
indicator "AftrPst" cannot be set.

SAP AG 1999
Interfaces
Contents:
l QM-IDI
l RFC Function Modules for Upload and
Download
l QM-STI
l BAPI Definition and Properties
l BAPIs in Quality Inspection and Quality
Notifications

SAP AG 1999
l Explain how interfaces are used in the QM
component
Interfaces: Unit Objectives

SAP AG 1999
Interfaces: Course Overview Diagram
Evaluations
9 4
Ease of Use
5
SAPscript
6
Follow-Up Actions
7
Basics
2 2
Status Management/
User Status
3
Customer
Enhancements
Archiving
10
Interfaces
8
1
Course Overview

SAP AG 1999
l The QM component should exchange data with
other systems using interfaces.
Interfaces: Business Scenario

SAP AG 1999
SAP SAP Logistics Logistics
Data Data Transfer Transfer
Quality Management System
QM Information System
- Inspection
catalogs
- Inspection
catalogs
Basic data
Subsystem
Q- level
Task
list
Insp. lot Results Usage decision
Basic data
Insp. lot
Results
Usage decision
QM-IDI: Data Transfer

n The QM-IDI ("Inspection Data Interface in Quality Management") provides the QM component
with an open interface to external systems and is designed to exchange 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 QM.

SAP AG 1999
l l Upload Upload
n n Single Single results results
n n Sample Sample results results
n n Characteristic results Characteristic results
n n Inspection points Inspection points
n n Usage decision Usage decision
l l Download Download
n n Catalog data Catalog data
n n Selection from Selection from worklist worklist
n n Operations Operations
n n Characteristic specifications Characteristic specifications
n n Additional master data Additional master data
n n Exceptions Exceptions
Data transmission Data transmission
Method Method: : Remote Function Call Remote Function Call
Function modules
QM-IDI: Data Transmission

n Data transfer between the subsystem and QM occurs synchronously, meaning that direct program-to-
program communication is established. The subsystem initiates both the request for the inspection
specifications from QM and the confirmation of results data. One advantage of this type of
communication is that the subsystem can independently request inspection lots for processing from
QM and is then able to adjust the size of the worklist to its own processing times and capacity using
comprehensive selection criteria.
n SAP provides function modules for the transfer of inspection specifications and the confirmation of
inspection results. These function modules can be called from non-SAP systems and are then
executed in the QM component.
n The SAP Remote Function Call ( RFC ) Interface is used for this purpose. The methods that must be
used and the prerequisites that must be fulfilled by a subsystem to integrate SAP RFC function
modules are outlined in the document "Remote Communication".

SAP AG 1999
Define subsystem IDs
Define mail addresses for transfer logs
Define trace level for application log
Function modules for changes to the
worklist
Define IDs for subsystems in the master records
for work centers
Assign work center to inspection plan
Work Center Work Center
Inspection Plan Inspection Plan
QM-IDI: Settings in the SAP System

1. Define the ID for subsystems and mail addresses for the transfer logs.
2. Use the trace level to define the scope of the notifications, which should be written in an
application log. These notifications can be displayed using transaction SLG1. The object is
QMQI.
3. If the worklist in a subsystem changes, run a function module. The module
QIRF_NOTIFY_FUNCTION acts as a copy model. In this way, you can create
customer-specific algorithms for notifications and logs.
4. Define these IDs in the master records for the work centers.
Determine whether the automatic generation of defect data is required. If so, you must
activate the automatic determination of a report type for the appropriate work centers.
5. If you want to have an inspection operation processed in a subsystem, assign a work center to
this operation. A quality data recording system must been specified for this work center.

SAP AG 1999
10
20
30
40
0001
0002
0003
0004
10
20
30
10
20
10
20
10
20
Inspection Inspection Plan Plan
Sub 1
Sub 1
Sub 2
Sub 2
Work center Work center Operation Operation Characteristic Characteristic
QM-IDI: Assignment at Operation Level

n The inspection characteristics for different operations can be processed in different systems. The
business object used to assign operations to the subsystem is the work center. Each operation is
assigned a work center, which in turn can be assigned to a subsystem. You can assign a subsystem to
more than one work center.

SAP AG 1999
l QIRF_SEND_INSP_REQUIRMENTS
Selection of operations to be processed, transfer of the
corresponding worklist
l QIRF_SEND_INSP_DATA_FOR_WL
Transfer of characteristic specifications and catalog entries to the
worklist
l QIRF_SEND_REQUIRMENTS_GET_DATA
Selection of operations to be processed, transfer of operations,
characteristic specifications, and catalog data
l QIRF_SEND_COMMIT_TO_QM
Update of lock entries
l QIRF_SEND_CATALOG_DATA
Transfer of catalog entries
l QIRF_INSPPOINT_GETLIST
Evaluation of existing inspection points in the SAP System
RFC Function Modules for Downloading

(C) SAP AG LO750 8-10
SAP AG 1999
l QIRF_GET_ORIGINAL_VALUES
Results confirmation for single results
l QIRF_GET_SAMPLE_VALUES
Results confirmation for sample results
l QIRF_GET_FEATURE_VALUES
Results confirmation for characteristic results
l QIRF_GET_INSP_POINT
Results confirmation for inspection points
l QIRF_GET_ALL_DATA_VALUES
Results confirmation for all result types
l QIRF_GET_USAGE_DECISION
Confirmation of usage decisions for inspection lots
l QIRF_GET_DEFECT_ITEMS
Confirmation of defect items
RFC Function Modules for Uploading

(C) SAP AG LO750 8-11
SAP AG 1999
l Evaluation and analysis of R/3 inspection results data using
external statistical software
l Flexible data selection in SAP QM
l Data transfer via API Open interface
l Advantages:
n A company can continue using existing statistical software
(investment protection).
n A wide range of statistics software with special functions is
available on the market.
QM-STI
SAP
QM
SAP SAP
QM QM
QM-STI: Statistical Interface

n The QM-STI interface ("Statistical Data Interface in Quality Management") provides the QM
application component with an open interface to external evaluation systems. QM inspection results
are transferred to the external evaluation system in a format defined by SAP.
n The QM-STI interface is used to carry out special evaluations that are not supported by the statistical
functions of QM results recording (control charts, histograms, process capability indices).
n Implementation Considerations
Precondition for the use of this function is an external statistical system compatible with the QM-STI
interface. One example of the integration of desktop applications is the evaluation function in
Microsoft Excel. In this case, the driver is in ABAP and controls Microsoft Excel using the OLE
technique. However, drivers are usually contained in the external system as RFC server programs.
The evaluation method must be defined in Customizing. For more information on defining the
evaluation method, refer to the QM Implementation Guide (IMG) by choosing Quality Inspection ->
Subsystems -> Define Evaluation Method for QM-STI Interface.

(C) SAP AG LO750 8-12
SAP AG 1999
QM-STI
ST01
ST02 M1
M2
StatSys: ST02
Method: M2
Control chart
Results recording
Results history
QM-STI: Calling the Interface

n You can start the data export from the following QM areas:
- Results Recording
In QM results recording you start a QM-STI evaluation of the current characteristic by choosing
Extras -> Statistics -> QM-STI evaluations. A dialog box appears. In this dialog box, you
choose an evaluation method and the corresponding RFC destination and enter further data (for
example, title and axis descriptions) for the current evaluation.
- Control Chart
You can start a QM-STI evaluation from a control chart via QM-STI evaluation. The dialog box
mentioned above appears. All samples available in the database that were read for the control
chart are transferred to the QM-STI Interface. This does not include samples for canceled
inspection lots. This means that samples that were not evaluated and samples or characteristics
that were not completed are not transferred to the interface.
- Results History
When you start the data export from a results history, the data of characteristics in various
inspection lots is transferred to the QM-STI evaluations. The samples are transferred in the
order that has been defined by the user in the results history.

(C) SAP AG LO750 8-13
SAP AG 1999
Report Report header header
Material_Data
Vendor_Data
Method_Data
Characteristic_Header
Characteristic_Quantitative
Sample_Header
Results_Quantitative
Results_Additional_Data
QM-STI: Data Structures

n The application data must be structured in a set order for the data transfer to the external statistical
system. The data is contained in a four-tiered hierarchy, made up of:
- The evaluation
- The characteristic
- The sample
- The single value

n Each hierarchy level contains one or more tables. For each evaluation method, you can define which
tables are transferred to the statistical system. This enables you to hide, for example, the sample
level, if it is not needed for an evaluation method.

(C) SAP AG LO750 8-14
SAP AG 1999
l Business Application Programming Interface
l 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
BAPI: Definition

n BAPIs are a "gateway" to the SAP System; this means that the SAP System uses them to provide
access to business data and processes.
n An object in the BOR can have many methods, of which one or more are implemented as BAPIs.
n BAPIs can have different functions:
- Creating an object
- Requesting the attributes of an object
- Changing the attributes of an object
...

(C) SAP AG LO750 8-15
SAP AG 1999
BAPI: Characteristics
l Object-based
n Access to methods of objects in the BOR
l Stable interface
n The interface of a BAPI is "frozen"
l Can be used internally and externally
n BAPIs can be used in the R/3 Systems and in external systems
l Functionally independent
n Each BAPI can be called up independently
l However: BAPIs do not contain a presentation layer
n Results can only be viewed externally using the calling program

n External clients can access BAPIs as well as methods of objects that are contained in the client,
thanks to the BAPIs object-based viewing procedure.
n SAP guarantees that despite any changes, the BAPI interface will remain compatible. This means
that programs currently using a BAPI will function in the future, even if SAP were to change the
coding behind the interface.
n You can also use BAPIs within the SAP System to access business data. This simplifies functional
enhancements to R/3 for both customers and partners.
n BAPIs represent basic operations in the SAP System that can be called up independently of one
another.
n Data supplied (and received) by a BAPI is in internal SAP format. External clients must convert this
data to provide the user with a different format. If you are using BAPIs to create your own
enhancements in the SAP System, you can prepare the data for input and output using screens.

(C) SAP AG LO750 8-16
SAP AG 1999
BAPIs in Quality Management
l Quality Planning
n Object type MatInspectionControl
(Material inspection control)
l Quality Inspection
n Object type InspectionLot (inspection lot)
n Object type InspLotOperation
(inspection operation)
n Object type InspectionLotCharacter
(inspection operation characteristic)
n Object type InspectionPoint
(inspection point for an inspection operation)
l Quality Notifications
n Object type QualityNotification (quality notification)

n Using the BAPI browser (transaction BAPI), you can directly access all additional information for
the individual BAPI methods in the SAP System.

(C) SAP AG LO750 8-17
SAP AG 1999
l 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.
l 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.
l 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.
Interfaces: Unit Summary

(C) SAP AG LO750 8-18
Interfaces Exercises

Unit: Interfaces
Topic: QM-IDI and QM-STI Interfaces

Exchange quality data using the QM-IDI and QM-STI interfaces

You want to download and upload data from other systems into the QM
system.
1-1 Create a worklist for QM-IDI.

1-2 Make confirmations for characteristics and use the single test function in the
Function Builder.

1-3 Perform a statistical evaluation using QM-STI from within results recording.

(C) SAP AG LO750 8-19
Interfaces Solutions

Unit: Interfaces
Topic: QM-IDI and QM-STI Interfaces
1-1 Assign a subsystem to a work center. Assign an operation in the inspection plan to
this work center.
Create an inspection lot using this inspection plan.
There must be at least one entry for this inspection lot in table QIWL. Check using
transaction SE16.
Call Function Builder (transaction SE37)
Function module QIRF_SEND_REQUIRMENTS_GET_DATA.
Use the test function.
Include the subsystem in structure I_QAILS (parameter SUBSYS).
As a result, the worklist from QIWL must have been copied.

1-2 Now confirm the result using module QIRF_GET_FEATURE_VALUES.
Set indicator I_IND_CLOSE_PROCESSING, enter the subsystem in the parameter
I_SUBSYS.
Enter data in T_QAIMRTAB:
Record type Q73.
Confirmation number.
Set KZABSCHL.
Enter the characteristic valuation for this record type.
After this, check the result using results recording.

1-3 Call the QM-STI in results recording using "Extras". Quantitative single values
must exist for the corresponding characteristic.

SAP AG 1999
Evaluations
Contents:
l SAP Business Intelligence
l Standard Analyses in QMIS
l Information Structures
l Update Rules
l Logical Databases
l ALV in List Output
l Ad Hoc Queries Using QuickView
l Comparison of SAP Query and QuickView

SAP AG 1999
l Create info structures in QMIS
l Use logical databases to perform evaluations
Evaluations: Unit Objectives

SAP AG 1999
Evaluations: Course Overview Diagram
Basics
2
4
Ease of Use
5
SAPscript
6
Follow-Up Actions
7
Interfaces
8 8
Status Management/
User Status
3
Customer
Enhancements
Archiving
10
Evaluations
9
1
Course Overview

SAP AG 1999
l Our company wants to be in a position to use
evaluation functions that are not included in the
SAP standard.
Evaluations: Business Scenario

SAP AG 1999
Standard analyses
information structures information structures
Update
Inspection lots
Notifications
Standard Standard
QMIS Standard Analyses

n Various methods of analysis are available in the Information System, based on the database in the
standard information structures.
n The standard analyses form an efficient tool for presenting and analyzing statistical data effectively
in the SAP Business Intelligence environment.
n You can also use flexible analyses to define individual views for the data in the information system.
Other SAP data can be integrated in these views.

SAP AG 1999
Characteristics Key figures
157 005
398
Time reference
Vendor
Material
Month
Inspection type
Plant
Number of lots...
Quantity...
Rate...
Organization of Information Structures

n Information structures form the data basis for the information system. The information structures are
special statistical tables, in which data from operative applications is continually updated in
summarized form.
n An information structure contains three basic types of information:
- Characteristics are typical summarization criteria without time reference, such as, inspection
type, vendor, and material.
- Periods establish the time reference. Data is cumulated and compressed for each period during
the update.
- Key figures provide meaningful business information, for example, "mean value of the quality
score", "total lots", "quantity to blocked stock", and "quota of skipped lots".
n From a technical point of view, characteristics and periods form the basic evaluation groups in
databases.

SAP AG 1999
Results recording
Status = 2
Status = 5
Regeneration
Status = 5
Inspection
operations
Inspection
operations
Insp.
lot
Insp.
lot
Characteristics
Key figures
157
157
005
005
398
398
Summarization of Inspection Results
Inspection
points
Inspection
points
Inspection
results
Inspection
results

n Inspection results are updated when an inspection characteristic is closed. If the characteristic is reset
to in process, this is recognized by the update program and the results are updated again, when the
characteristic is closed.
n Summarization occurs either at characteristic or sample level.
n It is necessary to regenerate the data from Release 3x.

SAP AG 1999
Material + (vendor/customer)
Work center
Inspection characteristic
Master inspection charac.
Plant
Period
Info Structure for Inspection Results
Characteristics
Characteristics

n You can analyze inspection results using the following standard info structures:
- General characteristics for material
- Quantitative characteristics for material
- General characteristics for vendor
- Quantitative characteristics for vendor
- General characteristics for customer
- Quantitative characteristics for customer
n The system does not take the info structures and qualitative characteristics that relate to the update or
manufacturer processing into account.

SAP AG 1999
.
.
.
.
.
.
.
.
Production
Stock transfer/
goods issue
Goods receipt
Delivery
Update rule: 22/ 52 / 53
.
.
.
.
Update Rule (by Origin)
Material Material
Vendor Vendor
Material Material
Material Material
Customer Customer

(C) SAP AG LO750 9-10
SAP AG 1999
Internal problem
notification F3/Q3
Notification for
vendor F2/Q2
Notification from
customer F1/Q1
Update rule: 33
Update rule: 34
Update rule: 32
Update Rule (by Notification Type)
Material Material
Vendor Vendor
Material Material
Material Material
Customer Customer

n The system updates the inspection results, based on the following parameters:
Material
Material, vendor
Material, customer
n You make the relevant settings in Customizing.

(C) SAP AG LO750 9-11
SAP AG 1999
Standard deviation
S
__
Mean value
Process capability index C
P
Critical index C
Pk
inspected and closed samples
n No. of
accepted samples No. of n
A
n
R
rejected samples No. of
n
D
defects in sample No. of
n
NU
nonconforming units No. of
n
LTol
times value exceeded lower
specification limit
No. of
n
UTol
times value exceeded upper
specification limit
No. of
All Quantitative
X
__
Key Figures for the Characteristics

n You can choose key figures, such as, standard deviation, mean value, and process capability indices
for quantitative characteristics.
n Key figures for samples, times when the tolerances are exceeded, and defects are available for all
characteristics.
n You can choose between three different process models to flexibly determine key figures, such as,
mean value, standard deviation, cpk and cp values.
n All characteristics can be monitored by the Early Warning System (EWS).
n You can use the compound characteristic function to group several characteristics that logically
belong together.

(C) SAP AG LO750 9-12
SAP AG 1999
Logical
database
ABAP program
GET <node>
ABAP program
OPEN SQL
(ABAP commands)
Generating Lists Using the LDB
ABAP program
NATIVE SQL
Database Database

n Usually, data that is to be displayed in list form is read from the database.
n You can use OPEN SQL or NATIVE SQL instructions to read data from the database.
n Instead of having to program access to the database yourself, you can use logical databases. The
logical database retrieves the data records and makes them available to the ABAP Program.

(C) SAP AG LO750 9-13
SAP AG 1999
ABAP 1
Query 1
Logical database
Query 2
ABAP 2
ABAP 3
ABAP 6
ABAP 5
Query 6
Query 3
Query 5
Query 4
ABAP 4
- Creates selection screen
- Performs input and authorization checks
- Reads data records
Advantages of the Logical Database

n Logical databases have many advantages:
- The system creates a selection screen. Selection screen versions or variants give you the
required flexibility.
- The user does not need to know the exact structure of the tables (in particular the foreign key
relationships). The system makes the data available in the correct sequence based on the GET
events.
- Performance improvements to the logical database take immediate effect in all related programs
and therefore do not need to be updated individually.
- Maintenance is carried out centrally.
- You can manage authorization checks from the central database.

(C) SAP AG LO750 9-14
SAP AG 1999
ABAP dictionary
ABAP dictionary
PGQ
PGQ
Logical view
Logical view
QALS
QALS
QAPO
QAPO
QAMR
QAMR
Logical Database: Overview
QAMV
QAMV

n An ABAP program that reads data from the database for programs of type 1 and displays them as
records, is known as a logical database.
n During this process, the sequence in which the data is supplied to the programs is determined by a
hierarchical structure. In addition, a logical database makes a selection screen available for the
programs (checking the user entries and error dialog). This screen can be configured in the programs.
n In Release 4.0, there are approximately 200 logical databases in the standard system. As a part of
namespace enhancement, a logical database's name has been extended to 20 characters (with a
namespace prefix of a maximum of 10 places). You no longer need enter an application ID for the
logical database in Release 4.0.

(C) SAP AG LO750 9-15
SAP AG 1999
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)
ABAP Events and the Logical Database

(C) SAP AG LO750 9-16
SAP AG 1999
What Is the ALV Classic?
l ALV stands for the ABAP List Viewer
l ALV Classic is a collective term for several function
modules in the function group SALV
l Tool for the standardized output of:
n Simple lists
n Hierarchically sequential lists with two hierarchy levels

n You can use ALV function modules to create standardized lists with generic functions.
n Since Release 4.6C, there has been control-based further development of ALV - ALV grid control.

(C) SAP AG LO750 9-17
SAP AG 1999
Reasons for Developing ALV
l Until the ABAP List Viewer (ALV) was introduced, various
report tools were used in the SAP System.
l Each report tool has its own functions and application areas.
l The ABAP List Viewer has standardized and simplified how
lists are used in the SAP System.
l A standardized data interface and list layout is available for
all lists.

(C) SAP AG LO750 9-18
SAP AG 1999
ALV Standard
l List layout based on specifications from the usability
group (LIBS)
l Generic functions in lists
l Only presentation, no selection
l Individual list display determined by the user
n Technical adjustments
n Functional enhancements

(C) SAP AG LO750 9-19
SAP AG 1999
Set of Generic Functions
l Detail
l Filter function
l Sort function
l Creation of subtotals and
totals
l Expand and collapse
l Show and hide
fields
l Download functions
l Change the layout

n The standardized lists created using ALV create a generic set of functions. In this way, a user can
make changes to the list.
n These generic functions are available in the menu and application toolbar.

(C) SAP AG LO750 9-20
SAP AG 1999
l Data is displayed in simple lists by calling up the function
module reuse_alv_list_display
l Transfer parameters
n Internal data table for list output
n Field descriptions for data tables (field catalog)
n General descriptions for list layout (optional)
l ALV sets its own status
l Using the callback technique, the standard ALV functions can
be flexibly combined with application-specific logic
Basic Principle

n The output of simple lists is triggered by the function module reuse_alv_list_display.
This function module issues an internal table with a structure in the form of edited lists with one or
more lines.
n All changes that are later made to the list refer directly to the internal output table. For example, the
sorting of lists causes the transferred, internal output tables to be sorted again, since these are
transferred by reference.
n The module requires either a field catalog or an internal table with a dictionary structure, as well as
descriptions of the list layout that differ from the standard (optional).
n After the list is displayed (ALV sets its own GUI status as a default setting), all the standard
operations can be performed.
n You can make changes to the standard system to meet your requirements. Various function modules
are available to process a list as required. Some of them are available for the individual layout of the
list display, others are explicitly called by the ABAP List Viewer.
n The procedure used for hierarchically sequential lists corresponds to the procedure used for simple
lists.

(C) SAP AG LO750 9-21
SAP AG 1999
Standard Call for ALV
Select * from ...
A B C
A B C
A
B
C
< Name >
Structure Field catalog
or
Internal table
Internal data table
Internal data table
Field descriptions
Field descriptions
Calling the ABAP List Viewer
Calling the ABAP List Viewer
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY
List output
List output
A B C
Data Data

n This slide describes the basic process for creating a list. Descriptions of data in the internal table can
be made either using the field catalog or a dictionary structure. You can also use a dictionary
structure to describe data and then enter formatting options using the field catalog.

(C) SAP AG LO750 9-22
SAP AG 1999
Field Catalogs
l The field catalog describes the fields for the internal data table.
l The field catalog is an internal table.
l The field catalog contains an entry for each output-relevant
column in the data table.
l Output options are defined for each column using the field
catalog.

(C) SAP AG LO750 9-23
SAP AG 1999
QuickViewer: Overview
Data source
Table
Database view
Table join
Functional area
Logical database
Create list
Basis or
layout mode
4Field sequence
4Sorting
4Selections
4...
Execute
Save list
Link to Word
ABC analysis
Display in ALV control
etc.

n The QuickViewer is a newly developed tool for 4.6A, which is used to create ad hoc reports. You
start the QuickViewer by choosing transaction SQ01.
n For example, the QuickViewer can use a database table or also a database view as a data source. A
list can be created from the fields of the named data source. Two modes are available for this: The
basis mode and layout mode.
n The QuickView includes a link, for example, to the EIS, ABC analysis, or ALV grid control. The list
can also be further edited in external programs, for example, Word.
n The created list can be saved and displayed again in the QuickViewer. The selection criteria can also
be stored for the saved list and can be called up at any time.

(C) SAP AG LO750 9-24
SAP AG 1999
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.
Help topics: Selection fields; Output options for the
list: List width
QuickView DEMO Change Create
SAP Query Execute
QuickViews for user TRAINER
LO750_D1 Demo in LO750

n Each user creates their own QuickViews that are not visible to other users. As a result, the
QuickViews of other users cannot be copied. You can change a QuickView into a SAP Query, if the
QuickView uses a functional area from the standard area as a data source. The query is then visible
to the user group.
n QuickViews are not linked to correction and transport systems.

(C) SAP AG LO750 9-25
SAP AG 1999
Creating a QuickView
Create QuickView DEMO: Choose data source Create QuickView DEMO: Choose data source
Example in LO750
DEMO
QuickView
Title
Comments
1. Data source:
Join using tables QALS and QAVE
Basis... Layoutm...
Table join

n To create a QuickView, you must specify a data source. You can specify database tables, database
views, logical databases, table joins, or functional areas for the SAP Query as data sources. The
functional area must be in the standard area (client-dependent).
n You have access to the specified data quantity, but you cannot enhance this by additional fields.

(C) SAP AG LO750 9-26
SAP AG 1999
Join Definition: Graphic
Join Definition
MANDANT
PRUEFLOS
KZART
ZAEHLER
VKATART
VWERKS
VAUSWAHLMG
...
QALS QALS
MANDANT
PRUEFLOS
WERK
ART
...
QAVE QAVE
Check Add table Delete table Table alias
INNER or LEFT OUTER link

n If you specify a table join as a data source, then you must first define this join before you can create
the list in the QuickViewer.
n The table join is defined graphically. You must specify links between the tables. The system can also
make proposals for you. This involves dictionary information being evaluated.
n The result quantity is determined by deciding for an inner or left outer join logic. For example, if you
only want to print the inspection lots from table QALS in a list, for which there are entries in table
QAVE, this counts as an inner join logic. However, if you want to print all inspection lots regardless
of whether there are entries in table QALS, you link both tables using a left outer join logic. In this
example, the left table is QALS.
n Alias tables enable you to use the same (database) table several times when defining the join.

(C) SAP AG LO750 9-27
SAP AG 1999
Basis Mode: Basic Structure
Data source
Create QuickView
Online documentation
Information

n The screen for the basis mode is split into 4 areas. The available fields (data source) are displayed in
the upper left corner in the form of a tree. Further information on usage is displayed in the lower left
corner of the screen. You can maintain the title and comments, and control output (list, Excel) in the
upper right screen area. In this area, you can control the structure of the list, define the sort sequence,
and enter selection criteria. You can switch to the online documentation in the lower right window.

(C) SAP AG LO750 9-28
SAP AG 1999
Creating a QuickView in Basis Mode
List fld select. Sort sequence Selection fields Data source
Fields in list Available fields
Example in LO750
DEMO
QuickView
Title
Comments Join using tables QALS and QAVE

n You create the QuickView using two table controls. You select the required list fields in the right
table control and transfer them to the left table control (Fields in the list) using the transfer functions.
You also control in the left table control (Fields in list) how many lines should be entered in the list
(Insert lines function).
n You do the same for the sort and selection fields: You select the required fields in the left table
control and copy them to the right control.

(C) SAP AG LO750 9-29
SAP AG 1999
Using QuickViews
l Ad hoc reports for a user
l Each user creates their own QuickViews, which are not
visible to other users
l Working with available data quantities
l No administrative costs (user group, functional area)
l QuickView can be changed into a SAP Query
l Link to internal (EIS, ABC, ALV) and external applications
l Limited functions in comparison to SAP Query
l No transport

(C) SAP AG LO750 9-30
SAP AG 1999
Overview: Program and Query
Describe list
REPORT ...
START-OF-SELECTION
...
WRITE ...
Program
ABAP
. . .
Output options
Line
Output options
Field
Title
Format
Classic
Query painter
Generate program

n If you create a list using a program (category 1), the data to be processed is, for example, created
using a logical database, processed in the program, and then issued in a list.
n A query is an evaluation of data, which a user can create using the SAP Query tool without
programming knowledge.
n The query takes you through a sequence of screens in which the line and list layout is described.
From Release 4.6A, you can graphically create query lists using the query painter.
n When the query is started, a program that corresponds to the list definition is automatically
generated. This program reads and processes the required data, and issues it in the list. The program
has the name AQmmbbbbbbbbbbbbqqqqqqqqqqqqqq. You can display the program name by
choosing the menu sequence AQL-1.
mm - coded client (standard area) or ZZ (global area)
bbbbbbbbbbbb - user group name (12 characters)
qqqqqqqqqqqqqq - query name (14 characters)
Spaces in the program name are replaced by '='.

(C) SAP AG LO750 9-31
SAP AG 1999
Organization in the Query
Queries
using
FA1
Queries
using
FA2
Queries
using
FA3
Administration
User group
UG2
User group
UG1
Functional area
FA1
Functional area
FA2
Functional area
FA3
Plans Creates
Assigns
Create

n The following tasks are included in the adminstrative tasks of the query: The creation of functional
areas and user groups, and the assignment of functional areas to user groups.
n The functional area determines to which database tables or fields in this table the query is referenced.
Functional areas are often based on logical databases.
n A user may only create and start queries, if they are assigned to at least one user group. A user can be
assigned to several user groups. The users in a user group have the same authorizations.
n The functional areas are assigned to a user group, to which the users in this group have access.
n A functional area can be assigned to several user groups.
n Several functional areas can be assigned to a user group.
n Queries are always created for a specific user group using a certain functional area. A user in a user
group has access to all queries that are created in that user group.

(C) SAP AG LO750 9-32
SAP AG 1999
Creating a Query
Functional area
FA1
User group
UG2
Functional area
FA1
User group
UG1
Query Query
New query
in FA1
Query Query
Copy Copy
Create
Change
Functional area
FA2
Functional area
FA2
Query Query
Query Query

n If you are assigned to several user groups, you can change between these user groups.
n A query is always created using a specific functional area. This functional area must be assigned to
the user group in which the query is created.
n As a rule, you can access all queries that are assigned to your user group.
n If you are authorized to define a query using a functional area, you can list all the queries for this
functional area.
n A query can only be copied from another user group into your own user group, if the functional area
for the query to be copied is also assigned to your own user group.

(C) SAP AG LO750 9-33
SAP AG 1999
Comparison of SAP Query and QuickView
Functional areas must exist
Local fields can be added
Programs can be linked (report/report
interface)
Query administration required (user
groups, functional areas)
Dataset is limited to the data source
Only basic lists
Report/report interface not available
No administrative costs since every
user only has access to their own
QuickViews
Easy, quick evaluations possible
SAP Query QuickView
Transport possible Transport not possible
Several partial lists possible
(statistics, ranked lists)

(C) SAP AG LO750 9-34
SAP AG 1999
l The standard analyses form an efficient tool for
presenting and analyzing statistical data
effectively in the SAP Business Intelligence
environment.
l 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.
l You can use the ALV technique to standardize the
output of lists in programs.
l You can perform ad hoc evaluations using the
QuickViewer.
l SAP Query has more functions than the
QuickView.
Evaluations: Unit Summary

(C) SAP AG LO750 9-35
Evaluations Exercises

Unit: Evaluations
Topic: Evaluations

Create evaluation programs that access a logical database

In your company, quality data should be evaluated according to certain
criteria.
1-1 Create your own info structure: S6##.

1-2 Create an evaluation program according to your specifications. To do this, use the
logical database "PGQ".
Program: ZQSTAT##
1-3 Create a list with information only from the inspection lot (table QALS). Use the
ALV technique.
Program: ZQALV##
1-4 Use the QuickViewer to perform an ad hoc evaluation for the inspection lot (tables
QALS and QAVE).
QuickView: QV##

(C) SAP AG LO750 9-36
Evaluations Solutions

Unit: Evaluations
Topic: Evaluations
1-1 Create an info structure in Customizing
Logistics - General Logistics Information System (LIS) Logistics Data
Warehouse Data Basis Information Structures Maintain Self-Defined
Information Structures
S691
Characteristics: Plant, Material, and Vendor (field catalog for characteristics
and inspection lot).
Key figures: All lots, rejected lots, skipped lots, and all notifications.
S068 and S098 act as copy models.
Generate the info structure.
Updating Updating Definition Specific Definition Using Update Rules
Maintain Update Rules
Update groups are "22" and "33".
Create S691/22 and S691/33.
Only maintain the correct rules for the updates.
Delete everything related to notifications for "22".
Only use the notification rules for "33", and change the source fields for the
characteristics. Function/rule/characteristic: MCIPM-MAWERK, -LIFNUM, -
MATNR.
Assign the appropriate conditions for rejected lots and skipped lots.
Update control, activate update.

1-2 Create a report using transaction SE38. The logical database is PGQ.

REPORT ZQMLDB00 .

TABLES:
QASE,
QAMV,
QALS.

(C) SAP AG LO750 9-37
SELECT-OPTIONS:
MERKMAL FOR QAMV-VERWMERKM.

START-OF-SELECTION.
GET QALS.
GET QAMV.
WRITE / QAMV-KURZTEXT.
GET QASE.
WRITE / QASE-MESSWERT.
END-OF-SELECTION.

1-3 ALV technique
Create a report using the logical database PGQ and selection screen 901.

REPORT ZQALVTR01.

TABLES:
QALS.
TYPE-POOLS: SLIS.

DATA: G_FIELDCAT_TAB TYPE SLIS_T_FIELDCAT_ALV.
DATA: G_REPID LIKE SY-REPID.

DATA:
FIELDCAT_TAB TYPE SLIS_T_FIELDCAT_ALV,
REPID LIKE SY-REPID,
QALS_TAB LIKE QALS OCCURS 0,
QALS_W LIKE QALS.

START-OF-SELECTION.

GET QALS.
APPEND QALS TO QALS_TAB.

(C) SAP AG LO750 9-38
END-OF-SELECTION.

REPID = SY-REPID.

CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
EXPORTING
I_PROGRAM_NAME = REPID
I_INTERNAL_TABNAME = 'QALS_TAB'
I_STRUCTURE_NAME = 'QALS_D01'
I_CLIENT_NEVER_DISPLAY = ' '
CHANGING
CT_FIELDCAT = FIELDCAT_TAB[]
EXCEPTIONS
INCONSISTENT_INTERFACE = 1
PROGRAM_ERROR = 2
OTHERS = 3.

CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
EXPORTING
* I_INTERFACE_CHECK = ' '
* I_CALLBACK_PROGRAM = ' '
* I_CALLBACK_PF_STATUS_SET = ' '
* I_CALLBACK_USER_COMMAND = ' '
* I_STRUCTURE_NAME =
* IS_LAYOUT =
IT_FIELDCAT = FIELDCAT_TAB[]
* IT_EXCLUDING =
* IT_SPECIAL_GROUPS =
* IT_SORT =
* IT_FILTER =
* IS_SEL_HIDE =
* I_DEFAULT = 'X'
* I_SAVE = ' '
* IS_VARIANT = ' '
* IT_EVENTS =
* IT_EVENT_EXIT =

(C) SAP AG LO750 9-39
* IS_PRINT =
* IS_REPREP_ID =
* I_SCREEN_START_COLUMN = 0
* I_SCREEN_START_LINE = 0
* I_SCREEN_END_COLUMN = 0
* I_SCREEN_END_LINE = 0
* I_BUFFER_ACTIVE =
* IMPORTING
* E_EXIT_CAUSED_BY_CALLER =
* ES_EXIT_CAUSED_BY_USER =
TABLES
T_OUTTAB = QALS_TAB
* EXCEPTIONS
* PROGRAM_ERROR = 1
* OTHERS = 2
.
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

1-4 QuickView
Create a QuickView using the data source table join. Link the tables QALS and
QAVE as an inner join.
This should be performed in accordance with the specifications given on the
appropriate slides.

(C) SAP AG LO750 10-1
SAP AG 1999
Archiving
Contents:
l Archiving Process
l Archiving Objects
l Customizing
l Organizing the Archiving of QM Data

(C) SAP AG LO750 10-2
SAP AG 1999
l Understand the basics of archiving
l Give an overview of the archiving options in QM
Archiving: Unit Objectives

(C) SAP AG LO750 10-3
SAP AG 1999
Archiving: Course Overview Diagram
Evaluations
9 4
Ease of Use
5
SAPscript
6
Follow-Up Actions
7
Interfaces
8 8
Status Management/
User Status
3
Customer
Enhancements
Basics
2
Archiving
10
1
Course Overview

(C) SAP AG LO750 10-4
SAP AG 1999
l Our company wants to archive quality data to meet
the requirements set for the storage of such data.
Archiving: Business Scenario

(C) SAP AG LO750 10-5
SAP AG 1999
Application data
(archive files)
Application data evaluation (print lists)
Incoming
document
QM
specialist
Outgoing
document
What Can Be Stored?

n Consider the following typical business process scenario: Documents are received (incoming
documents) that trigger or affect processes; documents are generated (outgoing documents) in a
business process; finally, business objects or processes are evaluated (print lists).
n You can link application objects to archived documents from within the Business Object (SAP
document) to display externally archived documents.
n You can store outgoing SAP documents created using SAPscript and link them to their underlying
business objects.
n You can store archive files and link them to archiving sessions.
n You can store print lists and create list management records.

(C) SAP AG LO750 10-6
SAP AG 1999
What Is Data Archiving?
l Storing data records from database tables to reduce the number of available
database tables in the system
l Reasons for data archiving
n Determined by the system
Memory space problems, performance, difficult database administration
n Legal specifications and operational requirements
Country-dependent storage requirements, data must be available to
external auditors, potential reusability of data
l Data deleted as a record from the tables
l Access to archived data controlled by the application

(C) SAP AG LO750 10-7
SAP AG 1999
Incorrect Definitions of Data Archiving
l 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.
l 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.
l 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.

(C) SAP AG LO750 10-8
SAP AG 1999
Frontend:
Administration
Application server:
Deletion
DB server:
Archiving D D V V B B
S S E E
D D B B ... ... D D B B ... ...
... ...
Background processing
Server for Archiving and Deletion Jobs

n The archiving program always runs in the background, primarily on a background server that is also
a database server.
n The deletion programs look for the next available background server. You must therefore always
make sure that all application servers also have access to the used file systems.
n From Release 4.5A, you can specify the server, on which the background jobs should be run.

(C) SAP AG LO750 10-9
SAP AG 1999
Archiving
program
Archiving: Step 1 - Archive
SAP
database
SAP
database
Archive
file
Archive
file

n In the first step, the archiving program creates an (initial) archive file.
The system then reads the data to be archived from the database as a background job and copies it to
the archive file. This operation continues until one of the following events occurs:
1. Archiving is complete.
2. Archiving is not yet complete, but the archive file has reached the size specified in Customizing.
3. Archiving is not yet complete, but the archive file already contains the number of archiving
objects specified in Customizing.
n Data is stored in the archive file in a format defined by SAP.

Length Table VBAK Data Table VBAP Data ......

(C) SAP AG LO750 10-10
SAP AG 1999
Archive
file
Archive
file
Archiving
program
Deletion
program
Deletion
program
Deletion
program
SAP
database
SAP
database
SAP
database
SAP
database
Archiving: Step 2 - Delete
Archive
file
Archive
file
Archive
file
Archive
file
Archive
file
Archive
file

n After the first archive file has been closed, archive management opens a second archive file and
proceeds with the archiving operation. At the same time, the system starts another program, which
reads the archived records and deletes them in the database.
This procedure ensures that only correctly archived records are deleted.
n When the last archive file is closed, a deletion program is also run for the file.
The diagram shows that several deletion programs can run in parallel for the created archive files.
n Since the archiving program does not alter any information contained in the database, (unlike the
deletion program), the archiving program prepares archive files quicker than they can be processed
by the corresponding deletion program. (This is, of course, dependent on the files to be archived.)
This has a positive effect on the total run time, since the database is used more productively.

(C) SAP AG LO750 10-11
SAP AG 1999
Deletion
program
Optical archive using ArchiveLink
HSM systems
Archiving: Step 3 - Options for Storing Archived
Information
SAP
database
SAP
database
Archive
file
Archive
file
Archive
file
Archive
file

n Archive files whose data has been deleted in the database can be stored in various ways.
Apart from using magnetic tape, the most frequently used methods are HSM Systems and archiving
in an external system using the SAP ArchiveLink.

(C) SAP AG LO750 10-12
SAP AG 1999
SAP DB SAP DB
Online
Archiving session
Archive files
Offline
Archiving
object
Archiving Process

(C) SAP AG LO750 10-13
SAP AG 1999
Archiving Objects
l Description of which data should be archived and how it is to
be archived (data model).
l Data is bundled into a self-contained business object,
independent of the conditions at the time of archiving.
l Programs for creating archive files and deleting data in the
database are contained in these objects.
l Further programs are available as required (creating/removing
indices, uploading, evaluating).
l Customer settings are assigned to each archiving object.
l Accessed from applications- you can define customer-specific
archiving objects for Z tables.

n Determining tables for an archiving object

Up to Release 3.1G: Transaction AOBJ, definition of structure
From Release 3.1G: Transaction SARA, menu option - database tables

(C) SAP AG LO750 10-14
SAP AG 1999
Schedule initial run
Schedule archiving
Schedule deletion
Schedule postprocessing
Schedule reload
Start evaluation
SARA Archiving
Object name
QM_CHARACT QM_CHARACT
F4 F4
Manage
Archiving Objects in Transaction SARA

n All archiving processes are carried out in the archive management function. Application data that
logically belongs together is grouped in an archiving object. By entering the name of the archiving
object, you can access the archiving session for this archiving object in the archive management
function.
n You can schedule the background job for the archiving sessions directly using archive management.
Alternatively, the jobs can also be scheduled within the application.
n The steps involved in archiving differ according to the archiving object.
n The initial run, postprocessing, and reloading are not supported by all archiving objects.
When dealing with archiving objects which require a usage, you have to trigger these activities
manually.
From Release 4.0, postprocessing programs can be started automatically.
n You can use archive management to control access to an archive file, and if you manage the archive
files manually, to also control the data medium, in which the archive files are stored.
n You can use the Archive Information System (transaction SARI) to evaluate archiving sessions.

(C) SAP AG LO750 10-15
SAP AG 1999
l QM_CHARACT: QM master inspection
characteristics
l QM_CONTROL: Movement data for quality
inspections
l QM_METHOD: QM inspection methods
l QM_PLAN: QM inspection plan
l QM_QMEL: Quality notification
Archiving Objects in QM

(C) SAP AG LO750 10-16
SAP AG 1999
Customizing
l 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
l 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
l Customizing for archiving in external archives
l Object-specific Customizing in the application

n In Customizing for archive objects, the logical file name is the name, with which the archive file is to
be created on the hard disk.

In the transaction FILE, a logical path is assigned to this logical file name.

Similarly, the logical path in the transaction FILE refers to a physical path and is dependent on the
operation system. In the transaction FILE, you must enter the syntax group of the operation system
that is being used.
n If an archive file is to be stored in an external archive, the physical path must correspond to the
exchange index between the SAP System and the archive (basic path in the archive definition).
The following slide shows how logical file names/logical file paths and physical file paths interact. It
uses the example of an archiving object, whose files are to be stored in an external archive.

(C) SAP AG LO750 10-17
SAP AG 1999
l Defining the residence times for inspection methods and
master inspection characteristics in Customizing. There
are no residence times for inspection plans.
l Defining the deletion sequence.
Recommended sequence:
n Task lists
n Inspection characteristics
n Inspection methods
Valid
from
Archiving
date
Residence time
Organizing the Archiving of QM Master Data (1)

(C) SAP AG LO750 10-18
SAP AG 1999
l Prerequisites for deletion:
n You must mark task lists with a deletion flag in the task list
header.
n 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.
l The archiving process:
n 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.
n In the second step, the master records are archived and deleted.
Organizing the Archiving of QM Master Data (2)

(C) SAP AG LO750 10-19
SAP AG 1999
l Defining the residence times and deletion times.
l You can only delete after archiving.
l Deletion sequence:
Last change made to the
usage decision
Archiving date
Deletion time
Deletion time
Residence time
Deletion date
Single results
Samples
Characteristics and
operations
Inspection lots
Organizing the Archiving of QM Movement Data

(C) SAP AG LO750 10-20
SAP AG 1999
Archiving Process Archiving Process
Before the first Before the first
archiving session archiving session
Before the first session
for a specific archiving object
Before each archiving
session
Coordinate
activities
Check dependencies
Coordinate activities
Check dependencies
Check application
Customizing
Check Customizing for ADK
Logical file name
Large archive file
ArchiveLink
Deletion program
Coordinate activities
Check disk space
Schedule archiving jobs
Check results
Save archiving files
Archiving Session Checklist

(C) SAP AG LO750 10-21
SAP AG 1999
l 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.
l 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.
Archiving: Unit Summary

LO750 Quality Management Configuration and Organization

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LO750 Quality Management Configuration and Organization

Uploaded by

Copyright:

Available Formats

LO750 Quality Management Configuration

and SQL Server

are registered trademarks of IBM Corporation.

is a registered trademark of ORACLE Corporation.

-OnLine for SAP and INFORMIX

are registered trademarks of the Open Group.

is a registered trademark of Sun Microsystems, Inc.

is a registered trademark of Sun Microsystems, Inc., used under license for

You might also like