Infor M3's purchase price retrieval logic for costing follows a defined hierarchy to find the most specific price. The system first searches for a valid price in a purchase agreement, which is managed in 'Purchase Agreement.Open' (PPS100). If no valid agreement price is found, the system then searches for a price defined for the specific supplier and item combination in 'Supplier.Connect Item' (PPS040). These two programs represent the primary sources for supplier-specific purchase prices used in purchase costing calculations.

A. Purchase Costing. Simulate (PPS295): This program is used to simulate purchase costs; it consumes or uses the retrieved price data but is not the source of the price itself.

B. Item. Open (MMS001): While a purchase price can be stored on the item master file, it is a general price that is overridden by more specific prices from agreements (PPS100) or supplier records (PPS040).

C. Item.Connect Warehouse (MMS002): This program manages item settings at the warehouse level, such as costing method and inventory data, not the supplier-specific purchase price.

1. Infor M3 Procurement User Guide: The documentation details the purchase price retrieval hierarchy. It specifies that the system first searches for a price from a purchase agreement (PPS100). If one is not found, it proceeds to check the supplier/item combination (PPS040), and only then does it check the item master file (MMS001). (Reference: Infor M3 Procurement User Guide for M3 BE, "Purchase Price Retrieval" section).

2. Infor M3 Costing User Guide: This guide explains how purchase costing elements are calculated. It confirms that the base for the calculation is the purchase price, which is retrieved according to the standard procurement hierarchy, prioritizing agreements and supplier-item records. (Reference: Infor M3 Costing User Guide for M3 BE, "Purchase Costing" chapter, section on "Costing Elements").