Pricing Agreement In Oracle Apps

A price requirement is the specific information made available to the price module when the module is called by order management. In general, this includes the customer, the product, the attributes associated with the debtor or product that can be used by the price module, the price date and other price attributes possibly required by the price module. Phase Verification: The phase you selected when setting up the cost-cost conversion line must be a phase performed during the SHIP price event. For base prices, use the «Line Rates» phase. If you select another phase, the phase you use for the change line should be a phase in which the SHIP event is associated. For price lists, modifiers and agree price lists (price characteristics), the following data are assigned: 1) Enter the name of the price agreement. 2) Enter agreement number 3) The contract review is by default at `1`4) Default revision date to current date 5) Enter Revision reason – useful it we are making a new revision. 6) Choose the customer to whom it applies 7) Choose the type of agreement 8) Choose the efficiency data for this price agreement You can create mathematical expressions called formulas used by the price module to calculate the list prices of the items and the discounts that apply to them. You can use these formulas to: After creating a context and its attributes, you can link the grouping of contextual attributes to a certain price transaction rating (PTE). For a particular PTE, this combination can be used within a pricing. Each PTE has its own combination of attributes. For more information, please see the association of attributes to a price transaction.

Grantee: the user or user of a type of grantee who is allowed to display or manage a price unit. Is used in combination with a type of grantee. Users in operating units who only need to display or maintain access to price units. Price lists are essential to ordering products, as each item entered into an order must have a price. To book the order, the ordered item must be on a price list. Each price list contains basic information about the top of the list and one or more price positions, price attributes and a secondary price list. Basic information on the price list includes the name of the price list, validity dates, currency, price control, rounding factor and shipping standards such as freight conditions and carrier. The next step is to assign permissions to all users in all operating units. Security permissions allow you to provide and/or manage access to pricing data.

For more information, see Creating Permissions. If an item is displayed in both the primary and secondary price list with the same validity dates, the price module uses the main price list to pay for the item.