Ways to show Posting level 30 also part of _Elim - is this possible, if yes how

It's unusual for a customer to request showing posting level 30 as part of "Elim" because they serve fundamentally different purposes within Group Reporting:

• Posting Level 20 (Elim): Specifically designed for pairwise eliminations between two consolidation units, automatically removing intercompany transactions.
• Posting Level 30: Used for group-level adjustments that don't directly eliminate transactions between units, but rather reflect adjustments needed for consolidated reporting.

Why the Request Might Arise

There might be a few reasons behind this request:

• Misunderstanding: The customer might not fully grasp the distinct roles of posting levels in Group Reporting.
• Specific Reporting Need: They might have a unique reporting requirement where certain group adjustments (typically level 30) need to be presented alongside eliminations for analysis purposes.
• Legacy System Carryover: If they're transitioning from a legacy system with different consolidation logic, they might be accustomed to a different approach to eliminations.

How to Address the Request

1. Clarify the Concepts: Start by explaining the differences between posting levels 20 and 30, emphasizing their intended purposes. Use clear examples to illustrate how each level works.
2. Understand the Underlying Need: Dive deeper into why the customer wants to see level 30 with eliminations. What specific information are they trying to obtain or analyze? This will help you determine the best solution.
3. Explore Alternatives: Instead of directly combining level 30 with eliminations, consider these options:
   • Separate Reporting: Create separate reports or sections within a report to show eliminations (level 20) and group adjustments (level 30) distinctly. This maintains the integrity of the consolidation process while providing the desired information.
   • Custom Report Logic: If SAP Group Reporting's standard reporting functions don't meet the need, you might need to develop custom reports using tools like SAP Analytics Cloud. This allows for greater flexibility in how data is presented and analyzed.
   • Enhanced Analysis: Use the reporting flexibility of Group Reporting to create reports that analyze the impact of both eliminations and group adjustments on key financial metrics. This can provide valuable insights without altering the core consolidation logic.
4. Document and Justify: If, after careful consideration, you decide to modify the system to include level 30 in the "Elim" presentation, thoroughly document the reasons and the impact on the consolidation process. This is crucial for auditability and future maintenance.

Important Considerations

• Data Integrity: Ensure that any modifications don't compromise the accuracy and integrity of the consolidation process.
• Auditability: Maintain a clear audit trail of all adjustments and eliminations.
• System Performance: Consider the potential impact on system performance if you introduce custom reporting logic.

By carefully analyzing the customer's request and exploring the available options, you can find a solution that balances their reporting needs with the principles of sound consolidation practices in SAP Group Reporting.