Unity FSP MFG 00 V01R01

Project Unity Functional Specification - Manufacturing Master Data
P ROJECT U NITY
F UNCTIONAL S PECIFICATION - M ANUFACTURING M ASTER D ATA
VERSION: 01 REVISION: 0100
Document Approval and Release

ROLE NAME (AND TITLE) DATE AND SIGNATURE
AUTHOR
ACCENTURE CLAUDIA BIANCHI
REVIEW
CSV – VALIDATION CARLO CANDOTTI

CONSULTANT
BUSINESS – LOCAL TEAM LEAD DAVE MARKOVICH
YANICK GAUTHIER
BUSINESS – CORPORATE TEAM DAVIDE COHA

LEAD
423524079.doc Page 1 of 88
APPROVAL
IT – CORPORATE MARCO MAIOLI
BUSINESS – NORTH AMERICA LUC RAYMOND

TEAM LEAD
GQ – VALIDATION SANDRO TACCANI

COORDINATOR
423524079.doc Page 2 of 88
Document History
Version- Change date Responsible person Change summary

Revision
V00R00 18-NOV-2011 Claudia Bianchi Initial Version
V01R00 10-DEC-2011 Marco Introna Approved Version
V01R01 10-SEPT-2014 Elisabetta Sozio Document updated for GSM

Valeria Mulas
Last version revision information
Paragraph # Change
Par. 2 Paragraph updated for GSM
Par. 3.1.3 Paragraph updated for GSM
Par. 3.1.6 Paragraph updated for GSM
423524079.doc Page 3 of 88
Table of Contents
1. Introduction.................................................................................................................... 5
1.1 Reference Documents............................................................................................. 5
1.2 Definitions & Acronyms...........................................................................................5
2. Document Purpose..................................................................................................... 7
3. Short Functional Description....................................................................................8
3.1 MFG01_Manufacturing Master Data.......................................................................8
3.1.1 MFG01-01_Bill of Material....................................................................................8
3.1.2 MFG01-02_Resources.......................................................................................... 9
3.1.3 MFG01-03_Recipe................................................................................................ 9
3.1.4 MFG01-04_Production Version...........................................................................13
3.1.5 MFG01-05_Material Master view (MRP, Work scheduling view).........................13
3.1.6 MFG01-06_Engineering Change Management...................................................14
4. Business Process Flow Chart..................................................................................17
5. Solution...................................................................................................................... 19
5.1 Bill of Material......................................................................................................... 19
5.2 Resources............................................................................................................... 25
5.3 Master Recipe......................................................................................................... 28
5.4 Production Version................................................................................................ 38
5.5 Material Master View.............................................................................................. 43
5.6 Engineering Change Management........................................................................48
5.7 Functional Message Codes & Content.................................................................54
6. Overview Of SAP Transactions & Customizing Activities..................................55
6.1 SAP Transactions................................................................................................... 55
6.2 Customizing Activities........................................................................................... 56
7. Overview of Additional Developments.................................................................87
7.1 Reports, Forms....................................................................................................... 87
7.2 Interfaces................................................................................................................ 87
7.3 Conversions........................................................................................................... 87
7.4 Enhancements........................................................................................................ 87
1. Introduction................................................................................................................ 5
1.1 Reference Documents............................................................................................. 5
1.2 Definitions & Acronyms...........................................................................................5
2. Document Purpose..................................................................................................... 6
3. Short Functional Description....................................................................................6
3.1 MFG01_Manufacturing Master Data.......................................................................6
3.1.1 MFG01-01_Bill of Material....................................................................................7
3.1.2 MFG01-02_Resources.......................................................................................... 8
3.1.3 MFG01-03_Recipe................................................................................................ 8
3.1.4 MFG01-04_Production Version...........................................................................11
3.1.5 MFG01-05_Material Master view (MRP, Work scheduling view).........................12
3.1.6 MFG01-06_Engineering Change Management...................................................13
4. Business Process Flow Chart..................................................................................15
5. Solution...................................................................................................................... 17
5.1 Bill of Material......................................................................................................... 17
5.2 Resources............................................................................................................... 23
5.3 Master Recipe......................................................................................................... 26
5.4 Production Version................................................................................................ 35
5.5 Material Master View.............................................................................................. 40
5.6 Engineering Change Management........................................................................45
5.7 Functional Message Codes & Content.................................................................50
6. Overview Of SAP Transactions & Customizing Activities..................................51
6.1 SAP Transactions................................................................................................... 51
6.2 Customizing Activities........................................................................................... 52
7. Overview of Additional Developments.................................................................84
7.1 Reports, Forms....................................................................................................... 84
423524079.doc Page 4 of 88
7.2 Interfaces................................................................................................................ 84
7.3 Conversions........................................................................................................... 84
7.4 Enhancements.......................................................................................................... 84
423524079.doc Page 5 of 88
1. INTRODUCTION
1.1 REFERENCE DOCUMENTS
Reference Document
[1] UNITY-MFG-URS – Manufacturing User Requirement Specifications
[2] UNITY-FSP-INV-07 – Manage manufacturing process in WM Functional Specification
[3] UNITY-FSP-INV-04 – Goods Receipt for Internal Production Functional Specification
[4] UNITY-FSP-SD-01 – Sales & Administration Master Data Functional Specification
[5] UNITY-FSP-PUR-01 – Purchasing Master Data Functional Specification
[6] UNITY-FSP-MFG-06 – Audit Trail Functional Specification
[7] UNITY-FSP-QUA-01 – Batch Management Functional Specification
[8] UNITY-FSC-MFG-02 – Manufacturing Bill of Materials Functional Specification
[9] UNITY-FSC-MFG-01 – Master Recipe Functional Specification
1.2 DEFINITIONS & ACRONYMS
Term/Acronyms Definition/Explanation
SAP Systems, Applications & Products in data processing
BoM Bill of Material; it is a complete, formally structured list of the components that make up a
product or assembly. The list contains the material number of each component, together
with the quantity and unit of measure.
ECM Engineering change management; it is an Engineering change document which is used for
BOM and recipe creation and changes.
FP Finished product; this term describes both the end product manufactured.
SFP Semi-finished Product; Terms describing an intermediate product, which could be used in
another intermediate product or in an end product manufactured.
PO Process Order; it is the main control instrument used in production. It is used to describe,
update and monitor all production-relevant factors, both planned and actual.
MRP Material Requirement Planning
QA Quality Assurance
PV Production Version; a production version determines which alternative BOM is used

together with which task list/master recipe to produce a material or create a master
production schedule.
MIC Master Inspection Characteristics
CM Change Master
MD Master Data
UoM Unity of Measure
ECR Engineering change Request
VFD Valid From Date
QM Quality Management
CP Control Panel
IH Injector Hood
PS Power Supply
S/N Serial Number
423524079.doc Page 6 of 88
Term/Acronyms Definition/Explanation
IPC In Process Control
SKU Stock Keeping Unit
423524079.doc Page 7 of 88
2. DOCUMENT PURPOSE
The purpose of this document is to describe how the solution will respond to user
requirements concerning Manufacturing Organizational Structure and, in particular, the major
guidelines for the business rules on creation/maintenance of Manufacturing master data.
Manufacturing Master Data are required in order to make full operational use of SAP
manufacturing processes in the Bracco Unity process scope.
This document is relevant for the following manufacturing companies:
 EZEM Canada Inc. (Montreal)

 EZEM Inc. (Mississippi)
 ACIST US (Eden Prairie)
 ACIST EU (Maastricht)
 SMC / BINJ EU (Losanna)
In the context of the Global Service Model initiative Acist EU (AC11) and Binj Eu (SM01)
Plants, initially intended to be distribution centers will be enhanced to support assembly and
repair process through the PP-PI module extension as per UNITY template. The scope is
limited to two main business scenarios:
 Assembly processes orders, based on discrete manufacturing and supporting the
transformation process of sub-assemblies into assemblies and devices (e.g. CT-
EXPRESS);
 Rework process orders used to support internal repair activities (e.g. CVI)
QM core functionalities supporting the production process will be extended as well, for more
details please refer to [7]. Usage of the PP-PI functionalities will allows full batch/serial
number traceability via process order standard tracking, a better visibility and control on
assembly costs and a full integration with repair service management leveraging the
rework/repair order scenarios (S/N SKU case only). The usage of the PP-PI module will
requires material master data extension is order to manage relevant production master data
(e.g. Work Scheduling View) and additionally the creation from scratch of the relevant
production master data (Resources, BOMs, recipes and Production Versions) described into
the following paragraphs.
Project Project Project Process Process Subprocess Subprocess

Stream Domai Domain Code Description Code Description
n Code
Operations MFG Manufacturing MFG01 Manufacturing
Master Data
MFG01-01 Bill of Material
MFG01-02 Resources
MFG01-03 Recipe
MFG01-04 Production Version
Material Master view
(MRP, Work
MFG01-05 scheduling view)
Engineering Change
MFG01-06 Management
For each of the above sub-processes, the following entities are in scope:
Subprocess Description ACIST US ACIST EU ACIST ASIA EZEM BDI SMC/

BINJ EU
Bill of Material X X X X
Resources X X X X
Recipe X X X X
Production Version X X X X
Material Master view (MRP, Work X X X X
scheduling view)
423524079.doc Page 8 of 88
Engineering Change Management X X X X
3. SHORT FUNCTIONAL DESCRIPTION
3.1 MFG01_MANUFACTURING MASTER DATA
Master Data is an integral part of the SAP ECC System. Manufacturing Master Data is the
general grouping terminology for all individual master objects used during manufacturing
process.
Different master data objects are used as inputs for the creation and management of the
Production Execution process. These components are:
 Bill of Materials;
 Resources;
 Master Recipes (Routings);
 Production Versions;
 Material Master;
 Engineering Change Management (ECM).
All these key master data elements will be described in the rest of this chapter.
3.1.1 MFG01-01_Bill of Material
The Bill of Material (BoM) is a complete, formally structured list of components and related
information (e.g., quantity, unity of measure, scrap information, stock category, etc.) to be
used during manufacturing of semi-finished products, finished products (FP), sub-assemblies,
assemblies and devices. Substantially, a bill of material includes the link between the
produced material and the list of components needed to produce/assemble it.
A BoM may contain the following kinds of components:
 externally procured components – raw materials & packaging components;

 externally procured components – “sub-assemblies”;
 internally produced components - "semi-finished products";
 internally produced components - "sub-assemblies";
 internally produced components - "assemblies" (CP, IH, PS);
 internally produced components - "serialized finished products" (in case of re-
work process);
 internally produced components - "finished products" (in case of re-work
process).
A BoM is defined at plant level for a specific material code and it is basically composed by an
header and an Item Master.
The BoM header contains produced goods information, such as:

 Product Code;
 Product Description;
 Validity Period;
 Product reference quantity1;
1
A BoM can only refer to a finished product quantity equal or greater than 1.
423524079.doc Page 9 of 88
 BoM usage (Production, Costing, Validation, Engineering, etc.);

 BOM status;
 Alternative BoM Code2.
The BoM Item Master contains components information, such as:
 Material Code;
 Material Description;
 Quantity to be used (based on the quantity needed to produce the semi-
finished/finished product reference quantity);
 Unit of Measure;
 Material reference scrap for production process (only for continous production);
 Stock Item Category (stock managed and non-stock managed materials).
It is also possible to maintain BoM status levels to allow material planning and procurement
prior to release BoM for production.
There are two ways for creating a BoM (both under change control process):
 create Bill of Material from scratch inserting all header and item data required;
 with reference to an existing BoM (creation for copy).
During the creation or change of BOMs it is possible to define a validity period and to track
changes with a specific validity date that reflects when the changes will become effective for
production.
3.1.2 MFG01-02_Resources
The resource represents the logical modeling of a transformation element for the production
process (e.g., production line, operating unit, work center, etc.) as well as the related
persons involved.
A resource is assigned to operations and phases in the master recipe and inherited in process
orders to specify where in the plant and by whom a process step is carried out.
In the resource important data are defined concerning:
 The use of production Resource/operators;

 The rules to replenish materials for the resource (resource replenishment area);
 The costs of operating the resource.
It is possible to create, change or delete a resource in the system. During resource creation
the following elements have to be specified:
 a resource category (e.g., a processing unit, a person, an intermediate storage area);
 a cost center;
 a default Resource Supply Area to manage the material replenishment process;
 a Resource Validity period;
 a Resource Controlling Area.
2
During the association of the BoM to the Product, it is necessary to define if it has to be used as the
primary BoM for the product or as one among the alternative ones. In the latter case we are talking
about multiple BOMs and the “Alternative BoM Code” field is used.
423524079.doc Page 10 of 88
3.1.3 MFG01-03_Recipe
Master recipe represents a sequence of operations and phases to produce semi-finished

products, finished products, sub-assemblies, assemblies and devices.
A master recipe consists of the following key elements:

 an header (containing produced goods information);
 a recipe structure (containing the structure of operations, sections and phases
required to run production process)
 a material assignment (containing the link between materials required to run
production process and the specific step of the process where components are used
into)
All these key elements are described in detail into the following sections.
3.1.3.1 Header data definition
Once the change request for a recipe has been created and released for changes the
creation/modification process can start. Concerning the recipe header data, department
Master Data Operator inserts/modifies at least the following header information:
 Recipe code (once assigned, it is not modifiable anymore) and description;

 Recipe Usage (e.g., Production, Re-work, Validation, Clinical, Engineering);
 Recipe group;
 Recipe validity period;
 Product code;
 Product Reference quantity (product quantity from which needed component
quantities are calculated);.
System allows the management of version counter (recipe counter) for master recipes in
order to differentiate different alternatives available (e.g. different reference quantities,
different recipe structure, etc…).
As an alternative to normal process flow, Master Data personnel can decide to create a new
recipe by duplicating an existing one in the system. Duplication of a recipe means that
destination recipe shall inherit all the attributes of the source recipe. Specifically, by
duplicating a recipe, Master Data operator assigns to the destination recipe the header data
taken from the source one. However, it is possible to assign a copied recipe to a different
product code.
Note: Once the Master Data operator has created a recipe header by duplicating an existing
one, the newly created recipe undergoes normal flow for recipe elements assignment.
3.1.3.2 Recipe Structure Definition
In order to define the recipe structure the Master Data personnel has to define the following
main set of information:
 Operation/phase/section structure (numbering, relationships, resource assignment,
description, etc…);
 Standard times definition;
 In Process Controls assignment.
423524079.doc Page 11 of 88
Operations, identified by a unique and sequential code ID into the recipe, can be actual
processing steps (e.g., mixing, filling, burn-in testing, assembling, etc.), preparatory steps
(e.g., pre-printed materials preparation, dispensing) or steps executed after actual processing
(e.g., quality controls).
In the recipe is defined the sequencing of the operations to be executed during the
production process and the direct relationship with related sections and phases.
For each processing operation, user can define:
 A resource, representing the area where the operation takes place;

 Alternative production lines that can process an operation in place of a defined one;
 The list of the In Process controls to be executed during the operation (if any);
 Labor and machine3 standard times that are required to produce a defined quantity of
the product.
Labor and machine standard times measure the resources (machine and operators) required
to complete the operation and can be used for planning, cost accounting and process revision
purposes.
Note: If the Master Data operator is creating/modifying recipes using the duplication
functionality he/she can assign to destination recipe the operation element inherited from the
source recipe or choose another one.
A section represents the main steps performed in order to process an operation.

Each section has a unique and sequential code ID which identifies it into the recipe (and this
is directly linked to the operation ID).
Typical sections, which make up the operations, are:
 Resource set-up (resource preparation for production activity);

 Resource run (resource actual production activity);
 Resource closure (reconciliation and verification activities).
For each section, user can define:
 The operation to which the section is assigned;

 The phases to which the section is assigned.
3
Machine times has to be defined only for EZEM plant
423524079.doc Page 12 of 88
A phase represents the steps performed on a resource in order to process a well defined set
of instructions. Typical phases, which make up the operations, are:
 Machine set up;

 Resource cleaning;
 Material Receiving;
 Goods Receipt.
For each phase, user can define:
 The section to which the phase is assigned to;

 The materials of the BOM that will be assigned to the current phase;
 The Control Key for the integration with other SAP modules (e.g. confirmation
modality, relevancy for costing, relevancy for in process control execution, relevancy
for goods receipt posting, etc…).
Once a resource has been associated to an operation, Master Data operator assigns/modifies
the labor and machine standard times for selected operation, performs a consistency check
for Production version (execution), create/modify relationships between phases.
Master Data Operator assigns/modifies standard labor and machine times for the operation
on the basis of the time needed to execute the activities foreseen. Labor and machine times
are assigned considering the specific product, whose recipe is being created/modified, and its
recipe types (if different recipe types exist).
Specifically, MD operator assigns/modifies the following data for labor and machine activities:
 Fixed time (time spent on production activity that does not depend on produced
quantity);
 Variable time versus unitary produced quantity (time spent on production activity to
produce a unitary quantity).
Note: if the operator is creating/modifying the recipe using the duplication functionality
he/she can assign to the destination recipe the recipe structure elements inherited from the
source recipe or choose another one.
Master Data Operator will include in the recipe the complete information relating to In-
process controls (IPC) to be executed in the Shop Floor.
Regarding the IPCs the Master Data operator will describe the tests or examinations to be
conducted, directly in the Shop Floor, on appropriate samples of in-process materials of each
batch/lot (associated to a run section). Such control procedures are established to monitor
the output and to validate the performance of those manufacturing processes that may be
responsible for causing variability in the characteristics of in-process material and the drug
product/assembly. Operator will describe the acceptance criteria for the IPC execution (e.g.,
limits, frequency and preset catalog) and appropriate statistical quality control criteria as a
condition for their conformance. IPCs are defined at operation level using an In-Process
Control (IPC) master file containing the following information:
 Master Inspection Characteristic Code;

 Master Inspection Characteristic Description;
 Master Inspection Characteristic Type (IPC Qualitative or Quantitative).
Note: It is always possible for MD operators to create, modify or delete predefined Master
inspection characteristics for a specific recipe.
423524079.doc Page 13 of 88
For Acist EU and BINJ EU Process orders, covering basically assembly and rework scenarios
on S/N SKUs, IPC will be not defined at recipe level. The QA release process will rely only on
inspection plans linked to the inspection lots created at the goods receipt posting. For more
details please refer to [7].
3.1.4 MFG01-04_Production Version
The Production Version is the object that references a unique combination of a BoM and a
master recipe for the production of a material on a specific key date.
A production version is mainly composed by the following data:
 Details on the material you want to produce, for example, the material number and
storage location where the material has to be stored;
 General data about the production version. These include:
o Production version identification code;
o Lot-size range and validity period of the production version;
o Information on whether the production version is locked (used in case of

production version obsolescence);
o The date and status of the latest consistency check run on production
version.
 The assignment of task lists/master recipes to the production version;
 The change number used for the creation of production version.
3.1.5 MFG01-05_Material Master view (MRP, Work scheduling view)
Material Master contains the information related to all the materials involved in the production
process. The main grouping criteria used to classify the materials are the following:
Material type
It represents the first level of classification for the materials and it is used by the system to
group together materials with the same properties to manage them properly.
Main examples of different material types are the following:

 Raw Materials;
 Packaging Components;
 Intermediate Materials;
 Semi-Finished Goods Materials;
 Finished Goods Materials;
 Spare Parts;
 Indirect Materials (non-stock items);
 Accessories.
Unit of measure
It contains all the units of measure (UoM) managed by the system and its properties such as
number of significant digits, number of decimal digit, etc. In the material master also the
conversion factors between UoM assigned to the same material will be managed.
423524079.doc Page 14 of 88
Lot size
It represents the specific lot size to consider for produced goods (fixed, variable with/without
rounding value) and its related reference values (target value, minimum lot size, maximum
lot size, rounding value).
Batch entry
It contains the rule to allocate the batch in process order for BoM components. The possible
options are:
 Component batch/lot is allocated manually before Process Order Release;

 Component batch/lot is allocated automatically by the system after Process Order
Release;
 Component batch/lot is automatically allocated by the system after material
replenishment confirmation;
 Component batch/lot allocation is not required at Process Order level.
Production storage location

This field contains the storage location where produced goods will be posted during the
Goods Receipt from Production.
Backflush
It is possible to set this flag (in the MRP2 view of the material Master) in order to define
whether a material has to be managed using backflushing or not.
Production schedule profile

It is used to manage specific rules for:
 material replenishment at process order release;

 automatic or manual process order release;
 bundle of documents generation;
 batch master and classification generation at process order release;
 process order type to use, as default, at process order creation.
Stock availability check

It contains the specific rule to follow for checking the stock availability at Process Order
Creation and Process Order Release based on specific stock status.
Goods Receipt Tolerances

It is used to define goods receipt tolerances for produced goods; the following options are
available:
 underdelivery tolerance;
 overdelivery tolerance;
 unlimited overdelivery.
Potency (relevant for Ezem only)

The standard potency of a material is held on the “Additional Data” section of material
master. In this section is defined the specific characteristic used to manage potency value
and the standard potency value (in percentage) used for planning and procurement
purposes.
423524079.doc Page 15 of 88
3.1.6 MFG01-06_Engineering Change Management

The process of Engineering change management includes the change request and change
approval activity which is managed and administered outside of SAP, and the creation,
change and inactivation of master data which is managed and stored in SAP.
The process starts when the requester submits a change request, the change control
administrator processes this change request and assign an ECR number to it. Then there is
an impact analysis on all the area related to the master data included in the ECR. After that,
the Change review board reviews it and decides to approve or reject the change request.
All this process is managed on paper (for Acist) and on Trackwise (for Ezem), in both cases
outside SAP.
Once the Change review board approves the ECR, then a change master is created on SAP in
order to authorize and track the maintenance of the master data in the system.
Change master is an object used by the system with basically two main parts:
 Change header – with description, valid from date and status;

 Object overview – with the list of all the objects impacted by that specific CM.
The Valid from date is the key date from which the object change is effective with the
corresponding change number. It is used to decide when a change performed using the
change number must become effective in the system. The picture below describes graphically
the usage of this date:
The master data impacted by the Change master are the following:
 Master Recipe
 Bill of Material
 Production version (only if both previous two object linked to the PV are selected
in the CM)
Quality assurance is responsible to create, maintain, approve and close the change master in
SAP.
The processing status of a change master is controlled by the Change number status. This
status contains the following information:
 If an object, relevant for CM, can be created/changed using this CM or not;

 If the valid from date in the CM can be changed or not.
The following Change no. status will be used:
 “03” ECM in progress – no change to VFD allowed;

 “04” Pending QA approval – CM cannot be used, VFD cannot be changed;
423524079.doc Page 16 of 88
 “05” Approved by QA – CM cannot be used, VFD can be changed;

 “06” ECM closed – CM cannot be used, VFD cannot be changed.
With these statuses and with the authorizations that will be given to specific users it will be
possible to control the process of the Engineering change management.
The “Authorization group” is used as identification for the plant which the CM is referred to:
this data is filled in the header screen of the CM with one of the following plant specific
values:
 “0010” – for Ezem
 “0020” – for Acist US
 “0030” – for Acist EU
 “0040” – for SMC/BINJ EU
In this way, the user can immediately recognize which plant the CM is impacting.
The following steps are used as process for the ECM:
1. Quality assurance operator creates a CM with:

 VFD = 31.12.2099, so the change will never be considered by the system during
actual production;
 Authorization group according to the plant – this value is customized in the

system based on the Change Number profile:
o ZMD001- Change Master Record Profile - Ezem;
o ZMD002 - Change Master Record Profile – Acist;
o ZMD004 - Change Master Record Profile – Acist EU;
o ZMD005 - Change Master Record Profile – SMC/BINJ EU.
o .
 Change no. status “03” – ECO in progress.
2. Quality assurance operator uses the change number to change the master data
impacted by the change; after that changes have been implemented, the Quality
assurance operator changes the Change no. status to “04”. This user is not
authorized to move the status to “05” or “06”.
3. Quality assurance approver reviews the change and, in case of approval, moves the
Change no. status to “05”. Now Quality assurance approver can change the VFD to
the correct one. If required, Quality assurance approver can access to C223
transaction in order to align the VFD of the Production versions eventually linked to a
recipe/BOM assigned to the CM.
4. If other modifications are required, Quality assurance approver can move back the
Change no. status to “03”, so CM can be used again.
5. If a change must be rejected, Quality assurance approver must set the Valid from
date to 31.12.2099, so the change will never be considered by the system.
6. When Quality assurance approver decides to close the CM, can set the Change no.
status to “06”. In this case the CM cannot be used for any further change on relevant
objects.
423524079.doc Page 17 of 88
4. BUSINESS PROCESS FLOW CHART
423524079.doc Page 18 of 88
423524079.doc Page 19 of 88
5. SOLUTION
5.1 BILL OF MATERIAL
Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
UNITY-FSP- BOM structure: header CS01 001 MFG01-01_0010 X X X X
MFG-00-0010
A BoM is defined at plant level for a specific material code and consists of an CS02 002 MFG01-01_0020
header and an Item Master that can be displayed accessing CS03 by material
CS03 003 MFG01-01_0060
code.
004 MFG01-01_0070
The BoM header contains:
 Material Code; MFG01-01_0080
 Material Description; MFG01-01_0090
 Validity Period;
 Product reference quantity; MFG01-01_0110
 BoM usage;
CO01-08_0020
 BoM status;
 Alternative BoM Code;
 BOM Text (valid for all the alternative BOM for the semi-finished
and finished products);
 Alternative text (valid for the specific alternative BOM);
 Base Quantity: quantity which all component quantities in a BOM
refer to;
 From and To lot size.
The BOM Status available in the BOM header are:

 01 = Active, set when the BOM can be used for any purpose
within the validity date timeframe;
 02 = Inactive, set when the BOM cannot be used within the
validity date timeframe;
 03= Active with history requirements (default value).
The involved processes for each status are the following:
423524079.doc Page 20 of 88
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
The alternative BoM code is used in case the BoM for the material is not the
primary BoM, but one of the alternative ones (Multiple BoM).
UNITY-FSP- BOM structure: item master CS01 005 MFG01-01_0010

MFG-00-0020
The BoM Item Master can be accessed by transaction CS01/CS02/CS03 and it CS02 MFG01-01_0130
contains for each component:
CS03 QUA03-02_0110
 Component Code; CO01-08_0020
 Component Description;
 Quantity to be used (based on the quantity needed to produce the
semi-finished/finished product reference quantity);
 Unit of Measure;
 Material reference scrap for production process;
 Stock Item Category (stock managed and non-stock managed
materials).
 Item Category. This can either be:
o ‘L’ – Stock item (normal item);
o ‘D’ – Document item;
X X X X
o ‘N’ – Non stock item.
 Quantity of component required to make the base quantity of the

produced material (this base quantity will be maintained in the
“header overview screen”).
Note: purified water and nitrogen are managed as non-stock item into the Bill of
Materials for produced products (daily batch is created by quality department and
mandatory assigned on process order prior order release; for more details please
refer to [7]).
Additional information are available on each BOM item such as:

 Relevant for costing flag;
 Relevant for production flag (this flag should be set up for all
manufacturing BOM usage type);
 Component scrap.
UNITY-FSP- BOM components CS01 026 MFG01-01_0010 X X X X

MFG-00-0030
The BoM item master can contain the following kinds of component:
423524079.doc Page 21 of 88
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
CS02 MFG01-01_0040
 externally procured components – raw materials & packaging
components; CS03 CO01-08_0020
 externally procured components – “sub-assemblies”;
 internally produced components - "semi-finished products";
 internally produced components - "sub-assemblies";
 internally produced components - "assemblies" (CP, IH, PS);
 internally produced components - "serialized finished products" (in
case of re-work process);
 internally produced components - "finished products" (in case of re-
work process);
 Potency based components: Active ingredients are defined in the
BOM in alternative UoM (GAI or KAI) and the quantity is expressed
at 100% of the potency. Refer to line UNITY-FSP-MFG-00-0585 for
details.
UNITY-FSP- Component scrap CS01 MFG01-01_0010

MFG-00-0040
Component Scrap is handled in SAP through the Component Scrap Factor CS02 CO04-01_0240
(contained in the BOM item master). It is the percentage of scrap that should
CS03
occur on average during production of the material if the material is a component.
When exploding the bill of material (BOM), the system increases the required
quantities of the components by the calculated scrap quantity.
Example:
X X X X
Required quantity: 200 pieces;

Component scrap: 10%;
Scrap quantity: 20 pieces;
Therefore, 220 pieces are required.
The component scrap component is available through selecting a line for an item
(in the General item overview screen) and pressing the button “item”, the system
will open the “Item: all data” screen.
UNITY-FSP- BOM Creation by change request CS01 001 MFG01-01_0020 X X X X

MFG-00-0050
To create a BOM the authorized user has to access the CS01 with the material 006 MFG01-01_0030
code, plant, change number and BOM usage.
007 MFG01-01_0150
423524079.doc Page 22 of 88
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
008 MFG01-01_0160
Note: for the details of the change number request please refer of dedicated ECM
section of this document. MFG01-06_0010
SD01-03_0230
BOM usage can be one of the following:
BOM Usage Description

1 Production
2 Engineering/Design
5 Sales & Distribution
6 Costing
8 Validation
Note: values 1, 2, 6 are standard in SAP, while 8 is a customizing profile added for
Validation BOM. Validation BOM will be not used by Acist EU and BINJ EU.
During the access to the transaction, system verifies that the user is authorized to
perform the creation of the BoM.
UNITY-FSP- BOM Creation for copy CS01 MFG01-01_0030

MFG-00-0060
A BOM can be defined for copy of an existing BOM accessing the transaction CS01 MFG01-01_0100
with the material code, plant, BOM usage, change number and alternative to copy.
MFG01-01_0150
For that purpose use the dedicated button or F7.
MFG01-01_0160
Note: if an already existing BOM exists for the same Material/Plant/usage Type it is
not possible to use that functionality to copy a BOM from a different usage type. If MFG01-06_0010
X X X X
it is the case, an alternative way is to first enter the creation screen and to go in
the menu edit > extend. This alternative way is needed if the user wants to copy
from a different BOM header material while alternatives exist for the same material
header.
perform the creation of the BoM.
UNITY-FSP- Costing BOM CS01 001 CO04-01_0240 X X X X

MFG-00-0070
While a new production BOM is created, a new costing BOM exact copy of the CS03 006 CO01-08_0010
production BOM should be created in order to run cost calculation estimation.
007
423524079.doc Page 23 of 88
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
The creation of the costing BOM should be done only after approval of the
production BOM to avoid additional changes in case the QA approval requires a
modification to the BOM
Additional costing BOM for simulation purposes will be handled directly by the
controlling teams.
UNITY-FSP- BOM Migration LSMW C-001 MFG01-01_0140

MFG-00-0080 X X
System is able to automatically migrate valid Bill of Materials from Legacy Systems
to SAP, if required. For more details please refer to [8].
UNITY-FSP- BOM Manual Migration CS01 MFG0101_140_GS

MFG-00-0085 M
The usage of the PP-PI module to manage assembly and rework processes CS02
requires the creation from scratch of the relevant production master data as BOM. X X
CS03
BOM migration will be handled manually as cutover step to be executed by
authorized users only. Validation process will be granted by the ECM usage as
described into paragraph 3.1.6
UNITY-FSP- BOM Change (preferred) C202 009 MFG01-01_0030
MFG-00-0090 To apply changes to a BOM the authorized user has to access transaction C202, go
in the Material tab, click on the BOM button and apply all the desired changes to MFG01-01_0160
the BOM.
MFG01-06_0010
Note: The change number is automatically inherited by the recipe. CO01- X X X X
08_0011_GSM
perform changes on the BoM.
UNITY-FSP- BOM Change CS02 009 MFG01-01_0030 X X X X

MFG-00-0100
As an alternative, it is possible to change a BOM using transaction CS02. In this MFG01-01_0160
case, the authorized user has to insert in the initial screen the material code, plant,
MFG01-06_0010
change, BOM usage and change number4.
CO01-
Note: for the details of the change number management please refer of dedicated 08_0011_GSM
ECM section of this document.
4
The possibility of modifying a BoM without change number is blocked implementing “SAP Note 420878 - BOM change without change number possible (W 29 045)”
423524079.doc Page 24 of 88
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
perform changes on the BoM.
UNITY-FSP- BOM Deletion CS02 009 MFG01-01_0030

MFG-00-0110
To delete a BOM, the authorized user has to access CS02 transaction with the MFG01-01_0160
material code, plant, BOM usage and change number. Then user has to select
Material BOM  delete in the BOM header. It is only possible to delete one specific MFG01-06_0010
BOM at a time. Also in case of alternative BOMs, the authorized user can only
delete one alternative of a multiple BOM or one variant of a variant BOM at a time
selecting from the initial overview the BOM to delete and then proceed as in the
normal case.
delete the BoM.
If you delete the BOM with reference to a change number, the system takes the
valid-from data from the change master record as the deletion date and the BOM
is deleted on this date. X X X X
Note: You can only use a change number with a valid-from date within the validity
period of the BOM.
Example 1:
 BOM is created with the valid-from date 05/01/1997.
 The authorized user wants to delete the BOM with change number D1 .
The change master record has the valid-from date 01/01/1997 .
The authorized user cannot delete the BOM with change number D1, because the
BOM is not valid on 01/01/1997.
UNITY-FSP- Change documents attached to the BOM can be visualized through transaction CS80 MFG01-01_0120
MFG-00-0120 CS80 or directly though the Audit Trail functionality (transaction AUT10). X X X X
AUT10 MFG07-01_0020
For the details of the audit trail please refer to [6].
423524079.doc Page 25 of 88
423524079.doc Page 26 of 88
5.2 RESOURCES
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
UNITY-FSP- Resource creation CRC1 010 MFG01-02_0010 X X X X
MFG-00-0130 The resource represents the logical modeling of a transformation element for the C201 011 MFG01-02_0030
production process (e.g., production line, operating unit, work center, etc.) as well
as the related persons involved. C202 023 MFG01-02_0040
A resource is assigned to operations and phases in the master recipe (C201/C202)
COR1 024 MFG01-02_0050
and in process orders (COR1/COR2) to specify with whom or at which parts of the
plant a process step is carried out. COR2 025 MFG01-02_0060
During resource creation the following elements have to be specified: MFG01-02_0070

 a Resource Category (‘0008’ – Processing Unit (to be used for MFG01-02_0080
production lines), ‘Z008’ – Proc. unit (no cost) - to be used for
production activities in Mississippi that are not relevant for costing MFG01-02_0090
purposes);
 a default Resource Supply Area to manage the material replenishment CO04-01_0220
process; CO01-
 a Resource Usage (‘008’ – Master Recipe + Process Order); 08_0061_GSM
 a Resource Validity period;
 a Person Responsible for the resource;
 a Resource controlling area;
 a Cost Center.
Note: resource category ‘0008’ (costing relevant) is used for Ezem Montreal and
Acist; resource category ‘Z008’ (not costing relevant) is used for Ezem Mississippi
in order to not perform product costing calculation; for Acist EU and Binj EU both
resource categories ‘0008’ and ‘Z008’ are used, as mainly assembly processes are
managed used work centers represent assembly station.
The system allows the assignment of a standard value key in order to define
standard values to be maintained, at master recipe level, for operations assigned
to the specific resource.
Only one standard value key is defined into the system:

 Z001 (Normal Production SVK).
To this value key are associated the following parameters:

 ZMAC_F for fixed machine time;
423524079.doc Page 27 of 88
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
 ZLAB_F for fixed labor time;
 ZMAC_V for variable machine time;
 ZLAB V for variable labor time;
 ZQC_V for QC laboratory time (variable).
For the standard values is activated the possibility to define the yield factor at
operation level in the master recipe.
perform the creation of the resource.
UNITY-FSP- Resource creation for copy CRC1 MFG01-02_0010

MFG-00-0140 It is possible to create a resource using an existing resource as a model (field copy MFG01-02_0020
from resource in the Initial screen). The authorized user has to insert the plant for
which create the resource, the reference resource and the resource category.
Then user has to choose in the list offered by the system the data to be copied
from the reference resource to the new one and click on to continue.
X X X X
perform the creation of the resource.
UNITY-FSP- Creation of a resource is traced in the system. A report can be accessed using CR10 MFG01-02_0020 X X X X
MFG-00-0150 transaction CR10.
Selection parameter in the initial screen are: MFG01-02_0030
423524079.doc Page 28 of 88
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
 Plant;
 Resource (work center) name;
 Resource (work center) category;
 Person responsible;
 From-to date.
UNITY-FSP- It is possible to find the where-used list of a resource. This report will be run using CA81 MFG01-02_0020
MFG-00-0160 selection criteria such as resource code and plant. The system gives information X X X X
about master recipe in which the resource code is used. MFG01-02_0030
UNITY-FSP- In Costing tab of the resource, a cost center must be assigned in order to CRC1 MFG01-02_0080
MFG-00-0170 associate Activity Type with a Cost rate.
CRC2 CO01- X X X X
08_0061_GSM
UNITY-FSP- Accessing the CR05 transaction with the plant code it is possible to view the list of CR05 MFG01-02_0020
X X X X
MFG-00-0180 all the resources created for the given plant.
UNITY-FSP- Resource deletion CRC2 MFG01-02_0010

MFG-00-0190 A resource can be deleted pressing the “Delete work center” button in ‘Basic data’
view of the CRC2 transaction. If the resource is still in use, an error message will X X X X
be shown and the resource cannot be deleted.
Deletion flag can be set choosing Extras->Status->Deletion flag.
423524079.doc Page 29 of 88
5.3 MASTER RECIPE

SMC/BINJEU
Acist Asia
Acist US
Acist EU
Ezem
BDI
UNITY-FSP- Master Recipe creation C201 012 MFG01-03_0020 X X X X
MFG-00-0200 Master recipe represents a sequence of operations each of them representing a 013 MFG01-03_0030
step required actually to produce semi-finished products, finished products, sub-
assemblies, assemblies and devices. MFG01-03_0130
MFG01-03_0140
A recipe can be created accessing C201 transaction and inserting recipe group, or
material and plant and the change request number. MFG01-03_0150
Note: for the details of the change number request please refer of dedicated ECM MFG01-03_0160
section of this document.
MFG01-03_0180
Each recipe is defined at Plant level. MFG01-03_0290
When creating a recipe, the authorized user has to insert at least the following MFG01-06_0010
information in the recipe header:
 Master Recipe description;
 Master Recipe Usage (e.g., Production, Engineering, Costing);
 Master Recipe group;
 Master Recipe validity period;
 Product code;
 Product Reference quantity (product quantity from which needed
component quantities are calculated).
For each processing operation, user can define:
 A resource, representing the area where the operation takes place;

 Alternative productions line that can process an operation in place of a
defined one;
 The list of the In Process controls to be executed during the operation
 Labor and machine standard times that are required to produce a
defined quantity of the product.
423524079.doc Page 30 of 88
SMC/BINJEU
Acist Asia
Acist US
Acist EU
Ezem
BDI
perform the creation of the recipe.
UNITY-FSP- Master Recipe creation for copy C201 MFG01-03_0020
MFG-00-0210 As an alternative to normal process flow, the authorized user can decide to create MFG01-03_0050
a new recipe by duplicating an existing one in the system. Also in this case the
authorized user has to specify the change number in order to start the creation MFG01-03_0110
process.
MFG01-03_0190
Duplication of a recipe means that destination recipe shall inherit all the attributes
of the source recipe. However, it is possible to assign a copied recipe to a different MFG01-03_0200
product code. X X X X
Specifically, by duplicating a recipe, the authorized user assigns to the destination MFG01-03_0210
recipe the header data and the item data taken from the source one. MFG01-03_0220
However, it is possible for the authorized user to apply changes to the originally
item data inserting a new operation/phase, deleting an existing one, etc. MFG01-03_0290
During the access to the transaction, system verifies that the user is authorized to MFG01-06_0010
perform the creation of the recipe.
UNITY-FSP- Master Recipe status C201 012 MFG01-03_0020

MFG-00-0220
System manages status key for master recipes to indicate the processing status of C202 014
a task list. For example, recipe status can indicate whether the task list is still in
the creation phase or has already been released. Available status for the recipe in
the system are the following:
X X X X
When a recipe is created the status is set as “1”, once it is ready to be used for
production activities it is set as “4”.
Note: status “2” and “3” are mentioned since they are possible entries from
standard SAP, however, they are not planned to be used.
423524079.doc Page 31 of 88
SMC/BINJEU
Acist Asia
Acist US
Acist EU
Ezem
BDI
UNITY-FSP- If no code is filled in the Recipe group field in the initial screen, when the Recipe is C201 022 MFG01-03_0020
MFG-00-0230 saved the system automatically assigns an internal number to the Recipe.
Nevertheless, this functionality is not used for engineering/validation and

production usage type since creation is to be done with change numbers. Objects
to be changed have to be inserted in the change number prior to creation, i.e.
naming has to be settled beforehand.
The following number ranges are configured in the system for internal and
external master recipe group assignment:
 Internal number range

o From 50000001 to 99999999
 External number range X X X X

o From AAAAAAAA to ZZZZZZZZ
The master recipe naming convention, managed by SOP, is as follows:
 Ezem Canada  from EC500001 to EC999999

 Ezem Mississippi  from EM500001 to EM999999
 Acist US  from AU500001 to AU999999
 Acist EU  from AE500001 to AE999999
 SMC/BINJEU  from BE500001 to BE999999
It is recommended to add in the recipe description the material number to which it

is linked. Nevertheless, it is up to the local master data team to take the finale
decision.
UNITY-FSP- Master Recipe Migration LSMW C-002 MFG01-03_0280

MFG-00-0235 X X
System is able to automatically migrate valid Master Recipes from Legacy Systems
to SAP, if required. For more details please refer to [9].
UNITY-FSP- Master Recipe Manual Migration C201 MFG01- X X
MFG-00-0237 03_0280_GSM
The usage of the PP-PI module to manage assembly and rework process requires
the creation from scratch of the relevant production master data as Recipes.
Recipe migration will be handled manually as cutover step to be executed by
authorized users only. Validation process will be granted by the ECM usage as
423524079.doc Page 32 of 88
SMC/BINJEU
Acist Asia
Acist US
Acist EU
Ezem
BDI
described into paragraph 3.1.6
In combination with the recipe also the Production version are created.
UNITY-FSP- Master Recipe structure: header C203 012 MFG01-03_0010

MFG-00-0240
A recipe is defined at plant level and consists of an header and an Item Master 015 MFG01-03_0030
that can be displayed accessing C203 transaction.
MFG01-03_0130
The recipe header data, contains at least the following header information: MFG01-03_0140
MFG01-03_0150
 Master Recipe description;
CO01-08_0050
 Master Recipe Usage (e.g., Production);
 Master Recipe group;
 Master Recipe validity period;
X X X X
 Product code;
 Product Reference quantity (product quantity from which needed
component quantities are calculated).
Master Recipe usage can be one of the following:
Recipe Description
Usage
1 Production
2 Engineering/Design
7 Costing
8 Validation
UNITY-FSP- Master Recipe structure: item master C201 016 MFG01-03_0010 X X X X

MFG-00-0250
C202 MFG01-03_0060
Item master contains the Operations, identified by a unique and sequential code
C203 MFG01-03_0070
ID into the recipe, associated to the recipe. It is possible to define different kinds
of recipes for different kinds of processes (e.g., rework, validation, clinical, MFG01-03_0080
engineering) simply setting type and sequence of operations/phases contained in
the recipe item master. MFG01-03_0090
MFG01-03_0120
Operations can be actual processing steps (e.g., Burn-in Testing, Assembly
423524079.doc Page 33 of 88
SMC/BINJEU
Acist Asia
Acist US
Acist EU
Ezem
BDI
Packing, etc.), preparatory steps (e.g., pre-printed materials preparation, etc.) or MFG01-03_0230
steps executed after actual processing (e.g., quality controls).
In the recipe is defined the sequencing of the operations to be executed during

the production process and the belonging sections and phases. Each phase is also
identified by a unique and sequential code ID into the recipe (directly linked to the
operation ID).
UNITY-FSP- The authorized user can define the following information within Master Recipe C201 010 MFG01-02_0050
MFG-00-0260 Item:
C202 011 MFG01-03_0160
 Operation Code;
C203 017 MFG01-03_0180
 Section Code;
 Phase Code;
 Resource (defined at operation level);
 Control Key (defined at phase level to manage relevancy for planning,
costing and confirmation); X X X X
 Labour and Machine standard times.
Labour and Machine standard times are defined at phase level and only for
confirmation-relevant phases to manage time declaration reconciliation process.
Authorized user has to define default values and activity types to manage Labour
and Machine time reconciliation according to the related settings of the resource
assigned to the operation.
Note: it is possible to define alternative resources, at operation level, for a specific
Master Recipe.
UNITY-FSP- Association phases – resources C201 010 MFG01-02_0050 X X X X

MFG-00-0270
Each phase has to be associated to a resource. Each resource is associated to a C202 011
standard value key.
C203
Only one standard value key is defined into the system:
 Z001 (Normal Production SVK).
To this value key are associated the following parameters:

 ZMAC_F for fixed machine time;
423524079.doc Page 34 of 88
SMC/BINJEU
Acist Asia
Acist US
Acist EU
Ezem
BDI
 ZLAB_F for fixed labor time;
 ZMAC_V for variable machine time;
 ZLAB V for variable labor time;
 ZQC_V for QC laboratory time (variable).
Please refer to resource master section of this document for more details.
For Acist EU and BINJ EU Machine times are not relevant as assembly and repair
processes require mainly labour time
UNITY-FSP- In the General Data tab the authorized user has to insert the operations, phases, C201 017 MFG01-03_0160
MFG-00-0280 resources and control keys as required.
C202
Five control keys have been identified so far:
 ZP01: Allows scheduling, Cost, confirmation possible but not necessary;

 ZP02: Allows scheduling, Cost, confirmation milestone;
 ZP03: Allows scheduling, Cost, inspection characteristic required, X X X X
confirmation possible but not necessary;
 ZP04: Allows scheduling, but not relevant for costing;
 ZP05: Allows scheduling, confirmation milestone, not relevant for
costing.
The milestone confirmation warrantees that any previous phases to be confirmed

will be confirmed as standard.
UNITY-FSP- To be able to schedule the recipe, plan capacities, enable confirmation by C201 016 MFG01-03_0100 X X X X
MFG-00-0290 milestone, relationships that determine how phases relate to each other in terms
of time are entered, selecting the phases in Operations tab and pushing C202
Relationships button.
Indicator Predecessor/Successor is used to specify how the authorized user
defines the relationship of a phase record to other phases.
The type of relation is the key used to determine the type of relationship between
phases. The following are allowed:
SF = Start to Finish;
SS = Start to Start;
FS = Finish to Start (Usual default);
FF = Finish to Finish.
423524079.doc Page 35 of 88
SMC/BINJEU
Acist Asia
Acist US
Acist EU
Ezem
BDI
Furthermore, user can define sections within an Operation such as:
 Set-up (preparation for production activity);
 Run (actual production activity);
 Closure (closure for production activity).
UNITY-FSP- BOM allocation / Production version C201 MFG01-01_0050

MFG-00-0300
Pre-requisites: C202 MFG01-03_0040
 BOM has been created independently from the master recipe;
 a material has been assigned to the recipe, in Recipe header tab 
material assignment button.
To allocate the BOM to the recipe the following actions are carried out in the
system:
1. The tab “Materials” is selected. If more than one material is assigned to
the recipe, the authorized user has to select the correct one. X X X X
2. The system displays the Production Version creation screen; the
following data need to be filled:
o Production version code and description;

o Alternative BOM and BOM usage for the BOM to be allocated
to the recipe that is being created.
The system will load automatically the BOM that has been indicated and it will be
possible to assign each component of this BOM at the phase where it will be
consumed, by selecting the material and pressing the Create assignment button.
UNITY-FSP- Operation Quality Data: C201 017 MFG01-03_0260 X X X

MFG-00-0310
To enable the execution of the IPC, the authorized user has to reference in the C202
Operation folder of the recipe, the parameter for the Inspection Point completion
with the push button QM Data for the Operation. Then, he has to set the
value “Automatic valuation based on Inspection Point definition” for the parameter
Inspection Point Completion.
Note: in order to assign IPC to one operation, it is required to configure on Control

Key with value Insp. Char. Required flagged (control key ZP03).
For Acist EU and BINJ EU the functionality is marked as applicable (as covered by
standard SAP) even if for current business scenario IPC execution is not requested
423524079.doc Page 36 of 88
SMC/BINJEU
Acist Asia
Acist US
Acist EU
Ezem
BDI
during assembly/repair processes.
UNITY-FSP- Inspection Characteristic: C201 MFG01-03_0250
MFG-00-0320
System associates at the operation an In-Process Control (IPC) master file C202 MFG01-03_0260
containing the following information: C203 MFG01-03_0270
 Master Inspection Characteristic (MIC) Code;
 Master Inspection Characteristic Description;
 Master Inspection Characteristic Type (IPC Qualitative or Quantitative).
X X X
In the Operation folder of the recipe, when a master recipe is created user can
insert
or display the IPC information in the production operations with the push button
Inspection Characteristic.
UNITY-FSP- Characteristic Overview Description C201 MFG01-03_0260

MFG-00-0330
When the Inspection Characteristic has been selected, the system shall open the C202
Characteristic Overview screen and the following header information are shown:
C203
 Recipe Group;
 Recipe Number;
 Recipe Description;
 Plant;
 Plant Description;
 Operation Number; X X X
 Phase Description.
Each MIC must be inserted in a row. Each Row is uniquely identified with the
number Inspection Characteristic number: it explicitly identifies an inspection
characteristic within an operation.
423524079.doc Page 37 of 88
SMC/BINJEU
Acist Asia
Acist US
Acist EU
Ezem
BDI
UNITY-FSP- Material assignment C201 MFG01-03_0240
MFG-00-0340
Material assignment consists in assigning BoM materials to specific C202
phases/operations. To perform material assignment, the authorized user has to X X X X
access the C201/C202 transaction and to select the material/s to assign to the
phases and the subordination relationship between phases and operations in the
Material tab.
UNITY-FSP- Backflush setting at phase level C201 MFG01-03_0170

MFG-00-0350 It is possible to set backflushing indicator at phase level in order to trigger C202
backflush at operation confirmation for all components associated to the specific
phase. This setting is defined in Materials tab, while selecting a component the
‘Material component assignment’ tab is opened; “Backflush” indicator can be X X X X
flagged if relevant.
If a material component is backflushed, the system posts the withdrawal
automatically with the standard consumption set in the process order material list
upon confirmation of the operation/phase to which the component is linked.
UNITY-FSP- Master Recipe change C202 MFG01-03_0020

MFG-00-0360
Authorized user can apply changes to an existing recipe accessing C202 MFG01-03_0050
transaction and inserting recipe group, or material and plant and the change
request number. MFG01-03_0110
MFG01-03_0290
Note: for the details of the change number request please refer of dedicated ECM
section of this document. X X X X
Accessing a recipe in change modality, the authorized user can insert a new
operation/phase, deleting an existing one, modify header data, modify material
assignment, etc.
Note: During the access to the transaction, system verifies that the user is
authorized to perform changes on the recipe.
UNITY-FSP- Master Recipe deletion C202 MFG01-03_0020 X X X X
MFG-00-0370
Authorized user can also delete a recipe. In this case, he has to set the deletion MFG01-03_0290
indicator in the master recipe header. When this indicator is selected the recipe
cannot longer be used for production activities.
423524079.doc Page 38 of 88
SMC/BINJEU
Acist Asia
Acist US
Acist EU
Ezem
BDI
Note: During the access to the transaction, system verifies that the user is
authorized to perform changes on the recipe.
UNITY-FSP- Master Recipe validity date C202 MFG01-06_0130

MFG-00-0380 X X X X
Only Master recipes whose change number validity date has been reached and C203
whose status is ”4” (i.e., released) can be used in production activities.
UNITY-FSP- Costing recipe C201 012 CO04-01_0220

MFG-00-0390
The Costing Recipe is set to calculate the standard cost of the product. Since 015 CO01-08_0040
standard cost is reviewed every year, the costing Recipe is frozen while standard
CO01-
cost is validated for the current year. Therefore no update of costing Recipe is
08_0051_GSM
needed until next year cost calculation exercise.
X X X X
For BINJ EU the need to manage recipe having operation not relevant for costing
purposes arises from the need to manage the specific scenario where assembly
activities for Empower and CT-Express (under the ownership of BINJ EU and
created under the plant SM01) are performed from ACIST EU technicians. In this
specific case the business requirement is to track just the actual labor hour spent
for the order completion, without post any cost in accounting. As a result, also in
the standard cost calculation of the manufactured material involved in this process
flow, labor hours costs must not be considered.
423524079.doc Page 39 of 88
5.4 PRODUCTION VERSION

SMC/BINJ EU
Acist Asia
Acist EU
Acist US
Ezem
BDI
UNITY-FSP- Production Version structure C201 MFG01-01_0050
MFG-00-0400 The Production Version is the object that references a unique combination of a
C202 MFG01-03_0040
material list (BoM) and a recipe for the production of a material on a key date.
MFG01-04_0010
It is defined at plant level and it is logically created at the act of linking a BoM to a
MFG01-04_0020
Master Recipe.
CO01-
User shall be able to define one or more Production Versions for each material that 08_0081_GSM
is produced internally. The following information associated to one Production
Version are managed into the system:
 Plant;
 Material Code;
 Production Version (four-character field representing the Production X X X X
Version, and its description);
 The Lock flag (two options available: “Not Locked” and “Locked for any
usage”. By default, the flag is set to “Not Locked”. This flag will be used to
block any production versions that are not ready to be used in production
execution or must no longer be used in production);
 Lot size range;
 Validity period for the PV (valid from and valid to date);
 Task list type: “Master recipe” = 2;
 Recipe group and counter;
 Alternative BOM and BOM usage;
 Change number assignment.
Note: only specific users are authorized to lock a production version to avoid its use
in production.
UNITY-FSP- A production version is unique for the following combination: C201 MFG01-04_0020 X X X X
MFG-00-0410 Material Code/ Plant/ Production Version Code. Therefore, a product version is
created for a dedicated plant. C202 MFG01-04_0050
C223 MFG01-04_0060
It is possible to create a production version from transaction code C223 or
C201/C202. In order to limit the number of transaction in the system, it is MFG01-04_0070
recommended to create a production version using the Recipe transactions
C201/C202 while no production version/”usage type” exists for the material.
423524079.doc Page 40 of 88
SMC/BINJ EU
Acist Asia
Acist EU
Acist US
Ezem
BDI
Otherwise, the Production Version should be created using C223 transaction.
UNITY-FSP- Production Version created for copy/duplication C223 MFG01-04_0030
MFG-00-0420
The Production Version can also be created for copy of an existing one. In this case MFG01-04_0040
the authorized user has to access the C223 transaction, selecting a plant to see all
the available production versions, select the one to copy, and then click on the copy X X X X
button. The system will ask to the user a code for the new production version. It is
also possible to assign a different product code to the new production version
created for copy.
UNITY-FSP- Change Production Version C201 MFG01-04_0070

MFG-00-0430
To change a production version, the authorized user has to access the C202 C202 CO01-
transaction with the details of the recipe. Then, in the Materials tab the user has to 08_0081_GSM
click on the production version to open the Production Version view. C203
In the Production version group box, the authorized user has to choose the fields to
modify (for example, its validity period). X X X X
Once the production version has been created, the authorized user can no longer
change the production version key or its BOM assignment.
However, it is possible to lock a production version to set the corresponding entry in

the Lock field.
UNITY-FSP- Check Production Version C201 MFG01-04_0010 X X X X

MFG-00-0440
Check of production version is used to check whether the data of a production C202
version is consistent with the data of the assigned master recipes and the assigned C203
alternative BOM. In this way, you make sure that a valid task list or valid BOM really
exists for the entire validity period of the production version.
To check the status of a Production Version, the authorized user has to access the
C201/C202/C203 transaction with the details of the recipe. Then, in the Materials
tab the user has to click on the production version to open the Production Version
view.
The consistency check determines a check status for the objects

assigned (recipe or BOM). All change statuses within the validity
period of the production version are taken into account. Warning
423524079.doc Page 41 of 88
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
and error messages about inconsistencies are displayed in the
check result. The check status for each object is displayed as an
icon in the production version. The following icons may be
displayed:
Check Meaning Possible Reasons

Status
Error  The object does not continuously

exist throughout the entire validity
period of the production version.
 The lot-size range of the object

does not comprise the entire lot-
size range of the production
version.
Warning  No check was carried out for the

object.
 The deletion flag is set for the

object.
 The header material of the

production version is not assigned
to the task list/recipe.
O.K.  None of the above inconsistencies

occurred.
423524079.doc Page 42 of 88
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
At the production version level, the check status is summarized as follows:
 If no master recipe or alternative BOM is assigned to the production

version, the yellow traffic-light is displayed;
 Otherwise a red traffic-light is displayed whenever a red traffic-light exists

at the object level.
UNITY-FSP- Display production Version C202 MFG01-04_0010

MFG-00-0450
To display the details of the production version used the authorized user has to C203 CO01-08_0090
access the C202/C203 transaction with the details of the recipe. Then, in the X X X X
Materials tab the user has to click on the production version to open the Production
Version view.
UNITY-FSP- Production version statuses C223 MFG01-04_0010

MFG-00-0460
The Production Version Status available are: MFG01-04_0070
 “Not Locked”, set when the Production Version can be used within the
validity date timeframe;
 “Locked for any usage”, set when the Production version cannot be used
within the validity date timeframe;
X X X X
Bringing together the “Production Version Lock status” with “valid from” and “valid
to dates”, we may have additional intended status like:
 In process: status “active” + from date “future” + to date “∞”, means

Production Version is not available and cannot be processed;
 Refurbish: status “active” + from date “past” + to date “today”, means

Production Version is not available and cannot be processed.
UNITY-FSP- Naming convention C223 MFG01-04_0010 X X X X

MFG-00-0470
The naming convention for production version is:
423524079.doc Page 43 of 88
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
 PXXX where XXX is the revision version of the normal internal production
version;
 VXXX where XXX is the revision version of the validation production

version;
 EXXX where XXX is the revision version of the engineering production

version;
 CXXX where XXX is the revision version of the clinical production version;
 RXXX where XXX is the revision version of the rework production version.
“XXX” is a manual counter from 001 to 999.

For Acist EU and BINJ EU only Normal Internal production and Rework production
will be in scope.
UNITY-FSP- Production Version are defined in SAP with a specific range “From lot size” “To Lot C201 MFG01-04_0010
MFG-00-0480 size”. This is relative to the possible batch size. In SAP, a production version will be
created per batch size ranges if necessary. C202 X X X X
C223
UNITY-FSP- It is possible to have multiple Production Versions ‘not locked’ at the same time and C223 MFG01-04_0010
MFG-00-0490 coexisting in the system.
X X X X
The system allows creation of different Production versions valid at the same time,
each of them having alternative bill of materials or/and different recipe.
423524079.doc Page 44 of 88
5.5 MATERIAL MASTER VIEW
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
UNITY-FSP- Material Master: general features MM01 MFG01-05_0020
MFG-00-0500 Material Master contains the information related to all the materials involved in the MM02
production process. Materials are classified in Material Master by type.
It is possible to define all the information related to the production process MM03
accessing into the material master the views managed by manufacturing X X X X
department: Work Scheduling and MRP views.
For more details on material master data, please refer to Master Data Functional
Specification.
UNITY-FSP- Material Master: Procurement details (MRP2 view) MM01 MFG01-05_0010
MFG-00-0510
In the MRP2 view of the material master it is possible to set the following fields: MM02
 Procurement type: it specifies whether the material has to be produced
in house (E) or to be procured outside (F) or both (X);
 Prod. Stor. location: the default storage location where produced goods X X X X
will be posted during the Goods Receipt from Production;
 Storage Loc. for EP: the first storage location for materials bought
outside (external procurement);
 Special Procurement: it explains in more details what kind of
procurement the material has to undergo (e.g., Subcontracting).
UNITY-FSP- Materials managed using backflush (MRP2 view) MM01 MFG01-05_0120 X X X X

MFG-00-0520
In the MRP2 view of the material master it is possible to set whether a material MM02
has to be managed using backflushing or not. The authorized user in this case has
to access the MRP 2 view of the material master (COR1, COR2), and to fill the
Backflush field with the opportune value. The possible choices are:
Backflush Description
01 Always backflush
02
Workcenter decides whether to
423524079.doc Page 45 of 88
backflush.
Always backflush means that the material is always managed for backflushing
consumption on all the process orders where the material is used.
UNITY-FSP- Batch determination (MRP2 view) MM01 MFG01-05_0040

MFG-00-0530
In the MRP2 view in the Batch Entry field it is possible to define at which level of MM02
the production process batches have to be determined. The authorized user has
the following options:
Batch Entry Description
1 The batches must be entered
in the order before it is
released.
2
The batches must be entered
in the order before the goods
issue is posted, but not
necessarily before the order is
released.
3 The batches are determined
automatically when the order X X X X
is released.
If no value for this field is entered by the authorized user, the system assumes by
default that the batches can be determined when the goods issue is posted (lot
allocation not required at Process Order level).
Note: Batch entry indicator refers to the components of an order, not to the
finished product to be manufactured.
For Ezem value “3” is used for all materials, except for potency-based
components, purified water and nitrogen which has to be set with value “1”.
For Acist value “2” is used for all materials to be replenished in production area.
For Acist EU and BINJ EU the batch entry field will be left blank as BOM
components for assembly/repair process are mainly S/N SKUs. The option will be
still available for spare parts used in repair process in case
For the details of how this field is managed at Inventory level, please refer to [2].
UNITY-FSP- Material Master: Work scheduling view MM01 018 MFG01-05_0090 X X X X

MFG-00-0540
In the Work scheduling view of the Material Master the authorized user can define MM02 MFG01-05_0100
423524079.doc Page 46 of 88
the production scheduling profile that has to be used for the material. The MFG01-05_0110
scheduling profile is used to manage specific rules for:
 material replenishment at process order release;
 manual process order release;
 bundle of documents generation;
 batch master and classification generation at process order release;
 process order type to use at process order creation.
Three scheduling profile has been defined:
 ZACAUT: for Automatic Batch Creation (at Order Release) in ACIST US;
 ZEZAUT: for Automatic Batch Creation (at Order Release) in Ezem;
 ZEZMAN: for Manual Batch Creation in Ezem/Binj EU/Acist EU.
Note: the production scheduling profile is then automatically copied by the system
into the order during order creation.
Note: Production schedule profile ZEZMAN is intended be used both in Acist EU

and Binj EU for batch managed configured injector is order to enable the external
batch assignment. It will allow to manually declare the batch number equal to the
serial number of the not configured injector listed into the bill of material but not
allocated on the order.
In the Tolerance Data tab of Work scheduling view it is also possible to:
 define goods receipt underdelivery/overdelivery tolerances for produced

goods (for more details on this process, please refer to [3]);
 Define whether a material has to be serial number managed (for more

details on this point, please refer to [4]).
UNITY-FSP- Critical Parts MM01 MFG01-05_0020

MFG-00-0550
In the Material Master the authorized user can define if a material has to be MM02 X X X
considered as critical during the assembly process. In this case, the authorized
user has to flag the Critical Part Item in the Work scheduling view of the material .
423524079.doc Page 47 of 88
UNITY-FSP- Availability check settings MM01 MFG01-05_0080

MFG-00-0560
In the MRP 3 view of the Material Master the authorized user can define the MM02
specific rule to follow for checking the stock availability at Process Order Creation X X X X
and Process Order Release based on specific stock status. It specifies whether and
how the system checks availability and generates requirements for materials
planning.
UNITY-FSP- Lot size data MM01 MFG01-05_0030

MFG-00-0570 This tab contains all the data related to the specific lot size to consider for MM02
produced goods and its related reference values (target value, minimum lot size,
maximum lot size, rounding value).
Lot size can be set as:
 fixed; X X X X
 variable with rounding value;

 variable without rounding value.
Rounding value is the value to a multiple of which the system rounds up the
procurement quantity. For more details on it please refer to [5].
UNITY-FSP- Batch/Lot managed materials MM01 MFG01-05_0090

MFG-00-0580
For material batch/lot managed the correspondent field into the Purchasing view MM02
X X X X
of the material master has to be flagged.
For more details on this point please refer to [5].
UNITY-FSP- Potency based materials MM01 026 MFG01-05_0050 X

MFG-00-0585
For material potency based, in the Basic data view of the Material Master  MM02 MFG01-05_0060
Additional data  Unit of measure TAB, the authorized user can define the
alternative unit of measure for the potency (KAI or GAI) and the related
conversion factor with the basic unit of measure (‘1:1’)
Where:
 KAI is Kilograms for Active ingredient for material codes with basic unit
of measure KG
 GAI is grams for Active ingredient for material codes with basic unit of
measure G
423524079.doc Page 48 of 88
In the Basic data view of the Material Master  Additional data 

Proportion/Prod.Unit TAB, the authorized user can define the average (nominal)
potency percentage for the material.
In particular, the authorized user enters for the characteristic POTENCY, the
average (nominal) potency percentage in the field Plan Value and clicks on the
field LUM (Leading batch-specific unit of measure) in order to enable the system
to consider the variance between the average actual proportion of Active
ingredient in stock and the planned proportion.
423524079.doc Page 49 of 88
5.6 ENGINEERING CHANGE MANAGEMENT

SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
UNITY-FSP- Change Master CC01 019 MFG01-06_0030 X X X X
MFG-00-0590
Change Master document management is composed by two subprocesses: 020 MFG01-06_0040
 Change Number Creation; MFG01-06_0100
 Change Number Release (Closure). MFG01-06_0110
Note: The approval process is not mentioned since it is managed outside SAP (in
Trackwise for Ezem, through paper-based process in Acist).
Authorized users are able to create/modify master data objects managed with
Change Master document management process only using created, and not
closed, Change Numbers.
The following information for a Change Master are maintained into the system:
 Validity Date;
 Change Document Profile (which is the plant in charge of the change);
 Reason for change (contains a link to the Change Request number);
 Master Data Objects linked to the Change Document;
 Change Request Status.
Following Change Master Profiles are defined into the system to segregate master
data activities at the different locations:
 ZMD001 - Change Master Record Profile – Ezem
 ZMD002 - Change Master Record Profile -– Acist US
 ZMD004 – Change Master Record Profile – Acist EU
 ZMD005 – Change Master Record Profile – SMC/Binj EU
423524079.doc Page 50 of 88
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
Note: Only authorized users are able to modify Change Number validity date.
UNITY-FSP- Change Number Creation CC01 021 MFG01-06_0010

MFG-00-0600 When a validation, engineering or production master recipe, bill of material, MFG01-06_0020
production version must be created or changed in the system, a formal change
request (process outside SAP) starts the process, and when the change request MFG01-06_0030
has been approved the QA responsible can create the Change Master in SAP.
MFG01-06_0060
Change Master is the object that contains all the information required for
managing a change. Change number is the code assigned by the system to this MFG01-06_0070
object which is identified by a unique ID. X X X X
MFG01-06_0090
Only authorized users have the authorization to create a CM and they can obtain
change numbers for creating/changing only Master Data related to their specific
plant.
In case of multiple plants across the same company code, the authorized user
(only if authorized to perform the action) can obtain change numbers for
creating/changing only Master Data related to their specific plant.
UNITY-FSP- When a Change master has to be created, QA enters in transaction CC01 and fills CC01 019 MFG01-06_0080 X X X X
MFG-00-0610 the field Profile with the correct value assigned by procedure to him. This profile
will drive default values for: 020
 Change no. status (initial value);

 Authorization group;
 Object types that can be processed with the CM.
Note: Fields Authorization group and Change no. status are automatically filled
according to the Profile inserted in the initial screen. In particular, the
Authorization group depends on the plant (“0010” for Ezem, “0020” for Acist US,
“0040” for Acist EU and “0050” for SMC/BINJ EU), while the initial Change no.
status will be “03” (ECM in progress).
Following Change Master Profiles are defined into the system to segregate master
data activities at the different locations:
 ZMD001 - Change Master Record Profile – Ezem
423524079.doc Page 51 of 88
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
 ZMD002 - Change Master Record Profile -– Acist US
 ZMD004 - Change Master Record Profile – Acist EU
 ZMD005 – Change Master Record Profile – SMC/Binj EU
In the Change header screen user must enter the following information:
 Change number description (40 digits);
 Valid from date, to indicate the date from which the changes will be
valid;
 Reason for change, general information about the reason of the
modification (40 digits, not mandatory).
UNITY-FSP- In order to assign specific master data objects which must be changed with a CM, CC01 MFG01-06_0010
MFG-00-0620 the authorized user has to push the button Objects and enter in the appropriate
tabs the reference to the master data.
Depending on the object to create/modify, user has to enter the following data:
 Master recipe – tab “TL”

o Task list type = 2 (master recipe);
o Group (recipe name); X X X X
o Description (not mandatory).
 BOM – tab “Mat. BOM”

o Material number;
o Plant;
o BOM usage;
o Description (not mandatory).
UNITY-FSP- Change Master modification CC02

MFG01-06_0060
MFG-00-0630 X X X X
If other master data must be added to a CM already created, user can enter in
MFG01-06_0090
CC02 transaction in order to add them.
UNITY-FSP- Lock master data objects CC01 MFG01-06_0020 X X X X

MFG-00-0640
If an object in the CM must not be changed anymore with reference to that CC02 MFG01-06_0030
423524079.doc Page 52 of 88
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
change number, then user can enter in the Objects screen and set, for the
relevant object(s), the indicator “Lock”.
In this way, a master data for which that indicator is active cannot be changed
using that specific change number.
UNITY-FSP- Change number status CC01 019 MFG01-06_0080

MFG-00-0650
The following Change no. status are available in the system: CC02
Change no. Description

status
03 ECM in progress
04
Pending QA approval X X X X
05 Approved by QA
06 ECM closed
When the authorized user has performed all the required changes in the system,
he can enter in transaction CC02 and change the Change no. status from ‘01’ to
‘02’. With this status, user is not allowed to change the master data. Also the Valid
from date cannot longer be changed.
UNITY-FSP- QA can inquiry all the CMs with status “04” in order to verify if the change can be CC02 019 MFG01-06_0080
MFG-00-0660 approved or not.
C223
In transaction CC02, user can open the match code, select Change master by
description and change type and filter for Change no. status = “04”.
If a CM can be approved, QA can then set the Change no. status to “05”. With this
status, user is not allowed to change the master data, but Valid from date field X X X X
can be changed: QA will set it to the real one, in order to activate the change.
Note: Only QA is authorized to change a CM with status “05”.
If required, QA can also access to C223 transaction in order to set the real Valid
from date for a Production version linked to a recipe/BOM assigned to the CM.
423524079.doc Page 53 of 88
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
UNITY-FSP- If a CM cannot be approved because modifications are required, then QA has to CC02 019 MFG01-06_0080
MFG-00-0670 move the Change no. status from “04” to “03” in order to enable the Functional
Data Expert to use it again. MFG01-06_0130
If a change must be rejected, then QA will have to:

X X X X
1. move the Change no. status to “05” in order to be able to change the
VFD;
2. move the Valid from date to “31.12.2099”;
3. move the Change no. status to “06” in order to close the CM.
UNITY-FSP- Change Master closure CC02 019 MFG01-06_0030

MF-00-0680
In case changes become obsolete, authorized users can close related Change MFG01-06_0120
Number to avoid its usage in production activities. When QA decides to close a
CM, they can access to CC02 transaction and move the Change no. status from X X X X
“05” to “06”. When the CM is in this status (ECM closed), it cannot be used to
change the master data associated to it. Also the Valid from date cannot be
changed.
UNITY-FSP- Display Change Master CC03 MFG01-06_0030

MFG-00-0690
Change master contains the history of master data changes linked to a specific MFG01-06_0050
Change Number. Only authorized users have the authorization to enter in
X X X X
transaction CC03 to display the CM.
In Change master screen, using the path Environment -> Reporting -> All
changes, it is possible to see the history of change made by the Change master.
UNITY-FSP- Change Number Reporting CC02 QUA07-02_0060 X X X X

MFG-00-0700
Authorized users can inquiry -filtered for some particular criteria (i.e., time period, CC03 QUA07-02_0070
authorized user who performed the change, PO/change number status, etc.)
CC05
 all the Bill of Materials that have been changed through the ECM
process; CC07
 all the Master Recipes that have been changed through the ECM
process.
423524079.doc Page 54 of 88
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
It is also possible to inquire for a specific change number the list of all the master
data that have been created/changed through it or to see all the information
related to it (CC03 transaction).
In any moment, for the authorized user it is possible to see ECM reporting views
clicking on Environment  Reporting on the top of the SAP screen and eventually
selecting some filtering criteria for showing the results.
423524079.doc Page 55 of 88
5.7 FUNCTIONAL MESSAGE CODES & CONTENT
Message Code Message Content
423524079.doc Page 56 of 88
6. OVERVIEW OF SAP TRANSACTIONS & CUSTOMIZING ACTIVITIES

6.1 SAP TRANSACTIONS
Transaction Code Transaction Title
CC01 Create Change Master
CC02 Change Change Master
CC03 Display Change Master
CC05 Change Overview
CC07 Engineering Change Mgmt Information
MM01 Create Material
MM02 Change Material
MM03 Display Material
C201 Create Master recipe
C202 Change Master recipe
C203 Display Master recipe
C223 Maintain Production Versions
LSMW Legacy System Migration Workbench
CRC1 Create Resource
CRC2 Change Resource
CR05 Work Center List
CR10 Work Center Change Documents
CA81 Master Recipe Usage and Resources
COR1 Create Process Order
COR2 Change Process Order
CS80 Change documents for Material BOM
AUT10 Evaluation of Audit Trail
423524079.doc Page 57 of 88
6.2 CUSTOMIZING ACTIVITIES

All customizing activities below have to be intended for the following plant in scope:
 CA01 – Montreal
 CA02 – Mississippi
 AC01 – Eden Prairie
 AC11 – Maastricht
 SM01 - Bracco Injeneering EU Losanna
Cust. No Customizing Description with Values T. Code or Path
001 Define Applications SPRO/Production planning for

process industries/Master
Data/Process
Order/Operations/BOM
Selection/Define Applications
002 Configure history requirement for BOM SPRO/Production/Basic

Data/Bill of Material/General
Data/BOM Usage/BOM
Usages/Configure history
requirement for BOM
003 Define default values SPRO/Production/Basic

Data/Bill of Material/Control
Data for Bills of
Material/Define default values
423524079.doc Page 58 of 88
004 Define BOM status SPRO/Production/Basic

Data/Define BOM status
005 Define Item Categories SPRO/Production/Basic

Data/Bill of Material/Item
Data/Define Item Categories
423524079.doc Page 59 of 88
006 Define BoM Usage SPRO/Production/Basic

Data/BoM Usage/Define BoM
Usage
007 Define priorities for BOM Usage (OPJI) SPRO/Production planning for
Data/Process
Order/Operations/BOM
Selection/Define priorities for
BOM Usage (OPJI)
423524079.doc Page 60 of 88
008 Define default values for item status SPRO/Production/Basic

Data/BOM usage/Define
default values for item status
423524079.doc Page 61 of 88
009 Define Modification Parameters SPRO/Production/Basic

Data/Bill of Material/Control
Data for Bills of
Material/Define Modification
Parameters
423524079.doc Page 62 of 88
010 Define parameters Production Planning for

Process Industries/Master
Data/Resource/General
Data/Standard Value/Define
parameters
423524079.doc Page 63 of 88
423524079.doc Page 64 of 88
423524079.doc Page 65 of 88
423524079.doc Page 66 of 88
423524079.doc Page 67 of 88
011 Define standard value key Production Planning for

Data/Resource/General
Data/Standard Value/Define
standard value key
012 Select Automatically SPRO/Production planning for

process industries/Process
order/Operations/Task list
Selection/Select Automatically
(OPJF)
423524079.doc Page 68 of 88
013 Define Profiles with Default Values SPRO/Production Planning for

Data/Master Recipe/Settings
for the Task List Type/Define
Profiles with Default Values
014 Define Recipe Status SPRO/Production Planning for

Data/Master Recipe/Data for
the Recipe Header/Define
Recipe Status
423524079.doc Page 69 of 88
015 Define recipe usage SPRO/Production planning for

Data/Master Recipe/Data for
the recipe header/Define
recipe usage
016 Standard Text Key (CA10) Standard Text Key (CA10)
423524079.doc Page 70 of 88
423524079.doc Page 71 of 88
423524079.doc Page 72 of 88
017 Define Control Keys SPRO/Production Planning for

Recipe Data/Define Control
Keys
423524079.doc Page 73 of 88
423524079.doc Page 74 of 88
018 Define Production scheduling profile (CORY) SPRO/Production planning for

process industries/Process
order/Master Data/Define
Production scheduling profile
(CORY)
423524079.doc Page 75 of 88
423524079.doc Page 76 of 88
423524079.doc Page 77 of 88
423524079.doc Page 78 of 88
423524079.doc Page 79 of 88
423524079.doc Page 80 of 88
423524079.doc Page 81 of 88
019 Define statuses for change master records SPRO/Cross Application

Components/Engineering
Change Management/Define
statuses for change master
records
423524079.doc Page 82 of 88
020 Maintain profile SPRO/Cross Application

Change
Management/Maintain profile
423524079.doc Page 83 of 88
021 Define number ranges SPRO/Cross Application

Change Management/Define
number ranges
423524079.doc Page 84 of 88
022 Define number ranges for Master Recipe SPRO/Production Planning for
Data/Master Recipe/Settings
for the Task List Type/Define
number ranges for Master
Recipe
023 Define Field Selection OPFA
024 Maintain Work Center Category OP40
423524079.doc Page 85 of 88
Create Work center category in copy from standard Work center category 0008
025 Maintain Screen Sequence OP13
026 Units of measure CUNI
423524079.doc Page 86 of 88
423524079.doc Page 87 of 88
7. OVERVIEW OF ADDITIONAL DEVELOPMENTS

7.1 REPORTS, FORMS
Dev. No FS-R Document Name Description FS Line No.
7.2 INTERFACES
Dev. No FS-I Document Name Description FS Line No.
7.3 CONVERSIONS
Dev. No FS-C Document Name Description FS Line No.
C-001 UNITY-FSC-MFG-02 Manufacturing Bill of Materials Functional Specification UNITY-FSP-MFG-00-0080
C-002 UNITY-FSC-MFG-01 Master Recipe Functional Specifications UNITY-FSP-MFG-00-0235
7.4 ENHANCEMENTS
Dev. No FS-R Document Name Description FS Line No.
423524079.doc Page 88 of 88

Unity FSP MFG 00 V01R01

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Unity FSP MFG 00 V01R01

Hochgeladen von

Copyright:

Verfügbare Formate

Project Unity Functional Specification - Manufacturing Master Data

F UNCTIONAL S PECIFICATION - M ANUFACTURING M ASTER D ATA

VERSION: 01 REVISION: 0100

Document Approval and Release

ACCENTURE CLAUDIA BIANCHI

CSV – VALIDATION CARLO CANDOTTI

BUSINESS – LOCAL TEAM LEAD DAVE MARKOVICH

BUSINESS – CORPORATE TEAM DAVIDE COHA

IT – CORPORATE MARCO MAIOLI

BUSINESS – NORTH AMERICA LUC RAYMOND

GQ – VALIDATION SANDRO TACCANI

Version- Change date Responsible person Change summary

V00R00 18-NOV-2011 Claudia Bianchi Initial Version

V01R00 10-DEC-2011 Marco Introna Approved Version

V01R01 10-SEPT-2014 Elisabetta Sozio Document updated for GSM

Last version revision information

Par. 2 Paragraph updated for GSM

Par. 3.1.3 Paragraph updated for GSM

Par. 3.1.6 Paragraph updated for GSM

Par. 5 Paragraph updated for GSM

Par. 6 Paragraph updated for GSM

[1] UNITY-MFG-URS – Manufacturing User Requirement Specifications

[2] UNITY-FSP-INV-07 – Manage manufacturing process in WM Functional Specification

[3] UNITY-FSP-INV-04 – Goods Receipt for Internal Production Functional Specification

[4] UNITY-FSP-SD-01 – Sales & Administration Master Data Functional Specification

[5] UNITY-FSP-PUR-01 – Purchasing Master Data Functional Specification

[6] UNITY-FSP-MFG-06 – Audit Trail Functional Specification

[7] UNITY-FSP-QUA-01 – Batch Management Functional Specification

[8] UNITY-FSC-MFG-02 – Manufacturing Bill of Materials Functional Specification

[9] UNITY-FSC-MFG-01 – Master Recipe Functional Specification

1.2 DEFINITIONS & ACRONYMS

SAP Systems, Applications & Products in data processing

MRP Material Requirement Planning

PV Production Version; a production version determines which alternative BOM is used

MIC Master Inspection Characteristics

UoM Unity of Measure

ECR Engineering change Request

VFD Valid From Date

S/N Serial Number

IPC In Process Control

SKU Stock Keeping Unit

This document is relevant for the following manufacturing companies:

 EZEM Canada Inc. (Montreal)

Project Project Project Process Process Subprocess Subprocess

Subprocess Description ACIST US ACIST EU ACIST ASIA EZEM BDI SMC/

Engineering Change Management X X X X

3. SHORT FUNCTIONAL DESCRIPTION

3.1 MFG01_MANUFACTURING MASTER DATA

3.1.1 MFG01-01_Bill of Material

A BoM may contain the following kinds of components:

 externally procured components – raw materials & packaging components;

The BoM header contains produced goods information, such as:

 BoM usage (Production, Costing, Validation, Engineering, etc.);

The BoM Item Master contains components information, such as:

In the resource important data are defined concerning:

 The use of production Resource/operators;

Master recipe represents a sequence of operations and phases to produce semi-finished

A master recipe consists of the following key elements:

3.1.3.1 Header data definition

 Recipe code (once assigned, it is not modifiable anymore) and description;

3.1.3.2 Recipe Structure Definition

For each processing operation, user can define:

 A resource, representing the area where the operation takes place;