You are on page 1of 38

Project Unity Functional Specification - Process Order Release

P ROJECT U NITY

F UNCTIONAL S PECIFICATION - P ROCESS O RDER R ELEASE

VERSION: 01 REVISION: 0100

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

423493968.doc Page 1 of 38
Project Unity Functional Specification - Process Order Release

Document Approval and Release


ROLE NAME (AND TITLE) DATE AND SIGNATURE

IT – CORPORATE MARCO MAIOLI

BUSINESS – NORTH AMERICA LUC RAYMOND


TEAM LEAD

GQ – VALIDATION SANDRO TACCANI


COORDINATOR

423493968.doc Page 2 of 38
Project Unity Functional Specification - Process Order Release

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

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 Paragraph updated for GSM

Par. 5 Paragraph updated for GSM

Par. 6 Paragraph updated for GSM

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

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

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

[3] UNITY-FSP-MFG-01 – Process Order Creation Functional Specification

[4] UNITY-FSF-MFG-01 – Process Order Form Functional Specification

[5] UNITY-FSI-MFG-01 - Automatic batch record printout at order release (SAP ECC --> Documentum)

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.

HFP Half-Finished Product

FP Finished Product

MRP Material Requirement Planning

DMS Device Master System

DMR Device Master Record

RLT Replenishment Lead Time

TECO Technical Completion

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.

Project Project Project Process Process Subprocess Subprocess


Stream Domai Domain Code Description Code Description
n Code
Operations MFG Manufacturing MFG03 Production
Execution – Detail
Scheduling
Process Order
MFG03-03 Release
Product Batch
Numbering
MFG03-04 Generation
MFG03-05 Bundle of documents

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 Release X X X X
Product Batch Numbering X X X X
Generation
Bundle of documents X X X X

3. SHORT FUNCTIONAL DESCRIPTION

3.1 MFG03-03_PROCESS ORDER RELEASE


Order release, according to production decision, can be performed according to the following
scenarios:

 Release order by order;


 Release group of orders (i.e., by date, planner, production line) within timeframe.

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:

 MRP Elements (include Purchase Orders, Purchase Requisitions, Dependent


Requirements, Reservations);
 Inventory Category (include Safety stock, Quality Inspection stock, stock in
Transfer, Blocked stock, Restricted Use stock, Sub-contracting stock);
 Replenishment Lead Time - RLT (check with or check without RLT).

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:

 Change the start/finish date of operations;


 Select an alternative resource (if this is allowed in master data).

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.

3.2 MFG03-04_PRODUCT BATCH NUMBERING GENERATION

Batch number generation and Batch master creation are automatically performed at Process
Order Release according to the following rules:

 Semi-finished product batch number creation


The semi-finished batch number is created automatically by the system during the
release of process order for semi-finished (bulk).

 Finished product batch number creation

423493968.doc Page 7 of 38
Project Unity Functional Specification - Process Order Release

Finished Product batch number is created, automatically or manually (depending on


the batch creation rule defined for the material), during the release of the packaging
process order.

 Sub-Assembly batch number creation


Sub-Assembly batch number is created during the release of the assembly order.

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.

3.3 MFG03-05_BUNDLE OF DOCUMENTS

At process order release the system is configured to automatically prints out the Process
Order Form containing the following main information:

 Process Order Header;


 Material List (with allocated batches)1;
 Operations List;
 Documented goods movements.

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

4. BUSINESS PROCESS FLOW CHART

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

5.1.1 Individual/Collective 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).

UNITY-FSP- Step 2b: Collective Process Order Release COR5 MFG03-03_0010 X X X X


MFG-02-0030 According to data entered by the user in selection screen, the system displays
formulation/packaging/assembly production process orders. The user should not
release bulk and packaging process orders that are linked to each another at the
same time: in fact in this scenario the release of packaging orders could fail
because the semi-finished batches could not be visible in the system yet (this

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.

UNITY-FSP- Step 2b: Collective Process Order Release COHVPI MFG03-03_0010


MFG-02-0050
According to data entered by the user in selection screen, the system displays
bulk/packaging/assembly production process orders. The user should not release
bulk and packaging process orders that are linked each another at the same time:
in fact in this scenario the release of packaging orders could fail because the semi-
finished batches could not be visible in the system yet (this scenario is not relevant
in case of “Continuous Flow” because bulk materials will not be relevant for X X X X
availability check).
User is able to select either one or a set of process orders, than trigger release
process by clicking the button “Release” or selecting from toolbar the option “Mass
Processing - Execute”. The system after the execution of mass processing displays
the “Display Log” screen with the details of the order release background process.
If errors occur during saving the order, the system highlight with red traffic lights
orders not release and related error messages.
UNITY-FSP- Step 2a: Individual Process Order Release COR2 MFG03-03_0010
MFG-02-0060 In order to perform individual process order release, user has to access to
transaction COR2 with the process order number related to the PO to release.
X X X X
After pressing ‘Enter’ the system displays process order header data and the user
is able to proceed with the order release clicking on the related button and than
saving the process order in order to make release effective.

423493968.doc Page 13 of 38
Project Unity Functional Specification - Process Order Release

5.1.2 Standard SAP checks at 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).

UNITY-FSP- Step 3: Material Availability Check COR2 001 MFG03-03_0020


MFG-02-0080
During process order release process system performs automatically “Material COR5 002 MFG03-03_0070
availability check” in order to verify availability of components belonging to the
material list of the order. 003 X X X X
In case of collective process order release, if orders have missing part the system 004
displays a popup highlighting orders without stock availability and do not allow to 005
proceed with order release.

UNITY-FSP- Step 3: Material Availability Check MM01 001 MFG03-03_0030 X X X X


MFG-02-0090 The availability check is performed based on checking rules defined for “Order MM02 002 MFG03-03_0040
Type – Process Order Release” process. The following availability check controls
are defined into the system: 003
 Z4 – Stocked Raw Materials & Packaging Components; 004
 Z5 – Stocked Internally Produced Materials; 005
 KP – No check.

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: Material Availability Check N/A 001 MFG03-03_0030


MFG-02-0100
For “Stocked Raw Materials & Packaging Components (Z4)” availability check is 002 MFG03-03_0040
defined according to the following rules (for all order types):
003
X X X X
 MRP Elements (include Dependent Reservations);
004
 Inventory Category (include Safety stock, w/o subcontracting);
005
 Replenishment Lead Time - RLT (check without RLT).

UNITY-FSP- Step 3: Material Availability Check N/A 001 MFG03-03_0030


MFG-02-0110
For “Stocked Internally Produced Materials (Z5)” availability check is defined 002 MFG03-03_0040
according to the following rules (for all order types):
003
X X X X
 MRP Elements (include Dependent Reservations);
004
 Inventory Category (include Safety stock, w/o subcontracting);
005
 Replenishment Lead Time - RLT (check without RLT)

UNITY-FSP- Step 3: Material Availability Check COR2 001 MFG03-03_0040


MFG-02-0120
For materials set-up at material master level with “No Check” (KP) option the 002 MFG03-03_0050
system skips the availability check without performing any verification on stock
availability. 003 MFG03-03_0070 X X X X
004
005

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.

UNITY-FSP- Step 4: Missing mandatory manual lot allocation COR2 MFG03-02_0060


MFG-02-0140
Material master settings:
In case of materials requiring mandatory batch allocation prior release at material
master level (MRP 2 view – ‘Batch entry’ field value ‘1’) the system during process X X X X
order release verifies if the user has manually allocated the batch otherwise does
not allow to proceed with order release display an error message. Please refer to
document [3] for more details on batch/lot allocation.

UNITY-FSP- Step 5a: Process Order Release COR2 MFG03-03_0010


MFG-02-0150 After release and saving the process order the system sets automatically the COR3
following standard statuses:
 REL – Released;
 PRC – Pre-costed; X X X X
 BCRQ – Order to be handled in batches;
 MACM – Material committed;
 SETC – Settlement rule created.

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

5.2 PRODUCT BATCH NUMBER GENERATION

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

 Manual batch number insertion (Contract Manufacturing)


System forces the user to manually specify batch number into the
process order header - goods receipt screen in field “Batch” in order to
proceed with process order release. Then the system performs the batch
master creation.

 Manual batch number insertion (Configured Injector Batch


managed). For ACIST EU and SMC/BINJ EU, in order to guarantee the
traceability along the production chain, system forces the user to
manually specify batch number into the process order header - goods X X X X
receipt screen in field “Batch” in order to proceed with process order
release. By procedure the assigned batch number must be equal to the
serial number of the not configured injector.

 Automatic batch number generation (Normal Production)


Product batch number is automatically generated at process order
release according to the sequential numbering defined at configuration
level. The batch number created is allocated in process order header -
goods receipt screen in field “Batch”. Then the system performs the
batch master creation.

Please refer to [2] for more details on batch numbering rules and batch master
generation.

UNITY-FSP- Step 8: Batch/Lot Master Creation MSC1N MFG03-04_0010 X X X X


MFG-02-0180
After the batch number generation the system triggers the creation of batch/lot MSC2N
master automatically initializing standard and classification data according to pre-
defined rules and batch class information assigned on the product at material

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

5.3 BUNDLE OF DOCUMENTS

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:

 Process Order Form: generated directly from SAP X X

 Paper Master Batch Record: generated by Documentum through


direct integration with SAP (for Ezem only)

Please refer to [4] and [5] for more details.

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 COPI MFG03-05_0020


MFG-02-0220
After the execution of the report, the system displays the list of process order for MFG03-05_0050
reprinting according to the selection parameters. In order to trigger the printout X X X X
the user is able to select the orders and click on the button “Print”.

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).

Please refer to [4] for more details.

UNITY-FSP- Step 9: Batch record print-out COR2 I-01 MFG03-05_0010


MFG-02-0250 At process order release the system triggers an automatic interface to
Documentum (external Document Management System) in order to perform the COR5
print-out of approved paper batch record related to product/production version of X
the process order.
Please refer to [5] for more details.

423493968.doc Page 22 of 38
Project Unity Functional Specification - Process Order Release

5.4 PROCESS ORDER MODIFICATION AFTER 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

5.5 FUNCTIONAL MESSAGE CODES & CONTENT

Message Code Message Content

423493968.doc Page 25 of 38
Project Unity Functional Specification - Process Order Release

6. OVERVIEW OF SAP TRANSACTIONS & CUSTOMIZING ACTIVITIES


6.1 SAP TRANSACTIONS

Transaction Code Transaction Title

COR2 Change Process Order

COR3 Display Process Order

COR5 Collective Process Order Release

COHVPI Mass. Processing: Process Orders

MM01 Create Material

MM02 Change Material

MSC1N Create Batch

MSC2N Change Batch

COPI Print Process Order Shop Floor Papers

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

423493968.doc Page 26 of 38
Project Unity Functional Specification - Process Order Release

Cust. No Customizing Description with Values T. Code or Path

001 Availability Check/Define Checking rule SPRO/Production planning for


process industries/Process
order/Operations/Availability
Check/Define Checking rule

002 Availability check/Checking group (OVZ2) SPRO/Production planning for


process industries/Process
order/Operations/Availability
check/Checking group (OVZ2)

423493968.doc Page 27 of 38
Project Unity Functional Specification - Process Order Release

Cust. No Customizing Description with Values T. Code or Path

423493968.doc Page 28 of 38
Project Unity Functional Specification - Process Order Release

Cust. No Customizing Description with Values T. Code or Path

003 Availability Check/Define Scope of the check SPRO/Production planning for


process industries/Process
order/Operations/Availability
check/Define Scope of the
check

423493968.doc Page 29 of 38
Project Unity Functional Specification - Process Order Release

Cust. No Customizing Description with Values T. Code or Path

423493968.doc Page 30 of 38
Project Unity Functional Specification - Process Order Release

Cust. No Customizing Description with Values T. Code or Path

004 Availability Check/Define checking control (OPJK) SPRO/Production planning for


process industries/Process
order/Operations/Availability
check/Define checking control
(OPJK)

423493968.doc Page 31 of 38
Project Unity Functional Specification - Process Order Release

Cust. No Customizing Description with Values T. Code or Path

423493968.doc Page 32 of 38
Project Unity Functional Specification - Process Order Release

Cust. No Customizing Description with Values T. Code or Path

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

Cust. No Customizing Description with Values T. Code or Path

005 Define status selection profile (BS42) SPRO/Production planning for


process industries/Process
order/Master
data/Order/Define status
selection profile (BS42)

423493968.doc Page 34 of 38
Project Unity Functional Specification - Process Order Release

Cust. No Customizing Description with Values T. Code or Path

006 Mass Processing: Order Release  Create Variant COHVPI

423493968.doc Page 35 of 38
Project Unity Functional Specification - Process Order Release

Cust. No Customizing Description with Values T. Code or Path

423493968.doc Page 36 of 38
Project Unity Functional Specification - Process Order Release

Cust. No Customizing Description with Values T. Code or Path

423493968.doc Page 37 of 38
Project Unity Functional Specification - Process Order Release

7. OVERVIEW OF ADDITIONAL DEVELOPMENTS


7.1 REPORTS, FORMS

Dev. No FS-R Document Name Description FS Line No.

F-01 UNITY-FSF-MFG-01 Process Order Form Functional Specification UNITY-FSP-MFG-02-0190


UNITY-FSP-MFG-02-0200
UNITY-FSP-MFG-02-0230
UNITY-FSP-MFG-02-0240

7.2 INTERFACES

Dev. No FS-I Document Name Description FS Line No.

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

Dev. No FS-C Document Name Description FS Line No.

7.4 ENHANCEMENTS

Dev. No FS-R Document Name Description FS Line No.

423493968.doc Page 38 of 38

You might also like