EBS 122 Cum RCD MFG MOC

E-BUSINESS SUITE
RELEASE CONTENT DOCUMENT
Manufacturing
Releases 12.1 and 12.2 (inclusive of 12.0.2 – 12.0.7)
Prepared by EBS Product Management and Strategy Teams
Last Updated: December 19, 2014

Version: 6.0
Copyright © 2014 Oracle Corporation

All Rights Reserved
Table of Contents
1. Disclaimer 1
2. Introduction 2
2.1. Purpose of Document 2
3. New and Changed Features in Oracle In-Memory Cost Management 3
3.1. Oracle In-Memory Cost Management for Discrete Manufacturing and Oracle In-Memory Cost
Management for Process Manufacturing – New Products – 12.1.3 3
3.1.1. Overview 3
3.1.2. Cost Impact Simulator (CIS) 3
3.1.3. Gross Profit Analyzer (GPA) 3
3.1.4. Cost Comparison Tool 4
4. New and Changed Features in Discrete Manufacturing 5
4.1. Oracle Discrete Manufacturing 5
4.1.1.1. Support for Contingent Worker 5
4.2. Oracle Discrete Manufacturing Extensions for Oracle Endeca 5
4.2.1. Overview 5
4.2.2. Endeca v5 7
4.2.2.1. Project Manufacturing Endeca Page 7
4.3. Oracle Mobile Discrete Production Supervisor for Oracle E-Business Suite 7
4.3.1. Overview 7
4.3.2. V.1.1.0 8
4.3.2.1. Mobile Foundation Updates 8
4.3.2.2. Accessibility Improvements 8
4.3.2.3. Client Time Zone Support in Work Order Summary Tiles page 8
4.3.2.4. Landscape Display Support Improvements 8
4.4. Oracle Cost Management 8
4.4.1. Release 12.0.4 (RUP4) 8
4.4.1.1. Iterative Periodic Average Costing (IPAC) for Brazil 8
4.4.2. Release 12.1.1 9
4.4.2.1. Iterative Periodic Average Cost Processor 9
4.4.2.2. Global Accounting Engine Forward Port to Subledger Accounting 9
4.4.2.3. Support for Landed Cost Management 9
4.4.3. Release 12.1.2 10
4.4.3.1. EMEA Joint Project - Inventory Master Book Report 10
4.4.3.2. SLA Post Down-time Upgrade as Concurrent Programs 10
4.4.4. Release 12.1.3 10
4.4.4.1. Encumbrance Accounting for Purchase Orders with Shop Floor Destination 10
4.5. Oracle Cost Management Extensions for Oracle Endeca 11
4.5.1. Overview 11
4.5.2. Terminology 12
4.6. Oracle Manufacturing Execution System (MES) for Discrete Manufacturing 13
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document ii
4.6.1. Overview 13
4.6.2. Release 12.1.1 13
4.6.2.1. Serialized Manufacturing 13
4.6.2.2. Shop Floor Device and Test Equipment Integration 13
4.6.2.3. Electronic Records and Signatures (ERES) 14
4.6.2.4. Improved Supervisor Dashboard 14
4.6.2.5. Printing Shop Floor Documentation 14
4.6.2.6. Usability Enhancements 14
4.6.2.7. Labor Skill Validation 15
4.6.3. Release 12.1.2 15
4.6.3.1. Ability to Perform Manufacturing Execution without any Dependency on the ERP System 15
4.6.3.2. Support for Detailed Routing Step in MES 15
4.6.3.3. Ability to Interface with Oracle E-Business Suite Releases Prior to Release 12 15
4.6.3.4. Web Services for Work in Process (WIP) 16
4.6.3.5. Simplified UIs for Users 16
4.6.4. Release 12.2.2 16
4.6.4.1. Enhanced Serialized Manufacturing 16
4.6.4.2. MES Operator Workstation Enhancements 16
4.6.4.3. MES UI Configurability Enhancements 16
4.6.4.4. MES Custom Extension User Exits / Hooks 17
4.6.5. Release 12.2.4 17
4.6.5.1. Resource Level Clock In/Out 17
4.6.5.2. Mass Return Components of Serialized Assembly (Dekitting) 17
4.6.5.3. 1.3Serialization APIs 17
4.6.7. Oracle Electronic Kanban - R12.2 18
4.6.7.1. Configurable and User-Friendly Graphical User Interface 18
4.6.7.2. Enhanced Planning Capabilities 19
4.6.7.3. Logical Kanban Support 19
4.6.7.4. Extensive Search Capabilities 19
4.6.7.5. Configurable Supply Statuses for Kanban Cards 20
4.6.7.6. Enhanced Supplier Kanbans 20
4.6.7.7. Replenishment Order Consolidation 20
4.6.7.8. Temporary Kanban Cards 20
4.6.7.9. Notifications and Alerts 20
4.6.7.10. Configurable Analytics Dashboard 20
4.6.7.11. Configurable Production Kanban Job Status 21
4.6.7.12. Configurable “Full” Status Tolerance 21
4.6.7.13. Import and Export Capabilities 21
4.6.7.14. Access and Security 21
4.6.7.15. Integration with iSupplier portal 21
4.6.7.16. Customizable Using the Provided Extensions 21
4.7. Oracle Quality 22
4.7.1. Release 12.1.1 22
4.7.1.1. Quality Workbench Performance Improvements 22
4.7.1.2. Quality Workbench Usability Improvements 22
4.7.1.3. Shop Floor Device and Test Equipment Integration 23
4.8. Oracle Quality Extensions for Oracle Endeca 23
4.9. Oracle Mobile Project Manufacturing for Oracle E-Business Suite 24
4.9.1. Overview 24
4.9.2. V.1.1.0 25
4.10. Oracle Shop Floor Management (OSFM) 25
4.10.1. Release 12.1.1 25
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iii
4.10.1.1. Refresh BOM/Routing of Lot Based Jobs 25
4.10.1.2. Lot Creation Using Substitute Components 25
4.10.1.3. Lot Uniqueness/Reuse of Lot Name 26
4.10.1.4. Network Routing – Lead Time Calculation 26
4.10.1.5. Lot Based Job Interface Enhancements 26
4.11. Oracle Supply Chain Globalization 27
4.11.1. Release 12.1.1 27
4.11.1.1. Buy/Sell Subcontracting 27
4.12. Oracle Outsourced Manufacturing for Discrete Industries (New Product) 28
4.12.1. Release 12.1.1 28
4.12.1.1. Buy/Sell Subcontracting 28
4.12.2. Release 12.1.3.4 29
4.12.2.1. Full Outsourcing 29
4.12.2.2. Endeca Information Discovery 30
4.12.2.3. 360 Degree View of Outsourced Manufacturing Business 31
5. New and Changed Features in Process Manufacturing 32
5.1. Oracle Inventory (Inventory Convergence) 32
5.1.1. Overview 32
5.1.2. Features 32
5.1.2.1. Dual unit of measure control for any item 32
5.1.2.2. Advanced lot control 32
5.1.2.3. Material status 33
5.1.2.4. Enhanced inventory allocation rules 33
5.1.2.5. Migrating to Oracle Inventory 34
5.1.2.6. Viewing historical data 34
5.1.3. Release 12.2 35
5.1.3.1. Advanced Catch-Weight 35
5.1.4. Product Dependencies 35
5.1.5. Third Party Integration Points 35
5.2. Oracle Process Manufacturing Product Development 35
5.2.1. Overview 35
5.2.2. Features 36
5.2.2.1. Inventory Convergence Impact on Product Development Workbench 36
5.2.2.2. Inventory Convergence Impact on Formula Management 36
5.2.2.3. Inventory Convergence Impact on Routings 36
5.2.2.4. Inventory Convergence Impact on Operations 36
5.2.2.5. Inventory Convergence Impact on Recipe Management 36
5.2.2.6. Inventory Convergence Impact on Technical Data 37
5.2.2.7. Inventory Convergence Impact on Simulator 37
5.2.2.8. Inventory Convergence Impact on Formula Analysis, Formula Inquiry, Indented BOM 38
5.2.2.9. Inventory Convergence Impact on Mass Search and Replace 39
5.2.2.10. Inventory Convergence Impact on Product Development Workflow and ERES 39
5.2.2.11. Item Substitution lists associated with the Item Master 39
5.2.2.12. Effective Formulas 39
5.2.2.13. One to One Substitutions 39
5.2.2.14. Using Substitute Items with Planning 40
5.2.2.15. Least Cost Formulation : Product Specifications 40
5.2.2.16. Least Cost Formulation : Generate Formulas based on Least Cost 40
5.2.2.17. Least Cost Formulation : Create Batches Based on Cost 40
5.2.2.18. Least Cost Formulation : Specify which Costs to use 41
5.2.2.19. Least Cost Formulation : Generate Batches without a predefined formula 41
5.2.2.20. Least Cost Formulation : Choose Materials based on Categories or Substitute Items 41
5.2.2.21. Least Cost Formulation : Select Formula/Recipe based on Least Cost 41
5.2.3. Release 12.0.6 (RUP6) 41
5.2.3.1. Fixed Process Loss 41
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iv
5.2.3.2. DFF for Step Material Associations 41
5.3. Oracle Process Manufacturing Quality Management 42
5.3.1. Overview 42
5.3.2. Features 42
5.3.2.1. Converged Inventory Modifications to OPM Quality 42
5.3.2.2. Enhanced Receiving Inspection 43
5.3.2.3. Copying Quality Specifications 43
5.3.2.4. Corrective Action Request and Tracking 43
5.4. Oracle Regulatory Management 44
5.4.1. Overview 44
5.4.2. Features 44
5.4.2.1. Regulatory Item Migration 44
5.4.2.2. Regulatory Item Properties Migration 44
5.4.2.3. Regulatory Formula Migration 44
5.4.2.4. Track the distribution of Safety Documents – Dispatch History 44
5.4.2.5. OPM Data available for export – Item Property Data 45
5.4.2.6. Document Rebuild Required Workflow 45
5.4.2.7. Regulatory Document Printing 45
5.4.2.8. Sales Order Document Required API 45
5.4.2.9. Shipping Attachment API 45
5.4.2.10. Print Regulatory Shipping Documents API 46
5.4.2.11. Regulatory Document Portal 46
5.4.2.12. Territory Profiles form 46
5.4.2.13. 3rd Party Data Change Workflow 46
5.4.3. Release 12.0.6 (RUP6) 46
5.4.3.1. OPM Regulatory Management: European Regulatory Compliance 46
5.4.4. Release 12.1.1 46
5.4.4.1. Regulatory Partner Certification 46
5.5. Oracle Process Manufacturing Process Execution 47
5.5.1. Overview 47
5.5.2. Features 47
5.5.2.1. Impact of Inventory Convergence on Process Execution 47
5.5.2.2. Screen Redesign 49
5.5.2.3. Rescheduling of Scaled Batch 49
5.5.3. Release 12.1.1 49
5.5.3.1. Multi-Batch / Support for Mass Transactions 49
5.5.3.2. Make-To-Order 50
5.5.4. R12.2 50
5.5.4.1. Oracle Process Manufacturing Outside Processing (OSP) (12.2.4+) 50
5.6. Oracle Process Manufacturing Extensions for Endeca – v5 52
5.6.1. Overview 52
5.6.1.1. Oracle Cost Management Extensions for Oracle Endeca 52
5.6.2. Endeca v5 54
5.6.2.1. Oracle Process Manufacturing Laboratory Management Visibility 54
5.7. Oracle Mobile Process Production Supervisor for Oracle E-Business Suite 54
5.7.1. Overview 54
5.7.2. V.1.1.0 55
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document v
5.8. Oracle Manufacturing Execution System (MES) for Process Manufacturing 55
5.8.1. Overview 55
5.8.2. Features 55
5.8.2.1. Batch Journal 56
5.8.2.2. Dispensing and Preweigh 57
5.8.2.3. Label Management 57
5.8.2.4. Deviation Management 57
5.8.2.5. Simplified Production Reporting 57
5.8.2.6. Improved Processing Instruction and SOP Visibility 57
5.8.2.7. Operator Certification 58
5.8.2.8. Simplified Electronic Signatures / Initialing 58
5.8.4. Release 12.0.2 (RUP2) 58
5.8.4.1. Touch Screen User Interface 58
5.8.4.2. Dispensing Area 58
5.8.4.3. Dispense Planning 59
5.8.4.4. Operator Certification 59
5.8.4.5. Least Cost Formulation Batches 59
5.9. Oracle Process Manufacturing Cost Management 59
5.9.1. Overview 59
5.9.2. Features 60
5.9.2.1. Maintain Process and Discrete Costing Applications 60
5.9.2.2. Costing of Transfers Between Discrete and Process Inventory Organizations 60
5.9.2.3. Subledger Accounting replaces MAC 60
5.9.3. Release 12.0.3 (RUP3) 61
5.9.3.1. OPM Financials: Detailed Subsidiary Ledger Report 61
5.9.3.2. OPM Financials: Non-Recoverable Taxes Support in Actual Costing 61
5.9.3.3. OPM Financials: Reconciliation Enhancements in Actual Costing 61
5.9.4. Release 12.1.1 61
5.9.4.1. Costed Indented Bill of Materials Report 61
5.9.5. Release 12.1.2 62
5.9.5.1. Support for Landed Cost Management 62
5.10. Process Manufacturing Planning 63
5.10.1. Overview 63
5.10.2. Features 63
5.10.2.1. Integration of Production Batches 63
5.10.2.2. Integration of Recipes 64
5.10.2.3. Integration of Inventory 64
5.10.2.4. Item Cost 64
5.10.2.5. Shop Calendar 64
5.10.2.6. Forecast 64
5.10.2.7. Item Substitution Effectivity Date Support 64
5.10.2.8. Firming Feedback from ASCP to OPM 64
5.10.3. Release 12.1.1 65
5.10.3.1. Resource Batching 65
5.11. OPM System Administration – Inventory Convergence Migration 65
5.11.1. Overview 65
5.11.2. Features 66
5.11.2.1. Convergence Migration 66
5.11.2.2. OPM System Administration 67
5.12. Oracle Process Manufacturing Logistics 68
5.12.1. Overview 68
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document vi
5.12.2. Features 68
5.12.2.1. Converged Inventory Modifications to Order Management 68
5.12.2.2. Move Orders enhanced to display Available Inventory 69
5.12.2.3. Automatic creation of a batch for a sales order line 70
5.13. Oracle Purchasing Integration 70
5.13.1. Overview 70
5.13.2. Features 70
5.13.2.1. Converged Inventory Modifications to Purchasing 70
5.13.2.2. Enhanced Receiving Inspection 71
5.14. Oracle E-Records 72
5.14.1. Overview 72
5.14.2. Features 72
5.14.2.1. Enable Electronic Recordkeeping for SSWA Applications 72
5.14.2.2. Electronic Recordkeeping for Mobile Transaction Framework 72
6. New and Changed Features in Manufacturing Operations Center 73
6.1. Oracle Manufacturing Operations Center – 73
6.1.1. Overview 73
6.1.2. Release 12.1.1 73
6.1.2.1. Open, Flexible Data Model 73
6.1.2.2. Customer Specific Process Parameter Monitoring Support 73
6.1.2.3. ERP Data Adaptor 74
6.1.2.4. Hierarchical Dimensions 74
6.1.2.5. Data Integration with Other Transactional Systems 74
6.1.2.6. Device Connectivity 74
6.1.2.7. Device Data Management and Contextualization 74
6.1.2.8. Time Zone Conversion 74
6.1.2.9. Error Handling 75
6.1.2.10. Role-based Dashboards 75
6.1.2.11. Manufacturing Operations Center Catalog - KPIs and Metrics 76
6.1.3. Release 12.1.2 77
6.1.3.1. Certification with Oracle E-Business Suite Release 12.0.6 77
6.1.3.2. Event Management Framework 77
6.1.3.3. EBS Adapter for Process Manufacturing 78
6.1.3.4. EBS Adapter Enhancement for Discrete Manufacturing 78
6.1.3.5. Production Quality Monitoring 78
6.1.3.6. Item Category Enhancement 78
6.1.3.7. Production Performance Reporting 79
6.1.4. Release 12.2.1 79
6.1.4.1. ODI based Data Integration Platform 79
6.1.4.2. Recalculation 79
6.1.4.3. Error Reprocessing 80
6.1.4.4. Asset Performance Dashboard 80
6.1.4.5. Production Supervisor Dashboard 80
6.1.4.6. Support for Oracle Business Intelligence Mobile 80
6.1.5. Release 12.2.3 81
6.1.5.1. Enhanced Inbound Integration with Oracle EBS 81
6.1.5.2. Outbound Integration with Oracle EBS-Discrete Manufacturing 81
6.1.6. Outbound Integration with Oracle EBS-Process Manufacturing 81
6.1.7. Release 12.2.4 82
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document vii
1. Disclaimer
This Release Content Document (RCD) describes product features that are proposed for
the specified release of the Oracle E-Business Suite. This document describes new or
changed functionality only. Existing functionality from prior releases is not described. It
is intended solely to help you assess the business benefits of upgrading to the specified
release of the Oracle E-Business Suite.
This document in any form, software or printed matter, contains proprietary information
that is the exclusive property of Oracle. Your access to and use of this confidential
material is subject to the terms and conditions of your Oracle Software License and
Service Agreement, which has been executed and with which you agree to comply. This
document and information contained herein may not be disclosed, copied, reproduced or
distributed to anyone outside Oracle without prior written consent of Oracle. This
document is not part of your license agreement nor can it be incorporated into any
contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in
planning for the implementation and upgrade of the product features described. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all
features described in this document without risking significant destabilization of the code.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Purpose of Document 1
2. Introduction
2.1. Purpose of Document

This Release Content Document (RCD) communicates information about new or changed
functionality introduced in Oracle E-Business Suite Releases 12.1 and 12.2, and in
subsequent Release Update Packs (RUPs) and off-cycle patches. For your convenience,
it also includes new or changed functionality introduced in the RUPs for Release 12,
including 12.0.2 through 12.0.7.
The features and enhancements described in this document are grouped by product, and
then by the release in which they first became available, for example, “Release 12.1.1”.
Features released in an off-cycle patch have a special designation – for example, a feature
released after 12.1.1, but before 12.1.2, is designated as “Release 12.1.1+”.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Purpose of Document 2
3. New and Changed Features in Oracle In-Memory Cost
Management
3.1. Oracle In-Memory Cost Management for Discrete Manufacturing and

Oracle In-Memory Cost Management for Process Manufacturing – New
Products – 12.1.3
3.1.1. Overview
Oracle In-Memory Cost Management is a new set of application tools that provides a
bottoms-up approach to maximizing profit margins by enabling near real-time insight into
all aspects of cost management. Oracle In-Memory Cost Management’s extreme
performance is possible because of the game-changing technical innovations within
Oracle’s engineered systems, including smart scans, flash cache, and high-bandwidth low-
latency InfiniBand networking.
Cost accountants and finance / operations managers now can use Oracle In-Memory Cost
Management to quickly perform what-if simulations on complex cost data and instantly
visualize the impact of changes to their business. Specifically optimized for Oracle’s
engineered systems, Oracle In-Memory Cost Management provides a suite of solutions to
perform complex cost analyses, identify optimal profit margins, and perform cost planning
and forecasting so that companies can make decisions in time to capture the highest
possible profits, safeguard current margins and identify optimal future margins, streamline
financial overview across the supply chain, and increase financial close efficiency.
The products consist of three components:
3.1.2. Cost Impact Simulator (CIS)

Simulations show the impact of product cost variations from bills of materials, routings,
resources, and overheads. The Cost Impact Simulator is used for analyzing the impact on
Cost of Goods Sold and gross profit margins originating from costs in on-hand quantity,
inventory, and work in process. You have the ability to perform comprehensive what-if
analysis on complex multi level bills of materials and routings in near real-time. This tool
replaces the manual labor intensive process of translating the impact of cost changes into
the price list. You can investigate the impact of a cost change by identifying the cost
components providing the new rolled up costs. This enables real-time simulation
capability for cost impact on product margins to analyze and plan target costs, and predict
margins based target cost scenarios.
3.1.3. Gross Profit Analyzer (GPA)
The Gross Profit Analyzer uses Oracle Business Intelligence Enterprise Edition (OBIEE)
technology. There are two methods for invoking the GPA. You can navigate from CIS to
analyze the downstream impacts of changes to costs (components, resources, and
overheads), on Cost of Goods Sold and margins (actual, planned, and forecasted). You can
also navigate directly to GPA from the Navigator to analyze actual versus /simulated
COGS and margins.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content DocumentOracle In-Memory Cost Management for Discrete Manufacturing and Oracle In-
Memory Cost Management for Process Manufacturing – New Products – 12.1.3 3
3.1.4. Cost Comparison Tool
The In-Memory Cost Management Cost Comparison tool provides the ability to
compare detailed indented assembly and recipe costs across different plants and
organizations. Costs are presented in a side by side view. This enables you to view costed
bills or recipes and associated elements, investigate differences, and take actions on costs
impacting profitability.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content DocumentOracle In-Memory Cost Management for Discrete Manufacturing and Oracle In-
Memory Cost Management for Process Manufacturing – New Products – 12.1.3 4
4. New and Changed Features in Discrete Manufacturing
4.1. Oracle Discrete Manufacturing

4.1.1.1. Support for Contingent Worker
This customer driven enhancement includes support for adding contingent workers as
resources on an Oracle WIP Work Order. Contingent workers work for companies on a
non-permanent basis and can include consultants or outside contractors. This is a very
common practice in manufacturing operations.
4.2. Oracle Discrete Manufacturing Extensions for Oracle Endeca

4.2.1. Overview
Oracle Discrete Manufacturing Extensions for Oracle Endeca is a new revolutionary
information discovery application from the Oracle E-Business Suite Extensions for
Oracle Endeca solution set. It allows shopfloor users to quickly find actionable
information in real time, improve their productivity and meet customer commitment. It
enables customers manage their manufacturing operational costs and leverage their
investment in Oracle E-Business Suite Discrete Manufacturing and Manufacturing
Execution Systems for Discrete Manufacturing.
Real Time 360 Degree view of Discrete Work Orders
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Discrete Manufacturing 5
Key Features:
• Real Time Work in Process Progress Insights: In order to achieve high
productivity and efficiency on the shopfloor, it is critical that the managers and
supervisors have real time view of the shopfloor at their fingertips. Oracle
Discrete Manufacturing Extensions for Oracle Endeca provides the real time
view of the shopfloor work orders, across organizations and departments that the
users have access to. It empowers the shopfloor users to gain quick insights at
both high level and at granular level on the work order information by syncing
discrete work order data from E-Business Suite manufacturing as frequently as
desired, up to near real time. Supervisors can quickly monitor the impact of the
delayed work orders on a color-coded dashboard and get to the reasons for
specific delays like components shortages, resource shortages, open exceptions,
quality issues etc very quickly.
• 360 Degree View of Current Work Orders: In a traditional search, user would
need to specifically know the exact search criteria on what they were looking for
and had a limited view of the results. The revolutionary search interface guides
the shopfloor managers and supervisors to visualize the real time issues on the
shopfloor. It provides a 360 degree view of open work orders for both in-house
and outsourced manufacturing operations. The extension allows the shopfloor
users with a shopping type of experience to explore all relevant work order data
to uncover the manufacturing bottlenecks and take corrective action quickly to
meet their customer commitments. The new dynamic and modern user interface
guides the user towards discovering answers to questions of specific interest
faster in the context of managing current challenges on the floor. Endeca search
allows employees to immediately access the most critical manufacturing
workorders rapidly and manage components shortages, resource bottlenecks and
other shop floor exceptions to avoid customer order delays.
• Manufacturing Exceptions Management: Exception data is graphically
displayed so that a user can quickly identify the customers and jobs impacted. A
dashboard highlights the most frequent number of unresolved exceptions with the
ability to drill down to analyze the root cause and take corrective actions.
Supervisors can quickly view the customers impacted because of shortages and
find available substitutes. A spreadsheet like view of all exception data –
impacted job, Operation sequence, date reported and contact and exception notes
• Work in Process Quality and Cost Variance Insights: Graphically identify the
work orders and assemblies that are impacted by scrap and rejects reasons to
discover current quality issues in the shop floor quickly. Quickly identify the jobs
and customers with low yield rate data to take remedial actions and improve
productions efficiency. Indentify the jobs where cost variances are high.
• Outside Processing Operation Insight: Quickly identify identify subcontract
order delays early and adjust production schedules to meet on-time customer
delivery and as necessary, identify alternate supplier to help mitigate outside
processing quality non-conformance problems
• Modern Technology with Mobility: In-memory technology platform, Key
production metrics, Mobile user friendly interactive summary charts, alerts, tag
clouds and Guided navigation for work order information discovery, search
structured attributes and unstructured text like exception notes, assembly and
component description etc.
• Fully integrated with Oracle E-Business Suite: Seamless navigation to work
content pages in Manufacturing Execution systems for Discrete Manufacturing
and work order FORM in Work in Process. Honors the same Organization
security configured in E-Business suite at run time instantly.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Discrete Manufacturing Extensions for Oracle Endeca 6
4.2.2. Endeca v5
4.2.2.1. Project Manufacturing Endeca Page

• Oracle Project Manufacturing Visibility: Leverage alerts, graphs, charts and
key summarized metrics to identify potential risks to project performance and
take immediate action. Dashboard access lets you quickly view important
information about projects, work orders, tasks or task assignments that can
potentially affect the schedule or profitability and make quick updates. You can
use the alerts, charts, graphs and metrics provided out-of-the-box or easily and
quickly configure your own.
Features include:
• 360 Degrees of Projects– Using the new project search and overview, alerts
help you discover the projects at risk. Use the alerts provided to identify late or
unapproved projects or easily configure your own. Use the cost analysis graphs
and charts to compare actual costs and identify the projects with the best or worst
performance against their cost budgets. The project delays chart helps you
quickly see the projects that have not started on time and the summarized metrics
provide at-a-glance financial totals for the projects in your operating unit.
Project Manufacturing Search and Overview Alerts and Summarized Metrics
• Project Dashboard access to project, work orders and task information using
alerts, graphs and summarized metrics
• Guided Navigation - Find projects, tasks, work orders and assignments
• Interactive tables with detailed project, work order, task and plan information
reduces navigation to multiple pages
• Use quick links to initiate project actions or update multiple tasks in a single
update
4.3. Oracle Mobile Discrete Production Supervisor for Oracle E-Business Suite
4.3.1. Overview
With Oracle Mobile Discrete Production Supervisor for Oracle E-Business Suite, discrete
manufacturing supervisors can monitor work in process and take quick actions on the go.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content DocumentOracle Mobile Discrete Production Supervisor for Oracle E-Business Suite 7
- Search or barcode scan work orders to view progress (on track, delayed, on hold,
exceptions)
- View work order and operations detail
- Perform quick actions like expedite, hold, release, unrelease, cancel and add notes
- View component issue and resource charges
- Manage production exceptions related to assembly, components, resources and quality
- Collaborate in transaction context using device features such as email, phone and text
Oracle Mobile Discrete Production Supervisor for Oracle E-Business Suite is compatible
with Oracle E-Business Suite 12.1.3 and 12.2.3 and above. To use this app, you must be a
user of Oracle Discrete Manufacturing, with mobile services configured on the server side
by your administrator. Users of Oracle Manufacturing Execution System for Discrete
Manufacturing get additional capability for exception management.
4.3.2. V.1.1.0
4.3.2.1. Mobile Foundation Updates

• Improvements in login and configuration flow
• Ability to change server URL without reinstalling app
• Diagnostics improvements
4.3.2.2. Accessibility Improvements

There are accessibility improvements in the Work Orders Tile page, Related Information
contextual tab bar, and Person contact card.
4.3.2.3. Client Time Zone Support in Work Order Summary Tiles page
Client time zone support is available in the Work Order Summary Tiles page.
4.3.2.4. Landscape Display Support Improvements

There are landscape display improvements for the Work Order Number in the Work
Order list, and in the Work Order Detail page header.
4.4. Oracle Cost Management

4.4.1. Release 12.0.4 (RUP4)
4.4.1.1. Iterative Periodic Average Costing (IPAC) for Brazil

This enhancement supports a legal mandate for Brazilian customers. Under Brazilian
Law, the cost of inter-organization transactions must include the actual absorption cost of
the items that have been transacted. Periodic costing has been enhanced to calculate the
cost of these transactions, including all input costs. This was available in 11.5.10 as
PACP.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Cost Management 8
4.4.2. Release 12.1.1
4.4.2.1. Iterative Periodic Average Cost Processor

Oracle Cost Management Release 12.1.1 extends the capabilities found in the Periodic
Average Cost (PAC) method through the addition of a new Iterative Periodic Average
Cost Processor (IPAC). The new IPAC processor allows you to more accurately cost
recursive Inter-Org transfers between organizations that are in different PAC cost groups.
When two PAC cost groups perform inter-org shipments of an item to each other, the
periodic cost of the item in each source org can only be calculated at the end of the
accounting period. However when an item is transferred back and forth between a pair of
PAC cost groups for example, the cost of the period transfers in each org can only be
calculated by simultaneously deriving the cost in each organization while factoring in the
cost of the as yet uncosted transfer transactions.
The new IPAC process resolves such bilateral transfer cost dependencies by recursively
calculating the cost in each PAC cost group.
4.4.2.2. Global Accounting Engine Forward Port to Subledger Accounting

The Global Accounting Engine (AX) functionality has been forward ported to Subledger
Accounting (SLA) Release 12.1.1, as this functionality did not exist in base Release 12.
The implementation of the Permanent Inventory Accounting feature in Subledger
Accounting Release 12.1.1 is necessary to provide an upgrade path for European
customers using the corresponding Global Accounting Engine feature in Oracle 11i.
Release 12.1.1 provides Subledger Accounting (SLA) rules with the same functionality
that was available with the Global Accounting Engine (AX) rules in previous releases.
Oracle 11i customers using AX for specific European requirements on top of CST will be
able to upgrade to Release 12.1.1 using seeded Subledger Accounting (SLA) definitions
that replace the Permanent Inventory Rules provided by the Global Accounting Engine in
Release 11i.
• All the accounting events for which AX creates journal entries in Release 11i are
accounted for Release 12.
• The accounts derived in SLA through the Account Derivation Rules match the
ones derived in AX.
• The Journal Entry Descriptions created by SLA match the ones assigned by AX
Permanent Inventory Rules.
• All the sources used in conditions in AX are available in SLA, so that similar
journal entries can be created under the same conditions.
• The journal entries created by SLA are equivalent to the ones created by AX.
4.4.2.3. Support for Landed Cost Management

Landed Cost Management Release 12.1.1 is available and supported with Oracle Cost
Management. The Landed Cost is calculated in order to accurately measure the
corporation’s costs and profitability by the good/item, product line, lot, business unit,
organization, etc. They play a significant role in actual costing, evaluating on-hand
inventory, as well as setting sales prices and revenue forecasting.
Oracle Cost Management supports the ability to cost buy items with Estimated Landed
Cost and Actual Landed Cost, Inventory valuation with ELC and ALC towards achieving
more accurate cost than just PO price and accounting distributions for Estimated Landed
Cost and Actual Landed Cost.
4.4.3. Release 12.1.2
4.4.3.1. EMEA Joint Project - Inventory Master Book Report

As per Italian legal requirements all first party legal entity should submit the Inventory
Master Book Report to the internal and external auditors when required to show the
movements of all inventory transactions between inventory organizations and
subinventories with in the same legal entity including opening and closing balances of all
items.
The Inventory Master Book has been changed in order to meet Italian and Chinese legal
requirements. In Italy Inventory Master Book report is mandatory for all Italian legal
entities with an inventory entity (manufacturing facility, warehouse, etc). For all first
party legal entity all inventory movements within a date range should be displayed in the
Inventory Master Book report. The report will print Ledger for Chinese requirements and
now is a report running parameter. This report will display opening inventory of all items
along with transactions and closing inventory balances of all inventory items. The report
a) must be submitted by first party legal entity, Per Ledger, Date range (like it is in the
existing report version), Inventory Organization, and Subinventory Organization; b) will
break per Item, per Inventory Organization, per Subinventory Organization or per a mix
of them.
It is required that the Inventory Master Book prints for the first party legal entity all items
transactions movements occurred in the Inventory and Subinventory Organizations
within the specified date range. Thus the new report version will continue to be submitted
within a date range (like it is in the existing report version). In Italy, all statutory reports,
official documents and official letters must print the first party legal entity identification
information, the page numbering according to the Italian laws and Italian fiscal authority
specifications. The amounts in the statutory reports are shown in the functional currency.
4.4.3.2. SLA Post Down-time Upgrade as Concurrent Programs

The objective is to decrease the volume of data upgraded to R12 when there is no need
for it. For e.g., for PO and AP encumbrance reversal only open PO needs to have XLA
distribution links when prior account entries need to be reversed. With the current
upgrade strategy, the customer is mandated to upgrade all sub ledgers data for all ledgers,
increasing unnecessarily the volume in XLA Distribution links, leading to administration
and performance issues.
With this objective in mind SLA has a new concurrent program “Upgrade Historical Sub
ledger Transaction Accounting” which can be used to upgrade the old data to SLA for a
particular product and ledger. The scope of this document is to discuss on the Costing
API changes done to support the XLA concurrent program.
4.4.4. Release 12.1.3
4.4.4.1. Encumbrance Accounting for Purchase Orders with Shop Floor Destination
Customers need to better control their expenses to avoid over-spending of their budgets.
For Public Sector, budget regulation is a statutory requirement.
The budgetary control is done during PO entry process.
For PO requisition approval: the fund booked is a commitment.
For PO Purchase Order approval: the fund booked as an obligation.
During the receiving of those purchased goods, the amount necessary for the acquisition
of those items will generate actual accounting entries. The fund previously booked will
be relieved when the actual accounting entries are created. This procedure is called
encumbrance reversal.
Cost Management is responsible for the actual accounting during the receiving process,
and relieves the fund previously booked by generating an encumbrance reversal
distribution representing the amount previously booked proportionate to the quantity
being received.
In EBS release 12.1.2, the implementation of encumbrance reversal for SCM is limited to
Inventory and Expense Receiving transactions. Now in release 12.1.3, this functionality
has been extended to Shop Floor destination Purchase Orders, where the distributions
will be created under WIP transactions.
Note for EAM Work-Order and OSP transactions: This approach will be implemented for
Shop Floor Destination Purchase Orders and customers are able to use encumbrance
accounting for the maintenance works.
4.5. Oracle Cost Management Extensions for Oracle Endeca

4.5.1. Overview
Oracle Cost Management Extensions for Oracle Endeca allows users to discover
transactions and related accounting information in real time thereby providing
opportunity to effectively manage the period close process, reconcile accounting as well
as ensure accuracy of accounting across sub ledgers. There are two intuitive user-
interfaces – the Period Health Check helps to discover transactions that are either
preventing or delaying period close and the Transaction Accounting Register assists in
reconciliation of accounting for all supply chain subledgers .
Period Health Check
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Cost Management Extensions for Oracle Endeca 11
Transaction Accounting Register
Key Features:
• Search Assistance: As End Users type in Search Box, the list of matching
values in key attributes like Organization, Transaction, Job, Receiving,
Maintenance, Project and Transfers are displayed for Period Health Check. For
Transaction Accounting Register the attributes include Organization, Job,
Account, Transaction, Receiving and Write-off
• 360 degree view of Pending Transactions and Incomplete Account Entries:
Supervisors can quickly monitor the impact of the unprocessed material and
shipping, pending transactions and interfaces and incomplete workorders on a
color-coded dashboard.
• Fully integrated with Oracle E-Business Suite: Fully integrated with Cost
Management and honors the same Organization security configured in E-
Business suite at run time instantly.
4.5.2. Terminology
Term Definition
PAC Periodic Average Cost method. Items are costed in a costing

process run at the end of an accounting period.
IPAC Iterative Periodic Average Cost Processor. The IPAC process
costs items that are transferred recursively between PAC cost
groups.
PAC Cost Group A group of inventory organizations whose items are costed
using Periodic Average Cost
Recursive Transfer An item that is transferred out of and into a PAC cost group
one or more times in the same accounting period.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Cost Management Extensions for Oracle Endeca 12
4.6. Oracle Manufacturing Execution System (MES) for Discrete
Manufacturing
4.6.1. Overview
To remain competitive in today’s global marketplace, several businesses have adopted a
“Distributed Manufacturing” model by running multiple manufacturing facilities located
across the globe. Adopting this approach helps in reducing costs, improving agility to
serve local markets and most importantly, gives the ability to retain control on the
manufacturing process execution globally.
In such environments, it is quite likely that each manufacturing plant within a business
may either be running a unique set of applications or relying on a centralized system
(such as ERP) to perform the day-to-day manufacturing functions. For businesses that
have deployed a centralized system for reporting manufacturing activities, at times, shop
floor work progress is hindered due to the non-availability of the application system. This
could be for reasons such as planned maintenance, network issues, etc. In yet other
situations where several manufacturing applications are used across plants, it is essential
that systems working at a plant level are connected to each other or a corporate level
system (such as ERP) for global monitoring of manufacturing operations. Hence, it is
extremely imperative for these businesses to have an application framework that
supports:
• 24x7 plant level manufacturing operations
• Real-time event driven operations management
• Global visibility, and control of manufacturing processes across multiple plants
and multiple applications
4.6.2. Release 12.1.1
4.6.2.1. Serialized Manufacturing

To improve product traceability and genealogy, many production environments require
that an assembly serial number be identified and associated with the product at either the
start of production, or at a specific step within the production process. In the past, in-
process serialized transactions were supported only through Mobile Supply Chain
Applications. In this release, MES for Discrete Manufacturing supports this functionality
by allowing operators to query one or many serial number(s) to retrieve work content
information, easily record component serial information and quality results, and perform
transactions. Operators can also continue to use the dispatch list, which will list both
serialized and non-serialized assemblies in their queue.
4.6.2.2. Shop Floor Device and Test Equipment Integration

Most shop floor environments have test equipment or other devices that capture
information about the product being produced. To allow more automated quality data
collection, this release will allow this device data to be captured directly into a quality
collection plan associated with the move, scrap, reject, complete and return assembly
transactions in the MES module. In addition, device data can also be collected in the
standalone quality entry mode. The device integration has been enabled through the
KEPServerEX MES Connector provided by Kepware Technologies (Oracle Certified
Partner) to connect to the shop floor devices.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content DocumentOracle Manufacturing Execution System (MES) for Discrete Manufacturing 13
4.6.2.3. Electronic Records and Signatures (ERES)
Electronic Records and Electronic Signatures (ERES) capability is required to support
FDA’s 21 CFR Part 11compliance for medical device manufacturers who need to adhere
to the functional requirements of the quality system specified in 21 CFR Part 820. In this
release, ERES capabilities have been provided for moves, completions, returns and
component material transactions associated with the discrete jobs in the MES
workstation. Any quality information collected as part of the MES transactions are also
included as part of the electronic record.
4.6.2.4. Improved Supervisor Dashboard

To aid the supervisor in managing his organization’s shop floor performance, additional
metrics have been added to the supervisor’s dashboard: Production to Plan by
Department, Labor Performance (Efficiency, Productivity and Utilization), First Pass
Yield, and Defective Parts per Million. In all cases, the supervisor can see a summary
view of performance for the past week when he or she enters the dashboard, and then can
drill to additional details. To support the labor performance metrics, shift in and shift out
capability has been added, and data can be imported from a time and attendance system.
Extending the theme of capacity shortages view in Release 12, additional tools have been
provided in this release. To aid decision making during shop floor execution, the
supervisor will have two views – a work order view that provides information on
component and resource shortages at the work order level; the second view provides a
view of the potential component shortages. From the work order view, supervisors can
then change the job status as appropriate based on the information provided to ensure
smoother shop floor execution.
4.6.2.5. Printing Shop Floor Documentation

The focus of the MES module has been to provide all the information required so that the
shop floor operator can perform and complete the production operations. However there
are situations where it is required to print all the information that is pertinent to a
manufacturing work order so that it can accompany the physical parts and assemblies
through the production process on the shop floor. From this release, operators and
supervisors can view and print a configurable job traveler and/or labels from MES for
Discrete Manufacturing.
4.6.2.6. Usability Enhancements

A major focus of this release has been to improve the overall usability of the MES
workstation. Examples of enhancements in this area include the addition of inline quality
results entry so the user doesn’t have to navigate to a separate page to enter quality
results, user sorting capabilities on the dispatch list, exception history visibility, an
association between exception types and reason codes.
In addition, to add flexibility to the system two new hooks (client extensions) are being
introduced:
• Ready-Status: In addition to the current seeded criteria, the ready-status in the
dispatch list also depends on the ready-status hook’s returned result. Customers
can implement their own validation by plugging in custom code in this hook.
Example of custom logic may be checking whether a sales order is on hold, all
components haven’t been picked, etc.
• Transaction Validation: Move, scrap, reject, and completion transactions are
disallowed if the custom validation implemented in this hook fails. Examples of
custom logic may be implementing tooling validation logic, or checking to see if
all push-type materials have been issued.
4.6.2.7. Labor Skill Validation
The purpose of Labor Skill Validation is to ensure the operator who handles the
manufacturing activities and the quality inspector who handles the inspection activities
(as part of the manufacturing operations) have the right qualifications and required
competencies at appropriate skill levels and required certifications to enable the operator
to perform the assigned functions. ISO quality standards and also regulatory requirements
for specific industries mandate companies to execute and document employee
competencies.
In this release, the MES for Discrete Manufacturing can check for required skills for the
operator who performs the operation when the operator clocks into a job operation or
during critical move transactions, such as move, scrap, reject or return transactions. This
check leverages HRMS for defining competencies, skill levels, certifications and
qualifications, and associating them with the employee.
4.6.3. Release 12.1.2
4.6.3.1. Ability to Perform Manufacturing Execution without any Dependency on the

ERP System
Manufacturing Execution System (MES) for Discrete Manufacturing module enables
manufacturers to deploy Oracle Applications directly as their shop floor execution system
without complex and costly integrations with third party manufacturing execution
solutions. Currently, MES works on top of Oracle WIP and requires the Oracle E -
Business Suite production instance to be up and running for performing shop floor
transactions through MES. Because of this dependency, shop floor personnel do not have
a way to report transactions through MES if the central ERP production instance is
temporarily unavailable due to bandwidth issues (especially in remote locations),
patching or in the event of any other maintenance activity being carried out. To reduce
this dependency, an implementation option is now provided using the Oracle Data
Integrator (ODI), to run the MES application independently, in a standalone mode,
allowing shop floor personnel to report transactions even when the central ERP
production instance is down. The transactions reported through MES are synchronized at
a later point of time when the backend ERP system is functional. This is especially
important in large companies with multiple facilities and having operations around the
globe.
4.6.3.2. Support for Detailed Routing Step in MES

From mfg execution perspective, niche MES solutions maintain detailed routing steps
within their solution to report and track the progress made in production. However, the
corresponding routing maintained in the ERP system is simplified and represents the key
steps for costing of material and resources. Detailed routing steps are maintained in MES
and have a mechanism/representation to indicate the operations/steps that need to be
reported back to ERP.
4.6.3.3. Ability to Interface with Oracle E-Business Suite Releases Prior to

Release 12
Currently, MES for Discrete Manufacturing is available for deployment on Release 12
and above. Several existing customers running on 11i10 have opted to use MES on top
of their current EBS installation. MES is now able to interface and work with Oracle E-
Business Suite releases prior to Release 12, specifically Release 11i10.
4.6.3.4. Web Services for Work in Process (WIP)
Web services are being provided for key WIP transactions. As part of this enhancement,
web services are provided by exposing business logic contained within Oracle forms
through Java APIs. These web services are cataloged in the Oracle Integration Repository
and can be browsed though Oracle Integration Repository Browser Interface under
respective product family node. By Clicking on the Business Entity in Integration
repository, you can view full description, list of web services for that business entity
along with the description of the web service, whereas description of parameters can be
seen from the xsd definition of the service available via the generated wsdl.
The following web services are provided for WIP:
• WIP Discrete Job: Create WIP discrete job
• WIP Move Transaction: Create WIP Move Transaction
• WIP Completion Transaction: Create WIP Completion Transaction
4.6.3.5. Simplified UIs for Users

Using Oracle ADF, the web services being provided in WIP can be leveraged to easily
create custom-made simplified UIs for shop floor operators as an alternative to out of the
box UIs.
4.6.4. Release 12.2.2
4.6.4.1. Enhanced Serialized Manufacturing

To improve product traceability and genealogy, many production environments require
that an assembly serial number be identified and associated with the product at either the
start of production, or at a specific step within the production process. And MES for
Discrete Manufacturing supports this functionality. There are specific capabilities added
to significantly improve the Serialized Manufacturing execution in this release which
include,
• Improved scanner friendly user interface to perform express material issue and
return transactions for both serialized and non-serialized components, including
ability to provide component serial attributes for specific assembly serial number.
• Ability to easily identify required, issued and open component quantities during
material transaction in the context of specific assembly serial number.
• User friendly warning and error messages in the context of specific assembly
serial number during material transactions.
• A clear 360 degree detail view user interface for each assembly serial number
listing required, issued and open components, ability to quickly filter and review
component issues, component serial numbers and component serial attributes,
move transactions and quality plan results etc
4.6.4.2. MES Operator Workstation Enhancements

The MES operator user interfaces are enhanced to display the Clock-In Context
Information and provide control over Operator simultaneous Clock-In.
4.6.4.3. MES UI Configurability Enhancements

The following enhancements are implemented around MES configurability,
• Ability to configure Custom UI Actions from the global action dropdown list
• Ability to control Operator Simultaneous Clock-In
• Ability to enter ‘Incomplete’ as the Requisition Status when creating OSP
Purchase Requisition
4.6.4.4. MES Custom Extension User Exits / Hooks

The following user exits/custom hook points are added.
• Custom user exit/hook for managing next operation step defaulting during both
standard and express move
• Custom user exit/hook for managing component lot selection during express
move
• Custom user exit/hook for managing express complete during express move
4.6.5. Release 12.2.4
4.6.5.1. Resource Level Clock In/Out

To improve time reporting capabilities, MES operators work can captured at a lower
level of granularity. The ability to clock in and out of a resource has been added
• Ability to configure at the Time Entry Mode parameter for all resources or
selected resources
• Ability to clock in/ out of a resource will be available from multiple MES entry
points including Dispatch list, Work Content and Search Serial pages
4.6.5.2. Mass Return Components of Serialized Assembly (Dekitting)
To improve productivity when disassembling an assembly serial and returning

components to stores, a new mass action has been added
• New Mass Return component in Global Actions Menu

• Initiates returns of all component serials, lots used in manufacture of an assembly
serial back into inventory. There is support for both cases, when assembly serial
belongs to open and closed work orders.
4.6.5.3. 1.3Serialization APIs

Assembly move, completion & component material transactions are now possible for
serialized assemblies through the standard open interfaces. Earlier these transactions were
possible only through the transaction user interfaces for serialized assembly work orders.
4.6.6. Terminology
Term Definition
Serialized Job A serialized job is a discrete job that has pre-defined and
associated assembly serial numbers. After the serialization
start operation, the progress on the shop floor is tracked using
the assembly serial number.
Genealogy Genealogy is the ability to provide complete history of a
finished product or a sub assembly by identifying the
lot/serial number of the assembly as well as the components
and their quantities, lot/serial numbers etc. This is a
requirement for industries/manufacturers that have to meet
traceability needs.
Term Definition
Job Traveler Job Traveler or shop packet is a set of documents associated

with a work order that travels with the assemblies as it moves
through the routing in the shop floor. It usually consists of
setup and work instructions, list of components and required
quantities, bar code labels, operation details and any other
relevant information that will aid the completion of the work
order. In some cases, it may also include spaces for
operators/inspectors to place their initials after
inspection/verification steps.
4.6.7. Oracle Electronic Kanban - R12.2

Oracle Electronic Kanban (E-Kanban) provides a complete solution for kanban
management enabling complex kanban planning, setup, execution, and kanban related
analytics and notifications. Built using Oracle’s latest technology for user interfaces,
Oracle Application Development Framework, the comprehensive, user friendly, and
configurable E-Kanban workstation provides you with both an overall view of kanban
cards and pull sequence details as well as allowing you to perform transactions within a
single user interface.
Integrated with Oracle E-Business Suite’s planning products, E-Kanban provides the
ability to simulate, plan and replan your kanban pull sequences allowing you to optimize
both your production and inventory management. Production, supplier, inter-organization
and intra-organization kanbans are all supported.
Oracle E-Kanban provides you with:
• Configurable and user friendly graphical user interfaces
• Extensive search capabilities
• The ability to view kanban cards, pull sequences, and carry out transactions
within a single user interface
• The ability to scan and transact kanban cards
• The ability to simulate, plan and replan kanban pull sequences from a single
user interface
• Configurable alerts and notifications
• Configurable analytics dashboard
• The ability to customize the solution using the provided extensions.
4.6.7.1. Configurable and User-Friendly Graphical User Interface

Built using Oracle’s latest technology for user interfaces, Oracle Application
Development Framework, the comprehensive, user friendly, and configurable E-Kanban
workstation provides you with both an overall view of kanban cards and pull sequence
details as well as allowing you to perform transactions such as card replenishment,
receipt and card status changes within a single user interface. Using the kanban card
summary view, you are able to gain instant insight into the supply status of every kanban
card associated with each pull sequence in a single glance. Kanban card history can also
be viewed.
Entire pull sequence chains can be viewed graphically, providing full visibility into your
supply chain.
4.6.7.2. Enhanced Planning Capabilities
Integrated with Oracle E-Business Suite’s planning products, E-Kanban provides the
ability to simulate, plan and replan your kanban pull sequences allowing you to optimize
both your production and inventory management.
E-Kanban allows you to:
• Plan for selected pull sequences
• Override the demand value calculated by the system with a user entered value
• Update production for a future date with future dated cards
• Add temporary cards when updating production
• View the horizontal plan for a pull sequence which depicts the day-wise view of
the planning calculations for a pull sequence over the selected time range. The
planning data depicted shows the beginning on hand inventory, daily demands,
number of cards on hand and replenished, closing on hand inventory, safety
stocks etc
Both the planned pull sequences and the horizontal plan for a pull sequence are displayed
within a single user interface, allowing you to quickly and easily see the effects of your
simulation changes.
You can search for pull sequences by either an entire kanban plan or item. When
selecting pull sequences by kanban plan, data from planning is used to calculate the size
or number of kanban cards. You can view, and adjust the output of the kanban planning if
you wish, to see the effects on both your pull sequence and its related horizontal plan.
When specific pull sequences are queried by item outside of a kanban plan, the system
uses the demand that has been entered directly into the pull sequence to calculate the
kanban size or number of kanban cards. You can view and adjust the demand to see the
effects on both your pull sequence and its related horizontal plan.
When you are happy with either the recommendations from planning, or the results of
your demand simulation, you can update production to generate the new number of
kanban cards or adjust the kanban size either for a single pull sequence, or for every pull
sequence listed in the pull sequence planning table.
When you update production

• If the system recommends a decrease in the number of kanban cards, the
extra cards are cancelled when the cards are replenished.
• If the system recommends an increase in the number of cards, the additional
cards are generated automatically through a concurrent request.
• If there is a recommended change in the size of the kanban, the current
kanban cards are replaced with new cards at the time of replenishment. New
cards are added without cancelling the existing cards.
4.6.7.3. Logical Kanban Support

E-Kanban supports the logical replenishment of kanban cards. Logical kanbans are
replenished automatically via the scheduled concurrent program without any user
intervention.
4.6.7.4. Extensive Search Capabilities

Providing you with an efficient way of locating kanban cards and pull sequences, search
criteria can now be saved and reused. You can search for your kanban cards by item,
kanban card number, destination subinventory, destination locator, document number,
source locator, source organization, source subinventory, supplier, supplier site, buyer
name, inventory health, source type, and planner code.
Pull sequences can be searched by item, buyer name, line code, locator, planner code,
site, source locator, source organization, source subinventory, source type, subinventory
and supplier.
4.6.7.5. Configurable Supply Statuses for Kanban Cards

Depending upon your business need, you may prefer to use your own custom supply
statuses for your kanban cards. E-Kanban allows you to configure additional supply
statuses if required which are mapped to the seeded statuses.
4.6.7.6. Enhanced Supplier Kanbans

E-Kanban supports an item being sourced from multiple suppliers. When you are
defining the pull sequence, you have the ability to define multiple suppliers with an
appropriate sourcing percentage. The system then generates the required number of cards
for each supplier so that the sourcing percentage is maintained. Each kanban card
generated is associated with a single supplier.
E-Kanban also supports the ability to update the supplier name in a kanban card if the
card is in either the “New” or “Full” status. If the user updates the supplier name in the
kanban card, the system will try to maintain the sourcing percentage as close as possible
to the values setup in the pull sequence.
4.6.7.7. Replenishment Order Consolidation

Replenishment order consolidation is the ability to generate a single document in order to
replenish multiple cards that belong to the same pull sequence. If multiple cards from the
same pull sequence are replenished, and are sourced from the same source, the system
can optionally consolidate the replenishment requirements into a single document, for
example a Purchase Order or an Internal Sales Order. Consolidation is supported for
supplier, inter-organization & intra-organization kanbans.
4.6.7.8. Temporary Kanban Cards

Temporary kanban cards can be created to handle demand fluctuations. A temporary
kanban card can have a maximum replishment cycle number entered or a disable date.
Once the kanban card attains the disable date or maximum cycle number, the card will be
cancelled on the next replenishment. If the card is in the replenishment process, it will not
be cancelled until it is next replenished.
4.6.7.9. Notifications and Alerts

E-Kanban has configurable notifications based on the following business events.
• Pull sequence creation
• Pull sequence update
• Kanban card creation
• Kanban supply status change
• Kanban cards status change
You can configure notifications based on any or all of these businesses events. The
application displays new notifications, and notifications that have been read, separately.
You can also acknowledge new notifications.
4.6.7.10. Configurable Analytics Dashboard

The following analytics are able to be configured and displayed on the E-Kanban
Dashboard:
• Inventory health – compares the inventory levels to safety stock and categorizes
the outcome as Good, Bad and Warning.
• Unmoved cards in each status – shows the number of cards of each supply type
that have been in a specific status for more than the defined length of time.
• Actual lead time versus planned lead time – compares the actual lead time of
replenished cards for each pull sequence with the lead time entered for the pull
sequence in the planning region of the setup tab.
• Actual demand versus planned demand– compares the actual demand for each
pull sequence with the average daily demand as used in the last planning run.
Custom panels are also able to be added to the dashboard by including a reference to their
URL in the Custom Panels setup parameter.
4.6.7.11. Configurable Production Kanban Job Status

Production kanban replenishment creates discrete or lot-based jobs. You can configure of
these jobs to be created in a “Released”,“Unreleased” or “Hold” status.
4.6.7.12. Configurable “Full” Status Tolerance

When you are receiving an order or completed job quantity against a kanban, you may
have received nearly, but not quite, all of the quantity required for that kanban, yet you
may want this kanban card to be considered full. E-Kanban allows you to enter a
predefined percentage for each kanban type that must be met in order for the kanban to be
placed in “Full” status again.
4.6.7.13. Import and Export Capabilities

Pull sequences and Kanban Cards can be imported to E-Kanban through the
provided API. Table data can also be exported in MS Excel format by clicking the
export button available for each table on the Summary and Planning tabs.
4.6.7.14. Access and Security

Access to the pages within E-Kanban can be configured by user responsibility.
The user can create responsibilities and restrict access to pages / form functions
for these responsibilities.
4.6.7.15. Integration with iSupplier portal

E-Kanban is integrated with iSupplier portal. Within iSupplier Portal, the supplier can
view and change the status of their relevant kanban cards on the E-Kanban tab to any
custom status mapped to the seeded ‘In Process’ status.
4.6.7.16. Customizable Using the Provided Extensions

By configuring the client extensions for custom business rules provided with E-Kanban,
you can customize the solution to meet the requirements of your operations. The provided
extensions allow you to:
• Define custom naming for kanban cards. For example, you can define an
alphanumeric prefix for kanban card numbers.
• Define valid custom status transitions through custom logic.
• Define logic for assigning suppliers to kanban cards for pull sequences with
multiple suppliers.
• Define custom logic to run while cancelling a kanban card. For example, you
can cancel the associated documents while cancelling the kanban card.
• Define a custom formula for calculating the number or size of kanban cards.
(This client extension has been enhanced.)
• Define custom logic to run when a supplier or inter-org kanban card is
received. For example, you can cancel the backordered quantity while
shipping.
• Define custom logic to run when an intra-org or inter-org kanban card is
transferred. For example, you can configure when a card is considered to be
in “Full” status for a particular item rather than just per card type.
• Define the custom threshold for bad and good inventory health at levels more
granular than the organization level.
• Define custom logic for determining whether a card is considered unmoved.
4.6.8. Terminology
Term Definition
E-Kanban Electronic Kanban Application

ERP Enterprise Resource Planning
Replenish Request for material
URL Uniform Resource Locator
4.7. Oracle Quality

4.7.1. Release 12.1.1
4.7.1.1. Quality Workbench Performance Improvements

The performance of the quality workbench (QWB) in retrieval of quality results has been
improved to ensure a better user experience. The likely situations are - retrieving quality
results from collection plans that either have a large number of records or have complex
parent child collection plans and attachments linked to the results.
4.7.1.2. Quality Workbench Usability Improvements

The quality workbench offers certain unique feature like the hierarchy grid (H-Grid) that
provides a view as well as navigation through multilevel parent-child plans. Additional
usability enhancements to QWB in this release are listed below:
4.7.1.2.1. Partial Page Refresh in Quality workbench
Partial page refresh (PPR) is a significant enhancement to the existing workbench
capabilities. This feature is to ensure that when the user enters the value for a
collection plan element in a collection plan and tabs out of the field, the page
refreshes and all the actions and validations associated with the collection plan
element are executed immediately without requiring the user to wait till the page is
saved. The improvements are:
• Online actions and validations are triggered based on collection element
values as soon as the user enters a value for the collection plan element and
tabs out of the field.
• The ability to overwrite values of collection elements that have been assigned
through collection plan element actions has been provided: At present if a
value is assigned to a collection plan element through an action then the
value cannot be overwritten. The PPR capability in the workbench will allow
overwriting the values that are assigned to a collection plan element as per
the business need.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Quality 22
4.7.1.2.2. New features and usability improvements in Quality Workbench
The following features have been provided in order to reduce the user navigation and
provide a better user experience:
• Deletion of quality results: Ability to delete collection plan records from the
workbench subject to the user having the sufficient privileges to do so.
• Export of quality results: Ability to export collection results to other
applications directly from the workbench. The users can export all the
records in the collection plan or only a subset of the records based on
filtering criteria.
• Reduced user navigation: The need for the user to navigate across multiple
pages in the application has been reduced by providing the following
capabilities:
o Multiple row entry for standalone and parent plan: Prior to this
release, the option of multiple row quality results entry is available
only for quality results entered for some transactions and also for
child plans in a parent and child scenario. Multiple row entry option
will be provided in all standalone and parent plans.
o “Add Another Row” capability: The quality workbench now
provides the ability to add another row in all user interfaces for
collection result entry.
o Display H-Grid after saving quality results: This feature eliminates
the need to navigate back and forth after saving the quality results to
continue entry, update or viewing of quality results.
• Dependent collection element will remain disabled until parent element is
entered: To prevent any inconsistency that can occur when the user enters
the value for the dependent collection plan element without entering the
value for the pre-requisite element, the dependent elements remain disabled
until the user enters a value for the pre-requisite element.
4.7.1.2.3. Inline Quality results entry in MES for Discrete Manufacturing:
This enhancement facilitates entering quality results in the same page as that of the
parent transaction in the MES module without any additional navigation.
4.7.1.3. Shop Floor Device and Test Equipment Integration

Please refer to Section 4.2.2.2.
4.8. Oracle Quality Extensions for Oracle Endeca

Oracle Quality Extensions for Oracle Endeca is a new revolutionary information
discovery application from the Oracle E-Business Suite Extensions for Oracle Endeca
solution set. It allows Quality Analysts, Shopfloor Managers and Production Control
personal to quickly explore and analyze product and process Quality data within E-
Business Suite, identify nonconformance sources, investigate the root cause and take
corrective action, near real time.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Quality Extensions for Oracle Endeca 23
Features include:
360 Degree View of all Quality Information
Oracle Quality Extensions for Oracle Endeca provides simple and intuitive data
discovery and analysis capabilities on the Quality data collected either in standalone
mode or across the different transactions like Asset, Process, Manufacturing and
Receiving, that Oracle Quality application integrates with. It provides unique, easy to
use powerful search, data discovery capability for Quality analysts to instantly find
answers to ad hoc questions that are otherwise difficult to answer. For example,
• How many nonconformances have been logged for an Item across different
organizations and their types?
• Which user owns the most number of high severity nonconformances?
• What are the corrective actions that have been taken to avoid recurrence of a high
number of scraps and improve yield on a Discrete Job?
Advanced Search on Quality Data
• Search and refine quality results using collection elements, both seeded and user
defined
• Search across quality collection plans and hierarchies
• Search across all quality organizations
• Search both structured and unstructured quality data
4.9. Oracle Mobile Project Manufacturing for Oracle E-Business Suite

4.9.1. Overview
With Oracle Mobile Project Manufacturing for Oracle E-Business Suite, project
managers and shop floor personnel can quickly search and manage project inventory on
the go.
- Search project on-hand material by item, project and task across operating units
- View project on-hand quantities by project locator
- View outstanding project borrow and payback transactions
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Mobile Project Manufacturing for Oracle E-Business Suite 24
- Identify project materials for transfer and borrow/payback
- Collaborate in transaction context using device features including email, phone,
and text
Oracle Mobile Project Manufacturing for Oracle E-Business Suite is compatible with
Oracle E-Business Suite 12.1.3 and 12.2.3 and above. To use this app, you must be a user
of Oracle Discrete Manufacturing, with mobile services configured on the server side by
for Discrete Manufacturing get additional capability for exception management.
4.9.2. V.1.1.0


There are accessibility improvements in the Work Orders Tile page, Related Information

4.10. Oracle Shop Floor Management (OSFM)

4.10.1. Release 12.1.1
4.10.1.1. Refresh BOM/Routing of Lot Based Jobs

Refresh BOM/Routing of Open Lot Based Jobs functionality is meant to propagate the
changes made to bills of material and routing of an assembly to the jobs that were created
for the assembly prior to the changes.
In release 12.1.1 this feature has been enhanced to enable jobs to get the new (or
changed) details of the BOM/Routing that are refreshed based on the routing revision
date or a revision date as specified by the user.
New parameters have been added to Refresh BOM/Routing of Open Lot Based Jobs
concurrent request, so that the user can refresh all selected jobs either as per Job Revision
Date or New Revision Date.
4.10.1.2. Lot Creation Using Substitute Components

In many manufacturing scenarios there is always a need to use alternate or substitute item
due to non-availability of the actual item (raw material) to create and process a job. There
other factors could be shortages, yield etc.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Shop Floor Management (OSFM) 25
From this release, during Lot Creation in OSFM, users can create a lot from a substitute
component as defined in the BOM. If Item A is a lot controlled end item, Item B is the
component for Item A, and Item C is a substitute for Item B, then in the lot creation form,
it is possible to enter an inventory Lot number for Item C and create a Lot Based Job for
Item A.
4.10.1.3. Lot Uniqueness/Reuse of Lot Name

OSFM solution allows creation of jobs with the same name. At times, this causes
inconsistency during completion and appending the sector extension, and proceeding
with further operations in the subsequent sector.
To control this, a new parameter has been introduced to either allow or disallow users
from creating lots with the same name as in the earlier/same sector.
As this functionality can vary for different business scenarios, users can set their
preferences accordingly. Customers migrating to Release 12.1.1 from prior releases can
continue using the existing functionality by setting the parameter as per their business
needs.
4.10.1.4. Network Routing – Lead Time Calculation

From release 12.1.1, the two options in the Tools Menu, i.e., Compute Lead Times and
Rollup Lead Times are available by default in the Network Routings when the user
chooses the seeded ‘Shop Floor Manager’ responsibility.
Compute Lead-time option is used to calculate manufacturing lead times for the selected
item in the Network Routings form. The calculation updates the lead-time attributes of
this manufacturing item, regardless of whether you manually maintain this item's lead
times. Changes to routing and resource usages can impact an item's lead times. After each
change made to a routing (adjusting usages, adding operations, and so on), the
manufacturing lead-time is recalculated for the item.
Lead-time for items with network routings is calculated using only resources on the
primary path. Manufacturing Lead Times for the same item (and more items) can also be
calculated by using the concurrent request.
Rollup Lead-time is used to roll up the cumulative lead times after each change made to a
bill (adding components, assigning to a different operation, and so on) or the item lead
times. Changes to the indented bill of material and component lead times can impact a
parent item's cumulative lead times.
Also the concurrent request can be used to rollup the cumulative Lead-times for the same
item (and more items).
4.10.1.5. Lot Based Job Interface Enhancements

Lot Based Job Interface has been enhanced to support the following features:
• Add operation: You can add new standard or non-standard operation as future
operation to the job.
• Delete operation: You can delete future operations on the job that are not on the
primary routing path. If you want to delete an operation in the primary path, then
delete the network links to the operation and then delete the operation. This also
deletes resources, resource instances and components from plan details.
• Add operation link: You can add new network link between two operations in the
job details. However, you have to exercise caution that the network formed by
such an action is valid.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Shop Floor Management (OSFM) 26
• Delete operation link: You can delete the existing network link between two
operations in the job details. However, you have to exercise caution that the
network formed by such an action is valid.
• Add resources: You can add new resources to both current and future operations.
• Delete resources: You can delete resources from both current and future
operations.
• Add components: You can add new components to both current and future
operations.
• Delete components: You can delete components from both current and future
operations.
4.11. Oracle Supply Chain Globalization

4.11.1. Release 12.1.1
4.11.1.1. Buy/Sell Subcontracting

Buy/Sell Subcontracting is a business practice where an Original Equipment
Manufacturer (OEM) outsources the complete manufacturing of an assembly to a
Manufacturing Partner (MP) and sells the components (used to build the assembly) to the
MP. The timing of sale is usually when the OEM ships the components to the MP. A
company can implement Buy/Sell Subcontracting when it has the following business
needs;
• Ownership of Subcontracting Components
When the subcontracting components are sold, the ownership is transferred from
an OEM to the MP. MP is fully responsible for the component inventory,
damage, etc.
• Receivables and Payables
Cash receipts from the sale of subcontracting components and payment for
purchase of assemblies are treated as independent business transactions.
Therefore, Receivables and Payables are usually not netted – OEM pays the MP
for purchasing the outsourced assembly and the MP pays for buying the
subcontracting components from the OEM.
Buy/Sell Subcontracting functionality is supported from this release with the following
features;
• Planning at OEM and MP
Planning considers the OSA (outsourced assembly) requirements in OEM and
appropriately plans for the constituent components required at MP.
• Goods Movement between OEM and MP
Creation of Subcontracting Purchase order triggers automatic creation of the
requisite sales and purchase orders to enable the movement of components from
OEM to MP. Also, the discrete jobs required to assemble the OSA at MP are
automatically created. Both synchronized shipment and prepositioned material
movements are supported.
• Inventory Tracking and Visibility at MP
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Supply Chain Globalization 27
Through online visibility into the component stocks available at the MP, the
OEM can effectively plan for the components that need to be shipped to the MP.
Further any unforeseen consumptions can be manually reconciled using a
workbench.
Buy/Sell Subcontracting functionality helps you to easily track and manage your
outsourced manufacturing activities with your partners.
Note: Buy/Sell Subcontracting feature is supported for all countries and costing methods
(Standard, Average, FIFO & LIFO).
4.11.2. Terminology
Term Definition
Prepositioned Components Components are shipped to the MP without reference to any

subcontracting order ahead of assembly requirements. When
the subcontracting order is created, these components are hard
allocated.
Synchronized Components Components are shipped to the MP with references to specific
subcontracting orders, along with the order.
4.12. Oracle Outsourced Manufacturing for Discrete Industries (New Product)

4.12.1. Release 12.1.1
4.12.1.1. Buy/Sell Subcontracting

Buy/Sell Subcontracting is a business practice where an Original Equipment
Manufacturer (OEM) outsources the complete manufacturing of an assembly to a
Manufacturing Partner (MP) and sells the components (used to build the assembly) to the
MP. The timing of sale is usually when the OEM ships the components to the MP. A
company can implement Buy/Sell Subcontracting when it has the following business
needs;
• Ownership of Subcontracting Components
When the subcontracting components are sold, the ownership is transferred from
an OEM to the MP. MP is fully responsible for the component inventory,
damage, etc.
• Receivables and Payables
Cash receipts from the sale of subcontracting components and payment for
purchase of assemblies are treated as independent business transactions.
Therefore, Receivables and Payables are usually not netted – OEM pays the MP
for purchasing the outsourced assembly and the MP pays for buying the
subcontracting components from the OEM.
Buy/Sell Subcontracting functionality is supported from this release with the following
features;
• Planning at OEM and MP
Planning considers the OSA (outsourced assembly) requirements in OEM and
appropriately plans for the constituent components required at MP.
• Goods Movement between OEM and MP
Creation of Subcontracting Purchase order triggers automatic creation of the
requisite sales and purchase orders to enable the movement of components from
OEM to MP. Also, the discrete jobs required to assemble the OSA at MP are
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content DocumentOracle Outsourced Manufacturing for Discrete Industries (New Product) 28
automatically created. Both synchronized shipment and prepositioned material
movements are supported.
• Inventory Tracking and Visibility at MP
Through online visibility into the component stocks available at the MP, the
OEM can effectively plan for the components that need to be shipped to the MP.
Further any unforeseen consumptions can be manually reconciled using a
workbench.
Buy/Sell Subcontracting functionality helps you to easily track and manage your
Note: Buy/Sell Subcontracting feature is supported for all countries and costing methods
(Standard, Average, FIFO & LIFO).
4.12.2. Release 12.1.3.4
4.12.2.1. Full Outsourcing

Full Outsourcing, also referred as Contract Manufacturing or Subcontracting assembly
is a business practice where an Original Equipment Manufacturer (OEM) outsources the
complete manufacturing of an assembly to a Manufacturing Partner (MP) and Supply the
components (used to build the assembly) to the MP, but retains the ownership of the
components . A company can implement Full Outsourcing when it has the following
business needs
• Outsourcing the assembly to MP: When the OEM plans to have the complete
Sub assembly or the finished assembly manufactured at a Manufacturing
partner's facility without the need for any internal manufacturing.
• Ownership of the Subcontracting Components:

When the subcontracting components are shipped, the ownership of the
components is still retained with OEM and component value is accounted and
reflected in the OEM book of accounts as inventory at MP site.
• Drop ship components: OEM intends to drop ship components from

Component Supplier to manufacturing partner.
• Drop ship Assembly: OEM intends to drop ship assembly from MP site to
Customer after MP completes the manufacturing of the assembly.
• Outsourcing support for WMS and EAM enabled Organizations:

Full outsourcing co-exists with WMS and EAM enabled inventory organizations.
• Manufacturing Partner supplied components in the outsourced assembly:

In addition to the components supplied by the OEM to the MP, the OEM can
additionally include components intended to be supplied by the MP in the BOM.
However, the OEM can never plan or ship these components to the MP but use it
only from an Engineering perspective. The MP may procure or manufacture
these components in-house, to use them in manufacturing the assembly and
charge OEM as part of value addition.
• Software components in the outsourced assembly: OEMs can include

intangible components like software, in the outsource assembly BOM, plan them
but never physically ship them to MP. MP can download this software from
software vendor’s site and install them in the assembly as part of the
manufacturing process.
Full Outsourcing functionality is supported from this release with the following
features;
• Planning at OEM and MP: Planning considers the OSA (outsourced

assembly) requirements in OEM and appropriately plans for the components
required at MP.
• Goods Movement between OEM and MP: Creation of Subcontracting

Purchase Order triggers automatic creation of the requisite sales and
purchase orders to enable the movement of components from OEM to MP.
Also, the discrete jobs required to assemble the OSA at MP are automatically
created. Both synchronized shipment and prepositioned material movements
are supported.
• Inventory Tracking and Visibility at MP: Through online visibility into

the component stocks available at the MP, the OEM can effectively plan for
the components that need to be shipped to the MP. Further any unforeseen
consumptions can be manually reconciled using a workbench.
• Accounting of Component Inventory: When OEM ships components to

MP, component inventory value is debited to an intransit account. Intransit
account is an asset account and can be rolled up to the balance sheet,
reflecting the inventory value at MP site as an asset in the balance sheet.
When the Assembly is received from the MP, component value is credited
from the intransit account, reflecting the reduction of inventory (consumed in
the manufacturing of the assembly) and asset value in the balance sheet
Full Outsourcing functionality helps you to easily track and manage your
Note: Full Outsourcing feature is supported for all countries and with ‘Standard
Costing’ method only
4.12.2.2. Endeca Information Discovery
A business user can get complete and real-time visibility into the overall health of
the outsourced manufacturing business using the rich user interface powered by
Endeca. Various aspects of the business such as subcontracting order status,
inventory balances, financial position, and quality issues can be visualized
intuitively using these interfaces.
4.12.2.3. 360 Degree View of Outsourced Manufacturing Business
Key Performance Indicators and metrics provide quick answers to simple business
questions like:
• How many subcontracting orders are delayed and which customers are impacted?
• What’s the value of our material at manufacturing partner locations?
• What’s the value of defective finished goods received from manufacturing
partners?
• What’s the value of uninvoiced subcontracting orders and replenishments?
• What are the value of outsourced products that had quality problems?
• Detailed analysis on any metric can be done using a comprehensive set of charts
and tabular data on the user interface. Using the guided navigation, google like
search capabilities, and tag clouds, the user can quickly get to the subcontracting
orders that need immediate attention. Outsourced manufacturing data across
manufacturing partners is presented together to allow for quick comparison to
differences.
4.12.3. Terminology
Term Definition
Prepositioned Components Components are shipped to the MP without reference to any

subcontracting order ahead of assembly requirements. When
the subcontracting order is created, these components are hard
allocated.
Synchronized Components Components are shipped to the MP with references to specific
subcontracting orders, along with the order.
5. New and Changed Features in Process Manufacturing
5.1. Oracle Inventory (Inventory Convergence)

5.1.1. Overview
Process Inventory features and functionality are now incorporated into Oracle Inventory.
With this release, customers of Oracle’s Process Manufacturing applications can now use
Oracle Inventory and Oracle Warehouse Management. The use of a single inventory
application provides the Oracle Process Manufacturing user seamless integration with the
rest of the e-Business Suite. This feature opens up additional functionality that was
previously only available to Discrete Oracle Inventory users, such as vendor-managed
and consigned inventory, reservations, move order requisitions, kanban, min-max
replenishment and robust physical inventory and cycle counting functionality. The
ability to implement Oracle Warehouse Management allows users to leverage
sophisticated picking rules, license plates (LPN’S), putaway rules and task management.
Information on the features of Oracle Inventory and Warehouse Management can be
obtained from data sheets and release content documents for these applications.
Process Inventory forms and reports are available for viewing and reporting of historical
data. This release also includes the migration of Process Inventory data into Oracle
Inventory.
In order to support the needs of process manufacturing organizations, several additional
features have been added to Oracle Inventory:
• Dual unit of measure control for any item
• Advanced lot control
• Material Status
• Enhanced inventory allocation rules
5.1.2. Features
5.1.2.1. Dual unit of measure control for any item

Process manufacturers often need to track inventory in two different units of measure,
which has been a main feature of Process Inventory. This functionality is now
incorporated into Oracle Inventory to support “catch weights” and other uses of dual unit
inventory tracking. Prices can be calculated in Order Management, based on either unit.
Oracle Inventory's Dual Unit of Measure Control enables users to transact inventory in
two unrelated units of measure where the conversion between the measures vary from lot
to lot or from one transaction to the next. If an item is dual unit of measure control
enabled, during transactions, users are prompted to enter the transaction quantity in both
units and are able to query on hand balances, availability and reservations in both units
for full supply chain visibility to all required handling units of measure.
5.1.2.2. Advanced lot control

Lot control is a critical feature used by process manufacturers to track and manage their
inventory. They often need to get answers to such questions as: 'Which lots were
delivered to which customers? Which lots were produced from that production line
during that shift? What was the quality of the components or ingredients and which
suppliers sent them?' To enable better visibility to a lot, its genealogy and attributes,
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Inventory (Inventory Convergence) 32
significant enhancements have been made to the lot tracking capabilities within Oracle
Inventory.
Sublot control, a feature supported in Process Inventory, has been incorporated into
Oracle Inventory and allows users to track the parent lot from which multiple lots were
created. Sublots have been replaced with Child Lots. The parent lot may refer to the
production batch that spawned the lot but, if the output of that batch varies in term of
grade or other QC attributes, multiple child lots might be received into inventory. Users
can query lots by their parent lot and view the parent lot in the lot genealogy form.
A lot can be grade controlled – a feature supported in Process Inventory, but one that is
new to Oracle Inventory. The product can be queried by grade and the grade can be
changed as required. Users can also track retest dates, expiration and retest actions
among other lot attributes. In addition, a new concurrent request in Oracle Inventory can
initiate a workflow if a lot or serial approaches any key milestone dates such as
expiration, retest or best-by date.
The genealogy form in Oracle Inventory has also been enhanced to allow users to view
quality inspection results from OPM Quality, material status, grade change history and
other information about the lot. The genealogy gives you history on transactions for this
lot, as well as its source, such as where it was purchased or from which batch it
originated. These features and more can provide materials managers with the tools they
need to enable faster turn-around on quality, customer care and production issues.
5.1.2.3. Material status

Quality Control and product lifecycle issues may require that certain material, although
stored in a ready to use state in the warehouse or production facility, may not be usable
for certain applications. A lot that has not yet passed inspection will not be shipped to a
customer or consumed in production. A warehouse location that has been discovered to
have erroneous inventory balances would not be included in available to promise
calculations. In Process Inventory, material could be controlled using Lot Status. In
Oracle Inventory, this functionality is called Material Status. This feature was previously
only available to Oracle Warehouse Management users, but is now available to all Oracle
Inventory users. It enables you to assign a material status to the material in an inventory
lot, serial, subinventory or locator and to use that status to restrict transactions. The
associated material statuses dictate which transactions can be performed on the lot, the
serial or the material that is stored in the subinventory or locator. In addition, Oracle's
planning applications and Inventory's availability calculations take the material status
into consideration when determining availability. Users can determine whether or not
product of a particular status can be reservable, included in ATP calculations or netted in
production planning. Using material status, warehouse employees, materials managers,
production planners and customer service representatives can be provided with a more
granular and accurate picture of the inventory that is available for them to use for each
business purpose.
5.1.2.4. Enhanced inventory allocation rules

Inventory allocation rules control how inventory is assigned to a move order, or other
request for inventory from Manufacturing or Order Management. These rules are being
enhanced to incorporate functionality from Process Inventory, as well as build on the
existing rules in Oracle Inventory. The allocation rules allow you to pick inventory by:
• Ordering based on lot number, item revision, subinventory and stock locator
• Picking inventory based on lot expiration or creation dates and receipt dates
• Allowing the selection of single or multiple lots
• Matching on customer specifications
• Allowing the partial allocation of a request
5.1.2.5. Migrating to Oracle Inventory

As part of the upgrade to this release, data from Process Inventory can be migrated into
Oracle Inventory. The migrated data includes:
• Current onhand inventory balances, which can be migrated as starting balances in
Oracle Inventory
• Lot and sublot master records, which can be migrated to the Oracle Inventory lot
master tables
• Lot and sublot conversions, which can be migrated into a new Oracle Inventory
table
• Lot statuses, which can be migrated as Material Statuses
• Inventory profiles, which can be migrated into new Organization Parameter
fields
• Allocation rules for Order Management and Process Execution
• Items, which already exist in Oracle Inventory, and can be updated for new
attributes and organization assignments
There is master data in Process Inventory that already exists in Oracle Inventory. This
data can not be modified and includes:
• Inventory organizations created as Process Warehouses
• Stock locators created as Process Warehouse Locations
• Subinventories created for Process Warehouses
Some data in Process Inventory can not be migrated, mostly because it is historical data
that cannot be altered. This includes:
• Completed inventory transactions
• Pending inventory transactions
• Physical and cycle count data
• e-Records and e-Signatures against inventory transactions
5.1.2.6. Viewing historical data

For data that cannot be migrated to Oracle Inventory, Process Inventory forms and
reports can remain accessible. These forms include mostly query screens, which only
allow the viewing of data. The historical data cannot be modified through these or other
forms. All Process Inventory reports can be available and can print the historical data
that remains in the Process Inventory tables. For users who do not have prior releases,
Process Inventory tables, menus and forms can not be installed. For current Process
Inventory users, the historical data can be displayed using the following forms:
• Transaction Inquiry
• Lot Genealogy
• Query Item Master
• Posted Journal Inquiry
Since the inventory migration can zero out any inventory balances in Process Inventory,
there can be limited use of the Item Inquiry form, which displays onhand inventory. It
can still be accessible, but little or no data can be displayed on that form. The same
applies to the Allocated Summary and Unallocated Inventory queries. Most of the
reports that display historical or master data can be available to print information from
Process Inventory.
5.1.3. Release 12.2
5.1.3.1. Advanced Catch-Weight

Catch Weight management applies primarily to the manufacturing, distribution and
consumer product industries where weights can vary from piece to piece, either due to
biological variations, or because of weight loss that occurs during storage. This
variability affects the procurement pricing and sales invoicing processes. A distinction
must be made between the fulfillment unit of measure and a valuation unit of measure.
While the fulfillment unit is the leading unit for all processes in operative logistics, the
valuation and payment flows take place on the basis of the valuation unit. The logistic
units often used are pieces, cases or each; the valuation units often used are
Kilogram/Pound. Although the term “catch weight” is most commonly used in the food
industry, this feature could be leveraged by a range of industries including those that
manage products with variable lengths.
As the raw material flows through the manufacturing process, the likelihood of finished
product not adhering to standard conversions is high. Even after storage, the finished
product can lose or gain weight due to heat or humidity in the facility. One storage
locator can have products from multiple process batches or lots in multiple license plates
(LPNs) which each have a different weight.
Most consumer packaged goods companies cost and invoice by weight and fulfill by
units. As a result of this, items are mostly defined with a Primary UOM of weight and a
Secondary UOM of units. For a warehouse resource involved in the fulfillment process,
a pallet of boxes of beef looks the same irrespective of the batch or lot or LPN. For this
reason, flexibility is needed regarding which UOM to use for fulfillment.
The Advanced Catch-Weight solution addresses this problem by introducing the concept
of a Fulfillment Base at the sales order line level. The Fulfillment Base is driven from
the Ordered UOM class and can either be the Primary UOM or the Secondary UOM.
Fulfillment Base is honored in warehouse management while fulfilling the order line.
Enhancements have also been made to Order Management, Advanced Pricing, Shipping,
and Mobile Supply Chain Applications to support this solution. Please refer to the
Advanced Catch-Weight Solution in Oracle E-Business Suite Applications white paper
for additional details [ID 1551171.1].
5.1.4. Product Dependencies
These features are available through Oracle Inventory.
5.1.5. Third Party Integration Points
Refer to the Oracle Inventory RCD for information on additional third party integration
points.
5.2. Oracle Process Manufacturing Product Development

5.2.1. Overview
Oracle Process Manufacturing Product Development gives you the tools to streamline the
development of new products from early experimental stages through piloting and into
full production. Recipe management meets industry standards, including S88.03.
Formulas and routings can be fine-tuned using graphical manipulation, formula analysis
and simulation/optimization tools. Workflow and status control allow you to track and
control each step of the product lifecycle, while least cost formulation provides guidance
on the optimal formula based on cost and available inventory.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Process Manufacturing Product Development 35
Product Development integrates with Process Execution, Process Costing and Advanced
Supply Chain Planning to give you a complete recipe and product management solution.
5.2.2. Features
5.2.2.1. Inventory Convergence Impact on Product Development Workbench

The workbench provides users with an interface that increases visibility to recipes and
their components, along with access to all of the forms necessary to create, copy, and
maintain formulations and routings.
One of the workbench features is the ability to change the “View By” context. Some of
the different options are View By Class, Product, Plant, Lab, etc. Queries on this form
can need to be modified for convergence to look at the new Item and Organization tables.
5.2.2.2. Inventory Convergence Impact on Formula Management

There are several requirements for Formulas. Users can be able to maintain Global and
Local Recipes (S88 Compliance). The owning organization for a formula can continue to
function with inventory organizations that can be defined as either a Plant or Lab.
Formulas can also work with the standard Oracle Applications Item Master
(MTL_SYSTEM_ITEMS).
5.2.2.2.1. Formula Security
Formula Security enables users to restrict access to formulas by user, responsibility and
organization using Oracle 8i/9i Virtual Private Database (VPD). Three levels of security
are possible – Update, View-Only, and Hidden. Each Formula has one Owning
Organization, and this is the attribute generally used to determine whether or not a
formula is accessible by others. There is also the concept of “Other Organization”, that
determines if someone from another organization can access formulas.
The requirement is to provide an organization migration so that none of the organizations
listed in the security tables are removed, and to maintain the integrity of the user-
organization table and function (or replace it with an equivalent).
5.2.2.3. Inventory Convergence Impact on Routings

Routings can continue to maintain a valid link to the organizations referenced in the
routing header. Routings can also be renamed to Process Routings to avoid confusion
with Routings used in Discrete Mfg.
5.2.2.4. Inventory Convergence Impact on Operations

Operations can continue to maintain a valid link to the organizations referenced in the
routing header. Operations can not be organization-specific.
To differentiate between Operations in Discrete Mfg and Process Mfg, Operations can be
renamed to Process Operations.
5.2.2.5. Inventory Convergence Impact on Recipe Management

Recipes can continue to use the default organization as the Creation Organization and the
initial Owning Organization. Additionally, more S88 compliance can be added. To
classify recipes by S88 Recipe Type, a new field can be introduced as part of the recipe
header that enables users to categorize each recipe as a General, Site, or Master Recipe.
A new View By for Recipes can be available from the Product Development Workbench
with a General Recipe at the top of the list, followed by all of its Site Recipes, and each
site displaying all of its Master Recipes. Also, General and Site recipe types can be
defaulted when new recipes are created. Recipes created under a Master Inventory
Organization can default to ‘General’ recipe type, while recipes created under all other
Inventory Organizations can default to ‘Site’ recipe type.
Recipe and Validity Rule security can continue to be supported through user,
responsibility and organization associations and via Formula Security.
5.2.2.5.1. Validity Rules
One or more Validity Rules can be associated with each recipe. A validity rule
determines when, where and under what circumstances a recipe can be used to create a
batch, to plan with, or base standard costs upon. The inventory-org field on each validity
rule determines which plant (inventory-org) the recipe is valid for. Leaving the
inventory-org field blank means that the recipe can be used in any plant. Plant specific
validity rules enable the maintainer of a recipe to restrict the use to a subset of plants.
Requirement: For global validity rules, validity rules would be applicable for “All”
inventory-orgs. For inventory-org specific validity rules, the inventory-org LOV and
validation would be restricted to Plants (inventory-orgs).
5.2.2.5.2. Recipe Overrides
Once a process engineer knows which materials can be processed in a given set of
equipment, they may want to adjust some of the default values in a recipe. For example,
the viscosity of different liquids may require machines to be run at different speeds,
effect throughput, and impact process loss, which accounts for 3 different fields that
would be adjusted. Therefore we’ve provided a number of process-specific override
fields. These fields are plant (inventory-org) specific and permit the user to adjust the
recipe to be more flexible and more accurate. This reduces changes that need to be made
in the batch as well as batch variances, provides for more effective planning, and more
accurate standard costs.
The inventory-org for overriding data would be restricted to Labs & Plants.
5.2.2.6. Inventory Convergence Impact on Technical Data

Technical Parameters are either Global or Lab specific attributes that are ultimately
associated with Items in a Formula. These are not item specific, but a Lab organization
may be required to create them. The requirement is to ensure that the convergence
project offers a way to define both Global (all orgs) and Lab-specific Technical
Parameters. LOV can only display labs.
Technical Parameter Sequences offers users a way to both sequence and configure the
data that appears on the Simulator. The requirement is to retain the ability to continue
using Lab organizations, Experimental and Inventory Items, and Item Categories.
Once Technical Parameters are established for a Lab, they can be associated with any
number of items (ingredients, products, and byproducts) thus becoming item attributes.
Each Item can have different technical data, and each Lot for that Item can also have its
own technical data value. Item Technical Data can be typed into the Item Technical Data
form or derived from Quality Results. Item Technical Data is also Lab specific.
When a formula or batch is loaded onto the simulator to perform “what if” scenarios
and/or allocations, the item technical data is displayed in order to help users decide upon
the best formulation.
The requirement for Item Technical Data is to ensure that Lab organizations are
maintained and the Item master is accessible for both Experimental and Inventory Items.
5.2.2.7. Inventory Convergence Impact on Simulator

The Simulator displays each ingredient, product, and byproduct in a formula or batch
with the quantity and technical parameter values for each. The Simulator is used to
display and edit formulas, batches, and the technical parameter values of the items, to
display the effects that changes to ingredient values have on the product values, and to
make or change batch allocations based on these values.
1. Organizations –
The Spreadsheet uses two different organizations fields. The first one is the Lab the
user is working in, and this Lab Organization determines which technical parameters
and technical data are displayed. The Lab Org is always used by the spreadsheet and
is set by the Profile Option “GMD: Default Lab”. The other organization field is
Plant, which is used only when a Batch is loaded on the spreadsheet. The Plant field
is part of the unique identifier for a Batch, and also determines in which plant the
inventory allocations can occur.
The spreadsheet will continue to support Lab organizations and Plants, and allow
these two different organizations to be used in the same form simultaneously.
2. Items –
Both Experimental and Inventory Items can be used on the spreadsheet. Normally
the items are loaded via the formula or batch, but items can also be added to the
spreadsheet through an LOV of the Item master table.
If a Formula is loaded onto the Spreadsheet, any new items added would be restricted
to those items associated with the formula owning organization. If a Batch is loaded
on the Spreadsheet, the list of available items would be restricted to the items
associated with the Plant (inventory org) the batch is associated with.
The spreadsheet supports of both Experimental and Inventory Items.
3. Lots/Sublots –
When working with either formulas or batches, the pick lots form can be invoked to
add lots/sublots or change allocations. There is also an Add Lot form. This feature
exists as of OPM Family Pack K (11.5.10) and stems from a requirement called
‘Pooling’.
While working with a Formula, the addition on lots/sublots is unrestricted. While
working with a Batch, the addition of lots/sublots is restricted to those warehouses
from which the Plant can consume inventory. When a batch is updated on the
spreadsheet, authorized users have the ability to update the actual batch and its
allocations.
The spreadsheet’s ability to pick from inventory using the same rules it presently
does, and update batches (which in turn may update inventory allocations and
balances) has been maintained during Inventory convergence.
5.2.2.8. Inventory Convergence Impact on Formula Analysis, Formula Inquiry,

Indented BOM
These three functions are analysis tools that display different aspects of a Formula. In
each case, Organization and/or Item may be used as a parameter to run the analysis.
The LOV for organizations would always be restricted to the current user’s User-
Organization associations.
If an Item is used as a parameter, then the program would validate that the item belongs
to at least one organization that the user is associated with.
If Formula Security is activated, then the parameters, LOVs and queries themselves will
continue to recognize the security policies. Units of Measure – Since each organization
may have its own default UOM, each of these reports can take this into consideration.
• Formula Analysis – UOM is a runtime parameter, so any UOM can be chosen (as
long as the necessary UOM conversions exist).
• Formula Inquiry – The original Formula UOMs is used.
• Indented BOM – This report offers a choice of UOMs – either the Formula UOM
or Inventory UOM. If Inventory UOM is chosen, then it uses the default UOM
of the organization under which the report was submitted (the User’s default
org).
5.2.2.9. Inventory Convergence Impact on Mass Search and Replace

Mass Search and Replace enables the identification and replacement of key components
in formulas, routings, operations, and recipes for single or multiple organizations. The
basic features of search and replace permit the query for fundamental components such as
the name, version, description, owner, and status. Advanced search and replace features
facilitate the search and replacement of components using conditions and specific values
in formulas, routings, operations, and recipes.
Within the new item-organization model, the list of ingredients that are available for
replacing in a formula are limited to only those items associated with the User’s
organizations.
5.2.2.10. Inventory Convergence Impact on Product Development Workflow and ERES

Status helps determine how a product development entity (formula, recipe, etc.) can be
used. For instance, a “New” formula can allow users to make modifications to it and
manipulate it using simulation tools. A formula that is “Approved for Lab Use” can be
modified to a certain extent but is generally used for creating Lab Batches. “Approved
for General Use” means the formula is usable by all programs that need it and normally
cannot be updated, while “On-Hold” and “Obsolete” mean the formula cannot be used.
These workflows are also configurable by organization
5.2.2.11. Item Substitution lists associated with the Item Master

Item Substitution Lists can be definable. An Item Substitution List is simply a list of
alternative items associated with the Item Master with a version and status. Once these
substitution lists are associated with an Item and approved, they can be used by any
Formula in which the Item is used as an Ingredient. When a new substitution list is
created, the user must be provided with a list of Formulas that contain the source item so
that they can choose which formulas this substitute would be associated with. Once the
list of formulas is chosen, the formula line detail for the relevant ingredient can have
access to the substitution list.
5.2.2.12. Effective Formulas

Once substitutes become part of a Formula, the Planning, Costing and Production
applications will see these substitutes as the active, effective ingredient. Visibility to the
substitute items, and a method to force these applications to look for the active substitutes
rather than the original ingredient in the formula has been provided.
Once a new, effective substitution is added to a Formula, approving this change the user
would be given the option to update all Pending batches that contain the original
ingredient. The original ingredient and its allocations would be deleted and replaced with
the new, unallocated item.
5.2.2.13. One to One Substitutions

Item Substitution lists may consist of only one item, a one for one substitution.
The one to one replacement of ingredients within Formulas and Batches is supported.
The software currently allows ingredients to be substituted without an item substitution
list, and this method would continue to be supported.
Ingredient substitutions within Batches would be limited to Batches in a status of
Pending.
5.2.2.14. Using Substitute Items with Planning

Substitutions are also visible to the Advanced Planning and Scheduling software. This
can allow planning to determine a plant’s capability to utilize one or more substitute
items in a formula, thereby enabling the plant to have the capability to promise a product
if one of the ingredients can be properly substituted.
Ingredient Substitutions in Formulas can allow the Capability to Promise Model that is
being utilized with Advanced Planning and Scheduling to determine if the facility can
make the product by determining if either the original item on the formula or the
component substitute item are available at the facility to produce the item that is being
requested.
Effective dates and Preference are considered in order to determine the best choice of
ingredients.
5.2.2.15. Least Cost Formulation : Product Specifications

The user, generally a formulator, is able to enter a complete product specification in the
software that represents the target properties of the product(s) that must be met as part of
the least cost formulation. This includes a form/table to define each individual
requirement, and also a form/table to define the product specific requirements including
min/max quantities, etc.
The Product Specification can also be used by the Least Cost Formulation program to
generate formulas and batches.
5.2.2.16. Least Cost Formulation : Generate Formulas based on Least Cost

The system generates least cost formulas while meeting the requirements defined within
the product specification. Two methods of formula generation are supported:
• Loading an existing formula into a tool like the simulator/optimizer and optimizing the
ingredients based on the latest costs available while meeting the requirements from the
product specification.
• Creating a new formula where no ingredients have been previously entered – the new formula
would be based completely upon the least cost and product specification.
5.2.2.17. Least Cost Formulation : Create Batches Based on Cost

The system generates least cost batches while meeting the requirements defined within
the product specification. Two methods of batch generation are supported:
• Loading an existing batch into a tool like the simulator/optimizer and optimizing the
ingredients and lot allocations based on the latest costs available while meeting the
requirements from the product specification.
• Creating a new batch where no formula/recipe has been previously entered – the batch’s bill
of materials would be based completely upon the least cost, product specification, and
available inventory. See the requirement below ‘Generate Batches without a predefined
Formula’ for more details.
5.2.2.18. Least Cost Formulation : Specify which Costs to use
Any cost method can be used as part of the optimization equation- standard, actual, and
lot costs
Users of least cost formulation specify which costs to use to determine the least cost, and
the retrieves costs that already exist in costing tables. Users do not have to enter costs
specifically for least cost formulation.
The ability to compare the actual cost of the intended input materials with the standard
cost of the materials specified for the batch by the formula prior to the actual batch
becoming WIP is provided
5.2.2.19. Least Cost Formulation : Generate Batches without a predefined formula

In order to create a batch that uses the least cost materials and also meets the product
specifications, the software is not restricted to a pre-defined formula with a set list of
ingredients. The least cost formulation program looks at the Product Specification and
on-hand materials to generate the optimal formulation. The formulation (batch) created
from this process would likely be used only one time, since it’s using a snapshot of
available inventory that may not exist again, however could be used for a weeks plan. .
5.2.2.20. Least Cost Formulation : Choose Materials based on Categories or Substitute

Items
The least cost formulation program is able to find the best materials to allocate based on
the attributes of the available materials. However, there are some restrictions around
which materials can be chosen for a given formula or batch. For instance, if the %FAT
attribute is considered as part of the equation for making Ice Cream, the LCF program
would NOT choose a material from the Meat family that has %FAT as an attribute.
5.2.2.21. Least Cost Formulation : Select Formula/Recipe based on Least Cost

As part of the Production processes, a user can choose the least cost formula. For
instance, when creating an individual batch, the software would identify to the user the
least cost formula, or sort the possible choices in order from least cost to most cost.
5.2.3. Release 12.0.6 (RUP6)
5.2.3.1. Fixed Process Loss

You can define the fixed process loss for all the batches using the Routing or Recipe
windows. You can define the priority for applying the fixed process loss at various levels
similar to variable process loss.· You can apply the fixed process loss in addition to the
variable loss. The fixed process loss is applied after calculating the variable loss and it is
added to the ingredient quantity or reduced from the product quantity based on how the
batch is created. You can select ‘Apply Fixed Process Loss’ check box, if the parameter
Apply Fixed Process Loss is set to Manually. It is by default un-checked on the Create
Batch/Firm Planned Order window.
5.2.3.2. DFF for Step Material Associations

Before Release 12.0.6, within the Recipe window and Step quantity tab, the DFF
flexfield was not available, even though it was set up. A descriptive flex field (DFF) is a
field that is comprised of segments. A flex field appears in a pop up window when you
click on the flex field icon. Each segment has a name and a set of valid values. Using
Descriptive flex fields you can store additional information about each step depending on
the values you enter in the Step Materials window. In Release 12.0.6, DFF for step
materials provides additional information like the registration of the sequence in which
the ingredients need to be consumed. The Descriptive Flex Field window displays the
flex field segments based on the Recipe Step Material associations flex field defined in
the Applications Developer responsibility.

• Oracle BOM (where the Item Master resides)
5.3. Oracle Process Manufacturing Quality Management

5.3.1. Overview
Oracle® Process Manufacturing Quality Management empowers Process companies to
enforce enterprise-wide proactive quality assurance through automated sampling and
approval workflows and ensure that materials received, produced, and shipped meet
quality specifications. OPM Quality also assures customer and regulatory compliance
with tools to handle the expiration of materials and generation of quality certificates.
5.3.2. Features
5.3.2.1. Converged Inventory Modifications to OPM Quality

Since OPM Quality has existing links to inventory and inventory transactions, the
following modifications were required:
• Item entry and validation – A multi-segment item number is supported, and any item
entered on a specification, sample, or stability study is designated in the item master
as “Process Quality Enabled”.
• Item revisions – The item revision capability in Oracle Inventory is extended to items
in Process-enabled inventory organizations when establishing setup data and
performing inventory transactions. Support for revision-controlled items is added in
item specifications, specification validity rules, item samples, stability studies, and in
the specification matching logic.
• Specification and sample ownership – Specifications and samples are owned by an
inventory organization. The owning inventory organization will determine the list of
valid items and tests that can be placed on a specification or sample.
• Specification usage – A specification can be used by a specific inventory
organization, or it can be global and used by all inventory organizations. If several
inventory organizations can use a specification, then separate validity rules are
created, one for each inventory organization.
• Inventory specification validity rule or sample – Information that may need to be
designated on a specification validity rule or captured on a sample includes new
fields such as Subinventory and Stock Locator.
• Quality-driven inventory transactions – When sample information is used to adjust
inventory, an inventory transaction is created, with a source type of OPM Quality and
a transaction type of Sample Issue.
• Material status, grade, action, and reason code migration – Material status, grade,
quality actions, and reason code support and security will be migrated to Oracle
Inventory. Therefore, any lookups for these entities are replaced to reference the
Oracle Inventory tables.
• Lot Genealogy – OPM Quality samples and results are viewable from the Oracle
Inventory Lot Genealogy inquiry.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Process Manufacturing Quality Management 42
5.3.2.2. Enhanced Receiving Inspection
When a receipt containing Process items is routed for inspection, OPM Quality
requirements can be enforced before the goods can be delivered to inventory. This
inspection point allows a visual inspection by the receiving clerk in Oracle Quality as
well as a more detailed sample analysis by a lab technician in OPM Quality. Upon
receipt, a workflow notification is sent to take a sample based on a supplier specification
validity rule defined in OPM Quality.
This enhanced solution also leverages the Oracle Quality skip receipt inspection rules,
while enforcing a mandatory collection plan. Through this interface, the receiving clerk
can see status updates and the acceptability of the sample analysis. Based on the outcome
of inspection, the user updates the accepted and rejected quantities of the receipt in the
collection plan, which in turn updates Oracle Purchasing. After inspection, the
appropriate quantities can be inventoried or returned to the supplier.
5.3.2.3. Copying Quality Specifications

A new copy to/from function is added to the specification to allow copying across
inventory organizations. This feature expedites a “push down” approach to propagating
corporate quality standards to local facilities. The newly copied entities can be modified
to suit site-specific requirements (e.g. environmental adjustments) then submitted for
approval.
5.3.2.4. Corrective Action Request and Tracking

Wherever quality issues are found in the supply chain, there are several international
quality standards (i.e., ISO 9000, QA 9000 – 4.13, 21 CFR 820.90, and AS 9001 – Clause
8.3) that dictate the guidelines and requirements for control of nonconforming product.
A corrective action solution gives the capabilities to submit and progress a Corrective
Actions Request (CARs) through the different phases of its lifecycle: problem
identification, analysis, resolution, and corrective and preventive actions. OPM Quality
leverages the existing Corrective and Preventive Actions solution in Oracle Quality to
correspond to the converged inventory model, referencing Process-enabled organizations
and Process Quality-enabled items. The solution also provides the ability to report on
corrective actions and supporting analyses performed.
• Oracle Inventory
• Oracle Purchasing
• Oracle Quality
5.3.4. Terminology
Term Definition
Lot Merge Lot merge can be used to merge multiple existing lots into
either an existing or a new lot.
Lot Split Lot Split is used to split a selected lot into child lots.
Lot Translate Lot translate enables users to either change the name of an
inventory lot to another name, or to convert one product to
another product. For example, you can change the lot name,
item, revision, or subinventory of an existing lot and move it
to another assembly.
Revision A particular version of an item, bill of material, or routing.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Process Manufacturing Quality Management 43
Term Definition
Warehouse Management The Oracle Warehouse Management System (WMS) is a

System (WMS) component of Oracle’s Supply Chain Management and
Manufacturing solution. It spans the areas of warehouse
resource management, warehouse configuration, task
management, advanced pick methodologies, and value added
services.
5.4. Oracle Regulatory Management

5.4.1. Overview
Oracle® Regulatory Management is a regulatory information management tool providing
hazardous material information to critical components of Oracle’s E-Business Suite. This
application enables any industries that store or ship hazardous materials to comply with
industry and government regulations. Automatically attach Material Safety Data Sheets
and other critical safety documents to Sales Orders and Shipments. Print and distribute
any safety documents as a standard part of your shipping and transportation
documentation. Oracle’s built-in “Attachments” feature will automatically associate the
safety document with the appropriate sales order line and shipments, and as part of the
Ship Confirm process your document set will be include all related safety documents.
The authoring of safety documents, along with the logic involved with adhering to
legislation and regulations, will no longer be supported from Oracle Regulatory
Management. We are working with some key vendors in this field and provide an open
interface for inbound and outbound data necessary to support these features.
5.4.2. Features
5.4.2.1. Regulatory Item Migration

Regulatory information (e.g., items, properties) is accessible to both discrete and process
items as part of our Product Information Management solution. This will provide an
easier integration to other applications like order management and shipping, and discrete
manufacturing will also be able to create regulatory items.
5.4.2.2. Regulatory Item Properties Migration

Regulatory Item Properties are an integral part of an item’s definition, currently in use by
OPM customers. Continuing support of these properties as part of the standard bundle is
available, while visibility and access to them are necessary from the discrete item master
5.4.2.3. Regulatory Formula Migration

Regulatory Formulas are formulas expressed in percentages – for instance, Hydrochloric
Acid is 95% Water, 5% Hydrogen Chloride. This data will be migrated to the Formula
Master in OPM Product Development. This will enable users of Product Development,
Process Execution, and even Costing to use regulatory data as part of their decision
making process. It is also integral to the export of data to 3rd party applications in order
to properly report on the concentration level of hazardous substances.
5.4.2.4. Track the distribution of Safety Documents – Dispatch History

Dispatch history is information regarding documents that have been sent – what
document (and version), who they’ve been sent to, which items they were sent for, and
when. Oracle will capture the dispatch history of all documents sent out via Shipping,
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Regulatory Management 44
and we’ll also provide a method to synchronize the Dispatch History with 3rd party
applications. There are 3 features related to this:
5.4.2.4.1. Public API to Store Dispatch Information
An API will be created to write Document Dispatch information to the new document
dispatch history table. The old document dispatch history table (gr_dispatch_histories)
will no longer be supported.
5.4.2.4.2. Form for Manual Entry of Dispatch Information
A new form will be created to support the manual entry of Document Dispatch
information, as well as for displaying existing document dispatch history records. Users
will be able to view the dispatched document from this form.
5.4.2.4.3. Dispatch History Report
A report will be created, using XML Publisher, to print Document Dispatch History. It
will be able to select data by Recipient, Document Type, Dispatch Method, Item and by
Dispatch Date. The XML that is generated by this report can also be sent to the 3rd
Party application in order to keep the document dispatch history synchronized between
the Oracle applications and the 3rd Party application.
5.4.2.5. OPM Data available for export – Item Property Data

Oracle data must be made available for export so that partners who are specialize in
document generation, new regulations, phrase libraries, ingredient databases, etc. can
produce the documents and supply the data we need for a complete solution. Documents
will then be stored within the E-Business suite. A Public API is provided to export
regulatory data in XML format using XML Gateway.
5.4.2.6. Document Rebuild Required Workflow

A new workflow has been created to send a notification to the Regulatory Manager when
a Regulatory Document would be rebuilt due to a change in Regulatory Item Properties
or a change in a Validity Rule/Formula that is used for a Regulatory Document.
5.4.2.7. Regulatory Document Printing

A new concurrent program will be created to allow a user to print a copy of a Regulatory
Document for an item. It will accept a range so that documents for more than one item
can be printed at one time.
5.4.2.8. Sales Order Document Required API

A new procedure will be created to determine if there are any hazardous materials
included on this Sales Order. If so, a message will be sent to the 3rd Party application to
retrieve the Sales Order information to determine if a new regulatory document must be
generated.
5.4.2.9. Shipping Attachment API

A new procedure will be created to determine if an MSDS must be attached to a
Shipment line so that it can be printed and distributed with the rest of the Shipping
documents. If distribution is required and a document has not already been attached, the
procedure will attach the document to the shipment line.
5.4.2.10. Print Regulatory Shipping Documents API
The existing API that prints Regulatory documents along with the rest of the shipping
documents will be modified to call the Document Dispatch History API for each
Regulatory document that is printed.
5.4.2.11. Regulatory Document Portal

A new portal will be created that will allow our customer’s customers to have access to
the current MSDS document for a given product. They will be able to search for the
document using several different criteria.
5.4.2.12. Territory Profiles form

The Territory Profiles form that was removed for release 11.5.9 will be re-instated. The
data entered in that form will be used by the Shipping Attachments API to determine
which document would be attached to the shipping line.
5.4.2.13. 3rd Party Data Change Workflow

A new workflow will be created to send a notification to the Regulatory Manager when a
message is received from the 3rd Party application stating that data received from Oracle
Applications has been changed in the 3rd Party application. The notification will contain
a list of the attributes that were changed for an item, as well as the value from the 3rd
Party application.
5.4.3. Release 12.0.6 (RUP6)
5.4.3.1. OPM Regulatory Management: European Regulatory Compliance

Three Field Name APIs were added to support the European Regulatory Compliance
feature.Currently, you can view, edit, and delete field names, field name classes, field
name properties, risk phrases, and safety phrases, the standard codes and descriptions for
which are seeded in the OPM Regulatory Management application. With this
enhancement, you can now create new field names, field name classes, field name
properties, risk phrases, and safety phrases. This enables you to enter organization
specific values for the new field name properties for a regulatory item. You can also
create risk and safety phrases that are text –based only and associate them to organization
specific regulatory items. The enhancement also lets you create and maintain hazard
classes and their descriptions in multiple languages without the installation of the
languages in the application, and associate them to regulatory items
5.4.4. Release 12.1.1
5.4.4.1. Regulatory Partner Certification

In order to provide a complete solution for companies to comply with industry and
government regulations, Oracle Process Manufacturing (OPM) Regulatory Management
application provides the ability to integrate with 3rd-party applications for the purpose of
Regulatory document generation.
A user can generate regulatory documents in a 3rd-party application based upon item
physical property values received from OPM Regulatory Management. The generated
documents can then be uploaded into the OPM Regulatory Management system where
they will be stored within Oracle Applications and can be attached to any applicable
object. The documents can be distributed from within Oracle Applications along with
shipping documents or can be printed/faxed/emailed to recipients. The documents can
also be distributed from within the 3rd-party applications, with the ability to synchronize
dispatch history between OPM Regulatory Management and the 3rd-party application.
• XML Gateway
• OPM Product Development
• Oracle BOM (Item master)
• Oracle E-Records
• AME
• Oracle Workflow

• Atrion
• The Wercs
5.5. Oracle Process Manufacturing Process Execution

5.5.1. Overview
Oracle® Process Manufacturing Process Execution provides functionality unique to
process industries. Oracle Process Manufacturing Process Execution ensures
manufacturing consistency throughout the production cycle by providing tight control of
ingredients and processes, balanced with the flexibility to respond to changing
conditions. OPM Process Execution supports bulk, continuous flow, and hybrid
manufacturing for make-to-stock and make-to-order environments. This capability lets
you build bulk runs, for example, as needed for economical stock quantities. It also
provides scheduling flexibility allowing you to schedule runs during specified hours,
shifts, days, or weeks depending upon your business needs.
Inventory Convergence is a major change in R12. The Process Inventory and Oracle
Inventory applications will be converged into a single system that will be used to manage
inventory across the entire Oracle E-Business Suite seamlessly, regardless of the type of
manufacturing that a business employs. Process features are added to Oracle Inventory to
support Process characteristics, such as dual units of measure, grade, child lots as a
subdivision of lot-controlled inventory, and the use of material status.
As a result, Process Execution has been modified and enhanced to use Oracle Inventory.
The existing cross-functional integrations with Advanced Planning and Scheduling and
Order Management will be preserved, while leveraging Warehouse Management System
functions.
In addition, several other smaller enhancements are made in Process Execution.
5.5.2. Features
5.5.2.1. Impact of Inventory Convergence on Process Execution

Process Execution is now using the Oracle organization structure and converged Oracle
Inventory Item Master, transactions, and reservations. This including the following
changes.
5.5.2.1.1. Organization Structure
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Process Manufacturing Process Execution 47
Inventory Organizations – Batches and Firm Planned Orders (FPO’s) take place in an
inventory organization that is defined as a plant, a research and development
laboratory, or both.
Subinventories and Locators – Batches consume from and yield into subinventories
and locators within the inventory organization.
Organization Parameters – Existing Process Execution profile options are migrated to
organization-specific parameters. This will make it easier to set business rules by
organization.
5.5.2.1.2. Items and Master Data
Item entry and validation – A multi-segment item number is supported, and any item
entered on a batch or FPO must be designated in the item master for that inventory
organization as “Process Manufacturing Enabled”.
Item revisions – The item revision capability in Oracle Inventory is extended to items
in Process-enabled inventory organizations when establishing setup data and
performing inventory transactions. The user will be able to specify a desired revision
on a formula/batch material line, and will be required to enter a revision on material
transactions for items that are revision controlled.
Material status, grade, action, and reason code migration – Material status, grade,
quality actions, and reason code support and security will be migrated to Oracle
Inventory. Therefore, any lookups for these entities are replaced to reference the
Oracle Inventory tables.
5.5.2.1.3. Reservations
Reservations replace the ‘pending lot allocations’ used currently in batches. Unlike
the current pending lot allocations, however, detailed reservations are ‘hard’
reservations; once you have reserved material to a batch, other sources of demand are
prevented from reserving or using this inventory.
High Level and Detailed Reservations – Batches support high level and detailed
reservations, enabling users to guarantee that inventory will be available to a batch.
High level reservations are at the organization level and detailed reservations are at
the lot, subinventory, and locator level. Users will also be able to enter partially
detailed reservations, specifying, for example, the lot but not the subinventory or
locator.
Automatic creation of detailed reservations – Detailed reservations can be created by
the system using picking rules to select the inventory. This is analogous to the
autoallocation functionality that currently exists in OPM. The material can be
selected based on the same criteria that are currently used in autoallocation, such as
First-In-First-Out or First-Expired-First-Out rules, and single/multi lot rules.
Select Available Inventory screen – Material can be selected and reserved from the
new Select Available Inventory screen. This replaces the current Pick Lots/Locations
screen, and allows you to select from a list of available inventory.
Manual entry of detailed reservations – Detailed reservations can be entered
manually.
Reserving from other documents – In addition to reserving from onhand inventory to
a batch, you can reserve from other sources of supply to other sources of demand. For
example, a batch will be able to reserve the pending supply from a purchase order.
The pending product yield from one scheduled batch can be reserved to an ingredient
line of another batch. The pending product yield from a batch can also be reserved to
a sales order.
5.5.2.1.4. Transaction Model
Transaction types will be either renamed or new ones created to support the issuing
and return of ingredients, and the yield or return of products, coproducts, and
byproducts.
Lot Genealogy – All lots consumed by or yielded by batches will be viewable from
the Oracle Inventory Lot Genealogy inquiry.
5.5.2.1.5. Move Orders
The optional use of move orders will be supported to control the movement of
material from the warehouse to the shop floor.
5.5.2.1.6. Mobile Supply Chain Applications
Process Execution will support the use of mobile devices for many batch activities,
such as the entry of ingredient consumption, product yield, and resource usage.
5.5.2.1.7. Warehouse Management
Customers who purchase the Warehouse Management System (WMS) will be able to
use this with Process Execution. Process Execution and WMS will interact through
the use of move orders. WMS Picking and Putaway rules will be available for use
with Process Execution, and you will be able to yield product into an LPN. An LPN,
or License Plate Number, is the basic entity managed by WMS; it can, for example,
represent a pallet or similar grouping of inventory.
5.5.2.1.8. Viewing Historical Batch Data
Screens will be provided to allow users to view batches processed before
Convergence. These screens will be display-only, and will allow the user to view all
information viewable on the 11i10 edit screens, by batch, including the inventory
transaction data.
5.5.2.2. Screen Redesign

The Batches and Batch Material Details forms will be combined into a Batch Details
form to allow the user to see more information on one screen and reduce the need to
navigate between screens. Batch header information that was previously hidden by
default will be displayed on an Additional Information tab on the Batch Details screen.
5.5.2.3. Rescheduling of Scaled Batch

When a batch is scaled, the user will have the option of specifying that the batch duration
would be recalculated and the batch rescheduled.
5.5.3. Release 12.1.1
5.5.3.1. Multi-Batch / Support for Mass Transactions

On the shop floor, due to the nature of the products being produced, batches of similar
nature will be sequenced and processed together. Transacting batches independently will
be time and resource consuming activity. To improve the usability and reduce the time
taken to transact batches, a new Mass Batch Actions form has been created. This provides
an option to transact several batches at one time.
The Mass Batch Actions form gives the user the ability to group batches based on
organization, product, recipe/version, formula/version, routing/version, operation/version,
batch status, planned start date/end date range and range of steps. Also the user will be
able to perform mass batch actions such as release, complete, close, reopen, revert to
WIP, un-release and auto detail on a set of batches based on the selection criteria.
5.5.3.2. Make-To-Order
Manufacturers need the ability to produce an item in response to a customer order. The
Customer Service Representative needs to have visibility of the Batch associated to the
order line. Data of particular relevance includes Planned / Actual Start dates, Planned
Completion dates and yield lot so that they may relay that information back to the
customer.
The Make-To-Order solution provides the ability to create a Batch or an FPO in response
to a Sales Order line. Configurable and flexible user defined rules will establish when an
order line qualifies for Make-to-Order. When an order is booked, processing will be
instigated for any qualifying lines to generate a new Batch or FPO as appropriate. The
Customer Service Representative will receive a notification advising of the Batch/FPO
creation and providing a cross reference of Sales and Batch/FPO numbers. The
Batch/FPO supply will be immediately reserved against the driving sales order line.
5.5.4. R12.2
5.5.4.1. Oracle Process Manufacturing Outside Processing (OSP) (12.2.4+)

Manufacturers do not always have the capabilities or equipment to perform all the steps
in their manufacturing process to produce their products. Many times they must send
material out of their plant for a step in the process to produce their finished goods. When
this outside manufacturing is needed users must be able to indicate this in the routing and
track the material and cost when it leaves their facility. They also must apply the cost of
this outside processing to the overall cost of the finished good.
Key Features:
• Ability to define a Resource as Outside Processing Resource: Plant Resource
and Generic resource can be associated with an outside processing item, so that
the resource can be used for outside processing.
• Automatic creation of a Requisition at Batch Creation, Batch Release, or
Step Release: When there is an operation in a routing that is not performed in-
house and work/service is required, the software provides the ability to create a
Requisition for this work/service.
• Manual Creation of Requisitions: This option allows you to automatically
charge outside processing resources at an OSP step, but does not link the creation
of the requisition to either creation or processing of the batch or step.
• Ability to define approvals as “Automatically/Manual” for PO/Req: This is

applicable when the Order is of high value and approvals are needed for the
purchase order to move ahead. The approval hierarchy has to be set and this can
be handled only on need by basis. Although certain low value PO can be of pre
approved nature as well.
• Manual Creation of Purchase Order and Lines: The user is able to define
manual Purchase order with outside processing items. For each purchase order
line, a batch that is to be charged needs to be specified. Transactions can be
tracked. Resource Cost or PO price can be used for resource costing depending
on the flag checked.
• Ability to receive full or partial quantity in an OPM enabled organization:

The Purchase Order can be received for the full or partial quantities and the
quantity delivered to the shop floor updates the OSP Actual step quantity.
• Managing Returns and Adjustments: Return of OSP item/service is allowed
for rework. Also the capability to reverse over-receipts that are erroneously
transacted is allowed in the system.
• Ability to integrate with OPM Costing: The Purchase Order that was raised on
the vendor is for a service. The value of the service is added to the Product cost.
User will define a Standard Cost for the resource associated with the Outside
Processing step. The organization must be setup for Standard Cost. Also the
Standard rate flag to choose between Resource Cost and PO Price cost is to be
introduced. Actual cost and Lot cost to be supported in later releases.
• Workflow Notifications: All the existing discrete notification have been added
for OPM
o Intermediate Shipment
o Ship and Receive Intermediates
o Notify Second Buyer and Supplier
o Update outside Processing Need by Date
• Multiple Outside Processing Steps per Batch: A Batch can have multiple OSP
steps that can be associated with the same or the different supplier. This can help
enable the customer to have various suppliers performing different operation in
the batch.
• Synchronization of the Batch and Purchase Order: The system will

synchronize the Batch to the Purchase Order and back. The system synchronizes
the PO whenever there is a Batch action like:
o Batch Reschedule
o Step Reschedule
o Batch/step quantity change
o Re-routing
o Batch Cancel
o Batch Termination

Oracle Inventory
No update in R12.
5.5.7. Terminology
Reservation A link between a source of supply and a source of demand. A
reservation guarantees availability of material to the demand.
Move Order A document that controls the planned and actual movement of
material from one location to another.
Make to Order (MTO) An industry term describing the process of manufacturing
products to supply customer orders.
5.6. Oracle Process Manufacturing Extensions for Endeca – v5
5.6.1. Overview
In process industries, variability of ingredients and processes are a common issue. Oracle
E-Business Suite Process Manufacturing Extensions for Endeca empowers manufacturing
supervisor managers, supply chain analysts and business users with the ability to find
these issues which hamper productivity and resolve them.
Key Features:
values in key attributes like Expiring Lots, Batches, Ingredients, Steps, Resources
and Sales are displayed
• 360 degree view of Batches and Expiring Lots: Supervisors can quickly
monitor the impact of the delayed batches and quality issues on a color-coded
dashboard.
• Batch Yield: Quickly identify the jobs and customers with low yield actual to
plan to take remedial actions and improve productions efficiency.
• Unallocated Ingredients: Gain immediate visibility into batches that require lot
assignments on the shop floor
• Expiring Lots: Easily identify lots that are about to expire and extended their
shelf-life proactively
• Quality Results: View sample results across plants/organizations for products
and ingredients.
5.6.1.1. Oracle Cost Management Extensions for Oracle Endeca

Oracle OPM Cost Management Extensions for Oracle Endeca allows users to discover
transactions and related accounting information in real time thereby providing
opportunity to effectively manage the period close process, reconcile accounting as well
as ensure accuracy of accounting across sub ledgers. There are two intuitive user-
interfaces – the Period Health Check helps to discover transactions that are either
preventing or delaying period close and the Transaction Accounting Register assists in
reconciliation of accounting for all supply chain subledgers .
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Process Manufacturing Extensions for Endeca – v5 52
Period Health Check
Transaction Accounting Register
Key Features:
values in key attributes like Organization, Transaction, Batch Receiving,
Maintenance, and Transfers are displayed for Period Health Check. For
Transaction Accounting Register the attributes include Organization, Job,
Account, Transaction, Receiving and Write-off
• 360 degree view of Pending Transactions and Incomplete Account Entries:
Supervisors can quickly monitor the impact of the unprocessed material and
shipping, pending transactions and interfaces and incomplete batches on a color-
coded dashboard.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Process Manufacturing Extensions for Endeca – v5 53
• Fully integrated with Oracle E-Business Suite: Fully integrated with OPM
Cost Management and honors the same Organization security configured in E-
Business suite at run time instantly.
5.6.2. Endeca v5
5.6.2.1. Oracle Process Manufacturing Laboratory Management Visibility
The OPM Quality pages provide the tools for quality managers and technicians to
monitor and improve efficiency of quality operations by having real-time information to
prioritize the samples to be tested, identify the lot expiry or retest samples and the trend
of the tests and sample dispositions from different sources. In addition, answers to
questions related to the quality of the material and process so that the non conformance of
the material is identified and corrective action are taken.
Features include:
values in key attributes like test name, sample number, disposition are displayed
• Quality Metrics – Graphical display of sample status and load information so
that with a glance superviors can assess productivity and production issues
• Corrective Actions – potential quality issues are highlighted in the tag cloud
region with font size indicating the frequency of occurrence
• Sample Insights - Quickly review sample dispositions, sample delays and test
expirations to proactively reassign tests to analyst for increase laboratory
productivity
5.7. Oracle Mobile Process Production Supervisor for Oracle E-Business Suite
5.7.1. Overview
With Oracle Mobile Process Production Supervisor for Oracle E-Business Suite, process
manufacturing supervisors can monitor batches and take quick actions on the go.
- Search batches and steps or barcode scan to view progress (on track, delayed,
exceptions, started late)
- View batches, steps, exceptions, and material details
- Perform quick actions like release, complete, reschedule, cancel, and email
- Manage production exceptions related to unallocated ingredients, expiring lots,
products, and by-products
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content DocumentOracle Mobile Process Production Supervisor for Oracle E-Business Suite 54
Oracle Mobile Process Production Supervisor for Oracle E-Business Suite is compatible
with Oracle E-Business Suite 12.1.3 and 12.2.3 and above. To use this app, you must be a
user of Oracle Process Manufacturing, with mobile services configured on the server side
by your administrator.
5.7.2. V.1.1.0


There are accessibility improvements in the Batches Tile page, Related Information

5.8. Oracle Manufacturing Execution System (MES) for Process

Manufacturing
5.8.1. Overview
Oracle is closing the gap between traditional Enterprise Resource Planning (ERP) and
Manufacturing Execution Systems (MES) for process manufacturers by adding a new
product to the process manufacturing product suite. Oracle MES for Process Industries
adds new production batch execution functionality and increases usability for
manufacturing operators, enabling fully paperless batch recordkeeping and adding
support for dispensing and pre-weigh operations. Traditionally, manufacturers had to
invest in building and maintaining costly interfaces between ERP, which held financial,
human resources, inventory, sales, purchasing and master recipe data and MES, which
manages the actual execution activities of the production batches on the shop floor.
Oracle is building deeper native MES capabilities into its applications so that costs, data
replication and risk of errors will be reduced, while data accuracy, process repeatability
and information visibility will be improved by managing all information in a single, real-
time database.
This product is designed for use in many process industry plants, especially those that are
looking to move to electronic batch recordkeeping and those that previously might have
opted to purchase a third-party MES. It offers the advantage of providing true enterprise-
wide information from the shop floor to the boardroom.
5.8.2. Features
The MES for Process Industries project takes a fresh look at how the manufacturing
process is actually executed, improves usability, fills functional gaps for process
manufacturing industries and provides the opportunity to eliminate significant amounts, if
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content DocumentOracle Manufacturing Execution System (MES) for Process Manufacturing 55
not all paper from the manufacturing batch recordkeeping process. This has been
accomplished with the addition of the following features and new functionality.
5.8.2.1. Batch Journal

The Batch Journal for a batch is created at the time a batch is created. The Batch Journal
is instantiated with all the details of the batch such as Recipe details, Process Instructions,
SOPs, and quality sampling plans. Once this Batch Journal is created, a deferred
Electronic Signature event is created for the approval of the Batch Journal. This is the
equivalent of the Master Batch Record approval.
The following are the capabilities that are available out of the Batch Journal
functionality:
• It is available “On Demand” during Batch Execution and available as an
electronic record after batch closure.
• It is available to be viewed online or printed.
• It is available from the batch header at any point in the batch cycle.
The SOPs attached to the recipe, formula, or routing components are available in the
Batch Journal as hyperlinks.
Batch Journal contains all the major events (along with dates and names of people) that
has happened to the batch:
• Batch Creation
• Master Batch Record Approval
• Batch Release
• Allocation
• Consumption details
• Material Yield details
• QC test results with an ability to drill down into the data
• Resource transactions
• Process parameter reporting
• Batch complete
• Batch cancel
• Batch Terminate
• Batch Reopen
• Electronic signatures recorded during the batch life cycle.
• Equipments used for the manufacturing process
• Information on each of the ingredients used, the lot numbers, quantity dispensed
and quantity used
• Yield information
• Identification of the persons performing and directly supervising or checking
each significant step in the operation
• Details of all critical and non critical deviations recorded
• Evidence of acknowledgement from the operator that he/she followed the process
exactly as per the SOP
• Electronic copies of all labels generated during batch execution and QC.
The batch journal is the complete record of the lifecycle of the production batch. Ideally,
it will replace the paper batch record, even in FDA-regulated industries.
5.8.2.2. Dispensing and Preweigh
Dispensing is a key requirement for many process manufacturers. Dispensing of the right
materials to the right batches prior to the manufacturing process is a key activity. This
process is especially critical when working with the active ingredients (APIs) in a drug,
chemical, food and beverage product formulation.
The formulation process requires right materials to be allocated with specific quality
parameters and in right quantities. Since the quantities that would be formulated may run
into decimals, the accuracy of weights is very critical. To enable this dispensing functions
have been integrated with weigh scales. Additionally, functionally to manage cleaning of
dispensing booths has been provided.
5.8.2.3. Label Management

Labels will be printable throughout the dispensing and manufacturing process.
5.8.2.4. Deviation Management

Deviation management is a key component for an electronic records system. The various
types of deviations that need to recorded are:
• Deviations from quantity consumed/yielded
• Deviations from specifications set for process parameters
• Item substitutions
• Resource substitutions
• User Defined Events
Users can classify deviations as either Critical or Non Critical. The user also can specify
the actions that need to be taken after a deviation is recorded. For example, critical
deviations need to be signed off by a QC Manager while the Production Supervisor can
sign off Non Critical deviations.
Critical deviations must be approved prior to closure of the batch and prior to material
disposition. If additional follow-up and analysis documentation is created, it is associated
with the batch and be incorporated into the batch journal. Also, the users can view any
Standard Operating Procedures that are linked to this type of deviation.
In order to capture deviations of quantities consumed/yielded, it is necessary to define
tolerances for items. These tolerances can be defined at various levels – Inventory
Organization, Item, Recipe/Formula and Recipe/Formula line item level.
5.8.2.5. Simplified Production Reporting

A new user interface has been provided to greatly simplify the batch process for operators
on the shop floor, while providing more direction to the operators to follow the best
practices defined in the recipe. In the past where operators were presented with a wide
array of screens, which had to be navigated in order to enter batch information, now
operators are able to very quickly and efficiently focus in on the tasks that are awaiting
their attention, and the system will lead them through those tasks. All along processing
instructions are up-to-date SOPs are at the operators’ fingertips.
5.8.2.6. Improved Processing Instruction and SOP Visibility

A new production process-oriented approach has been taken with this product. Rather
than managing production from a materials first perspective, OPM MES is designed with
the operator on the shop floor in mind. Processing instructions capability has been vastly
improved from the definition and execution standpoints.
When defining processing instructions, you may now associate actions to each
instruction. This combination of process instruction text and specific actions guide the
operator through the pre-defined process that they need to follow, as defined in the
recipe. Additionally, you may embed links to standard operating procedures (SOPs) in
the processing instructions. SOPs are typically used to describe broader procedural sets
that may be used beyond a particular recipe. For instance, the steps involved in cleaning a
particular model of equipment.
From the operator standpoint, the processing instructions are now prominently displayed
when a batch is processed. Actually, the processing instructions are intended to lead the
operator through the batch process, by documenting the proper things to do, where and
when they need to do them.
5.8.2.7. Operator Certification

Per 21 CFR Parts 211.25 and 820.25, the users involved in manufacturing and testing
activities in FDA-regulated industries need to be adequately trained to ensure product
quality.
To address these requirements, the following are the capabilities have been added:
• Based on the training records available, a training matrix may be created which
has information on which operator is trained on which resource and materials.
• Whenever an operator enters his/her signature, the system would validate that the
user is indeed trained and hence authorized to operate the resource.
5.8.2.8. Simplified Electronic Signatures / Initialing

The Oracle E-Records signing process now offers a simplified and streamlined signing
process for signature capture on very specific events, such as entry of a dispensing
weight, lot allocation and in-process deviation capture. These are transactions in which
the information that the signer is attesting to is right on the screen that they are on, so the
content of what they are signing is very clear.
5.8.3. Terminology
Term Definition
SOP Standard Operating Procedure

CFR Code of Federal Regulations
FDA United States Food and Drug Administration
5.8.4. Release 12.0.2 (RUP2)
5.8.4.1. Touch Screen User Interface

Oracle MES for Process Manufacturing brings shop floor execution closer to the
operators with the introduction of touch screen user interface in areas such as,
Operator Workbench (Material Transactions, Resource Transactions, Process
Parameters), Dispensing, and Reverse Dispensing. Each screen has been updated
with an intuitive, easy-to-use user interface, providing near real-time data capture at
the shop floor to facilitate compliance and improve productivity.
5.8.4.2. Dispensing Area

Dispensing Area is a new entity that represents the physical area in a warehouse
where the Dispensing activity is carried out. Dispensing Area is linked to
Subinventory which helps in tracking inventory movement for Dispensing, Resource
Usage, and Operator Access in a specific area. Additionally, the Dispensing Area
can be divided into smaller rooms called Dispensing Booths which are the specific
locations for Dispensing activity. Each Dispensing Booth can be monitored for
environmental conditions such as humidity and air quality.
5.8.4.3. Dispense Planning

Dispense Planning is a new workbench for supervisors to plan all dispensing
activities. Similar activities can be grouped together for planning a Dispense
Campaign, as well as assigning priority and resources for Dispensing. The Gantt
chart user interface displays resource overload, helping supervisors to better manage
their resources.
5.8.4.4. Operator Certification

Operator Certification satisfies the regulatory requirement of FDA 21 CFR Part
211.25 for Personnel Qualification. It enables a corporation to identify the required
skills and training needs, as well as certification approvals, for an operator to perform
production activities. Operator Certification is seamlessly integrated with Oracle
HRMS for all needs related to skills definition, training needs, and certification.
5.8.4.5. Least Cost Formulation Batches

This feature was introduced in the New Product Development module in Process
Manufacturing R12 and is now supported by MES for Process Manufacturing. A
user can now formulate to target product specifications and leverage this formula in
MES.
5.9. Oracle Process Manufacturing Cost Management

5.9.1. Overview
Oracle® Process Manufacturing Cost Management combines detailed cost-tracking
features with flexible analytical tools to help process manufacturers determine their true
product costs. Oracle Process Manufacturing Oracle Process Manufacturing Cost
Management is designed to support multiple costing methods, including standard and
actual costs, as well as lot costing. OPM Cost Management provides four possible
approaches for obtaining average actual product costs. It also supports your activity-
based costing initiatives, facilitates comprehensive “what if” analysis, produces variance
reports, conducts margin analysis, and improves your inventory-valuation accuracy.
In the converged inventory model, Process and Discrete Inventory Organizations can
potentially co-exist within the same Operating Unit. However, Discrete Costing and
Process Costing will remain distinct applications. Inventory Organizations that are
Process Enabled will use Process Costing, while Discrete Inventory Organizations will
use Discrete Costing.
To prevent both systems from costing the same transactions, Process users are denied
access to Discrete Costing forms. Therefore, a Process-Enabled organization can not set
up costs or costing information in the Discrete Costing application.
Additionally, in a converged environment, it is possible for inventory transfers to occur
between Process Organizations and Discrete Organizations. When such transfers occur,
both costing applications will properly account for their respective side of the transaction.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Process Manufacturing Cost Management 59
5.9.2. Features
5.9.2.1. Maintain Process and Discrete Costing Applications

With Inventory Convergence, the use of organization security is not be sufficient to
restrict process organization users from using discrete forms. Discrete Costing forms,
Concurrent Programs and reports have been modified to prevent a process organization
user from accessing discrete costing setup forms, reports and other programs. This was
necessary to ensure that process transactions are not accounted for twice, once in Discrete
Costing and again in Process Costing. The changes will not affect a discrete user’s
experience and hence will be transparent.
5.9.2.2. Costing of Transfers Between Discrete and Process Inventory Organizations

As described earlier, in the converged inventory model in R12 both Discrete Inventory
Organizations and Process Inventory Organizations share the same inventory setup and
transaction model. It is expected that there will be transfer of materials from a Process
Org. to a Discrete Org. and vice versa in the normal course of business in the enterprise.
Along with the transfer of materials the cost of the material would also be transferred to
ensure that the values of inventory movements/transfers are properly tracked in the
various sub-ledgers and ultimately in the General Ledger. In addition, in the case of
organizations that use some form of Average Costing the cost of the incoming material
would also be considered for the Perpetual or Periodic averaging.
The need for this feature arises from the fact that Discrete Organizations can use a
perpetual costing method while Process organizations use Period Costing. If the material
is transferred from a Process Organization to a Discrete Organization, the cost is not
known till the end of the period while the Discrete Organization needs the cost at the time
of receiving the material.
To ensure that material can be easily transferred and accounted for, transfers between
Discrete and Process Organizations will use a transfer price. The transfer price needs to
be set up between the organizations. A new account, Interorg Profit, is defined to capture
the difference in costs in the sending organization. This difference can be wiped out at the
end of the period through a manual reconciliation process.
5.9.2.3. Subledger Accounting replaces MAC

The Manufacturing Accounting Controller is replaced by the powerful and versatile
Oracle Sub Ledger Accounting (SLA). Subledger accounting provides tools that allow
users to configure their entries for applications requiring accounting. It includes an
architecture with a unified user interface and programs that can generate accounting for
both Oracle and non-Oracle applications. The adoption of the Oracle Subledger
Accounting in Oracle Process Manufacturing supplants the existing Manufacturing
Accounting Controller (MAC) application.
The Subledger Accounting streamlines accounting by providing detailed representations
based upon transactions from various applications. Users can rapidly create predefined
accounting policies; simultaneously create multiple financial representations using
different methods and rules. Accounts are mapped in the application, and, similar to the
MAC application, you can specify detailed rules on how the accounts will be determined.
Subledger Accounting provides users the ability to configure all components of their
subledger journal entry. This include the ability to determine what lines, accounts,
descriptions and reference information would be stored on the journal entry
The Account Derivation Rules engine provides a very flexible way to determine what
account is used for each line of the journal entry. Account Derivation Rules have the
following features:
• Determine the complete account code for journal entries or
• Determine values for individual segments for the account code for journal entries or
• Create account codes based upon constants, source values, or mapping sets or
• Use conditions and default values for complex rules
Subledger accounting is an intermediate step between subledger products and the Oracle
General Ledger. Journal Entries are created in subledger accounting and then transferred
to the Oracle General Ledger. Each subledger transaction that requires accounting is
represented by a complete and balanced subledger journal entry stored in a common data
model. Subledger accounting information can be used by analytical applications, reports
and in inquiries.
5.9.3. Release 12.0.3 (RUP3)
5.9.3.1. OPM Financials: Detailed Subsidiary Ledger Report

The Detailed Subsidiary Ledger Report provides a comprehensive online inquiry based
on accounting events and journal entries and the user can drill down to the exact
transaction that resulted in the event or journal.
5.9.3.2. OPM Financials: Non-Recoverable Taxes Support in Actual Costing

Actual Costing now correctly picks up non-recoverable taxes and all accounting entries
reported by OPM Financials are correct.
5.9.3.3. OPM Financials: Reconciliation Enhancements in Actual Costing

Previously, Actual Cost only considered closed production batches in a month which
resulted in production yield quantities under reported in cost calculations as well as
double counting of yield quantities of open batches in a specific costing period. Actual
Cost, in certain scenarios, included the invoice price override but did not take the invoice
quantity into consideration. As a result of these two issues, the inventory value reported
at month end did not tie in with the inventory account balances as reported in the
Subledger and GL. Actual Costing now considers all production yield quantities in cost
calculations, and considers the IPV amounts in invoices as additions to the PO Receipt
value in cost calculations.
5.9.4. Release 12.1.1
5.9.4.1. Costed Indented Bill of Materials Report

The Indented Bill of Materials (IBOM) Report is an informative and valuable feature of
Process Manufacturing available via Formulator responsibility. A Costed IBOM report
has been created allow OPM Costing users to see Standard Costing information at all
levels of Indented Bill of Materials (IBOM).
The Costed IBOM Report accesses the most recent cost rollup data and provides
summary information for the entire product BOM, with a single line for each item,
indented for each succeeding BOM level, and organized vertically so that parent/child
relationships are clearly shown. Costing summary data is presented for the Material,
Resource, Fixed Overhead, and Standard Cost Adjustment usage categories for each
product at each level of BOM. The cost component detail section of the report presents
cost component class details for the formulations shown in the summary data portion of
the report.
5.9.5. Release 12.1.2
5.9.5.1. Support for Landed Cost Management

Landed Cost (LC) is calculated in order to accurately measure the corporation’s costs and
profitability by the good/item, product line, lot, business unit, organization, etc. They
play a significant role in actual costing, evaluating on-hand inventory, as well as setting
sales prices and revenue forecasting. Oracle Process Manufacturing Cost Management
will use these landed costs when calculating the value of an item.
5.9.5.1.1. Ability to use Receiving Transactions LC for OPM Costing
The OPM costing engine is able to consider the Receiving transactions LC calculated by
LCM. As OPM requires charge allocation details to process the costing calculation,
LCM is able to calculate and store the detailed LC information at allocation level for the
receiving transactions.
5.9.5.1.2. Ability to use Receiving Corrections LC for OPM Costing
The OPM costing engine is able to consider the Receiving Corrections LC. LCM will
calculate and store the details of LC information at allocation level for each Receiving
Correction transactions.
5.9.5.1.3. Ability to use Return to Vendors LC for OPM Costing
The OPM costing engine is be able to consider the return to vendors LC. LCM will
calculate and store the details of LC information at allocation level for each Receiving
Returns transactions.
5.9.5.1.4. Actual Landed Cost
As a result of the acknowledgment of actual pricing information from the Payables
Invoices, LCM calculates the actual Landed Cost variations from the previous Landed
Cost calculations.
Based on this information, LCM will post the LC variation for each component type
(item, charges, and taxes) – necessary to calculate the cost variations.
5.9.5.1.5. New LC adjustment Import process to populate LC adjustments in OPM
New Landed Cost Adjustment Import process populates Estimated and Actual LC
adjustments into OPM repository.
5.9.5.1.6. LC Adjustments support in Actual Cost Process
Actual cost process support Item and Charge component types of LC adjustments in cost
calculations. Also Actual cost process support prorated adjustment if the adjustment is in
a period different from the receipt period.
New profile GMF: Landed Cost Adjustments Transfer Method to Inventory in Actual
Costing introduced to apply LC adjustment based on period opening inventory balance.
5.9.5.1.7. LC Adjustments Support in OPM Lot costing
OPM Lot Cost Process supports LC adjustments in lot cost calculations
5.9.5.1.8. LC Adjustments Support in OPM Accounting Pre-Processor
OPM Accounting Pre-Processor generates journal entries for LC adjustments for all OPM
cost types. New SLA event types are introduced to support LC adjustments
5.9.5.1.9. Modified OPM costing forms and reports for LC adjustments
• Actual cost view transactions window displays LC adjustments
• Detailed Subledger display journal entries for LC adjustments
• Lot Cost History report display LC adjustments information
5.9.5.1.10. Allow Process manufacturing organizations to be LCM enabled
The Inventory Organization definition form will allow the Process Manufacturing
organizations to be LCM enabled.
5.9.5.1.11. Landed Cost Visualization by PO
Currently, PO provides an option on the Purchase Orders (html) page to display the
Landed Cost (or acquisition cost) information as part of PO Freight and Special Charges
project.
LCM provides a new view page that summarizes the landed cost information by purchase
order. The costs amounts are summed by LC reference (e.g.: goods, freight, insurance,
etc.).
As a result of the implementation of the OPM and LCM integration, the current view
acquisition costs in PO will also display the acquisition cost information based on the
LCM data model.
Note: The display acquisition cost information from existent POs before LCM
implementation is still supported.
5.9.6. Terminology
Term Definition
Account Derivation Determines what account is used for each line of

Rules the journal entry
Transfer Price The Transfer Price is the price charged by one part
of a company for products and services it provides
to another part of the same company, in order to
calculate each division's profit and loss separately.
5.10. Process Manufacturing Planning

5.10.1. Overview
The Process Inventory and Oracle Inventory applications are converged into a single
system that is used to manage inventory across the entire Oracle E-Business Suite
seamlessly, regardless of the type of manufacturing that a business employs. Process
features will be added to Oracle Inventory to support Process characteristics, such as dual
units of measure, grade, child lots as a subdivision of lot-controlled inventory, and the
use of material status.
As a result OPM MRP will not be brought forward and all planning with OPM will
utilize Oracle’s Advanced Planning and Scheduling (APS) in an unconstrained manner
with enhancements to use Oracle Inventory.
5.10.2. Features
5.10.2.1. Integration of Production Batches

The integration of OPM and ASCP brought production batch data to APS through the
collection process. This data encompassed inventory transactions, material and resource
usage, and organizations (OPM Plants). All the current pulls of data are now changed to
reflect Oracle Inventory instead of OPM Inventory. The OPM organization now
leverages the Oracle organization structure, as the OPM organization and plants will be
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Process Manufacturing Planning 63
discontinued. The OPM Shop Calendar, which is used in the creation and rescheduling
of batches, will be replaced by the Oracle Work Day Calendar.
5.10.2.2. Integration of Recipes

The integration to APS brings the OPM Recipes to ASCP through the collection,
enabling planning to suggest production based on these recipes. With the change in the
organization structure recipes and resources reflect the new organizations to enable
planning to project resource loads and production batches against the correct entities.
5.10.2.3. Integration of Inventory

Prior to R12, inventory transactions go against OPM inventory tables. This includes lots,
statuses, locations, etc. The convergence of OPM inventory into Oracle inventory results
in all inventory pulls going to APS to be remapped to now use Oracle inventory. data
pulls from OPM inventory are stopped.
5.10.2.4. Item Cost

Item cost information is used in ASCP when running an optimized plan to maximize plan
profit. The OPM item cost information will still be maintained in OPM but the
organization structure changes will be reflected.
5.10.2.5. Shop Calendar

The OPM Shop Calendar is used with ASCP when scheduling production batches. The
calendar defines work and non-working days and shifts for the production plant. ASCP
schedules production batches accordingly during working days and shifts. Oracle
inventory also has a calendar called the Work Day Calendar. The “OPM Shop” Calendar
will be replaced by the “Oracle Work Day” Calendar. ASCP will then use the “Work
Day” Calendar when scheduling OPM production batches.
5.10.2.6. Forecast
The OPM Forecast will be replaced by using the existing discrete forecast forms. This
will provide OPM users with greater flexibility along with the use of API’s to load a
forecast into OPM. Not all users will need or want to use Demand Planning and the use
of the discrete forecast provides users with a basic tool.
5.10.2.7. Item Substitution Effectivity Date Support

The Item Substitution feature in OPM is being incorporated into the Formula Change
Request implemented in 11i.10. The ingredients associated to a formula will be able to
be substituted based on a valid list and associated effective dates as to when the substitute
ingredient is valid. Advanced Supply Chain Planning (ASCP) has current logic to use
substitute ingredients (components). The collection process will now pass these valid
substitute ingredients and dates to ASCP for effective planning. Planning will
recommend batches based on formula changes that will be effective at the Planned Start
Date of the Batch.
5.10.2.8. Firming Feedback from ASCP to OPM

The planner must be able to firm a “Planned Suggestion” in the ASCP workbench and
this suggestion will be implemented as “Firm” in OPM. OPM production batch has a
firm flag and this flag needs to be updated by a “Firmed” suggestion from ASCP. OPM
currently enables the user to manually update the firm flag on a batch in this way ASCP
will not replan the batch. This firm flag also must be automatically updated from the
ASCP when a suggestion is implemented and the batch created in OPM.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Process Manufacturing Planning 64
Advanced Supply Chain Planning (ASCP) suggests planned production orders when
using OPM. These suggestions can be “firmed” by the user and when the suggestion is
implemented in OPM (batch creation) the batch will automatically firmed. ASCP will
not reschedule a firmed batch.
5.10.3. Release 12.1.1
5.10.3.1. Resource Batching

Manufacturers must be able to ensure full utilization and efficient use of their resources.
In order to do that, they must be able to gather multiple production batches being
processed from upstream operations, and load them together into the same piece of
equipment to be processed concurrently.
OPM Planning has been enhanced to take advantage of the Resource Batching
functionality that is available in Production Scheduler and Advanced Supply Chain
Planning. A user will be able to go to the Plant Resource form, explicitly define a given
resource as batchable, and define a minimum and maximum spot capacity and a pull
forward window. Within Production Scheduler, a user can specify attributes values (such
as Temperature, Color, Duration etc) which can be used to group products/batches
together for processing. Production Scheduler and ASCP can then plan and schedule
multiple batches in a batchable resource simultaneously.
• OPM Process Execution
• OPM New Product Development
• OPM Cost Management
• Oracle Advanced Planning and Scheduling
5.10.5. Terminology
Term Definition
API Application Programming Interface

Batchable Resource A machine / oven / kiln (or similar) that can process many
items simultaneously, providing they share 1 or more similar
attributes (such as Temperature, Color, Duration etc).
5.11. OPM System Administration – Inventory Convergence Migration

5.11.1. Overview
In order to support a common organization and inventory model, the Process
Manufacturing development team has ensured that the fundamental data defined to run
your business is carried forward into the new tables, and transformed where necessary to
reflect data model changes. Migration and data transformation scripts will be provided
for this purpose, and run in different phases in order to have a minimal impact on
performance.
Many of the OPM System Administration functions will become obsolete as equivalent
functions already exist elsewhere in Oracle Applications.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document OPM System Administration – Inventory Convergence Migration 65
5.11.2. Features
5.11.2.1. Convergence Migration

5.11.2.1.1. Organization Migration
Migrating the organization structure touches the areas of OPM Financials, OPM System
Administration and OPM Inventory. The elimination of the OPM organization means
that the following will be migrated:
• OPM Company and Fiscal Policy will be validated against the operating unit, set
of books and legal entity definitions
• OPM Organizations, which are not companies, will be created as Inventory
Organizations. Any organization which will not be migrated would be “marked
for delete” in OPM.
• OPM Warehouses, which are already created as Inventory Organizations, can
remain at that level or be moved down to a Subinventory. The user needs to
choose which warehouses will become subinventories and the inventory
organization under which they fall.
• All re-mapping of organizations will be effective with transactions going
forward, and will have no impact on historical data.
5.11.2.1.2. Item Master
In the current OPM Inventory application, an item created in OPM is also inserted, via a
database trigger, into the Oracle Inventory item master. Additionally, item categories are
used to group OPM items, so there would be no migration issues with respect to item
categories.
Since most of the item and item category information resides in Discrete Inventory, the
migration of the item master consists of:
• Validating and synchronizing the item definition between Discrete and Process
• Validating the assignment of items into item categories
• Validating the assignment of items to organizations (both Process-Enabled and
Discrete organizations)
5.11.2.1.3. OPM Inventory
All of the OPM Inventory features will be migrated to their equivalent features in Oracle
Inventory. Here is a list:
• Inventory Balances
• Lots & Sublots
• Lot Allocation parameters
• Lot/Sublot Conversions
• Inventory Journals
• Inventory Creates, Adjustments, Movements, Status & Grade changes
• Lot Status Codes
• Period Balances
• Inventory Calendar
• Lot Genealogy
5.11.2.1.4. Physical Inventory/Cycle Counting
ABC Codes and related setup will be migrated, and the physical inventory transactions
are part of the completed transaction table which will not be migrated.
5.11.2.1.5. OPM Product Development
Product Development will not be migrated, but needs to be compatible with the new
definitions for organizations, items, and user-organization security. Objects affected are:
• Formulas
• Recipes
• Routings
• Operations
• Technical Data
• Simulation and Analysis Tools
5.11.2.1.6. Regulatory Management
Regulatory items will be migrated to the item master, and regulatory item properties will
also be migrated. Regulatory formulas will be migrated to the Formula tables in GMD.
5.11.2.1.7. Process Execution
Open batches in Process Execution will be migrated. This migration will occur by
closing the existing batch and recreating as a last step of migration with updated
inventory transactions. The old batch will no longer be updateable.
5.11.2.1.8. Quality Management
Most of Quality Management will not be migrated, although many updates will be made
within the data model to ensure compatibility with items, organizations, and inventory
transactions.
However, the following entities within QM will be migrated:
• Grades
• Actions
• Hold Reason Codes
5.11.2.1.9. Purchasing
Minimal changes are expected here for OPM customers using Oracle Purchasing. Lot
numbers will be updated to reflect the migration to the new Lot tables.
5.11.2.1.10. Planning
A few setup tables will need to be updated to deal with the new item master and
organizations tables, however Planning is already integrated to ASCP so no migration is
necessary.
5.11.2.1.11. Costing
Several tables within OPM Costing will be migrated to the new Subledger Architecture
(SLA). These include: Account Mappings, Event Codes, Sub Events and the Subsidiary
Ledger. However, other entities will remain in OPM Costing and will require a data
transformation to reflect the changes to items and organizations.
5.11.2.1.12. Manufacturing Accounting Controller
Manufacturing Accounting Controller will be replaced by SLA.
5.11.2.2. OPM System Administration

Many of the OPM System Administration functions will become obsolete as equivalent
functions already exist elsewhere in Oracle Applications. Aside from Organizations
which is discussed earlier in the document, the features that will be migrated are:
• Reason Codes and Reason Code Security (to Inventory Reasons)
• User Organizations (to Organization Access)
• Geography Codes (to Territory and AR Locations)
• Addresses (to HR Locations)
Support will be continued within OPM System Administration for the following
functions:
• Document Types and Document Ordering – most of these will become obsolete
except for those documents used by Process Execution and Quality Management
• Paragraphs
• Text Tokens
• Purge and Archive
• Workflow Setups
5.12. Oracle Process Manufacturing Logistics

5.12.1. Overview
Oracle Process Manufacturing Logistics is an extension of Oracle Order Management
and Oracle Purchasing that supports the needs of process manufacturers in the customer
fulfillment and procurement applications. Unique requirements for food and beverage,
pharmaceutical, chemical and other process manufacturers include:
• The ability to order, price, ship and receive in two units of measure
• Allocating inventory based on customer specifications and preferences
• Capturing additional acquisition costs, such as freight and special charges, as part
of your purchased material
• Optionally capturing electronic signatures and records
Process Logistics integrates with the Process Execution (manufacturing) and Process
Costing applications, along with the rest of the e-Business Suite, to provide a complete
solution for customer service and procurement.
The Process Inventory and Oracle Inventory applications are now a single application for
managing inventory across the entire Oracle e-Business Suite. Process features have
been added to Oracle Inventory to support Process characteristics, such as dual units of
measure, grade, child lots as a subdivision of lot-controlled inventory, and the use of
material status.
As a result, the integration between Process Inventory and Oracle Order Management has
been removed and the single inventory application, Oracle Inventory, is the one source of
all material management information. Key areas that have been enhanced for Order
Management include improved allocation (picking) rules and added features to Move
Orders. Additionally, the ability to price by a secondary quantity is available to all users
who track their inventory in two quantities. Process users can leverage all of the
functionality in Order Management, such as enhanced scheduling and reservations, and
international drop shipments, as well as Warehouse Management System functions.
5.12.2. Features
5.12.2.1. Converged Inventory Modifications to Order Management

Since Order Management and Shipping Execution integrated to Process Inventory for
inventory organizations that were flagged as “process-enabled”, this integration is
removed and replaced with similar logic now included in Oracle Inventory. Specifically,
the following areas are modified:
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Process Manufacturing Logistics 68
• Item entry and order quantity validation – All items are validated against the central
item master in Oracle Inventory. Items can now be defined as “dual unit of measure
controlled” and the logic to determine a required secondary quantity are based on the
settings in the Oracle Inventory item master. Similarly, lot control, grade control and
status control are established here and the corresponding settings are used throughout
Order Management and Shipping Execution.
• Reservations – Process Manufacturing users can leverage all reservation functionality
available to Order Management users. This includes fair share and percentage
reservations, reserving material at a detailed or high level, and enhanced reservations.
Enhanced reservations is a new feature for this release that enables the user match
any demand to any supply. Thus, a sales order can be reserved against a purchase
order or Process Execution batch. The reservation is then converted into an
allocation when the purchase order is received or the batch is completed.
• Pricing – An item can be tracked in two units of measure and priced in either unit.
The new column in the item master for Pricing determines the quantity on which the
price will be based. For items that are tracked in two quantities, the price can be
computed on either the primary or secondary order and shipped quantities. When
inventory is tracked in only one unit, but priced in a secondary unit, then the price is
computed when the shipped quantity is entered through the mobile transactions. This
feature of pricing by secondary quantity, without tracking the inventory in that
quantity, is known as catch weight pricing and is only available when Warehouse
Management is implemented with Order Management.
• Picking – All picking logic and picking rules are maintained through Oracle
Inventory. Picking rules in Oracle Inventory are enhanced to incorporate
functionality from Process Inventory (see the RCD for Process Inventory).
Additionally, the Oracle Warehouse Management application has a picking engine
that can be set up for more sophisticated picking logic. For both types of rules,
Process Manufacturing users can select to match on customer specifications
maintained in Process Quality. Move orders in Oracle Inventory facilitate the
movement of material to the staging location for shipping.
• Shipping – For items tracked in two units, the shipped quantities are maintained for
both units. License Plate Numbers and the packing functionality support the process
features of dual quantities, lot-controlled material and indivisible lots. When a lot is
indivisible, it will not be split between containers.
• Material status and grade – Material status and grade have been migrated to Oracle
Inventory. Status is used when determining if inventory can be picked or shipped.
The preferred grade from the sales order line can be used to pick the correct
inventory.
5.12.2.2. Move Orders enhanced to display Available Inventory

Move orders in Oracle Inventory are a request to move inventory within a facility. As
part of the movement, inventory is allocated to the move order request. In Process
Inventory, the move order allowed you to view available inventory and modify the
allocation. In Oracle Inventory, prior to this release, a view of available inventory did not
exist.
The new view shows inventory available in the inventory organization, based on onhand
balances, reserved and allocated inventory, quality grade, lot expiration dates and
material status. The view is accessed through the View/Update Allocations window from
Move Orders.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Process Manufacturing Logistics 69
5.12.2.3. Automatic creation of a batch for a sales order line
In a make-to-order environment, users do not satisfy demand through on-hand inventory,
but must schedule production to fulfill a customer order. A Process Manufacturing
production batch can be created from a sales order based on rules you establish for the
item and/or customer. A batch is automatically created using information from the sales
order line and recipes you maintain in Process Product Development. Once the batch is
created, it is reserved for the sales order and is allocated to the order or delivery when the
batch is completed.
• Oracle Order Management
• Oracle Shipping Execution
No update in R12. Terminology
Term Definition
Warehouse Management The Oracle Warehouse Management System (WMS) is a

System (WMS) component of Oracle’s Supply Chain Management and
Manufacturing solution. It spans the areas of warehouse
resource management, warehouse configuration, task
management, advanced pick methodologies, and value added
services.
License Plate Numbers The license plate number is a unique identifier of a container
(LPN’s) in the Supply Chain. The contents of the container are
tracked by this identifier. LPN’s are used to store and transact
inventory throughout the supply chain. The license plate may
represent a pallet, truck, or storage location. There may be
several items and lots in a LPN.
5.13. Oracle Purchasing Integration

5.13.1. Overview
As a result of the inventory convergence project, the integration between Process
Inventory and Oracle Purchasing has been removed and the single inventory application,
Oracle Inventory, is the one source of all material management information. Key areas
that have been enhanced for Purchasing include integration to Process Quality for
receiving inspection. Process users can leverage all of the functionality in Purchasing,
such as consigned and vendor managed inventory, enhanced drop shipments, and global
procurement/shared services, as well as Warehouse Management System functions.
5.13.2. Features
5.13.2.1. Converged Inventory Modifications to Purchasing

Since Purchasing and Receiving integrated to Process Inventory for inventory
organizations that were flagged as “process-enabled”, this integration is removed and
replaced with similar logic now included in Oracle Inventory. Specifically, the following
areas are modified:
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing Integration 70
• Item entry and order quantity validation – All items are validated against the central
item master in Oracle Inventory. Items can now be defined as “dual unit of measure
controlled” and the logic to determine a required secondary quantity are based on the
settings in the Oracle Inventory item master. Similarly, lot control, grade control and
status control are established here and the corresponding settings are used throughout
Purchasing and Receiving.
• Pricing and Acquisition Costs – Purchasing users can establish price lists and
acquisition costs through the Advanced Pricing application. The ability to set up
supplier price lists was introduced in 11i.10 and the functionality for acquisition costs
is new to R12 (see the RCD for Oracle Purchasing for additional detail). Process
manufacturers can take advantage of the full pricing functionality offered by Oracle
Purchasing for both price lists and acquisition costs. The set up of acquisition costs
includes designating Process Costing attributes for cost component class and analysis
code. Acquisition costs are applied to a receipt using discounts and surcharges
established in Advanced Pricing, or through freight cost integration through Oracle
Transportation. Process Manufacturers can implement Advanced Pricing and/or
Oracle Transportation to automatically compute the acquisition costs for a receipt.
• Vendor-Managed and Consigned Inventory – Process manufacturers can designate
items as vendor-managed or consigned inventory through the Approved Supplier
List. This allows suppliers to initiate replenishment through the iSupplier Portal for
inventory that they manage. For consigned inventory, a bill-only purchase order is
created for consumed inventory, while the original purchase order is used only for
receipt of the material.
• Receiving – For items tracked in two units, the received quantities are maintained for
both units. When receiving is used with Warehouse Management, then putaway
rules, License Plate Numbers and mobile transactions can be implemented.
• Material status and grade – Material status and grade have been migrated to Oracle
Inventory. Status and grade are assigned during receipt – grade can be assigned to
each lot, while status is taken from either the shipping organization or the item master
(the default status). The preferred grade from the purchase order line is used for
information only and can be communicated to the supplier.
5.13.2.2. Enhanced Receiving Inspection

When a receipt containing Process items is routed for inspection, OPM Quality
requirements can be enforced before the goods can be delivered to inventory. This
inspection point allows a visual inspection by the receiving clerk in Oracle Quality as
well as a more detailed sample analysis by a lab technician in OPM Quality. Upon
receipt, a workflow notification is sent to take a sample based on a supplier specification
validity rule defined in OPM Quality. This enhanced solution leverages the Oracle
Quality skip receipt inspection rules, while enforcing a mandatory collection plan.
Through this interface, the receiving clerk can see status updates and the acceptability of
the sample analysis. Based on the outcome of inspection, the user updates the accepted
and rejected quantities of the receipt in the collection plan, which in turn updates Oracle
Purchasing. After inspection, the appropriate quantities can be inventoried or returned to
the supplier.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Purchasing Integration 71
5.14. Oracle E-Records
5.14.1. Overview
The Oracle E-Business Suite 11i provides a complete set of tools for managing electronic
records, in accordance with the technical requirements in 21 CFR Part 11, including
strong security, audit trails, archiving, operational system checks built into GxP-critical
business flows and electronic signatures.
Oracle® E-Records is a configurable framework for securely capturing, storing, inquiring
and printing electronic records and electronic signatures (ERES) in compliance with
government regulations, such as the United States Food and Drug Administration’s 21
CFR Part 11. Oracle E-Records is part of the Oracle E-Business Suite, an integrated set
of applications that are engineered to work together.
5.14.2. Features
5.14.2.1. Enable Electronic Recordkeeping for SSWA Applications

In prior releases, Oracle E-Records was able to work with Forms-based applications in
the Oracle E-Business Suite. Now, Self Service Web Applications (a.k.a. SSWA or
Oracle Applications Framework) can be able to leverage electronic records and
signatures functionality, as well. This extends the breadth of applications in which you
can leverage electronic recordkeeping.
5.14.2.2. Electronic Recordkeeping for Mobile Transaction Framework

Enhancements have been incorporated into Oracle E-Records and the Mobile Web
Applications (MWA) Server to support 21 CFR Part 11-compliant electronic
recordkeeping with electronic signatures on mobile devices.
To support mobile users, a streamlined signing process has been enabled to support the
needs to mobile users and to fit on the smaller mobile displays. The enablement of the
individual mobile transactions to leverage this feature will be phased in during
subsequent releases.
• Workflow
 Business Event System
 Notification System
• Business Event System
• Oracle Approvals Management
• XML Gateway
• XML Publisher
5.14.4. Terminology
Term Definition
ERES Electronic Records and Signatures
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle E-Records 72
6. New and Changed Features in Manufacturing Operations
Center
6.1. Oracle Manufacturing Operations Center –

6.1.1. Overview
Oracle Manufacturing Operations Center (MOC) is a solution built on next generation
Manufacturing Operations architecture, leveraging the ISA-95 reference model. The
solution integrates and provides a common ground between the periodic and transactional
world of Enterprise Resource Planning (ERP) and the real-time, fragmented world of
shop floor manufacturing equipment and systems. This combination of real-time data
matched with the ERP-based business context enables Oracle Manufacturing Operations
Center to deliver increased visibility, sophisticated operational analytics, and
standardized and simplified integration between the enterprise and Shop Floor.
Oracle Manufacturing Operations Center connects to the existing infrastructure on the
plant floor, gathers raw data and builds business context around it by leveraging
information available in ERP and Manufacturing Execution Systems (MES) applications
◌۬ and converts it into useful information for business users. The solution not only enables
Plant Managers and their staff to monitor production operations in real-time, but also
builds a foundation for running Continuous Improvement (CI) programs such as Lean
and Six Sigma.
Oracle Manufacturing Operations Center combines the advantages of a prebuilt solution
with those of highly flexible extensibility in three important areas:
• An industry standard data model based, combined with a strong extensibility
framework.
• Prebuilt integrations, both down to the shop floor and up to the ERP, with
capabilities for extension and modification.
• Prebuilt Key Performance Indicators (KPIs) and analytics, delivered in Oracle’s
industry leading Business Intelligence (BI) technology enabling rapid extension
and configuration.
6.1.2. Release 12.1.1
6.1.2.1. Open, Flexible Data Model

The core component of Oracle Manufacturing Operations Center is a generic data model
that is open and extensible to meet the requirements of different industries. The data
model is loosely based on ISA-95 reference model and provides a good hierarchical
structure for reporting or building KPIs and metrics that can be analyzed along different
dimensions. The Data model is generic enough to support different modes of
manufacturing such as Discrete, Flow Manufacturing and Process Industries.
6.1.2.2. Customer Specific Process Parameter Monitoring Support

The data model also leverages Extensible Attributes Framework, a component leveraged
across other Oracle products such as Oracle PIM Data Hub that makes it open and
flexible to capture additional parameters with respect to entities such as Product,
Equipment and Work Orders. The BI metadata is enhanced to build custom reports for
the process parameters that are captured for equipment entity like monitoring the
pressure, temperature, etc. against the specifications setup.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Manufacturing Operations Center – 73
6.1.2.3. ERP Data Adaptor
Oracle Manufacturing Operations Center utilizes Oracle Warehouse Builder (OWB) to
deliver data integration mappings for extracting data from Oracle EBS. In this release, the
mappings cover Organizations, Shifts, Items, Item Category, Item Costs, Resource,
Resource Group, Resource Cost, released work orders/ flow schedules, Operations,
Material Requirements, and Resource Requirements from Discrete Manufacturing.
6.1.2.4. Hierarchical Dimensions

The analytical data model in Oracle Manufacturing Operations Center is built around
three key dimensions—Time (Calendar), Product, and Equipment. For each dimension,
there are seeded hierarchies provided out of the box. In addition, customers can build
their own hierarchies that are flexible and multi-level. Multiple hierarchies can co-exist in
the system.
6.1.2.5. Data Integration with Other Transactional Systems

Oracle Manufacturing Operations Center utilizes metadata-driven Oracle Warehouse
Builder to deliver ETL mappings for extracting data from other transaction systems such
as Manufacturing Execution Systems (MES), Quality or Maintenance Systems. The data
goes through the common staging and loading infrastructure whether it comes from
Oracle E-Business Suite (EBS) or other transactional systems.
6.1.2.6. Device Connectivity

Oracle Manufacturing Operations Center provides wide range of options for collecting
shop floor data, directly from Programmable Logic Controllers (PLCs), Supervisory
Control and Data Acquisition (SCADA) systems, and Distributed Control Systems
(DCSs). For example,
• Leverage partner solutions from Kepware Technologies, Matrikon and ILS
technologies to collect, aggregate and feed real-time sensor data into Oracle
Manufacturing Operations Center from OPC (Open Connectivity) servers. These
partner solutions would be enhanced by the vendors and certified to work with
Oracle Manufacturing Operations Center.
• Leverage existing connectivity options on the shop floor to feed equipment data
directly into Oracle Manufacturing Operations Center by leveraging the interface
table.
• Leverage Oracle Fusion Middleware components such as Enterprise Service Bus
(ESB) and BPEL and Oracle Warehouse Builder (OWB) tool to extract data and
process into Oracle Manufacturing Operations Center.
6.1.2.7. Device Data Management and Contextualization

One of the core strengths of Oracle Manufacturing Operations Center is the ability to
convert highly granular tag data from devices into meaningful business data for reporting
to business users such as Plant Managers and VP of Operations. Oracle Manufacturing
Operations Center has a Contextualization engine and functionality to define business
meanings and processing rules for various types of tag data.
6.1.2.8. Time Zone Conversion

MOC provides Oracle Warehouse Builder APIs to convert data in different time zone
into common time zone when they are loaded into MOC. By this way users can have the
MOC installed locally or centrally and can bring the data from corporate systems and
local systems without much problem on the time-zone conversion using this API.
6.1.2.9. Error Handling
Oracle Manufacturing Operations Center provides the infrastructure to capture and
process errors at every stage of data collection. Oracle Warehouse Builder allows
customers to define custom business rules to filter the data in Oracle Manufacturing
Operations Center.
6.1.2.10. Role-based Dashboards

The primary objective of Oracle Manufacturing Operations Center is to bring together
data from disparate sources into a single role-based dashboard allowing Plant Managers
and their staff to view manufacturing operations efficiently and effectively. Oracle
Manufacturing Operations Center leverages Oracle’s state-of-the-art BI platform from
Oracle Fusion Middleware to deliver dashboards that are easy to use and easy to
personalize. The open and flexible BI technology from Oracle Fusion Middleware also
makes it easier for users to build new KPIs and dashboards or modify existing ones. The
following are the dashboard pages and reports made available for Plant Managers:
Dashboard Pages Reports
Asset Performance (OEE) Overall Equipment Effectiveness by Plant
Overall Equipment Effectiveness Bottom Performers (by
Department)
Overall Equipment Effectiveness by Plant
Overall Equipment Effectiveness by Department
Overall Equipment Effectiveness Trend by Plant
Overall Equipment Effectiveness Trend by Department
Asset Performance (OEE) Overall Equipment Effectiveness by Department
by Equipment Overall Equipment Effectiveness Bottom Performers (by
Equipment)
Overall Equipment Effectiveness by Department
Overall Equipment Effectiveness by Equipment
Overall Equipment Effectiveness Trend by Department
Overall Equipment Effectiveness Trend by Equipment
Equipment Downtime Equipment Downtime Analysis
Analysis Equipment Availability Ratio Trend
Equipment Downtime Downtime Reasons
Reasons
Production Slippage Trend Production Slippage Trend
Production Loss Analysis Production Loss Distribution

OEE time Analysis
Production Loss Analysis
Production Loss Detail Production Loss Detail
Equipment Efficiency Equipment Efficiency Analysis
Analysis Equipment Performance Ratio Trend
Equipment Efficiency Equipment Efficiency Detail
Detail
Equipment Scrap Analysis Equipment Scrap Analysis
First Pass Yield Trend
Equipment Scrap Reasons Equipment Scrap Reasons
Batch Performance Production Variance by Product Category

Production Variance by Product
PPM Trend (Month to Date)
Batch Cycle Time Trend (Month to Date)
Service Level Performance by Product Category
Service Level Performance by Product
Batch Performance Detail Batch Performance Detail
Production Performance Performance to Schedule by Plant
Performance to Schedule by Department
Performance to Schedule by Equipment
Production Slippage by Equipment
Current Month Production Slippage Trend by Department
Current Month Production Slippage Trend by Equipment
6.1.2.11. Manufacturing Operations Center Catalog - KPIs and Metrics

Oracle Manufacturing Operations Center helps deliver operational intelligence in a
number of performance areas related to manufacturing operations based on the rich
analytics layer provided by BI technology. Oracle Manufacturing Operations Center
delivers key performance indicators (KPIs) in the following performance areas:
6.1.2.11.1. Manufacturing Asset Performance or Production Loss Analysis
Oracle Manufacturing Operations Center delivers a complete analytics framework for
VPs of Operations and Plant Managers to assess the performance of their
manufacturing assets. Overall Equipment Effectiveness (OEE) is a popular
framework for analyzing various reasons for loss of production capacity such as
• Downtime losses due to planned or unplanned downtime
• Uptime losses due to reasons such as “Operator on break”, “Waiting for
material” or “Set up time”.
• Efficiency losses
• Quality Losses
Oracle Manufacturing Operations Center provides a complete framework to capture
OEE at equipment level and roll it up all the way to the plant and enterprise.
6.1.2.11.2. Schedule Adherence
Schedule Adherence refers to a set of KPIs that help users understand the
performance of manufacturing operations against a production schedule that may
originate in an Oracle ERP system or in an external third-party system including
spreadsheets.
6.1.2.11.3. Batch Analyzer
Batch Analyzer refers to a set of KPIs that help understand the perfect manufacturing
order performance or performance of a specific work order or batch against its
defined objectives.
6.1.2.11.4. SPC/SQC
Oracle Manufacturing Operations Center supports an extensible attribute framework
to capture machine or line specific parameters. Machine parameters can also be
charted on SPC charts along with their control limits. Oracle Manufacturing
Operations Center supports most of the standard SPC/SQC charts.
6.1.2.11.5. Plant Maintenance
Complementary to the Manufacturing Asset Performance KPIs, the Plant
Maintenance KPIs help users understand the reasons for unplanned downtime and the
effects of lost production capacity due to unplanned downtime.
6.1.2.11.6. Quality
Quality KPIs help users understand and pin point locations of and reasons for scrap
and defects inside a plant.
6.1.2.11.7. Cost
Oracle Manufacturing Operations Center supports some cost-specific KPIs but
mostly depends on ERP systems or corporate data warehouses to deliver this
information.
6.1.2.11.8. Manufacturing Service Levels
Manufacturing Service Level KPIs measure performance against order ship dates.
6.1.3. Release 12.1.2
6.1.3.1. Certification with Oracle E-Business Suite Release 12.0.6

With this release, Oracle Manufacturing Operations Center is now certified to work with
Release R12.0.6 of E-Business Suite, Discrete and Process Manufacturing for collections.
Please note that MOC is a standalone edge product and requires the latest release of EBS
foundation on top of which the MOC patch gets applied. However, the EBS source
instance where either Discrete or Process Manufacturing is running can be on older
releases. The integration between MOC and EBS, which was earlier certified to work
with Release 11.5.10 of the source EBS instance, is now also certified for R 12.0.
6.1.3.2. Event Management Framework

Event Management Framework is a new feature in release 12.1.2 of MOC that reduces
reaction time between event happening in shop floor and response for the same event,
either automatically or manually initiated. Key capabilities that Event Management
Framework adds to MOC are as follows:
• Setup and configuration of event conditions, based on KPI thresholds or real-time
data from shop floor
• Handling actions based on both internal and external events in MOC, such as
sending mobile alerts, e-mails, or calling an external API to initiate a process
such as creating maintenance work request.
• Persistent storage of events for review and reporting
6.1.3.2.1. Event Setup and Configuration
Users can define different types of events based on event conditions such as
equipment down, control limit warning etc. Defined events can then be linked to
event actions such as “Creation of a Work Request in Oracle EAM” or general
notifications using mobile alerts or e-mail to production supervisor or maintenance
personnel.
6.1.3.2.2. Support for Externally Generated Events
Events can also be generated outside of MOC and imported into MOC for persistent
storage and action handling. For example, any alarm or fault occurring on equipment
can be brought into MOC for, notifications or other action, storage and analysis
purposes.
6.1.3.2.3. Actions on Internal/External Events
MOC provides a common action-handling framework that can process both internal
and external events. Internal events are generated based on raw data coming from
shop floor via an OPC server (provided by Oracle partners such as Kepware,
Matrikon or ILS). In addition to seeded actions such as “Creation of Work request in
EAM”, MOC would also support BPEL allowing customers to build custom actions.
6.1.3.2.4. Visibility to Events on Dashboards
MOC analytics repository has been enhanced to provide users capability to design
their own reports and dashboard based on the event history.
6.1.3.3. EBS Adapter for Process Manufacturing

In this release, Oracle MOC can collect data from Oracle 11.5.10 E-Business suite for
Process Manufacturing (OPM). The entities that can be collected from OPM are:
• OPM Items and Item Hierarchies
• OPM Resources along with Resource Hierarchies
• Process Batch and Material Produced
• Sales Orders pegged to Process Batches
This feature was previously released with Manufacturing Operations Center Release
12.1.1.01.
6.1.3.4. EBS Adapter Enhancement for Discrete Manufacturing

In this release, the EBS adapter is enhanced to collect data for following entities from
11i10 release of Oracle Discrete and Flow Manufacturing:
• Item Cost–this collects the latest item cost to add monetary value to material
production.
• Resource Cost–this collects the latest resource cost to add monetary value to
resource usage.
• Sales Orders pegged to Work Orders and Flow Schedules
12.1.1.01.
6.1.3.5. Production Quality Monitoring

A new extensible attribute entity Batch Operations is added to collect and maintain
production quality information from external data sources like LIMS and other quality
systems. This entity will help to analyze the samples results against the specifications.
This is a data model enhancement, so customers need to customize by building adapters
to the quality systems and modify the OBIEE repository to enable reporting.
12.1.1.01.
6.1.3.6. Item Category Enhancement

Oracle MOC now collects Item Category segments from EBS along with the categories
to provide additional attributes for analyzing the data.
12.1.1.01.
6.1.3.7. Production Performance Reporting
Oracle MOC now enables users to track the operation cycle time and its break up of Run,
Idle and Down Time contributions. These metrics are calculated based on the equipment
status and output it produces during the period. The following are the metrics that are
added for production performance monitoring:
• Cycle Time (Hours)
• Average Cycle Time (Hours)
• Run Time during Cycle (Hours)
• Idle Time during Cycle (Hours)
• Down Time during Cycle (Hours)
12.1.1.01.
6.1.4. Release 12.2.1
6.1.4.1. ODI based Data Integration Platform

With Release 12.2.1, Oracle Manufacturing Operations Center supports new technical
stack for data integration that is Oracle Data Integrator (ODI). The OWB Maps and
Process flows of R12.1.3 are either converted into equivalent ODI scenarios or
concurrent programs.
There is an improved Data Integration with Oracle EBS, Flat files and Device Tags
• EBS Adapters for Releases 12.2.1, 12.1.3 and 12.0.6
• All Manufacturing Methods- Discrete, Process, Flow, Repetitive
• Items and Item Hierarchies
• Resource and Resource Hierarchies
• Work Orders, Batches and Material Produced
• Sales Orders pegged to Work Orders/Process Batches
• Flat file based data collection with over 40 templates
• Data collection from Tags
6.1.4.2. Recalculation
The earlier version of MOC didn’t allowed users to correct or update any past status or
output data. The new Recalculation feature enables recalculation of the past data for
specific equipment or all equipment in a plant.
The users can perform recalculation for Equipment Output, Equipment Status or both
Equipment Output and Status.
The procedure involves uploading new Status or Output Flat file to File Location and
running ODI Scenario for Re-processing. Once the scenario completes, users can query
the Status or Output tables, Summary table and, Tag Reason Readings tables to review
the updates.
6.1.4.3. Error Reprocessing
This feature provides the capability to correct the errors encountered during loading of
data through Flat Files or collected from source systems (such as Oracle E-Business
Suite) using a simple WebADI based template. End users responsible for data upload do
not require database access to correct the wrongly entered data.
The users can download the WebADI template by clicking on ‘Reprocess Error Records’
link in the ‘Manufacturing Operations Center Administrator’ responsibility. After
downloading the template for a particular error table, the users can correct the data,
resubmit the records and run the ODI Package corresponding to the entity.
6.1.4.4. Asset Performance Dashboard

A new role-based dashboard for Plant Managers and Maintenance Managers that
provides insight on 360o view of equipment performance of production and non
production assets in a manufacturing plant or a maintenance facility.
Dashboard Page Reports

Production Assets Page Events, Asset Detail Status Trend, Asset
Downtime Analysis, Asset Production
Performance, Asset Output and Scrap and
Asset Operational Parameters for
Production Assets
Non Production Assets Page Events, Asset Detail Status Trend, Asset
Downtime Analysis, Asset Operational
Parameters for Non-Production Assets
6.1.4.5. Production Supervisor Dashboard

A new role-based dashboard for production supervisors to enable real-time tracking of
equipment output, status and exceptions for all equipment in the plant. Following Reports
are available in this dashboard:
• Alert for High Scrap
• Equipment Status- Latest Equipment Status, Time of Last Status Change
and Time Since Last Status Update
• Equipment Production Performance- Actual Production with respect to
Scheduled Production. Catch up Rate indicates the production rate to meet
scheduled production target
• Equipment Status Analysis- The breakup of Down, Idle and Run time
hours for equipment within a plant
• Equipment Status Trend- Displays Equipment Run, Idle and Down trend
for all reading times for time period selected
• Equipment Output Trend- Displays trend of Completed, Scrap quantity for
an equipment for all reading times for time period selected
• Equipment Downtime Analysis-Breakup of downtime reasons for all
reading times for time period selected
6.1.4.6. Support for Oracle Business Intelligence Mobile

Oracle Business Intelligence Mobile (BI Mobile) is an application that allows users to
view Oracle BI EE content on supported mobile devices such as the Apple iPhone and
Apple iPad. Users can view and analyze BI content such as analyses , dashboards, BI
Publisher content, scorecard etc.
This application can be downloaded from Apple iTunes App Store. This feature is
available only in Oracle Business Intelligence Enterprise Edition 11 g Release 1 (11.1.1)
onwards.
MOC’s dashboards such as Plant Manager, Facility Manager can be viewed on Apple
iPad and Apple iPhone by using Oracle BI Mobile.
6.1.5. Release 12.2.3
6.1.5.1. Enhanced Inbound Integration with Oracle EBS

With this release the new entities collected from Oracle EBS are:
• Resource instances as Equipment within MOC
• Work Order/Process Manufacturing batches reference data
• Operations
• Activities
• Resource requirements
• Resource instance schedules/ Equipment production schedules
• Material consumed
6.1.5.2. Outbound Integration with Oracle EBS-Discrete Manufacturing

Out-of-box outbound integration provided by MOC creates the following discrete job
transactions:
• Move transaction
• Completion Transaction
• Resource Transaction
Move Transactions
• MOC tags for Completed, Scrap, Rejected Quantities create corresponding move
transactions in Oracle WIP
• The Move Transaction from ‘To Move’ of current operation to the ‘Queue’ of
next operation should be manually done by users in EBS
Completion Transactions
• The various operations supported for Completion Transaction in Oracle WIP
using Output Quantity, Scrap and Rejected quantity tag are: To Move ,
Completion Transaction
• Completion Transaction can only be done for last segment of Job
Resource Transactions
• The Status tags from shop floor get processed as resource transactions in MOC
and create resource transactions in Oracle EBS. The transaction posted is for run
hours of the resource.
6.1.6. Outbound Integration with Oracle EBS-Process Manufacturing

Out-of-box outbound integration provided by MOC creates the following OPM batch
transactions:
• Material transactions are created for the product in OPM batch
• Resource transactions are created for the batch step activities
6.1.7. Release 12.2.4
Before this release, MOC maintained only the equipment status and equipment output
summary information. This summary is held at the level of Item, Workorder, Workday
Shift and Hour. With this release, a new equipment summary table is created to store
summarized information of extensible attributes.
Users can setup mathematical functions for an extensible attribute using a new page.
These attributes get summarized on an hourly basis by the ‘MTH: Process Transactions’
concurrent program and the summarized data is maintained in a new equipment extensible
attribute summary table The new table and columns are made available in the OBIEE
layer for reporting purpose.
6.1.8. Terminology
Term Definition
Contextualization The data stored in PLCs as tags is at a granular level and lacks
the required context. For tag or PLC data to be used for
transactions or business intelligence purposes, it needs to be
contextualized or converted into meaningful data
Control Charts Control charts are standard metrics prescribed by SPC/SQC to
monitor processes and determine if they are under control.
Each process parameter has defined upper and lower control
limits; the process is under control as long as the parameter
values are within these two control limits.
A data historian is like a video tape, in a closed circuit security
Data Historian system. The historian stores every event and every tag value as
it changes over time. Historians are more commonly used in
the process industries than Discrete. There are lots of packaged
historians out there, most popular being Pi from OSISOFT and
inTouch from Wonderware. Every automation vendor has a
data historian to offer such as iFix and iHistorian from GE
Fanuc and RSView32 from Rockwell.
Device This term is typically used for PLCs or any other type of
devices such as sensors, counters, and bar code readers that can
serve as means for collecting MOC data.
EMI Enterprise Manufacturing Intelligence or EMI is a term coined
by AMR Research to designate Manufacturing Intelligence
solutions that specifically focus on the plant floor and provide
details about performance of various types of equipments at the
plant floor. The term typically implies 3 things:
• Connection to the plant floor including lowest level plant
floor systems such as PLCs, SCADA and other types of control
systems,
• Monitoring plant performance in real time, and
• Providing a foundation for running continuous improvement
programs such as OEE< lean and six sigma.
Equipment One of the key models in S -95 and also a very commonly
Hierarchy referred one.
ISA -95 A standard for Enterprise to control system integration that
includes batch, continuous and discrete industries. Managed by
ISA (Instrumentation, Systems and Automation Society), ISA -
95 defines terminology, functional requirements, and borrows
or is based on PRM (Purdue Reference Model) for
manufacturing.
KPI Key Performance Indicators are quantifiable measurements
reflecting the critical success factors of an organization. They
differ depending on the organization.
Machine, Asset or The actual machine on which manufacturing activity is
Equipment performed. This document deals strictly with production
equipments only. Other types of assets such as conveyor belts,
carousels used in warehouses or other such material handling
equipments are in scope, as far as this solution is concerned.
Usually these are the lowest level entities in the equipment
hierarchy.
MES Manufacturing Execution System is used for a class of mid-
level systems that operate between ERP and the shop floor.
These systems typically belong to an enterprise class of
software, but provide a deeper view of the manufacturing
execution process on the shop floor.
MOC Manufacturing Operations Center (MOC)
ODI Oracle Data Integrator
ODI Agent An Agent is a run-time component of ODI that orchestrates the
integration process by sending commands to data servers, the
operating systems, or other technologies.
ODI CKM The CKM (Check Knowledge Module) is in charge of
checking that records of a data set are consistent with defined
constraints they can check either an existing table or the
temporary "I$" table created by an IKM.
CKM operates in both STATIC_CONTROL and
FLOW_CONTROL
In STATIC_CONTROL mode, the CKM reads the constraints

of the table and checks them against the data of the table.
Records that don’t match the constraints are written to the "E$"
error table in the staging area.
In FLOW_CONTROL mode, the CKM reads the constraints of

the target table of the Interface. It checks these constraints
against the data contained in the "I$" flow table of the staging
area. Records that violate these constraints are written to the
"E$" table of the staging area.
ODI Datastore In ODI the data is handled through tabular structures defined
as datastores.
ODI Interface An Interface is an ODI object that defines the rule to load one
target data store with the data from one or more source data
stores. A declarative design is used to implement the
transformations as mappings.
ODI Knowledge A knowledge module is a code template containing the
Module sequence OS commands necessary to carry out a data
integration task.
ODI Mapping A mapping is a business rule implemented as a SQL clause. It
is a transformation rule that maps columns in source data
stores onto one of the target data store columns. It is executed
by a relational database server at run time.
ODI Model A Model is a description of a relational data model. It is a
group of data stores stored in a given schema on a given
technology.
ODI Package A package is a predefined sequence of steps, designed to be
executed in order. They are many types of steps, such as:
Interfaces, Procedures, Actions/evaluations on variables,
Actions on models/sub-models/datastores, OS Commands,
ODI Tools
ODI Scenario A scenario is a partially generated code (SQL, shell, etc) for
the objects (interfaces, procedures, etc.) contained in a
package.
OEE The Overall Equipment Effectiveness measure is the basic
building block of a manufacturing improvement approach
called total productive manufacturing or TPM. Developed by
the Japanese in the 1960’s, TPM is a shop - floor focused
improvement program whose primary objective is to maximize
OEE. The 3 performance elements of OEE are clearly
influenced by numerous events —or losses as they are known.
For example, availability may be lost because of breakdowns,
material shortages, or operator absence. Each of these will
account for a proportion of the loss, and each can be measured
in percentage terms. By understanding both the types of loss
and their duration, operators can focus their improvement
activities on areas that will give the greatest benefits.
OPC OLE for Process Control (OPC) is a set of standard interfaces
based upon Microsoft's OLE/COM technology. The
application of the OPC standard interface makes possible
interoperability between automation/control applications, field
systems/devices, and so forth.
PLC A type of industrial controller. Originally, industrial
automation was implemented with discrete relays and timers,
which were connected together with copper wire. Using this
type of automation structure had a serious disadvantage: to
change the function (or logic) of the control system, the system
had to be literally rewired. Rewiring is time -consuming and
expensive. PLCs were invented to replace these banks of relays
in semi automated factories, notably automobile plants in the
late 1960s. The programming method that most PLCs use is
called ladder logic. Scan rates are critical for a PLC, because
PLCs constantly read (scan) all points, process logic, and then
write to all points. Most PLCs run on a proprietary network.
SCADA (SCADA) Supervisory Control and Data Acquisition. A
computer system for gathering and analyzing real time data.
SCADA systems are used to monitor and control a plant or
equipment in industries such as telecommunications, water and
waste control, energy, oil and gas refining, and transportation.
For example: A SCADA system gathers information such as
where a leak on a pipeline has occurred, transfers the
information back to a central site, alerts the home station about
the leak, performs necessary analysis and control, , and
displays the information in a logical and organized fashion.
SCA DA systems can be relatively simple, such as one that
monitors environmental conditions of a small office building,
or incredibly complex such as a system that monitors all the
activity in a nuclear power plant or the activity of a municipal
water system.
Sensor A device that responds to a physical stimulus (heat, light,
sound, pressure, motion, flow, and so on), and produces a
measurable corresponding electrical signal known as
transducer.
SPC/SQC A quality and process control methodology that relies on
control charts to determine if a particular process is under
control. There are standard control charts prescribed by
SPC/SQC for different types of quality and process parameters.
Tag A term used to represent individual data elements on a PLC.
The tags are configurable and can be programmed using PLC
programming techniques
Transactional A term used for software applications typically meant for
System automating transactions. It can include ERP, MES, and custom
or legacy homegrown applications that operate on a relational
database.

EBS 122 Cum RCD MFG MOC

Uploaded by

Copyright:

Available Formats

EBS 122 Cum RCD MFG MOC

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EBS 122 Cum RCD MFG MOC

Uploaded by

Copyright:

Available Formats

E-BUSINESS SUITE

RELEASE CONTENT DOCUMENT

Prepared by EBS Product Management and Strategy Teams

Last Updated: December 19, 2014

Copyright © 2014 Oracle Corporation

2.1. Purpose of Document

3.1. Oracle In-Memory Cost Management for Discrete Manufacturing and

The products consist of three components:

3.1.2. Cost Impact Simulator (CIS)

4.1. Oracle Discrete Manufacturing

4.2. Oracle Discrete Manufacturing Extensions for Oracle Endeca

Real Time 360 Degree view of Discrete Work Orders

4.2.2.1. Project Manufacturing Endeca Page

Project Manufacturing Search and Overview Alerts and Summarized Metrics

4.3.2.1. Mobile Foundation Updates

4.3.2.2. Accessibility Improvements

4.3.2.4. Landscape Display Support Improvements

4.4. Oracle Cost Management

4.4.1.1. Iterative Periodic Average Costing (IPAC) for Brazil

4.4.2.1. Iterative Periodic Average Cost Processor

4.4.2.2. Global Accounting Engine Forward Port to Subledger Accounting

4.4.2.3. Support for Landed Cost Management

4.4.3.1. EMEA Joint Project - Inventory Master Book Report

4.4.3.2. SLA Post Down-time Upgrade as Concurrent Programs

4.4.4. Release 12.1.3

4.5. Oracle Cost Management Extensions for Oracle Endeca

Period Health Check

PAC Periodic Average Cost method. Items are costed in a costing

4.6.2. Release 12.1.1

4.6.2.1. Serialized Manufacturing

4.6.2.2. Shop Floor Device and Test Equipment Integration

4.6.2.4. Improved Supervisor Dashboard

4.6.2.5. Printing Shop Floor Documentation

4.6.2.6. Usability Enhancements

4.6.3. Release 12.1.2

4.6.3.1. Ability to Perform Manufacturing Execution without any Dependency on the

4.6.3.2. Support for Detailed Routing Step in MES

4.6.3.3. Ability to Interface with Oracle E-Business Suite Releases Prior to

4.6.3.5. Simplified UIs for Users

4.6.4.1. Enhanced Serialized Manufacturing

4.6.4.2. MES Operator Workstation Enhancements

4.6.4.3. MES UI Configurability Enhancements

4.6.4.4. MES Custom Extension User Exits / Hooks

4.6.5.1. Resource Level Clock In/Out

4.6.5.2. Mass Return Components of Serialized Assembly (Dekitting)

To improve productivity when disassembling an assembly serial and returning

• New Mass Return component in Global Actions Menu

4.6.5.3. 1.3Serialization APIs

Job Traveler Job Traveler or shop packet is a set of documents associated

4.6.7. Oracle Electronic Kanban - R12.2

4.6.7.1. Configurable and User-Friendly Graphical User Interface

When you update production

4.6.7.3. Logical Kanban Support

4.6.7.4. Extensive Search Capabilities

4.6.7.5. Configurable Supply Statuses for Kanban Cards

4.6.7.6. Enhanced Supplier Kanbans

4.6.7.7. Replenishment Order Consolidation

4.6.7.8. Temporary Kanban Cards

4.6.7.9. Notifications and Alerts