Unity FSP MFG 04 V01R03

Project Unity Functional Specification - Process Order Confirmation
P ROJECT U NITY
F UNCTIONAL S PECIFICATION - P ROCESS O RDER C ONFIRMATION
VERSION: 01 REVISION: 0300
Document Approval and Release

ISSUED BY
SYSTEM INTEGRATOR SILVIA FERRAZZA 18.10.2017
REVIEWED BY
ITS-CSC
LOCAL QA
APPROVED BY
BO
AM
423493467.doc Page 1 of 34
Document Approval and Release

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

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

LEAD
APPROVAL
IT – CORPORATE MARCO MAIOLI
BUSINESS – NORTH AMERICA LUC RAYMOND

TEAM LEAD
GQ – VALIDATION SANDRO TACCANI

COORDINATOR
423493467.doc Page 2 of 34
Document History
Version- Change date Responsible person Change summary

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

Valeria Mulas
V01R03 18- OCT- 2017 Silvia Ferrazza Document updated for PR279823
Last version revision information
Paragraph # Change
Par. 2 Paragraph updated for GSM
Par. 5.3 Line UNITY-FSP-MFG-04-0260Paragraph updated added for PR279823
423493467.doc Page 3 of 34
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 MFG05-01_Process Order confirmation (Time Declaration).................................6
3.2 MFG05-02_Process Order Closure.........................................................................7
3.3 MFG08-01_Reporting...............................................................................................7
4. Business Process Flow Chart........................................................................................ 9
5. Solution.......................................................................................................................... 10
5.1 MFG05-01_Process Order confirmation (Time Declaration)...............................10
5.2 MFG05-02_Process Order Closure.......................................................................17
5.3 MFG08-01_Reporting............................................................................................. 20
5.4 Functional Message Codes & Content.................................................................23
6. Overview Of SAP Transactions & Customizing Activities..........................................24
6.1 SAP Transactions................................................................................................... 24
6.2 Customizing Activities........................................................................................... 25
7. Overview of Additional Developments.........................................................................32
7.1 Reports, Forms....................................................................................................... 32
7.2 Interfaces................................................................................................................ 32
7.3 Conversions........................................................................................................... 32
7.4 Enhancements.......................................................................................................... 32
423493467.doc Page 4 of 34
1. INTRODUCTION
1.1 REFERENCE DOCUMENTS
Reference Document
[1] UNITY-MFG-URS_V01R00 – Manufacturing User Requirements Specification
[2] UNITY-FSP-MFG-02 – Process Order Release Functional Specification
[3] UNITY-FSP-MFG-03 – Process Order Execution 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.
HFP/SP Half-finished/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.
RLT Replenishment Lead Time
FIFO First In First Out
FEFO First Expired First Out
S/N Serial Number
TECO Technical Completion
423493467.doc Page 5 of 34
2. DOCUMENT PURPOSE
The purpose of this document is to describe how the solution will respond to user
requirements concerning Manufacturing Process Order Confirmation process.
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)
Project Project Project Process Process Subprocess Subprocess

Stream Domai Domain Code Description Code Description
n Code
Operations MFG Manufacturing MFG05 Production
Execution – Closure
Activities
Process Order
Confirmation (Time
MFG05-01 Declaration)
MFG05-02 Process Order Closure
MFG08 Reporting
MFG08-01 Reporting
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
Process Order Confirmation (Time X X X X
Declaration)
Process Order Closure X X X X
Reporting X X X X
3. SHORT FUNCTIONAL DESCRIPTION
3.1 MFG05-01_PROCESS ORDER CONFIRMATION (TIME DECLARATION)
Process Orders confirmation is done at the end of production activities at operation level. It is
possible to manage both partial and final confirmation.
During process order confirmation operator is able to close open reservations, if needed.
Note: if any error occurs during process order confirmation, the operator can reverse the
process.
In EZEM, the operator declares actual values for labour and machine time, at operation level,
at the end of process order processing.
In ACIST, declaration is not performed and the user always confirms standard values (if
defined in the master recipe) for labour times 1, at operation level, at the end of process order
1
Machine time is not relevant for ACIST.
423493467.doc Page 6 of 34
processing. Time reconciliation is done on monthly basis, considering overall production

outcomes and production operator timesheets.
In ACIST EU and SMC/BINJ EU declared times are only related to Labour times, both
assembly process order and rework orders foresee only human resource involvement (no
machine time). Actual values for labor time, at operation level, are declared at the end of
process order processing.
3.2 MFG05-02_PROCESS ORDER CLOSURE
Process order is closed after completing and verifying production operations. In particular,
production department checks that all the following are verified before closing a Process
Order:
 Process order has status ‘Final confirmation’;

 Consumption of components are within pre-defined tolerances;
 No pending material request exists for the Process Order;
 Goods receipt confirmation has been received by the warehouse;
 Component scrap is within pre-defined limits.
During reconciliation process user can inquiry all the inventory movements related to a
specific Process Order (goods receipt for process order, goods issue against process order,
reversal of movements).
Note: User can only cancel a Process Order that is released but not yet in production.
Final Process Order closure (technical completion) corresponds to the “logistic closure” of the
Process Order. When technical completion is posted, no more inventory posting is allowed.
Only finance department can revoke process order technical completion, if needed.
It is possible to close released Process order at any time, even after the start of production
but it is possible to cancel Process Orders only if they are not yet in production.
3.3 MFG08-01_REPORTING
Reporting is the method to analyze the performance of the system: it consists in querying the
system for obtaining partial (filtered by same particular criteria) or complete information
about the data contained in it.
In the following are explained the different queries that are possible in the system.
User is able to inquire the list of Process Orders filtered by:
 order status;
 range of dates;
 product number.
User is able to inquire, for a process order, the details of confirmation data. For example, it is
possible to explore the details of actual values, confirmed quantity, confirmation type (if
partial or final), etc…
User is able to inquire, for a process order, the details of the following material movement
posting:
423493467.doc Page 7 of 34
 material consumption;
 material consumption reversal;
 product goods receipt;
 product goods receipt reversal.
Furthermore, it is always possible for the user to examine the details of goods movement
errors generated during material movement posting.
It is also possible for the user to query a Process Order by:
 order status;
 operation status;
 phase status.
At Process Order Release the details of missing parts due to inventory shortfall is available.
The user is able to inquire the list of all components batch/lot numbers and quantity used to
produce the specific Product batch/Process Order by:
 Product batch number;

 Process order number.
It is possible to query finished product process orders for which semi-finished product
batch/lot number has been allocated as well as those for which semi-finished product
batch/lot number is not allocated.
It is possible to report the list of restricted batches/lots allocated to a process order and the
reason for batch/lot restrictions at any point of time.
User is able to inquiry at any moment which production version has been used to produce a
specific production batch/lot.
User is able to inquiry and explode the BOM by level with the details of the revision ID and of
the change order number.
423493467.doc Page 8 of 34
4. BUSINESS PROCESS FLOW CHART
423493467.doc Page 9 of 34
5. SOLUTION
5.1 MFG05-01_PROCESS ORDER CONFIRMATION (TIME DECLARATION)
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- Process Order Confirmation – Milestone Confirmation COR6 003 MFG05-01_0010
MFG-04-0010
Confirmation of a process order is done at phase level through transaction COR6 CORR MFG05-01_0020
or CORR for collective entry. Nevertheless, in order to reduce the amount of
confirmation it is possible to set a milestone confirmation that will automatically
X X X X X
confirming the previous phases not already confirmed. This setting allows to
manage confirmation at operation level.
The system is set so that no successor milestone confirmation can be done in the
system without a previous milestone confirmation confirmed.
UNITY-FSP- Steps 2a-3: Process Order Confirmation – Single Order Confirmation COR6 003 MFG05-01_0010
MFG-04-0020
User is able to proceed with process order confirmation (single confirmation) MFG05-01_0020
launching transaction COR6 and inserting the following parameters:
 Process Order
 Operation/Phase* X X X X X
(*) if not inserted is automatically selected by the system if only phase for the
order requires confirmation, or manually selected by the user based on the list of
phases requiring confirmation displayed by the user.
After the insertion of selection parameters, clicking on “Enter” the system displays
the “Process Order Confirmation Create: Detail” screen.
UNITY-FSP- Step 2b: Process Order Confirmation – Collective Order Confirmation CORR 003 MFG05-01_0010 X X X X X
MFG-04-0030
User is able to proceed with multiple process order confirmation (multiple MFG05-01_0020
confirmation) launching transaction CORR and selecting one of the following
screen options:
 Confirmation view;
 Process Order view (preferred).
In case of “Confirmation view” the user has to insert the following selection
423493467.doc Page 10 of 34
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
parameters for all the orders requiring confirmation:
 Confirmation number.
In case of “Process Order view” the user has to insert the following selection
parameters for all the orders requiring confirmation:
 Process Order;
 Phase/Operation.
After the insertion of selection parameters, clicking on “Enter” the system
automatically set the following information into the “Collective Entry: Time Ticket”
screen:
 In case of “Confirmation view”:
o Process Order;
o Operation/Phase;
o Posting Date;
o Resource;
o Plant.
 In case of “Process Order view”:

o Confirmation number;
o Posting Date;
o Resource;
o Plant.
UNITY-FSP- Steps 4-5-6: Process Order Confirmation – Confirmation Data Insertion COR6 003 MFG05-01_0010 X X X X X
MFG-04-0040
During process order confirmation, in both the scenarios, following main CORR MFG05-01_0020
information have to be specified by the user:
 Confirmation Type: as per options specified in line 0010;
 Yield: actual produced quantity which confirmation data are referring
423493467.doc Page 11 of 34
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
to;
 Activities: labour/machine actual/standard times to confirm.
UNITY-FSP- Step 4: Process Order Confirmation – Confirmation Type COR6 003 MFG05-01_0030
MFG-04-0050
Process Order confirmation is done at phase level through transaction COR6 or CORR
CORR for collective entry. Three different confirmation type are allowed in the
system:
- Automatic final confirmation: The system set automatically the final
confirmation while the Yield confirm at phase level is equal or above the
yield expected. If the yield confirmed is lower than the quantity
expected, the system set automatically the flag partial confirmation.
- Final Confirmation: The user can declare a final confirmation, X X X X X
especially in the case of actual yield is lower than the yield expected.
The system is not waiting for any further confirmation.
- Partial confirmation: The user can state that the confirmation done at
phase level is partial; therefore the system is expecting further
confirmation.
For all order types (ZNOR, ZSTA, ZCLI, ZENG, ZREW, ZVAL), by default,
transaction COR6 is set for confirmation type: “Automatic final confirmation”.
UNITY-FSP- Step 6: Process Order Confirmation – Activity confirmation at phase COR6 003 MFG05-01_0010
MFG-04-0060 level
CORR MFG05-01_0020
The system allows the user to insert actual values of activities (e.g. labor hour,
machine hour, etc.) before the process order is technically complete or closed.
Zero is an acceptable labor time. This action is possible through transaction COR6
or CORR. The possible values that can be confirmed at each phase: X X X X X
 standard values: associated to the resource in the specific couple

phase/process order;
 actual values: inserted by the user based on the actual use of machine
and operators involved in the production process.
UNITY-FSP- Step 6: Process Order Confirmation – Activity confirmation at phase COR6 MFG05-01_0010 X X X X X
423493467.doc Page 12 of 34
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
MFG-04-0070 level MFG05-01_0020
When user accesses to COR6 for a couple process order-phase, the system does
not populate automatically fields “Yield” and “Time for activities” until the user:
 Enter manually any value in those fields
or
 Push the button “Actual data” to automatically retrieve default values
MFG-04-0080 level
MFG05-01_0020
In the “Process Order Confirmation Create: Detail” screen user has available, in
field for Yield, Scrap and Activities time, the following columns: MFG05-01_0030
X X X X X
 “Confirmed to date”: which shows the quantity (quantity/time)
already confirmed for that phase
 “Planned to be confirmed”: which shows the total quantity/time that
is expected to be confirmed (by default values)
MFG-04-0090 level
CORR MFG05-01_0020
The system retrieves the standard activities quantity based on the standard
time/yield of the phase confirmation while performing the actual confirmation. If
no modification is done by the user, while saving the confirmation the user back-
flushes the standard quantity of activities.
X X X X X
Otherwise in case of value modification according to actual values the system
records values inserted by the user.
During activity confirmation the user is able to insert comments using “Long Text”
button in the confirmation main screen. Text inserted by the user is then visible,
after confirmation, at any moment accessing in display modality to the
confirmation data.
UNITY-FSP- Step 8: Process Order Confirmation – Partial Confirmation COR6 003 MFG05-01_0030 X X X X X
MFG-04-0100
The system allows a partial confirmation of an order (partial confirmation of good CORR
issue and activity or a partial delivery of good receipt of a process order). It is
423493467.doc Page 13 of 34
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
possible to right away confirm the next scheduled process order.
UNITY-FSP- Step 7: Process Order Confirmation – Over/Underdelivery Tolerances COR6 003 INV03-03_0060 X X X X X
MFG-04-0110
During process order confirmation automatic checks are performed against: CORR INV03-03_0110
 Overdelivery tolerance: Two parameters can be checked regarding
overdelivery:
o Yield overdelivery at phase level– yield overdelivery is driven
by:
 The % in the field “Overdelivery tolerance” in work
scheduling view of the material master data
 A customizing point referring to check of
overdelivery (no check, warning message or error
message). Order type/plant has been set to
overdelivery above % in work scheduling view gives
an error message.
o Good Receipt overdelivery
 The % in the field “Overdelivery tolerance” in work

scheduling view of the material master data. For all
quantity good receipt over that tolerance, the
system will retrieve an error message.
Note: this check is set in place in order to avoid typing mistakes. Nevertheless, if
for operational reasons the delivery is over what was expected it is possible to set
in the process order the indicator “Unlimited Overdelivery” in Goods Receipt view,
the system would therefore not check the tolerance anymore.
 Underdelivery tolerance: Two parameters can be checked regarding
underdelivery:
o Yield underdelivery at phase level – yield underdelivery is
driven by:
 The % in the field “Underdelivery tolerance” in work
scheduling view of the material master data
 A customizing point referring to check of
underdelivery (retrieve no check, warning message
423493467.doc Page 14 of 34
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
or error message). Order type/plant have been set
to no underdelivery checked.
o Good Receipt underdelivery
 The % in the field “Underdelivery tolerance” in work

scheduling view of the material master data.
 A system message M7 021 to be set as Warning or
Error at good receipt of final confirmation.
 Message system M7 021 is set as warning in the
customizing.
Note: underdelivery is checked only at final confirmation and not at partial
confirmation of a phase.
UNITY-FSP- Process Order Confirmation – Confirmation reversal/correction CORS 003 MFG05-01_0030

MFG-04-0120
Process Order confirmation reversal can be done at process order/phase level: COR6 MFG05-01_0040
 No Automatic good receipt activated on the process order operation list MFG04-03_0110
The set of confirmation done within a phase/confirmation number (in MFG04-03_0120
case of partial receipt) in transaction COR6/CORR: activities and/or good
issues (in case of backflushing) has to be reversed entirely for the X X X X X
couple phase/confirmation number with transaction CORS. The entire
set of data reversed has to be reposted in SAP with the correct values
through transaction COR6/CORR.
During confirmation reversal the user is requested by the system to
insert “Reason for reversal”. Text inserted by the user is then visible,
after confirmation reversal, at any moment accessing in display modality
to the confirmation data.
UNITY-FSP- Process Order Confirmation – Confirmation data display CORT 003 MFG05-01_0030 X X X X X
MFG-04-0125
At any moment user is able to display confirmation data using transaction CORT
and inserting the following parameters:
 Process Order
 Operation/Phase (optional)
423493467.doc Page 15 of 34
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
After the insertion of selection parameters, clicking on “Enter” the system displays
the “Display Process Order Confirmation: Operation/Overview” screen. Selecting
the confirmation to display (checkbox) and clicking on button “Details” the user is
able to display all confirmation data previously specified during phase confirmation
(comments included).
423493467.doc Page 16 of 34
5.2 MFG05-02_PROCESS ORDER CLOSURE
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
UNITY-FSP- Process Order Closure – Reconciliation Activities COOISPI MFG05-02_0010
MFG-04-0130
While all quantities have been confirmed in a process order, it is possible to have a MFG08-01_0010
recap of all the quantities planned vs actual quantities so that the manufacturing
area can identify the reasons for variances. MFG08-01_0020
For example, this can be done using report transaction COOISPI where: MFG08-01_0050
- Planned quantities and values can be found in: MFG08-01_0060
o Order header MFG08-01_0070

MFG08-01_0080 X X X X X
o Components
o Operations
- Actual quantities and values can be found in:

o Documented Goods movements
o Confirmations
Deviation should be followed up and documented outside SAP by procedure within

the manufacturing papers.
UNITY-FSP- Process Order Closure – Error on Goods Movements COGI MFG05-02_0020 X X X X X

MFG-04-0135
At confirmation of good issue or good receipt, issues can happen such as:
 Category 1:
o The batch number of the good receipt is not entered by the
user
o The batch number of a good issue component is not entered
by the user
o The storage location of a good issue or a good receipt is
missing and not entered by the user
 Category 2:
423493467.doc Page 17 of 34
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
o There is not enough stock in SAP order to perform the good
issue, whereas there was enough physical stock since
manufacturing has been performed normally on the shopfloor
For category 1 type of error, the user should correct the error in foreground, i.e.
before saving the good issue/good receipt.
For category 2 type of error, the user should double check its entry and if all is
according to physical manufacturing events, the user should save the confirmation
without correcting the error.
The error is then recording in SAP in transaction COGI, no posting is done in SAP
of partial quantity. This log of error should be reprocessed every day in order to
have correct stock inventory.
UNITY-FSP- Steps 11-12-13: Process Order Closure – Technical Completion COR1 001 MFG05-02_0020
MFG-04-0140
A process order has to be “Technically Closed (TECO)” by the user when: COR2 002
 All confirmations have been done in the system. This will have to be COHVPI
checked manually by the user using a procedure, since there is no
system check.
 Consumption of components are within pre-defined tolerances. This will
have to be checked manually by the user using a procedure, since there
is no system check.
 There is no processing error of goods movements in the system relative X X X X X
to the process order. The system does not allow the technical closure of
an order if for example processing error of goods movements remains or
the inspection lot is not yet completed.
The technical closure can be done order by order through the transaction
creation/change of a process order COR1/COR2 and in mass through transaction
COHVPI.
Note: in order to track over/under consumption of components, a procedure
should be put in place in order to check potential differences planned/actual and
inform the manufacturer.
UNITY-FSP- Steps 11-12-13: Process Order Closure – Technical Completion COR2 001 MFG05-02_0060 X X X X
MFG-04-0150
In order to make changes to a process order that has not been yet processed by 002
423493467.doc Page 18 of 34
SMC/BINJ EU
Acist Asia
Acist US
Acist EU
Ezem
BDI
controlling, it is necessary to re-open the order. For that purpose, user has to
open the process order in change modality (COR2) and from the toolbar has to
select the path “functions > restrict processing > Technically Complete”.
UNITY-FSP- Steps 11-12-13: Process Order Closure – Order Forced Completion COR1 001 MFG05-02_0040
MFG-04-0160
If an order should not be executed on the shop floor, the process order should be COR2 002 MFG05-02_0050
closed in order to:
 Suppress the process order from the expected process order to be
planned
 Suppress the order reservation on the component quantities X X X X X
 Suppress the capacity reservation on the resources.
Note that it is possible to close an order released:
 But not yet in production
 After the start of production if no error of goods movements is linked to
the process order and the inspection lot is not yet performed.
UNITY-FSP- Process Order Closure – Order Deletion COR2 MFG05-02_0030

MFG-04-0170
It is possible to set a deletion flag on a closed process order in order to allow X X X X X
archiving. For that purpose user has to open the process order in change modality
(COR2) and from the toolbar select the path “functions>Deletion flag> active”.
UNITY-FSP- Process Order Closure – Order Freezing COR6 001 MFG05-02_0060

MFG-04-0180
It is not possible to confirm activities, good issue and good receipt after the MIGO 002 X X X X X
“Technical Closure (TECO)” of a process order. The system retrieves an error
message in transaction COR6 or MIGO.
UNITY-FSP- Process Order Closure – Technical Completion Reversal COR2 001 MFG05-02_0070
MFG-04-0190
Only authorized users are allowed to revoke order technical completion. For that 002
purpose, user has to open the process order in change modality (COR2) and from X X X X X
the toolbar has to select the path “functions > restrict processing > Revoke
Technically Complete”.
423493467.doc Page 19 of 34
5.3 MFG08-01_REPORTING
Line No. Description of solution with Business process step number T.Code Cust. Dev. URS
SMC/BINJ EU
Acist Asia
No No Reference
Acist US
Acist EU
Ezem
BDI
UNITY- Manufacturing Reporting – Process Order Information System COOISPI MFG05-
FSP-MFG- The main reporting used in manufacturing is available in the T.code: ‘COOISPI’ “Process Order Information System”. 02_0010
04-0200
MFG08-
User can view all the orders in the system, including the orders with deletion flags or deletion indicators. Archived orders 01_0010
are not taken into account. The order information system has the following display options:
MFG08-
 In an individual object list, a list is generated for the selected object (for instance, order header, operation and 01_0040
component). User can define the structure and appearance of the individual object list with a layout.
 On the object overview the individual orders are displayed with their subordinate objects in a hierarchical MFG08- X X X X X
01_0050
structure. With an overall profile, you can define which fields are displayed and which objects (order headers,
items, sequences, and so on) are read or displayed. In addition, user can define which fields are displayed for MFG08-
the individual objects. 01_0060
MFG08-
01_0080
UNITY- Manufacturing Reporting – Errors log on Process Order creation/release COR2 MFG08-
FSP-MFG- Reason for failures in case of creation and release of process order can be checked directly in the process order with the 01_0070
04-0210 T.Code “COR2” or “COR3” and selecting from the toolbar the path: ‘ GoTo -> Logs’ and selecting the appropriate step of COR3 X X X X X
MFG08-
the process. 01_0090
UNITY- Manufacturing Reporting – Single-level Bill of Materials Display CS11 MFG01- X X X X X

FSP-MFG- User is able to inquiry Single-level BoM launching transaction CS11 and inserting the following selection parameters: 01_0110
04-0220
 Material;
 Plant;
 Alternative BoM (mandatory if required qty not inserted);
 BoM application;
 Valid From (date);
 Change number (optional);
423493467.doc Page 20 of 34
SMC/BINJ EU
Acist Asia
No No Reference
Acist US
Acist EU
Ezem
BDI
 Required qty (mandatory if required qty not inserted).
The system provides a report which provides for a given HFP/FP, for specified time period time, the valid BOMs with a list
of data related to components. In case of finished product the system is providing also the details about the following
levels (HFG Bill of Material).
In the first screen, the change number can be defined by the user. The date from which change is effective can be
displayed in the layout.
UNITY- Manufacturing Reporting – Single-level Bill of Materials Display CS11 MFG08-

FSP-MFG- 01_0130 X X X
04-0225 User is able to inquiry Single-level BoM with the additional information on the revision ID and on the change order number,
at header and at item level
UNITY- Manufacturing Reporting – Multi-level Bill of Materials Display CS12 MFG01-

FSP-MFG- User is able to inquiry Multi-level BoM launching transaction CS12 and inserting the following selection parameters: 01_0110
04-0230
 Material;
 Plant;
 Alternative BoM (mandatory if required qty not inserted);
 BoM application; X X X X X
 Valid From (date);
 Change number (optional);
 Required qty (mandatory if alternative BoM not inserted).
The system provides a report which provides all materials belonging to the multi-level BoM with details about each single
level available.
UNITY- Manufacturing Reporting – Where used List (Material) Display CS15 MFG01- X X X X X
FSP-MFG- 01_0070
04-0240 User is able to inquiry all Bill of Materials where a specific component is used launching transaction CS15 and inserting the
following selection parameters: MFG01-
01_0110
 Material;
MFG01-
 Type of where used’ list (Direct / Using classes); 01_0130
 Valid from/to (date);
423493467.doc Page 21 of 34
SMC/BINJ EU
Acist Asia
No No Reference
Acist US
Acist EU
Ezem
BDI
 Required qty;
 Plant;
 Item category;
 Usage.
The system provides a report that shows all the products (with details of BoM alternative and item) where the selected
material is used into.
UNITY- Manufacturing Reporting – Display Batch/Lot used Production Version COR3 MFG08-
FSP-MFG- 01_0100
04-0250 User is able to see which Production Version is used to produce a specific production batch/lot launching transaction COR3
and displaying the Master Data view in the PO header. In the Production Version tab it is possible to know the Production
Version used as well as the BOM explosion date.
X X X X X
423493467.doc Page 22 of 34
SMC/BINJ EU
Acist Asia
No No Reference
Acist US
Acist EU
Ezem
BDI
UNITY- Process order operations confirmation details report ZMFG027 MFG08- X
FSP-MFG- 01_0180
04-0260 The report extracts the process order operations and confirmations details with the confirmation yields and statuses-
CNF,PCNF or blank by inserting the following selection parameters.
 Process order
 Material (Process order/material are mandatory fields)
 Production plant (Set as AC01)
 Actual release date
 Actual finish date
 Basic finish date
The output fields displayed are

 Process order
 Material
 Actual release date
 Actual finish date
 Basic finish date
423493467.doc Page 23 of 34
SMC/BINJ EU
Acist Asia
No No Reference
Acist US
Acist EU
Ezem
BDI
 Operation
 Operation short text
 Operation quantity
 Operation UOM
 System Status
 Confirmation
 Confirmation yield
 Confirmation status
423493467.doc Page 24 of 34
5.4 FUNCTIONAL MESSAGE CODES & CONTENT
Message Code Message Content
N/A N/A
N/A N/A
N/A N/A
N/A N/A
423493467.doc Page 25 of 34
6. OVERVIEW OF SAP TRANSACTIONS & CUSTOMIZING ACTIVITIES

6.1 SAP TRANSACTIONS
Transaction Code Transaction Title
COR1 Create Process Order
COR2 Change Process Order
COR3 Display Process Order
COR6 Single Process Order Confirmation
CORR Collective Entry of Confirmations
CORS Cancel Process Order Confirmation
CORT Display Process Order Confirmation
COOISPI Process Order Information System
COGI Processing goods movemnts w. errors
COHVPI Mass Processing: Process Orders
MIGO Goods Movement
CS11 Display BOM Level by Level
CS12 Multilevel BOM
CS15 Single-Level Where-Used List
423493467.doc Page 26 of 34
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 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)
002 Define Status profile (BS02) SPRO/Production planning for process

industries/Process order/Master
data/Order/Define Status profile
(BS02)
423493467.doc Page 27 of 34
423493467.doc Page 28 of 34
003 Defined confirmation parameters (OPK4) SPRO/Production planning for process

industries/Process
order/Operations/Confirmation/Defined
confirmation parameters (OPK4)
423493467.doc Page 29 of 34
423493467.doc Page 30 of 34
423493467.doc Page 31 of 34
423493467.doc Page 32 of 34
Configuration activities required for all order types.
423493467.doc Page 33 of 34
7. OVERVIEW OF ADDITIONAL DEVELOPMENTS

7.1 REPORTS, FORMS
Dev. No FS-R Document Name Description FS Line No.
N/A N/A N/A
7.2 INTERFACES
Dev. No FS-I Document Name Description FS Line No.
N/A N/A N/A
7.3 CONVERSIONS
Dev. No FS-C Document Name Description FS Line No.
N/A N/A N/A
7.4 ENHANCEMENTS
Dev. No FS-R Document Name Description FS Line No.
N/A N/A N/A
423493467.doc Page 34 of 34

Unity FSP MFG 04 V01R03

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Unity FSP MFG 04 V01R03

Загружено:

Авторское право:

Доступные форматы

Project Unity Functional Specification - Process Order Confirmation

F UNCTIONAL S PECIFICATION - P ROCESS O RDER C ONFIRMATION

VERSION: 01 REVISION: 0300

Document Approval and Release

SYSTEM INTEGRATOR SILVIA FERRAZZA 18.10.2017

Document Approval and Release

ACCENTURE MARCO INTRONA

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 Marco Introna Initial Version

V01R00 10-DEC-2011 Marco Introna Approved Version

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

Last version revision information

Par. 2 Paragraph updated for GSM

Par. 3 Paragraph updated for GSM

Par. 5 Paragraph updated for GSM

Par. 6 Paragraph updated for GSM

Par. 5.3 Line UNITY-FSP-MFG-04-0260Paragraph updated added for PR279823

[1] UNITY-MFG-URS_V01R00 – Manufacturing User Requirements Specification

[2] UNITY-FSP-MFG-02 – Process Order Release Functional Specification

[3] UNITY-FSP-MFG-03 – Process Order Execution Functional Specification

1.2 DEFINITIONS & ACRONYMS

SAP Systems, Applications & Products in data processing

HFP/SP Half-finished/Semi-finished product; Terms describing an intermediate product, which

MRP Material Requirement Planning

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

RLT Replenishment Lead Time

FIFO First In First Out

FEFO First Expired First Out

S/N Serial Number

TECO Technical Completion

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/

3. SHORT FUNCTIONAL DESCRIPTION

3.1 MFG05-01_PROCESS ORDER CONFIRMATION (TIME DECLARATION)

processing. Time reconciliation is done on monthly basis, considering overall production

3.2 MFG05-02_PROCESS ORDER CLOSURE

 Process order has status ‘Final confirmation’;

User is able to inquire the list of Process Orders filtered by:

It is also possible for the user to query a Process Order by:

 Product batch number;

4. BUSINESS PROCESS FLOW CHART

 In case of “Process Order view”:

 standard values: associated to the resource in the specific couple

 The % in the field “Overdelivery tolerance” in work

 The % in the field “Underdelivery tolerance” in work

UNITY-FSP- Process Order Confirmation – Confirmation reversal/correction CORS 003 MFG05-01_0030

5.2 MFG05-02_PROCESS ORDER CLOSURE

- Planned quantities and values can be found in: MFG08-01_0060

o Order header MFG08-01_0070

- Actual quantities and values can be found in:

Deviation should be followed up and documented outside SAP by procedure within

UNITY-FSP- Process Order Closure – Error on Goods Movements COGI MFG05-02_0020 X X X X X

UNITY-FSP- Process Order Closure – Order Deletion COR2 MFG05-02_0030

UNITY-FSP- Process Order Closure – Order Freezing COR6 001 MFG05-02_0060

UNITY- Manufacturing Reporting – Single-level Bill of Materials Display CS11 MFG01- X X X X X