Professional Documents
Culture Documents
Procurement
Release 12.1 (through 12.1.3)
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.2. Oracle iSupplier Portal 4
3.2.1. Overview 4
3.2.2. Release 12.1.1 4
3.2.2.1. Dispute Resolution for G-Log Invoices 4
3.2.2.2. AP/AR Netting 4
3.2.2.3. Products and Services Search 4
3.2.2.4. Business Classification Recertification 5
3.2.2.5. Third Party Payments 5
3.2.3. Release 12.1.3 5
3.2.3.1. Work Confirmation Correction 5
3.3. Oracle Procurement Contracts 5
3.3.1. Overview 5
3.3.2. Release 12.1.1 6
3.3.2.1. Structured Terms Authoring in Repository Contracts 6
3.3.2.2. Secure Enterprise Search 6
3.3.2.3. Deliverable Payment Holds 6
3.3.3. Release 12.1.2 7
3.3.3.1. Author Individual Clauses in Microsoft Word 7
3.3.3.2. Project Manager Dashboard for Maintenance of Procurement Deliverables 8
3.4. Oracle Purchasing 9
3.4.1. Overview 9
3.4.2. Release 12.1.1 9
3.4.2.1. PO and Requisition Mass Update 9
3.4.2.2. Enable All Sites for Global Contract Purchase Agreements 9
3.4.2.3. FPDS-NG Integration 9
3.4.3. Release 12.1.2 9
3.4.3.1. Purchase Order Pricing Enhancement 9
3.4.3.2. Project Security within Oracle Purchasing 10
3.4.3.3. Procurement Web Services – Purchasing 10
3.4.4. Release 12.1.3 11
3.4.4.1. Landed Cost Management (LCM) Integration 11
3.4.4.2. Asset Lifecycle Management (ALM) Integration 11
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.
For your convenience, features are organized by product, and then by the release in
which they first became available. Release 12.1.1 was the first generally-available
release of Release 12.1. Features released in an off-cycle patch on Release 12.1.1, but
before Release 12.1.2, are designated as Release 12.1.1+. Features released in RUP2 of
Release 12.1 are designated as Release 12.1.2, and so on.
Existing functionality in Release 12.0, Release 12.0.x Release Update Packs (RUPs), or
prior releases is not described in this document. For a complete overview of all
functionality included in prior releases, this document should be read in conjunction with
the Release 12 and Release 12.0.x RUP RCDs. These RCDs can be found in My Oracle
Support Document 404152.1 Release Content Documents for E-Business Suite Release
12 and 12.0.x Release Update Packs.
A requester can update Quantity and Need-By Date of an approved internal requisition.
If desired, tolerances can be set for automatic approval of updates made to the internal
requisition.
Many new synchronization features are provided. Quantity and Need-By Date changes
on the internal requisition line are automatically propagated to the internal sales order
and vice versa. Cascading of an internal sales order Schedule Ship/Arrival date with the
internal requisition is may be controlled through a profile option. Cancellation of an
internal requisition/line will automatically cancel the corresponding internal sales
order/line and vice versa. And finally, the urgent flag on the internal requisition line will
flow onto the internal sales order line as the shipment priority, based on a profile option
setting.
In R12.1.1 onwards, requesters creating Non-Catalog Requests will have the option of
category being predicted for the purchase being made. After the requester clicks on
“Add to Cart” they will be able to view a “suggested best fit” category with a list of
categories that could be alternate possibilities. The same window can also be used to
parse the complete Category hierarchy. This approach uses the Oracle Spend
Oracle iSupplier Portal is the enterprise application that structures all supplier
communication through a secure, Internet-based portal. It is a key component of Oracle
Advanced Procurement, the integrated suite that dramatically cuts all supply
management costs.
When such disputes occur, it is important that the supplier is able to log and track all
activities for a particular invoice. To better help suppliers in these situations, new fields
have been added to the View Invoice page so that the supplier can see the original value
for their invoice and the reason for the discrepancy.
The new feature will give iSupplier Portal users visibility into the AP/AR netting
activity, so they can easily see which invoices will be paid standalone, which invoices
will be offset against receivable transactions, and which groups of invoices will be paid
by a single payment. On the View Invoices and Payments pages, if a particular invoice
has been netted, the users will be able to see the Netted Amount and the Reckoning
Currency. Furthermore, the users will be able to drill down to the Netting Report, which
will show all transactions that are a part of the netting batch.
The new feature is available within both the Profile Management pages for existing
suppliers and the prospective supplier registration flow.
This feature significantly reduces risk and administrative burden for buying
organizations because they will no longer need to manage the recertification process
manually.
Establishing Third Party Payment relationship can be done from iSupplier Portal.
Suppliers can add a new relationship and find and update existing relationships.
Oracle Procurement Contracts is the enterprise application that creates and enforces
better purchasing contracts. It is a key component of Oracle Advanced Procurement, the
integrated suite that dramatically cuts supply management costs.
With Release 12.1.1, users can now author structured terms and conditions while
creating a Repository contract. These terms are based on standard templates, clauses and
policies defined in the contract terms library. Users can also use the Contract Expert
feature to bring in additional clauses that may be required based on the business terms of
the particular contract. The contract can then be printed for signature, or exported to
Microsoft Word for redlining/collaboration with the external party. The deviations report
functionality will provide a quick overview of all policy violations in the contract.
Structured terms authoring promotes standards based contract authoring and reduces the
overall time-to-contract. Risk associated with non-standard contracts is also mitigated by
ensuring approvers have visibility to all policy violations.
Secure Enterprise Search provides flexibility to match user entered keywords to search
both structured text, such as contract terms, and unstructured text, such as text contained
in attached documents. Additional structured contract attributes may be used to further
refine the search, and include: contract number, contract name, supplier/customer/party
name, contract status, start date, and end date. Unstructured data/text search
functionality requires licensing of Oracle Secure Enterprise Search (SES).
This feature requires additional products to be licensed for full functionality described
below, including Financials and Services Procurement.
In Release 12.1.1, new hold and release reasons are seeded in Oracle Payables.
A “PO Deliverable” hold can be placed on all supplier invoices that are matched
to a purchase order that has a deliverable with payment hold terms and is nearly
due or is overdue.
Many construction firms adhere to a “Pay when Paid” policy for subcontract
agreements, in order to manage cash flow for a project. Specifically,
construction companies will hold the payment of subcontractor bills until the
construction firm has been paid by the owner. Now, a Pay when Paid payment
term may be specified for a subcontract to automatically result in the placing of
holds on all subcontractor invoices under that subcontract until the
corresponding customer payment is received.
• Line spacing
• Table formatting
Also in 12.1.1, a new Payment Controls Workbench in Oracle Projects allows the project
manager to view a checklist of all subcontract deliverables to assist in evaluating the
subcontractor status prior to releasing monthly progress payments.
A new program, Mass Close of Purchase Document, allows users to mass close Purchase
documents. The Mass Close functionality applies to Purchase Orders that have been fully
processed i.e. batch processing has completed, but are not in the closed status as well as
for Purchase Orders that the user needs to manually close. The program is applicable to
Standard Purchase Orders, Blanket Purchase Agreements, Planned Purchase Orders and
Contract Agreement and Blanket Releases
• View the pricing modifier information for a purchase order and/or Global Blanket
Purchase Agreement line and view the pre-calculated price adjustments applied by
the price engine.
• Manually enter a price modifier, change modifier rate, and recalculate the price.
• Query existing manual modifiers and apply them to a Purchase Order and Global
Blanket Purchase Agreement unit price.
• Change the modifier rate and apply changes to PO or Global Blanket Purchase
Agreement Line.
These new features provide an accurate view of pricing information to the buyer,
increased flexibility for buyers to price an order, and streamlined supplier
communication on prices.
As part of 12.1.2, the following web services are provided for 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. This enhancement is key for budgetary
control.
Oracle Services Procurement is the application that enables complete control and
oversight for services spending. It is a key component of Oracle Advanced Procurement,
the integrated suite that dramatically cuts all supply management costs.
Oracle Services Procurement further streamlines all aspects of the acquisition process for
complex services including:
• On a work confirmation for a PO, users now have the ability to enter
incremental or cumulative progress values, as absolute amount or percentage
• Users now have the complete visibility to the progress as they can view the
absolute and percentage values for both incremental and cumulative progress.
Oracle Sourcing is the enterprise application that improves the effectiveness and
efficiency of strategic sourcing. It is a key component of Oracle Advanced Procurement,
the integrated suite that dramatically cuts all supply management costs.
Oracle Sourcing enables buyers to source more of the organization’s spend at lower total
cost. Oracle Sourcing creates immediate savings through rapid deployment, and ensures
long-term savings with consistent execution and compliance.
The first stage includes the technical evaluation of all responses to questions and
parameters pertaining to the technical aspects that are used by the sourcing organization
to evaluate the technical feasibility and capabilities of the suppliers. During this stage,
commercial aspects remain sealed so that they do not influence the decision making
process. For bids that fail the technical evaluation, the commercial part will remain
sealed. Evaluators can then analyze the commercial aspects (such as price and delivery
terms) for only those bids passing the technical stage.
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.
During the commercial round, the buyer can then complete the surrogate bidding process
for those suppliers not carrying out their own bidding. The buyer is able to enter the
commercial terms provided by a supplier to enable scoring for the commercial round to
be completed. Upon approval of the quote, it is short-listed for placing the purchase
order or contract.
Bid Total
Calculated
Instantly
Line Filter
Predefined
List of
Link to Values
Scoring
Worksheet
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
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.
This enhancement improves the calculation of the per unit total cost when fixed amount
cost factors are used and the buyer awards a supplier a quantity that is either equal to or
lower than the response quantity. Whereas before Oracle Sourcing used the response
quantity to calculate the per unit total cost, the new formula utilizes the award quantity to
distribute the fixed amount cost factor resulting in a more accurate award amount
calculation.
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
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.
Often, buyers have a need to provide additional information on the header page, for
example, information on contract value, final project approver, etc. Headers attributes
are of two types: a) Visible to Buyers only (who have access to negotiation) and b)
Visible to both the buyer and supplier. As shown in the figure below, there are two DFFs
in the negotiation header page which helps to capture these attributes:
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
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
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.
Buyers can now determine a constraint priority for award optimization by indicating the
importance of a given constraint. The concept of setting up priorities for constraints will
help the optimization engine identify which constraints can be automatically relaxed
when, otherwise, no solution exist. By automatically relaxing a constraint, the engine
may find an acceptable solution, saving the buyer time and avoiding an iterative process
for optimizing.
Upon optimizing a scenario, buyers will be able to analyze the cost of a particular
constraint. Buyers typically want to evaluate by how much an award decision results on
a more expensive award because of a business constraint (i.e., the additional cost
Buyers will also have the ability to view award optimization scenarios side-by-side to
compare the results of different optimization approaches. Buyers will select what
scenarios they want to display side-by-side and Oracle Sourcing will show award
amounts and savings for those scenarios. Buyers will be able to effectively see the
before and after effects of changes made to the optimization criteria and/or weightings
when reviewing optimization results.
With Quantity based constraints, buyers can now indicate award allocation not only in
terms of award amount, but also in terms of award quantity. For example, 15% of all
units should be awarded to minority owned suppliers allowing for more control over the
optimization constraints.
Oracle Sourcing Optimization allows buyers to enter the incentives given by suppliers.
Buyers can enter the current total spend and rebate percentage for each supplier, and the
rebate structure for any extra award made on top of the current spend. In addition, a fixed
amount incentive can be specified to account for a signing or transition bonus. Oracle
Sourcing Optimization uses these values to calculate the additional savings yielded by
the incentives, and adds the amount to the total savings in the award scenario. Buyers can
then use the information to make more informed award decisions.
Spend Classification processes the data contained in P&SA and predicts appropriate
category information for each invoice line. To be able to do the predictions, Spend
Classification uses existing categorized data from PS&A to create a knowledge base.
Features in Spend Classification allow data stewards to test and validate the learning
performance, ensuring the knowledge base is performing classification at adequate
levels. Once the knowledge base has been built, the product can be used to classify
spend data residing in P&SA.
• UNSPSC
In R12.1.1 onwards, requesters creating Non Catalog Requests will have the option of
category being predicted for the purchase being made. After the requester clicks on Add
to Cart they will be able to view a “suggested best fit” category with a list of categories
that could be alternate possibilities. The same window can also be used to parse the
complete Category hierarchy. This approach uses the Oracle Spend Classification in real
time to assess the category of what the requester is ordering. The requester merely picks
the purchasing category and continues checking out. This capability allows even
unstructured requests to be categorized appropriately, aiding downstream spend analysis.
Many organizations track supplier data in multiple ways, driven by the needs of different
business units or unconnected business processes The result is disparate supplier
definitions that make it difficult to have a complete and coherent summary of each
trading partner.
Oracle Supplier Hub is a new 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.
Full details about the capabilities of the Supplier Hub application can be found in the
Master Data Management Release Content Document.
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
The Advanced Search allows any of the standard and extended profile attributes to be
used as search criteria and for the results to be viewed using multiple display formats.
The profile information retrieved from the search can be exported in spreadsheet format,
modified and then re-imported to enable mass data changes to be handled in an efficient
manner. The Advanced Search criteria and display formats can be personalized both at
the administrator and business user level.
The supplier user can maintain standard company profile details; Address, Contacts,
Business Diversity Classifications, Products and Services category and Banking Details.
Changes they provide can then be reviewed by internal administrators before approval.
Suppliers are also able to access qualification and on-going compliance information that
they are required to provide to the buying organization to maintain their status in the
system.
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.
In addition to the walk-up process, buyers can pre-register and send invitations to
prospective suppliers, requesting them to provide additional details for pre-qualification
and approval using the self-service capability.
To support complex or lengthy supplier registration, prospective suppliers can save their
draft registration request at any time, and return to it at a later date. Once a prospective
supplier has registered, their request is routed through an approval hierarchy for review.
Approvers are notified when they are required to review a request and can check
graphically the overall approval status for a given request.
As part of the approval routing, SLM includes the qualification information collected
from the supplier as well as incremental feedback provided by business users assessing
the request. This allows basic supplier profile and qualification details to be gathered,
deliverables like Insurance certificates and Code of Conduct documents to be stored and
Products and Services information to be recorded within the Qualification packet.
The buying organization can apply business rules that will use the details in the request
to customize the approval flow so that the appropriate approvers can look at the details.
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.
Supplier Lifecycle Management enables administrators to utilize the RFI tools to gather
and manage supplier compliance and profile information that are required on an
anniversary basis. They can define key compliance information that is required from
suppliers and then store the feedback provided by the supplier into the supplier master
profile record.
The feedback gathered about the supplier is stored in the supplier profile allowing
performance trends to be tracked and risk to be effectively managed.
The Oracle Supplier Network (Oracle SN) enables Oracle Purchasing customers and
their suppliers to accelerate collaboration and deliver significant efficiency savings by
conducting business electronically. Buying organizations are able to achieve quick cost
savings by leveraging the community of enabled suppliers on Oracle SN where
thousands of XML transactions are exchanged daily.
Oracle SN 5.0 is the most recent release and offers a range of new features.