Info Record Price Not Defaulting Into PO
The purchase order is not reading the purchasing info record price because the condition record's validity period does not cover the PO date, the info record does not match the PO's plant or purchasing organisation, a source list or outline agreement is forcing a different price source, or the price line was manually overwritten and is no longer eligible for automatic redetermination.
This page covers why a purchasing info record maintained for a vendor and material does not show up as the price in a new or changed purchase order. It walks through the validity, scope, and source-of-supply precedence issues that block automatic price determination, the check sequence across ME13, ME22N and ME03, and the difference between a data fix and a configuration fix.
Published 16 Sept 2026· 1,140 words
The business symptom
A buyer reports that the vendor price agreed and entered in the system last week is not showing up on a new purchase order for the same material and vendor. The PO either proposes the old price, proposes zero, or opens the price field for manual entry instead of filling it automatically. Sometimes the complaint is the opposite: the price fills in but it is a different value than what purchasing negotiated, and nobody can explain where that number came from. The buyer usually insists the info record 'is definitely there' because they can see it in display mode, and asks why the system is ignoring it on this one purchase order while it worked fine last month on a similar one.
The configuration behind it
Most cases trace to one of the following, roughly in order of frequency.
- Validity period mismatch: the condition record inside the info record has a valid-from and valid-to date range that does not include the purchase order's pricing date, most often because the record was created with today's date as the start and the PO carries an earlier requisition or delivery date used for pricing.
- Plant or purchasing organisation scope mismatch: the info record was created plant-specific for one plant but the PO is for a different plant, or it was created for one purchasing organisation while the PO sits under another; without a plant-independent or cross-org record, no price is found.
- Wrong info record category: the record exists as a standard info record but the PO item is subcontracting, consignment, or pipeline, and the system is looking for a different category that was never created.
- Source list or outline agreement precedence: a fixed source list entry or an active contract for the same material and vendor takes priority in source-of-supply determination and its own price is used instead of the info record's condition record.
- Deletion or blocking indicator set: the info record or its condition record carries a deletion flag at the purchasing organisation or plant level, which stops it from being proposed even though it is still visible in display.
- Price scale not covering the order quantity: a scale was defined for certain quantity bands and the PO quantity falls outside all of them, so the system falls back to the base price or leaves the line open.
- Manual override on a previous PO: a buyer typed a price directly into a PO line, which sets the condition to manual origin; if that PO was used as a reference or copied, the manual flag carries forward and blocks automatic redetermination.
- Calculation schema or schema group assignment at the vendor level does not include the price condition type used by the info record, so the pricing procedure never looks for that condition at all.
What to check
Work from the info record outward to the PO, not the other way round.
- ME13: display the info record for the vendor, material, plant and purchasing organisation on the PO. Confirm it exists at the right scope and check for a deletion or blocking indicator.
- ME13 conditions tab: check the validity dates and the price scale against the PO's order date and quantity.
- ME22N item conditions tab: check whether the price condition shows as automatic or manual origin, and use the pricing analysis option to see the system's own explanation for why the info record condition was or was not selected.
- ME03 or the PO's source of supply tab: check for a fixed source list entry pointing to a different vendor or record.
- Contract assignment: check whether an outline agreement is referenced on the PO item, since a contract price overrides an info record price.
- Vendor purchasing view: confirm the schema group assigned matches what is expected for this pricing procedure.
How to prove it in the data
Pull the PO item's conditions tab and run the pricing analysis for that condition type, which lists every condition record the system evaluated and states explicitly why each was rejected, such as validity, scale, or exclusion. Compare that output side by side with the info record displayed in ME13 for the same vendor, material, plant and purchasing organisation and quantity. The mismatch, whether date, scope, or scale, is visible directly in that comparison without needing to reproduce the transaction.
Resolution path
If the cause is a validity date, extend or correct the condition record's valid-from and valid-to dates in ME12; this is a data fix, no transport needed. If the cause is scope (wrong plant, wrong purchasing org, wrong category), create the missing info record at the correct scope rather than trying to widen the existing one, since scope fields are not changeable after creation in most cases. If a source list or contract is taking precedence and that is not the intended behaviour, correct the source list entry or the contract validity, both data fixes owned by purchasing. If the calculation schema or schema group assignment is excluding the condition type, that is a configuration change to the pricing procedure or vendor schema group default, and it needs to go through a transport and regression check against other vendors using the same schema group. If the price was set to manual origin on a template PO, delete and recreate the condition line in ME22N so it reverts to automatic, or create a fresh PO without copying the flagged reference.
The fix people try first (and why it fails)
The reflex fix is to type the correct price directly into the PO's condition line and move on. It clears the immediate complaint but sets the condition to manual origin, which means the next PO for the same vendor and material will hit the identical issue, and any future change to the info record price will silently stop reaching this PO line. It also removes the audit trail back to the negotiated price, which surfaces later as an unexplained price variance at invoice verification.
Whose problem this is
Info record content and validity dates belong to purchasing master data maintenance, usually the buyer or a central master data team. Schema determination and condition type sequencing in the pricing procedure belong to MM configuration. The handover note should carry vendor, material, plant, purchasing organisation, PO number, and the pricing analysis output showing the rejection reason.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-functional-issues/info-record-price-not-pulled-into-the-purchase-orderERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.