Documente Academic
Documente Profesional
Documente Cultură
P ROJECT U NITY
VERSION: 01 REVISION: 00
AUTHOR
REVIEW
YANNICK GAUTHIER
425498759.doc Page 1 of 31
Project Unity Functional Specification - Manufacturing Other Processes
APPROVAL
425498759.doc Page 2 of 31
Project Unity Functional Specification - Manufacturing Other Processes
Document History
Paragraph # Change
425498759.doc Page 3 of 31
Project Unity Functional Specification - Manufacturing Other Processes
Table of Contents
1. Introduction........................................................................................................................ 5
1.1 Reference Documents............................................................................................. 5
1.2 Definitions & Acronyms...........................................................................................5
2. Document Purpose.......................................................................................................... 6
3. Short Functional Description.......................................................................................... 6
3.1 MFG06-02_ Re-Work / Re-Pack Process Management..........................................6
3.1.1 Re-Work............................................................................................................... 6
3.1.2 Re-Pack................................................................................................................ 8
3.2 MFG06-04_Contract Manufacturing........................................................................9
4. Business Process Flow Chart......................................................................................10
5. Solution.......................................................................................................................... 12
5.1 Re-Work.................................................................................................................. 12
5.2 Re-Pack................................................................................................................... 17
5.3 Contract Manufacturing Process Management...................................................19
5.4 Functional Message Codes & Content.................................................................19
6. Overview Of SAP Transactions & Customizing Activities..........................................20
6.1 SAP Transactions................................................................................................... 20
6.2 Customizing Activities........................................................................................... 21
7. Overview of Additional Developments.........................................................................31
7.1 Reports, Forms....................................................................................................... 31
7.2 Interfaces................................................................................................................ 31
7.3 Conversions........................................................................................................... 31
7.4 Enhancements.......................................................................................................... 31
425498759.doc Page 4 of 31
Project Unity Functional Specification - Manufacturing Other Processes
1. INTRODUCTION
1.1 REFERENCE DOCUMENTS
Reference Document
Term/Acronyms Definition/Explanation
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.
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.
QA Quality Assurance
425498759.doc Page 5 of 31
Project Unity Functional Specification - Manufacturing Other Processes
2. DOCUMENT PURPOSE
The purpose of this document is to describe how the solution will respond to user
requirements concerning Manufacturing Other Processes (Re-work, Re-Pack, Contract
Manufacturing).
For each of the above sub-processes, the following entities are in scope:
3.1.1 Re-Work
The input of a rework process can be:
425498759.doc Page 6 of 31
Project Unity Functional Specification - Manufacturing Other Processes
All batch/lot rework is performed according to procedures. The quality of the reworked
batch/lot/serial number is then approved by QA.
For a rework order, the bulk/assembly/finished product itself is used as input material, along
eventually with additional components, in the material list of a rework process order. Product
to be reworked has to be available in the plant where rework is performed.
EZEM: as output of the rework process, it is produced a new batch (reworked) for
the same product code different compared to the original one requiring rework; this
scenario is both applied in case of rework required due to QA disposition on inspected
batch or customer return.
o Out of Box Failure (OBF): device is returned back from customer due to
not conforming without ever being used;
o Refurbishment: a used device is return back from customer for any reason.
In case of OBF, the material returned back is received into the system with valued
stock, an inspection process is carried out on it and then the process of rework is
performed having as output a finished product with same material number and Serial
Number of the reworked product.
Refurbished products, due to their lost of value connected with their usage, cannot
be sold on the market with same price as new products; for this reason the material
returned back is received into the system with 0 value stock; after QA inspection and
disposition, the returned used product can be issued on the rework process order
into the system. In this scenario, rework order is created using as product a new
material code and, as component, product to be reworked. During Goods Receipt
from production user declares same S/N both for issuing reworked product and
receiving new product (S/N traceability has to be maintained).
Another business scenario that could require rework, other than customer return and
normal QA disposition on products internally produced requiring rework (UD =
“Rework”), is the need of 100% inspection required for S/N managed raw materials
for which during incoming inspection on pulled samples is identified a not conformity.
In fact in this scenario the following steps are performed:
1
A specific batch/lot search strategy is configured in order to select only batches/lots whose status is
“REWORK”.
425498759.doc Page 7 of 31
Project Unity Functional Specification - Manufacturing Other Processes
Only specific users are authorized to create/release Rework Process Orders and, in particular,
for EZEM Rework Orders are created by Manufacturing department and released by QA, while
for ACIST rework orders are created and released by MFG department.
3.1.2 Re-Pack
It is sometimes necessary during or at end of a packaging process to execute additional
operations in order to solve packaging not conformities identified during in-line production.
These additional processing steps are called “repack”.
New operations for re-packing process are added on the existing normal production process
order (maintaining the same batch).
Costs associated with re-packing process activities are tracked throughout actual time
confirmation done for the re-packing operations and additional materials required to run
additional packing steps.
In order to maintain control of changes occurring on released process order after the release
process the “PO approval” functionality is configured for all the following order types:
The enhancement related to the master data validity check (please refer to [3] for more
details) is extended in order to set-up automatically the following process order status as part
of process order release completion:
Based on this status the system does not allow any change on the process order approved
master data (e.g. material list, operation list, etc…); the only way to allow changes required
for re-pack process is to withdraw the approval status for the process order using manual
function available on the “Change Process Order” transaction. In this scenario the system
replace the approval status mentioned above with the following one:
After that the required changes have been performed on the process order is required a
“Manual Approval” in order to proceed with execution activities. This step is performed using
425498759.doc Page 8 of 31
Project Unity Functional Specification - Manufacturing Other Processes
manual function available on the “Change Process Order” transaction. In this scenario the
system replace the approval status mentioned above with the following ones:
In this way the system always identifies, through the additional status, the POs for which the
automatic approval has been removed and manually granted after the changes.
Only specific users are authorized to perform the steps described above and, in particular,
“Withdraw approval” can be performed by Manufacturing or QA department, whereas final
“Manual Approval” can be performed by QA department only.
Note: Repack process is not relevant for ACIST and it is not taken into account for that plant.
Based on Material Master settings the batch number to be produced may need to be
manually specified in the Process Order based on customer specification (product
managed with manual batch number generation; for more details please refer to
[6]);
Process Order form has to be printed out with product batch expiration date
displayed according to the specific format defined by the customer (for more details
please refer to [12]).
425498759.doc Page 9 of 31
Project Unity Functional Specification - Manufacturing Other Processes
425498759.doc Page 10 of 31
Project Unity Functional Specification - Manufacturing Other Processes
425498759.doc Page 11 of 31
Project Unity Functional Specification - Manufacturing Other Processes
5. SOLUTION
5.1 RE-WORK
Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference
Acist Asia
Acist US
Acist EU
Ezem
BDI
UNITY-FSP- Rework Process Scenarios N/A
MFG-05-0010
Rework process can be triggered by one of the following scenarios:
Non conforming produced product requiring rework;
X X
Any product returned from customer requiring rework;
An un-planned 100% inspection required on a raw material S/N managed
failing quality control tests on a sampled quantity (only for Acist)
In case of OBF, the material returned back has to be received into the system as
valued stock. Then, an inspection process is carried out on it by QA department (for
the details of this process please refer to [9]). Finally, the process of rework on the X
material is performed (for the details of the rework PO creation please refer to the
following lines). The new product output of the rework process has the same S/N of
the input one as well as the material code.
In case of refurbishment, the material returned back is received into the system with
0 value stock (for the details of this process please refer to [7] and [8]); after the
inspection process carried out by QA department (for the details of this process
please refer to [9]), the returned product is the input of the process of rework into
the system (for the details of the rework PO creation please refer to following lines).
The new product output of the rework process has the same S/N of the input one
but different material code.
UNITY-FSP- Rework Process Scenario – 100% Re-inspection MIGO MFG06-02_0010 X
MFG-05-0025
Another business scenario that could require rework, other than customer return and
425498759.doc Page 12 of 31
Project Unity Functional Specification - Manufacturing Other Processes
Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference
Acist Asia
Acist US
Acist EU
Ezem
BDI
normal QA disposition on products internally produced requiring rework (UD = QA11 MFG06-02_0030
“Rework”), is the need of 100% inspection required for S/N managed raw materials
for which during incoming inspection on pulled samples is identified a not conformity. COR1
In fact in this scenario the following steps are performed:
COR2
At incoming inspection an inspection lot is generated with a sample size
(minor than 100% sampling) calculated based sampling strategies;
UNITY-FSP- Create rework order for batch/lot managed materials COR1 MFG06-02_0010
MFG-05-0030
Rework Order can be created accessing COR1 transaction with code of the material COR2 MFG06-02_0020
to be reworked, plant and Order Type “ZREW” for a FP/HFP/assembly batch
MIGO MFG06-02_0030
managed material and adding the same material as a component in the Material List
Tab of the Process Order. In this case, the system allows to change the batch X X
number from the original batch of FP/HFP/assembly during goods issues to the new
batch number during goods receipt. In COR1/COR2, the original batch number of the
FP/HFP/assembly can be assigned in the materials list.
The new batch number can be assigned in the Goods Receipt tab of the process
order or manually entering a new Batch number at Goods Receipt posting.
UNITY-FSP- Create rework order for S/N managed materials (OBF Process) COR1 MFG06-02_0010 X
MFG-05-0040
Rework Order can be created using COR1 transaction with code of the material to be MIGO MFG06-02_0090
reworked, plant and Order Type “ZREW” for a S/N managed material and
considering the same material as a component in the Material List Tab of the Process
425498759.doc Page 13 of 31
Project Unity Functional Specification - Manufacturing Other Processes
Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference
Acist Asia
Acist US
Acist EU
Ezem
BDI
Order (COR1).
Note: for S/N managed rework products no S/N allocation is allowed on the order,
but it is declared directly during Goods issue process.
UNITY-FSP- Create rework order for S/N managed materials (Refurbishment Process) COR1 MFG06-02_0010
MFG-05-0050
Rework Order can be created using COR1 transaction with code of the material to be MIGO MFG06-02_0030
produced, plant and Order Type “ZREW” for a S/N managed material and adding as
MFG06-02_0090
a component in the Material List Tab of the Process Order (COR1) the original X
material to be reworked.
Note: for S/N managed rework products no S/N allocation is allowed on the order,
but is declared directly during Goods issue process.
This process is manual and a specific procedure has to be introduced to control the
process. For the details of the cost centers to be used please refer to [11].
UNITY-FSP- Rework Order Creation Authorization Settings COR1 002 MFG06-02_0060
MFG-05-0060
At the act of create Rework Process orders the system verifies if the user is 003
authorized to perform the action (creation/release). The following scenarios are
X
relevant:
ACIST: only manufacturing dept is authorized to create rework order
EZEM: only manufacturing dept is authorized to create rework order
2
The percentage rate in the other rows has to be canceled to avoid error messages.
425498759.doc Page 14 of 31
Project Unity Functional Specification - Manufacturing Other Processes
Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference
Acist Asia
Acist US
Acist EU
Ezem
BDI
UNITY-FSP- Rework Order release Authorization Settings COR2 002 MFG06-02_0070
MFG-05-0070
At the act of release Rework Process orders the system verifies if the user is 003
authorized to perform the action (creation/release). The following scenarios are X
relevant:
ACIST: only manufacturing dept is authorized to release rework order
EZEM: only QA dept is authorized to release rework order
UNITY-FSP- Update Rework Order for Rework Process Requirements COR1 MFG06-02_0050
MFG-05-0080
At process order creation (or at PO change) the system proposes the BOM and the COR2
recipe maintained for that material according to Production Version selected by the
user. It is possible for the user to change/delete/ modify the list of
materials/components and also the operation, sections for deleting a phase,
changing/modifying it using a new resource, etc.
Note: all the components proposed by the system can be deleted, but there is the
need to retain at least one operation, sections before deleting the recipe in a rework X X
Process Order.
Material List for a process Order can be accessed by clicking the following Icon
425498759.doc Page 15 of 31
Project Unity Functional Specification - Manufacturing Other Processes
Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference
Acist Asia
Acist US
Acist EU
Ezem
BDI
The operator declares a Goods Receipt (movement 101) and Goods Issue
(movement type 261) for the same Serial Number entering the MIGO with the PO
code and selecting the material for which posting the movement.
Note: for more details on the GR please refer to [10]; for more details on the Goods
Issue please refer to [4].
UNITY-FSP- Rework Order Long Text Management COR2 MFG06-02_0010
MFG-05-0110
In the transaction COR2, Process Order Long Text field can be used for manual entry
X X
of NCMR report from another document. This will help the shop floor to understand
the rework operation to be performed on the FP/SFP/assembly material when the
original process order is still open.
UNITY-FSP- Lot Allocation on Rework Order COR2 001 MFG03-02_0050
MFG-05-0120
Prior to be assigned to a rework order, quality status of batches/lots has to be MFG06-02_0080
“Rework” and batch status “Released”. This is to avoid other users accidentally
X X
consuming these batches of products on normal production activities. In particular, it
is possible to create Re-Work process order only if the stock for bulk/finished
product/assembly to be re-worked is available in the plant with specific batch status
"Rework".
UNITY-FSP- Order Execution for Order Type ZREW COR6 MFG06-02_0010
MFG-05-0130 X X
For the details of the PO Execution please refer to [4]. MIGO
425498759.doc Page 16 of 31
Project Unity Functional Specification - Manufacturing Other Processes
5.2 RE-PACK
Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference
Acist Asia
Acist US
Acist EU
Ezem
BDI
UNITY-FSP- Process Order Update for Repack COR2 MFG06-02_0100
MFG-05-0150
The new operation for the re-packing process is added on the existing normal
production process order (maintaining the same batch) accessing the COR2 with
material number, plant and Order Type. Then the operator has to click on the
X
Note: Any Process Order can be used for doing re-pack if the PO is not technically
completed (TECO status) except for orders whose Order Type is “ZREW”.
The enhancement related to the master data validity check (please refer to [3] for
more details) is extended in order to set-up automatically the following process order
status as part of process order release completion:
Based on this status the system does not allow any change on the process order
approved master data (e.g. material list, operation list, etc…); the only way to allow
changes required for re-pack process is to withdraw the approval status for the
process order using manual function available on the “Change Process Order”
transaction. In this scenario the system replace the approval status mentioned above
with the following one:
425498759.doc Page 17 of 31
Project Unity Functional Specification - Manufacturing Other Processes
Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference
Acist Asia
Acist US
Acist EU
Ezem
BDI
After that the required changes have been performed on the process order is
required a “Manual Approval” in order to proceed with execution activities. This step
is performed using manual function available on the “Change Process Order”
transaction. In this scenario the system replace the approval status mentioned above
with the following ones:
In this way the system always identifies, through the additional status, the POs for
which the automatic approval has been removed and manually granted after the
changes.
Only specific users are authorized to perform the steps described above and, in
particular, “Withdraw approval” can be performed by Manufacturing or QA
department, whereas final “Manual Approval” can be performed by QA department
only.
425498759.doc Page 18 of 31
Project Unity Functional Specification - Manufacturing Other Processes
Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference
Acist Asia
Acist US
Acist EU
Ezem
BDI
UNITY-FSP- Contract Manufacturing process orders are orders that are used to manage an COR1 MFG06-04_0010
MFG-05-0190 internal production by commitment of an external customer.
MFG06-04_0020
A process order of this type can be created using “ZNOR” as order type and, in
X X
general, is managed as a normal production/packaging process, so please refer to
previous sections of this document and to [2], [3], [4], [5] for more details. If
required, user is able to use on the process order stock received in consignment
from Customer to produce finished product batch.
UNITY-FSP- For the details of batch numbering rules used for Contract Manufacturing orders COR2 MFG06-04_0010
MFG-05-0200 please refer to [6]. X X
MIGO
UNITY-FSP- For the details of shelf life expiration date format management on the process order COR2 R-01 MFG06-04_0010
MFG-05-0210 form please refer to [12]. X X
COPI
425498759.doc Page 19 of 31
Project Unity Functional Specification - Manufacturing Other Processes
425498759.doc Page 20 of 31
Project Unity Functional Specification - Manufacturing Other Processes
425498759.doc Page 21 of 31
Project Unity Functional Specification - Manufacturing Other Processes
425498759.doc Page 22 of 31
Project Unity Functional Specification - Manufacturing Other Processes
425498759.doc Page 23 of 31
Project Unity Functional Specification - Manufacturing Other Processes
002 Define Authorization Key for User Status Profile(BS52) SPRO/Production planning for
process industries/Process
order/Master
data/Order/Define
Authorization Key for User
Status Profile(BS52)
425498759.doc Page 24 of 31
Project Unity Functional Specification - Manufacturing Other Processes
profile (BS02)
425498759.doc Page 25 of 31
Project Unity Functional Specification - Manufacturing Other Processes
425498759.doc Page 26 of 31
Project Unity Functional Specification - Manufacturing Other Processes
004 Define Authorization Key for User Status Profile(BS52) SPRO/Production planning for
process industries/Process
order/Master
data/Order/Define
Authorization Key for User
Status Profile(BS52)
425498759.doc Page 27 of 31
Project Unity Functional Specification - Manufacturing Other Processes
data/Order/Define Status
profile (BS02)
425498759.doc Page 28 of 31
Project Unity Functional Specification - Manufacturing Other Processes
425498759.doc Page 29 of 31
Project Unity Functional Specification - Manufacturing Other Processes
425498759.doc Page 30 of 31
Project Unity Functional Specification - Manufacturing Other Processes
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.
7.4 ENHANCEMENTS
Dev. No FS-R Document Name Description FS Line No.
425498759.doc Page 31 of 31