SAP Document and Reporting Compliance for Perú - SAP S/4HANA Cloud Public Edition DemoStarter

[Antony_Pantoja]

Hello Experts

Currently, the SAP DRC solution is active and the legal reports are working. However , I am unable to create new custom reports in the “Define Statutory Reports” app.

My user has all the required roles.

What could be missing?
Is another configuration missing?

#Sap Document and Reporting Compliance

#SAP S/4HANA Cloud Public Edition

Best regards,

Antony Pantoja

[Chuma · Accepted solution]

Hello @Antony_Pantoja 

Thank you for your question

Likely Causes and Solutions:

Missing Write Access to Configuration Environment

Even with all roles assigned, the “Define Statutory Reports” app only allows report creation in a configuration tenant (CBC or Q system)—not in production systems.

Check:
Are you in a Starter or Production system? If so, the button will not appear.

Solution:
You must be in a Customer Configuration Tenant (Q system) to create or edit report definitions. This is by SAP design.

Role vs. Business Catalog Check

Ensure that you not only have the correct roles but also the business catalogs required for edit access:

Required Catalogs for Report Creation:

• SAP_CA_BC_DRC_REP_PC (DRC Report Processing)
• SAP_CA_BC_DRC_REP_CONF_PC (DRC Report Configuration)

Solution:
Ask your administrator to confirm that your role includes both catalogs with write access.

Configuration Mode, Missing in CBC

If you are working via SAP Central Business Configuration (CBC), make sure the activity "Define Statutory Reports" is enabled for configuration in the corresponding CBC scope.

App Variant Restriction

Ensure you're using the correct version of the app. Some customers mistakenly use a read-only variant (typically used in productive tenants or for viewing standard content).

What you can check:

• Confirm you're working in a customer configuration system (Q system), not starter or production
•  Verify your user has write-access catalogs (SAP_CA_BC_DRC_REP_CONF_PC)
• Ensure CBC scope includes “Define Statutory Reports”
• Check with your system admin if a custom UI adaptation or launchpad restriction was applied

Let me know if you need further support

With kind regards

Chuma

[Stefan_Scholten · Accepted solution]

Dear Chuma,

thank you for the perfect summary about SAP DRC solution in the context of potential topics which may have an effect on usability of the “Define Statutory Reports” app.

Best regards

Stefan

[Antony_Pantoja · Accepted solution]

Hello Chuma, good afternoon

Currently, I am on an SAP SAP S/4HANA Cloud Public StarterDemo system.

On the CBC side, everything is activated and the SAP DRC is configured.

Also, at the role level I have access to everything with write and read permissions.

however, I still cannot create custom templates in the Define Statutory Reports” app.

Thank you very much for your support.

Best regards,

Antony Pantoja.

[Chuma]

Hello @Antony_Pantoja 

You are doing everything right—this is a system-type limitation, not a misconfiguration.
To move forward, you’ll might need to switch to a Q system where DRC configuration is allowed

Let me know if you still need further information

Thanks and kind regards

Chuma

[Antony_Pantoja]

Hi @Chuma

Yes, you are quite right. I will try to corroborate on a real SAP 3-system landscape of a s4 public customer.

thank you very much for your support and time

Kind regards,

Antony Pantoja

[Chuma]

Hello @Stefan_Scholten 

Many thanks for your feedback and remark! 

With regards

Chuma

[Jeremy_Deo]

Hello again dear user,

And thank you for asking your question in the SAP Community blog.

The reason you’re not seeing the “Create” button in the Define Statutory Reports app is likely one of these:

1. Missing authorization

You probably don’t have the right role. You need the business catalog:
SAP_CA_DRC_REPORT_CONF_PC (Statutory Reporting - Configuration)
Without it, you can only view reports, not create them.

2. Demo or restricted tenant

If you're working in a Demo Starter System, the ability to create reports may be intentionally disabled. Try again in your test (Q) or production system.

3. UI glitch

Sometimes it’s just a display issue. Try refreshing the page, clearing your cache, or switching browsers but in your case, I think this reason is not the one honestly.

I hope this will help you answer your question.

Best regards,

Jeremy

[Sandra_Rossi]

Not a blog here, it's Q&A or Discussions or whatever else.

[Antony_Pantoja]

Hi @Jeremy_Deo

thank you very much for your support and time

Kind regards,