127_ERP607_BPD_EN_UK

EHP7 for SAP ERP 6.0

September 2013

English

Quality Management for Procurement with Vendor Evaluation (127)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practices Quality Management for Procurement with Vendor Evaluation (127): BPD

Copyright

© 2013 SAP AG or an SAP affiliate company. 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.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

© SAP AG Seite 2 von 25


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Contents

1 Purpose.................................................................................................................................. 5

2 Prerequisites.......................................................................................................................... 5

2.1 Master Data and Organizational Data.............................................................................5

2.2 Business Conditions........................................................................................................6

2.3 Roles............................................................................................................................... 6

3 Process Overview Table.........................................................................................................7

4 Process Steps........................................................................................................................ 8

4.1 Purchasing...................................................................................................................... 8

4.1.1 Displaying List of Purchase Requisitions to be Assigned and Converted to Purchase Orders.................................................................................................................... 8

4.1.2 Receiving Goods from Vendor to the Purchase Order.............................................8

4.2 Quality Inspection..........................................................................................................10

4.2.1 Calling Inspection Lot Worklist – Inspection Instruction and Report.......................10

4.3 Goods are OK...............................................................................................................11

4.3.1 Recording Results..................................................................................................11

4.3.2 Usage Decision......................................................................................................12

4.3.3 Evaluating Vendor..................................................................................................13

4.4 Goods are not OK.........................................................................................................14

4.4.1 Recording Results with defects..............................................................................14

4.4.2 Usage Decision and Quality Notification Creation..................................................15

4.4.3 Creating Return Delivery........................................................................................17

4.4.4 Goods Issue for Return Delivery............................................................................18

4.4.5 Completing Notification..........................................................................................19

4.4.6 Evaluating Vendor..................................................................................................20

5 Appendix.............................................................................................................................. 21

5.1 Reversal of Process Steps............................................................................................21

5.2 SAP ERP Reports.........................................................................................................24

5.3 Used Forms...................................................................................................................24



Quality Management for Procurement with vendor Evaluation

1 PurposeThis scenario deals with quality inspection activities during the procurement process.

A customer orders goods from specified vendor 300001. On goods receipt, an inspection lot is generated according to the defined material specification. A usage decision is then made as to whether to accept or reject the material, based on the inspection result.

Both alternatives are described in this document. Therefore the document splits up after chapter 4.2.1 Calling Inspection Lot Worklist – Inspection Instruction and Report.

If the material is accepted the chapter 4.3 Goods are OK and its subchapters are relevant.

If the material is rejected the chapter 4.4 Goods are not OK and its subchapters are relevant.

It is only possible to process one of the alternatives with an inspection lot. If you want to process both alternatives you have to create another inspection lot by processing the chapters 4.1 Purchasing and 4.2 Quality Inspection again.

The scenario focuses on the following activities:

Goods Receipt based on Purchase Order

Inspection Defects Recording

Usage Decision after inspection

Quality Notification creation and completion in case of rejection

Goods Return to Vendor with Return Delivery Creation in case of rejection

Vendor Evaluation process

2 Prerequisites

2.1 Master Data and Organizational DataA range of indispensable master and organizational data was created in your ERP system in the implementation phase, such as the data that reflects the organizational structure of your company, as well as master data that suits its operational focus, for example, master data for materials, vendors, customers, and so on.

This master data usually consists of standardized SAP Best Practices default values and enables you to go through the process steps of this scenario.

You can test the scenario with other material, or organizational data for which you have created master data. To find out how to create master data, refer to the Master Data Procedures documentation.

Use the following master data in the process steps described in this document:



Manufacturing / TradeMaster data Value Comments

Material R120

Plant 1000

Vendor 300001

PO from scenario 130

2.2 Business ConditionsThe business process described in this Business Process Documentation is part of a bigger chain of integrated business processes or scenarios. Consequently, you must have completed the following processes and fulfilled the following business conditions before you can start going through this scenario:

Business condition Scenario

You have completed the following steps described in the Business Process Documentation Prerequisite Process Steps (154):

- Roll MM Period to Current Period. Perform this activity if the MM period in the system is not set to the current period. Usually, this activity has to be done once a month.

- Product Costing: Costing Run

Prerequisite Process Steps (154)

2.3 Roles

UseThe following roles must have been installed to test this scenario in the SAP NetWeaver Business Client (NWBC). The roles in this Business Process Documentation must be assigned to the user or users testing this scenario. You do not need these roles if you are not using the NWBC interface, but the standard SAP GUI.

PrerequisitesThe business roles have been assigned to the user who is testing this scenario.

Business role Technical name Process step

Employee (Professional User)

SAP_NBPR_EMPLOYEE_S Assignment of this role is necessary for basic functionality.

Warehouse Clerk SAP_NBPR_WAREHOUSECLERK_S

MIGO, VL02N

Quality Specialist SAP_NBPR_QUALMGR_S QA32, QE01, QA11, QF11, QM10

Purchaser SAP_NBPR_PURCHASER_S ME61



3 Process Overview TableProcess step External

process reference

Business condition

Business role

Trans-action code

Expected results

Purchasing

Process purchase requisitions to Purchase Orders

Procurement without QM (130)

See scenario no. 130



Receive Goods from Vendor to the Purchase Order

Warehouse Clerk

MIGO Inspection lot from goods receipt

Quality Inspection

Call Inspection Lot Worklist (optional)

Quality Specialist

QA32 Worklist with inspection lots without a usage decision is shown.

Goods are OK

Record Results Quality Specialist

QE01 Result of the quality inspection recorded

Usage Decision Quality Specialist

QA11 Usage decision for material inspection lot

Evaluate Vendor Purchaser ME61 Vendor evaluation

Goods are not OK

Record Results Quality Specialist

QE01 Result of the quality inspection recorded

Usage Decision and Quality Notification Creation

Quality Specialist

QA11 Usage decision for material inspection lot

Create Return Delivery

Quality Specialist

QM10 Quality notification entered into the system, return delivery created

Post Goods Issue Warehouse Clerk

VL02N Return goods issue posted

Complete Notification

Quality Specialist

QM11 Quality notification completed

Evaluate Vendor Purchaser ME61 Vendor



Process step External process reference

Business condition

Business role

Trans-action code

Expected results

evaluation

4 Process Steps

4.1 Purchasing

4.1.1 Displaying List of Purchase Requisitions to be Assigned and Converted to Purchase Orders

Procurement without QM (130)

ProcedureTo execute this activity process the following steps using the master data from this document (also see the table below):

Steps to process from scenario Procurement without QM (130)

Create Purchase Order manually

Approval of Purchase Orders (optional)

Master Data

Field name Description User action and values Comment

Material R120

Vendor 300001

ResultAfter executing this step, the purchase order is created with reference to each item of the purchase requisition.

For printing handling and procedure of purchase orders please see the building block Procurement without QM (130), section Print Purchase Order.

4.1.2 Receiving Goods from Vendor to the Purchase Order

UseTake packing slip from container and verify part number on container and quantity matches packing slip information. Also verify number of containers received.

Procedure



1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics → Materials Management → Inventory Management → Goods Movement → Goods Receipt → For Purchase Order → PO Number Known

Transaction code MIGO

2. On the Goods Receipt - <Username> screen, ensure that Goods Receipt and Purchase Order are selected in the fields on the top of the screen.

3. Enter the purchase order number and choose Enter.

4. Choose 2 Individual slip with inspection text checkbox to print a goods receipt/issue slip.

If multiple lines exist, choose the Close Detail Data button to be able to view all lines. Choose the line and continue the process. If you want to find an item with a particular part number within the PO, enter the part number then choose Search in Item Overview. When a line appears with the correct part number, select the line and continue the process.

5. On the Quantity tab page, under item level, enter the quantity to be received.

Production data needs to be entered if Batch Management is applicable.

6. Change storage location if necessary and enter the text field (optional).

7. If material is serialized: On the Serial Numbers tab page, enter serial number. If serial number is unknown, search for one by using the Find button.

8. If material is handled in batches: On the Batch tab page, enter the external batch number, or leave empty for internal number assignment.

9. Choose the Item OK checkbox at the bottom of screen.

10. Choose Post.

Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role

Business role Warehouse Clerk

(SAP_NBPR_WAREHOUSECLERK_S)

Business role menu Warehouse Management → Receiving → Purchase Order

1. On the All Purchasing Documents Ready for Goods Receipt screen, mark <your Purchasing Document >.

2. Choose Create Material Document.

3. Choose Individual slip checkbox to print a goods receipt/issue slip.

If multiple lines exist, choose the Close Detail Data button to view all lines. Choose the line and continue the process. To find an item with a particular part number



within the PO, enter the part number then choose Search in Item Overview. When a line appears with the correct part number, select the line and continue the process.

4. On the Quantity tab page, under item level, enter the quantity to be received.

Production data needs to be input if Batch Management is applicable.

5. Change the storage location if necessary, and enter the text field (optional).

6. If material is serialized: On the Serial Numbers tab page, enter serial number. If serial number is unknown, search for one by using the Find icon.

7. If material is handled in batches: On the Batch tab page, enter the external batch number or leave empty for internal number assignment.

8. Select the Item OK checkbox at the bottom of screen.

9. Choose Post.

ResultAn inspection lot has been created, and it can be viewed by displaying the material document.

4.2 Quality Inspection

4.2.1 Calling Inspection Lot Worklist – Inspection Instruction and Report

UseThe purpose of this activity is to print out the inspection instruction and the inspection report.

Procedure



SAP ECC menu Logistics → Quality Management → Quality Inspection → Worklist → Inspection → Change Data

Transaction code QA32


Business role Quality Specialist

(SAP_NBPR_QUALMGR_S)

Business role menu Quality Management → Quality Inspection → Inspection Lot → Change Data for Inspection Lot

2. On the Inspection Lot Selection screen, make the following entries, and then choose Enter:


Lot created on From-date and to-date System proposes




dates

Plant Plant 1(1000) You can also use input help (F4)

List settings Select only inspection lots without a usage decision

3. Choose Execute (F8).

The worklist with inspection lots, without a usage decision, is shown. From here, the following steps can be performed directly (instead of accessing the transactions step by step):

1. Print inspection report button Inspection Report

2. (Optional) If it is not visible, in the screen, go to the right and open the list.

On the Result Printout screen, enter the inspection lot number in the Inspection Lot field and form YB_QM_INSP_RESUL in the Form field (section print parameters), then choose Execute.

In the Print: window, enter a printer (for example, LOCL for local printer) in the Output Device field then choose Print.

You can also choose Print Preview to check the layout and details before print out the report.

ResultThe inspection lot information is printed out for review.

4.3 Goods are OK

4.3.1 Recording Results

UseThe purpose of this activity is to record the results of the quality inspection of the goods in the system. In this case all goods are accepted and no defects are recorded.

Procedure



SAP ECC menu Logistics → Quality Management → Quality Inspection → Inspection Result → For Operation → Record

Transaction code QE01






Business role menu Quality Management → Quality Inspection → Inspection Results → Record Characteristic Results

2. On the Record Results: Initial screen, make the following entries, then choose Enter:


Inspection Lot Inspection lot number determined in the step before

You can also use input help (F4)

3. On the Record Results: Characteristic Overview screen, make the following entries, and then choose Enter:


Accept X Flag checkbox

Inspected <Quantity of lot> Enter total quantity

Result Result of specification

01 (for okay) You can also use input help (F4)

4. Choose Close

5. Choose Save.

6. Choose Back to return to the SAP Easy Access screen.

Result

The result of the quality inspection for the material has been recorded.

4.3.2 Usage Decision

UseSince no defect was recorded during the inspection procedure, the usage decision should be made to accept the material. Subsequently, the material should be sent to unrestricted stock.

Procedure



SAP ECC menu Logistics → Quality Management → Quality Inspection → Inspection Lot → Usage Decision → Record





Business role menu Quality Management → Quality Inspection → Inspection Lot → Record Usage Decision



2. On the Record Usage Decision: Initial Screen, enter the inspection lot determined in the previous step and choose Enter to confirm your entries.

3. On the Record Usage Decision: Characteristic Overview screen, in the UD code field, use the input help (F4) to choose YB02-Usage Decision at Goods Receipt 01 Quality test complied), and confirm with Enter.

If the dialog box: Reqd characteristics still open! Do you want to force inspection completion? appears, choose Yes, so you do not have to inspect every single item of the whole amount

Currently the selection of code groups within the input help (F4) is not restricted, so that all available code groups will be listed. To restrict it to the relevant code group (here YB02-01), refer to the configuration guide for this building block, section Maintain Inspection Type.

4. Choose the Inspection lot stock tab page.

5. Choose the Proposal button.

6. Choose Enter to confirm your entries.

7. Choose Save to save the Usage Decision. The system issues the message Usage Decision for lot Plant_1 (1000) xxxxxxxxxx is saved.

8. When saving and if material is serialized: In the Copy Serial Numbers dialog box, delete the serial numbers which should not be posted to the stock use, for example, unrestricted or blocked.


Result

The Usage Decision has been made for the material inspection lot.

In the stock overview you can see, that the amount in the quality inspection stock has been moved to the unrestricted stock.

SAP GUI: Transaction MMBE

SAP NWBC: Role Warehouse Manager (SAP_NBPR_WAREHOUSEMANAGER_M), path Warehouse Management Inventory Control Display Stock Overview

Enter material, plant and storage location from above.

4.3.3 Evaluating Vendor

Use



The purpose of this activity is to valuate the vendor after the goods have been inspected and returned.

Procedure



SAP ECC menu Logistics → Materials Management → Purchasing → Master Data → Vendor Evaluation → Maintain

Transaction code ME61


Business role Purchaser

(SAP_NBPR_PURCHASER_S)

Business role menu Purchasing → Reporting → Vendor Evaluation → Maintain Vendor Evaluation

2. On the Maintain Vendor Evaluation: Initial Screen, make the following entries: and choose Enter.


Purch. Organization 1000

Vendor Domestic vendor 01 (300001)

3. On the Maintain Vendor Evaluation: Overview of Main Criteria screen, set the Weighting Key to 01.

4. On the same screen, choose Edit Auto. new Evaluation from the menu.

In SAP NWBC, choose More first.

The system then evaluates the vendor again, and the score against Quality is increased automatically.

5. Choose Save to confirm your entries.

The system ends the vendor evaluation process with the message Evaluation record changed.


ResultVendor evaluation is performed.

4.4 Goods are not OK

4.4.1 Recording Results with defects

Use



The purpose of this activity is to record the results of the quality inspection of the goods in the system. In this case the goods are defect and the quality check fails.

Procedure



SAP ECC menu Logistics → Quality Management → Quality Inspection → Inspection Result → For Operation → Record

Transaction code QE01




Business role menu Quality Management → Quality Inspection → Inspection Results → Record Characteristic Results

2. On the Record Results: Initial screen, make the following entries, then choose Enter:


Inspection Lot Inspection lot number determined in the step before

You can also use input help (F4)

3. On the Record Results: Characteristic Overview screen, make the following entries, and then choose Enter:


Reject X Flag checkbox

Inspected <Quantity of lot> Enter total quantity

Result Result of specification

02 (for not okay) You can also use input help (F4)

4. Choose Close.

5. Choose Save.


Result

The result of the quality inspection for the material has been recorded.

4.4.2 Usage Decision and Quality Notification Creation

UseSince a defect was recorded during the inspection procedure, the usage decision should be made to reject the material. Subsequently, the material should be sent to blocked stock, and a quality notification created to inform the vendor of the rejection.



Procedure



SAP ECC menu Logistics → Quality Management → Quality Inspection → Inspection Lot → Usage Decision → Record





Business role menu Quality Management → Quality Inspection → Inspection Lot → Record Usage Decision

2. On the Record Usage Decision: Initial Screen, enter the inspection lot determined in the previous step and choose Enter to confirm your entries.

3. On the Record Usage Decision: Defect Overview screen, in the UD code field, use the input help (F4) to choose YB02-01 Usage Decision at Goods Receipt 02 Quality test failed (to blocked stock), and confirm with Enter.

If the dialog box: Reqd characteristics still open! Do you want to force inspection completion? appears, choose Yes, so you do not have to inspect every single item of the whole amount

Currently, the selection of code groups within the input help (F4) is not restricted, so that all available code groups are listed. To restrict the relevant code group (here YB02-01), please refer to the configuration guide of this building block, section Maintain Inspection Type.

4. Select the defects item line, and then choose Activate notification or Ctrl+F2.

5. On the Quality Notification: Activate screen, make the following entries:


Priority 2 High

Coding YB02-01 03 Vendor Problem

Description Reject for defects inspected

Coordinator <user> For example, your user name

6. Choose Enter to confirm your entries. The system activates the notification and issues the message Marked defect item(s) activated.



7. Choose the Inspection lot stock tab page.

8. Choose the Proposal button, and enter 1060 in the StLoc field.

Optional: You can also post the quantity to scrap stock in this step and perform related scrapping steps. These are not described in this scenario.


10. Choose Save to save the Usage Decision. The system issues the message Usage Decision for lot xxxxxxxxxx is saved.


Result

The Usage Decision has been made for the material inspection lot.

4.4.3 Creating Return Delivery

UseFollowing rejection of the material, you need to create a return delivery to return the material to the vendor. A customer number is assigned to the vendor as a return customer.

Procedure



SAP ECC menu Logistics → Quality Management → Quality Notification → Worklist → Notification → Change Data

Transaction code QM10




Business role menu Quality Management → Quality Notifications → Change List of Quality Notifications

2. On the Change List of quality notifications: Selection of Notifications screen, make the following entries:


Outstanding Set indicator

Notification Date Use the date system proposed

3. Choose Execute to load the notifications.

4. Select the applicable notification, and choose Notification or Ctrl + Shift + F6.



5. On the Change Notification: Vendor-Rel. Defect screen, go to Notification Print Notification. (NWBC: More… Notification Print Notification)

6. Select the ShopPaper 5999 (Rejection Report) and choose Print/Fax (F8) to print the Rejection Report.

7. On the Change List of Qual. Notification: List of Notifications screen, select your notification, and choose Notification.

8. On the Change Notification: Vendor-Rel. Defect screen, choose QM: Activity Description in the Action box.

9. On the Internal Note screen, enter a description, that is, Return Delivery.


11. In the Action box, choose Log Telephone Call, and make the following entries in the Outgoing Call window:


Start Use the date system proposed

End Use the date system proposed

Conversation status

Reached

Subject of conversation

description

12. Confirm with Enter.

13. On the Change Notification: Vendor-Rel.Defect screen, choose the green flag Put in Process.

14. Save your entries.

15. On the Change List of Qual. Notification: List of Notifications screen, select your notification, and choose Notification.

16. On the Change Notification: Vendor-Rel. Defect screen, choose Create Return Delivery in the Action box.

17. On the Create Return Delivery screen, enter 0003 in the Reason for Movement field and 1060 in the Stor.loc field.


19. Confirm the following warning message with Yes.

20. The system then creates the return delivery with the message Return delivery created with number xxxxxxxxxx.

21. Choose Back twice to return to the SAP Easy Access screen.

If an error occurs during the last step of delivery creation, go back to the SAP Easy Access screen and repeat this step.



ResultThe quality notification has been entered into the system and return delivery has been created.

4.4.4 Goods Issue for Return Delivery

UseIn this activity, you fill in the picking quantity and post the goods issue.

Procedure



SAP ECC menu Logistics → Logistics Execution → Outbound Process → Goods Issue for Outbound Delivery → Outbound Delivery → Change → Single Document

Transaction code VL02N




Business role menu Warehouse Management → Shipping → Outbound Delivery → Change Delivery

2. Enter the created delivery number and choose Enter.

3. On the Return Del. To Vendor 8xxxxxxx : Overview screen, choose the Picking tab page, and enter the following data:


Picked Qty. Picked Quantity Enter your PO quantity

4. Choose Post Goods Issue.

5. The system displays the message Return Del. To Vendor xxxxxxxxxx has been saved.


ResultThe return goods issue is posted.

The print out of the delivery note is executed automatically and immediately (see settings in transaction VV23 for Output Type LD00, and user setting defaults in transaction SU01).

You can also start the print out manually:

1. On the Display Outbound Delivery Initial Screen: From the menu, choose Outbound Delivery Issue delivery Output.



2. Choose the line with the message type LD00 – Delivery Note.

3. Choose the PRINT icon

4.4.5 Completing Notification

UseAfter the material is sent back to the vendor, the notification should be closed.

Procedure



SAP ECC menu Logistics → Quality Management → Quality Notification → Worklist → Notification → Display Data

Transaction code QM11




Business role menu Quality Management → Quality Notifications → Display List of Quality Notifications

2. On the Display List of Qual. Notification: Selection of Notifications screen, make the following entries:


In Process Select indicator

Notification Date Use the date system proposed

3. Choose Execute to load the notifications.

4. Choose Display Change to switch from display to change mode.

5. Select the notification with the description Reject for defects inspected.

6. Choose Notification.

7. On the Change Notification: Vendor-Rel. Defect screen, choose Complete.

8. Confirm the information message with the proposed time and External Origin by choosing Enter.

9. The system then completes the notification with the message Notification xxxxxxxxxx completed.

10. Choose Back twice to return to the SAP Easy Access screen.

ResultQuality notification is completed.



4.4.6 Evaluating Vendor

UseThe purpose of this activity is to valuate the vendor after the goods have been inspected and returned.

Procedure



SAP ECC menu Logistics → Materials Management → Purchasing → Master Data → Vendor Evaluation → Maintain

Transaction code ME61




Business role menu Purchasing → Reporting → Vendor Evaluation → Maintain Vendor Evaluation

2. On the Maintain Vendor Evaluation: Initial Screen, make the following entries, and choose Enter:


Purch. Organization

1000

Vendor Domestic vendor 01 ( (300001)

3. On the Maintain Vendor Evaluation: Overview of Main Criteria screen, set the Weighting Key to 01.

4. On the Maintain Vendor Evaluation: Overview of Main Criteria screen, choose Edit Auto. new Evaluation from the menu.

In SAP NWBC, choose More first.

5. The system then evaluates the vendor again, and the score against Quality is decreased automatically.

6. Choose Save to confirm your entries.

7. The system ends the vendor evaluation process with the message Evaluation record changed.


ResultVendor evaluation is performed.



5 Appendix

5.1 Reversal of Process StepsIn the following section, you can find the most common reversal steps, which you can take to reverse some of the activities described in this document.

Receive Goods from Vendor to Purchase Order

Transaction code (SAP GUI) MIGO

Reversal: Cancel material document

Transaction code (SAP GUI) MBST



Business role menu Warehouse Management Material Documents Cancel material document

Comment Warehouse Management Consumption and Transfers Cancel Material Document

Evaluate Vendor

Transaction code (SAP GUI) ME61

Reversal: Evaluate vendor

Transaction code (SAP GUI) ME61



Business role menu Purchasing Reporting Vendor Evaluation Maintain Vendor Evaluation

Comment

Defects Recording

Transaction code (SAP GUI) QF11

Reversal: Change defects recording

Transaction code (SAP GUI) QF02



Business role menu Quality Management Quality Inspection Defects Change Defect Data

Comment

Usage Decision and Quality Notification Creation



Transaction code (SAP GUI) QA11

Reversal: Change usage decision

Transaction code (SAP GUI) QA12



Business role menu Quality Management Quality Inspection Inspection Lot Change Usage Decision With History

Comment

Create Return Delivery

Transaction code (SAP GUI) QM11

Reversal: Delete return delivery

Transaction code (SAP GUI) VL02N



Business role menu Warehouse Management Shipping Outbound Delivery Change Delivery

Comment

Post Goods Issue

Transaction code (SAP GUI) VL02N

Reversal: Cancel goods issue

Transaction code (SAP GUI) VL09



Business role menu Warehouse Management Shipping Outbound Delivery Cancel Goods Issue for Delivery Note

Comment

Complete Notification




Reversal: Change notification




Business role menu Quality Management Quality Notifications Change Quality Notification

Comment

5.2 SAP ERP Reports

UseThe table below lists the most frequently used reports that help you to obtain additional information on this business process.

You can find detailed descriptions of the individual reports in the following BPD documents, which provide a comprehensive compilation of all important reports:

Financial Accounting: SAP ERP Reports for Accounting (221)

Logistics Processes: SAP ERP Reports for Logistics (222)

Note that the descriptions of some reports that are an indispensable part of the process flow may be located directly in the section where they belong.

ReportsReport title Transaction code Comment

List Display of Purchase Requisitions ME5A A list of all selected purchase requisitions is displayed.

List of Notifications QM11 A list of several notifications, from which you can select one or more notifications for editing or displaying.

Stock Overview MMBE The stock overview is displayed.

5.3 Used Forms

Use



In some of the activities of this business process, forms were used. The table below provides details on these forms.

Common form name

Form type Used in process step

Output type

Technical name

Delivery Note SmartForm Goods Issue Create Return Delivery

LD00 YBUK_SDDLN

Result printout SAPscript form

Call Inspection Lot Worklist – Inspection Instruction and Report

YB_QM_INSP_RESUL

Rejection Report SmartForm Create Return Delivery

YBUK_QMCOM
