Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
0 Implementation @ ISAP
Blueprint Phase Project Integrate
Document Control:
Author
File Name and Path
Created Meenakshi G. Solanki
Last Edited
Number of Pages 36
Target Readership
Contents:
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 present system in Indo Schöttle 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
information’s 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.
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 Schottle’s R/3 system. At the conclusion of the
blueprint , the Mphasis Consultants will determine the SAP functionality required
to run the Indo Schottle business.
The Blueprint reiterates the R/3 organizational structures that have been
identified and will serve as the basis for the initial configuration activities. The
Mphasis team believes that R/3 can accurately model Indo Schottle’s
organizational requirements.
No significant configuration choices have been identified that will prevent the
future implementation of additional capabilities within the R/3 environment.
The information gathered and documented in the Blueprint is sufficient for the
team to go forward into the Realization phase.
1. Quality Planning
a. Basic Data
· Inspection Methods
· Master Inspection Characteristics
· Catalogs
b. Inspection Planning
2. Quality Inspection
a. Inspection Lot Creation
b. Results Recording
d. Inspection Lot Completion
3. Quality Control
a. Dynamic Modification Of the Inspection Scope
b. Quality Notifications
4. Control in Logistics
a. QM in Procurement
b. QM in Production
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.
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.)
You can organize the view selection according to your needs using user settings.
Once inspection results have been recorded for an inspection lot and the
inspection is finished, you must reach a decision about the usage of the
inspected material. The Inspection Lot Completion (QM-IM-UD)
component provides you with the functions to:
When you make a usage decision for an inspection lot, the system also :
Usage decision
When you make the usage decision, you decide whether to accept or reject the
goods in the inspection lot based on the results of the inspection. While you are
in the transaction for the usage decision, you can also:
· Record defects
· Activate quality notifications
· Confirm activities for QM orders
· Make stock postings
· Once you have made the usage decision, the inspection is completed.
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
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
usage decision is made. The new inspection stage is used by the system to
calculate the sample sizes for the next inspection lot.
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:
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).
This component contains functions that allow you to integrate the tasks of Quality
Management with the procurement processes.
· · 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
This component contains functions, which allows carrying out several individual
inspections at different intervals during production or as a result of certain events.
(while producing process goods). You can monitor the production process
continuously with respect to the inspection characteristics
· 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.
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.
Material Master
Vendor evaluation
Processing goods receipt inspections
Role in invoice processing for quality nonconforming material supply
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.
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.
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.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:
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.
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.
The first time when an inspection method will be assigned, the system
sets a usage indicator in the inspection method. This indicator is relevant
when you delete an inspection method.
User can define a Catalog and store information in a coded form (for
example, data that describes inspection results, observations, tasks, or
decisions made during an inspection). Catalogs ensure that this
information is maintained uniformly by allowing user to assign a unique
key and a descriptive text to each entry .
Make usage decisions and carry out evaluations using the codes in
catalog 3 during inspection completion.
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.
6.1 - Introduction
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.
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.
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.
Production 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.
Vendor
Purchasing organization
Inspection lot size
Revision level for material (if required)
Vendor Master.
Plants
Work centers
Material Master
6.1.7 - Interface
When user will make a correction to the actual quantity of a stock-relevant
inspection lot, the system makes a posting in the Materials Management
(MM) component and creates a new material document to record the
changes. If the inspection lot is not stock relevant, the system records the
changes for informational purpose only (that is, no stock posting occurs).
Inspection Lot creation at the time of Confirmation of Production Order.
6.1.10 - Authorization
6.2 - Introduction
6.2.2– Description :
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.).
Work center for defining operation (i.e. Where operation takes place).
6.2.6 - Interface
6.2.9 - Authorization
6.3 - Introduction
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.
6.3.2 – Description :
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 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 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.
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 .
Inspection Characteristics are kept as master data where as the same will
be taken when the Inspection plan is carried out.
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
6.3.9 - Authorization
6.4 - Introduction
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.
6.4.2 – Description :
An inspection lot is the basis for all the results processing which has to be
created initially.
Name of the inspector, as well as the starting date and time of the
inspection will be entered in the system.
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 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.
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.
6.4.6 – Interface
6.4.9 - Authorization