Help Home/Creating Negotiations
When you create a new negotiation, your first step is to create your negotiation header. This header contains negotiation level information related to the entire negotiation.
To create your negotiation header: Complete the following fields (*indicates a required field):
*Title The name by which this RFI, RFQ, or auction will be known. You must specify a title for your negotiation and once the negotiation is published, the title cannot be changed.
The negotiation style controls the structure of the negotiation document by identifying which sourcing document elements appear. Negotiation styles can streamline and standardize the creation of negotiation documents. For example, if input from a collaboration team is not required for many negotiations, the Sourcing Administrator can define a negotiation style in which fields related to collaboration teams do not appear. Also, if your negotiation is a large or very large negotiation, you must select a style that supports that type of negotiation.
Security Level You can select a security level to restrict access to the sourcing document.
Buyer The creator of the negotiation .
Requester If the Requester field is available, then select the business owner of the negotiation. By default, the buyer value defaults to the Requester field. You can select for example, the owner of the negotiation if this person is different from the creator of the negotiation.
Note: The Requester field is hidden by default and must be enabled using Oracle Application Framework personalization.
Organization The operating unit, such as a division or department, to which this negotiation applies. The organization you select here determines the values for many later attributes (such as the negotiation currency and shipping addresses). If this negotiation document was originally created in Oracle Purchasing, the backing requisition information is carried forward and this field cannot be updated. Note that if you have entered information on this page, for example in the Payment Terms field, and you change the Organization, the page refreshes and you will lose the information you entered. Once you proceed to the next step, this value cannot be changed.
Outcome(auction, RFQ only) Designate your RFQ or auction outcome as either a standard purchase order or a blanket or contract purchase agreement. This cannot be changed once you proceed to the next step.
The outcome field also contains values defined in the Purchase Document Styles. Similar to Negotiation Style, Purchasing Styles allow buyer organizations to implement various features in Purchasing. In Sourcing, user interface elements for the negotiation are hidden or displayed based on the Negotiation Style as well as the Outcome. Purchasing Document Styles are used when creating complex services RFQs. See Oracle Purchasing User Guide for instructions on defining Purchasing Document Styles and details on complex work document styles.
Sourcing Project:
If the current negotiation is being conducted in connection with a project in Oracle Projects, you can link this negotiation to the project by project number.
Collaboration Team You can identify a group of users from within your company who will collaborate on this negotiation. For each member, you can choose to:
Make the member an approver of the sourcing document.
Give the member the ability to score supplier responses to negotiation Requirements (if scoring is allowed by the negotiation style sheet).
Give the member view-only access to the document. View-only members can view the document but cannot update any information.
Define a particular task for that member to perform, and a target date by which the task should be completed. The team member marks the task as complete once it is finished.
See Working with Collaboration Teams for information on the document approval process. See "Understanding Security Levels" for information on the interaction between security levels and a collaboration team.
Terms
Global Agreement (Blanket Purchase Agreement only)
Effective Start/Effective End Date (Blanket Purchase Agreement only) Use the pop-up calendar to identify the start and end dates of the agreement.
Bill-To Address Address to which your RFQ/Auction bills should be sent. Click the flashlight icon to browser for other addresses. You can select any of the addresses address is defined in Oracle Purchasing.
Ship-To Address Address to which the RFQ/Auction items will be shipped. Click the flashlight icon to browse for other addresses. The possible values for your operating in Oracle Purchasing.
FOB The FOB terms for your supplier. The possible values and the default are defined in Oracle Purchasing.
Total Agreement Amount (Blanket Purchase Agreement only) The amount the buyer agrees to spend with the supplier over the course of the agreement.
Minimum Release Amount (Blanket Purchase Agreement only)
Payment Terms The payment terms for your suppliers. The possible values are defined in Oracle Payables. The default is set in Oracle Purchasing.
Carrier The freight carrier your supplier should use. The possible values for your operating unit are defined in Oracle Inventory. The default is set in Oracle Purchasing
Freight Terms The freight terms for your supplier. The possible values and the default are defined in Oracle Purchasing.
Currency Shows the default currency for the negotiation. This is the buyer's default currency. Click Manage Response Currencies to allow responses in more than one currency. See Accepting Negotiation Responses in Multiple Currencies for instructions on allowing additional currencies.
Price Precision The number of decimal places allowed for per-unit prices entered in the RFx/Auction currency. The precision you set doesn't apply to per-unit prices entered in a currency other than the RFx/Auction currency, nor does it apply to currency amounts such as Bid Total or the bid value of Fixed-Amount price elements. While you can set the precision for unit-prices entered in a non-RFx/Auction currency when you define your currency list, the precision for amounts is automatically governed by the standards defined by the ISO (International Organization for Standardization). The ISO standards are used automatically by Sourcing.
Requirements You can request information on suppliers at the negotiation level by defining negotiation Requirements. Requirements can be external, in which case responses are provided by the supplier. Examples of external requirement information might be a supplier's years in business, ownership, or personnel qualification. Requirements can also be used internally, in which case the response is provided by some kind of internal evaluator. Internal requirement responses might include level of customer service provided, or prior on-time history. Either way, responses to requirement requests can be evaluated and used by personnel when awarding the negotiation.
Responses to Requirements can be scored according to the desirability of the response. You can define the Requirement such that the system automatically scores the response (in which case you must specify the allowable values (or ranges of values) for that requirement and each one's score. Or evaluators can view the response and enter a score manually.
Additionally, if you have multiple Requirements for the negotiation, you can weight them to reflect the each requirement's importance relative to the other requirements.
See Defining Requirements for instructions on defining Requirements.
Additional Header Attributes (Buyer Only) Select the context in this region and record information as required. The details that you enter in this region are visible only to the buyers who can access the negotiation. You can provide additional information about the negotiation header for buyers, for example, internal negotiation details such as the name of the project, total budget sanctioned, and final approver.
Note: This region is hidden by default and must be enabled using Oracle Application Framework personalization.
Additional Header Attributes (Buyer & Supplier) Select the context in this region and record information as required. The information that you enter in this region is available to both buyers and suppliers. You can provide information for both buyers and suppliers, for example, additional supplier information such as the supplier address and contact number.
Note: This region is hidden by default and must be enabled using Oracle Application Framework personalization.
Abstracts and Forms
Abstracts and forms are used to publish information on upcoming sourcing events. This information is available publicly without the supplier needing to sign into the system.
Notes and Attachments
You can use notes and attachments to supply suppliers and internal users additional information on this negotiation.