Oracle Sourcing Approvals Setup
Oracle Sourcing has provided the stage and participants out-of-the-box to enable customers to easily organize and author approval routing rules for negotiation and award approval tasks.
Sourcing has provided Stage and Participants out of the box to enable customers to easily organize and author approval routing rules for negotiation and award approval tasks. From Oracle Functional Setup Manager, select these tasks:
This table contains negotiation approval header level attributes.
-
Manage Supplier Negotiation Approvals
To create and maintain approval rules for negotiation approval flow.
-
Manage Supplier Negotiation Award Approvals
To create and maintain approval rules for award negotiation approval flow.
Negotiation and Award Approvals can be enabled from Configure Procurement Business Function page.
Approval rules configured in the seeded stages are executed in this sequence:
-
Preapproval Stage
-
Header Stage
-
Postapproval Stage
-
Postapproval FYI Stage
There are four seeded stages for negotiation and award approval flows respectively and within each stage there are seeded participant types. The non-FYI participant types are seeded as rule based, which allows picking the list builder (Supervisory, Position, Job Level, and Approval Groups) that's applicable for any organization.
-
Preapproval Stage
-
This stage is used if approvals are required before routing to other stages and to different approvers.
-
Seeded Participants
-
Preapproval (FYI) - The buyer for negotiation will receive a negotiation FYI notification. A single person will be notified using this participant type. The rule to notify the buyer is available out of the box
-
Preapproval (Parallel) Consensus - All identified approvers receive a notification for approval in parallel. Approval is required from all approvers.
-
Preapproval (Parallel) First Responder Wins - Approvals are routed in parallel for this participant type. This participant type is more commonly used in conjunction with approval groups. The first responder to provide approve or reject action will represent the outcome of all remaining approvers.
-
Preapproval Serial - Approvals are routed in Serial. Approval process is completed sequentially from approver to approver.
-
-
-
Header Stage
-
Seeded Participants
-
Header Approval (FYI) - User can configure rule to send FYI notifications to approvers.
-
Header Approval (Parallel) Consensus - Approvals are routed in parallel for this participant type. This participant type is more commonly used in conjunction with approval groups. This participant type requires approval from all approvers.
-
Header Approval (Parallel) First Responder Wins - All identified approvers receive a notification for approval in parallel. The first responder to approve or reject the request defines the outcome of all remaining approvers.
-
Header Approval (Serial) - Approvals will be routed in serial. This participant is generally used for supervisory or position hierarchy based routing. The approvers returned based on all rules that apply in a serial participant will be notified sequentially from approver to approver.
-
Header Approval 2 (Serial) - Approvals will be routed in serial. If your organization has a requirement to have a second hierarchy based routing in parallel to the Header Approval (Serial) participant, rules should be maintained in this participant.
-
Header Approval 3 (Serial) - Approval will be routed in serial. Similar to Header Approval 2 (Serial), this participant allows another hierarchy based routing in parallel to Header Approval (Serial) and Header Approval 2 (Serial) participants.
-
-
-
Postapproval Stage
-
This is used to route for Postapprovals.
-
Seeded Participants
-
Postapproval (Parallel) Consensus - Approvals are routed in parallel for this participant. This participant is more commonly used in conjunction with approval groups. This participant requires approval from all approvers.
-
Postapproval (Parallel) First Responder Wins - Approvals are routed in parallel for this participant. This participant is more commonly used in conjunction with approval groups. The first responder to approve or reject sets the outcome for all remaining approvers.
-
Postapproval (Serial) - Approvals are routed in serial for this participant.
-
-
-
Postapproval (FYI) Stage
-
This stage isn't available in the BPM Worklist Administration page for modification.
-
Seeded Participant
-
Postapproval (FYI) The Postapproval FYI stage is created to send the negotiation owner, FYI notification for negotiation approvals outcome.
-
-
You don't need to use all of the seeded stages and participant. If you don't need to use any of the seeded participants, you will need to disable the participant from Manage Supplier Negotiation Approvals or Manage Supplier Negotiation Award Approvals pages.
This table includes negotiation approval header level attributes.
Attribute |
Notes |
---|---|
Approval Amount |
Negotiation approval amount for negotiation approval flow. |
Clauses Changed from Contract Template |
Indicates whether any clause has changed on the negotiation compared to the contract template in the terms library or not. |
Contract Template Expired |
Indicates whether the contract template on the negotiation has expired or not. |
Contract Terms Exist |
Indicates whether the negotiation has contract terms and conditions associated with it or not. |
Contract Deliverable Modified |
Indicates whether any contract deliverable is modified or not. |
Contract Terms Template |
Name of the contract terms template applied on the negotiation. |
Contract Deliverable Exists |
Indicates whether a contract deliverable exists on the negotiation. Contract deliverables are commitments that must be fulfilled as part of negotiations and contract agreements. |
Header Attribute 1-20 |
Text typed descriptive flexfield attribute. |
Header Attribute Number 1-10 |
Number typed descriptive flexfields attribute. |
Header Attribute Category |
Text Category typed descriptive flexfield attribute. |
Large negotiation | Indicates the type of negotiation. |
Lines in Negotiation | Indicates the numbers of lines present in the large negotiation. |
Lines pending award | Indicates the lines that are yet to be awarded. |
Negotiation Change Type |
Route the negotiation or award documents to the right approver based on whether it’s an amendment or a new round. You can also use this attribute if you require amendments to approved RFQs be automatically approved, but when a new round is created, the RFQ should be routed to additional approvers in the organization hierarchy. Or, if you require at least 2 rounds to award negotiations (for example, a first RFQ round to shortlist suppliers, and a second auction round to identify the best pricing), you can set up approval rules to automatically reject an award decision unless it's a new round. |
Negotiation Currency |
The currency code of the functional currency of negotiation. |
Negotiation Type |
Type of negotiation such as RFQ, Auction or RFI |
Negotiation Outcome |
Selected outcome for the negotiation. |
Negotiation Owner |
The name of the user who created the negotiation. |
Negotiation Owner Department |
The department of the user who created the negotiation. |
Negotiation Owner Grade |
The grade of the user who created the negotiation. |
Negotiation Owner Job Name |
The negotiation owner's job name. |
Negotiation Owner Job Level |
The negotiation owner's job level. |
Negotiation Owner Position |
The negotiation owner's position. |
Negotiation Style |
The negotiation style on which the negotiation is based. |
Negotiation Display Name |
The name of the negotiation. |
NonStandard Clause Modified |
Indicates whether any nonstandard clause is modified or not. |
NonStandard Clause Exist |
Indicates whether any nonstandard clause exists or not. |
Payment Terms |
Terms used to schedule payments and to calculate due dates, discount dates, and discount amounts for invoices matched against the purchase order. |
Procurement BU |
The business unit that manages and owns the purchasing document. |
Response Visibility |
Indicates whether the response will be visible to the supplier. |
Standard Clause Exist |
Indicates whether any standard clause exists or not. |
Standard Clause Modified |
Indicates whether any standard clause is modified or not. |
Two Stage Evaluation |
Two Stage Negotiation is set to Yes or No. |
This table includes line level attributes.
Attributes |
Notes |
---|---|
Backing Requisition Exists |
Indicates whether backing requisition exists for the negotiation. |
Category Name |
The products and services category indicating what the company supplies. |
Current Price |
Current price of the item. |
Description |
Description of the item. |
Item |
Item number |
Line Type |
A type to indicate whether a purchasing document line is for goods or services, as well as some default attributes associated with the line. |
Location |
Location to which the request should be delivered |
Line Attribute 1 - 20 |
Text typed descriptive flexfield attribute. |
Line Attribute Number 1 - 10 |
Number typed descriptive flexfields attribute. |
Line Attribute Category |
Text Category typed descriptive flexfield attribute. |
Procurement Category Hierarchy Level 1 -10 |
Number of procurement category hierarchy level attribute. |
Requisitioning BU |
BU in which the requisition is created. |
Start Price |
It refers to the highest price at which responding for a line can begin and all response price must be equal to or below the Start Price |
Target Price |
Target Price for the negotiation line item. |
UOM |
A division of quantity defined as a standard of measurement or exchange. |
This table includes award approval header level attributes.
Attributes |
Notes |
---|---|
Award Amount |
Indicates negotiation award amount. |
Procurement BU |
The business unit that manages and owns the purchasing document. |
Negotiation Type |
Indicates type of negotiation such as RFQ, Auction or RFI |
Contract Terms Exist |
Indicates whether negotiation has contract terms and conditions associated with it or not. |
Negotiation Currency |
The currency code of the functional currency of negotiation. |
Payment Terms |
Terms used to schedule payments and to calculate due dates, discount dates, and discount amounts for invoices matched against the purchase order. |
Clauses Changed from Contract Template |
Indicates whether any clause has changed on the negotiation compared to the contract template in the terms library or not. |
Contract Template Expired |
Indicates whether the contract template on the negotiation has expired or not. |
Standard Clause Exists |
Indicates whether any standard clause exists or not. |
Non-Standard Clause Exist |
Indicates whether any nonstandard clause exists or not. |
Contract Deliverable Exist. |
Indicates whether a contract deliverable exists on the negotiation. Contract deliverables are commitments that must be fulfilled as part of negotiations and contract agreements. |
Standard Clause Modified |
Indicates whether any standard clause is modified or not. |
Non-Standard Clause Modified |
Indicates whether any nonstandard clause is modified or not. |
Contractual Deliverable Modified |
Indicates whether any contract deliverable is modified or not. |
Contract Terms Template |
The name of the contract terms template applied on the negotiation. |
Header Attribute 1 - 20 |
Text typed descriptive flexfield attribute. |
Header Attribute Number 1 - 10 |
Number typed descriptive flexfields attribute. |
Header Attribute Category |
Text Category typed descriptive flexfield attribute. |
This table includes award approval line level attributes.
Attributes |
Notes |
---|---|
Requisitioning BU |
Business Unit in which the requisition is created. |
Item |
Item number |
Description |
Description of the item. |
Line Type |
A type to indicate whether a purchasing document line is for goods or services, as well as some default attributes associated with the line. |
Category Name |
The products and services category indicating what the company supplies. |
UOM |
A division of quantity defined as a standard of measurement or exchange. |
Location |
Location to which the request should be delivered |
Current Price |
Current price of the item. |
Start Price |
It refers to the highest price at which responding for a line can begin and all response price must be equal to or below the Start Price |
Target Price |
Target Price for the negotiation line item. |
Awarded Quantity |
Indicates quantity being awarded. |
Recommended Award Amount |
Indicates system recommended award amount |
Savings Amount |
Indicates savings amount for the award line item. |
Backing Requisition Exists |
Indicates whether backing requisition exists for the negotiation. |
Line Attribute 1 - 20 |
Text typed descriptive flexfield attribute. |
Line Attribute Number 1 - 10 |
Number typed descriptive flexfields attribute. |
Line Attribute Category |
Text Category typed descriptive flexfield attribute. |
Procurement Category Hierarchy Level 1 - 10 |
Number of procurement category hierarchy level attribute. |
This table includes award approval awarded suppliers.
Attributes |
Notes |
---|---|
Supplier |
Name of the supplier. |
Supplier Site |
Site from which the supplier will process the request. |
Requirement Score |
Score for requirement response. |
You can define your own attributes and can use them for creating rules by accessing Manage User Defined Attributes page. Sourcing Approvals will support user-defined attributes of type Custom Function (for non-cloud implementations) and Currency Conversion Function. User defined attributes can be created in negotiation and award approval tasks.