M8147 – No Basic Purchase Price Relevant to Pricing Found with Schema RM1000

Just encountering error M8147 means VKP5 cannot calculate a retail price due to a missing purchase price reference. The PB00 condition record must exist in MEK1, schema RM1000 must include PB00 and PBXX in M/08, and condition types must be marked as pricing-relevant in M/. All three requirements are mandatory-without them, the pricing screen will not open.

Key Takeaways:

• Missing PB00 condition records in transaction MEK1 prevent the system from determining a base purchase price, which is required for retail price calculation in VKP5.
• The pricing schema RM1000 must include both PB00 and PBXX condition types, properly configured in transaction M/08, to enable correct pricing flow.
• Condition types must be explicitly marked as relevant to pricing in the condition type setup (M/)-without this flag, even existing records are ignored during price determination.

The Empty Record in MEK1

You’ll see an empty record in MEK1 when the system can’t locate a PB00 purchase price condition for the material. This missing entry blocks VKP5 from calculating any retail price, even if RM1000 is assigned. Without a valid condition record, pricing data remains inaccessible-ensuring no price can be processed or displayed.

The Order of RM1000

You must ensure the pricing schema RM1000 includes PB00 and PBXX condition types configured in M/08, as missing entries block VKP5 from calculating retail prices. Without a valid purchase price condition record in MEK1, the system cannot proceed. Confirm all condition types are marked as relevant to pricing in M/. Learn more about resolving this issue by reviewing Error M8147 – Account Determination for entry not possible.

The Mark of Relevance

You must ensure condition types PB00 and PBXX are marked as relevant to pricing in transaction M/08. Without this flag, the system ignores them during price determination, even if records exist in MEK1. This missing relevance setting blocks VKP5 from calculating any retail price, leaving the pricing screen inaccessible despite correct schema assignment.

The Three Essential Truths

You must have the PB00 condition record in MEK1, or VKP5 will fail to calculate pricing. The RM1000 schema needs PB00 and PBXX properly assigned in M/08-missing entries block retail price processing. Without flagging these condition types as relevant to pricing in M/, the system cannot proceed. All three elements are non-negotiable for opening the pricing screen.

Summing up

On the whole, you must ensure a valid purchase price condition record exists for M8147, as pricing cannot proceed without it. The schema RM1000 requires PB00 and PBXX properly assigned and flagged for pricing in M/08. If any component is missing, VKP5 will block the process. For further guidance, review Re: Create article error in pur/sales view.

FAQ

Q: What does error M8147 mean when running VKP5?

A: Error M8147 indicates that the system cannot determine a basic purchase price needed to calculate the retail price. This occurs during the VKP5 pricing simulation when no valid purchase price condition is found under the RM1000 pricing schema. The system relies on this data to proceed with pricing, and without it, the pricing screen fails to open. The root cause usually involves missing condition records, incorrect schema setup, or missing configuration flags for pricing relevance.

Q: Why is the PB00 condition record missing in MEK1, and how does it trigger M8147?

A: The PB00 condition record defines the base purchase price for a material and is maintained in transaction MEK1. If this record is missing for the relevant vendor, plant, and validity period, the system has no source price to reference. When VKP5 runs and checks the RM1000 schema, it looks for PB00 as the starting point. Without it, the pricing engine stops and raises M8147. Users must ensure PB00 is correctly created in MEK1 with the right conditions before attempting retail pricing.

Q: How should the RM1000 pricing schema be configured to avoid this error?

A: The RM1000 schema must include both PB00 and PBXX condition types in transaction M/08. PB00 serves as the base purchase price, while PBXX (such as PB01, PB02) may represent surcharges or reductions. If either is missing from the schema sequence, the system skips or fails to process the purchase price step. Users must verify the correct order and presence of these condition types in the schema to ensure the pricing flow can access the necessary data.

Q: What does “pricing relevance” mean for condition types, and why is it important?

A: Pricing relevance determines whether a condition type is considered during price calculation. In the condition type configuration (transaction M/), PB00 and related PBXX types must be marked as relevant for purchase price determination. If this flag is missing, the system ignores the condition even if records exist in MEK1. This setting ensures that VKP5 recognizes and retrieves the purchase price data when applying the RM1000 schema.

Q: What steps can I take to resolve M8147 completely?

A: Start by checking MEK1 to confirm a valid PB00 record exists for the material, vendor, and plant. Next, go to M/08 and review the RM1000 schema to ensure PB00 and any required PBXX types are included in the correct sequence. Finally, verify in the condition type settings (M/) that PB00 is flagged as relevant for pricing. All three elements-data, schema structure, and configuration-must be in place. Once confirmed, rerun VKP5 to see if the pricing screen opens without error.