Академический Документы
Профессиональный Документы
Культура Документы
Procurement
Releases 12.1 and 12.2 (inclusive of 12.0.2 – 12.0.7)
1. Disclaimer 1
2. Introduction 2
2.1. Purpose of Document 2
3. New and Changed Features in Procurement 3
3.1. Oracle iProcurement 3
3.1.1. Overview 3
3.1.2. Release 12.1.1 3
3.1.2.1. Change Management for Internal Requisitions 3
3.1.3. Release 12.1.2 3
3.1.3.1. In-line Commodity Classification 3
3.1.4. Release 12.1.3+ 4
3.1.4.1. Information Template Enhancements 4
3.1.4.2. Primary Favorite Charge Account can take Precedence over Employee Charge Account 4
3.1.4.3. Dual Budgetary Control Support 4
3.1.4.4. Attachment Support in Change Order Process 4
3.1.4.5. Account Generator Support in Requisition Import 4
3.1.4.6. Requisition Update PL/SQL API 4
3.1.4.7. Approve Requisitions On-the-Go 4
3.1.5. Release 12.2 5
3.1.5.1. Automatic Updates to Encumbrance (GL) Date 5
3.1.5.2. Visibility of Item Master Attachments in Item Search and Detail Pages 5
3.1.6. Release 12.2.4 5
3.1.6.1. iProcurement One-Step Check Out 5
3.2. Oracle iProcurement Extensions for Oracle Endeca 5
3.2.1. Overview 5
3.2.2. Release 12.1.3+ 6
3.2.2.1. Search All Catalogs 6
3.2.2.2. Advanced Filtering 6
3.2.2.3. Item Comparison 6
3.2.2.4. Easy to Implement and Configure 6
3.3. Oracle Mobile iProcurement for Oracle E-Business Suite 6
3.3.1. Version 1.1.0 6
3.3.1.1. Mobile Foundation Updates 6
3.3.1.2. Accessibility Improvements 7
3.4. Oracle iSupplier Portal 7
3.4.1. Overview 7
3.4.2. Release 12.0.3 (RUP3) 7
3.4.2.1. Forward Port of JFMIP/FSIO from 11.5.10 to R12 for Federal Customers 7
3.4.3. Release 12.1.1 8
3.4.3.1. Dispute Resolution for G-Log Invoices 8
3.4.3.2. AP/AR Netting 8
3.4.3.3. Products and Services Search 8
3.4.3.4. Business Classification Recertification 8
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document ii
3.4.3.5. Third Party Payments 9
3.4.4. Release 12.1.3 9
3.4.4.1. Work Confirmation Correction 9
3.4.5. Release 12.2 9
3.4.5.1. Integrate with Oracle Flow Manufacturing to View and Edit E-Kanbans 9
3.4.5.2. Capture Additional Supplier Contact details 9
3.5. Oracle Procurement Contracts 9
3.5.1. Overview 9
3.5.2. Release 12.0.2 (RUP2) 9
3.5.2.1. User-Defined Variables with PL/SQL Procedures as Source 9
3.5.3. Release 12.1.1 10
3.5.3.1. Structured Terms Authoring in Repository Contracts 10
3.5.3.2. Secure Enterprise Search 10
3.5.3.3. Deliverable Payment Holds 10
3.5.4. Release 12.1.2 12
3.5.4.1. Author Individual Clauses in Microsoft Word 12
3.5.4.2. Project Manager Dashboard for Maintenance of Procurement Deliverables 12
3.5.5. Release 12.1.3+ 13
3.5.5.1. Apply Multiple Templates to a Sourcing or Purchasing Document 13
3.5.5.2. APIs for Importing Templates, Rules, Questions and Constants 13
3.5.5.3. New Clause Descriptor Field 13
3.5.5.4. Clause Mandatory Attribute at Rule Level 13
3.5.5.5. Clause Section Placement by Contract Expert 13
3.5.5.6. Deletion of Provisional Sections from Solicitation to Award 14
3.5.5.7. Instruction Text 14
3.5.5.8. Multi-Row Variables 14
3.5.5.9. Display Clause Number and Sort by Clause Number 14
3.5.5.10. Contract Expert History 15
3.5.5.11. Delete Multiple Clauses, Sections and Deliverables 15
3.5.5.12. Defaulting Rules for Contract Administrator 15
3.5.5.13. Purge Process for Repository Contracts 15
3.5.6. Release 12.2 15
3.5.6.1. Repository Contracts Configurability Enhancements 15
3.5.6.2. UDA support for Deliverables 16
3.5.6.3. MS Word 2010 Certification 16
3.5.6.4. Contract Expert Performance Improvements 16
3.5.7. Release 12.2.4 16
3.5.7.1. Repository Contracts Printing Enhancement 16
3.6. Oracle Purchasing 16
3.6.1. Overview 16
3.6.2. Release 12.0.2 (RUP2) 16
3.6.2.1. Integration between Oracle Purchasing and Oracle Transportation Management 16
3.6.2.2. iSetup APIs 17
3.6.3. Release 12.0.6 (RUP6) 17
3.6.3.1. Contract Commitments Integration with Self Service Purchasing (Oracle Public Sector Financials
International) 17
3.6.4. Release 12.1.1 17
3.6.4.1. PO and Requisition Mass Update 17
3.6.4.2. Enable All Sites for Global Contract Purchase Agreements 17
3.6.4.3. FPDS-NG Integration 18
3.6.5. Release 12.1.2 18
3.6.5.1. Purchase Order Pricing Enhancement 18
3.6.5.2. Project Security within Oracle Purchasing 18
3.6.5.3. Procurement Web Services – Purchasing 18
3.6.6. Release 12.1.3 19
3.6.6.1. Landed Cost Management (LCM) Integration 19
3.6.6.2. Asset Lifecycle Management (ALM) Integration 19
3.6.7. Release 12.1.3+ 19
3.6.7.1. Encumbered Document Revisions without Un-reserving Funds 19
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iii
3.6.7.2. Approvals Management Engine (AME) for PO Approvals 19
3.6.7.3. Current and Pending Approvers in Action History Region 20
3.6.7.4. Withdrawing Purchase Order after Submitted for Approval 20
3.6.7.5. Configurable Notification in Purchase Order 20
3.6.7.6. Outside Processing Lines in Global Blanket Agreements (GBPAs) 20
3.6.7.7. Support for Importing Complex Purchase Orders 20
3.6.7.8. New ASL APIs 20
3.6.7.9. Buyer Work Center Session Preferences 21
3.6.7.10. Purchasing Document Open Interface (PDOI) Enhancements 21
3.6.7.11. PO Business Service Object (BSO) Webservices 21
3.6.7.12. Lead-Time based Promised Date calculation 21
3.6.7.13. Approve Purchase Orders On-the-Go 21
3.6.8. Release 12.2 22
3.6.8.1. Automatic Updates to Encumbrance (GL) Date 22
3.6.8.2. Support for Additional Extension Hooks 22
3.6.9. Release 12.2.4 22
3.6.9.1. Spreadsheet based authoring of PO Lines 22
3.7. Oracle Mobile Procurement for Oracle E-Business Suite 22
3.7.1. Version 1.1.0 22
3.7.1.1. Mobile Foundation Updates 22
3.7.1.2. Accessibility Improvements 23
3.8. Oracle Services Procurement 23
3.8.1. Overview 23
3.8.2. Release 12.1.1 23
3.8.2.1. Time Reporting and Contractor Assignment Flexibility 23
3.8.3. Release 12.1.2 23
3.8.3.1. Oracle Projects – Work Confirmations 23
3.8.4. Release 12.2.4 24
3.8.4.1. Advances, Recoupment and Retainage for Standard Purchase Orders 24
3.8.4.2. Support for Inventory Destinations in Complex Purchase Orders 24
3.9. Oracle Sourcing 24
3.9.1. Overview 24
3.9.2. Release 12.1.1 24
3.9.2.1. Two Stage Evaluation of RFP 24
3.9.2.2. Two Stage RFQ – Surrogate Bids 25
3.9.2.3. Supplier Response PDF 25
3.9.2.4. Enhanced Spreadsheet Support 25
3.9.2.5. Countdown Clock 26
3.9.2.6. Price Tier Enhancements 26
3.9.2.7. Cost Factor Enhancements 27
3.9.3. Release 12.1.2 27
3.9.3.1. Earnest Money Deposit 27
3.9.4. Release 12.1.3 28
3.9.4.1. Requester Field in the Sourcing Header 28
3.9.4.2. Descriptive Flex Field (DFF) in Oracle Sourcing Header 28
3.9.4.3. Landed Cost Management (LCM) Integration 29
3.9.5. Release 12.1.3+ 29
3.9.5.1. Online Discussions Attachments 29
3.9.5.2. Terms and Conditions Controls 29
3.9.5.3. Lot Price Summation 30
3.9.5.4. Delete Supervisor from Collaboration Team 30
3.9.5.5. Sort and Delete Suppliers from Invited Suppliers Page 30
3.9.6. Release 12.2 30
3.9.6.1. Add Requisition lines to a Draft Negotiation (RFx & Auction) 30
3.9.6.2. Response Withdrawal 30
3.9.6.3. Track Amendment Acknowledgements 30
3.9.6.4. Staggered Awards 31
3.9.6.5. Import of Price Breaks 31
3.9.6.6. Negative Cost Factors 31
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iv
3.9.6.7. Sourcing APIs 31
3.9.7. Release 12.2.4 31
3.9.7.1. Mass Update of Buyers 31
3.9.7.2. Surrogate Quotes for Suppliers without an User Account 31
3.10. Oracle Sourcing Optimization 32
3.10.1. Overview 32
3.10.2. Release 12.1.1 32
3.10.2.1. Sourcing Optimization Enhancements 32
3.10.2.2. Price Tier Optimization 32
3.10.2.3. Supplier Incentives 33
3.11. Oracle Spend Classification 33
3.11.1. Overview 33
3.11.2. Release 12.1.2 34
3.11.2.1. Integration with Oracle Procurement and Spend Analytics 7.9.6 34
3.11.2.2. Knowledge Base Creation and Incremental Updates 34
3.11.2.3. Multiple Knowledge Bases 34
3.11.2.4. Easy to Use User Interface 34
3.11.2.5. Export and Import to Excel 35
3.11.2.6. Ability to Classify Data into Multiple Taxonomies 35
3.11.2.7. In-line Commodity Classification 35
3.11.3. Release 12.2 36
3.11.3.1. Reclassify Historical Data 36
3.11.3.2. Asynchronous Approval Flow 36
3.11.3.3. Enhanced Training Data Upload 36
3.11.3.4. Enhanced Tracking Capabilities 36
3.11.3.5. Improvements in Analyzing Batches and Excel to Export 36
3.11.3.6. Increased Flexibility in Resetting Data 37
3.11.4. Release 12.2.4 37
3.11.4.1. Delete Classification Batch 37
3.11.4.2. Run Classification on Selected Transactions 37
3.11.4.3. Simplified User Interface 37
3.11.4.4. Prevent Reset of Transactions in Classified, Unapproved Batches 37
3.12. Oracle Supplier Hub 37
3.12.1. Overview 37
3.12.2. Release 12.1.1+ 38
3.13. Oracle Supplier Lifecycle Management 38
3.13.1. Overview 38
3.13.2. Release 12.1.1+ 39
3.13.2.1. 360° Supplier View 39
3.13.2.2. Supplier Search 39
3.13.2.3. Supplier Profile Management (including Self-Service) 39
3.13.2.4. Extended Supplier Profile 39
3.13.2.5. Registration and On-Boarding of New Suppliers 40
3.13.2.6. Qualification Management 40
3.13.2.7. Compliance and Profile Audits 41
3.13.2.8. Performance Evaluation 41
3.13.2.9. Supplier Notifications 41
3.13.3. Release 12.1.3+ 41
3.13.3.1. Mandatory Internal Requirements 41
3.13.3.2. Associate Address to Contacts 42
3.13.3.3. Keyword Search 42
3.13.3.4. Default User Creation 42
3.13.3.5. Reinstate a Rejected Supplier Request 42
3.13.3.6. Registration Approval Workflow Enhancements 42
3.13.3.7. Streamlined Prospective Supplier Registration Process 43
3.13.3.8. View Prospective Supplier Registration Status 43
3.13.4. Release 12.2.4 43
3.13.4.1. Registration Approval Workflow Enhancements 43
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document v
3.13.4.2. Approval History on Supplier Profile 43
3.14. Oracle Supplier Network 43
3.14.1. Overview 43
3.14.2. Version 5.0 44
3.14.2.1. Consolidated Hub Administration 44
3.14.2.2. Production Routing Controls 44
3.14.2.3. UTF-8 Support 44
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document vi
1. Disclaimer
This Release Content Document (RCD) describes product features that are proposed for
the specified releases of the Oracle E-Business Suite. This document describes new or
changed functionality only. Existing functionality from prior releases is not described. It
is intended solely to help you assess the business benefits of upgrading to the specified
release of the Oracle E-Business Suite.
This document in any form, software or printed matter, contains proprietary information
that is the exclusive property of Oracle. Your access to and use of this confidential
material is subject to the terms and conditions of your Oracle Software License and
Service Agreement, which has been executed and with which you agree to comply. This
document and information contained herein may not be disclosed, copied, reproduced or
distributed to anyone outside Oracle without prior written consent of Oracle. This
document is not part of your license agreement nor can it be incorporated into any
contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in
planning for the implementation and upgrade of the product features described. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all
features described in this document without risking significant destabilization of the code.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 1
2. Introduction
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 2
3. New and Changed Features in Procurement
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 3
3.1.4. Release 12.1.3+
3.1.4.2. Primary Favorite Charge Account can take Precedence over Employee
Charge Account
Employees can define Favorite Charge Accounts in iProcurement Preferences, and can
mark one of those accounts as the Primary Favorite. iProcurement uses a series of rules to
generate charge accounts during the checkout process. Under certain circumstances,
iProcurement gets the charge account from the employee record in HR. But if that is not
specified, it defaults to the Primary Favorite. However, if an employee needs the Primary
Favorite to override the charge account on their HR record, they can now do so with the
‘Override Employee Charge Account’ preference in iProcurement.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 4
Employees can quickly filter approval requests by sender or subject, review header and
line details, action history and comments, and respond back with their approval or
rejection, right from their smartphone.
This feature is forward ported to 12.2.3.
For a full description, refer to the E-Business Suite Applications Technology Release
Content Document.
3.1.5. Release 12.2
3.1.5.2. Visibility of Item Master Attachments in Item Search and Detail Pages
While viewing the details of the item after having searched for them in the store,
iProcurement users will now be able to see attachments associated with the Item Master
for those items. This will enable users to gain access to item attachments like design
specifications etc, and thus better equip them to choose the right product to order.
3.1.6. Release 12.2.4
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 5
3.2.2. Release 12.1.3+
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 6
• Diagnostics Improvements
3.4.2.1. Forward Port of JFMIP/FSIO from 11.5.10 to R12 for Federal Customers
This feature addresses the delta between 11.5.10 functionality and R12 functionality,
related to meeting the requirements given by JFMIP in 2004 for iSupplier Portal. The
following iSupplier Portal pages are impacted:
3.4.2.1.1. Supplier Search Page
The DUNS number is available at the supplier site level for CCR Suppliers. A user
can retrieve distinct supplier records while performing the search using the DUNS
Number.
3.4.2.1.2. Organization Page
A CCR Supplier indicator was provided on the Organization page. If the supplier is a
CCR Supplier, then the Taxpayer ID, DUNS Number and SIC attributes, and Bank
Account tab are rendered view-only.
3.4.2.1.3. Manage Sites Page / Update Address Page
In the Update Address page for CCR Suppliers, the attributes Country, Address
Lines, City, State, Postal Code, Province, DUNS Number, and Pay Site are view-
only.
A new attribute, DUNS Number, was added and displayed in the Identification tab
within the Manage Sites page, for Federal Financials installations. If the supplier site
is a CCR supplier site, the user cannot update this field.
The newly added icon “View CCR Supplier” allows the user to access the General
Information page from the federal application, to view CCR supplier site-specific
data.
3.4.2.1.4. Tax Details Page
An indicative comment was provided on the tax details page; it identifies the Tax
Details of a CCR vendor.
3.4.2.1.5. Bank Details Page
A CCR indicator appears when the assignment level is Supplier Site, and if the site is
a CCR site. For a CCR Site, adding new bank accounts, modifying any bank, branch
or account information, changing the priority of bank accounts and update bank
account number is not possible.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 7
3.4.2.1.6. Invoice Management page
A descriptive comment “CCR Site” was added to the Invoice Management page.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 8
3.4.3.5. Third Party Payments
Third party payments help parties engaged in business set off their liabilities without
directly paying them. This reduces the direct funds movements and enables transactions
to be settled easily. When customers are making payments from their Payables system,
there might be instructions from the supplier to make payment to a different party (Third
Party). In that case the remittance of the payment has to be made to the Third Party.
Establishing Third Party Payment relationship can be done from iSupplier Portal.
Suppliers can add a new relationship and find and update existing relationships.
3.4.4. Release 12.1.3
3.4.5.1. Integrate with Oracle Flow Manufacturing to View and Edit E-Kanbans
Oracle iSupplier Portal integrates with the E-Kanban feature of Oracle Flow
Manufacturing. Suppliers can now use iSupplier Portal to view a summary of their E-
Kanbans and update the status on their E-Kanbans.
For more information, consult the Manufacturing RCD.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 9
Contract Terms Library and the values are provided by users when they author contract
terms and conditions.
Contracts customers have requested the ability to create user-defined variables whose
values can be sourced from descriptive flex fields, custom tables, or even a Purchase
Agreement or RFQ that are not supported as system variables. With RUP2, user-defined
variable values can now be sourced from any data source. The data source is
encapsulated as a custom PL/SQL procedure that is associated to the user-defined
variable definition. As a user authors contract terms and conditions, the system will
automatically obtain the values from the data source eliminating the need for users to
manually enter them.
3.5.3. Release 12.1.1
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 10
The following features enable users to track such requirements and to automate the
payment hold process.
This feature requires additional products to be licensed for full functionality described
below, including Financials and Services Procurement.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 11
3.5.4. Release 12.1.2
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 12
3.5.5. Release 12.1.3+
Contract Expert rules specified in the original template continue to govern exclusively.
For instance, if a new template is added that contains Contract Expert rules these rules
will not be retained as part of the contract.
Migrating elements from the Contract Terms Library from one environment to another is
sometimes necessary, for instance to graduate templates and rules created in a test
instance into production. Once created in a test instance, it can be time-consuming to
reproduce these rules in production.
Now, interfaces (APIs) can be used by technical staff to efficiently upload and create new
entities. New APIs include:
• Templates
• Rules, and
• Questions and Constants
APIs can be used to create new entities and update existing templates and rules. These
APIs return error and warning messages to simplify troubleshooting.
A clause descriptor field displays on the Contract Template, Rules Definition and
Contract Terms pages. This field can be updated from Contract template and Rules
definitions page. This field is hidden by default, and references a user-defined lookup for
the list of values.
If undefined at the clause level, the template level setup will be used to determine
whether a Contract Expert suggested clause should be added as mandatory or optional.
Today when a clause is added to a contract via Contract Expert, it is added to the default
section. Now, contract administrators have the flexibility to add the clause to different
sections based on attributes of the contract.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 13
When creating a clause, the contract administrator may insert a variable such as the
contract printing format (see image below). The user can now define the appropriate
section for a clause based on variable values. When the clause is added to the document
by the Contract Expert, the clause will get added to the section based on the value of the
variable of the document.
There are a number of clauses which are specific to a sourcing (Solicitation) document
and should not move onto the final contract. These are called Provisional Clauses.
Now, the user can indicate that certain sections are provisional. Provisional Sections and
their clauses do not flow to the award document when the award contract is created from
the solicitation document.
The clauses in a document may contain URLs of external websites where additional
information is available. One can add the destination URL in the instruction text of the
clause with the appropriate HTML tags. This will now make the URL available as a
hyperlink which will be available for the user to click from the clause details page.
Currently the variable field in a contract clause only accepts single values. However,
there is a need to provide multiple values for a single variable in the form of an n X n
matrix. For example, the variable contact number can have 3 columns – Country, City
and Number with multiple rows. Users can now leverage the UDA (User Defined
Attribute) framework to set up attributes groups and refer these groups in Multi-Row
Variables.
The variable creation page will allow the user to designate the variable as multi-row and
associate attributes and printing RTF templates to them. These variables when available
in a contract for a Sourcing or Purchasing document will allow the user to enter multiple
rows for a given variable and this will be printed in the PDF document as per the defined
RTF template. This is available for buyer updateable variables and does not support
PL/SQL values.
The clause number may be used by contracting professionals for many purposes. Now,
the clause number may be used for searching, updating or adding clauses. The clause
number has been added to the Contract Terms page, the Search results page for clauses,
and the summary page after Contract Expert in run.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 14
It is also required to sort the clauses in a section by the clause number. There will be a
button available which will sort all the clauses in a section by the clause number. This is
currently optimized for the Federal clause numbering scheme as follows:
<NUMBER 1>.<NUMBER 2>-<NUMBER 3><Some text>
Search is an alphanumeric sort on the clause number. A code hook is provided, enabling
customers to embed desired sorting logic (for example, the numbering schema is
different) which will be called when sorting occurs.
Contract Expert History allows buyers to view the Contract Expert questions, the
responses provided, and the resultant policy deviations and net clause additions. For
revisions in orders or amendments in a Sourcing document, the user will also be able to
enter the amendment description and also view it in the Contract Expert summary page.
This capability will simplify audit requirements and will provide details around the
responses provided and changes in different revisions and amendments.
A delete function on the Contract Terms page allows users to delete multiple clauses,
sections and deliverables from a draft document. Clauses marked as mandatory will not
be allowed to be deleted.
The Check Contract Administrator Warning is displayed today when the user validates
the Contract terms or tries to publish / submit for approval a Sourcing or Purchasing
document that has contract terms added to the document. For purchasing documents,
users can now provide the default value for the contract administrator using the profile
option OKC: Default Contract Administrator for Contract Terms. We will not display the
warning message for a Sourcing document, though the feature will still be available.
Repository Contracts now provides greater flexibility and improved capabilities to the
contracting professional. The contract administrator can now control the different entities
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 15
that are available for each contract type. Custom signature and approval workflows may
be defined individually for each contract type, which enhances the applicability of
repository contracts in different business scenarios. Customers can leverage repository
contracts to integrate them within their existing business flows in different application
modules. Repository contracts also support UDA (User Defined Attributes) pages. So,
each contract can contain multiple additional pages to capture specific business
information. This will allow the repository contracts to be used a as solution for modeling
different document management requirements along with their own process lifecycle.
The Contract Expert engine now has improved performance of the complete flow.
Impacts include faster UI and better formatting of the question and answer fields. There
is no change to the Contract Expert process itself.
UDA (User Defined Attributes) fields may be used to capture additional data for each
contract type. The Contract Type setup page now allows the contract administrator to
specify the manner in which UDA attributes are printed by selecting appropriate data and
layout templates.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 16
Oracle Transportation Management combines transportation planning and execution
with freight payment, inbound freight logistics, and freight rating and routing. Oracle
Transportation Management adds the following features and enhancements to Oracle
Purchasing:
Carrier selection and tender
Freight rating and routing
Actual ship quantities update and re-rate
Freight payment, freight payment audit, and approval
Visible in-transit statuses
Inbound carrier selection
Inbound in-transit statuses
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 17
3.6.4.3. FPDS-NG Integration
Most U.S. Federal Government agencies must track and report their contract activity in a
variety of ways, including publishing certain contract activity to the Federal Procurement
Data System – Next Generation (FPDS-NG). Oracle Purchasing Release 12.1.1 provides
support for integration with FPDS-NG by ensuring that required contract and vendor data
elements are captured in the system and that submission data passes all required FPDS-
NG validations.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 18
• Requisition: Create Requisition, Delete Requisition, Query Requisition, and
Update Requisition.
Note that these support requisitions in iProcurement as well as Purchasing.
Oracle Landed Cost Management gives organizations financial visibility into their
extended supply chain costs including transportation, handling fees, regulatory duties and
taxes and helps them to determine the landed cost of the material for transactional
purposes. This allows organizations to have better control over procurement costs,
maximize profits, increase competitiveness, and ensures that complex trade activities are
compliant with regulatory mandates.
This integration allows purchasing users to simulate the Landed Costs at the creation time
of purchase orders, allowing better procurement decisions based on the estimated Landed
Cost of the items.
In EBS Release 12.1.2, the implementation of encumbrance reversal for SCM was
limited to Inventory and Expense Receiving transactions. Now in Release 12.1.3, this
functionality has been extended to ‘Shop Floor’ destination Purchase Orders, where the
distributions will be created under WIP transactions. Purchasing will support
encumbering funds for Purchase Orders generated from eAM (with a ‘Shop Floor’
destination) during the approval process.
All public sector organizations, such as municipal, state, provincial and federal
government organizations are required to encumber or reserve funds that have been
committed to a supply purchase order. Therefore, prior to approval of any purchasing
document, the available funds must be checked and reserved against the available budget
for the specified account code combination. Enhancement is key for budgetary control.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 19
approving the PO documents. Enterprises can use the predefined AME transaction type
and PO workflow process or they can create custom transaction type and workflow
process based on their business requirements. Buyers can add adhoc Approvers and
Electronic Signatories using the Approval Options screen. The AME process can also be
used to add multiple reviewers and electronic signatories to the approval hierarchy.
This feature is forward-ported to 12.2.4.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 20
3.6.7.9. Buyer Work Center Session Preferences
Purchasing now provides user preferences for setting default values in the Buyer Work
Center. Default values for various attributes can be specified using the Preferences page
of Buyer Work Center for quick and easy creation of Purchase Orders. These values are
defaulted when a new Purchase Order is created, thereby reducing repeated data entry.
This feature is forward-ported to 12.2.4.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 21
3.6.8. Release 12.2
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 22
3.7.1.2. Accessibility Improvements
Improvements were made in the Purchase Order details page, related information
messages, contextual tab bar and person contact card.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 23
3.8.4. Release 12.2.4
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 24
By adding support for two stage RFP in Oracle Sourcing, organizations can help ensure a
more impartial evaluation of supplier bids based on the independent evaluation of the
technical capabilities and then the commercial terms of a supplier’s bid.
Response – Lines
Bid Total
Calculated
Instantly
Line Filter
Predefined
List of
Link to Values
Scoring
Worksheet
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 25
The spreadsheets for supplier response creation not only has an improved and user
friendly look and feel, but it can provide immediate feedback to suppliers through the
robust formulas used to calculate scores, even when they are not connected to the system.
The enhanced spreadsheets will allow buyers and suppliers to enter the data more
efficiently and reduce the number of errors during data entry in the offline environment,
thus improving the overall user experience during the process.
Analysis – Lines
Overall Savings
Calculated Instantly
Side-by-Side
Bid
Comparison
Perform
What-If
Analysis
Buyers also have a more powerful tool to conduct analysis of supplier responses and
make smarter award decisions. Buyers can easily view totals and savings, conduct what-
if analysis of different award scenarios, and view side-by-side comparison of all elements
of supplier responses.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 26
Users can define quantity based price tiers when creating negotiations for Blanket
Purchase Agreements. Buyers can select whether they want to have price breaks,
quantity based, or no price tiers in the negotiation. When price tiers are enabled, buyers
can define the quantity range and the target price for each tier within a line. Similarly,
suppliers can create their own price tiers when they submit a bid. The award price is
based on the tier that corresponds to the award quantity assigned to each supplier.
EMD is received by the EMD Administrator, a new responsibility made available for
EMD transactions, or can be paid online by the suppliers (Corporate EMD). The EMD
Administrator can exempt a supplier from paying EMD, or refund or forfeit the EMD
amount, depending on the business policies.
There is an out-of-the-box integration with Oracle Financials, so that the receipt, forfeit
and refund of EMD can leverage Oracle Receivables and Oracle Payables. For customers
not using Oracle Financials, there is a non-integrated EMD deployment process where
the company can still use the EMD feature in Oracle Sourcing. There are reports
available for the buying organization to validate the EMD status and details for different
negotiations and suppliers.
This feature in Oracle Sourcing ensures that the end-to-end sourcing process for the
buying organization can be performed using Oracle Sourcing application, and customers
will not have to rely on processes outside the application to complete their sourcing
negotiations. This shortens the sourcing cycle which otherwise can lead to delays in
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 27
receiving and returning the EMD amount and affects the productivity of buying
organization due to manual checks and coordination. Also, all EMD related information
is retained in the application which can be leveraged for future reference and audit
requirements.
At times, there is a need to capture the name of the business owner of the negotiation or
in the case where the owner/sponsor is separate from the person running the negotiation.
The requester field is available in the negotiation header (RFI, RFQ and Auctions).
The default value is the buyer, but it can be updated as shown in the screenshot below.
Please note that the field, by default, is not available in the application and can be made
available though personalization.
The buyer can create different contexts which will control the different attributes
displayed. For example, in this case the context additional supplier information selection
displayed the contact address, contact number and budget sanctioned attributes. These
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 28
fields can be used to convey additional negotiation related information to the buyer and
supplier community.
Please note that the DFFs, by default, are not available in the application and can be made
available though personalization
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 29
3.9.5.3. Lot Price Summation
Certain negotiations use a Lot hierarchy to organize bidding lines. For Lots, the actual
award happens at the parent “Lot” level with detailed bid information collected at the
child (or “Lot Lines”) level.
Sourcing professionals can now view a Lot price, calculated as the sum of the price for
each Lot Line in that Lot. One example where this capability is applicable is for basic
bills of materials, where the item (Lot) level costing is naturally a summation of the
individual components (Lot Lines).
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 30
3.9.6.4. Staggered Awards
Sometimes sourcing awards are desired only for part of a negotiation. In these cases,
optimal timing for awarding different parts of the negotiation occurs at multiple dates.
For example, a large project scenario may involve a negotiation with many lines, with the
entire project in one document. In this case a single award timeframe may be premature
for the decision on certain lines.
With staggered awards a sourcing professional may evaluate and award one or more
lines, and later revisit the negotiation and award additional lines. The staggered award
process allows the buyer to award different lines at different points in time. New awards
can be used to create a new Purchase Order or Agreement in Purchasing.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 31
3.10. Oracle Sourcing Optimization
3.10.1. Overview
When allocating business to suppliers, buyers often must strive to meet multiple
purchasing goals and business policies. For example: “award at least 10% business to
minority-owned suppliers,” “no single supplier should get more than 80% of the total
business,” or “at least half of the business should go to incumbent suppliers”. It can be
challenging to achieve maximum savings while meeting such business policies,
particularly if there are many line items and a large number of competitive bids.
Oracle Sourcing Optimization can help by allowing the buyer to create scenarios that can
be automatically optimized to determine the best award, while adhering to policies and
goals defined on the scenario. This results in better and faster award decisions.
3.10.2. Release 12.1.1
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 32
engine analyzes all combinations of price tiers submitted by suppliers to determine the
best award recommendation. Award quantities specified in the award recommendation
are used to assign the correct unit price to the resulting purchasing documents.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 33
Fig. 6: Oracle Spend Classification, Classification Summary Page
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 34
column level search, and filters. Users can drill down to segments of data directly from
various Key Performance Indicators (KPIs) defined for classification results.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 35
3.11.3. Release 12.2
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 36
the taxonomy structure. This provides access to knowledge base prediction patterns at
each level of the taxonomy for additional evaluation and analysis.
Users can now delete classification batches that are no longer required for any business
function. This will allow users to get rid of batches that are no longer of any use, such as
a batch created after an unsuccessful classification run.
Prior to this feature, when a classification run was initiated the application created a
single batch and picked up all eligible transactions. This sometimes created a huge
classification batch.
Now users can explicitly specify the set of transactions that need to be classified, leading
to manageable batch sizes. Smaller batches lead to improved query performance,
reduced download time, quicker batch analysis, and faster approval and reset.
Spend Classification now comes with a simplified user interface. Most key functions
such as creating a knowledge base, enriching a knowledge base, and initiating a
classification run are centrally organized around the Dataset entity In addition, users can
now view the entire history of actions performed in the context of each entity.
The ability to reset dataset transactions that were part of a classified but unapproved
batch was possible. However, this could be confusing as once the batch was approved; all
transactions within the batch were stamped with the predicted category codes.
Now the application ignores resetting transactions that are part of a classified,
unapproved batch.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 37
Oracle Supplier Hub is an application that provides a portfolio of Master Data
Management tools to enable organizations to better manage their supplier master records
centrally. Built on the foundational technology used to support mastering of customer
information, Supplier Hub can be used by both organizations that need to aggregate
supplier data from a range of application systems and also by those running a single E-
Business Suite instance.
Supplier Hub consolidates supplier information from disparate systems and business lines
into a single repository, provides cleansing and third party enrichment tools for effective
data management, and provides the resulting "single point of truth" supplier data as a
service to consuming applications, enterprise business processes and decision support
systems.
Supplier Hub is a complementary solution to Supplier Lifecycle Management (SLM). It
can be implemented to extend the SLM capabilities by providing comprehensive quality
management functionality to cleanse the underlying supplier identity information that has
been enriched through the SLM tools.
Deployment of Supplier Hub enables organizations to have a consistent understanding of
the trading partners that they use to procure the various goods and services required to
support their business. This clarity is essential in order to be able to carry out effective
analysis of spending patterns so that appropriate tactical and strategic decisions can be
made about specific supplier relationships and overall company procurement policies.
3.12.2. Release 12.1.1+
Oracle Supplier Hub provides the following set of features:
• Supplier Master Profile
• Supplier Classification Management
• Supplier Hierarchy Management
• Supplier Data Import and Source Management
• Supplier Data Quality Management
• Supplier D&B Data Enrichment
• Supplier Data Publication and Synchronization
Full details about the current capabilities of Oracle Supplier Hub can be found in the
Master Data Management RCD.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 38
Once a supplier has been approved, SLM also enables organizations to gather feedback
from key stakeholders as part of an overall supplier performance tracking process. In
addition, Supplier Lifecycle Management also allows key stakeholders to identify and
track critical compliance documents and attributes that need to be gathered from suppliers
on a periodic basis in order for the two parties to maintain an active business relationship.
3.13.2. Release 12.1.1+
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 39
organization. In addition to the attribute name, administrators are able to add descriptive
text to help explain the purpose of the attribute.
Fine-grained access control tools allow administrators to manage which users can have
access to the individual attributes in the extended set of profile details. This is
particularly important when sensitive information is stored in the profile and access needs
to be restricted to appropriate users either internally or at the supplier.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 40
Once a registration request has been approved or rejected, the supplier is automatically
notified by email. Following approval, the qualification details provided by a supplier
become part of their profile that can be updated at a later date.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 41
3.13.3.2. Associate Address to Contacts
Prior to this release, while creating a registration request a prospective supplier did not
have the option of associating an address to a contact. This was done by an administrator
within the buyer’s organization once the supplier was registered.
This feature allows the prospective supplier to associate an address to a contact during
registration process. All the addresses defined by the supplier in the system will be
available for association, streamlining the registration process.
This feature is also provided for iSupplier Portal.
This feature is forward-ported to 12.2.4.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 42
This feature is forward-ported to 12.2.4.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 43
• Single Connection: Oracle SN is a messaging hub so each organization need only
setup a single connection to get access to the community of buyers/suppliers
• Multiple Document and Transformation Support: The buying organization and its
suppliers can exchange Purchase Orders, PO Acknowledgments, PO Change
Requests, Advanced Shipment Notices and Invoices that can be automatically
converted between OAG and cXML formats
• Self-Testing: Trading partners do not have to coordinate connectivity testing.
Instead, Oracle SN allows each partner to utilize a Test Hub to send and receive
sample documents to validate their connection
• Supplier Punch-in access to multiple customer Oracle iSupplier Portal
applications
3.14.2. Version 5.0
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document 44