Strategy Group 55: PIRs Consumption with reference...

dineshudl · 3 weeks ago

I'm working with Planned Independent Requirements (PIRs) linked to Characteristic/Configuration Data for Product Variants, and I need your insights to resolve a behavior I’ve encountered.

🎯 Objective:

Create PIRs for a product variant (Strategy Group 55) with assigned characteristics/configuration.

PIRs should only be consumed when a sales order with matching configuration is created.

PIRs should generate planned orders, but not convert to production orders until a matching sales order is received.

Lower-level components can be procured based on PIRs.

🧪 Test Scenario:

MRP View:

Configurable Material (Strategy 25): Individual/Collective = Individual

Product Variant (Strategy 55):

Individual/Collective = Collective

Assigned Configurable Material and completed characteristic assignment.

Maintained Planning Variant with characteristic values.

MD61: Created PIR for Product Variant.

MD04: PIR’s configuration was carried into the planned order, and lower-level components were planned correctly after MRP run.

⚠️ Issue / GAP Identified:
When I create a sales order with a different characteristic combination than the one in the PIR, the PIR is still being consumed - even though the configuration does not match. (other word, to be accurate 95% matches)

📌 Additional Info:

No Planning Table or Planning Profile used (per Strategy 55 behavior).

Assumption: PIR consumption is happening for closest match if no exact match is available.

Has anyone encountered this? Am I missing a key configuration or step to ensure that PIRs are only consumed for 100 % matching configurations?

Would appreciate any guidance or shared experiences!
Thanks in advance!

Ndubuisi_PALMER

Hello

This could occur due to incorrect or missing configuration in the requirements consumption logic. Here's what you should review:

1. Check the Consumption Mode and Requirements Class

Go to transaction OVZI (Requirements Class):

Locate the Requirements Class associated with Strategy Group 55 (often class 102).
Ensure the "Consume PIRs" setting is set to require an exact configuration match.
Specifically, verify field "Requirement Cons. With Config." is set correctly:
- It should be set to blank or a value that requires exact configuration match, depending on your system version.
- In some systems, value '1' allows approximate match — avoid this if exact match is needed.

2. Configuration Profile Settings (CU42)

For your configurable material and its variants, go to transaction CU42:

Make sure the configuration profile used does not allow flexible matching.
In particular:
- Set "Planning Material" correctly for the variant.
- If dependency logic (preconditions, selection conditions) is used, verify that it aligns with strict matching rules.

3. PIR Planning Variant (CTPV)

You mentioned using a planning variant with assigned characteristics.

Double-check that the variant is properly assigned and active.
Run transaction CTPV (for planning variant maintenance) to review the exact values assigned.
Make sure there is no fallback behavior (e.g., missing value = ignore) that could allow 95% matching.

4. Check the BAdI / Enhancement Use

If your system has custom enhancements, verify if BAdI MD_PIR_FLEX_CONS or MD_PIR_REDUCTION (or equivalent exits in customer namespace) have been implemented to allow consumption based on closest match.

You might need to adjust or deactivate this logic if it leads to unwanted consumption.

5. Test with Simulation

Use transaction MD63/MD73 to simulate PIR consumption:

Create two PIRs for different characteristic values.
Create a sales order with a mismatched configuration.
Simulate requirements reduction and observe which PIR is consumed.

Recommended Fix Steps

Review the Requirements Class (OVZI) and ensure the configuration consumption behavior is exact.
Confirm planning variants are strictly assigned without optional fields or missing values.
Check if any BAdIs or user exits are overriding standard behavior.
If available, enable the check in your system to prevent PIR consumption when the configuration is not a 100% match (may vary slightly by enhancement pack/version).

Summary

Strategy 55 supports strict configuration-based PIR consumption.
If your system consumes PIRs for partial matches, it indicates a misconfigured requirement class, configuration profile, or planning variant, or possibly a custom enhancement allowing flexible match.
Correcting this ensures PIRs are only consumed when sales orders have an exact configuration match, as you intend.

Best regards