1158 To 11510

RELEASE CONTENT DOCUMENT
Oracle Applications
Generated by: RCD Search Tool

Generation Date:18-Nov-2005 3:18 AM
Copyright © 2005 Oracle Corporation

All Rights Reserved
1
Table of Contents
Disclaimer.................................................................................................................................................................15
1. Financial.............................................................................................................................................................16
1.1 Oracle Assets................................................................................................................................................16
1.1.1 Release 1158 Features...........................................................................................................................................16
1.1.1.1 Adjustments API.....................................................................................................................................................16
1.1.1.2 Retirements and Reinstatements API.....................................................................................................................16
1.1.1.3 Common Transaction API......................................................................................................................................16
1.1.1.4 Parallelized Mass Transactions...............................................................................................................................16
1.1.1.5 Depreciable Basis Formula.....................................................................................................................................16
1.1.1.6 Reclassifications API..............................................................................................................................................16
1.1.1.7 Unplanned Depreciation API..................................................................................................................................16
1.1.1.8 Manual Depreciation Override...............................................................................................................................16
1.1.1.9 Capitalizations API.................................................................................................................................................16
1.1.1.10 Mass Copy Continue Despite Errors....................................................................................................................16
1.1.1.11 Additions API.......................................................................................................................................................16
1.1.1.12 Asset Description API..........................................................................................................................................16
1.1.1.13 Transfers and Unit Adjustements API..................................................................................................................16
1.1.1.14 Enhanced Mass Retirements.................................................................................................................................16
1.1.1.15 View Currency Details..........................................................................................................................................16
1.1.1.16 Enhanced Mass Change and Mass Transfers........................................................................................................16
1.1.2.1 Enhanced Mass Transfers.......................................................................................................................................16
1.1.2.2 Enhanced MRC Processing....................................................................................................................................17
1.1.2.3 Enhanced Mass Revaluations.................................................................................................................................17
1.1.2.4 Source Line Retirement..........................................................................................................................................17
1.1.2.5 Override Depreciations in MRC-enabled Books....................................................................................................17
1.1.2.6 Japanese Depreciable Tax Report Enhancement....................................................................................................17
1.1.3 Release 11510 Features.........................................................................................................................................17
1.1.3.1 Group Asset Security .............................................................................................................................................17
1.1.3.2 Group Depreciation ................................................................................................................................................17
1.1.3.3 Polish Tax Depreciation..........................................................................................................................................17
1.1.3.4 Enhanced Depreciation Override............................................................................................................................17
1.1.3.5 Business Events......................................................................................................................................................17
1.1.3.6 Mass External Transfers.........................................................................................................................................17
1.1.3.7 Retirement Notification..........................................................................................................................................17
2
1.1.3.8 Support for CIP Assets in Groups...........................................................................................................................18
1.1.3.9 Mass Property.........................................................................................................................................................18
1.1.3.10 Asset Trace Utility................................................................................................................................................18
1.1.3.11 Enhanced Asset Inquiry........................................................................................................................................18
1.1.3.12 Enhanced 'What-If' Analysis in Multiple Reporting Currencies (MRC)..............................................................18
1.2 Oracle Cash Management.............................................................................................................................19

1.2.1.1 Reconciliation Open Interface Integration with Treasury......................................................................................19
1.2.1.2 Bank Statement Transmission................................................................................................................................19
1.2.1.3 Exchange Rates for Foreign Currency Bank Accounts..........................................................................................19
1.2.1.4 Intra-day Transaction Reporting.............................................................................................................................19
1.2.2.1 Archive and Purge of Bank Statement Open Interface...........................................................................................19
1.2.2.2 Intra-Day Bank Statement Transmission................................................................................................................19
1.2.2.3 XML Interface for Bank Statement........................................................................................................................19
1.2.3.1 Cash Positioning Enhancements.............................................................................................................................19
1.2.3.2 Batches Available for Reconciliation Report.........................................................................................................19
1.2.3.3 Reconciliation of Oracle Payroll EFT Payments....................................................................................................20
1.2.3.4 Bank Purging Program............................................................................................................................................20
1.2.3.5 Cash Forecasting By Transaction Currency ..........................................................................................................20
1.2.3.6 Cash Forecasting Temporary Labor and Fixed Price Services...............................................................................20
1.2.3.7 Cash Positioning ....................................................................................................................................................21
1.2.3.8 Cash Forecasting ....................................................................................................................................................21
1.3 Oracle General Ledger..................................................................................................................................23

1.3.1.1 Journal Import Warning Status for Data Errors......................................................................................................23
1.3.1.2 Translation Performance Enhancement..................................................................................................................23
1.3.1.3 Parallel Consolidation Performance Enhancement.................................................................................................23
1.3.1.4 Open Period/Posting/Transla Compatib Across Sets of Books..............................................................................23
1.3.1.5 Translation/Consolidation Compatibility...............................................................................................................23
1.3.1.6 Global Consolidation System Cross Instance Data Transfer..................................................................................23
1.3.2.1 Fiscal Year-End Amount Type in FSG Reports.....................................................................................................23
1.3.2.2 Streamlined Revaluation Process............................................................................................................................23
1.3.2.3 Budget Pgms, Translation, Posting Compat Acr Sets of Boo................................................................................23
1.3.2.4 Global Intercompany System (GIS) Reject of Interco Txns Op.............................................................................23
1.3.2.5 Translation of Income Stmt Accounts Using Period-End Rates.............................................................................23
3
1.3.2.6 MRC Journal Originator Tracking..........................................................................................................................23
1.3.2.7 Enh Global Consolid System Cross-Instance Data Txfr Securi.............................................................................23
1.3.2.8 Enhanced Account Hierarchy Manager Security....................................................................................................23
1.3.3.1 FSG Reports Name Display in Concurrent Manager.............................................................................................23
1.3.3.2 Open Period/Posting/Translation/Summary Accounts Program Compatibility Among Sets of Books.................23
1.3.3.3 Continue Step-Down Allocation Option.................................................................................................................24
1.3.3.4 GL Standard Reports Integration with XML Publisher (CU1)...............................................................................24
1.3.3.5 XBRL Financial Reporting ....................................................................................................................................24
1.3.3.6 Streamlined Core Oracle Financials Workbenches................................................................................................24
1.3.3.7 Secondary Tracking Segment.................................................................................................................................24
1.3.3.8 Presentation Quality FSG Reports Using XML Publisher.....................................................................................24
1.3.3.9 Journal Import SRS Program..................................................................................................................................25
1.3.3.10 Journal Import Group By Effective Dates............................................................................................................25
1.3.3.11 Interface Data Transformer...................................................................................................................................25
1.3.3.12 Multilingual Support For FSG Amount Types.....................................................................................................25
1.3.3.13 MRC Revaluation Against Primary Currency......................................................................................................25
1.3.3.14 Currency Rates Manager .....................................................................................................................................25
1.3.3.15 Open Integration with External Processing..........................................................................................................26
1.4 Oracle Payables.............................................................................................................................................27

1.4.1.1 Invoice Approval Workflow...................................................................................................................................27
1.4.1.2 View Currency Details............................................................................................................................................27
1.4.1.3 Payment Batch Scheduling.....................................................................................................................................27
1.4.1.4 Primary Pay Site.....................................................................................................................................................27
1.4.1.5 Profile Option Migration........................................................................................................................................27
1.4.1.6 MRC Technology Changes.....................................................................................................................................27
1.4.1.7 Payment Batch Enhancements................................................................................................................................27
1.4.1.8 Building Prepayment Accounts When Matching...................................................................................................27
1.4.1.9 Expense Report Import...........................................................................................................................................27
1.4.1.10 Invoice Approval Workflow Enhancement..........................................................................................................27
1.4.1.11 Folderized Payment Batch Sets............................................................................................................................27
1.4.1.12 Interest Expense Proration....................................................................................................................................27
1.4.1.13 Further Payment Batch Enhancements.................................................................................................................27
1.4.1.14 Enh Matching Controls for Finally Closed Purchase Orders...............................................................................27
1.4.1.15 Automatic Bank Transmission..............................................................................................................................27
1.4.1.16 Mass Additions Create Program...........................................................................................................................27
1.4.1.17 Enhanced Separate Remittance Advice................................................................................................................27
1.4.1.18 iSupplier Portal Invoices.......................................................................................................................................27
4
1.4.2.1 1099 Reporting 2002 Changes................................................................................................................................27
1.4.2.2 Enhanced Open Items Revaluation Report.............................................................................................................28
1.4.2.3 XML Payment Processing......................................................................................................................................28
1.4.2.4 Enhanced Bank Account Identification..................................................................................................................28
1.4.2.5 Price Correction Enhancements..............................................................................................................................28
1.4.2.6 Multiple Currency Reports.....................................................................................................................................28
1.4.2.7 Period Close Exceptions Report.............................................................................................................................28
1.4.2.8 XML Invoices.........................................................................................................................................................28
1.4.2.9 Enhanced Control of Prepayments with Automatic Offsets...................................................................................28
1.4.2.10 Accounting Events Enhancement.........................................................................................................................28
1.4.3.1 Gapless Invoice Numbering for Self-Billing Invoices ..........................................................................................28
1.4.3.2 Invoice Approval Workflow Resubmission Enhancement.....................................................................................28
1.4.3.3 Invoice Validation Concurrent Processing ............................................................................................................28
1.4.3.4 UI Enhancements....................................................................................................................................................28
1.4.3.5 Supplier Site Contact Enhancements......................................................................................................................29
1.4.3.6 Supplier Site Attachments......................................................................................................................................29
1.4.3.7 Supplier Open Interface..........................................................................................................................................29
1.4.3.8 Supplier Bank Account Update Enhancements......................................................................................................29
1.4.3.9 Retroactive Pricing of Purchase Orders Support....................................................................................................29
1.4.3.10 Invoice Attachments in Oracle iSupplier Portal...................................................................................................29
1.4.3.11 Exclude Tax from Discount Calculation Enhancement .......................................................................................29
1.4.3.12 Amount Based Matching......................................................................................................................................29
1.4.3.13 Bank Account Function Security Enhancements..................................................................................................30
1.4.3.14 Enhanced Purchase Order Number Display in Oracle iSupplier Portal...............................................................30
1.4.3.15 Enhanced Matching Controls for Oracle iSupplier Portal....................................................................................30
1.4.3.16 Payables Accounting Entries Program and Report Enhancements .....................................................................30
1.5 Oracle Receivables.......................................................................................................................................31

1.5.1.1 Bills Receivables Balance Assignments.................................................................................................................31
1.5.1.2 Display of Operating Unit Field.............................................................................................................................31
1.5.1.3 Require Adjustment Reason...................................................................................................................................31
1.5.1.4 Lockbox Invalid Match Reference.........................................................................................................................31
1.5.1.5 MRC Inquiry Window............................................................................................................................................31
1.5.1.6 Deposit Enhancements............................................................................................................................................31
1.5.1.7 Promised Commitment Amounts............................................................................................................................31
1.5.1.8 Balance Segment Profile Option.............................................................................................................................31
5
1.5.1.9 Purchase Cards........................................................................................................................................................31
1.5.1.10 Prepayments..........................................................................................................................................................31
1.5.1.11 Trade Management Deduction Integration...........................................................................................................31
1.5.1.12 ACH Integration with iPayment (no depend on Receivables)..............................................................................31
1.5.1.13 Autoresolution and Split Claim Functionality......................................................................................................31
1.5.1.14 Attachment Functionality.....................................................................................................................................31
1.5.1.15 Setup Details Report.............................................................................................................................................31
1.5.2.1 Credit Management.................................................................................................................................................31
1.5.2.2 1099 Indicator.........................................................................................................................................................31
1.5.2.3 XML Invoices.........................................................................................................................................................31
1.5.2.4 Party Paying Relationships.....................................................................................................................................31
1.5.2.5 Multiple Reporting Currencies - Report Enhancements.........................................................................................32
1.5.2.6 Open Items Revaluation Report Enhancement.......................................................................................................32
1.5.2.7 Event Based Revenue Management.......................................................................................................................32
1.5.2.8 Multiple Reporting Currencies - Trigger Replacement..........................................................................................32
1.5.3.1 Allocate Transactional Data to Sales Groups.........................................................................................................32
1.5.3.2 User Interface Enhancements.................................................................................................................................32
1.5.3.3 Receipt to Receipt Applications.............................................................................................................................33
1.5.3.4 Invoice Creation API..............................................................................................................................................33
1.5.3.5 Invoice API Enhancement......................................................................................................................................33
1.5.3.6 Leveraging Oracle Approvals Management (AME) in Credit Memo Workflow...................................................33
1.5.3.7 Deposit API.............................................................................................................................................................33
1.5.3.8 Deductions Management Enhancements................................................................................................................34
1.5.3.9 Multiple Prepayment Types....................................................................................................................................34
1.5.3.10 Bank Account Function Security Enhancements..................................................................................................34
1.5.3.11 Enhanced Returns, Cancellations, and other Credit Activities.............................................................................34
1.5.3.12 Customer Credit Classifications...........................................................................................................................34
1.5.3.13 Deposit Application..............................................................................................................................................35
1.5.3.14 GL Transfer Program Controls for Business Users..............................................................................................35
2. Logistics..............................................................................................................................................................36
2.1 Oracle Inventory Management.....................................................................................................................36
2.1.1.1 Intercompany Invoicing with Advanced Pricing....................................................................................................36
2.1.1.2 Material Workbench...............................................................................................................................................36
2.1.1.3 Movement Statistics Release Number Display.......................................................................................................36
2.1.1.4 Movement Statistics Reference Period...................................................................................................................36
6
2.1.1.5 Movement Statistics Data Export Concurrent Program.........................................................................................36
2.1.1.6 Greek Inventory Trial Balance Report....................................................................................................................36
2.1.1.7 Safety Stocks by Project.........................................................................................................................................36
2.1.1.8 Large Org - Organization Hierarchy LOV Performance Enh.................................................................................36
2.1.1.9 Tax Registration Number........................................................................................................................................36
2.1.1.10 Greek Inventory Analytical Ledger Report..........................................................................................................36
2.1.1.11 Movement Statistics Ignore Record......................................................................................................................36
2.1.1.12 New Inventory Item Definition form....................................................................................................................36
2.1.1.13 Vendor Managed Inventory..................................................................................................................................36
2.1.2.1 Pick Methodologies for WIP..................................................................................................................................36
2.1.2.2 OSFM Lot API........................................................................................................................................................36
2.1.2.3 Greek Reports.........................................................................................................................................................36
2.1.2.4 Vendor Managed Inventory (VMI).........................................................................................................................36
2.1.2.5 MinMax Move Order Enhancements.....................................................................................................................37
2.1.2.6 Move Order Fill-Kill...............................................................................................................................................37
2.1.2.7 Serial Number Uniqueness by Model Item (ER 2112615).....................................................................................37
2.1.2.8 Consigned Inventory from Supplier.......................................................................................................................37
2.1.2.9 Serial Tracking in WIP with Genealogy.................................................................................................................37
2.1.2.10 OSFM Kanban Support........................................................................................................................................37
2.1.3.1 Component Picking Enhancements........................................................................................................................37
2.1.3.2 Consigned Inventory Diagnostics...........................................................................................................................37
2.1.3.3 PAR Replenishment Counts...................................................................................................................................37
2.1.3.4 Allocation Delete at Move Order Cancel (CU1)....................................................................................................38
2.1.3.5 Cross-Organization Serial Genealogy Inquiry (CU1)............................................................................................38
2.1.3.6 Aging Based Consumption of Consigned Inventory..............................................................................................38
2.1.3.7 ERES Support for 21 CFR Part 11 Compliance.....................................................................................................38
2.1.3.8 Enhanced Inter-company Transactions...................................................................................................................38
2.1.3.9 Item Master Changes..............................................................................................................................................39
2.1.3.10 Movement Statistics Exception Report.................................................................................................................39
2.1.3.11 Outbound Flow Sequence.....................................................................................................................................39
3. Manufacturing....................................................................................................................................................40
3.1 Oracle Bills of Material................................................................................................................................40
3.1.1.1 Manufacturing Routing Management.....................................................................................................................40
3.1.1.2 Manufacturing BOM Management.........................................................................................................................40
3.1.1.3 EBS Item Master.....................................................................................................................................................41
7
3.2 Oracle Cost Management..............................................................................................................................45
3.2.1.1 Transfer Inv Price Variance for Maint Work Orders (eAM)..................................................................................45
3.2.1.2 Enforce Integer Requirements flag for ASCP (BOM)............................................................................................45
3.2.1.3 Work in Process Value Report for Shop Floor Management.................................................................................45
3.2.1.4 New Item Attributes (Items)...................................................................................................................................45
3.2.1.5 Enhancements to Item Relationships (Items).........................................................................................................45
3.2.1.6 Enhanced Cost Import............................................................................................................................................45
3.2.1.7 Rule Based Material Overhead Absorption............................................................................................................45
3.2.1.8 Non Std Expense Work Orders Support for Shop Floor Mgmt..............................................................................45
3.2.1.9 Opt Estimated Scrap Acctg Support for Shop Floor Mgmt....................................................................................45
3.2.1.10 Transfer to Mfg. Copy to Mfg. Proc integ w/ ECO (ENG)..................................................................................45
3.2.1.11 End-Item Subst Item Wrkbench w/DataEntry enab Fldr-Items............................................................................45
3.2.1.12 Enhanced Supply Chain Rollup............................................................................................................................45
3.2.1.13 Category Grants (Items)........................................................................................................................................45
3.2.2.1 Enhancements to Routing.......................................................................................................................................45
3.2.2.2 Set Cost Controls....................................................................................................................................................45
3.2.2.3 Enhancements to BOM...........................................................................................................................................45
3.2.2.4 Enhance Support for Consigned Inventory from Supplier.....................................................................................45
3.2.2.5 Item Workbench with a Data Entry enabled Folder (Items)...................................................................................45
3.2.2.6 Transfer Pricing Costing and Accounting..............................................................................................................45
3.2.2.7 Enh WIP Lot Transaction Costing for Lot Based Work Orders.............................................................................46
3.2.2.8 FIFO/LIFO Layer Cost Management.....................................................................................................................46
3.2.2.9 Periodic Costing Acquisition Cost Adjustments....................................................................................................46
3.2.2.10 Enhanced Costing of Asset Maintenance.............................................................................................................46
3.2.3.1 Support for Retroactive Price Changes...................................................................................................................46
3.2.3.2 Support for Direct Labor Purchase Order for Maintenance Work Orders..............................................................46
3.2.3.3 Support for Enhance Intercompany........................................................................................................................46
3.2.3.4 Enhanced Period Close Summarization..................................................................................................................46
3.2.3.5 Increased Flexibility for Charges to Maintenance Work Orders............................................................................46
3.2.3.6 Supply Chain Cost Rollups with Dynamic Lot Size...............................................................................................46
3.2.3.7 Support for Linking of Maintenance Work Orders................................................................................................46
3.2.3.8 Support for Global Procurement in a Shared Services Environment.....................................................................47
3.3 Oracle Engineering.......................................................................................................................................48

3.3.1.1 MLS support for Change types...............................................................................................................................48
8
3.3.1.2 ERES Support in Eng Module for 21 CFR Part 11 Compliance............................................................................48
3.3.1.3 Increase change type name length..........................................................................................................................48
3.4 Oracle Quality...............................................................................................................................................49

3.4.1.1 Quality support for PJM in Mobile Supply Chain Apps (MSCA).........................................................................49
3.4.1.2 Flow Workstation Integration.................................................................................................................................49
3.4.1.3 Enabling Long Comments as New Collec Element Data Type..............................................................................49
3.4.1.4 New Collection Element and Trigger: TCA Party..................................................................................................49
3.4.1.5 Skip Lot Inspection WMS/MSCA Inbound Receiving Integ.................................................................................49
3.4.1.6 Receiving Insp Sampling WMS/MSCA Inbound Receiv Integ.............................................................................49
3.4.1.7 Multi-Lingual Support (MLS) for Quality..............................................................................................................49
3.4.1.8 Parent-Child Collection Plans.................................................................................................................................49
3.4.1.9 New Collection Trigger: PO Routing Name in Receiv Txn Int.............................................................................49
3.4.1.10 Order/Line-Specific Specifications and Samples.................................................................................................49
3.4.1.11 Folders Facility in Enter/Update Quality Results.................................................................................................49
3.4.1.12 Automatic Sequence Generation In Collection Elements.....................................................................................49
3.4.1.13 Quality support for PJM in Warehouse Mgmt System (WMS)............................................................................49
3.4.1.14 Quality Specification Matching Inquiry in Order Manageme..............................................................................49
3.4.1.15 WMS User-initiated Quality Check......................................................................................................................49
3.4.1.16 MSCA / Quality Inbound Receiving Integration..................................................................................................49
3.4.2.1 Quality Plans at Maintenance Operation Completion............................................................................................49
3.4.2.2 UOM Conversion at Specification Element Level.................................................................................................49
3.4.2.3 Support WIP Serial Tracking..................................................................................................................................49
3.4.2.4 Route Completion Transaction Flow......................................................................................................................50
3.4.2.5 Support Global Specifications................................................................................................................................50
3.4.2.6 Mobile LOV Enhancement project.........................................................................................................................50
3.4.2.7 Add Scrap Account and Item Revision as Collection Trigger................................................................................50
3.4.2.8 Job Deferral Transaction Flow...............................................................................................................................50
3.4.2.9 Corrective Actions Tracking...................................................................................................................................50
3.4.2.10 MRB Dispositions.................................................................................................................................................50
3.4.2.11 Support for Mobile Move Complete, Return and Move, Txn..............................................................................50
3.4.2.12 New Quality Actions to Create Work Order........................................................................................................50
3.4.2.13 Extend Specification Support for Range of Categories........................................................................................50
3.4.2.14 Installed Base Svc Support - new collec elements trigg.......................................................................................50
3.4.2.15 Maintenance Operation Completion Transaction Flow........................................................................................50
3.4.2.16 Nonconformance Management.............................................................................................................................50
3.4.2.17 Incr Spec Element Collec Element for Dec Precision up to.................................................................................50
3.4.2.18 MRB Disposition Transaction Flow.....................................................................................................................50
9
3.4.3.1 ERES Support in Item, BOM and Engineering Modules.......................................................................................50
3.4.3.2 UI Enh: Read Only Collection Element.................................................................................................................53
3.4.3.3 UI Enh: Date and Time Support.............................................................................................................................53
3.4.3.4 PO - Receiving Enh: Centralized Receiving Functions for WMS..........................................................................54
3.4.3.5 PO - Receiving Enh: Receiving Time Stamp Support............................................................................................54
3.4.3.6 Guaranteed by Manufacturer Results (Enhancement #3763419) (CU1)................................................................54
3.4.3.7 Samples and Results Screen Expansions (Enhancement #3676133) (CU1)..........................................................54
3.4.3.8 EAM Integration with Rebuild Work Orders.........................................................................................................54
3.4.3.9 ERES Support in Quality Module..........................................................................................................................54
3.4.3.10 ERES Support in Purchasing and Receiving Modules.........................................................................................57
3.4.3.11 ERES Support in Inventory Module.....................................................................................................................58
3.4.3.12 ERES Support in WIP Module.............................................................................................................................59
3.4.3.13 ERES Support in Shipping Module......................................................................................................................60
3.4.3.14 PO - Receiving Enh: Receiving Locator Support.................................................................................................60
3.4.3.15 UI Enh: Quality Workbench.................................................................................................................................60
3.4.3.16 OPM Quality Screen Enhancements (CU1).........................................................................................................61
3.4.3.17 Test Selection for Results Association (Enhancement #3756942) (CU1)............................................................61
3.4.3.18 UI Enh: Gapless Sequence Element Generation...................................................................................................61
3.5 Oracle Work in Process................................................................................................................................63

3.5.1.1 Discrete Workstation Coexistence with Shop Floor Mgmt....................................................................................63
3.5.1.2 Overcompletion Quantities Reserved to Sales Orders............................................................................................63
3.5.2.1 Infinite Scheduler Modifications............................................................................................................................63
3.5.2.2 Additional Date Choices on Closed Jobs SRS........................................................................................................63
3.5.2.3 Support for Additional Pick Methodologies...........................................................................................................63
3.5.2.4 Enh Warnings when Completing, Canceling, or Closing Jobs...............................................................................63
3.5.2.5 Unit Effectivity Update through Mass Load...........................................................................................................63
3.5.2.6 Option to Manually Release Tasks for Comp Picking for Mfg..............................................................................63
3.5.2.7 Lead Time Calculation Enhancement.....................................................................................................................63
3.5.2.8 Component Picking by Job Operation....................................................................................................................63
3.5.2.9 Serial Tracking and Genealogy through Production...............................................................................................63
3.5.3.1 Scheduling Workbenches.......................................................................................................................................63
3.5.3.2 Operation Progress Reporting.................................................................................................................................63
3.5.3.3 Discrete Workstation Enhancements......................................................................................................................64
3.5.3.4 Component Quantity Change during Backflush.....................................................................................................64
10
3.5.3.5 Component Picking Enhancements........................................................................................................................64
3.5.3.6 Alternate Resource Sets..........................................................................................................................................65
3.5.3.7 Additional Flexibility for Excluding ECOs............................................................................................................65
3.5.3.8 Electronic Records and Electronic Signatures (ERES) Support for 21 CFR Part 11 Compliance.........................65
3.5.3.9 Modifications to Transaction Processing Profiles .................................................................................................66
3.5.3.10 Mobile Manufacturing Enhancements..................................................................................................................66
3.5.3.11 Usability Improvements for Component Lot/Serial Entry during Backflush (CU1)............................................66
3.5.3.12 Outside Processing Enhancements.......................................................................................................................66
3.5.3.13 Scrap Enhancement...............................................................................................................................................66
4. Order Management.............................................................................................................................................67
4.1 Oracle Order Management............................................................................................................................67
4.1.1.1 Euro Customer Conversion Program......................................................................................................................67
4.1.1.2 Order Management Diagnostic Programs...............................................................................................................67
4.1.1.3 Default Source Type for Drop Ship........................................................................................................................67
4.1.1.4 Commitment Enhancements...................................................................................................................................67
4.1.1.5 EDI 875 - Grocery Products Purchase Order..........................................................................................................67
4.1.1.6 Global Credit Checking..........................................................................................................................................67
4.1.1.7 EDI 850 -Purchase Order........................................................................................................................................67
4.1.1.8 API Extension for Defaulting Dependencies..........................................................................................................67
4.1.1.9 Manual Release of Credit Check Holds Enhancements.........................................................................................67
4.1.1.10 International Trade Management (ITM) Additions..............................................................................................67
4.1.1.11 Item Substitution at Scheduling............................................................................................................................67
4.1.1.12 Order Information Enhancements.........................................................................................................................67
4.1.1.13 Pricing and Availability........................................................................................................................................67
4.1.1.14 Sales Order Form Usability Enhancements..........................................................................................................67
4.1.1.15 Pricing by Secondary Quantity/UOM (Catchweight Pricing)..............................................................................67
4.1.1.16 Multiple Currency Price Lists...............................................................................................................................67
4.1.1.17 Audit Trail.............................................................................................................................................................67
4.1.1.18 View Shipping Status Window.............................................................................................................................67
4.1.1.19 Prepaid Credit Card Receipts in Order Management...........................................................................................68
4.1.1.20 Credit Checking Support for External Systems....................................................................................................68
4.1.1.21 Drop Shipment of Configurations.........................................................................................................................68
4.1.1.22 Solution-Based Modeling.....................................................................................................................................68
4.1.2.1 Enhanced Basic Search for Finding Customers......................................................................................................68
4.1.2.2 Call Supply To Order Workbench to display Supply informat..............................................................................68
4.1.2.3 TeleSales eBusiness Center to Sales Order Window..............................................................................................68
11
4.1.2.4 Order Management Setup Validation Report.........................................................................................................68
4.1.2.5 Enhanced Multi-currency Setup.............................................................................................................................68
4.1.2.6 Electronic Msgs: RosettaNet..................................................................................................................................68
4.1.2.7 Display of Operating Unit Field.............................................................................................................................68
4.1.2.8 Credit Management Integration..............................................................................................................................68
4.1.2.9 High Volume Order Import....................................................................................................................................68
4.1.2.10 Enhanced Pre-calculated Exposure.......................................................................................................................68
4.1.2.11 Blanket Orders......................................................................................................................................................68
4.1.2.12 Scheduling Across Orders....................................................................................................................................68
4.1.2.13 Related Items and Manual Substitution................................................................................................................68
4.1.2.14 Electronic Msgs: EDI (850/860/875)....................................................................................................................68
4.1.2.15 Quick Order Entry................................................................................................................................................68
4.1.2.16 Override ATP........................................................................................................................................................68
4.1.2.17 Electronic Msgs: XML.........................................................................................................................................69
4.1.2.18 Enh Freight Rating Ship Method Selection thru Oracle Tra................................................................................69
4.1.2.19 Late Demand Penalty............................................................................................................................................69
4.1.2.20 Gross Margin Display on Sales Order Line..........................................................................................................69
4.1.2.21 Override Item Description on Sales Order...........................................................................................................69
4.1.2.22 Variable Duration Accounting Rule.....................................................................................................................69
4.1.3.1 Versioning...............................................................................................................................................................69
4.1.3.2 Retroactive Billing .................................................................................................................................................69
4.1.3.3 Scheduling Flexibility.............................................................................................................................................69
4.1.3.4 Catch Weights for Discrete Inventory....................................................................................................................70
4.1.3.5 Blanket Sales Agreement Enhancements...............................................................................................................70
4.1.3.6 OM-EM: RosettaNet 3A8 Request Purchase Order Change / OAG Change PO...................................................71
4.1.3.7 OM-EM: RosettaNet 3A7 Notify Purchase Order Update / OAG Change SO......................................................71
4.1.3.8 OM-EM: RosettaNet 3A4 Request Purchase Order / OAG Process PO................................................................72
4.1.3.9 OM-EM: RosettaNet 3A4 Purchase Order Response / OAG Acknowledge PO....................................................72
4.1.3.10 OM-EM: Open Interface Tracking User Interface................................................................................................72
4.1.3.11 Multiple and Partial Payments..............................................................................................................................72
4.1.3.12 Preview and Print Sales Documents.....................................................................................................................73
4.1.3.13 Order Management Parameters............................................................................................................................73
4.1.3.14 OM-EM: RosettaNet 3A9 Request Purchase Order Cancel / OAG Cancel PO...................................................73
4.1.3.15 Project/Task Changes for Booked Orders............................................................................................................73
4.1.3.16 Approval Enhancements.......................................................................................................................................73
4.1.3.17 Advanced Item Search..........................................................................................................................................74
4.1.3.18 Automatic Fulfillment Set and Line Set Assignment...........................................................................................74
4.1.3.19 Authoring and Negotiating Contract Terms ........................................................................................................74
12
4.1.3.20 Drop Ship Change Management ..........................................................................................................................75
4.1.3.21 Drop Ship Across Sets of Books...........................................................................................................................75
4.1.3.22 International Trade Management (ITM) Partner Integration Enhancements.......................................................76
4.1.3.23 High Volume Shipping Interface .........................................................................................................................76
4.1.3.24 High Volume Pricing............................................................................................................................................76
4.1.3.25 Global Order Promising for ATO Configurations................................................................................................77
4.1.3.26 Fulfillment with Wait............................................................................................................................................77
4.1.3.27 Move Add Change Disconnect (MACD).............................................................................................................77
4.1.3.28 Line Level Ship/Arrival Sets................................................................................................................................77
4.1.3.29 Configuration Date Effectivity Enhancements.....................................................................................................78
4.1.3.30 Display Choices for Freight Rating......................................................................................................................78
4.1.3.31 Decimal Quantities for Options of ATO Configurations......................................................................................78
4.1.3.32 End Customer.......................................................................................................................................................78
4.1.3.33 Service Termination .............................................................................................................................................79
4.1.3.34 Simple Negotiation in Oracle Order Management...............................................................................................79
4.1.3.35 Pricing and Availability Enhancements................................................................................................................81
4.1.3.36 Publishing Plan Results to Oracle Order Management .......................................................................................82
4.1.3.37 Reservation Enhancements...................................................................................................................................82
5. Procurement........................................................................................................................................................83
5.1 Oracle Purchasing.........................................................................................................................................83
5.1.1.1 Enhancements to Procurement of Configured Items..............................................................................................83
5.1.1.2 ASN Inbound into Oracle Purchasing via XML.....................................................................................................83
5.1.1.3 Enhancement to Purchasing Documents Open Interface........................................................................................83
5.1.1.4 Integration with Oracle Sourcing............................................................................................................................83
5.1.1.5 Enhanced Requisition Modification Capabilities...................................................................................................83
5.1.1.6 Support for Vendor Management Inventory...........................................................................................................83
5.1.1.7 Enhancements to Email PO....................................................................................................................................83
5.1.1.8 Auto Sourcing Enablement during Blanket Agmt Approval..................................................................................83
5.1.2.1 Integration with Oracle Commitment Budgetary Control (CBC)..........................................................................83
5.1.2.2 Global Agreements.................................................................................................................................................83
5.1.2.3 Receiving Improvements........................................................................................................................................83
5.1.2.4 Renegotiate Blanket Agreements in Oracle Sourcing............................................................................................83
5.1.2.5 Currency amount-based Price Tolerances for POs.................................................................................................83
5.1.2.6 Outbound XML Purchase Order Improvements.....................................................................................................83
5.1.2.7 API Additions.........................................................................................................................................................83
5.1.2.8 Consigned Inventory...............................................................................................................................................83
13
5.1.2.9 Pricing Improvements.............................................................................................................................................83
5.1.3.1 Services Procurement.............................................................................................................................................84
5.1.3.2 Purchasing Documents Open Interface Enhancements..........................................................................................84
5.1.3.3 Requisition Approval Management using Oracle Approvals Management...........................................................84
5.1.3.4 Accounting..............................................................................................................................................................84
5.1.3.5 Center-Led Procurement Features..........................................................................................................................85
5.1.3.6 AutoCreate and Purchase Order Entry Usability ...................................................................................................86
5.1.3.7 Gapless Self-Bill Invoice Numbering.....................................................................................................................86
5.1.3.8 FDA CFR 21 Compliance.......................................................................................................................................86
5.1.3.9 Logistics..................................................................................................................................................................87
5.1.3.10 Procurement Contracts..........................................................................................................................................88
5.1.3.11 Pricing...................................................................................................................................................................89
5.1.3.12 Purchase Order Printing and Communication......................................................................................................90
14
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.
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.
15
1. Financial
1.1 Oracle Assets

1.1.1 Release 1158 Features
1.1.1.1 Adjustments API
No description is available for this feature.
1.1.1.2 Retirements and Reinstatements API
1.1.1.3 Common Transaction API
1.1.1.4 Parallelized Mass Transactions
1.1.1.5 Depreciable Basis Formula
1.1.1.6 Reclassifications API
1.1.1.7 Unplanned Depreciation API
1.1.1.8 Manual Depreciation Override
1.1.1.9 Capitalizations API
1.1.1.10 Mass Copy Continue Despite Errors
1.1.1.11 Additions API
1.1.1.12 Asset Description API
1.1.1.13 Transfers and Unit Adjustements API
1.1.1.14 Enhanced Mass Retirements
1.1.1.15 View Currency Details
1.1.1.16 Enhanced Mass Change and Mass Transfers
1.1.2.1 Enhanced Mass Transfers
16
1.1.2.2 Enhanced MRC Processing
1.1.2.3 Enhanced Mass Revaluations
1.1.2.4 Source Line Retirement
1.1.2.5 Override Depreciations in MRC-enabled Books
1.1.2.6 Japanese Depreciable Tax Report Enhancement
1.1.3.1 Group Asset Security
A group asset can now be enabled or disabled from the Asset Workbench. A disabled
group will not depreciate and you cannot perform any transactions affecting the group
asset.
1.1.3.2 Group Depreciation
Group Depreciation simplifies management of large volumes of assets by pooling
individual assets into groups. This feature also enables companies to comply with tax,
financial and regulatory reporting governing asset depreciation. Examples of such
reporting are Capital Cost Allowance in Canada, Written Down Value in UK, Asset
Depreciation Ranges in US, tax reporting of Blocked Assets in India and corporate tax
reporting in Japan.
1.1.3.3 Polish Tax Depreciation
New depreciable basis rules will be provided for compliance of Polish tax regulations
governing the depreciation of assets.
1.1.3.4 Enhanced Depreciation Override
Depreciation Override provides a mean to 'true-up' an asset's depreciation expense and
bonus depreciation expense for a given accounting period. A new form will be available
for entering user-defined expense amounts to override system-calculated amounts.
1.1.3.5 Business Events
Oracle Assets now supports the subscription of Business Events for addition, retirement
and transfer of assets using Oracle Workflow. Business Events simplify integration
between Oracle Assets and other systems by minimizing the need for custom database
triggers.
1.1.3.6 Mass External Transfers
Mass External Transfers offers an open interface for accepting asset transfers and source
line transfers from external systems.
1.1.3.7 Retirement Notification
Retirement Notification streamlines the process of retiring massive numbers of assets in a
retirement project. Users of Oracle Projects in the field can raise retirement notifications
to fixed assets accountants by specifying certain options such as category, location and
number of assets, etc. The system selects assets based on the selected criteria and retires
them when the fixed assets accountants approve the selection. Cost of removal and
proceeds can be transferred from Oracle Projects into Group Assets in Oracle Assets for
reserve adjustments.
17
1.1.3.8 Support for CIP Assets in Groups
CIP assets can now be assigned to Group Assets. This option is controlled at the Asset
Book level.
1.1.3.9 Mass Property
Mass Property Asset Treatment provides companies with high asset volumes the ability
to treat similar assets installed in the same fiscal year as a single asset, which holds the
aggregate cost and units. Storing assets in this manner greatly simplifies the tracking,
reporting, analysis and ultimately the retirement of these assets, since all like assets from
a particular vintage year are stored as an individual asset.
1.1.3.10 Asset Trace Utility
Asset Trace Utility provides a comprehensive view of asset data for diagnoses and
troubleshooting. This HTML report shows data stored major transaction database tables
for a given asset.
1.1.3.11 Enhanced Asset Inquiry
Asset Inquiry is a self-service inquiry tool that allows you to access real-time information
of your assets. This tool is enhanced with Advanced Search capability and additional
search parameters. You can also view attachments to assets such as documents, images,
video and audio clips, etc.
1.1.3.12 Enhanced 'What-If' Analysis in Multiple Reporting Currencies (MRC)
What-if Analysis and the following reports can now be processed from a single
application responsibility related to the primary currency book:
• Reserve Summary
• Reserve Detail
• Cost Summary
• CIP Summary
• Cost Detail
• CIP Detail
• Asset Additions
• Cost Adjustments
• Asset Retirements
• Fully Reserved Assets
• Account Drill Down
• Drill Down Report
• Cost Clearing Reconciliation
• Journal Entry Reserve Ledger
• Tax Reserve Ledger
18
1.2 Oracle Cash Management
1.2.1.1 Reconciliation Open Interface Integration with Treasury
1.2.1.2 Bank Statement Transmission
1.2.1.3 Exchange Rates for Foreign Currency Bank Accounts
1.2.1.4 Intra-day Transaction Reporting
1.2.2.1 Archive and Purge of Bank Statement Open Interface
1.2.2.2 Intra-Day Bank Statement Transmission
1.2.2.3 XML Interface for Bank Statement
1.2.3.1 Cash Positioning Enhancements
Cash Positioning is a planning tool that helps you view your daily cash position by
currency or by bank account, allowing you to project your daily cash needs and evaluate
your company's liquidity position.
To expedite the generation of a cash position, you can now specify in your cash position
worksheet the option to use pre-calculated prior day cash flow balances instead of
generating real-time prior day cash flow balances. To utilize this option, you will need to
select 'Yes' for the 'Use Calculated Prior Day Cash Flow and Overdue Transactions
Balances' field in the worksheet and run the Cash Position Prior Day Cash Flow and
Overdue Transactions program to calculate your prior day balances as well as the
overdue transactions, prior to generating your cash position. You can choose to run the
Cash Position Prior Day Cash Flow and Overdue Transactions program manually or you
can have the program run automatically according to the schedule you define. In addition
to calculating prior day and overdue transaction balances, the Cash Position Prior Day
Cash Flow and Overdue Transactions program will purge old summary data.
Additionally, overdue transactions will be displayed in a separate row from the prior day
cashflows in the cash position results.
Lastly, the existing discoverer workbook for cash position results has been replaced with
four simplified workbooks for ease of use. The four new workbooks are: Cash Position
with Surplus / (Deficit), Cash Position with Closing Balance, Cash Position with Surplus
/ (Deficit) using Calculated Prior Day Cash Flow and Overdue Transactions and Cash
Position with Closing Balance using Calculated Prior Day Cash Flow and Overdue
Transactions.
1.2.3.2 Batches Available for Reconciliation Report
The new report 'Batches Available for Reconciliation', lists payment batches and
19
remittance batches that are available for reconciliation. The existing Transactions
Available for Reconciliation Report has been modified to display individual transactions
such as payments or receipts that are available for reconciliation. The new report can be
run with the following parameters - Batch Type, Bank Account Number and Order By.
1.2.3.3 Reconciliation of Oracle Payroll EFT Payments
This feature enhances the bank reconciliation functionality in Oracle Cash Management
by providing the ability to reconcile Payroll EFT payments, in addition to Payroll check
payments in Oracle Cash Management.
Oracle Cash Management provides support for various payment formats like NACHA,
BACS etc. for Payroll EFT Payments reconciliation. In order to use this feature, you will
first need to define the transaction code that specifies the payroll payment format. When
defining a transaction code with a payment format, the 'Payroll Matching Order' field
will show the order you need to define your BANK_TRX_NUMBER format in your
bank statement-mapping template. You will then need to either update or define a new
bank statement-mapping template to enter the Format for the BANK_TRX_NUMBER
with the format that is needed to identify the EFT payments.
Multiple identifiers might be needed to identify EFT payments. You will need to
determine what the identifiers are and enter the Format for the BANK_TRX_NUMBER
with the formats that are needed to identify the EFT payments. The format should be
entered in the order specified by the Payroll Matching Order assigned to the transaction
code setup for Payroll EFT payments. Once the setup is complete you can load, import
and reconcile bank statements containing Payroll EFT payments.
1.2.3.4 Bank Purging Program
The Bank Purging program is a tool to purge Oracle Payables and Oracle Payroll banks,
bank branches, internal bank accounts and employee bank accounts that have never been
used. This program reduces the number of unnecessary banks, bank branches and bank
accounts in the system and is provided as a data clean up tool. The Bank Purging
Program runs across operating units and automatically submits the Bank Purging
Execution Report when it is run. This program can be run in two modes - one is the
preview mode where you can preview the bank records that can be purged and second is
the actual purge process. It is recommended that you run the program in the preview
mode first to confirm that the records picked up by the program are the ones you actually
want to purge.
The Bank Purging Program also kicks off the Bank Purging Execution Report that
displays bank records that are processed by the program.
1.2.3.5 Cash Forecasting By Transaction Currency
This feature enhances the existing cash forecasting functionality in Oracle Cash
Management by providing the ability to view forecast results in the transaction currency.
For this purpose, the existing Cash Forecast by Transaction Currency worksheet has been
modified to include transaction amounts grouped by transaction currency. These amounts
will be displayed under "Transaction Amount by Transaction Currency", adjacent to the
"Forecast Amount by Transaction Currency".
1.2.3.6 Cash Forecasting Temporary Labor and Fixed Price Services
This feature enhances the existing cash forecasting functionality in Oracle Cash
Management for Purchase Orders and Purchase Requisitions source types. You will now
be able to forecast three additional purchase line types: Fixed Price Services, Rate Based
Temporary Labor, and Fixed Price Temporary Labor, in addition to the existing line
types of Goods and Services. You can choose to include or exclude line types of
'Temporary Labor' from your cash forecast, when defining the forecast template row for
20
the Purchase Order or Purchase Requisition source types.
1.2.3.7 Cash Positioning
Cash Positioning is a planning tool that helps you view your daily cash position by
currency or by bank account, allowing you to project your daily cash needs and evaluate
your company's liquidity position.
This feature replaces the current cash positioning functionality in Oracle Treasury with
an enhanced Cash Positioning module in Oracle Cash Management, providing a single
access point for both Cash Management and Treasury users to generate their daily cash
positions based on actual cash flows from various Oracle Applications.
The new Cash Positioning module has an improved user interface, being based on the
new Oracle Applications Framework. The new User Interface introduces a cash position
worksheet, which allows more flexibility in the selection of sources to be included in the
cash position. A new source, bank account balance, has been added so that you can
include your actual or projected bank account balances for bank accounts shared between
Oracle Treasury and Oracle Cash Management, as your beginning balance for a cash
position. In addition to the three existing balance types - Ledger Balance, Cash Flow
Balance and Interest Calculated Balance, you will be able to load and import two more
balance types - 1-day float and 2-day float that can be used to offset the opening
balances. You can also enter the target balance for bank accounts shared between Oracle
Treasury and Oracle Cash Management in treasury, for display in the cash position.
Treasury user's can also choose to include subsidiary bank account balances in their cash
position, which are displayed in a separate section in the 'View By Bank Account' page.
The single Treasury Transactions source has been replaced with two new sources -
'Treasury Inflow' and 'Treasury Outflow'. The new Cash Positioning module allows you
to generate daily cash positions by bank account and by currency by including actual
cash flows from Oracle Payables, Oracle Receivables, Oracle Treasury and Oracle
Payroll. You can include intra-day transactions that have been loaded and imported into
Oracle Cash Management, user-defined inflows and outflows and data from your legacy
systems through the External Cash flow Open Interface.
Using the newly updated cash positioning module, you can view your daily cash position
for a range of currencies and bank accounts, drill down to the source transaction details,
exclude detail transactions from the cash position, drill down to the details of intra-day
activities, compare the bank reported intra-day activities with the system calculated net
cash flow and generate exposures in treasury for the differences, refresh the cash position
online, view the target balance and the difference between the projected closing balance
and target balance per bank account, initiate inter-account funds transfers, export the cash
position results to an external application like Excel and view the cash position in a
discoverer workbook to analyze the results further.
Additionally, from the cash position results, you can generate Balance Gapping for any
currency included in the cash position over a given date range to identify gaps in your
cash flows, view your short term liquidity position in the Available Liquidity section for
discounted security deals, fixed income security deals and short term money deals and
drill down to the details of each of these deal types.
Lastly, the consolidated module applies Oracle Treasury's Legal Entity security when
treasury users create and view cash positions. For Cash Management users, the Treasury
Inflow and Treasury Outflow sources along with the features of Balance Gapping and
Funds Transfer are not available.
1.2.3.8 Cash Forecasting
Cash Forecasting is a planning tool that helps you to anticipate the flow of cash in and
21
out of your business, allowing you to project your cash needs and evaluate your
company's liquidity position.
This enhancement merges Oracle Treasury's Cash Forecasting module with Oracle Cash
Management to streamline the creation and generation of cash forecasts and in the
process eliminates dual development and maintenance. The consolidated cash forecasting
module has an improved user interface, being based on the new Oracle Applications
Framework. The new user interface allows more flexible entry of forecast templates,
giving you the option to setup forecast templates for forecasting by days either manually
or automatically. You can also copy forecast templates as well as template rows within a
template. The existing single forecast source of Treasury Transactions has been split into
two to distinguish between inflows and outflows and the new sources are named-B
"Treasury Inflow" and "Treasury Outflow" respectively. The consolidated module also
provides you the option to view forecast results by bank account and by GL Cash
Position in addition to the regular transaction source view. You can do this by choosing
the option to view the opening balance either by bank account, by GL Cash Position or
both, when submitting the forecast. If you choose to view the opening balance by bank
account, you must also specify the type of bank account balance and the float for
offsetting the balance. Treasury user's can also choose to include subsidiary bank account
balances in their forecast results. The forecast results will be grouped either by bank
account name and number or the GL Cash Account for transactions sources that have a
bank account associated to them. Projected cash flow sources like Sales Order, Invoices
etc. do not have a bank account associated to them and will be grouped under a heading
called "Other" and displayed in a separate row. You can also drill down to the details of
transactions per bank account or per GL Cash Account. This new feature allows you to
project the closing bank account balance or GL Cash Position for your forecast horizon.
The GL Cash Position is no longer available as a transaction source as it is now
incorporated into the forecast submission parameters as a view option.
Additionally, from the forecast results by transaction source page you can choose to
exclude rows from summary calculation, drill-down to source transaction details, exclude
transactions from summary cash flows and add new transactions manually to the cash
flows. You also have the ability to export both the details and the summary cash flows to
an external application like Excel and to view the cash forecast in a Discoverer
Workbook to analyze the results further.
Lastly, the consolidated module applies Oracle Treasury's Legal Entity security when
treasury users create and view forecasts. For Cash Management users, the two sources of
Treasury Inflow and Treasury Outflow are not available for forecasting.
22
1.3 Oracle General Ledger
1.3.1.1 Journal Import Warning Status for Data Errors
1.3.1.2 Translation Performance Enhancement
1.3.1.3 Parallel Consolidation Performance Enhancement
1.3.1.4 Open Period/Posting/Transla Compatib Across Sets of Books
1.3.1.5 Translation/Consolidation Compatibility
1.3.1.6 Global Consolidation System Cross Instance Data Transfer
1.3.2.1 Fiscal Year-End Amount Type in FSG Reports
1.3.2.2 Streamlined Revaluation Process
1.3.2.3 Budget Pgms, Translation, Posting Compat Acr Sets of Boo
1.3.2.4 Global Intercompany System (GIS) Reject of Interco Txns Op
1.3.2.5 Translation of Income Stmt Accounts Using Period-End Rates
1.3.2.6 MRC Journal Originator Tracking
1.3.2.7 Enh Global Consolid System Cross-Instance Data Txfr Securi
1.3.2.8 Enhanced Account Hierarchy Manager Security
1.3.3.1 FSG Reports Name Display in Concurrent Manager
The Financial Statement Generator (FSG) report name is now displayed when you
review your concurrent requests. This allows you to quickly and easily identify your FSG
reports in the Concurrent Manager without having to view each report's output.
1.3.3.2 Open Period/Posting/Translation/Summary Accounts Program
Compatibility Among Sets of Books
You can now open periods, run translation, post journals, and maintain your summary
accounts simultaneously when these programs are initiated in different sets of books.
23
This significantly improves performance for companies using multiple sets of books in a
single database instance. Instead of having to wait for each program to complete before
the next one can begin, you can run the following programs in parallel among different
sets of books: Open Period, Posting, Translation, Add/Delete Summary Accounts,
Incremental Add/Delete Summary Templates, and Maintain Summary Templates.
1.3.3.3 Continue Step-Down Allocation Option
Step-Down Allocation Sets was first introduced in Release 11i to allow you to
automatically generate journal batches in a specific order so that the posted results of one
step are used in the subsequent step. Previously, Step-Down Allocations stopped
processing if a step did not generate a journal entry. This required users to manually
generate the subsequent batches.
Now, you can control whether a Step-Down Allocation process should continue
processing even if one of the steps did not generate a journal entry. By setting a new
profile option, you can instruct Step-Down Allocation Sets to continue processing to the
end of the Allocation Set.
1.3.3.4 GL Standard Reports Integration with XML Publisher (CU1)
1.3.3.5 XBRL Financial Reporting
Oracle General Ledger now supports eXtensible Business Reporting Language (XBRL).
You can create financial reports in XBRL format using the Financial Statement
Generator (FSG).
XBRL is an open specification for software that uses eXtensible Markup Language
(XML) data tags to standardize financial reporting across industries, regulatory bodies,
and geographies.
You can link FSG reports to XBRL taxonomies, enabling the automatic creation of
XBRL instance documents. The ability to create reports in XBRL allows you to prepare,
publish and exchange financial information across all software formats and technologies
in a consistent standards-based manner for easy distribution, analysis, and comparison.
1.3.3.6 Streamlined Core Oracle Financials Workbenches
In this release, Oracle Financials improved the format and usability of workbenches in
five core products to streamline transaction entry and management. The user interface in
key screens was enhanced to reduce the number of keystrokes required to enter and
manage transactions, and to make access to associated transaction details quick and
intuitive.
Screens were consolidated and made larger to display more data at once using fewer
windows. While primarily cosmetic, these enhancements will improve speed and ease of
use for all types of users who enter and manage these key financial transactions. Oracle
General Ledger enhanced the Enter Journals Workbench with these improvements.
1.3.3.7 Secondary Tracking Segment
You can now specify a segment in your chart of accounts as a secondary tracking
segment, in addition to the balancing segment, to perform more detailed analysis within
Oracle General Ledger. The secondary tracking segment is used in the revaluation,
translation, and fiscal year-end close processes. The system will automatically maintain
unrealized gain/loss, retained earnings, and cumulative translation adjustments by unique
pairs of balancing segment and secondary tracking segment values.
1.3.3.8 Presentation Quality FSG Reports Using XML Publisher
Financial Statement Generator (FSG) is now integrated with XML Publisher so that you
24
can use the convenient formatting features of a word processing application to design the
layout of your FSG reports. Some of the report formatting options include changing font
characteristics, adding graphical images, inserting headers and footers, creating borders,
reordering columns, and supporting an unlimited number of columns in your reports.
This enables you to create boardroom-quality financial reports directly from the general
ledger, which ensures the integrity and auditability of your financial information. For
more information on formatting features, please refer to the XML Publisher release
content document.
1.3.3.9 Journal Import SRS Program
You can now submit the journal import program from Standard Request Submission
(SRS) to take advantage of the SRS features, such as grouping journal import runs into
request sets and scheduling journal import to run automatically. Using request sets and
scheduling allow multiple journal import requests to run simultaneously, and also allow
you to control the sequence in which journal import should run during the period close.
1.3.3.10 Journal Import Group By Effective Dates
Journal Import now provides an option to automatically group journal lines into journal
entries based on effective dates. This functionality was previously only available to
customers using average balance processing. Now this option is available to all
customers and is particularly useful for those who use Daily Business Intelligence.
1.3.3.11 Interface Data Transformer
The Interface Data Transformer is a user-friendly tool that facilitates the import of data
from external feeder systems into Oracle General Ledger. It takes data from external
feeder systems that have been loaded into the GL_INTERFACE table and transforms it
into the proper format for import into Oracle General Ledger based on rules that you
define.
The Interface Data Transformer offers a variety of ways to transform data in the
GL_INTERFACE table. You can use string functions to parse and concatenate
substrings, reference lookup tables to convert one value into another, or call PL/SQL
functions to perform sophisticated transformations. You can even define conditions to
control when transformation rules are applied and validate the results of the
transformation through value sets and lookup tables. This flexibility makes it easier for
you to integrate non-Oracle systems into Oracle General Ledger.
1.3.3.12 Multilingual Support For FSG Amount Types
Multilingual support has been added to the Financial Statement Generator (FSG) amount
types. Amount types, such as PTD and YTD, can now be displayed in the installed
language. This is particularly useful for global companies using multiple language
installations on a single instance to view amount types in the language of their choice
when creating reports.
1.3.3.13 MRC Revaluation Against Primary Currency
You now have more flexibility when revaluing balances in Multiple Reporting
Currencies (MRC) Reporting sets of books. Instead of revaluing the MRC reporting
book's balances against the primary book's entered currency amounts, you can revalue
against the primary set of books' functional currency balances. Applying this revaluation
methodology in your reporting sets of books enables you to adhere to the Translation
standards of #SFAS52 (which can also be satisfied by Oracle General Ledger translation
functionality), while maintaining transaction level detail in your reporting currency at the
same time.
1.3.3.14 Currency Rates Manager
25
The Currency Rates Manager presents a new interface for you to easily manage your
daily and historical rates. You can quickly upload and download currency rates via
spreadsheets, or you can enter and maintain rates using the new web-based user interface.
For daily conversion rates, you can automatically upload daily rates from a spreadsheet
or manage rates using the web-based interface. Currency Rates Manager can even
automatically calculate the cross rates between two or more currencies to ensure
consistency in daily conversion rates across currencies. For example, if you define rates
from U.S. dollars to euros, and from U.S. dollars to Japanese Yen, the Currency Rates
Manager can calculate the cross rate between euros and yen, and the inverse rate from
yen to euros. This ensures that intercompany transactions across multiple currencies are
accounted for with consistent rates, minimizing the effect of exchange rate differences
during the intercompany elimination process. Automatic generation of cross rates also
reduces the number of currency combinations and rates that you must enter manually,
thus enabling you to work more efficiently.
For historical rates, you can automatically upload rates from a spreadsheet, or you can
automatically download rates into a spreadsheet. The ability to download historical rates
into a spreadsheet enables you to modify the rates if necessary, and copy them from one
set of books to another for ease of maintenance. Added security is provided to ensure that
you can only upload historical rates to periods that are open.
1.3.3.15 Open Integration with External Processing
Oracle General Ledger now includes a number of business events to allow you to
customize Oracle General Ledger processes without modifying the standard code. You
can configure each event to trigger a notification, message, or other process to perform
additional data validation or enrichment, for example.
The Oracle Workflow Business Event System is an application service that leverages the
Oracle Advanced Queuing (AQ) infrastructure to communicate business events among
systems within an enterprise as well as between enterprises. The Business Event System
consists of the Event Manager, which lets you register subscriptions to events that are
significant to your systems, and event activities, which let you model business events
within workflow process. For more information, please refer to documentation on the
Oracle Workflow product.
Oracle General Ledger now includes the following business events:
• Account Disabled: This event occurs when an account is disabled in the GL
Accounts form or by the Inherit Segment Value Attributes program.
• Period Opened: This event occurs when a period is opened for the first time.
• Period Closed: This event occurs when a period is closed.
• Period Re-opened: This event occurs when a period is opened after it was
previously closed.
• Journal Import Started: This event occurs when a journal import process is
initiated.
• Journal Import Completed: This event occurs when a journal import process is
completed.
• Posting Completed: This event occurs when a posting process is completed.
26
1.4 Oracle Payables
1.4.1.1 Invoice Approval Workflow
1.4.1.2 View Currency Details
1.4.1.3 Payment Batch Scheduling
1.4.1.4 Primary Pay Site
1.4.1.5 Profile Option Migration
1.4.1.6 MRC Technology Changes
1.4.1.7 Payment Batch Enhancements
1.4.1.8 Building Prepayment Accounts When Matching
1.4.1.9 Expense Report Import
1.4.1.10 Invoice Approval Workflow Enhancement
1.4.1.11 Folderized Payment Batch Sets
1.4.1.12 Interest Expense Proration
1.4.1.13 Further Payment Batch Enhancements
1.4.1.14 Enh Matching Controls for Finally Closed Purchase Orders
1.4.1.15 Automatic Bank Transmission
1.4.1.16 Mass Additions Create Program
1.4.1.17 Enhanced Separate Remittance Advice
1.4.1.18 iSupplier Portal Invoices
1.4.2.1 1099 Reporting 2002 Changes
27
1.4.2.2 Enhanced Open Items Revaluation Report
1.4.2.3 XML Payment Processing
1.4.2.4 Enhanced Bank Account Identification
1.4.2.5 Price Correction Enhancements
1.4.2.6 Multiple Currency Reports
1.4.2.7 Period Close Exceptions Report
1.4.2.8 XML Invoices
1.4.2.9 Enhanced Control of Prepayments with Automatic Offsets
1.4.2.10 Accounting Events Enhancement
1.4.3.1 Gapless Invoice Numbering for Self-Billing Invoices
Oracle Payables can now automatically assign gapless, sequential invoice numbers to all
self-billing invoices for a supplier site. This feature meets certain country-specific
invoice numbering requirements for invoices created using the ERS feature, the
Automatic Debit Memo from Return to Supplier Transaction feature, and the Retroactive
Pricing of Purchase Orders feature.
1.4.3.2 Invoice Approval Workflow Resubmission Enhancement
Oracle Payables has enhanced the Invoice Approval Workflow feature to automatically
resubmit invoices to the workflow process. An invoice will be resubmitted to the
workflow approval process if the invoice amount is changed after the invoice is
approved, or if the invoice is in the process of being approved.
1.4.3.3 Invoice Validation Concurrent Processing
Oracle Payables can now concurrently process multiple instances of the Invoice
Validation program.
1.4.3.4 UI Enhancements
Oracle Payables improved the invoice and payment windows to streamline transaction
entry and management. These windows are now larger, display more information, have
enhanced functionality, and are more intuitive. Some windows were consolidated so
users can review and manage transactions using fewer windows. The major changes are
as follows:
• The Invoices window has new tabs so without opening additional windows you
can manage holds and scheduled payments, as well as review payments and
prepayments for an invoice.
• The Invoice Gateway window has been renamed to Quick Invoices.
28
• Both the Payments window and Payment Batches window have a new button to
allow you to easily monitor your payment concurrent programs.
• The Payments window has a new Invoices region that displays the invoices paid
by each payment, all in a single window.
1.4.3.5 Supplier Site Contact Enhancements
Users can now record additional details for supplier site contacts in new fields in the
Contact tab of the Supplier Sites window: E-mail, URL, Alternate Phone, and Fax.
1.4.3.6 Supplier Site Attachments
Oracle Payables now supports the attachment of supplemental files at the supplier site
level. This feature's functionality is identical to that currently available at the supplier
level.
1.4.3.7 Supplier Open Interface
Oracle Payables has added new open interface tables and concurrent programs to support
the automated import of supplier records from external sources. This feature offers the
same validations as the Suppliers and Supplier Sites windows.
1.4.3.8 Supplier Bank Account Update Enhancements
Payables has enhanced supplier bank account functionality with the following new
features:
• When a user makes a supplier bank account inactive, Payables can now optionally
replace that account on any unpaid or partially paid scheduled payments with the
supplier's primary bank account.
• A new function controls the display of the Bank Accounts and Supplier
Assignments tabs in the Suppliers and Banks windows. If a user's responsibility
does not have access to this function, then the user cannot see the following:
• Bank Accounts tab in Suppliers window
• Bank Accounts tab in Supplier Sites window
• Supplier Assignments tab in Bank Accounts window
1.4.3.9 Retroactive Pricing of Purchase Orders Support
Oracle Payables supports Oracle Purchasing's new Retroactive Pricing of Purchase
Orders feature. When using this feature, after a Purchasing user updates the price of a
purchase order item, the system creates adjustments in Payables for any existing invoices
matched to that item. The net effect is as if each original invoice had been matched at the
new price.
1.4.3.10 Invoice Attachments in Oracle iSupplier Portal
Suppliers can now attach supplemental files to the invoices they enter in Oracle iSupplier
Portal. Attachments can be any type of supported file, including text files, images, and
video clips.
1.4.3.11 Exclude Tax from Discount Calculation Enhancement
Oracle Payables has extended its discount functionality. The Exclude Tax from Discount
Calculation Payables option previously applied only when taxes were calculated at the
invoice header level. Now this option will also apply when the automatic tax calculation
is at Line or Tax Code level. This feature is limited to unpaid invoices only.
1.4.3.12 Amount Based Matching
Oracle Payables has enhanced matching functionality for services procurement. So that
users can match invoices based on variable rates for services, they can now match based
on an amount only, rather than matching on quantity and price. The self-service invoice
entry capability in Oracle iSupplier Portal has also been enhanced to support this new
29
feature.
1.4.3.13 Bank Account Function Security Enhancements
Three new functions allow you to control each user's access to the three bank account
types; Internal, Customer and Supplier. For example, you can grant a clerk who manages
suppliers full access to supplier bank accounts but deny that user access to customer and
internal bank accounts. These new functions control bank account access in Oracle
Payables windows and reports.
1.4.3.14 Enhanced Purchase Order Number Display in Oracle iSupplier Portal
Oracle Payables has enhanced purchase order number display in Oracle iSupplier Portal.
The order in which purchase orders are displayed has been improved, and the release
number has been added for blanket purchase orders.
1.4.3.15 Enhanced Matching Controls for Oracle iSupplier Portal
Oracle Payables has added a new profile option that prevents suppliers from matching an
invoice to more than one purchase order when they enter invoices online in Oracle
iSupplier Portal.
1.4.3.16 Payables Accounting Entries Program and Report Enhancements
Oracle Payables has improved the Payables Accounting Process so it no longer creates
accounting entries with an error status. Previously the accounting process created an
accounting entry with an error status when the system built an invalid account during
accounting, or when the Validate Accounts program parameter was enabled and a
transaction had an invalid account. Users then needed to provide a valid account for the
accounting entry in the Update Accounting Entries window in Oracle Payables. Now,
when the accounting process identifies an invalid account, the accounting process does
not create accounting entries for the transaction. The details of the transaction are still
listed in the exceptions report, enabling users to always resolve any invalid account
issues before creating accounting entries.
Oracle Payables also enhanced exception reporting in the Payables Accounting Entries
Report. The report has a new exception section that lists all transactions within the
program parameters that could not be accounted.
30
1.5 Oracle Receivables
1.5.1.1 Bills Receivables Balance Assignments
1.5.1.2 Display of Operating Unit Field
1.5.1.3 Require Adjustment Reason
1.5.1.4 Lockbox Invalid Match Reference
1.5.1.5 MRC Inquiry Window
1.5.1.6 Deposit Enhancements
1.5.1.7 Promised Commitment Amounts
1.5.1.8 Balance Segment Profile Option
1.5.1.9 Purchase Cards
1.5.1.10 Prepayments
1.5.1.11 Trade Management Deduction Integration
1.5.1.12 ACH Integration with iPayment (no depend on Receivables)
1.5.1.13 Autoresolution and Split Claim Functionality
1.5.1.14 Attachment Functionality
1.5.1.15 Setup Details Report
1.5.2.1 Credit Management
1.5.2.2 1099 Indicator
1.5.2.3 XML Invoices
1.5.2.4 Party Paying Relationships
31
1.5.2.5 Multiple Reporting Currencies - Report Enhancements
1.5.2.6 Open Items Revaluation Report Enhancement
1.5.2.7 Event Based Revenue Management
1.5.2.8 Multiple Reporting Currencies - Trigger Replacement
1.5.3.1 Allocate Transactional Data to Sales Groups
By leveraging Oracle Resource Manager and utilizing revenue and non-revenue sales
credit assignments, Oracle Receivables now allocates your transactional data to
appropriate sales groups. As a result, you can determine which sales group contributed
more to your company's bottom line. You can also ensure that your sales resources are
allocated efficiently.
You can view sales group information from the Sales Credits window off the
Transactions workbench, as well as from the Revenue Accounting and Sales Credits
window.
If necessary, you can change sales group defaults by manually selecting a fitting sales
group from a list of values, or by using the Revenue Accounting Actions Wizard. You
can also manually adjust sales group assignments that are imported into Oracle
Receivables from Oracle Order Management and Oracle Service Contracts.
1.5.3.2 User Interface Enhancements
Oracle Receivables has improved three major windows to streamline transaction entry
and management. These windows are now larger, display more information, and are
more intuitive. Windows have been conveniently consolidated so users can review and
manage transactions using fewer windows.
The following windows were enhanced;
Transactions
• Transactions Header
• Transactions Lines
• Distributions
• Tax
• Tax Summary
• Freight
• Sales Credits
Receipts
• Receipt Applications
• Receipt Summary
• Quick Cash
• Credit Memo Applications
• Revenue Accounting
32
• Revenue Accounting Form
• Action Results
• Folder Forms
• Find Windows
• Transactions Overview
• Transactions
• Receipts
1.5.3.3 Receipt to Receipt Applications
Receipt-to-Receipt Applications gives users the ability to apply receipts to other open
receipts which have On Account and Unapplied cash. This provides an efficient approach
to settling open cash, by eliminating the need to open multiple receipts to apply to on
account and unapplied cash. From just one receipt, users can apply to open receipts and
the balances and accounting will be automatically updated on all affected receipts. In
addition, Trade Management users gain the ability to apply to receipts that have open
Claim Investigations, which will in turn update amounts, or cancel claims in Trade
Management. This allows users to net underpayments with overpayments in the system,
where it is determined that claim research in Oracle Trade Management is not necessary.
1.5.3.4 Invoice Creation API
With the Invoice Creation API users can now create Invoices directly, in real time,
instead of through a batch.
1.5.3.5 Invoice API Enhancement
In addition to creating Invoices, users now have the ability to create Debit Memo's using
the Invoice API.
1.5.3.6 Leveraging Oracle Approvals Management (AME) in Credit Memo
Workflow
The Credit Memo Workflow has been enhanced with Oracle Approvals Management to
provide more flexible support to your operations, especially those using elaborate
approval chains and multiple currencies.
Oracle Approvals Management allows you to define reusable rules that:
• Ascend the HR supervisory hierarchy in a variety of ways
• Automatically delegate one approver's authority to another approver
• Provide the ability to skip an approver
• Can be future dated allowing automatic rollover to new rules at the appropriate
time.
Other inherent benefits of Oracle Approvals Management include:
• User created exceptions that can be applied to specific approvers or specific types
of transactions
• Automatic currency conversion to your functional currency so that standardized
rules can be used with multiple business scenarios
• The ability to easily insert SQL statements to expand your rules to fit your unique
ways of doing business
The enhanced workflow also includes notification to the collector and sales person of the
final resolution of the credit request.
1.5.3.7 Deposit API
A public API is now available for Oracle Receivables deposit functionality.
33
1.5.3.8 Deductions Management Enhancements
Automatic Claim Creation Through AutoLockbox and QuickCash
If you are integrating with Oracle Marketing Online's Trade Management to track and
resolve claims, then Automatic Claim Creation lets you automatically create claims for
short payments, overpayments, and invalid transactions through AutoLockbox. Using
AutoLockbox, you can create claims in high volume, thus shortening the time to
resolution and reducing the total cost of ownership of deductions management.
Depending on how you run your business, you can choose whether or not you want to
create claims for invalid transactions, credit memos, and negative and positive claims.
In addition, claim functionality has been enhanced to accept and store customer reason
codes through AutoLockbox and in the Receipt Applications window. Using Trade
Management, you can map these reason codes to your organization's internal codes.
Receipt to Receipt Applications
Oracle Trade Management users can now apply short payments or overpayments on
remittances to open claims on other receipts. A Receivables clerk can seamlessly resolve
open cash without the hassle of jumping to various forms.
Receipt Write-off for Underpayments
You can now manually write-off underpayments on receipts. This functionality includes
the ability to set approval limits for write-off amounts at the user and system level. This
can be done in Receivables and from Oracle Trade Management.
1.5.3.9 Multiple Prepayment Types
The Multiple Prepayment Types feature enhances the existing Credit Card Prepayments
functionality to include the collection of prepayments via ACH bank transfer, direct debit
and check. In addition to seamless, out-of-the-box integration with Oracle Order
Management, a public Prepayment API is now available to create prepayment receipts.
Refunding of prepayments can be done directly to a charged credit card or via integration
with Oracle Payables.
1.5.3.10 Bank Account Function Security Enhancements
Oracle Receivables has strengthened internal controls by extending function security to
the Bank Account Setup window. You can now control user access based on internal,
customer, and supplier bank account types.
1.5.3.11 Enhanced Returns, Cancellations, and other Credit Activities
Automated Receipt Handling for Credits
When credits are due to a customer, you must decide whether to refund associated
payments or use the cash to reduce other outstanding items on the customer's account. To
handle such situations promptly and efficiently, use the new Automated Receipts
Handling for Credits feature. You can set the receipt handling policy to automatically
refund credit card payments, or apply receipts to on-account cash.
When refunding, some credits require careful investigation before funds are returned to
the customer. Oracle Receivables recognizes when user intervention is required and
automatically places questionable items on account. Depending on the outcome of the
investigation, you can then initiate the refund or choose another receipt application.
You can also set your enterprise's credit card refund minimum. Amounts less than the
minimum are placed on account, letting you manage these receipts according to your
business practices.
1.5.3.12 Customer Credit Classifications
34
If customer credit standing directly impacts your business relationship with your
customers, you can use the Customer Credit Classification feature to assign and maintain
credit classifications at the customer account level. Credit classifications can be managed
using customer profile classes. Each customer within a customer profile class inherits the
credit classification of the group.
Note: If you use Oracle Credit Management, assignment and maintenance of credit
classifications in Oracle Receivables is controlled by Credit Management.
1.5.3.13 Deposit Application
Applying customer deposits to their purchases has been made more flexible. At the time
of a customer order, deposit information may not be recorded on the order. The user will
now be able to add the deposit information after the invoice is generated. A deposit can
be added to any open invoice, including invoices that have been partially paid or
credited.
1.5.3.14 GL Transfer Program Controls for Business Users
GL Transfer Program Controls offer business users the convenience of scheduling GL
Transfer Program run times and the ability to easily correct invalid GL accounts
uncovered during the GL Post process. The Correct Invalid GL Accounts form lets users
perform mass and/or individual updates to invalid GL accounts. Enhancements to the
Unposted Items Report help to identify transactions that require modification.
35
2. Logistics
2.1 Oracle Inventory Management

2.1.1.1 Intercompany Invoicing with Advanced Pricing
2.1.1.2 Material Workbench
2.1.1.3 Movement Statistics Release Number Display
2.1.1.4 Movement Statistics Reference Period
2.1.1.5 Movement Statistics Data Export Concurrent Program
2.1.1.6 Greek Inventory Trial Balance Report
2.1.1.7 Safety Stocks by Project
2.1.1.8 Large Org - Organization Hierarchy LOV Performance Enh
2.1.1.9 Tax Registration Number
2.1.1.10 Greek Inventory Analytical Ledger Report
2.1.1.11 Movement Statistics Ignore Record
2.1.1.12 New Inventory Item Definition form
2.1.1.13 Vendor Managed Inventory
2.1.2.1 Pick Methodologies for WIP
2.1.2.2 OSFM Lot API
2.1.2.3 Greek Reports
2.1.2.4 Vendor Managed Inventory (VMI)
36
2.1.2.5 MinMax Move Order Enhancements
2.1.2.6 Move Order Fill-Kill
2.1.2.7 Serial Number Uniqueness by Model Item (ER 2112615)
2.1.2.8 Consigned Inventory from Supplier
2.1.2.9 Serial Tracking in WIP with Genealogy
2.1.2.10 OSFM Kanban Support
2.1.3.1 Component Picking Enhancements
Attributes of the job, such as quantity increase, or component deletion, may change after
an associated component pick task was created. These changes may impact the pick task.
This project addresses many types of job changes, and synchronizes these to the
associated task. For example: a job status change, a job quantity increase, and a
component supply type change. Other changes may trigger a warning message to the
user.
For more details on this feature please see the associated section in the Discrete
Manufacturing RCD.
2.1.3.2 Consigned Inventory Diagnostics
When you agree toB consume and pay forB materials held on consignment, you must
ensure that all required setups are performed so that automatic transactions can take place
without fail. Diagnostic capabilities have been added toB ensure that consumption of
consigned materialsB can beB performed on demand andB thatB billing documentsB can
beB createdB without delay.B Notifications indicating the nature of errors and remedial
actions can be sent automatically when the diagnostic programs are executed.
In addition, the view material transactions form has been enhanced to allow users to
query the consumption advice status of consumed materials.
2.1.3.3 PAR Replenishment Counts
PAR (Periodic Automated Replenishment) Level Counting addresses the needs of
facilities which do not store perpetual inventory levels, but still require locator level
replenishment to specific stock level targets. This practice is common in the
replenishment of supplies stores within hospitals and healthcare organizations.
This feature extends existing Replenishment Count capabilities to allow users to perform
locator level stock counting in non quantity tracked subinventories and for the system to
generate the appropriate replenishment document (Internal Requisition, Purchase Order
Requisition or Move Order) based on the item's sourcing for that subinventory if the
stock level has fallen below the target on hand for the locator.
Mobile user interfaces have also been provided for Replenishment Count entry and
changes have been made to the move order pick slip report to honor the Pick Slip
Grouping rules when printing pick slips to facilitate the intra organization transfer of
material to replenish these locations.
37
2.1.3.4 Allocation Delete at Move Order Cancel (CU1)
2.1.3.5 Cross-Organization Serial Genealogy Inquiry (CU1)
2.1.3.6 Aging Based Consumption of Consigned Inventory
In some consignment arrangements with suppliers, you are required toB purchase
materialsB held in consigned stockB past anB agreed uponB duration of time.B Aging
based consumption facilitates the purchase of consigned materials by allowing users to
identifyB the items whose consignment status is nearing or past due for purchase
according to limits established in the Approved Supplier List.B This information is
available to internal users through a new inventory menu, and to suppliers through the
iSupplier Portal and can be exported at any time to support period end financial
reporting.
2.1.3.7 ERES Support for 21 CFR Part 11 Compliance
Validating the compliance of operating environments in accordance with the FDA's 21
CFR Part 11 is of high importance to Medical Devices Manufacturers and Life Science
industries. By incorporating tools within the Oracle E-Business Suite to maintain cGMP/
QSR critical records electronically, customers are able to meet compliance requirements,
while maintaining operational efficiency.
With this release, Oracle Inventory has extended the support for Electronic Records and
Electronic Signatures to miscellaneous transactions. Based on user defined setup
parameters, the system may prompt a user for an electronic signature while performing
Account Alias Receipts and Issues and Miscellaneous Receipt and Issue transactions in
Oracle Inventory. When viewing transactional history in the lot or serial genealogy
forms, Oracle Inventory can display the Electronic Record generated for those
transactions. For more information on this functionality, please refer to the Oracle
Quality section of the Release Content Document.
2.1.3.8 Enhanced Inter-company Transactions
Many large corporations operate a diverse set of organizations and operating units and
perform procurement and sales transactions across those entities. Any given transaction
may impact several organizations and operating units and require a complex sequence of
linked accounting entries. Without proper system support, this can be a costly and error
prone process.
With this release, Oracle Inventory has enhanced its inter-company invoicing to support
these global fulfillment and procurement business flows. This new functionality
supports:
• Shared Procurement Services: If a PO is placed by an operating unit (OU) that is
different from the material destination OU, then the procurement OU can invoice
that receiving OU. The invoice can be done at either the PO price or the transfer
price, and accounting is done to represent a transfer of ownership between the
OU's. For more information on Shared Procurement Services, please refer to the
Purchasing section of the Procurement Family Pack RCD.
• Ownership Transfer during sales order shipments: When doing a sales order
shipment from an OU that is different from the OU on the sales order, users can
now generate accounting which represents a transfer of ownership from the
shipping OU and the selling OU, rather then just a pure invoice. In this case, the
inter-company invoice is always done at transfer price.
• Drop Ship Across Sets of Books: On a drop ship sales order, you must specify the
38
warehouse (Org) that owns the fulfillment of the order. In this release, this Org
can be in a different set of books, and the purchasing can be done through a
shared procurement center. Invoicing and accounting are done as described above.
For more information on Drop Ship Across Sets of Books, please refer to the
Order Management RCD.
• Chains of inter-company relationships: In all of the above cases, users can define
a chain of OU's through which ownership must pass when transacting between a
selling and shipping OU, or between a procuring and receiving OU.
Inter-company invoices are generated between all OU's, and accounting is done to
represent and ownership transfer between all OU's in the chain.
New inventory transactions have been created that do not generate material movements
but are used for invoicing and accounting purposes.
2.1.3.9 Item Master Changes
For information on the changes being made in Inventory Items, Categories, Catalogs and
other item maintenance features, please refer to Bill of Materials/Items section of this
document.
2.1.3.10 Movement Statistics Exception Report
The movement statistics exception report has been modified to summarize validation
errors and to provide instructions for resolving these errors, facilitating the completion of
INTRASTAT declarations in the European Union.
2.1.3.11 Outbound Flow Sequence
The Pull Sequences setup definition for Kanban cards has been enhanced to support
outbound flow sequencing. For more information on this feature, please refer to the Flow
Manufacturing section of this document.
39
3. Manufacturing
3.1 Oracle Bills of Material

3.1.1.1 Manufacturing Routing Management
Import network Routings
You can import Network routings through the Routing Business Object API.
Attributes on Resource Entity
You can enter a supply subinventory and locator for a machine resource. If the routing
does not specify a supply subinventory or locator they can be derived from the resource.
Alternate Resources on Standard Operations
You can define alternate resources for a standard operation.
Substitute Group Requirement for Resources
You can group resources by substitute group numbers. Resources with the same
substitute group number can be considered substitutes for each other. Schedule sequence
number only determines which resources are simultaneous.
Electronic Records and Electronic Signatures (ERES) Support in Routing Module
for 21 CFR Part 11 Compliance
For more information on this functionality, please refer to the Oracle Quality section of
the Release Content Document
3.1.1.2 Manufacturing BOM Management
Direct Item Components
You can add direct item components to an Asset BOM. A 'Direct Item' can be any of the
following:
• A non-stockable item. These are also called "Planned Direct Items"
• An item from the supplier catalog that does not reside in the Item Master
• An item that is created on the fly during work order execution and added to the
work order, procured, and delivered to the point of use.
Certain business practices like Asset Maintenance require that a BOM be able to hold
components that are non-inventory items or direct items. Such items could be one-time
items, which may not be inventoried and are directly delivered to the shop floor.
Increase maximum # of components
Increases the number of components at any level of a BOM from 9999 to 9,999,999. You
can have up to 60 levels in a BOM.
Configuration BOM Allowed Organization Parameter
An organization level BOM parameter to control whether configuration BOMs can be
created in a organization.
Lead Time Program Changes
Today when you compute the cumulative manufacturing and the cumulative total lead
times for an item, the calculation includes all options in a model, resulting in inflated
40
lead times.
You should be able to enter the lead time for the models and option classes used for
forecast consumption and not have them overwritten when the calculate lead times
program is executed.
A new parameter at the organization level is available "Include model/option class item
in lead time rollup". The default value for this parameter is unchecked, meaning by
default that the cumulative lead time calculations are not performed for Model/Option
classes
Item Delete Business Event in Delete Group
Successful deletion of Item or an error during deletion of an item is an event of interest
for internal and external systems. Delete Groups today handles the deletion of Item by
performing various constraint checks before the item is physically deleted. A Success or
Failure Business Event will now be raised for any application to subscribe to.
Electronic Records and Electronic Signatures (ERES) Support in BOM Module for
21 CFR Part 11 Compliance
the Release Content Document.
3.1.1.3 EBS Item Master
APS Item Attributes
Several new item attributes are added to the item master to support Oracle Advanced
Planning and Scheduling features for 11i10. Please refer to the 11i10 APS RCD -
Advanced Supply Chain Planning for details on these features. Below are descriptions of
the new features followed by a list of the new or modified APS related item attributes:
VMI Planning Engine - Oracle currently enables Vendor Managed Inventory (VMI)
with suppliers. The customer - who has implemented Oracle - sets up the Approved
Supplier List (ASL) with the min-max values, sets up a blanket purchase agreement, runs
the VMI planning engine, and generates purchase release and notifies suppliers.
Suppliers respond by shipping material. There also exists a need whereby the supplier
monitors and replenishes inventory at a customer site, instead of the customer doing so
and requesting inventory.
• Add the choice "Vendor Managed" to the Inventory Planning Method drop down
• Minimum quantity in UOM
• Minimum days of supply
• Maximum quantity in UOM
• Maximum days of supply
• Fixed Order Quantity
• Release Authorization Required
• Consigned
• Auto-expire ASN
• Forecast Type for Average Daily Demand Calculation
• Horizon for Average Daily Usage Calculation
• Start and end dates for 'superseded' item relationship
• Planning Enabled
Distribution Requirements Planning - Distribution Requirements Planning (referred to
as DRP) is a new planning method. DRP uses the same demands, supplies and cost data
41
as MPP/MPS & MRP plans. However DRP can be used as demand schedules for
MPP/MPS/MRP plans. An item can be specified as being DRP planned in which case,
we need to specify the target & Maximum Inventory Levels and their replenishment
windows.
It is often desirable to master schedule end items only with respect to their critical
components and their associated bottleneck resources. Certain customers want to run two
separate plans, one to schedule their primary production quantities and the other to
schedule all related parts and subassemblies. You will be able to flag MRP planned items
as critical components for MPS and DRP planning. This will allow you to plan master
scheduled items with respect to only critical components and their material and resource
constraints.
• Exclude From Budget
• Target Inventory Level Days of Supply
• Target Inventory Level Calculation Window
• Maximum Inventory Level Days of Supply
• Maximum Inventory Level Calculation Window
• DRP Planned
• Critical Component
• For the attribute, Planning Method: change the LOV to the following values:
• Not Planned
• MRP Planning
• MPS Planning
• MRP/MPP Planned
• MPS/ MPP Planned
• MPP Planned
• Oracle ASCP will allow users to model Minimum Transfer Quantities (MTQ)
between operations and organizations. This implies that a downstream operation
of a routing in one organization can start after completion of MTQ at the upstream
operation of another routing in a different organization.
These MTQ can be modeled with respect to convergence or divergence of supplies. In
case of divergence, supply from one upstream process splits into 2 or more downstream
processes of the same item. In case of convergence, supplies from 2 or more upstream
processes of the same item are consumed by one downstream process.
If an item A in Org 1 is used to make Item B in Org2 and both items are Make Items,
then there is either a continuous processing of Item A in the manufacturing process of
Item B or a discrete transfer. If discrete transfers, then supply quantities can be fed to org
2 at regular intervals or at the start of the operation. These values are captured in the
Master Items and Organization Item levels.
• Continuous Inter Organization transfers
• Convergent Supply Consumption Pattern
• Divergent Supply Feeding Pattern
• Catchweight attributes
Some industries require capturing an additional quantity at the time of ship confirmation
for the purposes of pricing and invoicing, but do not require that on-hand balances be
maintained in this additional unit-of-measure. A common usage might be to sell and
track product using a standard unit such as EACH, with an approximate weight and
42
nominal list price based on the average weight for that unit. However the actual billed
price would be computed on a "price per pound" basis, using the actual weight of the
shipped item. Because the actual weight of each unit varies, standard unit-of-measure
conversions cannot be used. Instead the weight must be captured during the picking and
shipping flow. This weight is then used to re-compute the price at shipping.
The Dual Control attribute is split into "Tracking", "Pricing", and "Defaulting" attributes
to support the catchweight feature in 11i10.
OM integration with HTML
You can use the HTML based item search when creating orders. Items are restricted to
only those that are sellable.
UCC -128 Support for WMS
Two new columns, 'Unit of Measure' and 'Revision', were added to the
MTL_CROSS_REFERENCE table to support item cross-references for GTIN codes.
GTIN is a global identifier for an item and its packaging configuration that is common to
vendors, retailers etc. For example 12-can pack of Pepsi has a unique GTIN number and
24-can pack has a different GTIN number. In 11i9, customers can track the GTIN
number using existing cross-references functionality. In 11i10, WMS can track the UOM
used in the packaging configuration as well as the revision of the item (if the item is
under revision control).
VMI /Consigned item attributes
You cannot update one of the following item attributes if an ASL exists with the VMI
enabled flag or with the Consigned flag checked:
• Outside Processing Item from No to Yes
• Asset Item Type from null to a non null value
• Transactable from Yes to No
• Stockable from Yes to No
A new message is defined with the following text: "You cannot update this attribute
because this item is enabled for either VMI or Consigned Inventory. Please review the
Approved Supplier List entries for this item."
This message is displayed to the user in the Item Definition form, returned to the calling
program by the item API, or stamped on the error record by the Item Open Interface
import program. This applies to updates executed through:
• The Item Definition form;
• The Item Open Interface;
• The Item API;
• Service Item Attributes
Improves the UI layout of the Service item attributes and added some more validation
rules to ensure the correct setup of Service related attributes. Two attributes are renamed:
Serviceable Product [Symbol_Wingdings_224] Enable Contract Coverage, Asset
Creation [Symbol_Wingdings_224] Create Asset.
CTO Related Item Attributes
Two new CTO related item attributes are added. See the descriptions below:
• Added a new "Option Dependent Sourcing" non-visible attribute in the items
table. This new, non-visible attribute on a configured item indicates that its
43
sourcing is option dependent. This attribute is controlled at the item master level.
It is set by CTO when a configuration item is created, or when an item is
pre-configured having option dependent sourcing. It is not visible in the Item
form, as users are not able to update this field.
• Added Autocreated Configuration Item checkbox on items form to change an
autocreated item to a preconfigured item.
• Electronic Records and Electronic Signatures (ERES) Support in Item
Module for 21 CFR Part 11 Compliance
44
3.2 Oracle Cost Management
3.2.1.1 Transfer Inv Price Variance for Maint Work Orders (eAM)
3.2.1.2 Enforce Integer Requirements flag for ASCP (BOM)
3.2.1.3 Work in Process Value Report for Shop Floor Management
3.2.1.4 New Item Attributes (Items)
3.2.1.5 Enhancements to Item Relationships (Items)
3.2.1.6 Enhanced Cost Import
3.2.1.7 Rule Based Material Overhead Absorption
3.2.1.8 Non Std Expense Work Orders Support for Shop Floor Mgmt
3.2.1.9 Opt Estimated Scrap Acctg Support for Shop Floor Mgmt
3.2.1.10 Transfer to Mfg. Copy to Mfg. Proc integ w/ ECO (ENG)
3.2.1.11 End-Item Subst Item Wrkbench w/DataEntry enab Fldr-Items
3.2.1.12 Enhanced Supply Chain Rollup
3.2.1.13 Category Grants (Items)
3.2.2.1 Enhancements to Routing
3.2.2.2 Set Cost Controls
3.2.2.3 Enhancements to BOM
3.2.2.4 Enhance Support for Consigned Inventory from Supplier
3.2.2.5 Item Workbench with a Data Entry enabled Folder (Items)
3.2.2.6 Transfer Pricing Costing and Accounting
45
3.2.2.7 Enh WIP Lot Transaction Costing for Lot Based Work Orders
3.2.2.8 FIFO/LIFO Layer Cost Management
3.2.2.9 Periodic Costing Acquisition Cost Adjustments
3.2.2.10 Enhanced Costing of Asset Maintenance
3.2.3.1 Support for Retroactive Price Changes
Cost Management supports Retroactive Price Changes (See Purchasing in the
Procurement Family). Retroactive Price Changes automatically create adjustments to
Accounts Payable Accruals and Encumbrance Reversal for the effected receipts. The
Retroactive Price Variance account holds the difference between the original price and
the revised price.
3.2.3.2 Support for Direct Labor Purchase Order for Maintenance Work Orders
Cost Management supports the direct shop floor delivery of labor charges and equipment
charges. You can include labor and equipment charges on a purchase order for
maintenance work orders. Cost Management includes these charges on the estimate for
the work order, and charges the work order upon delivery of these services. You can
view these charges by work order or by maintained asset. (See Enterprise Asset
Maintenance -- Direct Purchases Charged to Appropriate Cost Categories.)
3.2.3.3 Support for Enhance Intercompany
In this release, Oracle Inventory has introduced Enhance Intercompany transactions to
support Drop Shipment across Sets of Books, Shared Procurement Services, and
Ownership Transfer during sales order shipments across operating units. Oracle Cost
Management costs and performs the accounting for both the physical and financial flows.
See Enhanced Intercompany in the Inventory RCD for more information on this project
and its significance to global corporations. Caret
3.2.3.4 Enhanced Period Close Summarization
You can run the Period Close separately from the Periodic Close Summarization. This
separation speeds the closing process.
3.2.3.5 Increased Flexibility for Charges to Maintenance Work Orders
You can choose whether or not to charge items from expense subinventories to
maintenance work orders based on your business practices. If you choose to charge these
items, Cost Management will credit the subinventory's expense account. You can use
both methods for different classes of maintenance work orders. (See Enterprise Asset
Maintenance -- Issue/Return of Rebuildable Items.)
3.2.3.6 Supply Chain Cost Rollups with Dynamic Lot Size
The Supply Chain Rollup includes the ability to change the standard lot size by the
multiplier you choose. You can simulate changes in lot sizes to analyze their impact on
costs.
3.2.3.7 Support for Linking of Maintenance Work Orders
Using Parent and Child Work Order Relationships, you can view Work Order Cost by
46
Parent-Child Work Order Hierarchy. (See Enterprise Asset Maintenance - Work Order
Linking -- Work Order Costing.)
3.2.3.8 Support for Global Procurement in a Shared Services Environment
Cost Management supports Global Procurement in a Shared Services Environment (See
Purchasing in the Procurement Family).
47
3.3 Oracle Engineering
3.3.1.1 MLS support for Change types
MLS support for Change types. You can setup change types in multiple languages. Caret
3.3.1.2 ERES Support in Eng Module for 21 CFR Part 11 Compliance
3.3.1.3 Increase change type name length
Increased the change type name from 10 characters to 80 characters.
48
3.4 Oracle Quality
3.4.1.1 Quality support for PJM in Mobile Supply Chain Apps (MSCA)
3.4.1.2 Flow Workstation Integration
3.4.1.3 Enabling Long Comments as New Collec Element Data Type
3.4.1.4 New Collection Element and Trigger: TCA Party
3.4.1.5 Skip Lot Inspection WMS/MSCA Inbound Receiving Integ
3.4.1.6 Receiving Insp Sampling WMS/MSCA Inbound Receiv Integ
3.4.1.7 Multi-Lingual Support (MLS) for Quality
3.4.1.8 Parent-Child Collection Plans
3.4.1.9 New Collection Trigger: PO Routing Name in Receiv Txn Int
3.4.1.10 Order/Line-Specific Specifications and Samples
3.4.1.11 Folders Facility in Enter/Update Quality Results
3.4.1.12 Automatic Sequence Generation In Collection Elements
3.4.1.13 Quality support for PJM in Warehouse Mgmt System (WMS)
3.4.1.14 Quality Specification Matching Inquiry in Order Manageme
3.4.1.15 WMS User-initiated Quality Check
3.4.1.16 MSCA / Quality Inbound Receiving Integration
3.4.2.1 Quality Plans at Maintenance Operation Completion
3.4.2.2 UOM Conversion at Specification Element Level
3.4.2.3 Support WIP Serial Tracking
49
3.4.2.4 Route Completion Transaction Flow
3.4.2.5 Support Global Specifications
3.4.2.6 Mobile LOV Enhancement project
3.4.2.7 Add Scrap Account and Item Revision as Collection Trigger
3.4.2.8 Job Deferral Transaction Flow
3.4.2.9 Corrective Actions Tracking
3.4.2.10 MRB Dispositions
3.4.2.11 Support for Mobile Move Complete, Return and Move, Txn
3.4.2.12 New Quality Actions to Create Work Order
3.4.2.13 Extend Specification Support for Range of Categories
3.4.2.14 Installed Base Svc Support - new collec elements trigg
3.4.2.15 Maintenance Operation Completion Transaction Flow
3.4.2.16 Nonconformance Management
3.4.2.17 Incr Spec Element Collec Element for Dec Precision up to
3.4.2.18 MRB Disposition Transaction Flow
3.4.3.1 ERES Support in Item, BOM and Engineering Modules
Title 21, Part 820 of the Code of Federal Regulations lists the "Quality System
Regulation" which is applicable to the Medical Device Manufacturers. Subpart C
(820.30) describes the "Design Controls' that needs to be implemented as part of the
Quality System of the device manufacturer. The business processes that are governed by
this subpart of the regulation includes - Design and Development Planning, Design Input
and Design Output, Design Review, Design Verification, Design Validation, Design
Transfer (Transfer to Manufacturing), Design History and Design Changes.
Based on the above:
• During the design or engineering phase all items, bills and routings that are
50
defined in the Engineering module are captured as E-records. These events in
Oracle Applications are the design activities that are critical steps in the
documentation of the medical device to be manufactured.
• When a medical device is ready to be transitioned from the design phase to
manufacturing, an Engineering Change Order (ECO) shall be submitted. Only the
ECO approval workflow will be captured as E-Record and E-Signature events.
This provides a snapshot of the entire ECO at the point in time it is approved.
In 11i10, - the ERES transactions that are supported: Table Heading: entry cannot be
inserted.
Engineering Module:
Event eRec eSig Form/Navigation Description
ECO Creation Yes No Engineering -> These two events
ECO Update ECOs provide mechanism
to capture an
eRecord for any
ECO change.
ECO Approval Yes Yes - Deferred ECO Approval Must use this
Workflow workflow to obtain
eSignature when
approvals for
revising items,
revising bill and
routing during
design and
development and
transferring product
from engineering to
manufacturing.
ECO Yes No Engineering -> The ECO
Implementation ECOs -> Tools > implementation
Implement event invokes events
for actual changes
such as Bill Update,
Routing Update,
Transfer To
Manufacturing, etc.
that run in the
background.
ECO Schedule Yes No Engineering -> Captures the ECO
ECOs -> Tools > schedule date and
Schedule comments with the
ECO contents.
ECO Reschedule Yes No Engineering ->
ECOs -> Tools >
Reschedule
ECO Cancellation Yes No Engineering ->
ECOs -> Tools>
Cancel
Transfer to Yes Yes - Online Engineering > Online e-signature is
Manufacturing Prototypes > captured for
Transfer To form/navigation # 1,
Manufacturing #2 , #3 and #4.
Engineering -> For #5, the ECO
Prototypes > Items > approval captures the
Master/Organization e-signature.
Items > Tools ->
Engineering Transfer
Engineering >
Prototypes >Bills >
51
Tools > Transfer Bill
Engineering >
Prototypes >
Routings > Tools >
Transfer Routing
Through ECO
Approval and
Implementation
Copy to Yes Yes - Online Engineering >
Manufacturing Prototypes > Copy to
Manufacturing form
Items Module:
Item Creation Yes Yes - Online Inventory -> Items Create an item or
Item Update -> Master Items to make changes to an
create/update existing item.
manufacturing item
Engineering ->
Prototypes -> Items
-> Master Items to
create/update
engineering items
Item Organization Yes Yes - Online Inventory -> Items When an item is
Assignment -> Master Items > assigned to an
Tools > Organization organization(s), the
Assignment for online e-signature
manufacturing items captures the
Engineering -> organization
Prototypes -> Items assignment and, in
-> Master Items > the background, an
Organization e-record is created
Assignment to create by the item creation
engineering items event.
Item Revision Yes Yes - Online Inventory -> Items If the Master Items
Entry -> form is invoked from
Master/Organization the Inventory menu,
Items > Tools > the item revision is
Revisions for a manufacturing
Engineering -> item.
Prototypes -> Items If the form is
-> invoked from the
Master/Organization Engineering menu,
Items > Tools > the item revision is
Revisions for an engineering
item.
Item Cross Yes No Inventory >Items> Item Cross
Reference Entry Master/Organization Reference defines
Items > Tools > the references of
Cross -References inventory items to
supplier items,
manufacturing items,
items used to keep
labeling information,
etc.
BOM/ Routing Modules:
Bill Creation Yes Yes-Online for Bills Bill of Materials > The ECO Approval
Bill Update created / updated Bills > Bills collects the
through the bills Engineering > e-signatures and the
form Prototypes > Bills > bill creation/update
52
No for bills created Bills is captured as an
or updated by ECO e-Record in the
implementation background
No for engineering The e-signature is
bills that are captured as part of
transferred or copied the Transfer to
to manufacturing Manufacturing or
Copy to
Manufacturing
event.
Routing Creation Yes Yes-Online for Bill of Materials > The ECO Approval
Routing Update Routings created / Routings > Routings collects the
updated through the Engineering -> e-signatures and the
routings form Prototypes -> routing
No for routings Routings > Routings creation/update is
created or updated captured as an
by ECO e-record in the
implementation background.
No for engineering The e-signature is
routings that are captured as part of
transferred or copied the Transfer to
to manufacturing Manufacturing or
Copy to
Manufacturing event
Mass Change Bills Yes Yes-Online Engineering -> The Mass Change
ECOs -> Mass Bills event invokes
Changes the Bill Update event
Bill of Materials > (e-record only) for
Bills > Mass each impacted bill.
Changes
3.4.3.2 UI Enh: Read Only Collection Element
Users can now setup Collection Elements and setup Collection Plans to allow an
administrator to define a particular collection element to be read-only. This enhancement
allows an assign-a-value action target to be readable by the user in the Quality
Workbench and forms, but not changeable by the user. When an element is read-only it
can still be populated by default values and assign-a-value actions -- but cannot be
changed.
The following list describes characteristics of the Read Only attribute.
1. The Read Only attribute of a collection element enables a user to view the element's
value, but disallows any manual direct update by the user.
2. Values for the read-only collection elements can be assigned using assign-a-value
actions that can be fired upon satisfying a set of conditions, default values, etc.
3. Pre-existing collection elements have an editable/updateable Read Only attribute for
backward compatibility.
4. This is supported both in Quality Workbench and Forms UIs.
3.4.3.3 UI Enh: Date and Time Support
Date and Time - Data Type
Our users have frequently requested a date and time collection element. With the Date
and Time project we have created a new data type to support this project and the
enhancement requests. This new Date and Time type requires that both the date and time
be entered during collections and stored in system.
Elements Affected by the Data Type Change
There are thirteen Collection elements in Oracle Quality that have been changed to the
53
new data type. These elements previously stored only dates and now store both the date
and time. Data entered previously to the upgrade only displays the date.
The following elements have been changed to the Date and Time data type:
Transaction Date Approval Date Follow up Date Date Opened Date Closed Start Date
End Date Date Required Expected Receipt Date BOM Date BOM Routing Date Actual
Resolution Date Expected Resolution Date
3.4.3.4 PO - Receiving Enh: Centralized Receiving Functions for WMS
Quality now supports a mixed platform receiving, i.e. the ability to create receipt on the
mobile WMS platform, perform an inspection using desktop application for Quality and
finally deliver using mobile WMS. This mixed platform supports provide users a much
more flexible system and allows WMS users to fully utilize Quality's desktop features.
Quality also supports the receiving transactions for lot and serialized items and LPN
based transactions, using desktop forms and the Receiving Open Interface is generic
enough for all e-business customers and should not be limited to only customers using
the WMS product.
3.4.3.5 PO - Receiving Enh: Receiving Time Stamp Support
Quality supports a change in Purchasing/Receiving to record the time that a transaction
happens. Receiving transactions including receipt creation, receiving, inspection, transfer
and delivery transactions support the date timestamp feature. Time information is
captured together with date information and is available for quality collection. . Since
Quality is the major platform for receiving inspection, it's important that Quality support
the timestamp for the Transaction Date element, which is used for the inspection date.
3.4.3.6 Guaranteed by Manufacturer Results (Enhancement #3763419) (CU1)
3.4.3.7 Samples and Results Screen Expansions (Enhancement #3676133) (CU1)
3.4.3.8 EAM Integration with Rebuild Work Orders
Quality integration with eAM is enhanced to support Rebuild Work Orders. This means
the elements: Asset Group, Asset Number and Asset Activity are extended to support
Rebuild Item, Rebuild Serial Number and Rebuild Activity. The quality data collection
during eAM Maintenance Work Order Completion, eAM Maintenance Operation
Completion and eAM Asset Query also support Rebuild Work Orders and Rebuild Items.
The Create Maintenance Work Request and Create Maintenance Work Order quality
actions are also enhanced to support Rebuild Items.
3.4.3.9 ERES Support in Quality Module
The basic business needs are to obtain approval of quality specifications, quality results
and collection plan definitions that are created or updated, and provide timestamps for
these events. As an example, the quality records that would qualify to have signatures
enabled are specifications used in inspection activities (receiving, in-process, finished
goods) that would determine the acceptance status for that medical device and determine
its ability to meet its intended use. Also, the record (signature) for the approval must be
maintained in the system, so that it is available for inquiry purposes.
The sections of the FDA Quality System regulations - 21CFR820, which are applicable
to the Quality module, are:
• 820.70 - Production and Process Controls
• 820.75 - Process Validation
•
54
820.80 - Receiving, in-process and finished device acceptance
• 820.86 - Acceptance Status
• 820.90 - Nonconforming Product
• 820.100 - Corrective and Preventive Action
Where appropriate, the translation of the 21CFR820 requirements, in combination with
21CFR11 requirements would define the scope of the business events in Quality that
needs to be Part 11 compliant.
Per section - 820.70 Production and Process Controls and 820.75 - Process Validation,
each manufacturer shall develop, conduct, control and monitor production process to
ensure that a device confirms to its specifications. The process controls include but not
limited to, documented instructions, standard operating procedures (SOPs), and methods
that define and control production, monitoring and control of process parameters and
component and device characteristics during production, approval of process equipment,
and criteria for workmanship. Some of these activities such as monitoring parameters of
equipment during production can be modeled as quality collection plans and data
collected for the same.
Per section - 820.80 Receiving In-process and Finished Device Acceptance and 820.86 -
Acceptance Status , each manufacturer shall establish and maintain acceptance
procedures to ensure that specified requirements for in-process product are met and
in-process product is controlled until the required inspection and tests or other
verification activities have been completed and/or necessary approvals are obtained. All
in-process acceptance activities must be documented.
Similarly, final acceptance activities are critical. Adequate procedures are required for
finished device inspection to ensure that each production run, lot, or batch of finished
devices meets acceptance criteria. Acceptance activities must be documented. Also, each
manufacturer is required to identify by suitable means the acceptance status of product,
to indicate the conformance or nonconformance of product with acceptance criteria.
The device acceptance activities can be modeled in Oracle Quality using quality
specifications, collection plans and results collected for these activities.
Per section - 820.90 - Nonconforming Product , it is required for manufacturers to
establish and maintain procedures to control products that do not conform to specified
requirements. The procedures shall address the identification, documentation, evaluation,
segregation, and disposition of nonconforming product. The evaluation of
nonconformance shall include a determination of the need for an investigation and
notification of the persons or organizations responsible for the nonconformance. The
evaluation and any investigation shall be documented. Enabling Electronic Records and
Electronic Signatures can meet these requirements from the regulations for the
Nonconformance and Disposition solution introduced in 11i9.
Per section 820.100 - Corrective and Preventive Action , it is required for manufacturers
to establish and maintain procedures for implementing corrective and preventive action
with the supporting documentation. Enabling Electronic Records and Electronic
Signatures can meet these requirements from the regulations for the Corrective Action
solution introduced in 11i9.
In 11i10, - the Quality transactions that are supported with ERES:
Collection Element Yes No Quality > Setup > To model hints &
Creation Collection Elements instructions.
Collection Element
Update
55
Collection Plan Yes Yes - Online Quality > Setup > Conditions under
Creation Collection Plans which you collect
Collection Plan quality data, and
Update enable transactional
collection.
Specification Yes Yes - Deferred Quality > Setup > Item and Test
Creation Specifications Specifications.
Specification Org Yes Yes - Online Quality > Setup > Item and Test
Assignment Specifications Specifications.
Specification Yes Yes - Online Quality > Setup >
Update Specifications
Quality Result Yes Yes - Online Quality > Results > Multiple applications
Creation Enter Quality possible with this,
Results for e.g. inspection
results, test results
etc.
Quality Result Yes Yes - Online Quality > Results > Update to the
Update Update Quality previously entered
Results quality results
Nonconformance Yes No Quality > To report a
Creation Nonconformances > nonconformance
Enter found during
Nonconformances inspection or other
quality activities
Nonconformance Yes No Quality > To track
Update Nonconformances > nonconformance
Update status e.g. Closing.
Nonconformances
Nonconformance Yes Yes - Deferred Quality > Use this event if a
Master Approval Nonconformances formal signature
Nonconformance >Enter/Update needs to be obtained
Detail Approval Nonconformances for a
nonconformance
prior to deciding on
the disposition.
Disposition Yes No Quality > To initiate a
Creation Dispositions > Enter disposition resulting
Dispositions from a
nonconformance.
Disposition Update Yes No Quality > To track disposition
Dispositions > status, e.g.
Update Dispositions Completion of
Rework.
Disposition Header Yes Yes - Deferred Quality > Use this event if a
Approval Dispositions > formal signature
Disposition Detail Enter/Update needs to be obtained
Approval Dispositions for the execution of a
disposition, e.g.
rework, scrap, etc.
Corrective Action Yes No Quality > Corrective Submits a corrective
Creation Action > Enter action request.
Corrective Action
Request
Corrective Action Yes No Quality > Corrective Use to track root
Update Action > Update cause, closing CAR
Corrective Action etc.
Request
Corrective Action Yes Yes - Deferred Quality > Corrective Use to obtain
Request Approval Action > Enter approval of the
/Update Corrective submitted corrective
Action Request action request.
Corrective Action Yes Yes - Deferred Quality > Corrective Separate approvals
56
Approval Action > are possible for
Corrective Action Enter/Update Corrective Action
Implementation Corrective Action such as
Approval Request Start or finish of
Analysis
Test
Before or after
implementation of
Preventive action
Containment action
Corrective action
Verification of
corrective action
implementation
effectiveness
3.4.3.10 ERES Support in Purchasing and Receiving Modules
21CFR Part 820.50 - Purchasing Controls and 21CFR Part 820.86 - Receiving,
In-Process, and finished device acceptance are the applicable sections of the regulations
that are applicable to the Purchasing/Receiving modules. The device manufacturer is held
responsible for the component parts that are purchased from the suppliers and used to
build the medical device. They are also responsible for having adequate processes
governing the controls on purchasing and receiving inspections.
There are two separate areas in Purchasing and Receiving that are covered by the FDA
requirements; Approved Supplier List entries and Receiving Inspection of purchased
goods. As the buying organization is chartered with procuring goods and services from
approved suppliers, they hold the responsibility of creating and maintaining a base of
qualified suppliers - this applies to component suppliers as well as suppliers of services.
Accordingly, the buying organization must have a system which tracks changes to the
qualified supplier list, specifically recording any edits, additions, or deletions to the list
as documented transactions for an audit trail.
The FDA regulations require the manufacturer to ensure that received material is in
accordance with the terms, conditions, and description of its corresponding purchase
order, and is also within the acceptable specifications and requirements established by
the manufacturer.
The manufacturer must further establish inspection procedures that define the acceptance
and rejection criteria. The outcome (e.g., "accept" or "reject") of the inspection must be
validated through a signature. Additionally, the inspection process and outcome must be
documented to establish an audit trail.
The inspection procedures established must:
• Ensure that the material supplied is in accordance with the purchasing agreement.
• Ensure that the received material is within the acceptable specifications and
requirements, established by the manufacturer.
• Establish inspection procedures that define accept and reject criteria.
• Document inspection, acceptance and rejection activities.
In 11i10, - the purchasing and receiving ERES transactions that are supported:
ASL Creation Yes No Purchasing -> ASL can be created
ASL Update Supply Base -> or updated in the
Approved Supplier ASL form, through
List the PO approval
PO Approval workflow or through
workflow the Purchasing
57
Document Open
Interface (PDOI)
Receiving Quality Yes Yes - Online Purchasing -> This is supported
Inspection Receiving -> only if Oracle
Receiving Quality is
Transactions implemented and
QA: PO Inspection
profile option is set
to Oracle Quality
Receiving Transfer Yes No Purchasing -> This is now only
with Quality Data Receiving -> supported if Oracle
Collection Receiving Quality is
Transactions implemented.
Receiving Delivery Yes No Purchasing -> This is now only
with Quality Data Receiving -> supported if Oracle
Collection Receiving Quality is
Transactions implemented.
3.4.3.11 ERES Support in Inventory Module
The applicable sections for requirements are Sections 820.60 Identification, 820.65
Traceability, 820.120 Device Labeling, 820.130 - Device Packaging. 820.150 - Storage,
& 820.160 - Distribution.
It is required that adequate procedures are followed to identify the product during all
stages of receipt, production, distribution and installation and to prevent product mix-ups.
Traceability requirements exist for critical devices and recalled products. Procedures are
required to control packaging, protect the device, handling the product and control
storage areas and stock rooms. Control must be exercised on labeling activities to
preserve the integrity of the labels. Labels must also be inspected for accuracy. Label
storage and operations on labels must be controlled.
A combination of Oracle modules including Inventory, WIP, Quality could satisfy these
regulations. In addition, Oracle Tutor, an SOP authoring tool could be utilized.
The Inventory transactions that are ERES enabled are:
Miscellaneous Yes Yes - Online Inventory -> Only online
Transactions Transactions-> transaction
Transaction types Miscellaneous processing mode is
supported are: Transaction supported
• Miscellaneou
s Issue
• Miscellaneou
s Receipt
• Account Issue
• Account
Receipt
• Account
Alias Issue
• Account
Alias Receipt
Oracle provides electronic record and electronic signature inquiry features to the
following forms:
Form Description
Inventory -> On hand, Availability -> Lots form -> For each lot, there are material and move transactions
View Genealogy button associated with it. If the base transaction captured an
eRecord/ eSignature, user can click View eRecord
option from the Tools menu to view the eRecord and
eSignature collected for a particular transaction
58
event.
Inventory -> On hand, Availability -> Serial For each serial, there are material and move
Numbers form -> View Genealogy button transactions associated with it. If the base transaction
captured an eRecord/ eSignature, user can click View
eRecord option from the Tools menu to view the
eRecord and eSignature collected for a particular
transaction event
3.4.3.12 ERES Support in WIP Module
The sections of the FDA Quality System regulations - 21CFR820, which are applicable
to the Work-In-Process module are 820.70 - Production and Process Controls, 820.75 -
Process Validation, 820.80 - Receiving, in-process and finished device acceptance and
820.86 - Acceptance Status.
Per section - 820.70 Production and Process Controls and 820.75 - Process Validation,
each manufacturer shall develop, conduct, control and monitor production process to
ensure that a device confirms to its specifications. The process controls include but not
limited to, documented instructions, standard operating procedures (SOPs), and methods
that define and control production, monitoring and control of process parameters and
component and device characteristics during production, approval of process equipment,
and criteria for workmanship.
Per section - 820.80 Receiving, in-process and finished device acceptance, each
manufacturer shall establish and maintain acceptance procedures to ensure that specified
requirements for in-process product are met and in-process product is controlled until the
required inspection and tests or other verification activities have been completed and/or
necessary approvals are obtained. All in-process acceptance activities must be
documented. Similarly, final acceptance activities are critical. Adequate procedures are
required for finished device inspection to ensure that each production run, lot, or batch of
finished devices meets acceptance criteria. Acceptance activities must be documented.
In 11i10, - the ERES transactions that are supported:
WIP Material Yes Yes - Online WIP -> Material Only online
Transactions Transactions -> WIP transaction
Transaction Types to Material processing mode is
be supported Transactions supported
WIP Component
Issue
WIP Component
Return
WIP Negative
Component Issue
WIP Negative
Component Return
Assembly Move Yes Yes - Online WIP -> Move Only online
Transaction Types to Transactions -> transaction
be supported: Move Transactions processing mode is
Assembly move supported
Assembly Return If quality results are
and Move collected for this
Assembly Move event, it will be part
Transaction Types to of the e-record.
be supported:
Assembly Move and
Completion (EZ
Completion)
Assembly Yes Yes - Online WIP -> Material Only online
Completion Transactions -> transaction
59
Transaction Types to Completion processing mode is
be supported: Transactions supported
WIP Assembly If quality results are
Completion collected for this
WIP Assembly event, it will be part
Return of the e-record.
3.4.3.13 ERES Support in Shipping Module
The regulation that governs the distribution of medical devices is 21CFR820.160 -
Distribution of Subpart L - Handling, Storage, Distribution and Installation is the
applicable section for electronic records and signatures in Shipping. The regulation states
that the device manufacturer is responsible for the control and the distribution of the
devices. Only the devices approved for distribution can be distributed and adequate
procedures should be in place to support the same. In addition, the device manufacturer
needs to maintain records that include the following information:
• The name and address of the initial consignee;
• The identification and quantity of devices shipped;
• The date shipped
• Any control number(s) used which may include lot and serial numbers
In 11i10, - the Shipping transaction that is supported with ERES:
Delivery Close Yes No Quality > Other > "Delivery Close"
Requests > Run > cannot be undone
Generate Shipping and this is the final
Electronic Record closing point of a
concurrent program shipment delivery
line
A concurrent
program titled
"Generate Shipping
Electronic Record"
has to be initiated
either manually or at
periodic intervals to
generate the
e-record.
This is supported only if Quality is implemented.
3.4.3.14 PO - Receiving Enh: Receiving Locator Support
It is now possible to have a Subinventory and Locator while in Receiving. Previously, it
was only possible in the receiving process to input a Subinventory and Location at the
Delivery Transaction. Now a Subinventory can be used to store the material while in the
inspection process. This enhancement makes it possible for Quality to use the Receiving
Subinventory and Location during the Receiving Inspection process.
3.4.3.15 UI Enh: Quality Workbench
The Quality Workbench is a completely new set of screens designed to ease and enhance
the entry of quality data in real business scenarios. The current method to enter Quality
data in forms requires users to horizontally scroll across the screen to enter or view data
in a quality collection plan. In the current method data is entered in horizontal rows and
only about 7-9 fields are visible to the user at one time it is difficult to view a whole row
of data that has been entered. The users group has consistently requested an improved
user interface as one the most important enhancements for us to make in Quality.
This new Quality Workbench will give the user one whole page to enter a single row of
60
data. The users now have a whole screen to see much more data and be able to visually
evaluate data that they have already entered for review and editing. Data on the screen is
in two columns and the user can then enter data for a complete row using the whole
screen. The user is then able to enter child plan data in a child plan or copy the row
entered to quickly duplicate the row above. Also, in Parent/Child entry the design
supports entering data in vertical format during multiple-record child data collection.
This is achieved by using the Show & Hide table feature in OA Framework. Show &
Hide lets the users expand a row of data to either show all fields or in the hide mode to
only display the first five columns of a collection plan. This is a very efficient method to
display to the user multiple rows of a Child Plan.
The Quality Workbench has four page tabs on the top of the screen that correspond to the
four separate business processes that are handled in Oracle Quality. The tabs allow quick
and easy access to the user of collection plans that are relevant to the business process tab
by pulling up only plans of that type.
The four tabs are:
• Collection Plans - in this region you will be able to query collection plans and
either do views of Quality data or input to collection plans.
• Nonconformance - this region allows the user to enter and view only
nonconformance collection plans and Disposition plans.
• Corrective Action - the region to enter and update corrective action plans.
• Skiplot - the area to view skiplot results.
The Quality Workbench quality results data entry supports a "read-only" attribute for
collection elements. When an element is read-only it can only be populated by default
values and assign-a-value actions - but cannot be changed during the data entry time by
the user.
3.4.3.16 OPM Quality Screen Enhancements (CU1)
3.4.3.17 Test Selection for Results Association (Enhancement #3756942) (CU1)
3.4.3.18 UI Enh: Gapless Sequence Element Generation
The current functionality of the automatic sequence element, released in 11i8, is that if a
user enters a collection plan, the sequence element increments every time a row is
entered, even if the user exits without saving the record. If the user does exit without
saving the plan results, then that sequence is not used, and there is a gap in the sequence
of numbers. So regardless of whether the transaction is saved, a new sequence number is
generated, each time and not every sequence number can be tied to a line of data
resulting in a gap of numbers in the sequence. While the sequence element is extremely
useful our users have requested this enhancement to end any confusion that could happen
because of a missing sequence number.
The new Gapless Sequence is an enhancement to the sequence collection element that
produces a numbering routine only when the transaction is saved and hence the numbers
are continuous without a gap. It is important for many applications of a sequence
particularly in auditable conditions that the sequence number is unbroken and sequential
and there are no gaps in the numbering. This is important for our Non Conformance and
Corrective Action Solution Templates because the FDA and other government regulated
businesses need to account for every number used in an NCM or CAR. Errors or unsaved
records need to be accounted for and this enhancement takes care of these issues. Also a
report is available to verify that all Sequence Numbers have been used and any numbers
61
that have been deleted can be accounted for. The report is called the Sequence Element
Audit Report.
It is also important to note that users will now be unable to trigger online actions based
on the values of the sequence since the sequence numbers are generated after Save. The
sequence element also cannot be generated on a Mobile application but only from a
desktop Quality input either through forms or through the Quality Workbench.
62
3.5 Oracle Work in Process
3.5.1.1 Discrete Workstation Coexistence with Shop Floor Mgmt
3.5.1.2 Overcompletion Quantities Reserved to Sales Orders
3.5.2.1 Infinite Scheduler Modifications
3.5.2.2 Additional Date Choices on Closed Jobs SRS
3.5.2.3 Support for Additional Pick Methodologies
3.5.2.4 Enh Warnings when Completing, Canceling, or Closing Jobs
3.5.2.5 Unit Effectivity Update through Mass Load
3.5.2.6 Option to Manually Release Tasks for Comp Picking for Mfg
3.5.2.7 Lead Time Calculation Enhancement
3.5.2.8 Component Picking by Job Operation
3.5.2.9 Serial Tracking and Genealogy through Production
3.5.3.1 Scheduling Workbenches
Scheduling workbenches are available for customers to view current job and operation
schedules and resource load compared to capacity, and to manually modify schedule
times as needed. Schedule times shown in the Gantt chart can be a result of constrained
scheduling in Advanced Planning or unconstrained scheduling in Manufacturing. Two
workbench styles are available - one with a job oriented Gantt chart and the other with a
resource oriented Gantt chart. Features include: 1) a table view in the Gantt chart of jobs
or resources, 2) user preferences for what details to display in the table view, what text to
display on the Gantt bars, and which jobs or resources to display in the Gantt at startup,
and 3) the ability for production schedulers and supervisors to interactively drag to
reschedule jobs and operations as required.
3.5.3.2 Operation Progress Reporting
There is now a way to capture a subjective completion percent on any job operation. The
user enters a completion percentage for one or more operations, and the system calculates
the percent complete for the entire job based on a weighted average of scheduled hours.
The calculation logic is system provided. This function is intended for future
63
enhancements but work order completion percent is available via an API.
3.5.3.3 Discrete Workstation Enhancements
There are several significant enhancements to the Discrete Workstation to broaden its
usability to more types of manufacturers. Users of resource instances are able to launch
the workstation for a specific instance and see dispatch lists by individual machine or
person if jobs are scheduled to that level of detail. There is also new functionality in the
business process of performing transactions providing users added capabilities to: 1)
collect quality information during assembly move and completion, 2) complete
assemblies under serial control, 3) enter sales order and completion subinventory and
locator information when completing assemblies, and 4) backflush serialized
components.
3.5.3.4 Component Quantity Change during Backflush
You now have the ability to explicitly allow or prevent overwrite of BOM required
quantity while component backflush is occurring during all assembly move and
completion transactions, and work orderless completions performed through mobile
screens (work orderless completions through the desktop form have full flexibility and
this is retained). This control is introduced through a new organization parameter that,
when enabled, allows users to change issue quantity on items being backflushed; and
when disabled, prevents users from changing issue quantity.
Backflush during Assembly Move or Completion - In addition to push components
which can always be issued to a job in any desired quantity, some pull components can
now be over or under issued as well - those requiring additional information input (like
manual entry of lot or serial number). Enable this capability through a new parameter,
allowing users the flexibility to issue more or less quantity than specified on the bill of
material at the time backflush is occurring.
Backflush during Work Orderless Completion (Mobile only) - Behavior for components
defined as Push (even though they are backflushed in work orderless completions) is
changed so they can be issued in any quantity during the completion transaction as long
as the new parameter is enabled. This behavior change also applies to pull components
requiring user verification or entry of additional information (exactly as with assembly
moves and completions).
3.5.3.5 Component Picking Enhancements
Multiple enhancements have been made to the component picking functionality for
manufacturing, originally introduced in Release 11i7. The intent is to enhance the
flexibility and usability of the first phase solution, and expand on existing features
making them beneficial to a larger number of customers. In summary, these
enhancements enable users to:
Link a Supply Subinventory to a Resource
Users have the ability to associate a subinventory (and locator, if under locator control)
to any machine resource. This is desirable when a resource, that is a production line or
machine, has a dedicated subinventory supplying components to any work utilizing this
resource. Applicable to discrete, repetitive, and lot-based manufacturing, having this
subinventory-to-resource relationship defined has two clear benefits:
• All backflush components required on operations using such a resource have the
specified subinventory as their supply subinventory.
• The supply subinventory changes when work on such a resource is re-dispatched
to an alternate resource.
Where this relationship is not defined, supply subinventory determination for backflush
64
components functions as it does currently.
Pick for a Range of Material Requirement Dates or Job Build Sequence
There will be two new criteria users are able to specify when searching for discrete job
requirements to pick:
• As an expansion of the current feature of selecting a requirement cutoff date, users
are able to specify a date range for picking components. So instead of getting all
past due pick requirements along with current ones, users are able to focus on
picking strictly for current requirements to keep production supplied, while
leaving past due requirements for cleanup at another time.
• Using a new way to search for open component requirements, users are able to
pick release components for all jobs having a build sequence included in a desired
range, as entered by the user on the Find window.
• Overissue Move Order Quantity
Users are able to issue a quantity of a component greater than the total quantity allocated
during previous runs of pick release. Applicable to all discrete, flow, lot-based, and
repetitive manufacturing modes, this feature supports times when it may be desirable or
more efficient for material pickers to pick a quantity greater than the allocated quantity
on a move order line.
Synchronize Job Component Requirements and Move Order Quantities
Automatic synchronization of inventory allocations and task statuses to reflect changes
made to material requirements of discrete and lot based jobs and repetitive schedules are
significantly enhanced. Material requirements changes caused by a change in job status,
job or component quantity increase or decrease, component deletion, assembly scrap, or
change in component supply type or location automatically trigger corresponding
material handling related events. These events may include changes to picking
instructions, warning messages, or move order line cancellation depending on the type of
requirement change that occurs.
3.5.3.6 Alternate Resource Sets
Applicable to constraint-based planning and scheduling, this functionality makes
alternate resources more flexible by allowing users to specify that a group or set of
resources can be substituted for another group of resources. Existing alternate resource
functionality allows one-for-one substitution, or substitution by group when all resources
in the group are simultaneous. This new functionality expands the use of groups of
resources as alternates by enabling the resources in the set to be sequential.
Example scenarios where this new capability could be applied are when customers wish
to define alternates and: 1) setup varies by machine so sequential setup and run resources
are substituted as a group, or 2) a set of machines are used sequentially in an operation
and the type of machine used first determines the type of machine used second.
3.5.3.7 Additional Flexibility for Excluding ECOs
With this modification to an existing profile, you have additional flexibility when
deciding whether to see the effects of engineering change orders (ECOs) in exploded
bills when choosing a revision or revision date. In addition to including or excluding
open ECOs, you can now choose to have the system exclude all open, released,
scheduled, and implemented ECOs during the bill explosion process.
3.5.3.8 Electronic Records and Electronic Signatures (ERES) Support for 21 CFR
Part 11 Compliance
Applicable to all FDA regulated industries such as food, pharmaceuticals, and medical
65
devices, this functionality provides support for creation of electronic records of activities
subject to audit, retention of those records, and capture of electronic signatures as legally
binding as signatures on paper. Satisfaction of these requirements is quickly becoming a
critical business requirement, and Oracle Mfg support of these features enables
companies falling under FDA regulation and similar regulations around the world to
comply. See the Quality section of the Release Content Document for more information.
3.5.3.9 Modifications to Transaction Processing Profiles
The function and dependence of transaction processing profiles affecting assembly
moves and completions with backflush is being modified to improve consistency and
minimize invalid transactions. The purpose of this modification is to have the move or
completion transaction and its associated backflush transaction work together, so they are
both online or both background. Additionally for background processing, once the
move/completion manager picks up a record for processing, backflushing occurs in the
same commit cycle. This eliminates the possibility of move or completion being
processed while backflushing fails.
3.5.3.10 Mobile Manufacturing Enhancements
Enhancements in this release for Mobile Manufacturing functionality only, are:
• Creation of reservation to sales order during Work Orderless Completions
• LPN user directed putaway
• Display of item quantity available in specified subinventory, locator, lot, or
revision during all WIP transactions that issue items out of inventory
(ref: Component Quantity Change during Backflush above and the Release Content
Document for Mobile Supply Chain Applications)
3.5.3.11 Usability Improvements for Component Lot/Serial Entry during Backflush
(CU1)
3.5.3.12 Outside Processing Enhancements
Improved communication has been enabled between manufacturing and procurement
functions when job schedule date or quantity changes occur and an outside processing
operation is impacted. The improved communication takes the form of job changes being
propagated to related purchasing documents. Users can choose to have this propagation
be fully automatic, automatic subject to approval, or manually accomplished.
PO date changes are initiated by a new concurrent program that evaluates differences
between OSP operation dates on jobs and need-by dates on associated POs, then launches
the purchasing change order approval workflow for each difference exceeding preset
tolerances. For quantity changes, there is a choice: 1) to have this same workflow
initiated each time there is a change to job quantity, or 2) to make PO quantity changes
manually. Date and quantity changes made to purchasing documents through the
workflow can be done automatically or only after approval.
Features built in this release are applicable to: 1) discrete jobs, 2) repetitive schedules,
and 3) maintenance work orders.
3.5.3.13 Scrap Enhancement
When assemblies are scrapped on a routing, component and item-based resource
requirements for future operations are reduced to reflect that fewer assemblies are
passing through those operations. The reduced requirements are considered when
processes like component picking or planning/scheduling are run after the scrap
transaction occurs.
66
4. Order Management
4.1 Oracle Order Management

4.1.1.1 Euro Customer Conversion Program
4.1.1.2 Order Management Diagnostic Programs
4.1.1.3 Default Source Type for Drop Ship
4.1.1.4 Commitment Enhancements
4.1.1.5 EDI 875 - Grocery Products Purchase Order
4.1.1.6 Global Credit Checking
4.1.1.7 EDI 850 -Purchase Order
4.1.1.8 API Extension for Defaulting Dependencies
4.1.1.9 Manual Release of Credit Check Holds Enhancements
4.1.1.10 International Trade Management (ITM) Additions
4.1.1.11 Item Substitution at Scheduling
4.1.1.12 Order Information Enhancements
4.1.1.13 Pricing and Availability
4.1.1.14 Sales Order Form Usability Enhancements
4.1.1.15 Pricing by Secondary Quantity/UOM (Catchweight Pricing)
4.1.1.16 Multiple Currency Price Lists
4.1.1.17 Audit Trail
4.1.1.18 View Shipping Status Window
67
4.1.1.19 Prepaid Credit Card Receipts in Order Management
4.1.1.20 Credit Checking Support for External Systems
4.1.1.21 Drop Shipment of Configurations
4.1.1.22 Solution-Based Modeling
4.1.2.1 Enhanced Basic Search for Finding Customers
4.1.2.2 Call Supply To Order Workbench to display Supply informat
4.1.2.3 TeleSales eBusiness Center to Sales Order Window
4.1.2.4 Order Management Setup Validation Report
4.1.2.5 Enhanced Multi-currency Setup
4.1.2.6 Electronic Msgs: RosettaNet
4.1.2.7 Display of Operating Unit Field.
4.1.2.8 Credit Management Integration
4.1.2.9 High Volume Order Import
4.1.2.10 Enhanced Pre-calculated Exposure
4.1.2.11 Blanket Orders
4.1.2.12 Scheduling Across Orders
4.1.2.13 Related Items and Manual Substitution
4.1.2.14 Electronic Msgs: EDI (850/860/875)
4.1.2.15 Quick Order Entry
4.1.2.16 Override ATP
68
4.1.2.17 Electronic Msgs: XML
4.1.2.18 Enh Freight Rating Ship Method Selection thru Oracle Tra
4.1.2.19 Late Demand Penalty
4.1.2.20 Gross Margin Display on Sales Order Line
4.1.2.21 Override Item Description on Sales Order
4.1.2.22 Variable Duration Accounting Rule
4.1.3.1 Versioning
Oracle Order Management has introduced Versioning to capture changes and updates
made to any transaction, which includes Sales Orders, Quotes and Blanket Sales
Agreements. Creating and managing versions can be of great assistance during the
negotiation phase of any transaction and helpful when maintaining history throughout the
life of a Sales Order, Negotiated Order and Blanket Sales Agreement. The history of
changes that are made to a transaction will be captured and stored, available to be viewed
and compared at another time. Amendments to the document can automatically trigger
versioning or the user can choose to manually version the transaction.
Features include:
• Manual or automatic generation using the processing Constraint framework to
determine what type of amendment will cause a roll in the version.
• Ability to capture Reason for changes made to all transactions. (Sales Order,
Negotiated Order, Blanket Sales Agreement).
• Ability to view reasons history for a given entity.
• The ability to display a comparison of changes across versions.
• Versioning captures changes that occur during negotiation. When the transaction
enters the fulfillment phase, versioning works in conjunction with audit trail. The
audit trail may track all sales order changes that may not necessarily constitute
revising the sales order to a new version.
4.1.3.2 Retroactive Billing
Retroactive Billing is a common business process in some industries, especially the
Automotive industry, whereby a customer requests changes to the amounts charged on
already invoiced orders and receives credits or additional invoices. Order Management
provides a query to identify order lines that have previously been invoiced that may be
subject to such retrobilling, a simple approval mechanism, and then the automatic
generation of credit memos (and occasionally invoices).
4.1.3.3 Scheduling Flexibility
New scheduling parameters are offered to users, allowing users to control various
scheduling activities. These parameters control:
• Whether a change in Request Date should trigger rescheduling. Users can
maintain current functionality, or set the parameter such that changing the Request
69
Date does not trigger rescheduling.
• Whether a change in Ship Method should trigger rescheduling. Users can keep the
existing behavior, or allow the Ship Method to be changed without triggering
rescheduling.
• How Promise Date is used. Promise Date can be defined as a static field, either
the first Request Date or the first Schedule Date. Other choices are making the
Promise Date dependent on the Request Date or the Ship Date. A fifth choice is
setting the Promise Date manually, i.e. by defaulting or manual entry.
• Partial manual reservations. When reserving manually on the sales order form or
using the Reservation Time Fence, users can choose whether or not to allow
partial reservations.
• The behavior of the Latest Acceptable Date (LAD) for manual scheduling. Users
can choose to ignore the LAD without a warning, ignore the LAD with a warning,
or to honor the LAD.
4.1.3.4 Catch Weights for Discrete Inventory
Catch weight support allows the user to specify a secondary quantity and secondary
UOM at the time of shipping and to reprice and invoice the order based on that quantity.
Catch weight support in Oracle Order Management has been available only for Inventory
Organizations which are enabled for Process Manufacturing.
Now any catch weight enabled item, which is shipped from a Warehouse Management
System (WMS) inventory organization, can capture the secondary quantity and
secondary UOM at time of shipping. This actual quantity is used to determine the
extended price for the order line and this price is prorated to determine the selling price
for the primary quantity.
Please refer to the Oracle Inventory RCD for additional details.
4.1.3.5 Blanket Sales Agreement Enhancements
Oracle Order Management continues to enhance Blanket Sales Agreements (BSA) to
leverage common functionality including workflow, approvals, versioning, and
processing constraints as well as include BSA-specific functionality such as inline
pricing.
Enhanced features include:
• Workflow enhancements:
• Negotiation and Fulfillment phases
• Internal Approvals
• Create Internal Approver List
• Automatically attach Adobe Portable Document Format (PDF) of
current BSA for Approvers to reference easily
• Quality Assurance (QA) validation for contractual terms and conditions
included in Negotiation flow
• Introduction of new processes to manage the BSA life cycle:
• Draft
• Internal Approval
• Customer Acceptance
• Terminate
• Expire
• Lost
70
• Close
• Direct access to Oracle Sales Contracts
• Automatic and Manual Versioning
• Customer Acceptance captured in a new tab
• Ability to create customer-specific Price List
• Ability to add customer items to a Price List
• New Pricing tab offers:
• Price List and Modifier List created through BSA are only updateable
through that BSA and are therefore unique to that BSA
• Inline Pricing directly on the BSA lines for line-level discount % or discount
amount
• Negotiate Range Breaks across release orders
• BSA will accumulate quantities and amounts ordered against it and price
accordingly
• Enhanced configuration support:
• Ability to define options and option classes on the Blanket Sales Agreement
to hold price for configurations on releases
• Ability to define service items on the Blanket Sales Agreement to hold price
on releases
• Service items can be associated with a Standard item or can be used as part
of a configuration
• New document(s) with Print enhancements
• Security through Processing Constraints
• Copy
• Attachments
4.1.3.6 OM-EM: RosettaNet 3A8 Request Purchase Order Change / OAG Change
PO
The RosettaNet 3A8 and the equivalent OAG Change PO XML Electronic Message has
been added with this release and will provide the following collaboration capabilities:
Functionality includes:
The 3A8 can be used as a response by the buyer to a seller initiated 3A7 Notify Of
Purchase Order Update.
The 3A8 can be used by the buyer to convey changes to the seller for an existing sales
order that is in pending or accept status.
4.1.3.7 OM-EM: RosettaNet 3A7 Notify Purchase Order Update / OAG Change SO
The RosettaNet 3A7 and the equivalent OAG Change SO XML Electronic Message has
been added with this release and will provide the following collaboration capabilities:
• Enables a seller to acknowledge acceptance or rejection of a pending order line as
communicated via the RosettaNet 3A4 Purchase Order Response / OAG
Acknowledge PO.
• The RosettaNet 3A7 Notify Purchase Order Update / OAG Change SO electronic
message can also be used by the seller to initiate changes to a previously sent
buyer initiated purchase order.
• This electronic message may be used by the buyer as a basis for initiating a
71
RosettaNet 3A9 Request Purchase Order Cancellation / OAG Cancel PO when
changes suggested by the seller are not accepted.
4.1.3.8 OM-EM: RosettaNet 3A4 Request Purchase Order / OAG Process PO
Oracle Order Management continues to enhance the existing RosettaNet 3A4 Request
Purchase Order and the equivalent OAG Process PO XML Electronic Messages to
provide additional functionality and collaboration capability.
• A pending status can now be assigned at the order line level.
• Addition of the new pending status now allows all of the current statuses available
in the RosettaNet standard to be applied at the order line. The statuses are:
• Accepted / Rejected / Pending
4.1.3.9 OM-EM: RosettaNet 3A4 Purchase Order Response / OAG Acknowledge
PO
The RosettaNet 3A4 Purchase Order Response and the equivalent OAG Acknowledge
PO XML Electronic Message has been enhanced to provide additional functionality and
collaboration capability.
• A pending status can now be returned to the buyer signaling that the order line is
in a pending status.
• All of the current status available in the RosettaNet standard can now be returned
in the response message. The statuses are:
• Accepted / Rejected / Pending
4.1.3.10 OM-EM: Open Interface Tracking User Interface
The Open Interface Tracking UI is added to allow users to monitor the Electronic
Messages supported by Order Management.
• Access to Workflow Status, XML Gateway Transaction Monitor and Order
Import Corrections form via the UI.
The ability to maintain history for XML, EDI Electronic Messages.
The ability to maintain history for Order Import processing.
4.1.3.11 Multiple and Partial Payments
Oracle Order Management is enhanced to allow additional types of payment vehicles and
to allow specification of a payment at the line level. Also multiple prepayments can be
processed at the order header level, to provide support for down payments. Major
features include the following:
• New payment types include Wire Transfer, Purchase Card, Automated Clearing
House transaction (ACH) and direct debit.
• New UI to display and enable Payment Types and input optional attributes.
• New UI to input and display payment information for an order.
• Ability to input prepayment data for an order. You may create multiple
prepayments and they can be for a partial amount of the order total or for the full
amount of the order. OM creates one or more AR receipts linked to the order, for
later application to the invoice when it is created.
• A new workflow activity for Payment Assurance. Use it if you want to verify that
a prepayment has been collected before you ship, for example.
72
• Ability to enter one payment instrument at the line level, as long as there are no
prepayments on the order.
• A new 'quick receipt' document that can be printed and handed to a retail
customer.
• Enhanced Credit Card Authorization for Installment terms. OM provides option to
authorize the first installment only instead of the total order amount.
• Batch authorization of Credit Cards, including automatic retries of authorizations
that fail due to network outages.
• Ability to create multiple payments and prepayments using Order Import.
4.1.3.12 Preview and Print Sales Documents
A flexible preview and print feature provides the ability to generate a printable Adobe
Portable Document Format (PDF) that can meet a business' layout requirements. Preview
and Print is an action available on each business document (Sales Order, Release Order,
Quote, Blanket Sales Agreement) that displays the PDF document, which can be viewed
and printed.
Features include:
• Layout Templates can be easily designed to meet specific formatting requirements
• Ability to print all necessary information of the business document including
header, line information, and signature block
• A default Layout Template can be defined on the Transaction Type
• Field on the business document displays the Layout Template defined for the
Preview and Print
• Automatically attaches PDF in Workflow notification to Internal Approvers
and attaches the PDF file to the business document in the system
4.1.3.13 Order Management Parameters
The Oracle Order Management Parameters form is enhanced for greater flexibility.
Parameters can be functionally grouped, and users can define controls there as easily as
with profile options.
4.1.3.14 OM-EM: RosettaNet 3A9 Request Purchase Order Cancel / OAG Cancel
PO
The RosettaNet 3A9 Request Purchase Order Cancel and the equivalent OAG Cancel PO
has been enhanced with this release and will provide the following collaboration
capabilities.
The ability to cancel line items in pending status.
The ability to partially cancel line items on an order.
The ability for the buyer to respond to a seller initiated 3A7 Notify Purchase Order
Update / OAG Change SO.
4.1.3.15 Project/Task Changes for Booked Orders
This enhancement benefits users of Oracle Project Manufacturing. Prior to this, once an
order line was booked, the user could not make any adjustments to the Project or Task
attached to the line. This restriction is lifted; thus allowing the user to make changes to
the Project or Task number at any time until the order is closed.
4.1.3.16 Approval Enhancements
A workflow process for Approvals has been created to leverage in any business process
73
where Approvals may be required. The Approver list can be setup easily in Oracle Order
Management and tied to a specific transaction type. Workflow notifications provide users
the details of the approval or rejection.
The Approval activity as been seeded in the Negotiation Phase as well as in the Oracle
iStore Returns flow.
A List of Approvers can be defined through the Transaction Type or Approver form.
4.1.3.17 Advanced Item Search
The intent is to provide the Oracle Order Management user with an additional, expanded
item search capability within the Sales Order form and the Quick Sales Order form. The
user can search for items using criteria such as item description, category, catalog
information, etc. This enables the user to select items by characteristics that vary
frequently. For example a distributor of CDs, DVDs or videos may take orders by
Current Chart Position as well as Catalogue number, Artist, Title, etc. Once the search is
complete and the item selected, that item is added to the sales order.
It does not replace the current Item LOV, but adds the ability for the user to search for
items based upon item attributes.
Please see the 11i9 Advanced Product Catalog RCD for additional information.
4.1.3.18 Automatic Fulfillment Set and Line Set Assignment
Oracle Order Management enhances Line Set (Ship/Arrival) and Fulfillment Set
functionality with seeded defaulting rules which will minimize the need for user action
thus reducing error and keystrokes.
Features include:
• Provide the ability to automatically assign all lines of an order to one Fulfillment
Set.
• Allow defaulting header level Line Set (Ship/Arrival) and Fulfillment Set from
Order Transaction Types
• Support removal and addition of a line from Lines Sets and/or Fulfillment sets
from Order Import and Process Order API.
4.1.3.19 Authoring and Negotiating Contract Terms
If the Oracle Sales Contracts option is licensed, Oracle Order Management users can
author contract terms on all sales documents. As part of creating a sales document, sales
managers or sales representatives can pick a standard contract template. During
negotiations, if modifications need to be made to the standard terms, contract negotiators,
contract administrators or legal can edit the standard terms. The sales contract can be
printed for customer acceptance and signature.
Businesses will not only benefit from the fundamental contract capabilities available in
base Order Management like price holds, enforcing pricing on future orders etc., but also
have the ability to negotiate contract terms and conditions.
All Oracle Order Management entities have been enhanced to support the contract terms
authoring flows:
• Quotes: Sales Orders beginning with a Negotiation workflow
• Sales Orders: Sales Orders beginning with a Fulfillment workflow
• Release Orders: Sales Orders with a Blanket Sales Agreement reference
governing items, price, and terms
• Blanket Sales Agreements: Long-term agreement which can be referenced on a
single transaction to leverage volume pricing, terms and conditions and
74
accumulation data
With the sales contracts option, Oracle Order Management transactions leverage
advanced contract authoring capabilities into the existing robust sales processes. Features
include:
• Author contract terms:
• Apply a Contract Template
• Choose additional standard clauses
• Create non-standard clauses
• Choose alternate clauses
• Validate contract terms for inaccuracies
• Preview and print contract in PDF. Printable sales contract includes headers,
lines, contract terms and Signature Block. The flexible printing infrastructure
allows companies to configure the layout to conform to corporate standards.
• Workflow enhancements: Negotiation and Fulfillment flows
• Automatically attaches printable PDF to the approver workflow notification
and to the transaction as a contract document.
• Record customer acceptance information
• Clause Security through Processing Constraints
For more information on creating standard clauses, contract templates, authoring and
managing sales contracts please refer to the Oracle Sales Contracts RCD.
4.1.3.20 Drop Ship Change Management
Oracle Order Management has enhanced the drop shipment process by communicating
additional data elements from Oracle Order Management to Oracle Purchasing and then
to the end supplier, providing visibility to the Sales Order Number on the supply order
and automatically sending Sales Order changes to the Purchase Order and then the
Supplier. These enhancements now offer enhanced communication and automation of the
drop ship business flow:
• Companies may now communicate drop ship purchase orders to suppliers that
include additional details about the end customer (for example, ship-to, customer
name, ship-to contact, shipping instructions etc.). This information allows
suppliers to ship goods more efficiently and with increased accuracy.
• Customer requested changes to sales orders would now automatically propagate
through the entire procure-to-pay process. Oracle Order Management
communicates changes (for example, order quantity, ship to address, schedule
date, etc.) directly to Oracle Purchasing and then to the supplier without any
manual intervention.
With enhanced change management, Oracle Order Management and Oracle Purchasing
will provide a more harmonized and automated process for drop shipments. Additionally,
with this enhanced functionality, the Sales Order Purchase Order Discrepancy report will
be obsolete and unsupported.
4.1.3.21 Drop Ship Across Sets of Books
Currently, drop ship lines can only be sourced from suppliers defined in the same
Operating Unit or Set of Books as the Operating Unit in which the customer sales order
is taken. Now we are providing the ability to drop-ship goods across Operating Units,
Legal Entities and Sets of Books.
To understand this better, consider the following business flow. A customer places a
75
sales order with a sales organization in Canada (Set of Books 1). The procurement is
managed by a central purchasing organization in the United States (Set of Books 2). A
purchase requisition and purchase order is automatically generated and sent to the
supplier who ships the item directly to the customer. An inter-company invoice
transaction will be automatically generated between the US (SOB 1) and Canada (SOB
2) to compensate the US organization for the cost of procuring the item for the Canadian
sales organization.
The major features include the following:
• Oracle Order Management and Oracle Purchasing have enhanced the integration
to handle drop shipments across Operating Units, Legal Entities, and Sets of
Books (SOB). Purchase Requisitions and supplier Purchase Orders can now be
created in different Operating Units. This will be supported for non-OPM
customers.
• You will be able to see Requisition and Purchase Order information that are in
different Operating Units within Order Management's Drop Ship Tab, Additional
Line Information Window.
• With the enhanced Inter-Company transaction support, Inter-company Invoices
will be generated between multiple Organizations (Operating Units, Legal
Entities, Sets of Books) that are involved in a Drop Shipment flow. This will be
supported for non-OPM customers.
Refer to Oracle Inventory's RCD on Enhanced Inter-Company Transactions for more
details.
4.1.3.22 International Trade Management (ITM) Partner Integration
Enhancements
Oracle Order Management introduces Generic Export Compliance Request via XML for
all the export related compliance checks. These include Restricted Party Screening,
Embargo Country Screening, License Determination, Document Generation and other
partner supported screening like EPCI etc. The partner ITM application evaluates the
transaction for export compliance and responds to Oracle Applications with the overall
compliance pass or fail status for each of the order lines. The audit trail of the
compliance checks is maintained in the partner ITM application.
Please see the Oracle Shipping Execution RCD for additional information.
4.1.3.23 High Volume Shipping Interface
High Volume Order Processing (HVOP) functionality is enhanced to improve the
performance of the interface from Oracle Order Management to Oracle Shipping
Execution.
With HVOP, orders can be imported in either Entered or Booked status.B If orders
imported with HVOP come in with a Booked status, the interface of Oracle Order
Management to Oracle Shipping is enhanced.
The performance of the interface from Oracle Shipping to Oracle Order Management has
also been improved.B If users ship the complete ordered quantity of multiple lines at
once using the Trip Stop Interface, performance is optimized.B Even if some of the lines
are completely shipped and others are partially shipped, a performance benefit is
expected for the lines that are completely shipped.B There may be some performance
benefit for partially shipped lines, but it is not expected to be as significant as the
performance gains for lines that are shipped completely.
4.1.3.24 High Volume Pricing
High Volume Order Processing (HVOP) functionality is enhanced to improve the
76
performance of pricing high volumes of order lines. HVOP pricing supports many
features, e.g. discounts, surcharges, freight and special charges, static or dynamic
formulas and GSA pricing.
Optimal (bulk) performance for pricing requires setups are described below.
• The Java pricing engine is installed. Please refer to Oracle Advanced Pricing's
RCD on Middle-Tier Pricing Engine for more details.
• There are restrictions on Custom Sourcing rules that use information from the
current order/line from Oracle Order Management tables.
4.1.3.25 Global Order Promising for ATO Configurations
Scheduling for ATO models is enhanced so that sourcing rules can be used to select a
warehouse for an ATO model. With this functionality, users will no longer need to
specify a warehouse for the ATO model.
If the ATO model or any of its components are ATPable, the promised availability will
consider the matched configuration supply if ASCP is installed. If the user chooses to
drill from the Availability window to ATP Details, the quantity of available matching
configured items is displayed. A new column, Days Late, identifies options that are
extending the Schedule Date on the ATP Details window.
4.1.3.26 Fulfillment with Wait
Oracle Order Management has enhanced the Fulfillment Workflow activity to provide a
new seeded workflow sub-process "Wait to Fulfill Line". Customers can add this
sub-process before the existing defer_fulfillment and/or fulfill_line.
Order Management becomes more restrictive to user changes once an order line has been
fulfilled. As an example, a user cannot cancel or change the quantity on an order line
once it is fulfilled. Without the new subprocess, non-shippable lines are immediately
fulfilled once the order is Booked. Once Booked, users are prevented from performing
changes on these lines.
The new subprocess can be used for shippable, non-shippable and bill only lines alike to
defer the fulfillment activity thus creating an opportunity to make changes or corrections.
4.1.3.27 Move Add Change Disconnect (MACD)
From the Sales Order and Quick Sales Order forms order upgrades of customers' existing
services are supported. The functionality required to support changes to customers'
existing services is commonly referred to as "MACD" functionality (acronym for Move,
Add, Change and Disconnect) and is especially attractive to telecommunications
companies. The major part of the revenue for telecommunication companies comes from
orders where their existing customers are ordering changes to their installed base of
electronic services.
The sales representative can select services from their customer's Installed Base and
reconfigure the customer's services by e.g. moving, adding, changing or disconnecting
products. What line type to set for an order line that holds a reconfigured service is
configurable given what changes were done to the service in the configuration session.
Different services within a model can have different line types and hence different
fulfillment flows.
By introducing MACD functionality, the full life cycle of customers' services can be
tracked in the eBusiness suite; customers' services can be uniquely configured, ordered,
fulfilled, serviced and changed/upgraded.
4.1.3.28 Line Level Ship/Arrival Sets
Oracle Order Management has increased the choice to their customers of header level
77
Ship/Arrival Set functionality. The profile, "OM: Assign new set for each line", provides
two alternatives:
Many businesses do not wish to create multiple shipments for a single order. The default
will be set to "N" thus creating ONE Ship/Arrival Set per order. As an example, if the
header level choice is Ship, then all successfully scheduled lines will automatically go
into one Ship Set when created.
It is important for other businesses that a single line ship complete and multiple
shipments are allowed per order. By setting the profile to "Y", the system will create a
unique Ship/Arrival Set for EACH line in an order as long as the line can be scheduled.
4.1.3.29 Configuration Date Effectivity Enhancements
Many users require the ability to manage sales order and configuration changes on an
on-going basis. As part of the increased flexibility provided to customers in handling the
many dates used in processing orders within the supply chain, Oracle Configurator
customers are now able to specify either the creation date of the model line or the system
date until booking for validation of item effectivity in new or existing configurations.
This option will be provided by an Order Management system parameter, OM:
Configuration Effective Date. Based on the value of the Order Management system
parameter, Order Management will pass the selected date (creation or system) to
Configurator for the configurator effective date and configurator lookup date.
To understand what this means, consider the following business scenario. A sales order
for a configuration is entered on Day 1 but is not booked. On Day 2, the definition of the
configuration changes - an option becomes invalid. On Day 3, the sales order is changed.
The configuration information is passed to the Configurator for validation. With the old
behavior, the configuration would be validated based on the rules in effect on Day 1, the
date that the configuration was originally created. With the new behavior, depending on
the setting of the profile option, Configurator may validate based on the updated
configuration rules from Day 2.
4.1.3.30 Display Choices for Freight Rating
Oracle Order Management is expanding the integration with Oracle Transportation to
provide users the ability to view eligible freight charges (contracted rates or otherwise)
and choose between different ship methods (mode, carrier and service level). Users can
choose carrier/ship method for its rates, or for optimal delivery times.
If multiple freight options exist, the user will be able to view all eligible freight options
(including mode, carrier and service level) along with what the estimated charge and cost
for each ship method as well as the estimated in-transit time and then indicate their
choice.
4.1.3.31 Decimal Quantities for Options of ATO Configurations
While selecting options for a model, users can currently enter only whole integer
quantities. Some businesses build products that need to be ordered in decimal quantities.
We now provide the ability to specify decimal quantities when selecting options for ATO
models, both in the Configurator and in the Options Window.
For instance, if both the parent and child are set to integer values (indivisible flag on the
item master = yes), then Configurator verifies that the ratio between the child quantity
and the parent quantity is an integer, and that the ratio is between the child component's
minimum quantity and maximum quantity, inclusive. Or if the child allows a decimal
(indivisible flag on the item master = no), the ratio should be allowed to take any value
between the child component's minimum and maximum quantities.
4.1.3.32 End Customer
78
This feature enables you to specify the End Customer on a sales order.B You can specify
a different End Customer for each line.
The Sold To customer is passed to Service Contracts.B Three attributes can be defaulted
to Install Base:B Owner, Current Location, and Installed Location.B If an End Customer
is specified, the owner of the shippable product is automatically updated in Install Base.B
Additionally, the End Customer location or another location specified on the order can be
defaulted to Install Base as the Installed Location and/or Current Location.
This functionality is supported in the Sales Order window and the Quick Sales Order
window.B All the End Customer and Install Base attributes can be processed by Process
Order API and Order Import.B EDI and XML are not supported.
Users have the option to assign sales credits based on the End Customer or Sold To
customer.
4.1.3.33 Service Termination
Service items in Oracle are traditionally defined as agreements to provide service such as
extended warranties. The ability to terminate a service item and credit the customer is a
common business requirement in many industries. For example, you may purchase a
dishwasher and an extended warranty. After the item has shipped, you decide to return
the dishwasher to the store and "terminate" the extended warranty.
In this release, Oracle Order Management will enhance the flow for terminating service
when a product is returned. Now, Order Management will use the RMA line to govern
the issuance of full or partial credits to the customer. Order Management will also make
the determination whether the product return also qualifies for service credit. With this
enhancement, Install Base will use the information from RMA product line to determine
whether a credit is given. This will allow for more flexibility in credit and re-bill
scenarios when, for instance, there is an incorrect billing address. The user can 'terminate'
the order, generate a credit and re-bill the order with the correct billing address.
4.1.3.34 Simple Negotiation in Oracle Order Management
The Oracle Order Management framework has been extended to include a workflow
phase to support the activities that typically occur within a negotiation process, such as
internal approval and customer acceptance. A sales order in the negotiation phase will be
referred to as a Quote. This allows users to create and manage quotes during the
negotiation phase and transition the quote to a firm order, which will begin its fulfillment
flow, after completion of the negotiation.
Usability features as follows:
• A separate menu option is available for entering Quotes
• Date Expiration
• Pricing and Availability queries
• Copy support
• Defaulting of attributes that can affect a quote
• Display of Related Items, such as up-sell, cross-sell or substitute items, and their
price and availability
• Integration with Pricing
• Integration with TCA
• Allows minimal data entry and can be processed through to Oracle Order
Management as a firm order complete with approvals (Internal/External).
Relevant information captured by the quote will flow through to the order.
• Change Management using Processing Constraints and versioning
79
• Automated Process definition - workflows can be defined and extended.
• Visibility via Order Information Portal
• Customer Location
Oracle Order Management is being enhanced to allow an additional address type of
Customer Location that can be used both within the Negotiation phase (for both sales
order and blanket sales agreements) or Fulfillment phase. In the Negotiation phase, it
should be used as a mailing address to which the quote can be sent. Customer Location
will be an Order header value that can be defaulted if it represents the primary sold to site
and used as a data source for defaulting attributes.
Customer Location on a Quote/Order can be different from Ship To and Bill To Address.
Date Expiration
Oracle Order Management has introduced Date Expiration. A Quote is an offer to do
business and the validity of that offer is often limited to a specific period. If the customer
does not complete the negotiation by a specific point in time, then the offer is liable for
closure.
Many negotiated orders may be generated during the normal course of business but not
all quotes will come to fruition. The negotiated orders have a specific life cycle and, as
such, should close when that cycle expires without the intervention of users who are
resourced generating future sales.
Features include:
• Expiration Dates entered will be honored by workflow and when the date has
passed the quote will automatically move to a Closed status in the Work Flow and
become eligible for purge.
• The offer expiration date can be entered manually by the user or by the
defaulting rule framework. The user may override the date at any time unless
processing constraints are defined to manage who and when may amend this
date.
• When the quote is due to expire a notification can be generated to alert the
CSR. The user may require the notification ten days before the offer expires.
This duration/notification initiation may vary from Transaction type to
transaction type.
• Purge
• Oracle Order Management has enhanced the purge criteria to include negotiated
orders that are no longer needed within the operational requirements of the order
taken and order administration.
• Copy
Oracle Order Management has enhanced the copy function to allow the creation of
Quotes based on an existing Quote or Sales Order using the Copy Orders feature.
A new quote may be created by copying information from the following sources:
• An existing quote at any stage of the order process
• A previous version that has been archived and is view only.
• An existing Sales Order
• Multiple lines from any of the above sources
• Multiple quotes/sales orders to Multiple quotes
• A specific version of the source document may be copied and the new
80
transaction will start with Version '0'.
• Seeded Workflows
• Oracle Order Management workflow processes are enhanced to automate
and standardize the pre-order negotiation phase:
• Negotiation Flow - Generic. This is a simple negotiation flow, without approvals.
The user prepares the negotiation, gets final acceptance from the customer, and
converts the negotiation to either a Sales Order or a Blanket Sales Agreement.
Negotiation Flow - Generic with Approval. The user prepares the negotiation, gets
approval(s) as required, gets final acceptance from the customer, and then converts the
negotiation to either a Sales Order or a Blanket Sales Agreement.
Quick Codes
Users can define quick codes tailored to their business. The quick codes provide
transaction status information, independent of workflow. Users can query either on the
quick-code status or the workflow status.
Supported features of Quotes relative to Sales Orders
The functionality supported with Quotes is similar to the level of support for Sales
Orders. There are a few Sales Order features that are not available during the negotiation
phase of a transaction including:
• Holds
• Scheduling
• Independent line flows
• Cancellations - transaction should be progressed to a LOST status.
• Ship Sets and Arrival Sets
• Commitments can be selected as a place holder only
• Credit check
• Negotiation to Internal Order Process
• Standard Reports
4.1.3.35 Pricing and Availability Enhancements
The Pricing & Availability form, which allows users to quickly check the price and/or
availability of an item without entering an order, is being enhanced to extend usability
features as follows:
• Ability to take the item being queried or any items in the 'saved' selection area and
automatically convert it into a Quote or a Sales Order.
• Additional search criteria, including demand class, line type as well as the ability
to enter 'ask for' promotions and coupons.
• Ability to do Pricing and Availability checks of ATO items.
• Enhanced defaulting of attributes that can affect Pricing and Availability,
including demand class, item identifier type, order type, warehouse and price list.
• New results tab to display Related Items, such as up-sell, cross-sell or substitute
items, and their price and availability.
• New sub-tab of Pricing results tab to display 'Additional Benefits'. These are
modifiers that are applicable but that do not affect the selling price, including
terms substitution, promotional goods, other item discounts, item upgrade,
coupons and accruals.
• Display of modifier Price Breaks in addition to existing price list Price Breaks.
81
• Ability to apply Manual Discounts to items whose price is being checked.
• Ability to store a selected group of items being checked, so that they can all be
ordered at once.
4.1.3.36 Publishing Plan Results to Oracle Order Management
In previous releases of Oracle Order Management, Oracle Global Order Promising was
called at the time of scheduling to determine the scheduled ship date for sales order lines.
After that, supply or demand changes would have no effect on lines that were previously
scheduled. In this release, if certain conditions occur, Oracle Advanced Supply Chain
Planning (ASCP) has the ability to update the schedule (ship / arrival) date, warehouse,
and shipping method on sales order lines based on planning. A planning attribute,
Demand Satisfied Date (DSD), is the material availability date. If the DSD is greater than
the Request Date, ASCP may change the scheduled ship date.
Users may want to firm an order line, so that ASCP cannot change the warehouse from
which the item is sourced. Order Management provides three ways to firm the sales order
line:
• Based on an event. Users could choose to firm the line at scheduling, or when the
line is interfaced to shipping, or not at all.
• Through a seeded workflow process. A new workflow subprocess will hold the
lines until they are progressed. Once the lines are progressed, they are firmed. A
new concurrent program is provided for progressing lines waiting at this
subprocess.
• Using the Firm flag on the sales order line. Users firm the line by setting the flag
manually, or they can unfirm the line.
4.1.3.37 Reservation Enhancements
The Reserve Orders concurrent program is being enhanced to support the three
reservation modes below. Once partial quantities are reserved, users can pick release by
Prior Reservation, and ship the partial quantities.
• Partial. You can determine whether or not to include a line with an existing partial
reservation. Supply is not guaranteed for all lines.
• Percentage. You can specify any percentage from 1 to 100, and a percentage of
the Requested Quantity will be reserved as long as supply exists. The Order By
parameter can be used to ensure supply for higher priority lines.
• Fair Share. You can give each of the queried lines its Fair Share. For example, the
requested quantity is 60 for one line and 40 for another. Ten are available. The
first line gets a Reserved Quantity of 6, and the second line gets 4. When using
Fair Share, each of the queried lines will get supply, assuming there is enough for
each line to get at least 1.
An additional parameter has been added for Shipment Priority, allowing users to reserve
lines for a specified Shipment Priority.
Three reservation run types are provided: Reserve, Simulate, or Create Reservation for
Set. If desired, users can simulate the output and adjust the reserved quantity before
committing the reservations.
A hook is provided for users who wish to write their own code to apply their own
specific business rules to adjust the results of running Reserve Orders.
Within Scheduling Across Orders, users can run Reserve Orders, view the simulated
output if desired, make modifications, and commit the reservations.
82
5. Procurement
5.1 Oracle Purchasing

5.1.1.1 Enhancements to Procurement of Configured Items
5.1.1.2 ASN Inbound into Oracle Purchasing via XML
5.1.1.3 Enhancement to Purchasing Documents Open Interface
5.1.1.4 Integration with Oracle Sourcing
5.1.1.5 Enhanced Requisition Modification Capabilities
5.1.1.6 Support for Vendor Management Inventory
5.1.1.7 Enhancements to Email PO
5.1.1.8 Auto Sourcing Enablement during Blanket Agmt Approval
5.1.2.1 Integration with Oracle Commitment Budgetary Control (CBC)
5.1.2.2 Global Agreements
5.1.2.3 Receiving Improvements
5.1.2.4 Renegotiate Blanket Agreements in Oracle Sourcing
5.1.2.5 Currency amount-based Price Tolerances for POs
5.1.2.6 Outbound XML Purchase Order Improvements
5.1.2.7 API Additions
5.1.2.8 Consigned Inventory
5.1.2.9 Pricing Improvements
83
5.1.3.1 Services Procurement
Oracle Services Procurement enables a streamlined process for sourcing, procuring and
managing of services, such as contingent labor, facilities management, marketing,
information technology, consulting services, and more. These commodity areas usually
account for a large percentage of an organization's spend. Oracle Purchasing enables key
business functions in the services procurement flow, including preferred supplier
identification and management, long term agreements for fixed price and rate based
services, purchase order management, time card management and auto invoice
generation and payment.
Please refer to the Oracle Service Procurement RCD for more information.
5.1.3.2 Purchasing Documents Open Interface Enhancements
The Purchasing Documents Open Interface (PDOI) currently supports importing of new
blanket agreements, new standard purchase orders, and new lines on existing blanket
agreements. With 11.5.10, you can add new lines and associated shipments to an existing
standard purchase order. Similar to importing blanket agreements, you can specify that
the new line should be brought in as 'approved', or you can import the new line as
'incomplete' and then initiate the approval process. The standard purchase order will be
revised and, upon approval, communicated to the supplier.
5.1.3.3 Requisition Approval Management using Oracle Approvals Management
Oracle Purchasing now provides the option to use Oracle Approvals Management as the
approval engine for requisitions. Some of the benefits include:
• Single approval engine with consistent and uniform approval policies across
multiple Oracle Applications modules including Oracle iExpenses.
• Approval policies can be defined once and be leveraged across multiple products;
hence less maintenance is required.
• Approval policies can easily be extended using the standard features of Oracle
Approvals Management eliminating the need to customize individual applications
or the workflow.
5.1.3.4 Accounting
Category Based Account Defaulting in Oracle Purchasing
Account generation workflow logic has been enhanced to add category specificity to the
default expense charge account on purchase orders or releases. Companies can call out
segments that will carry category specific values in the multi-segment charge account
structure. The account generator workflow has been enhanced to construct the expense
account based on a combination of the employee default expense account and the
category specific rules. Equivalent functionality for expense account defaulting onto
requisitions in Oracle Purchasing has been available since Release 11.5.9.
Encumber Blanket Agreements
Many organizations negotiate long-term agreements with suppliers and commit to a
certain level of spending during the life of the agreement. These minimum spending
commitments need to be captured and budgeted. Buyers now are able to capture these
commitments and encumber funds on Blanket and Global Blanket Agreements to
accurately reflect existing commitment levels. These funds are encumbered against a
summary budget account as called out by the buyer on the agreement. The encumbrance
on an agreement is gradually relieved as purchase orders or releases are created against
the agreement. Requisition lines referencing encumbered agreements are not
84
encumbered, as funds committed on the backing agreement have already been reserved.
Selectively Un-reserve fund
Users can now relieve encumbrance at any level (Header, Line, Shipment, or
Distribution) of the purchasing document from the entry forms (Enter Purchase Orders,
Enter Releases, or Enter Requisitions).
Import Grant Information
Companies can now import award information related to purchase order distributions via
the Purchasing Documents Open Interface (PDOI). This eliminates the need for manual
data entry when importing purchase order information from an external source. In
addition, Oracle Purchasing now provides improved visibility into grant award
information when grants are used as a source of funding on requisitions and purchase
orders. Users can review grant award information on Purchase Order and Requisition
Distribution Summary screens.
5.1.3.5 Center-Led Procurement Features
With 11.5.10, Oracle Purchasing includes a powerful solution for automating the
purchase order execution, receipt and invoice where the requesting business unit differs
from the organization that issues the purchase order. With the intercompany transaction
flows established, the system can issue the PO from the appropriate buying center and
handle the required accounting charges. This solution can be especially useful for
companies that use shared service centers or when POs need to be issued by specific
subsidiary organizations.
Enable Purchase Order Execution in Any Organization
Buyers were able to centrally negotiate pricing and contract terms on behalf of multiple
organizations using Oracle Sourcing in 11.5.9. The finalized agreement was captured as a
global blanket agreement in Oracle Purchasing. Enabled organizations were able to
leverage the centrally negotiated pricing but forced to generate purchase orders in the
organization where demand originated. Now, buyers can define purchase order execution
organizations for each of the demand-generating and enabled organizations on a global
blanket agreement. For example, a European-based company can create and enable a
global agreement with a supplier based in China and specify that all purchase orders
issued against the global agreement will be issued from an international subsidiary
organization in China. Furthermore, buyers can also specify the supplier location
(supplier site) from which demand will be satisfied for each of the enabled organizations.
Global Contract Purchase Agreements
Oracle Purchasing introduces the new global contract purchase agreements document
with 11.5.10. Global contract purchase agreements, like global blanket agreements,
enable companies to centralize supplier relationship management and to standardize
terms and conditions across all enabled organizations when doing business with a given
supplier. Buying organizations may find global contract purchase agreements especially
helpful when considering how best to use Oracle Advanced Pricing capabilities with a
central procurement organization. In addition, global contract purchase agreements may
be helpful in some situations when extending a single negotiated supplier catalog across
many organizations.
Procurement Execution in Shared Services Environments
Buyers in central procurement organizations are typically responsible for procuring on
behalf of multiple demand raising organizations within a company. With this release,
Oracle Purchasing provides a powerful framework from which an organization's complex
85
procurement environment can be mapped directly to system execution. For example,
enterprises can:
• Map purchase order generating organizations (Shared Service Centers) to demand
raising organizations via Global Blanket Agreements or Global Contract Purchase
Agreements.
• Continue to rely on automatic document creation to preserve automated
generation of purchase orders where possible, even when the purchase order will
be created in a different organization than where demand originated.
• Extend buyer productivity through access to central procurement functions from
the AutoCreate workbench when manual intervention or manual purchase order
creation is required.
• Receiving Accounting & Drop Shipments
Regardless of which organization issued the purchase order, receipts continue to be
processed in the demand raising organizations. To reconcile accounting between
organizations, companies model their financial relationships and the system initiates and
executes appropriate cost transfer/invoicing accounting transactions, especially if these
flows cross Legal Entities and Sets of Books. Business transactions like receipts, invoice
matches and payments automatically initiate the appropriate cost transfer or
inter-company invoicing accounting transactions based on the rules defined in the
financial relationship between the purchase order creation and receiving organizations.
Please refer to the About Oracle Inventory in Oracle Supply Chain Management
document for details on Financial Flow Modeling.
The drop shipment process has also modified to go across traditional organization
boundaries. Companies can have local or central order capture organizations that
interface with a center-led procurement shared services organization. In fact, the order
capture organization and purchasing organization can even belong to different Sets of
Books. The appropriate accounting and inter-company invoicing transactions are
automatically initiated based on the rules defined in the financial relationship between
the sales order and purchase order creation organizations.
5.1.3.6 AutoCreate and Purchase Order Entry Usability
The following modifications were made to the AutoCreate and Enter Purchase Order
windows in order to enhance buyer productivity:
• Increased size of AutoCreate window to display more requisition lines
• Increased size of Enter Purchase Order window to display more order lines
• Reduced pop up messages
• Provided 'Reassign Buyer' option in the AutoCreate window
5.1.3.7 Gapless Self-Bill Invoice Numbering
Self-bill Invoices (SBI) is an automated invoicing where the buying company creates an
invoice on behalf of the supplier. This process lowers the invoicing costs, errors and
cycle time for both buyers and suppliers. SBIs include evaluated receipt settlements,
debit memos, and purchase price adjustment invoices. Certain countries require that
invoice numbers on SBIs be gapless.
Oracle Purchasing now supports gapless invoice numbering for all self-billing invoices.
The buying organization has the flexibility to turn on or off gapless SBI numbering by
supplier site or by operating unit.
5.1.3.8 FDA CFR 21 Compliance
Oracle Purchasing now aids compliance with the FDA Code of Federal Regulations 21
86
Part 11 requirements governing the technical aspects of computer and software systems
that are used by manufacturers. Specifically, Oracle Purchasing now satisfies the two
primary requirements of CFR Part 11: electronic records ("e-Records") and electronic
signatures ("e-Signatures").
The new functionality is manifest in two areas: the Approved Supplier List (ASL) and
Receiving Inspections with Oracle Quality. Changes to an ASL attribute are now
recorded through an e-Record to an evidence store. Likewise, an e-Record snapshot is
also stored for Receiving Inspections using Oracle Quality. Additionally, Receiving
Inspections using Oracle Quality capture an e-Signature through a self-service browser
window. Please refer to the Oracle Quality RCD for additional information.
5.1.3.9 Logistics
Receiving Open Interface Enhancements
Most companies managing receiving docks in a high volume environment use barcodes
and RF scanning devices to record shipment and receipt information. Such capabilities
are readily available when receiving using the Oracle Mobile Supply Chain (Oracle
MSCA) or Oracle Warehouse Management (Oracle WMS) applications. Should a
company have some other form of barcode/RF support then the Receiving Open Interface
(ROI) provides a mechanism to process the generated transactions. Substantial
improvements to ROI include:
• Support for most receiving transactions, including Advanced Shipment Notices
(ASN), receipts, deliveries, inspections, and transfers.
• Multi-stage transaction processing. For example, a user may import related
Receive, Transfer and Deliver transactions as and when they occur.
• Receiving transactions against Return Material Authorizations (RMA), Internal
Orders, and Inter-organizational transfers.
• The import of transactions in "Batch," "Immediate," and "Online" modes.
These enhancements are intended to significantly improve the productivity of personnel
working on receiving docks by minimizing manual data entry requirements.
Nested License Plate Number (LPN) and Lot/Serial
• Suppliers can include Lot/Serial and LPN information on Advance Shipment
Notices (ASNs). This information is automatically captured in subsequent receipt
transactions, thus greatly reducing manual data entry at time of receipt.
• Users can define lot and serial information on all receiving transactions imported
via ROI. These include receipts, transfers, inspections, deliveries, returns and
corrections.
• Users may now use License Plate Numbers (LPNs) to improve the efficiency of
the receiving process by grouping items and transacting on the group as a whole.
This allows companies to consolidate material from one or more shipments into
one LPN and track at the container level. Users can also record LPN pack and
unpack events during the receiving process to accurately reflect the changing
levels of aggregation. Nested LPNs can also be defined to emulate containers
within containers. Please note that ability to use LPNs in the receiving process is
available only for receiving transactions imported via the receiving open interface.
• Receiving Locator Support
• Subinventory and locator functionality has been extended to the receiving dock
allowing for an added level of granularity to receiving locations. It is now possible
to specify receiving subinventories and locators on receiving transactions in
addition to the receiving location, when importing these transactions via the open
87
interface. This makes it easier to accurately track material on the receiving dock.
• Through integration with Oracle Inventory, receiving personnel now have access
to the Inventory Material Workbench, providing a view of all the material
contained in receiving sub-inventories and locators.
• Buyer Driven Logistics Management
Some companies choose to manage inbound shipments from their supply base. Oracle
Purchasing is now integrated with Oracle Transportation Management to provide
transportation execution personnel and planners visibility into open purchase orders,
shipments available for pickup at supplier sites, and in-transit shipments. Based on this
information, planners can create an optimal route for their logistics fleet. This route can
include a combination of supplier locations for goods pickup (inbound shipments) and
customer locations for shipment drop-off (outbound shipments). This feature allows
companies to greatly reduce freight costs by optimizing their transportation plans.
Drop Ship Enhancements
The integrated business flow between Oracle Order Management and Oracle Purchasing
facilitating Drop Shipments has been streamlined. Enhancements include:
• Improved Purchase Order Communication: Drop Ship Purchase Order
information communicated to suppliers includes all relevant details about the end
customer (customer name, ship-to contact, etc.).
• Automatic Document Synchronization: Customer requested changes to sales
orders (for example, Order Cancellation, Quantity Increase, Date Changes) in
Oracle Order management would now automatically flow down to the
corresponding purchasing documents. This ensures that the Sales Order and the
corresponding Purchase Order are always in sync, hence eliminating the need for
manual data synchronization. Changes to the Sales Order are automatically
captured as revisions to the corresponding Purchase Order. These changes can be
automatically communicated to the supplier as a purchase order change.
• ASN Auto-generation of Receipt: Suppliers send Advanced Shipment Notices
(ASN) to notify the purchasing organization that goods have been shipped to the
customer. Buying organizations can now choose to automatically record receipt
transactions against the supplier ASN. This receipt enables buying organizations
to recognize liability and to optionally auto-generate the invoice as soon as the
goods are shipped to the end customer. The receipt can also be used to
automatically generate an invoice for the end customer in Oracle Accounts
Receivable.
• Timestamps for Improved Logistics Management
Users can now specify a time associated with need by and promised dates on requisitions
and purchase orders. This allows customers to be more specific in communicating their
requirements to suppliers. Oracle Purchasing also allows capture of timestamps for
receiving transactions.
Some organizations may find the additional time component useful to more effectively
plan resource requirements, receiving activity and downstream material usage, especially
in low lead-time, JIT environments.
5.1.3.10 Procurement Contracts
Oracle Procurement Contracts provides robust contract management capabilities for
procurement professionals, including a sophisticated contract terms library, robust
deliverables tracking and formal change management. Organizations can use these
capabilities to minimize exposure to contractual risks, maximize their buying power, and
88
eliminate erroneous payments- from sourcing through contract award, order execution
through termination or renewals. Oracle Purchasing allows users to leverage these new
capabilities in various aspects of the procurement flow - contract authoring with
sophisticated terms, deliverables definition and tracking, contract binding and document
signatures, document communication in PDF format, contract attachments with
versioning, and more.
Please refer to Procurement Contracts RCD for more information.
5.1.3.11 Pricing
Model Complex Pricing with Oracle Advanced Pricing
Oracle Advanced Pricing is now integrated with Oracle Purchasing and Oracle
iProcurement. Oracle Advanced Pricing is a flexible pricing engine capable of addressing
complex pricing needs of customers. Using Oracle Advanced Pricing, purchasing
professionals can setup complex pricing structures in the form of price lists, price
formulas and modifiers. Price lists contain the basic information that associates price and
currency with an item, service, group of products or services, or sub-component. Pricing
formulas let you model mathematical relationships for product pricing using certain order
attributes. Price modifiers allow you to setup discounts or surcharges that can be applied
on top of base prices.
To price requisitions and purchase orders based on pricing rules setup in Oracle
Advanced Pricing, the requisition or purchase order line need simply reference a contract
purchase agreement.
Retroactive Price Changes
Prices for items on blanket agreements can change over the effective period of an
agreement as a result of ongoing negotiations between the buyer and the supplier. In fact,
it is common practice in certain industries to initiate and execute against an agreement
with an interim price. A firm price may get finalized several months into the life of the
agreement. In these scenarios it is possible that the updated price is applicable
retroactively. Oracle Purchasing allows buyers to make price changes on Global Blanket
Agreements and on Blanket Agreements. With 11.5.9, Oracle Purchasing allowed
automatic updates to orders (Standard POs and Blanket Releases) referencing the
modified agreements with the latest pricing as long as there was no receiving or
invoicing activity against these orders. With this release Oracle Purchasing can
optionally update prices on orders to reflect the latest agreement price, even if there has
been receiving and invoicing activities against them. Additionally, for orders that have
been received against, Oracle Purchasing automatically adjusts the accrued liability to
reflect the latest pricing. Finally, for orders that have been invoiced, Oracle Purchasing
automatically generates Price Adjustment Invoices in Oracle Payables. Depending on the
nature of the change, the Payables department can then process either a payment or a
Debit Memo request against the Price Adjustment Invoice.
Price Update Flexibility on Purchase Orders, Releases
Users can now manually change prices on purchase orders or releases even if there have
been receiving and invoicing activities against them. This greatly simplifies the
procurement process for goods or services where pricing is volatile and changes often
need to be made after the purchase order has been created and possibly even after a
purchase order has been received or invoiced.
Custom Pricing APIs
The Custom Pricing APIs can be used to complement the integration with Oracle
Advanced Pricing and can also be used with the Retroactive Price Changes feature. There
89
are three new APIs supported in Oracle Purchasing:
• Custom Pricing Date API: Allows businesses to call custom logic (e.g, pl/sql
code) to determine the pricing date for purchases. For example, a company can
use this API to set the pricing date as the requisition approval date or the expected
shipment date.
• Custom Requisition Pricing API: Allows businesses to add logic to adjust the
price on requisitions based on referenced source documents.
• Custom PO/Release Pricing API: Allows businesses to add logic to adjust the
price on standard purchase orders and releases based on referenced source
documents.
5.1.3.12 Purchase Order Printing and Communication
Oracle Purchasing includes a powerful and flexible solution for creating and formatting
purchase orders in Portable Document Format (PDF). In Oracle Purchasing, the buyer
can view a draft version of the PDF purchase order. After approval, generated PDF
documents can be sent via email, print, or fax and are viewable online via Oracle
iSupplier Portal. You can set up layout templates that define how your purchase orders
should be formatted, including the company logo, headers, footers, and watermarking. If
Procurement Contracts is being used, the associated Terms and Conditions can be added
to the PDF document. For more information, please see the dedicated document for that
new product.
90

1158 To 11510

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

1158 To 11510

Transféré par

Droits d'auteur :

Formats disponibles

RELEASE CONTENT DOCUMENT

Generated by: RCD Search Tool

Copyright © 2005 Oracle Corporation

1.2 Oracle Cash Management.............................................................................................................................19

1.3 Oracle General Ledger..................................................................................................................................23

1.4 Oracle Payables.............................................................................................................................................27

1.5 Oracle Receivables.......................................................................................................................................31

3.3 Oracle Engineering.......................................................................................................................................48

3.4 Oracle Quality...............................................................................................................................................49

3.5 Oracle Work in Process................................................................................................................................63

1.1 Oracle Assets

2.1 Oracle Inventory Management

3.1 Oracle Bills of Material

4.1 Oracle Order Management

5.1 Oracle Purchasing

Vous aimerez peut-être aussi