Prior to doing any parts pricing, enrich locates the price book that is in effect for the particular work order. This could be the customer/unit price book, the customer price book, the customer class price book, or the shop price book. Within the selected price book, the line for the material cost type can be further defined by equipment type. Once a price book is located, it is used for all pricing on the work order. In other words, as an example, enrich would not use the customer price book for labor while using the shop price book for material; all cost types must come from the same price book.
The price for a part on an invoice is determined as follows:
If the part is the miscellaneous part (as defined by the Materials business parameter), the selling price will come directly from the price as entered on the work order. However, entering a selling price on a miscellaneous part is optional. If a price is not supplied, enrich will continue searching through the structure.
The next step is to check the price book for a specific price defined for the part. If a specific part price is found, the discount will also be taken from that level.
If the part was put onto a work order via an esetimate, the estimate price and discount will be used. This happens even if a price was found in step 2 above. That is important to note, since the normal course of events is to stop looking for a price once one has been found.
If there is still no price, the PI (parts interface) pricing comes into play.
If the Parts Interface Pricing business parameter is set to Yes, enrich looks through the active PI batches where the effective date of the batch is less than/equal to the invoice date. If the part is found, its price is taken from the PI column based on item category, customer, customer class, and facility. The hierarchy is: customer/item category, customer, customer class/item category, customer class, facility/item category, facility. Note that item category is never checked independently, only in conjunction with the customer, customer class, or facility. No discount is applied when a price is found in PI pricing. The assumption is that the price has already taken discounts into consideration.
If the Parts Interface Pricing business parameter is set to No, but the Use PI Pricing flag is set to Yes at the selected price book level, the pricing will be taken from the PI source defined on the price book. A discount percentage or amount may be defined along with the flag, in which case the system will apply the discount found on the price book PI definition to the price found in PI.
There are several key considerations in selecting an upload price:
If the item manufacturer is blank on the item master, the price from the first active upload on which the part is found will be accepted, regardless of the upload manufacturer.
If the item manufacturer on the item master has a value, the price will be retrieved from the first active upload on which the part is found where the upload also has that manufacturer. If the upload manufacturer is blank, it will be accepted as a match.
If the item master and the uploads are all defined with manufacturers, a price will only be considered when there is a match on manufacturer.
If still no price has been picked up, the next step is to check the price book base rates. The first lookup is for a price and discount for the item category and manufacturer. If that has no results, the second lookup is by item category without the manufacturer.
If there is still no price, the base rates are used and the base rate discount is applied.
Lastly, if there is a billing override price, it will be used regardless of what pricing may have been found above. If there is a billing override discount, it will also be used, but if not, any discount found previously will be used. For example, if there was a price and discount at the item category, that discount would be used, but the price from the override would be selected.
Back to Interfaces or on to Parts Interface Control