Professional Documents
Culture Documents
P ROJECT U NITY
AUTHOR
REVIEW
YANICK GAUTHIER
APPROVAL
423493968.doc Page 1 of 38
Project Unity Functional Specification - Process Order Release
423493968.doc Page 2 of 38
Project Unity Functional Specification - Process Order Release
Document History
Paragraph # Change
423493968.doc Page 3 of 38
Project Unity Functional Specification - Process Order Release
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 MFG03-03_Process Order Release.........................................................................6
3.2 MFG03-04_Product Batch Numbering Generation................................................7
3.3 MFG03-05_Bundle of documents...........................................................................8
4. Business Process Flow Chart....................................................................................9
5. Solution.......................................................................................................................... 11
5.1 Process Order Release..........................................................................................11
5.1.1 Individual/Collective Process Order Release.....................................................11
5.1.2 Standard SAP checks at Process Order release...............................................14
5.2 Product Batch Number generation.......................................................................18
5.3 Bundle of Documents............................................................................................ 20
5.4 Process Order Modification after Release...........................................................23
5.5 Functional Message Codes & Content.................................................................25
6. Overview Of SAP Transactions & Customizing Activities.........................................26
6.1 SAP Transactions................................................................................................... 26
6.2 Customizing Activities........................................................................................... 26
7. Overview of Additional Developments.................................................................38
7.1 Reports, Forms....................................................................................................... 38
7.2 Interfaces................................................................................................................ 38
7.3 Conversions........................................................................................................... 38
7.4 Enhancements........................................................................................................ 38
1. Introduction................................................................................................................ 5
1.1 Reference Documents............................................................................................. 5
1.2 Definitions & Acronyms...........................................................................................5
2. Document Purpose..................................................................................................... 6
3. Short Functional Description....................................................................................6
3.1 MFG03-03_Process Order Release.........................................................................6
3.2 MFG03-04_Product Batch Numbering Generation................................................7
3.3 MFG03-05_Bundle of documents...........................................................................8
4. Business Process Flow Chart....................................................................................9
5. Solution.......................................................................................................................... 11
5.1 Process Order Release..........................................................................................11
5.1.1 Individual/Collective Process Order Release.....................................................11
5.1.2 Standard SAP checks at Process Order release...............................................14
5.2 Product Batch Number generation.......................................................................18
5.3 Bundle of Documents............................................................................................ 19
5.4 Process Order Modification after Release...........................................................22
5.5 Functional Message Codes & Content.................................................................24
6. Overview Of SAP Transactions & Customizing Activities.........................................25
6.1 SAP Transactions................................................................................................... 25
6.2 Customizing Activities........................................................................................... 25
7. Overview of Additional Developments.................................................................37
7.1 Reports, Forms....................................................................................................... 37
7.2 Interfaces................................................................................................................ 37
7.3 Conversions........................................................................................................... 37
7.4 Enhancements.......................................................................................................... 37
423493968.doc Page 4 of 38
Project Unity Functional Specification - Process Order Release
1. INTRODUCTION
1.1 REFERENCE DOCUMENTS
Reference Document
[5] UNITY-FSI-MFG-01 - Automatic batch record printout at order release (SAP ECC --> Documentum)
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
WM Warehouse Management
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.
423493968.doc Page 5 of 38
Project Unity Functional Specification - Process Order Release
2. DOCUMENT PURPOSE
The purpose of this document is to describe how the solution will respond to user
requirements concerning Manufacturing Process Order Release process.
For each of the above sub-processes, the following entities are in scope:
In the latter case, the system provides to the user the list of orders that have to be released
and the authorized user may decide to release all the list, a part of it (excluding some order
from it), or to include another order.
The release of an order corresponds to the final approval for starting the operations.
System performs material availability check automatically at Process Order release according
to the rules specified at Material Master level for the components (that can be grouped as
“Stocked Raw Materials” or “Stocked Internally Produced Materials”), based on the following
classification parameters:
It is also possible to set the “No Check” category for the material in order to skip availability
check for specific components (e.g., liquid bulks).
423493968.doc Page 6 of 38
Project Unity Functional Specification - Process Order Release
During material availability check the system checks the availability of all the theoretical
quantity of the components (according to what specified in the BOM).
If some components are not available after availability check, then the order cannot be
released except for specific categories of products (e.g., liquid bulks) whose material category
in the material master is set as “No Check”.
Batch allocation, if not managed during Process Order creation, is managed in background
during process order release for those materials whose Material Master setting is “Automatic
Batch Allocation at Order release”. Instead in case of materials set as “Mandatory Batch
Allocation prior Order release” the system does not allow to proceed with order release in
case of missing batch allocation on the order. No allocation is foreseen for serial numbers
that are directly declared during goods issue process. The above scenario are not applicable
for Acist EU and BINJ EU.
Furthermore, for those materials whose batch is not allocated at this stage, it will be allocated
during material replanishment to production performed by warehouse department.
Warehouse management (WM) will only use lots for components that were not allocated
before release by planning and that have a proper status. For Acist EU and BINJ EU, even if
storage location WM managed are in place, the PP-PI/WM interface for automatic
replenishment is not in scope.
For potency-based components, after batch allocation the system re-calculates BoM quantity
in Process Order material list based on actual potency value defined at Batch Master level for
the allocated Batch.
After batch/lot allocation, the quantity allocated to components is reserved on the order and
not available for other process orders.
System also triggers the automatic batch number and batch master creation at Process Order
release.
Once a process order has been released, the user only can:
It is not possible for the user to release a process order if the validity of master data (BoM,
Recipe) linked to the order at the process order creation has expired before process order
release.
Batch number generation and Batch master creation are automatically performed at Process
Order Release according to the following rules:
423493968.doc Page 7 of 38
Project Unity Functional Specification - Process Order Release
In ACIST EU and SMC/BINJ EU, in order to guarantee the traceability along the production
chain, a manual procedure drives the batch assignment for the header material in the process
order: in case of batch managed configured injector, before order release, the user should
manually declare the batch number equal to the serial number of the not configured injector.
Note: There is no link between the batch creation and the calculation of the expiration date
for the considered batch.
At process order release the system is configured to automatically prints out the Process
Order Form containing the following main information:
Process order form will contain also the following layout characteristics:
Header / Footer;
Page numbering (e.g., 1/5);
Printout date;
User Id.
Note: In case of updates in the process order, it is possible to re-print the process order form
with modified information.
EZEM only:
System divides material list in the process order print-out into two main sections:
Pre-printed materials list: containing only pre-printed materials of the process
order);
Other materials list: containing all remaining materials of the process order
(this could be either dispense at weighing or dispense at manufacturing room).
Moreover, during this phase it is possible to trigger automatic print-out of paper master batch
record from Documentum (external Document Management System - DMS).
1
For the materials whose batch is not yet allocated at the step of the process the relative step is blank.
423493968.doc Page 8 of 38
Project Unity Functional Specification - Process Order Release
423493968.doc Page 9 of 38
Project Unity Functional Specification - Process Order Release
423493968.doc Page 10 of 38
Project Unity Functional Specification - Process Order Release
5. SOLUTION
5.1 PROCESS ORDER RELEASE
Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference
SMC/BINJ EU
Acist Asia
Acist EU
Acist US
Ezem
BDI
UNITY-FSP- Process Order Release (Individual / Collective) COR2 MFG03-03_0010
MFG-02-0010 Process Order release, for all order types, can be performed according to the
following scenarios: COR5
X X X X
Manual individual release;
Manual collective release.
UNITY-FSP- Step 2b: Collective Process Order Release COR5 005 MFG03-03_0010
MFG-02-0020 In order to perform collective process order release, user has to select the created
process orders to release; during the collective process order release several
selection parameters are available for the user in order to identify required process
orders:
Process order type (optional);
Production plant (mandatory);
Production scheduler (optional); X X X X
Range of Scheduled start dates (optional);
MRP controller (optional);
Selection profile: – ZAP001 (optional) or ZAP002.
The selection profile “ZAP001” will be used to select only process orders which
have status ‘CRTD’ (Created); the selection profile “ZAP002” will be used instead
to select only process orders which have status ‘CRTD MACM” (Created and
Material committed).
423493968.doc Page 11 of 38
Project Unity Functional Specification - Process Order Release
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
scenario is not relevant in case of “Continuous Flow” because bulk materials will
not be relevant for availability check).
User is able to select either one or a set of process orders, than trigger release
process. If errors occur during the saving of the process order, the system logs
errors temporarily in the screen where the list of process orders is displayed to the
user in column ‘Result of release’. This log is temporary. Before returning back to
initial selection screen, the user can refer to the logs stored in ‘Result of release’
column.
UNITY-FSP- Step 2b: Collective Process Order Release COHVPI 006 MFG03-03_0010 X X X X
MFG-02-0040 Another alternative to perform collective order release is to use transaction
COHVPI. In order to perform collective process order release, user has to select
the created process orders to release; during the collective process order release
several selection parameters are available for the user in order to identify required
process orders such as:
List = Order Headers (optional);
Process Order (optional);
Material (optional);
Production Plant (optional);
Order Type (optional);
MRP Controller (optional);
System Status (optional);
Resource (optional);
Basic Start/End dates (optional);
Scheduled Start/End dates (optional);
Release date (optional).
A specific variant will be created in order to set-up the massive release function
selection as:
Function: Release;
Execute Function: Execute function immediately;
423493968.doc Page 12 of 38
Project Unity Functional Specification - Process Order Release
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
Processing Mode: Execute changes to data;
Max. No. of Processes: 20;
Save Log: Always;
Output logs flagged;
Display application toolbar flagged (with “Release” button selected);
Release Control Order: Order release.
423493968.doc Page 13 of 38
Project Unity Functional Specification - Process Order Release
Line No. Description of solution with Business process step number T.Code Cust. No Dev. No URS Reference
SMC/BINJ EU
Acist Asia
Acist EU
Acist US
Ezem
BDI
UNITY-FSP- The following automatic checks are performed by the system at the saving of COR2 001 MFG03-03_0020
MFG-02-0070 process order release:
002
Material availability check;
003
X X X X
Missing mandatory manual batch/lot allocation;
004
Automatic batch/lot allocation at release;
005
Master Data Validity check (Master Recipe, BoM).
Availability check rule is linked to the material at material master level for the
component (MRP 3 view). The following parameters are used in order to define
checking rules:
MRP Elements (include Purchase Orders, Purchase Requisitions,
Dependent Requirements, Reservations);
Inventory Category (include Safety stock, Quality Inspection stock,
423493968.doc Page 14 of 38
Project Unity Functional Specification - Process Order Release
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
stock in Transfer, Blocked stock, Restricted Use stock, Sub-contracting
stock);
Replenishment Lead Time - RLT (check with or check without RLT).
UNITY-FSP- Step 3: Master Data Validity check (Master Recipe, BoM) COR2 MFG03-01_0040 X X X X
MFG-02-0130
Standard SAP functionality checks the validity of BOM and Recipe copied to the
process order at the time of creation. After creating and saving the process order
the material list, operation list within the order is no longer linked with original
BOM, Master recipe master data. So during process order release, the standard
feature of SAP does not check the validity of master data.
423493968.doc Page 15 of 38
Project Unity Functional Specification - Process Order Release
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
A custom functionality is developed in order to perform the above mentioned
check according to the following scenarios:
in COR5 transaction (collective order release) the developed program
checks whether the material list, operation list contained in the process
order is still valid by comparing with master data. If the check identifies
that the material list, operation list is not valid then the process order is
not released. The reason for release failure is logged temporarily in
column ‘Result of release’. If the developed program does not identify
any errors during the check then it proceeds further.
in COR2 transaction (change order) the developed program checks
whether the material list, operation list contained in the process order is
still valid by comparing with master data. If the check identifies that the
material list, operation list is not valid then the process order is not
released. System provides error pop up message. If the developed
program does not identify any errors during the check then it proceeds
further.
423493968.doc Page 16 of 38
Project Unity Functional Specification - Process Order Release
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- Step 6a: Automatic batch/lot allocation at release COR2 MFG01-05_0070
MFG-02-0160
Material master settings: MFG03-02_0060
In case of materials requiring automatic batch allocation at order release at MFG03-02_0090
material master level (MRP 2 view – ‘Batch entry’ field value ‘3’) the system during
process order release verifies if batch has been allocated manually and, if not, MFG03-02_0100
perform automatic batch allocation following same rules valid for manual batch MFG03-02_0120
allocation process.
X X X X
Note: also with batch entry field value ‘3’, it is still possible to do a manual
allocation before release. The automatic allocation is triggered by the system in
case no manual decision has been taken.
This setting is required for potency-based materials and EZEM raw materials,
packaging components and semi-finished product managed with release order part
replenishment strategy. After batch allocation for potency-based materials, the
system re-calculates BoM quantity in Process Order material list based on actual
potency value defined at Batch Master level for the allocated Batch.
423493968.doc Page 17 of 38
Project Unity Functional Specification - Process Order Release
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- Step 7a: Batch Number creation COR2 MFG03-04_0010
MFG-02-0170 For internally produced goods different batch numbering rules are managed by the COR5 QUA05-
system according to the following scenarios: 02_0066_GSM
Please refer to [2] for more details on batch numbering rules and batch master
generation.
423493968.doc Page 18 of 38
Project Unity Functional Specification - Process Order Release
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
master data level.
Please refer to [2] for more details on batch numbering rules and batch master
generation.
423493968.doc Page 19 of 38
Project Unity Functional Specification - Process Order Release
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- Bundle of Documents generation at Process Order Release COR2 I-01 MFG03-05_0010
MFG-02-0190 At the process order release saving different kind of documents are automatically COR5 F-01
printed out:
UNITY-FSP- Step 5a: Process Order Form print-out COR2 F-01 MFG03-05_0020
MFG-02-0200
At process order release the system automatically prints-out the process order COR5 MFG03-05_0050
form containing critical information related to:
“Process Order Header” (e.g. Process Order number, order quantity,
order scheduled start/finish dates)
“Operation List” (e.g. operation number, phase number, resource)
“Material List” (e.g. component number, quantity, unit of measure,
allocated batch number)
“Order goods movements” (e.g. goods issue posting, goods issue
X X X X
reversal, goods receipt posting, goods receipt reversal)
In case not all the batches are allocated at the moment of printing the list, the
lines related to materials whose batch is not yet allocated are blank.
Note: Changes are possible until the order is not yet in production and at any
moment the user can trigger the modified Process Order form re-printing.
Please refer to [4] for more details.
(*) For ACIST EU and SMC/BINJ EU the Paper Master Batch Record print-out is
relevant
423493968.doc Page 20 of 38
Project Unity Functional Specification - Process Order Release
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- Step 5a: Process Order Form print-out COPI F-01 MFG03-05_0020
MFG-02-0210
In case of reprinting required or at the end of the order, to track into the form also MFG03-05_0050
the “Other goods movements” section with details of goods movements posted,
the user is able to trigger the dynamic reprinting of Process Order form.
Using transaction COPI with selection option “Reprint”, the user is able to launch
the process order form using the following selection parameters:
Plant;
X X X X
MRP Controller;
Order Type;
Process Order (range);
Material;
Release date;
Scheduled start/end date.
UNITY-FSP- Step 5a: Process Order Form print-out COR2 F-01 MFG03-05_0040
MFG-02-0230
Process order print-out contains the following layout information: COR5
Header/footer;
page numbering (e.g., 1/5); X X X X
printout date;
User Id.
Please refer to [4] for more details.
UNITY-FSP- Step 5a: Process Order Form print-out COR2 F-01 MFG03-05_0030 X
423493968.doc Page 21 of 38
Project Unity Functional Specification - Process Order Release
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
MFG-02-0240 Process order print-out for Ezem will be structured according to the following COR5
sections:
pre-printed materials list: containing only pre-printed materials of the
process order);
other materials list: containing all remaining materials of the process
order (this could be either dispense at weighing or dispense at
manufacturing room).
423493968.doc Page 22 of 38
Project Unity Functional Specification - Process Order Release
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- After releasing the process order, the authorized user is able to perform the COR2 MFG03-02_0140
MFG-02-0260 following changes in process order:
MFG03-03_0060
Change finish date in process order header;
Change Resource; X X X X
Change the batch allocated to a component in the material list;
Under and Over delivery tolerance;
Force order closure (TECO) in advance.
UNITY-FSP- Selecting alternative resource in the operation list of Process Order COR2 MFG03-03_0060 X X X X
MFG-02-0270
The operator accesses transaction COR2 (Process Order Change) and selecting the
‘Operation’ list screen display the list of Process Order operations and related
resources allocated. Then authorized user selects the operation for which
alternative resource is required and trigger resource selection criteria. The system
lists the alternative resources defined at master data level into the Master Recipe
and the user is able to select the required alternative resource. When order is
saved changes become effective on the order.
Resource can be changed in the operation list only until performing partial
confirmation / final confirmation of process order phase. Moreover the operator
has to check that material staging has not yet been started otherwise the staging
activities have to be reversed and repeated.
If the phase is already partially confirmed / finally confirmed, the changes made to
the resource in the operation list of process order does not have effect on the
confirmation transaction.
Pre-requisite for selection alternative resource:
o Resource class of type 019 has to be created in classification
master data. Then the resource class has to be maintained in
resource master data.
Issues/constraints in selection of alternative resources:
423493968.doc Page 23 of 38
Project Unity Functional Specification - Process Order Release
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
o When an alternative resource is selected through resource
classification, the standard values do not change. This means
that in case the alternative resource has different standard
times defined impacts on cost calculation have to be managed
manually.
For plants ACIST EU and SMC/BINJ EU, the selection of alternative resource is not
applicable.
UNITY-FSP- Changing batch allocated to component in the order material list COR2 MFG03-02_0060
MFG-02-0280
The operator accesses transaction COR2 (Process Order Change) to perform
changes in lot allocation in material list of process order. The operator selects
component (including also lines with batch allocated, if any) and trigger batch
determination.
Please refer to [3] for more details.
X X
When a batch different from that allocated in a PO is used (additional material
request), allocated batch in PO has to be deleted in order to enable staging and
consumption posting for that different batch.
If it is needed to change batch or an additional batch has to be used, changes
shall be performed in PO. In MIGO or COR6 the batch used will be always the one
allocated in the PO or if no batch is allocated in the PO, the one WM determined.
423493968.doc Page 24 of 38
Project Unity Functional Specification - Process Order Release
423493968.doc Page 25 of 38
Project Unity Functional Specification - Process Order Release
423493968.doc Page 26 of 38
Project Unity Functional Specification - Process Order Release
423493968.doc Page 27 of 38
Project Unity Functional Specification - Process Order Release
423493968.doc Page 28 of 38
Project Unity Functional Specification - Process Order Release
423493968.doc Page 29 of 38
Project Unity Functional Specification - Process Order Release
423493968.doc Page 30 of 38
Project Unity Functional Specification - Process Order Release
423493968.doc Page 31 of 38
Project Unity Functional Specification - Process Order Release
423493968.doc Page 32 of 38
Project Unity Functional Specification - Process Order Release
Note: the same configuration has to be executed for all the Order types.
423493968.doc Page 33 of 38
Project Unity Functional Specification - Process Order Release
423493968.doc Page 34 of 38
Project Unity Functional Specification - Process Order Release
423493968.doc Page 35 of 38
Project Unity Functional Specification - Process Order Release
423493968.doc Page 36 of 38
Project Unity Functional Specification - Process Order Release
423493968.doc Page 37 of 38
Project Unity Functional Specification - Process Order Release
7.2 INTERFACES
I-01 UNITY-FSI-MFG-01 Automatic batch record printout at order release (SAP ECC --> Documentum) UNITY-FSP-MFG-02-0190
UNITY-FSP-MFG-02-0250
7.3 CONVERSIONS
7.4 ENHANCEMENTS
423493968.doc Page 38 of 38