BUSINESS BLUEPRINT DOCUMENT

Quality Management

Version: V4.0
Date: 11th Dec 2007

Page 1 of 70

Document Information
Document Name

Business Blue Print

Title

QYM_QM_BBP_V4.0

Document Purpose
Key Words
Document Status

Complete

Contact for Enquiries

Release
1.0
2.0
3.0
4.0

Document Change Control :
Description Created
Date
Reviewed Date
by
by
Quality
Pavan
21/01/2008
Management Kumar
Quality
Pavan
31/01/2008
Management Kumar
Quality
Pavan
20/02/2008
Management Kumar
Quality
Pavan
08/03/2008
Management Kumar

Approve
d by

Date

Page 2 of 70

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

TABLE OF CONTENT
Master data..............................................................................................................4
Inspection in Procurement..................................................................................12
Inprocess Inspection...........................................................................................18
Inspection after Production................................................................................24
Retesting of Finished goods...............................................................................30
Vendor approval process....................................................................................35
Recurring Inspection...........................................................................................41
Washwater testing................................................................................................46
Quality Notifications............................................................................................51
Calibration of Equipments..................................................................................63

Page 3 of 70

Packaging materials. Master data 1. produced and sold are subjected to certain quality inspections These inspections are carried out based on the Specifications defined Specification can be numerical values and characteristic attributes For all the materials fixed samples are drawn depending on the material Inspection manuals will be attached to the specifications Vendor records are maintained for approval process Inspection procedures will be maintained for all materials 2. In-process Bulk material and Finished materials which are procured.  Not Applicable Page 4 of 70 . all the Raw materials. Organizational Considerations Address any issues agreed in the workshop concerning the SAP organizational structure and this process.1. Describe the naming and numbering convention in case of masters and enterprise structure    The naming convention for Master inspection characteristics will be external The naming convention for the Inspection methods will be external The naming convention for the Sampling procedures will be external 3. Requirements/Expectations A brief / bulleted list of requirements and expectations        In KIMMCO & ROCKWOOL. This typically does not include any SAP specific terms. Explanations of Functions and Events Explain what events and processes trigger this process  Not Applicable 4. Facing materials. General Explanations (For Masters and Enterprise structure include Naming Convention) Describe the business process in detail. it should relate purely to the business rules.

 Not applicable 8.5. Description of Improvements Describe improvements which will result from implementation of the SAP System. Be sure to include any impact on business drivers.  Not Applicable 7. Describe how this process will be addressed in the product. Changes to Existing Organization processes Change management issues as appropriate. Solution in SAP. Page 5 of 70 . Process Diagrams Provide all related process maps or diagrams Material Master QM view Code groups / Selected sets Qualitative Characteristics Inspection Method Master Inspection Characteristics Quantitative Characteristics Sampling Procedure Inspection Plan 6.

g. QM inspection data is the prerequisite for creation of inspection lots in Quality Management. tasks. The data related to the material can be stored at the relevant organizational levels. and sells.Quality Management Master Data Material Master The material master contains information of all the materials that a company procures. or decisions made during an inspection). This information is stored in individual material master records. Quality Management view The Quality Management data is maintained at plant level. stores. observations. Page 6 of 70 . Catalog The Catalogs are used to explicitly define and store information in code form (e. Inspection Description type 01 Z1 Goods Receipt inspection against Purchase Order 02 Z3 In-process Inspection 03 Z4 Goods Receipt from production 04 Z9 Recurring Inspection of Batches 05 Z89 Other Inspection 06 Z101 Vendor approval process 07 Z14 Calibration inspection Post to Inspection Stock: The system posts a material to the Stock in Quality Inspection Inspection with task list: The inspection is performed based on a Task list (Quality Plan). Catalogs would be ensuring that this information is maintained uniformly by assigning a unique key and a descriptive text to each entry. A Catalog Contains unique. Inspection type: It defines how an inspection is performed. The material master record is structured in accordance with the organizational units like plant and storage location. non-numeric data that is stored in a system. produces. The following inspection types would be used depending upon the material movements. data that describes inspection results. GR Processing time: Number of workdays required after receiving the material for inspection and placement into storage. It is the company's central source for retrieving material-specific data. Different Inspection types are assigned to each material No.

at the time of inspection lot processing. Code groups can be used in inspection plans or master inspection characteristics.Catalog is used to store information at the characteristic level in Quality Plan. for example. at the time of usage decision. Codes make up the lowest level of a catalog. a defect location or a usage decision. A code is always assigned to a code group. Plant UD Code Description 01 A Accepted 02 A1 Accepted with one deviation 03 A2 Accepted with two deviations 04 A3 Accepted with three deviations 03 R Rejected 04 R1 Scrap Codes Codes describe qualitative contents in machine form that can be easily processed. We can select codes from different code groups within a catalog type. Code groups Code groups are used to combine and structure codes within a catalog type Code groups are used at client level to group codes that have the same contents or relate to one another. within a catalog types. They can describe. Selected sets from the catalog types Characteristic attribute and Usage decision also contain a valuation for each code. Codes that are copied into a selected set are known as set codes. and in quality notification. Selected sets can be used to combine codes from several code groups for processing that are allowed or useful for a particular application. a characteristic attribute. A code can be assigned to one or several selected sets. Code group Color Codes Black Green Blue Other colors Selected sets A selected set contains a combination of different codes at plant level. The code is distinctive in conjunction with the catalog and code group. Selected set Color of PE bags Codes Black Green Blue Valuation Accepted Accepted Accepted Page 7 of 70 . The Catalog for Usage decision for all inspection types will be maintained as below codification No. as additional information (Accepted or Rejected). a defect type.

Rejected Black – Rejected Sampling Procedure A Sampling Procedure defines the rules that specify how the system calculates the sample size and it contains information about the valuation of an inspection characteristic during result recording (Valuation mode). Page 8 of 70 . You can assign a sampling scheme to a sampling procedure. Quantitative / Qualitative Quantitative Master inspection characteristics Length Qualitative Color Values / Range Lower limit – 10 m2 Upper limit – 15 m2 Target value – 13 m2 Yellow .Other colors Rejected Master Inspection characteristics Master inspection characteristic describes what needs to be inspected. Quantitative Characteristic: The Master Inspection characteristic is treated as a quantitative characteristic which has a specific measurable value. master records for inspection characteristics would be created in the Quality Management (QM) system as a master data. We will maintain different Sampling procedures for different type of materials based on the Material and its Base unit of measure. with the valuation OK or not OK. A master inspection characteristic can be of quantitative characteristics or qualitative characteristics and it can be even a derived (calculated) characteristics.Accepted White – Accepted Green . In KIMMCO & ROCKWOOL the sample size for all the incoming materials will be fixed or based on the lot size. Qualitative Characteristic: The Master inspection characteristic is treated as qualitative having descriptive in Nature. Sampling Scheme The sampling scheme contains information for drawing samples based on the size of the inspection lot. To facilitate and standardize inspection planning. You can define tolerance limits and a target value for a quantitative characteristic. Inspection results are recorded as codes from inspection catalogs. It defines the inspection requirements for materials.

No. plant and vendor. in process inspection and recurring inspection etc. for example. You create inspection methods as master records and assign them to master inspection characteristics. In the inspection plan. SAP offers inspection plans for different uses. A long text field is available in the Inspection method. the system checks if the purchase Active orders. From number To number 01 00000001 49999999 Page 9 of 70 . which can be used for maintaining inspection manuals. operation: Characteristics Inspection plan will be created in following number ranges by automatically. The Q-info record would be created with a combination of material. Field Description 01 Release by Date until which the material for the plant can be ordered from the vendor 02 Release Quantity Is If this indicator is set. material to be inspected. or inspection plans. how the inspection is to take place. Z4 (Goods receipt) 5 Goods receipt Z3 (In process) 1 Production Z9(Recurring inspection) 9 Material check Z89 (Manual lot) 3 Universal Inspection plans will be created with following control key No. you define the sequence of inspection operations and the range of specifications available for inspecting inspection characteristics. The Q-Info record contains following information No. vendor release for procurement or a Vendor approval process. Inspection plans will be created for following usages Inspection type Usage Description Z1. characteristics to be inspected. Inspection plans help to describe how a quality inspection of one or several materials is to take place. and inspection specifications. for example. the sum of the material ordered from the vendor for this plant is greater than the released quantity 03 Status profile Status profile is maintained for Vendor approval process Inspection Plan Inspection planning functions to define inspection criteria.Inspection Methods Describes the procedure for inspecting a characteristic. Quality Info Records (Optional) The Q-Info records would be maintained if the material requires Quality assurance agreement. goods receipt inspection. Usage Description 01 QM01 Insp. You can assign several inspection methods to a master inspection characteristic.

Creating & Changing Master data Page 10 of 70 . Approaches to Covering Functional Deficits Documentation of any work-around or assumptions that have been made when outlining functional deficits.        List of Master Inspection characteristics Where used list of Master Inspection characteristics Where used list of Sampling procedures List of Inspection methods Where used list Inspection methods Missing Inspection plans List of Quality info records 13. as well as estimating the need for ABAP (or similar) resources.9. identify any gaps. Reporting Requirements Document the various reports that you would require.  Not applicable 10. Integration considerations Specify what integration you need with other modules / sub modules  Not applicable 12.  Not applicable 11. This section is important when assessing risk. Description of Functional Deficits Where appropriate. Authorization Requirements Document the level of authorizations that you need for each process in the system   Quality head – Creating & Changing Master data Quality Supervisor .

       Code groups and selected set – Manual creation Master inspection characteristics – Manual creation Inspection methods – Manual creation Sampling procedures – Manual creation Quality info records – Manual creation Inspection plans for raw materials – Manual creation Inspection plans for finished goods – LSMW Page 11 of 70 . what data is to be converted manually/automatically and at what point in time. Quality control chemist – Display Master data 14. This is critical information that is used later. Where the information is to come from. File Conversion / Interface Considerations Document file conversion / interface requirements.

until the material is approved by the quality department. it should relate purely to the business rules. This typically does not include any SAP specific terms. General Explanations (For Masters and Enterprise structure include Naming Convention) Describe the business process in detail. the received goods will be accepted or rejected Once the received goods are accepted by the Quality personnel the goods will be available for Production For some raw materials samples will be sent to the external laboratories for inspection It may take 25 . the system should not accept the material to be issued to the production 3.30 days for the samples to get inspected Even before the results arrive from the external laboratory. warehouse person takes the materials into Quality inspection stock and inform the Quality personnel The Quality person will draw a sample After the sample is drawn it will be inspected based on the specifications defined Based on the results of the inspection. the raw material will be used for production After the results from the external laboratory are arrived. the results will be recorded In case of any rejections. Facing materials and Packaging materials are analyzed based on the specifications defined Purchase department will procure the materials from the vendor Once the materials are received from the Vendor. the quality department will inform the purchase department about the defects The problem is analyzed and further action will be taken by the purchase department When the material is received from the Vendor. the payment to the vendor should be blocked 2. Describe the naming and numbering convention in case of masters and enterprise structure   Inspection of raw materials should be triggered automatically Unless the quality inspection is completed.2. Requirements/Expectations A brief / bulleted list of requirements and expectations               All the incoming Raw materials. Explanations of Functions and Events Page 12 of 70 . Inspection in Procurement 1.

Process Diagrams Provide all related process maps or diagrams Page 13 of 70 .Explain what events and processes trigger this process   When Raw materials. Inspections will be carried out Unless the inspection results are recorded and decision is made by the quality head. Facing materials and Packaging materials are received from a Vendor.  Not Applicable 5. the materials will not be used for production 4. Organizational Considerations Address any issues agreed in the workshop concerning the SAP organizational structure and this process.

from where the goods cannot be issued to production After completing the inspections. from where the goods can be issued to the production Page 14 of 70 .Create Purchase order Goods receipt against Purchase order Inspection Lot creation Result Recording Rejected Usage Decision Accepted Blocked Stock Unrestricted Stock Defect Recording Can be issued to Production Create Quality Notification 6. results will be recorded and Usage decision will be made as Accepted or Rejected Once the inspection lot is accepted. the goods will be posted to Unrestricted stock. they will be posted to the quality stock.       Inspections are identified by the purchase order number or batch number in the current system Now the inspections will be identified by the Inspection lot number in SAP There are three major types of stocks in SAP like Unrestricted. Changes to Existing Organization processes Change management issues as appropriate. Quality and Blocked stock When the goods are received from the vendor.

as soon as GR is made for the material. the inspection lot number will be written on the facing material 7. an inspection lot must be created in the system..e. Description of Improvements Describe improvements which will result from implementation of the SAP System. the inspection lot would be either accepted or rejected. This acceptance or rejection is termed as USAGE DECISION. Whenever materials are received from procurement process (external source).   In case the inspection lot is rejected. Based on the quality scores. This is a special kind of stock – i. All the quality activities are carried out for the inspection lot generated. the goods will be posted to Blocked stock In Rockwool India ltd. vendor evaluation will be done Analytical reports can be generated which can be used by personnel from all user groups to aid them in their daily activities 8. The incoming material immediately moves into the QUALITY INSPECTION STOCK. the stock will be posted to unrestricted stock Quality scores will be provided to the inspection lot. Be sure to include any impact on business drivers. processing the quality inspections are on the basis of inspection lot. If you want to inspect a specific quantity of a material. now in SAP. and complete the inspection with a usage decision. Describe how this process will be addressed in the product. The Quality Inspector would inspect the material based on the specifications of inspection lot. when the facing materials are received from the Vendor. Only if the material is accepted in the Usage Decision. Once an inspection lot has been created. record the results of the characteristics of the inspection lot and based on the valuation of the recorded characteristics (parameters). the supplier number is written on the material in the current system For traceability purpose. Solution in SAP. using inspection lot we can inspect the goods. If the materials were to be rejected the same would be posted to blocked stock from where the Page 15 of 70 . the material will directly posted to Quality stock from where we cannot issue the material to production Once the Usage decision is made for the inspection lot. In the Quality Management component.      Once the material is received from the Vendor. the stock would be posted from Inspection stock to Un restricted stock from which the material could be freely issued. record the inspection results. this is a restricted stock where material cannot be issued for any purpose. an inspection lot is generated automatically.

Purchase department will procure the materials from the vendor using purchase order.material would be sent back to the vendor or as the decision would be taken. Vendor will supply the material against the purchase order. 01 02 03 04 05 06 Field Plant Inspection lot Material System status Inspection start date Inspection end date 07 08 09 10 11 Inspection type Vendor Inspection Plan Inspection lot quantity Sample size Description Plant of the inspection lot Inspection lot number for material Material code and description Inspection lot status Date when the material received in warehouse Inspection start date + average inspection duration in material master Goods Receipt Insp. warehouse person takes the materials into Quality inspection stock and system generates inspection lot number automatically. The following material types are procured No. 01 02 03 Material type ZROH ZPAC ZFAC Description Raw Materials Packaging Materials Facing Material Once the material is received. 01 Inspection lot origin 01 Description From Number To Number Goods Receipt 010000000000 019999999999 Inspection lot contains following information No. against Purchase Order From which vendor material is received From which plan the inspection lot is created Quantity received in warehouse It is determined from sampling procedure maintained in quality plan Inspection Lot creation  Inspection lot is created automatically (Quality Management)  Pending inspection lots will be displayed in a report  Stock will automatically posted to Quality stock  Inspection instructions and Sample drawing instructions can be printed Page 16 of 70 . The following inspection lot number ranges are used in QM in Procurement process No.

with three deviations Accept.  If the inspection lot is rejected(R-Rejected) then the stock will be posted to blocked stock  Quality scores will be provided to the inspection lot based on the Usage decision code Code A A1 A2 A3 A4 R R1  Short text Accept Accept.Result recording       Samples are inspected in quality control laboratory as per the specifications defined in the task list (Inspection plan) Test results are entered in the result recording transaction Valuation of the results (Accepted / Rejected) is done If the inspection results are Rejected. with two deviations Accept. samples will be sent to the external laboratory for inspections  For the Master inspection characteristics which are inspected outside. in the control indicators Long term inspection will be activated Page 17 of 70 . with four deviations Rejected Scrap Valuation code Accepted Accepted Accepted Accepted Accepted Rejected Rejected Quality score 100 90 70 50 40 01 01 These quality scores will be used in Vendor evaluation Long term inspection  For some raw material. then the defects will be recorded and a Quality notification will be created with notification type ZV (Complaints against Vendor) Close the results entered The inspection lot status will change from REL (Released) to INSP (Inspected) Usage decision  Usage decision transaction is executed for selected inspection lot in work list  Verifies the results of inspection lot entered by QC analyst  Depending upon the results the usage decision code is entered  If the inspection lot is accepted (A-Accepted) then the stock will be posted to unrestricted stock. with one deviation Accept.

At the time of result recording, the results for long term characteristics will not be
entered and Usage decision will be made (Accepted)

Usage Decision will be made and the goods can be used for production

Once the results are received from the external laboratory, the results of those
characteristics will be entered in the system

In a long-term inspection:

There can already be a usage decision for the inspected material during the long-term
inspection

You can still record inspection results for long-term characteristics, once you have made
the usage decision

The system sets a separate status in the inspection lot to identify the long-term
inspection and it provides special work lists for this purpose

Invoice Blocking:


In the Material master QM view, QM procurement key will be activated and Control key
– 0007 will be assigned.
The payment of the invoice is blocked with blocking reason I (I = Inspection), if you
want to prevent automatic payment of the invoice from a QM standpoint.
When the invoice is created, the system determines whether an inspection lot exists and
if necessary, sets blocking reason I. This occurs in the following instances:
There is still no usage decision for the inspection lot
The inspection lot is rejected

The automatic payment program checks whether the blocking reason I still exists

Invoice verification takes place with reference to the goods receipt.
If there are several partial deliveries for an order item, the system checks for each GR
item whether blocking reason I exists. This means that automatic payment of the invoice
is only prevented for partial deliveries that do not fulfill requirements.

The system does not automatically remove blocking reason I, if an acceptance decision
is made for the inspection lot concerned. You must remove blocking reason I at invoice
verification or invoice release.

9. Description of Functional Deficits
Where appropriate, identify any gaps. This section is important when assessing risk, as well as
estimating the need for ABAP (or similar) resources.

Page 18 of 70

Not applicable

10. Approaches to Covering Functional Deficits
Documentation of any work-around or assumptions that have been made when outlining
functional deficits.

Not applicable

11. Integration considerations
Specify what integration you need with other modules / sub modules

Integrated with Materials management, as the inspection lot is generated after the
goods are received against a purchase order

12. Reporting Requirements
Document the various reports that you would require.


List of pending Inspection lots (Standard)
Results display (Standard)
Display of Results for each inspection lot in a single screen (Development)

13. Authorization Requirements
Document the level of authorizations that you need for each process in the system


Quality head – Creating & Changing Inspection lot, Result recording, Usage decision
and Stock posting
Quality Supervisor - Creating & Changing Inspection lot, Result recording, Usage
decision and Stock posting
Quality control chemist – Display Inspection lot and Result recording

14. File Conversion / Interface Considerations
Document file conversion / interface requirements. Where the information is to come from,
what data is to be converted manually/automatically and at what point in time. This is critical
information that is used later.

Not applicable
Page 19 of 70

3. Inprocess Inspection
1. Requirements/Expectations
A brief / bulleted list of requirements and expectations



During the production of semi finished and finished products, in process inspections are
carried out by quality department
Quality inspections will be carried out at regular intervals of time (For example - Once
in every 15 mins)
Quality person will inspect the sample according to the specifications defined and
record the results
In case of any deviations the quality department will inform the Production department

Page 20 of 70

Describe the naming and numbering convention in case of masters and enterprise structure  The inspection lot should be created automatically 3. Process Diagrams Provide all related process maps or diagrams Page 21 of 70 . it should relate purely to the business rules.  Not Applicable 5.    about the deviations The production department will make necessary changes and start producing the finished goods The defects will be analyzed and further action will be taken In case the results are within the specified range the production process will be continued further Certificate of Analysis is created. printed and it will be sent to the customer along with the finished goods 2. General Explanations (For Masters and Enterprise structure include Naming Convention) Describe the business process in detail. This typically does not include any SAP specific terms. Explanations of Functions and Events Explain what events and processes trigger this process  After the process order is created and released. Organizational Considerations Address any issues agreed in the workshop concerning the SAP organizational structure and this process. the inspection lot is generated automatically 4.

Create Process order Release Process order Inspection Lot creation Result Recording / Valuation (Inspection points) Rejected Usage Decision Defect Recording Accepted Confirm Process order Create Quality Notification 6.  Not Applicable 7. Description of Improvements Page 22 of 70 . Changes to Existing Organization processes Change management issues as appropriate.

The following inspection lot number ranges are used in QM in Production process No.  Immediately after releasing the Process order.Describe improvements which will result from implementation of the SAP System. Quality Inspection would be carried out and the results observed during inspection will be recorded against each operation in the inspection lot. 01 02 03 04 05 06 07 08 09 10 11 Field Plant Inspection lot Material System status Inspection start date Inspection end date Description Plant of the inspection lot Inspection lot number for material and batch Material code and description Inspection lot status Date when the process order is released Inspection start date + average inspection duration in material master Inspection type In process Inspection Order Process Order number Inspection Plan From which plan the inspection lot is created Inspection lot quantity Quantity of process order Sample size It is determined from sampling procedure Page 23 of 70 . for process order From Number To Number 030000000000 039999999999 Inspection lot contains following information No. Inspection points will be defined based on time (to enter results at regular intervals). in-process inspections can be carried out. Describe how this process will be addressed in the product. as many as the inspections carried out (Inspection Points). the inspection lot will get generated  Inspection point identification will be the date and time  Analytical reports can be generated which can be used by personnel from all user groups to aid them in their daily activities 8. Be sure to include any impact on business drivers. inspection lot would automatically be created for the in-process inspection. During production activities against the process order. Once the Process order is released by the production person. inspection characteristics would be maintained in the ‘Master Recipe’. For the inspection relevant operations / phases during production. Solution in SAP. Many Inspection results can be recorded for the same inspection lot of the process order. 01 Inspection lot Description origin 03 In-process insp.

maintained in inspection plan Inspection Lot creation  Inspection lot is created automatically after releasing the process order by the production person  Inspection instructions and Sample drawing instructions can be printed  Process order number is displayed in the Inspection lot number Result recording       Samples are inspected based on the specifications defined in the Master Recipe Test results are entered in the result recording transaction Result recording will be done at different inspection points Valuate the results (Accepted / Rejected) for each inspection point If the results are rejected. This section is important when assessing risk. then the defects will be recorded and a quality notification will be created with notification type ZM (Internal problem notification) Close the results entered Usage decision  Usage decision transaction is executed for selected inspection lot in work list  Verifies the results of inspection lot entered by QC analyst  Based on the results the usage decision code will be entered  If the Inspection lot is accepted. Approaches to Covering Functional Deficits Documentation of any work-around or assumptions that have been made when outlining Page 24 of 70 . as well as estimating the need for ABAP (or similar) resources. identify any gaps. then the process order operation will be confirmed 9. Description of Functional Deficits Where appropriate.  Not applicable 10.

Authorization Requirements Document the level of authorizations that you need for each process in the system    Quality head – Creating & Changing Inspection lot. File Conversion / Interface Considerations Document file conversion / interface requirements.Creating & Changing Inspection lot.  Not applicable 11. Where the information is to come from.    List of pending Inspection lots (Standard) Results display (Standard) Display of Results of all the inspection points and all the characteristics in one screen (Development) 13. This is critical information that is used later. as the inspection lot is generated after releasing the process order 12. what data is to be converted manually/automatically and at what point in time. Integration considerations Specify what integration you need with other modules / sub modules  Integrated with Production planning. Reporting Requirements Document the various reports that you would require. Result recording and Usage decision Quality Supervisor .  Not applicable Page 25 of 70 . Result recording and Usage decision Quality control chemist – Display Inspection lot and Result recording 14.functional deficits.

4. Requirements/Expectations A brief / bulleted list of requirements and expectations   In Rockwool. Inspection after Production 1. there are some inspections which are carried out after completion of production Inspection for specifications like Sulphur content. Moisture absorption etc are carried out once in four days Page 26 of 70 . Chloride content.

then the finished goods will be ready for dispatch In case the material is rejected. Process Diagrams Provide all related process maps or diagrams Page 27 of 70 . Explanations of Functions and Events Explain what events and processes trigger this process   When finished goods are received from the production. it should relate purely to the business rules. Certificate of Analysis will be printed and sent along with the goods The results of the above specifications are printed in the certificate Once the results are accepted. Organizational Considerations Address any issues agreed in the workshop concerning the SAP organizational structure and this process. the system should not accept the material to be delivered to the customer 3. Inspections will be carried out Unless the inspection results are recorded and decision is made by the quality head. This typically does not include any SAP specific terms. the material will be posted to blocked stock The quality department will inform the production department and further action will be taken 2.      These results will be valid for four days For all the dispatches.  Not Applicable 5. General Explanations (For Masters and Enterprise structure include Naming Convention) Describe the business process in detail. Describe the naming and numbering convention in case of masters and enterprise structure   Inspection of finished goods should be triggered automatically Unless the quality inspection is completed. the materials will not be dispatched to the customer 4.

Changes to Existing Organization processes Change management issues as appropriate. an inspection lot will be generated and stock will be posted to quality stock From Quality stock the goods cannot be delivered to the customer After completing the inspections.Create Process order Goods receipt from Process order Inspection Lot creation Result Recording Rejected Usage Decision Accepted Blocked Stock Unrestricted Stock Defect Recording Can be delivered to the customer Create Quality Notification 6.     All the inspections will be identified by the Inspection lot number in SAP When the produced goods are received from production. results will be recorded and Usage decision will be Page 28 of 70 .

the stock would be posted from Inspection stock to Un restricted stock from which the material could be freely issued. 01 Inspection lot origin 04 Description From Number To Number Goods Receipt 040000000000 049999999999 Inspection lot contains following information No.  Analytical reports can be generated which can be used by personnel from all user groups to aid them in their daily activities 8. an inspection lot is generated automatically. the inspection lot would be either accepted or rejected. Only if the material is accepted in the Usage Decision. Describe how this process will be addressed in the product. this is a restricted stock where material cannot be issued for any purpose. All the quality activities are carried out for the inspection lot generated. Be sure to include any impact on business drivers. the stock will be posted to unrestricted stock from where the goods can be delivered to the customer In case the inspection lot is rejected. The Quality Inspector would inspect the material based on the specifications of inspection lot. as soon as GR is made for the material.e.. the stock will be posted to Blocked stock The characteristics will be inspected once in four days But the results of the characteristics will be recorded in all the inspection lots which are generated within that four days 7. Once the material is received. This is a special kind of stock – i. This acceptance or rejection is termed as USAGE DECISION. The material immediately moves into the QUALITY INSPECTION STOCK. Solution in SAP. Field Description Page 29 of 70 . Whenever materials are received from production process.    made for the inspection lot Once the inspection lot is accepted. warehouse person takes the materials into Quality inspection stock and system generates inspection lot number automatically. Description of Improvements Describe improvements which will result from implementation of the SAP System. If the materials were to be rejected the same would be posted to blocked stock from where the material would be reworked or scraped or as the decision would be taken. record the results of the characteristics of the inspection lot and based on the valuation of the recorded characteristics (parameters). The following inspection lot number ranges are used in Inspection after Production process No.

then the defects will be recorded and a Quality notification will be created with notification type ZM(Internal problem notification) Close the results entered The inspection lot status will change from REL (Released) to INSP (Inspected) Usage decision  Usage decision transaction is executed for selected inspection lot in work list  Verifies the results of inspection lot entered by QC analyst  Depending upon the results the usage decision code is entered  If the inspection lot is accepted (A-Accepted) then the stock will be posted to unrestricted stock  If the inspection lot is rejected(R-Rejected) then the stock will be posted to blocked Page 30 of 70 .01 02 03 04 05 06 Plant Inspection lot Material System status Inspection start date Inspection end date 07 08 09 10 Inspection type Inspection Plan Inspection lot quantity Sample size Plant of the inspection lot Inspection lot number for material Material code and description Inspection lot status Date when the material received in warehouse Inspection start date + average inspection duration in material master Goods Receipt Inspection from production From which plan the inspection lot is created Quantity received in warehouse It is determined from sampling procedure maintained in quality plan Inspection Lot creation  Inspection lot is created automatically (Quality Management)  Stock will automatically posted to Quality stock  Inspection instructions and Sample drawing instructions can be printed Result recording       Samples are inspected in quality control laboratory as per the specifications define in the task list Test results are entered in the result recording transaction Valuation of the results (Accepted / Rejected) is done If the inspection results are Rejected.

 Not applicable 10. as the inspection lot is generated after the produced goods are received from production 12. Authorization Requirements Document the level of authorizations that you need for each process in the system Page 31 of 70 . other material Rejected Scrap Valuation code Accepted Accepted Accepted Rejected Rejected 9. identify any gaps.  Not applicable 11. Reporting Requirements Document the various reports that you would require. Description of Functional Deficits Where appropriate.    List of pending Inspection lots (Standard) Results display (Standard) Display of Results for each inspection lot in a single screen (Development) 13.stock  The UD codes will be as follows Code A A1 AX R R1 Short text Accept Accept with one deviation Accept. Integration considerations Specify what integration you need with other modules / sub modules  Integrated with Production planning. as well as estimating the need for ABAP (or similar) resources. This section is important when assessing risk. Approaches to Covering Functional Deficits Documentation of any work-around or assumptions that have been made when outlining functional deficits.

Retesting of Finished goods 1. what data is to be converted manually/automatically and at what point in time.  Not applicable 5. Result recording. File Conversion / Interface Considerations Document file conversion / interface requirements. This is critical information that is used later. Result recording. Requirements/Expectations A brief / bulleted list of requirements and expectations Page 32 of 70 .   Quality head – Creating & Changing Inspection lot.Creating & Changing Inspection lot. Usage decision and Stock posting Quality control chemist – Display Inspection lot and Result recording 14. Where the information is to come from. Usage decision and Stock posting Quality Supervisor .

Explanations of Functions and Events Explain what events and processes trigger this process   In KIMMCO. before delivering the material to that sales order. where the finished goods are not produced for any particular sales order.       In KIMMCO. it should relate purely to the business rules. the deviations will be recorded and material will be blocked Further action will be taken based on the problem analysis These inspections are not related to any sales order or production order 2. Describe the naming and numbering convention in case of masters and enterprise structure  Not Applicable 3. inspection are carried out 4. the goods will be dispatched to the customer In case of any defects. there are some cases. Process Diagrams Provide all related process maps or diagrams Page 33 of 70 . Organizational Considerations Address any issues agreed in the workshop concerning the SAP organizational structure and this process. finished goods stocks are available in the storage location. before delivering the finished goods to the customer. This typically does not include any SAP specific terms.  Not Applicable 5. General Explanations (For Masters and Enterprise structure include Naming Convention) Describe the business process in detail. the material will be inspected Then inspections will be carried out based on the specifications defined If the results complies with the specifications. which are not reserved to any sales order After the receipt of a sales order for that material. These materials are produced and kept in stock After a sales order for this material is received.

Page 34 of 70 .  Not Applicable 7. Be sure to include any impact on business drivers. Changes to Existing Organization processes Change management issues as appropriate.Initiate Inspection of Finished goods Create Inspection lot Manually Result Recording Usage Decision Rejected Defects Recording Accepted Deliver Finished Goods Create Quality Notification 6. Description of Improvements Describe improvements which will result from implementation of the SAP System.

Whenever the materials which are in stocks require inspection before delivery. the material can be delivered. record the results of the characteristics of the inspection lot and based on the valuation of the recorded characteristics (parameters). Then the quality person will create an inspection lot manually. Once the quality person record the results and make a Usage decision as ACCEPTED. The Quality Inspector would inspect the material based on the specifications of inspection lot. the stores person will inform the quality control department to inspect the materials. This acceptance or rejection is termed as USAGE DECISION. All the quality activities are carried out for the inspection lot generated. Inspection Lot creation  Inspection lot is created manually for the stock quantity  Inspection instructions and Sample drawing instructions can be printed Result recording       Samples are inspected in quality control laboratory based on the specifications defined in the task list Test results are entered in the result recording transaction Valuate the results (Accepted / Rejected) If the inspection results are rejected. Not applicable 8. then the defects will be recorded and a Quality notification will be created with notification type ZM (Internal problem notification) Close the results entered The inspection lot status will change from REL (Released) to INSP (Inspected) Usage decision  Usage decision transaction is executed for selected inspection lot in work list  Verifies the results of inspection lot entered by QC analyst  Depend upon the results the usage decision code is entered  If the Inspection lot is Accepted. the inspection lot would be either accepted or rejected. Describe how this process will be addressed in the product. Solution in SAP. then the goods can be delivered to the Sales order Page 35 of 70 . While creating the inspection lot the quantity of the material which has to be inspected will be entered.

then the goods will be blocked and further action will be taken While creating the inspection lot manually.  Not applicable 11. This section is important when assessing risk. If the Inspection lot is Rejected. identify any gaps. Authorization Requirements Document the level of authorizations that you need for each process in the system  Quality head – Creating & Changing Inspection lot. Result recording and Usage Page 36 of 70 . the person who is creating the inspection lot has to select the inspection plan from the list.   List of pending Inspection lots Results display 13.  Not applicable 10. Integration considerations Specify what integration you need with other modules / sub modules  Not applicable 12. 9. as well as estimating the need for ABAP (or similar) resources. Approaches to Covering Functional Deficits Documentation of any work-around or assumptions that have been made when outlining functional deficits. Reporting Requirements Document the various reports that you would require. Description of Functional Deficits Where appropriate.

Where the information is to come from. File Conversion / Interface Considerations Document file conversion / interface requirements.  Not applicable 6. Vendor approval process 1. Requirements/Expectations A brief / bulleted list of requirements and expectations Page 37 of 70 . This is critical information that is used later. Result recording and Usage decision Quality control chemist – Display Inspection lot and Result recording 14.  decision Quality Supervisor . what data is to be converted manually/automatically and at what point in time.Creating & Changing Inspection lot.

quality department will inform the purchase department The purchase department will block the goods and further action will be taken 2. Organizational Considerations Address any issues agreed in the workshop concerning the SAP organizational structure and this process. then the purchase department will send a Trial order to the Vendor for a smaller quantity Once the goods are received from the vendor against that purchase order. then they will approve the Vendor on quality aspects In case of any defects in the material.  Not Applicable 5. This sample will be inspected based on the specifications defined If the results are meeting the requirements. inspection are carried out If the results are meeting the specific requirements. General Explanations (For Masters and Enterprise structure include Naming Convention) Describe the business process in detail.       In KIMMCO. it should relate purely to the business rules. Explanations of Functions and Events Explain what events and processes trigger this process  This process should trigger only for a new Vendor. Describe the naming and numbering convention in case of masters and enterprise structure  Not Applicable 3. when the Raw materials are procured from a new Vendor. approval process will be carried out Initially samples of the Raw material will be taken from the vendor. This typically does not include any SAP specific terms. Process Diagrams Provide all related process maps or diagrams Page 38 of 70 . 4.

Receive Sample from New Vendor Create Inspection lot Manually Result Recording Accepted Usage Decision Create quality info record & Initiate Vendor approval process Rejected Request for another sample Create Purchase order & Assign Status profile Goods receipt against Purchase order Inspection Lot creation Result Recording Rejected Usage Decision Blocked Stock Create Quality Notification Accepted Unrestricted Stock Vendor Approved 6. Changes to Existing Organization processes Page 39 of 70 .

the inspection lot would be either accepted or rejected. Then the quality person will create an inspection lot manually. Be sure to include any impact on business drivers. Once the quality person record the results and make a Usage decision as ACCEPTED. Describe how this process will be addressed in the product. Defects and Notifications can be generated 8. Inspection Lot creation  Inspection lot is created manually for the sample received from the Vendor  Inspection instructions and Sample drawing instructions can be printed Result recording      Samples are inspected in quality control laboratory based on the specifications defined in the task list Test results are entered in the result recording transaction Valuate the results (Accepted / Rejected) Close the results entered The inspection lot status will change from REL (Released) to INSP (Inspected) Page 40 of 70 . the material can be procured from the new Vendor. Solution in SAP. Quantities. Quality scores. The Quality Inspector would inspect the material based on the specifications of inspection lot. All the quality activities are carried out for the inspection lot generated. record the results of the characteristics of the inspection lot and based on the valuation of the recorded characteristics (parameters). the Purchasing department person will inform the quality control department to inspect the sample.  Not Applicable 7.Change management issues as appropriate.   Analytical reports can be generated which can be used by personnel from all user groups to aid them in their daily activities Reports on Overview of Inspection lots. Description of Improvements Describe improvements which will result from implementation of the SAP System. This acceptance or rejection is termed as USAGE DECISION. Whenever the Samples are taken from a new Vendor.

vendor and plant. Inspection Lot creation  Inspection lot is created automatically (Quality Management). In material master QM view.  Stock will automatically posted to Quality stock  Inspection instructions and Sample drawing instructions can be printed  Status in the quality info record will be – Vendor approval process initiated Result recording       Samples are inspected in quality control laboratory based on the specifications define in the task list Test results are entered in the result recording transaction Valuate the results (Accepted / Rejected) If the inspection results are rejected. Result recording will be done. an inspection lot will be generated automatically. When the purchase order is created for the material to that new vendor. the status in the quality info record will be changed to – Vendor approved. usage decision code will be entered by the quality manager. then the defects will be recorded and a Quality notification will be created with notification type ZV (Complaints against a Vendor) Close the results entered The inspection lot status will change from REL (Released) to INSP (Inspected) Page 41 of 70 . then the materials can be procured from the Vendor Vendor approval process Vendor approval process in carried out in QM based on the results of the inspection lot. Quality info record will be created in the system with the combination of material. Status profile will be created and assigned to the quality info record. Immediately after entering the Usage decision code as accepted. Based on the results. When the material is procured from the vendor. the status in the quality info record will be – Vendor approval process initiated. QM procurement key will be activated.Usage decision  Usage decision transaction is executed for selected inspection lot in work list  Verifies the results of inspection lot entered by QC analyst  Based on the results the usage decision code is entered  If the Inspection lot is Accepted.

 If the inspection lot is rejected(R-Rejected) then the stock will be posted to blocked stock (QC Manager). identify any gaps. Integration considerations Specify what integration you need with other modules / sub modules  Integrated with Materials management.  Not applicable 10.Usage decision  Usage decision transaction is executed for selected inspection lot in work list  Verifies the results of inspection lot entered by QC analyst  Depend upon the results the usage decision code is entered  If the inspection lot is accepted (A-Accepted) then the stock will be posted to unrestricted stock. as well as estimating the need for ABAP (or similar) resources.  If the inspection lot is Accepted then the status in the quality info record will changed to – Vendor is approved 9. as the quality info record can be created only if a Vendor master is created for the new Vendor 12.  Not applicable 11. Approaches to Covering Functional Deficits Documentation of any work-around or assumptions that have been made when outlining functional deficits. Reporting Requirements Document the various reports that you would require. Page 42 of 70 . Description of Functional Deficits Where appropriate. This section is important when assessing risk.

Usage decision and Stock posting Quality control chemist – Display Inspection lot and Result recording 14. Authorization Requirements Document the level of authorizations that you need for each process in the system    Quality head – Creating & Changing Inspection lot.Creating & Changing Inspection lot. Result recording.  List of pending Inspection lots Results display 13. File Conversion / Interface Considerations Document file conversion / interface requirements. Result recording.  Not applicable 7. what data is to be converted manually/automatically and at what point in time. Where the information is to come from. Requirements/Expectations A brief / bulleted list of requirements and expectations Page 43 of 70 . Recurring Inspection 1. Usage decision and Stock posting Quality Supervisor . This is critical information that is used later.

the system should not accept the material to be issued to the production 3. General Explanations (For Masters and Enterprise structure include Naming Convention) Describe the business process in detail. This typically does not include any SAP specific terms. it should relate purely to the business rules.  Not Applicable 5.       Some raw materials like Adhesives and Binder raw materials are batch managed These batches will have shelf life and expiry dates The quality parameters of these batches will be monitored at regular intervals After every 90 days. Process Diagrams Provide all related process maps or diagrams Page 44 of 70 . Organizational Considerations Address any issues agreed in the workshop concerning the SAP organizational structure and this process. Explanations of Functions and Events Explain what events and processes trigger this process  Not Applicable 4. the material will be placed in quality stock Once the inspection specifications are accepted. Describe the naming and numbering convention in case of masters and enterprise structure   Inspection lot should be triggered automatically when the next inspection interval arrives Unless the quality inspection is completed. then the material can be issued for production If the inspection specifications are rejected. the batches which are available in storage location will be inspected At the time of inspection. then the material will be blocked and further action will be taken 2.

Batch (Next inspection interval) Deadline Monitoring of Batches Batch posted to Quality stock Inspection Lot Created automatically Result Recording Rejected Usage Decision Accepted Blocked Stock Unrestricted Stock Defect Recording Can be issued to Production Create Notification 6. Page 45 of 70 . Changes to Existing Organization processes Change management issues as appropriate.

Solution in SAP. the inspection lot gets generated automatically The batch will be automatically posted to quality stock 8. the batch will be automatically posted to quality stock and system creates an inspection lot automatically 7. based on the next inspection date of batches. the inspection are carried out manually Now in SAP.  In the present system.    Deadline monitoring will be scheduled in background The batches for which the next inspection interval is arrived. Describe how this process will be addressed in the product. You can plan such inspections by having the system monitor the date for a recurring inspection. Description of Improvements Describe improvements which will result from implementation of the SAP System. The system can automatically create inspection lots at predefined intervals for selected batch materials. The system creates inspection lots automatically for recurring inspections if the following conditions have been met:  Each material to be inspected is defined as a batch material in the material master record  An inspection interval is specified in the Quality Management view of the material master record  An inspection type is active for inspection lot origin 09 in the inspection settings of the material master record  The inspection settings in the material master record specify an inspection using a task list or material specification (if you want to record results for inspection characteristics)  A Next inspection date is specified for the batch in the batch master Recurring inspections are triggered by a report that we can execute manually  The system can automatically create inspection lots Based on the “Next Inspection Date” field in the Batch master (which is initially set during the original inspection). Be sure to include any impact on business drivers. when the next inspection date is arrived.  Inspection lot will be automatically created when the next inspection date is reached Page 46 of 70 .

Integration considerations Specify what integration you need with other modules / sub modules  Not applicable Page 47 of 70 . Approaches to Covering Functional Deficits Documentation of any work-around or assumptions that have been made when outlining functional deficits. No. as well as estimating the need for ABAP (or similar) resources. 01 The following inspection lot number ranges are used in Recurring Inspection process Inspection lot origin 09 Description From Number To Number Recurring Inspection 090000000000 099999999999  The stock of that particular batch will be automatically posted to quality stock  The quality person draws the sample  The samples are tested in the quality control laboratory according to the specifications defined in the Inspection plan  Test results are entered in the results recording transaction of inspection lot  Depending upon the results the usage decision code will be entered   If the inspection lot is accepted(A-Accepted) then the stock will be posted to unrestricted stock If the inspection lot is rejected(R-Rejected) then the stock will be posted to blocked stock 9. Description of Functional Deficits Where appropriate.  Not applicable 10. This section is important when assessing risk. identify any gaps.  Not applicable 11.

  List of pending Inspection lots (Standard) Results display (Standard) 13. Result recording. Reporting Requirements Document the various reports that you would require. what data is to be converted manually/automatically and at what point in time. File Conversion / Interface Considerations Document file conversion / interface requirements.  Not applicable Page 48 of 70 .12. Where the information is to come from. Usage decision and Stock posting Quality Supervisor . This is critical information that is used later. Authorization Requirements Document the level of authorizations that you need for each process in the system    Quality head – Creating & Changing Inspection lot.Creating & Changing Inspection lot. Usage decision and Stock posting Quality control chemist – Display Inspection lot and Result recording 14. Result recording.

Process Diagrams Provide all related process maps or diagrams Page 49 of 70 . it should relate purely to the business rules. then the water will be discarded and fresh water will be taken 2. Organizational Considerations Address any issues agreed in the workshop concerning the SAP organizational structure and this process.8. when the solid content is out of specification. Requirements/Expectations A brief / bulleted list of requirements and expectations      While producing binder material. This typically does not include any SAP specific terms. Describe the naming and numbering convention in case of masters and enterprise structure  Not Applicable 3.  Not Applicable 5. General Explanations (For Masters and Enterprise structure include Naming Convention) Describe the business process in detail. Explanations of Functions and Events Explain what events and processes trigger this process  Not Applicable 4. wash water is used in the production This wash water will be recycled The solid content of the wash water is inspected in each shift This inspection is carried out once in a shift After 7 or 8 days. Washwater testing 1.

Description of Improvements Describe improvements which will result from implementation of the SAP System.   Inspection results will be recorded in each shift based on the inspection points The identification of the inspection points will be the date and time Page 50 of 70 . Be sure to include any impact on business drivers. Changes to Existing Organization processes Change management issues as appropriate.Initiate Inspection of Wash water Create Inspection lot Manually Result Recording in each shift Usage Decision Rejected Discard the wash water Accepted Use the Water further 6.  Not Applicable 7.

Solution in SAP. The identification of the inspection point would be date and time. the water can be used in the production activity. Inspection Lot creation  Inspection lot is created manually for the wash water  Inspection instructions and Sample drawing instructions can be printed Result recording       Samples are inspected in quality control laboratory based on the specifications define in the task list Test results are entered in the result recording transaction for each inspection point (Once in a shift) Valuate the results (Accepted / Rejected) If the inspection results are rejected. the inspection lot would be either accepted or rejected. The result recording will be done in each shift as an inspection point. record the results of the characteristics of the inspection lot and based on the valuation of the recorded characteristics (parameters). then defects will be recorded and will be informed to concerned person to change the water Close the results entered The inspection lot status will change from REL (Released) to INSP (Inspected) Usage decision  Usage decision transaction is executed for selected inspection lot in work list  Verifies the results of inspection lot entered by QC analyst  Depend upon the results the usage decision code is entered Page 51 of 70 . All the quality activities are carried out for the inspection lot generated. Describe how this process will be addressed in the product. While creating the inspection lot the quantity of the material which has to be inspected will be entered. Once the quality person record the results and make a Usage decision as ACCEPTED. This acceptance or rejection is termed as USAGE DECISION. The quality person will create an inspection lot manually for wash water testing. The Quality Inspector would inspect the wash water based on the specifications of inspection lot.8.

This is critical information that is used later. Page 52 of 70 . Where the information is to come from. This section is important when assessing risk. identify any gaps. File Conversion / Interface Considerations Document file conversion / interface requirements.  Not applicable 10. Approaches to Covering Functional Deficits Documentation of any work-around or assumptions that have been made when outlining functional deficits. Authorization Requirements Document the level of authorizations that you need for each process in the system    Quality head – Creating & Changing Inspection lot. what data is to be converted manually/automatically and at what point in time.9. Result recording and Usage decision Quality Supervisor . Reporting Requirements Document the various reports that you would require.Creating & Changing Inspection lot.   List of pending Inspection lots Results display 13.  Not applicable 11. Result recording and Usage decision Quality control chemist – Display Inspection lot and Result recording 14. Description of Functional Deficits Where appropriate. as well as estimating the need for ABAP (or similar) resources. Integration considerations Specify what integration you need with other modules / sub modules  Not applicable 12.

Quality Notifications Page 53 of 70 . Not applicable 9.

the quality department will record the defects  The Quality department will inform the Purchase department about the defective material received  The Purchasing department will take a decision (Ex – Return delivery or Accept with deviation etc)  The corrective action will be taken by the Purchasing department  After completing the corrective action. Subsequent delivery or Price reduction)  The corrective action will be taken by the Sales department  After completing the corrective action. Requirements/Expectations A brief / bulleted list of requirements and expectations Customer complaints  The CSD department will receive the complaints from the customer  CSD department will inform the Quality department about the complaint received. the complaint will be closed by the CSD department Complaints against Vendor  When the material received from a Vendor is found defective. the material will be kept on hold  The Quality department will inform the Production department about the defects  The Quality department will define some corrective actions (Ex – Rework or Scrap etc)  The Production department will perform the corrective actions Page 54 of 70 . if any defects are found.1. if the complaint is technical  The Quality department will trace back the inspection results of the produced goods  The Quality department will analyze the problem  The Quality department will inform the CSD department about the results of the goods  The CSD department will take a decision (Ex – Return delivery. the complaint will be closed by the purchase department Internal problems  While producing the finished goods.

This typically does not include any SAP specific terms. After completing the corrective actions. Describe the naming and numbering convention in case of masters and enterprise structure  The number range for Notifications will be internal 3. the complaint will be closed by the quality department 2. General Explanations (For Masters and Enterprise structure include Naming Convention) Describe the business process in detail. Explanations of Functions and Events Explain what events and processes trigger this process Quality notifications will be created in the following cases    Defective material received from the Vendor Complaint received from the Customer Defects found in Produced material 4. Process Diagrams Provide all related process maps or diagrams Notification Overview Page 55 of 70 . it should relate purely to the business rules. Organizational Considerations Address any issues agreed in the workshop concerning the SAP organizational structure and this process.  Not Applicable 5.

Information related to the overall notification General data Tasks Activities Notification Header Notification Header level Item Overview Notification Item level Item Individual notificationrelated defects Item Item Causes Information related to a single defect item Tasks Activities Customer complaint Notifications Page 56 of 70 .

Receive Customer complaint by CSD dept Customer name Material number Purchase order number Process order number Sales order number Complaint quantity Defect types Causes Creation of Customer complaint notification (ZC) by CSD dept Reference object is Sales order number Or Process order number Inform Quality department about the customer complaint Trace back the results and Analysis of the complaint by Quality dept Revert back to the CSD department Define corrective actions by CSD dept and assign person responsible Performing the Tasks by Sales dept Forward notification to CSD dept Closing of the notification by CSD dept Vendor related Notifications Page 57 of 70 .

Inspection lot with reference to the Purchase order Vendor name Material number Purchase order number Goods receipt number Complaint quantity Defect types Causes Usage Decision Rejected Accepted Post the goods to unrestricted stock Record defects and Create Notification (ZV) by Quality dept Analyze the problem and inform Purchasing department Define Tasks and assign person responsible by Purchasing dept Purchasing department takes a decision on received materials Perform the Tasks and Completing the Tasks by purchasing dept Completion of Tasks by purchasing department Close the Notification by purchasing dept Internal problem Notification Page 58 of 70 .

Changes to Existing Organization processes Page 59 of 70 .In process Inspection lot with reference to the Process order Usage Decision Accepted Confirm Operation Process order number Material number Inspection lot number Complaint quantity Defect types Causes Rejected Record Defects and Create Notification (ZM) by Quality dept Analyze the problem and inform Production department Define Tasks and assign person responsible by Quality dept Take corrective actions & Implement in production Perform the Tasks and Complete the Tasks by Production dept Feedback from Production department Close the Notification by Quality dept 6.

In a quality notification for a customer complaint.Change management issues as appropriate. Solution in SAP. Customer complaints and Internal problems Now in SAP. there is no procedure to handle Complaints against vendor. A customer complaint may include the following reference objects:  Sales order number  Process order number When you process a quality notification for a customer complaint.   In the existing system. Customer wise. you can specify one or more reference objects. Describe how this process will be addressed in the product. Material wise. You can use a notification for a customer complaint to record and process a problem that is reported by a customer. Plant wise and Period wise 8. Customer complaint Notification A customer complaint is a quality notification type (ZC) that deals with a problem involving poor-quality goods or services delivered to a customer. you can also display the following supplementary information for a customer: Page 60 of 70 . A reference object has a relationship to the problem in a quality notification. Description of Improvements Describe improvements which will result from implementation of the SAP System. Be sure to include any impact on business drivers. Notification type wise. we can handle above complaints using Quality notifications 7.         Using quality notifications we can describe a problem and identify the affected reference objects Defects can be recorded and causes for the problem can be analyzed The system will record the names of all the persons who are involved with the problem Log all activities that have been carried out for the problem Print various types of reports related to the problem Generate list of notifications for processing and evaluation purpose Analytical reports can be generated which can be used by personnel from all user groups to aid them in their daily activities Reports on Overview of Notification can be generated Vendor wise.

terms of payment. Processing of Notification  The Customer complaint will be received by the CSD department  After receiving the customer complaint. the task will be completed in the notification Page 61 of 70 . Sales summary  Summary of important customer information (for example. the CSD department will create a notification with notification type ZC  The notification will be create with reference to the Sales order number or Process order number which will be printed on the label  While creating the notification. order data. all the data from the sales order or process order will be copied to the notification  The CSD department will inform the Quality department about the customer complaint. transaction data. the quality department will inform the CSD department about the results  The information will be forwarded through SAP to the external mailing system  The CSD department will define the corrective tasks depending the upon the complaint  The person responsible will be assigned against each task and release the task  The corrective tasks will be performed in or outside the notification by the user responsible for the task  Once the corrective action is performed by the concerned user.  Related notifications for the Customer. the in process inspection lot number will be available  Using this inspection lot number. and so on). the inspection results will be monitored in the display results transaction  After monitoring the inspection results. Material and the combination of both. in the assignment tab. using the external mailing system  The Quality department will trace back the results of the complained goods using based on the process order number or the sales order number  The Quality department will analyze the causes of the complaint  Traceability – In the process order display transaction.

quantities of Material ordered from the Vendor etc). The status profile of the Tasks is as follows Status Description TSOS Task outstanding TSRL Task released TSCO Task completed TSSC Task successful  The notification will be closed by the CSD department after all the tasks are completed  The status profile of the Notification is as follows Status Description OSNO Outstanding notification OSTS Outstanding tasks ATCO All tasks completed NOCO Notification completed Vendor complaint Notification A complaint against a vendor is a quality notification type (ZV) that deals with a problem involving poor-quality goods or services delivered by a Vendor or Manufacturer. You can use a notification for a complaint against a Vendor to record and process a problem that was confirmed in a delivery. A reference object has a relationship to the problem in a quality notification. When you process a quality notification for a complaint against a Vendor. you can also display the following supplementary information for a customer:  Summary of important information for the Vendor / Material (for example. Material and the combination of both Processing of Notification Page 62 of 70 . you can specify one or more reference objects.  Related notifications for the Vendor. In a quality notification for a complaint against a Vendor.

an inspection lot will be automatically generated  We can record the result at different intervals of time Page 63 of 70 . if any defects are found. the purchase department will complete the tasks  Finally the purchasing department will close the notification Internal Problem Notification An internal problem report is a quality notification type (ZM) that deals with quality related problems that originate within our own Organization. the quality department will inform the Purchase department about the complaint using the external mailing system  The information will be forwarded through SAP to the external mailing system  The purchasing department will trace back the purchasing documents  The Purchase department will define the corrective tasks and assigns person responsible against the tasks  These tasks will be performed by the purchasing users in or outside of the notification  After completing the tasks. the stocks will go into quality stock and an inspection lot is generated automatically  At the time of result recording for the inspection lot. the quality control chemist will record the defects  After recording the defects. We can use this notification for an internal problem report to record and process company internal problems (for example. In a quality notification for an internal problem report. a notification will be created with notification type ZV  All the data relating to that purchase order will be copied to the notification  The quality department will monitor the defects and analyses the causes of the problem  The quality department can take a usage decision. we can specify one or more reference objects. When the raw materials are received from the Vendor. A reference object has a relationship to the problem in a quality notification. if they want to block the stock  Once the notification is created and analysis is done on the problem. Processing the Notification  When a Process order is released. defects confirmed for a material or a product in a production process).

 Not applicable 11. Page 64 of 70 . then the defects will be recorded  The notification with notification type ZM will be created  All the data related to that process order will be copied to the notification  The quality department will analyze the problem and identify the causes of the problem  The quality department will inform the Production department about the notification  The information will be forwarded through SAP to the external mailing system  The quality department will define corrective tasks in the notification and assign the person responsible against the task  The production department will perform the tasks defined in the notification  The production department will complete the tasks  The quality department will close the notification 9.  Not applicable 10. Description of Functional Deficits Where appropriate. This section is important when assessing risk. Integration considerations Specify what integration you need with other modules / sub modules  Intergrated with SD. if any defects are found. MM and PP modules 12. While recording the results. identify any gaps. Approaches to Covering Functional Deficits Documentation of any work-around or assumptions that have been made when outlining functional deficits. as well as estimating the need for ABAP (or similar) resources. Reporting Requirements Document the various reports that you would require.

what data is to be converted manually/automatically and at what point in time. Where the information is to come from. This is critical information that is used later.  Not applicable Page 65 of 70 .  List of pending Notifications List of Tasks with status 13. Authorization Requirements Document the level of authorizations that you need for each process in the system    Quality head – Creating Quality notifications. File Conversion / Interface Considerations Document file conversion / interface requirements. assigning tasks and closing the notifications Quality control chemist – Creating Quality notifications 14. assigning tasks and closing the notifications Quality Supervisor – Creating Quality notifications.

10. it should relate purely to the business rules. Requirements/Expectations A brief / bulleted list of requirements and expectations      All the measuring and test equipments which affects quality will be periodically calibrated for accuracy Calibrations takes place both internally and externally The facility to define allowable range of equipment / instrument should be available The calibration reading should be recorded in the system Provision to maintain history of calibration should be possible 2. General Explanations (For Masters and Enterprise structure include Naming Convention) Describe the business process in detail.  Not Applicable 5. Organizational Considerations Address any issues agreed in the workshop concerning the SAP organizational structure and this process. Process Diagrams Page 66 of 70 . This typically does not include any SAP specific terms. Calibration of Equipments 1. Describe the naming and numbering convention in case of masters and enterprise structure  Not Applicable 3. Explanations of Functions and Events Explain what events and processes trigger this process  Not Applicable 4.

Provide all related process maps or diagrams Create Maintenance order Release Maintenance order Inspection Lot creation Result Recording / Valuation (Equipment) Rejected Recalibrate the Equipment Usage Decision Accepted Confirm Maintenance order Page 67 of 70 .

Description of Improvements Describe improvements which will result from implementation of the SAP System. system creates an inspection lot automatically Maintenance order number will be copied to the inspection lot Generates inspection specifications for each piece of the equipment Determines the inspection lot quantity based on the number of pieces of equipment specified in the maintenance order Determines which inspection characteristics to be inspected  The following inspection lot number ranges are used in Equipment Calibration process No. The objective of a calibration inspection is to determine whether each piece of equipment specified in the maintenance order meets the predefined performance specification. Changes to Existing Organization processes Change management issues as appropriate.  Not Applicable 7.  Not applicable 8. Describe how this process will be addressed in the product. This process contains  Inspecting the equipment specified in the maintenance order  Record inspection results of each piece of the equipment  Valuate each piece of equipment  Make a Usage decision for the inspection lot Inspection lot creation      When a Maintenance order is released. Solution in SAP. This scenario describes how to process test or measurement equipment in a calibration inspection. Be sure to include any impact on business drivers. 01 Inspection lot origin 14 Description From Number To Number Plant Maintenance 140000000000 149999999999 Page 68 of 70 .6.

identify any gaps. we valuate and close each characteristic and then valuate each piece of equipment The valuation specifies whether we accept or reject the equipment at operation level Usage decision    Usage decision code will be entered in Usage decision transaction as Accepted or Rejected Usage decision for an inspection lot confirms that an inspection has been completed The following UD codes will be used Code A R R1 R2  Short text Usable Cannot be used Recalibration Rework + Calibration Valuation code Accepted Rejected Rejected Rejected Once the inspection lot is completed.  Not applicable 11. as well as estimating the need for ABAP (or similar) resources. Integration considerations Specify what integration you need with other modules / sub modules Page 69 of 70 .Result recording    After inspecting each piece of test equipment. Approaches to Covering Functional Deficits Documentation of any work-around or assumptions that have been made when outlining functional deficits. we will record inspection results for each characteristics in each operation to determine whether the recorded values are within the predefined inspection specifications On the basis of inspection results.  Not applicable 10. This section is important when assessing risk. Description of Functional Deficits Where appropriate. the maintenance order will be confirmed 9.

Result recording and Usage decision Instrumentation Engineer .    List of pending Inspection lots Results display Calibration history 13. Authorization Requirements Document the level of authorizations that you need for each process in the system    Maintenance head – Creating & Changing Inspection lot. Where the information is to come from.Creating & Changing Inspection lot. This scenario is integrated with Plant maintenance. When the maintenance order is created and released. what data is to be converted manually/automatically and at what point in time. File Conversion / Interface Considerations Document file conversion / interface requirements. Reporting Requirements Document the various reports that you would require.  Not applicable Page 70 of 70 . 12. Result recording and Usage decision Instrumentation Technician – Display Inspection lot and Result recording 14. an inspection lot will be generated automatically. This is critical information that is used later.