Escolar Documentos
Profissional Documentos
Cultura Documentos
Blueprint Phase
Document Control:
Author
File Name and Path
Created
Last Edited
Number of Pages
Version
Revision
Date
Meenakshi G. Solanki
36
Revision Description
V1.0
Author
Mr S. S Pathak
Target Readership
Sign-Off
Contents:
1.0
1.1
1.2
1.3
2.0
2.1
2.2
2.3
2.4
2.5
3.0
4.0
5.0
6.0
6.1
6.2
6.3
6.4
Executive Summary...................................................................................4
Background ...............................................................................................4
Enterprise Resource Planning (ERP) Project Objectives.5
Overview of Blueprint Phase.5
QM Module Introduction ...........................................................................7
Quality Planning.........................................................................................7
Quality Inspection......................................................................................8
Quality Control .........................................................................................11
Quality Notifications..12
Control in logistics.13
QM Module Integration..15
QM Business Process in Scope.16
QM Master Data...17
Business Process Mapping in SAP R/320
Creating Inspection Lot.21
Quality Specification..25
Inspection Plan28
Result Recording32
1.
Executive Summary
Background
Indo Schottle Auto Parts Pvt. Ltd. was established in 1985 with the principal
business focus of manufacture and sale of auto parts and engine components.
The company's registered office and manufacturing facilities are located at
Urawade, Taluka Mulshi, Pune City. Indo Schttle is growing at a very fast pace
and has now progressed to being the prime O.E. supplier of Engine Valve Collets
in India. The company also exports products to USA, Europe and Asia. Indo
Schttle also manufactures Collets, spare parts for turbo charger, oil seal plate
etc. for Japanese applications viz. Suzuki, Isuzu, Nissan, Honda and Toyota.
The present system in Indo Schttle includes a MS DOS based system called PC
Soft and data capturing in MS Excel Sheets. This leads to data distribution, i.e.
there is no centralization of data and security in terms of creation and deletion of
records. As a result, creation of summary reports becomes very cumbersome
and time consuming. Currently no option available to consolidate the finance
informations across multiple divisions.
Indo Schottle has decided to implement an integrated ERP solution and has
selected the SAP R/3. Indo Schottle is implementing SAP R/3 5.0 ECC along
with Country India version to support upto maximum users across the plants.
Mphasis is the implementation partner for the R/3 implementation.
1.2
1.3
This Document summarizes the findings of the Mphasis consulting team, which
conducted the requirement analysis of Indo Schottle for the SAP R/3 system.
This information was gathered thru the interviews conducted at the Indo Schottle
plants with managers , key users and personnel from information system, as well
as the reviews of the business processes, business procedures, documentation
and relevant reports.
The immediate purpose of the analysis is to prepare to move rapidly with the
implementation of the Indo Schottles R/3 system. At the conclusion of the
blueprint , the Mphasis Consultants will determine the SAP functionality required
to run the Indo Schottle business.
2.0
QM Module Introduction
2.1
Quality Planning
2.2
Quality Inspection
The system uses the inspection lot to record, process, and manage information
for a quality inspection. This information includes:
Inspection processing data such as:
Inspection lot origin
Inspection date
Processing status of inspection lot
Account assignment information for cost settlement
Inspection specifications (for example, the task list or material specification
according to which the goods in the inspection lot will be inspected)
Inspection results
Recorded characteristic values
Recorded defects
Usage decision (a decision that specifies whether the goods in the inspection
have been accepted or rejected)
An inspection lot can be created manually by the user or automatically by the
system.
Once an inspection lot has been created, an inspection specification is usually
assigned to it. The system can assign an inspection specification automatically or
you can assign one manually.
Quality Inspection Result Recording
In the Results Recording component, you record and process results for
inspection characteristics. The inspection lot is the reference object in results
recording.
The recorded inspection results, document the quality of the inspected product
and provide the basis for creating batch specifications and inspection certificates.
You can use the recorded result data to make evaluations for quality control
purposes.
This function includes a worklist for recording inspection results for all objects
that allow results recording
(inspection lots, partial lots, inspection points in production or goods receipt,
physical samples, equipment and functional locations).
R/3 Business Blueprint for BALCO
On the selection screen, you first define the selection criteria for the objects to be
processed and then start the selection.
After inspection lot selection, the first operation with characteristics to be
processed appears automatically.
The corresponding characteristic overview screen is displayed to record results.
(If you select a characteristic for results recording, the characteristic single
screen appears.)
10
Record defects
Activate quality notifications
Confirm activities for QM orders
Make stock postings
Once you have made the usage decision, the inspection is completed.
2.3
Quality Control
Active quality control ensures the constant quality of the processes and products.
You use quality control to:
Update of the qualit y level based on the inspection results
Usage of control charts to control the characteristic values
Update of the vendor evaluation for the procurement process
Quality Control Dynamic Modification Of The Inspection Scope
Dynamic modification refers to the possibility of flexibly determining the
inspection scope. For example, you can use the data from past inspection
valuations to calculate the current inspection scope.
For goods receipt inspections, goods issue inspections, and inspections during
production, dynamic modification means:
You can vary the sample size in stages between a predefined inspection scope
(for example, 100%) and a skip. A skip means that a certain number of deliveries
or lots are not inspected.
The inspection severity can change between a normal, reduced, and tightened
inspection.
The variation or change depends on past inspection results that are reflected in
the current quality level.
For dynamic modification at lot creation, the quality level is updated when an
inspection lot is created. The system assumes that the forthcoming inspection
will lead to an acceptance of the inspection lot or characteristic.
An inspection lot, which is created immediately after the quality level is updated,
uses the information in the updated quality level without a usage decision having
been made.
If dynamic modification is carried out at lot creation and the inspection lot is
subsequently rejected, the system updates the quality level again when the
Process definition documents
Created by : Meenakshi G. Solanki
11
usage decision is made. The new inspection stage is used by the system to
calculate the sample sizes for the next inspection lot.
2.4
Quality Notifications
This component contains functions for recording and processing different types
of problems (for example, problems resulting from poor-quality goods or
services). You can use the notifications to analyze the recorded
defects and monitor the correction of these problems. In particular, the
notifications can help you process internal or external problems such as:
Complaints against vendors
Company-internal problems
Other user-specific problems
As an extremely flexible system, you can also use this component to process and
manage information of a positive nature (for example, to implement a "suggestion
system" in your company to manage improvements).
2.5
Control in logistics
12
Supply quality documents with requests for quotations and purchase orders
Evaluate vendors on the basis of quality
Certify vendors or manufacturers that have QM systems implemented, to
reduce the inspection requirement
Request that quality certificates be submitted with the delivered goods and
monitor the receipt of these certificates
Manage the posted goods in inspection stock
Block the payment of invoices until the goods have been inspected and
accepted
Control In Logistics QM In Production
This component contains functions, which allows carrying out several individual
inspections at different intervals during production or as a result of certain events.
With the component QM in Production, you can process inspections during a
production operation (while manufacturing discrete parts) or a process phase
(while producing process goods). You can monitor the production process
continuously with respect to the inspection characteristics
Using inspection points for an inspection during production, you can:
R3 Business Blueprint for BALCO
Inspect materials at regular intervals
Record inspection results for each inspection point and valuate each inspection
point with a "usage decision"
Assign a produced quantity to each inspection point and allocate the inspection
point quantities to partial lots.
With production lots with inspection point processing, the system transfers the
results to the batch
classification when you record results for the inspection point and not when the
usage decision is made.
13
The Quality Management module is fully integrated with other modules of SAP
R/3. The continuous exchange of information with other application areas in the
R/3 System ensures a real time database.
Considering the specific requirements of the organization, the SAP QM module
could be integrated with other modules.
The broad level integration areas with SAP QM module are,
3.1
Materials Management
Material Master
Vendor evaluation
Processing goods receipt inspections
Role in invoice processing for quality nonconforming material supply
3.2
14
The Quality Management module of SAP R/3 (ver ECC 5.0) offers appropriate
support in terms of mapping and representing the activities performed by QA
department in material procurement, production and quality notifications.
4.1
4.2
Role in Production
During production inprocess inspection lot will be created. This can be displayed
by users as and when required. Inspection lot for goods receipt from production
will be created. Result recording will be done and based on this, product will be
classified into various grades. Inspection result will be transferred to the batch
characteristics as characteristic values.
Process definition documents
Created by : Meenakshi G. Solanki
15
4.3
Quality Notifications
Quality notifications will be used to analyze the recorded defects and monitor the
correction of these problems in particular; Company-internal problems, complaint
related to vendors or other user specific problems.
Also it will be utilized to process and manage information of a positive nature (for
example, to implement a "suggestion system" to manage improvements).
5.0
QM Master Data
5.1 - Introduction
Scenario
Quality Management
Process
QM<Master Data>
5.2 - DESCRIPTION
Master data includes information that is important for quality management. It is
handled independently from the maintenance of inspection plans.
In the QM component, the following data is maintained as master data:
16
When Creating the master inspection characteristics the user should enter
the Valid from field the system proposes the current date as the beginning
date for the validity period of the master inspection Characteristics.
User has to define the Characteristics Type in the system qualitative or a
quantitative characteristic.
Then user will maintain the control indicators for the characteristic.
The control indicators defines how inspection results are to be recorded,
whether a sampling procedure is required or whether, in the case of a
quantitative characteristic, upper and/or lower tolerance limits have to be
entered. If you are creating a quantitative characteristic, you can maintain
a tolerance key and quantitative data.
form (for
tasks, or
that this
a unique
17
attributes
2-Tasks
8-Activities
9-Defect Type
3-Usage decisions
4-Events
5-Causes
6-Defect consequences
Make usage decisions and carry out evaluations using the codes in
catalog 3 during inspection completion.
Classify quality notifications on the basis of the entries in the
catalog for (for example, as a problem notification, complaint or
reminder)
5.2.4 - <Dynamic Modification Procedure>
18
For each inspection stage, you can define conditions under which the
system increases or decreases the inspection . There are two cases :
An "OK" case
A "not-OK" case
If the conditions for a "not-OK" case are met, the system selects the new
inspection stage that was defined for a "not-OK" case. The number of
rejections that must occur before the inspection stage can be changed
If the conditions for the "OK" case are met, the systems selects the new
inspection stage that was defined for an "OK" case. The number of
inspections to be carried out before the inspection stage can be changed.
If neither condition is fulfilled, the system does not change the inspection
stage.
19
6.0
6.1 - Introduction
Scenario
Quality Management
Process
The results that are recorded during an inspection are stored in the
inspection lot record. User can only access the individual inspection
results through the inspection lot. The usage decision for an inspection lot
completes the inspection and is stored with the inspection lot.
Inspection lot created manually. Individual inspection results can only be
accessed through the inspection lot. When the inspection lot is created an
inspection plan is attached which includes inspection characteristics to be
inspected. A usage decision completes the inspection and is stored with
the inspection lot.
When the materials / components are procured from a vendor & triggers
for an inspection , the system creates an inspection lot ,user make a
usage decision for an inspection lot, the system normally posts the stocks
to unrestricted-use stock, assuming the usage decision for the inspection
lot is OK.
20
6.1.3 Description :
User will enter the material , Plant for which the inspection lot is being
created. Causes for the Inspection lot has to be provided by the User.
Inspection Lot Origins which support the automatic creation of an
inspection lot can also be used to create a lot manually .They are :
Goods receipt, external (purchase order)
automatically
Goods issue
automatically
Production
automatically
automatically
automatically
Only Inspection types defined and marked as active in the material master
for the components / materials can be entered in the Inspection Lot Origin
field, also respective inspection plan or Routing has to be created before
hand.
When an inspection lot is created automatically, all stock postings are
carried out by the QM component. As a result, user can make stock
postings using the functions within the scope of the usage decision.
An inspection plan or material specification must be assigned to the
material.
User will enter vendor-related data, or the following information to identify
the origin of goods for which you are creating the inspection lot:
Vendor
Purchasing organization
Inspection lot size
Revision level for material (if required)
21
Vendor Master.
Plants
Work centers
Material Master
22
6.1.7 - Interface
Report Name
SAP T-code
Remarks (standard/
development : Y/N)
6.1.10 - Authorization
Authorization Roles
Description
23
6.2 - Introduction
Scenario
Quality Management
Process
QM<Quality Specification>
6.2.2 Description :
24
Define the inspection plan for each material at plant level, i.e. On screen
define the material and plant & go to the operation.
You can also attach inspection method with each inspection characteristic
in the inspection plan.
Inspection plan contains the control indicators i.e. Targeted value, Lower &
upper limit and we can change it in inspection plan if required.
Inspection plan is created for different uses (i.e. inspection of good receipt
RM, in-process inspection, FG inspection, stock transfer, calibration, etc.).
25
6.2.6 - Interface
6.2.7 - Gaps and Solutions
Report Name
SAP T-code
Remarks (standard/
development : Y/N)
6.2.9 - Authorization
Authorization Roles
Description
26
6.3 - Introduction
Scenario
Quality Management
Process
QM<Inspection Plan>
The inspection plan is the task list used by the Quality Management
(QM) component to process quality inspections. Inspection plans are
used to carry out such production-related tasks (for example, inspecting
goods upon goods receipt or goods issue).
Quality inspections during production are carried out on the basis of the
routing. Inspection Plans depends on the master data This data includes
inspection catalogs, inspection characteristics, inspection methods,
sampling procedures, sampling schemes, dynamic modification rules,
inspection plans, reference operation sets and material specifications.
The plan consists of the following elements:
General information (header)
One or more operations; operations within the QM component are
created and maintained exactly as those within the Production
Planning (PP) component. For information about operations, see
the online documentation for PP Production Planning.
For each operation you can define :
Test equipment used for the inspection (as production resources) .
Location where the inspection takes place (as work centers).
Inspection characteristics (inspection characteristics cannot be
assigned to a sub-operation).
6.3.2 Description :
27
The inspection plans are created in the planning plant. One plan for each
group of materials and type of inspection (e.g. final inspection, recurring
inspection) required. Where there is more than one inspection type
required for a specific material group then we can keep them in the same
task list group and distinguish them by different group counters.
All of the materials within the same material group will then be assigned to
the relevant group and group counter(s) For better control and
maintenance, it is feasible to keep all inspection plans in a Planning Plant
with assignment to related Production Plant.
User will Enter a date in the future the inspection plan will be valid. The
system will populate this field with the current date.
User can Enter a short description of the inspection plan.
User will enter the Usage Key which is a alphanumeric key that uniquely
identifies the inspection plan use ID, (I.E. production, goods issue, goods
receipt, universal)
User has to specify the Inspection plan status which will be a
alphanumeric key that uniquely identifies the inspection plan status, (I.E.
created, released)
User has specify the inspection points to process the inspection, enter the
inspection points .
Then user will attach the Operations related to the work centres. Then the
Qualitative or Quantitative indicators are set to get the Inspection
Characteristics.
In the Inspection plan Inspection methods are attached to the Materials
User will define the vendor code who has supplied the materials .
If a raw material is obtained from more than one Vendor and a different
inspection plan is required for each these are created as follows.
Create two inspection plans for the same material, two group counters, as
per the above instruction.
In the material assignment window user will enter the vendor number to
which each counter is applicable .
28
Vendor Master.
Material Master
Work centers
6.3.6 Interface
The inspection plan structure mirrors the structure of the routing in the
Production Planning (PP) component
Report Name
SAP T-code
Remarks (standard/
development : Y/N)
29
6.3.9 - Authorization
Authorization Roles
Description
6.4 - Introduction
Scenario
Quality Management
Process
QM<Result Recording>
30
If more than one inspection plan exist for a finished product, e.g. different
plans for different customers, it is necessary to select the right task list in
inspection lot.
For inspection of purchasing, system will be able to select the inspection
plan if we assign different plan to different vendors.
If a master inspection characteristic is set to be Required in inspection
plan, user is not allowed to skip it with result recorded.
6.4.2 Description :
An inspection lot is the basis for all the results processing which has to be
created initially.
After user enter an inspection lot, specifying operation (because results
processing is carried out at the level of the inspection operation). User
must process all of the characteristics in an operation before you proceed
to the next operation.
Name of the inspector, as well as the starting date and time of the
inspection will be entered in the system.
The system displays all inspection characteristics to be processed for
each respective operation on the characteristic overview screen. For each
characteristic the status, valuation, short text, sample size (to be
inspected), number of inspected single units, and the number of
nonconforming units are displayed. The displayed data depends on the
recording view.
31
Using the various results recording views, User can record the values
directly on the characteristics as defined.
The entries that are relevant on the characteristic main screen are
determined by the definition of the inspection characteristic in the
inspection plan. The characteristic category, the control indicators of the
inspection characteristic, and the sampling procedure all play an important
role in the definition of the characteristic.
The steps involved in results recording tasks on the characteristic main
screen depend on the type of recording form. Inspection results can be, for
example, summarized recording of inspection results, processing of
single-unit results, or results recording tasks in classes.
To record results for inspection points in an inspection during production,
user should take care the following conditions which have to met
The user field combination for the inspection point type (inspection
during production) has been defined.
The inspection lot must be released for results recording.
User will enter all the required values on the characteristic is valuated.
Once the User has valuated a characteristic, he will close it. This function
ends the processing of the characteristic.
If an error occurs when closing a characteristic, the system will enter a
note in the characteristic error message list or display an error message
on the screen.
Once User closes the characteristic (or if he wants to exit before he have
finished processing the characteristic), he must save the results that yhas
been entered for the characteristic.
32
6.4.6 Interface
Report Name
SAP T-code
Remarks (standard/
development : Y/N)
6.4.9 - Authorization
Authorization Roles
Description
33
34