Hits from other Reporting Entities in Tax Compliance within Run Compliance Reports

[adrsdl89]

Dear SAP Community,

We are facing an issue with SAP Document and Reporting Compliance (DRC) in the "Run Compliance Report" app, specifically in the context of tax compliance, and would appreciate your insights.

Scenario:
When a user runs a compliance report for a specific reporting entity (e.g., XYZ1), the system is also returning hits in tax compliance for other entities (XYZ2, XYZ3), where the user has authorizations.

Expectation:
Our client wants the system to return hits only for the selected reporting entity in Tax Compliance. For example, when the run compliance Reports app is executed for XYZ1, only hits for XYZ1 should appear in tax compliance, regardless of whether the user has authorizations for XYZ2 and XYZ3.

Key Details:

• The user running the report has authorization for all three entities: XYZ1, XYZ2, and XYZ3.
• The issue occurs when the report is executed with XYZ1 as the selected reporting entity in the app.
• Our goal is to restrict the tax compliance hits to the selected reporting entity (XYZ1), without impacting the user's overall authorizations for the other entities.

  Additional Considerations:

  1. Compliance Scenarios and Compliance Checks:
     • In our configuration, compliance scenarios and compliance checks include selection conditions (e.g., equal to or not equal to company code, document type, tax code, etc.).
     • Could these selection conditions be impacting the results by allowing hits for other reporting entities (e.g., XYZ2 and XYZ3)? If so, what adjustments can we make to ensure results are strictly filtered for the selected reporting entity?

Question:

Is it possible to configure the "Run Compliance Report" app or adjust the logic in SAP DRC to ensure that tax compliance results are limited to the selected reporting entity (XYZ1) even if the user has authorization to multiple entities? Additionally, how can we ensure that the selection conditions in compliance scenarios and compliance checks do not inadvertently include results from other entities?

Additional Context:
We’ve reviewed the configuration settings for the app and considered authorization objects, but the issue persists. Could there be specific filters, configurations, or overlooked areas in compliance scenarios that need adjustments?

Thank you and Best regards

Adrian