Understanding Base Prices

When you enter an item on a sales order, the system retrieves the base price information for that item. You can define base prices for any combination of items, item groups, customers, or customer groups.

When you enter an item in the F4101 table, you should enter the sales price level. The sales price level determines how you define the base price for an item. This table describes the levels at which you can define prices:

Level	Description
Item	Define one overall price for an item. You cannot include branch/plant, lot, or location information.
Item/Branch	Define different prices for each item and branch combination. You cannot include location and lot information.
Item/Branch/Location	If you define pricing by location and lot, you can also define branch/plant information.

When you define any special pricing or discounts for an item or customer, the system bases the calculation of the discounted price on the base price.

You can assign effective dates when you define the base price for an item. If you do not assign effective dates, the system assigns them based on the current system date. You also specify the sales price based-on date in the system constants to determine which date on the sales order the system uses as the price effective date. The sales price based-on date can be the promised date, the order date, or the date that you define in the system constants. The system retrieves the price with an effective date range that includes this sales price based-on date.

You can also use effective dates to enter a new price while an old price is still in effect. For example, you can overlap the dates for the base price and the dates for a discount price that you are offering for a limited period. When you set up date ranges that overlap, the system retrieves the price that expires first.

For every price, you can also define a credit price to use for negative quantities.

You can use JD Edwards EnterpriseOne Sales Order Management pricing to add prices for items in the domestic currency and as many other currencies as necessary. For example, you can set up base prices for one item in both US dollars and the euro. Currency code and unit of measure are both keys to the F4106 table. If you are using multicurrency, the system searches for a price in this sequence:

1. Customer's currency and the user-specified unit of measure.

2. Customer's currency and the item's primary unit of measure.

3. Domestic currency and the user-specified unit of measure.

4. Domestic currency and the item's primary unit of measure.

If the system does not find a match, it moves to the next level in the pricing hierarchy structure and searches in the same sequence.

You can copy base price information for an item that belongs to an item group. The system duplicates pricing information but does not duplicate the item group information.