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 Technical Areas of QM Customizing (2) ....................................................................................................... 2-8 Technical Areas of QM Customizing (3) ....................................................................................................... 2-9 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 Change Procedure (2)................................................................................................................................... 6-13 Change Procedure (3)................................................................................................................................... 6-14 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 Customizing for the Action Box (2)............................................................................................................. 7-12

Customizing for the Action Box (3)............................................................................................................. 7-13 Customizing for the Action Box (4)............................................................................................................. 7-14 Customizing for the Action Box (5)............................................................................................................. 7-15 Customizing for the Action Box (6)............................................................................................................. 7-16 Customizing for the Action Box (7)............................................................................................................. 7-17 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 OrganizationConfiguration and Organization

R/3 Release 4.6 August 2000 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: Some software products marketed by SAP AG and its distributors contain proprietary software

components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered

trademarks of Microsoft Corporation. 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. ORACLE is a registered trademark of ORACLE Corporation. INFORMIX-OnLine for SAP and INFORMIX Dynamic ServerTM are registered trademarks of

Informix Software Incorporated. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide

Web Consortium, Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for

technology invented and implemented by Netscape. 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 ProcessIndustry

LO721 3 days

QM in Sales and Distribution / QualityCertificates

LO725 2 days

QM inProcurement

LO715 3 days

QM in Discrete and RepetitiveManufacturing

LO720 2 days

SAP AG 1999

Recommended R/3 Development Environment IMG Basic Concepts

Required BC400 - ABAP Workbench: Basics LO705 - Quality Inspections

Prerequisites

SAP AG 1999

Participants: Project team Employees responsible for the technical

introduction of the QM component Duration: 3 days

Target Group

Notes to the user 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

Course Goals

Course Objectives

Course Content

Course Overview Diagram

Main Business Scenario

Contents:


SAP AG 1999

At the conclusion of this course, you will understand: The technical settings in Customizing for the

Quality Management (QM) application component Functions that enable additional customer-

specific enhancements without modification The archiving of QM data

Course Goals


SAP AG 1999

At the conclusion of this course, you will be able to define: Technical Customizing settings

The SAP enhancement concept

SAPscript forms in QM

Interfaces (QM-IDI, QM-STI, BAPIs)

The logical database in QM

Archiving options

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 94

Ease of Use 5

SAPscript 6

Follow-Up Actions 7

Interfaces 88

Status Management/User Status

3Customer Enhancements

Archiving 10

Course Overview 1

2Basics


SAP AG 1999

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:

Customizing Projects

QM Customizing Structure

Technical Areas of QM Customizing


SAP AG 1999

Show how Customizing functions are linked to the IMG

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 94

Ease of Use 5

SAPscript 6

Follow-Up Actions 7

Interfaces 88



Archiving 10

Basics 2

1Course Overview


SAP AG 1999

Our company wants to gain an impression of theconfiguration 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

The SAP Reference IMG contains all Customizing activities. The Project IMG contains the selected Customizing activities. 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

IMGIMG

Quality Management

Quality Planning

Quality Inspection

Quality Certificates


Quality Control

Environment

QM Customizing Structure

Test Equipment Management

QM in Logistics

Basic Settings

Menu path for Customizing: SAP Easy Access > Tools > AcceleratedSAP > Customizing > Edit Project

The Implementation Guide for the QM component is divided into functions. The steps can be processed in the given order.


SAP AG 1999

Function Module Assignment Quality Planning

Rules for sample determination

Valuation rules

SPC criteria

Inspection points

Quality Inspection

Follow-up actions for the usage decision

Quality score procedures

Sample types (FM for label printing)

Quality Certificates

Data origin


Follow-up functions

Follow-up actions for tasks

Course component

Technical Areas of QM Customizing (1)


SAP AG 1999

Scheduling a program as a job Inspection for deadline monitoring

Automatic usage decision

Search helps Inspection characteristic

Inspection method

Inspection plan

Quality info record

Inspection lot

Certificate profiles

Quality notifications



SAP AG 1999

Function enhancements Subscreens

Function keys

Function modules

Field selection

Status management

List variants

Condition technique

Partner concept

Interfaces

Distribution of ALE master data

Workflow

Archiving

Course component


(C) SAP AG LO750 2-10

SAP AG 1999

Basics: Unit Summary

Show that the IMG contains documentation for each activity. You can execute the activities directly.

Explain that functions are available for project management and project documentation.

Process each Customizing activity using the IMG.

Explain how QM Customizing is structured into BasicSettings, QM in Logistics, Quality Planning, Quality Inspection, Quality Certificates, Quality Notifications,Quality Control, Test Equipment Management, and Environment

Describe how the QM application component offers awide range of options for setting up your system to suit your needs.

You are now able to:


SAP AG 1999

Customer Enhancements

Contents:

Enhancing Functions

SAP Enhancements and Customer Enhancement Projects

Procedure for SAP and Customers

Processing Components

Activating Enhancement Project

Creating Field Exits


SAP AG 1999

Understand the enhancement concept at SAP

Create an enhancement project

Customer Enhancements: Unit Objectives



SAP AG 1999

Customer Enhancements: Course Overview Diagram

Evaluations 94

Ease of Use 5

SAPscript 6

Follow-Up Actions 7

Interfaces 88


2Basics

Archiving 10

Customer Enhancements 3

1Course Overview


SAP AG 1999

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 developmentCustomer development

CustomizingCustomizing

EnhancementEnhancement

Request enhancementAvoid modification

Request enhancementAvoid modification

Enhancing Functions

Before carrying out a modification, check whether your request can be fulfilled using Customizing or the enhancement concept.

You can request enhancements in the SAPNet R/3 Frontend.


SAP AG 1999

Function module

Field 1

Menu 2Function 1Function 2Cust. functionFunction 3

Menu 1 Menu 3

Field x

Field y

Program Enhancements

Screen exit

Program exit

Menu exit

Field exit

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)

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

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 SAPSAPenhancementsenhancements

DefinitionDefinitionofof

enhancementenhancementprojectsprojects

CMOD

Customer Enhancement Project

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).

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

CC

C

E

C

CC

C

E

E

E

P

E

E

P

C EComponent SAP enhancement P Customer enhancement projects

C E

C

SAP Enhancements and Customer Enhancement Projects

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).

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

SAP application programmers plan possible application enhancements in their applications and define the required components. They then combine these components to create SAP enhancements.

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 componentsfor enhancement

project

Process componentsfor enhancement

project

Document enhancement project

Document enhancement project

Function modules

Menu entries

Subscreens

Customer documentation:

EE

E

P

Activate enhancement project

Activate enhancement project ActivateActivate

Customer Procedure

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

CreateCreate

SaveSave

Creating a Customer Enhancement Project

Project Management

Attribute

Project

Short txt

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.

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

SaveSave

Assigning SAP Enhancements to Customer Project

Project Management

Project

SAP enhancements

Change SAP Change SAP enhancementsenhancements

Customers edit the menu exits using Project Management. 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. 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 boxDialog boxDialog boxLang.

TextScreen PainterScreen PainterScreen Painter

Customers process the components in the enhancement project using the Project Management function.

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 projectActivate project

Activating Enhancement Project

Project Management

Project

Activating the enhancement project means that all of the components are activated. Once the project has been successfully activated it has the status active.

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.

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 enhancements11

Create a field exit22

Create function module44

Field exit for data element ..?33

Activate function module66

Assign program/screen(for local field exit only)7

7

Activate field exit88

Process function module55

Display FM: InterfaceDisplay FM: InterfaceDisplay FM: InterfaceImport parameter

Export parameter

INPUT

OUTPUT

ABAP Function Library: Initial screenABAP Function Library: Initial screenABAP Function Library: Initial screen

Function moduleFIELD_EXIT_

Creating a Field Exit

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.

Field exits are only considered when a screen is generated, if the profile parameter "abap/fieldexit = YES" is set on all application servers.

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

Field exits cannot be processed with the debugger.

(C) SAP AG LO750 3-16

SAP AG 1999

SAP application programmers plan program exits, menu exits, and screen exits for theapplication and combine them to form SAPenhancements.

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


Contents:

Using Status Management

Defining and Creating a Status Profile

Assigning Status Profile to Object Types

Defining and Assigning User Status toBusiness Transactions

Selection Profile


SAP AG 1999

Use general status management

Define your own user statuses in addition to the existing system statuses and assign them to objects

Create and use selection profiles

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 88

Basics


Archiving 10

Status Management/User Status 4

1Course Overview


SAP AG 1999

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

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 transactionfor example,- Releasing- Closing

Number ofactive statuses

Number ofexecutable transactions

changes defines

Statuses

The current processing status of an object is documented using one or more statuses. 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.

If a business transaction is carried out, it can, in turn, set or delete one or more statuses for the affected object.

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

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.

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 profileCreateCreate sstatus profiletatus profile

Assign status profile to object types

AssignAssign statusstatus profileprofile to to object typesobject types

Define user statusDefine user statusDefine user status

Assign user statusto businesstransactions

Assign user statusAssign user statustoto businessbusinesstransactionstransactions

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 sstatus profiletatus profile

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 typesPermitted object types

TaskTask

InspInsp.. lot withlot with planplan and charsand chars

InspInsp.. lot withlot with plan w/oplan w/o charschars

InspInsp.. lotlot w/o planw/o plan or charsor chars

Quality info recordQuality info record

Quality notificationQuality notification

Quality certificate profileQuality certificate profile

Partial lotPartial lot

Assigning Status Profile to Object Types

Assign status profile to object types

Assign status profileAssign status profile to to object typesobject types

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 statusUser statusStatus

number Status Short textLong text

Init.status

Lowest status no.

Highest status no.

Auth. codePriorityPosition

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 statusDefine user statusDefine user status

You must enter a four-character (maximum length) language-dependent ID to identify each user status.

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 controlTransaction controlBusiness transaction No influence Allowed Warning Disalld No action Set Delete

Status profileStatus profile LO705-00

StatusStatus LKD

Make usage decision

Assigning User Status to Business Transactions



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

Inclusive Exclusive Active Inactive Never active


System status 1 System status 1

and / or

and / or and / or



System status 2 System status 2

Without status profile



System status 1 oruser status 1


With status profile





Selection Profile

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.

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.

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

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

Status management is used in the following QM objects: Quality info record, inspection lot, quality certificate, quality notification.

The SAP System differentiates between system status and user status. The system status is defined by SAP, and the user status is freely defined.

You can define your own status profiles. Each status profile must be assigned to at least one object. Each status profile contains one or more allowed statuses. You can define the system response for each status within the framework of the SAP-defined business transactions.

You can define a status profile and user status in several languages.

You can use selection profiles to define status combinations for selecting objects.

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:

Configuration Using Table Controls

Field Selection

Variable Lists

Results Recording Configuration


SAP AG 1999

Customize the SAP interface to suit a user's requirements using field selection, list variants, and table control

Configure results recording

Ease of Use: Unit Objectives



SAP AG 1999

Ease of Use: Course Overview Diagram

Evaluations 94

Basics 2

SAPscript 6

Follow-Up Actions 7

Interfaces 88



Archiving 10Ease of Use 5

1Course Overview


SAP AG 1999

Our company wants to individually configure itsSAP interfaces.

Ease of Use: Business Scenario


SAP AG 1999

Change column order

Change column width

Create variant Current setting Standard setting

Delete variant

10203040

Item Req. qty. Material Short text I A

10203040

Item Req. qty. Material Short text I A

Configuration Using Table Control

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.

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.

The user-dependent variant takes precedence over the system variant.


SAP AG 1999

1. Upper limit1. Lower limitSelected setBasic sample quantityInfo field 1

GeneralGeneral

Dependent on values of Dependent on values of influencing fieldsinfluencing fields

Modifiable field Input Req. Disp. Hide

Module pool

Screen group

Influencing field

Influencing value

Field Selection

Determine the name of the program, to which the screen belongs. To do this, call up the screen in question and choose System -> Status.

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.

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 fieldsinfluencing 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 variantGeneral 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_. 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)

You can change the list display using display variants. 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 TVARVD: Dynamic date calculationB: User-specific variable

Selection criteria T D B Name of variablesQL_ENSIBCurrent date - xxx, current date + yyy

SelectedNot selectedNot supported

T: Table variable from TVARVD: Dynamic date calculationB: User-specific variable

Variable Lists (Object Selection)

PS

SS

Type The Type field shows whether the type is a parameter (P) or a select option (S).

P (Protect field) selected: The corresponding selection criterion cannot be entered at the start of the program using this variant.

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 (Hide field until) 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.

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.

L (Switch SPA/GPA off) 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 lotOperation

:

:

4711

10

Status

Characteristic closed

Surface

Close on CONTINUE

Close on saving

Skip CH view

Results Recording Configuration

Customizingrecording

configuration

Customizingrecording

configuration

5

Userparameters

Userparameters

Results recording can be made easier by configuring the recording procedure. You can predefine the recording configuration in a table (Customizing). 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

In QM there are a number of ways to define(set) fields to suit the needs of every company and user:

Table control

Field control

Variable lists

By configuring results recording, you can simplify the recording procedure.

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:

Forms and Print Programs

Processing Sequence: Form Processor

Procedure for Changes


SAP AG 1999

Explain the basics of SAPscript

Describe the principle relationship between a print program and form

Show how you can also read data in a form

SAPscript: Unit Objectives



SAP AG 1999

SAPscript: Course Overview Diagram

Evaluations 94

Ease of Use 5

Basics 2 Follow-Up Actions 7

Interfaces 88



Archiving 10

SAPscript 61Course Overview


SAP AG 1999

Our company wants to create forms and print programs using the SAPscript editor.

SAPscript: Business Scenario


SAP AG 1999

Text editorLayout

(forms, styles)

Programming interface Form processor

Database

Maintenance transactions

Application transactions

ABAPWorkbench

ABAPWorkbench

User

SAPscript from User View

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 2Form 2

Form 1Form 1

Form 3Form 3

Dear...

Invoice

Document

Forms

A form defines the appearance and the layout of a document. A form is used for each SAPscript text printout. Forms can already contain standardized text modules with placeholders for variable data. The

application can call up and print the modules as necessary. For layout changes, such as moving a printed area of text, changing the font, paragraph formatting,

and tab settings, you simply change the form. The SAPscript transaction used to edit forms can be reached from the SAP initial screen by choosing

Tools-> SAPscript -> Form. 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 2Form 2

Form 1Form 1

Form 3Form 3

The Print Program

SAP DBSAP DB

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

DocumentDocument

Print program

Application transaction

Form:Form:

Form processor

Invoice

Processing Sequence: Form Processor

SAP DBSAP DB

The interaction of the print program and form help you to create documents to suit your needs. 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. 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.

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.

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 thatthis meetsyourrequirements

yourrequest,andhope that this requestmeetsyour requirements

Chicago StateBan kAcc. no: 0815 4711

Sort code:000000000

Mr D. Test7 Old Road47110 Irving Chicago, 3rd June

Invoice no. 4123-45-556-678

Type.No. Price 00345 200.-00379 150.-02378 50.-00458 300.-Total 700.-

Print programreport jh_form_01.

tables: scustom.select * from scustom...

......call function 'OPEN_FORM'

......call function WRITE_FORM'

......call function CLOSE_FORM'

......

ABAP ABAP reportreportApplication data

Form:

DB

Tasks of the Print Program and Form Processor in SAPscript

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.

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.)

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 FUNCTIONCALL FUNCTION 'OPEN_FORM''OPEN_FORM'EXPORTINGEXPORTING

FORM FORM = .= . . .. .LANGUAGE LANGUAGE = .= . . .. .DEVICE DEVICE = .= . . .. .OPTIONS OPTIONS = .= . . .. .DIALOG DIALOG = .= . . .. .

IMPORTINGIMPORTINGLANGUAGE LANGUAGE = .= . . .. .

EXCEPTIONS ...EXCEPTIONS ... = . . .= . . .

CALL FUNCTIONCALL FUNCTION 'CLOSE_FORM''CLOSE_FORM'IMPORTINGIMPORTING

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

Form Print: Start and Finish

Function module OPEN_FORM initializes the form print. This function must be called before other form functions can be used.

The FORM and LANGUAGE parameters specify the form and requested language. The DEVICE parameter controls the output medium (PRINTER, TELEFAX, SCREEN). The OPTIONS parameter (Structure ITCPO) allows you to specify attributes for the printer or fax

control, for example, number of copies or immediate print. The DIALOG parameter allows you to suppress an entry screen for device parameters (for example,

device names: DEVICE = PRINTER, DEVICE = TELEFAX). The form print must be ended with CLOSE_FORM so that the output can be carried out. 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 changesStructural changes

NewNew text elementstext elementsare neededare needed

Additional dataAdditional datais requiredis required

UsingUsing thethe print print program program to to print print

another another formform

When Do You Modify the Print Program?

Changes to SAP objects are called modifications. 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. 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 fieldscontained in the existingtables, or are new fields and tables required?

Are the necessary fieldscontained in the existingtables, or are new fields and tables required?

Change Procedure (1)

In addition to the standard data that is available, you occasionally need other data. 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? 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 enhancementsalready exist in the form of customer exits?

Do SAP enhancementsalready 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?


Determine whether you only need to modify the form, or whether the print program also has to be modified.

Ensure that the PERFORM command in SAPscript can also be used to retrieve data. 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. 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


Make as few modifications as possible. Use the SAP standard as a template for enhancements. Use the SAP standard form to modify a form and copy it to the customer name space Z or Y. Modify

the copied form. When making structural changes to the form, you must also adjust the print program accordingly. Copy the print program to the customer name space Z or Y. Modify the copied program. Define the new form and, if required, the print program in Customizing. Test your modifications.

(C) SAP AG LO750 6-15

SAP AG 1999

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

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&

/*

lo750 quality management configuration and organization

Documents

course objectives

quality management qm

technical areas of qm

course overview diagram

course goals

course content

qm customizing structure

organization lo750 release