Consolidation data load fails with XML file integration-schema validation errors in consolidation module

ERP SAP S/4HANA
, , , , , , , ,
1

Our consolidation data load process started failing after we upgraded to S/4HANA 1809. The job runs from transaction SEM-BCS but aborts with an authorization error related to HANA CDS views.

Error message:


Authorization check failed for CDS view
View: I_GLACCOUNTLINEITEMRAWDATA
User: CONS_USER
Required privilege: SELECT

I’ve verified in SU24 that the role S_RFC_ADM is assigned to CONS_USER, and the user has S_TABU_DIS authorization for table access. However, the consolidation data extraction still fails when trying to read financial data from the underlying CDS views.

In HANA Studio, I can see the CDS view exists, but I’m not sure how to assign the correct HANA privileges to the SAP user. This is new territory for us since our old ECC system didn’t use CDS views for consolidation. How do I properly map SAP authorizations to HANA CDS view privileges for consolidation data loads?

2

CDS view authorization is different from traditional table authorization. You need to check both SAP authorization objects (S_TABU_NAM) and HANA analytic privileges. Run RSECADMIN to see if there are DCL (Data Control Language) restrictions on the CDS view.

3

The issue is that CDS views in S/4HANA use a dual authorization model: SAP ABAP authorizations AND HANA SQL privileges. For I_GLACCOUNTLINEITEMRAWDATA, you need to grant the underlying HANA analytical privilege. Go to HANA Studio → Security → Analytical Privileges and find the privilege associated with financial data. Then assign it to the technical user’s HANA database user (not just the SAP user). This is a common gotcha after ECC to S/4HANA migration.

4

Here’s the complete solution for CDS view authorization in consolidation scenarios:

1. CDS View Authorization Check: First, verify the CDS view definition and its access controls. In transaction SE11, display view I_GLACCOUNTLINEITEMRAWDATA and check the ‘Access Control’ tab. You’ll see if DCL (Data Control Language) is defined:

@AccessControl.authorizationCheck: #CHECK
DEFINE VIEW I_GLACCOUNTLINEITEMRAWDATA AS SELECT FROM acdoca
  WHERE CompanyCode IN (SELECT CompanyCode FROM I_CompanyCodeVH)

This indicates that access control is active and requires specific authorization.

2. SU24 Role Check and Enhancement: In SU24, check transaction SEM_BCS (your consolidation transaction) and verify these authorization objects are maintained:

  • S_TABU_NAM: Authorization for CDS views (add I_GLACCOUNTLINEITEMRAWDATA with activity 03)
  • F_BKPF_BUK: Company code authorization for financial documents
  • F_BKPF_GSB: Business area authorization

Critical step: In SU24, set these objects to ‘Check’ status (not ‘Do not check’). Then regenerate your consolidation role in PFCG.

3. HANA Privilege Assignment: The error indicates missing HANA-level privileges. In HANA Studio:

a) Navigate to Security → Users → find your technical user (check with SM04 what database user is mapped to CONS_USER)

b) Grant analytical privilege:

GRANT SELECT ON SCHEMA SAPSR3 TO CONS_USER;
GRANT EXECUTE ON _SYS_REPO.GRANT_ACTIVATED_ANALYTICAL_PRIVILEGE
  TO CONS_USER WITH GRANT OPTION;
CALL _SYS_REPO.GRANT_ACTIVATED_ANALYTICAL_PRIVILEGE(
  'sap.fin.central.gl/AP_GLACCOUNTLINEITEM',
  'CONS_USER'
);

This grants the analytical privilege specifically designed for GL account line item CDS views.

c) Verify privilege assignment:

SELECT * FROM EFFECTIVE_PRIVILEGES
WHERE USER_NAME = 'CONS_USER'
  AND OBJECT_TYPE = 'ANALYTICALPRIVILEGE';

Additional Configuration: For consolidation-specific requirements:

  • Apply SAP Note 2638453 which addresses CDS authorization issues in SEM-BCS for S/4HANA 1809
  • In transaction RSECADMIN, activate the authorization trace, run your consolidation load, and review which specific CDS access controls failed
  • Ensure the CONS_USER has authorization object S_RFC for remote-enabled function modules used by consolidation (F_BKPF_BUK with activity 03)

Testing and Validation: After implementing these changes:

  1. Clear the user’s authorization buffer (SU01 → Utilities → Reset buffers)
  2. Test CDS view access directly: Use transaction SE16 to display I_GLACCOUNTLINEITEMRAWDATA with your CONS_USER
  3. If direct access works but consolidation still fails, check the RFC connection (SM59) and ensure the destination user has the same privileges

We resolved this exact issue for a client after S/4HANA 1809 upgrade. The root cause was that consolidation loads use both dialog and RFC users, and HANA privileges were only assigned to the dialog user. Both users need identical HANA analytical privileges for the consolidation data load to succeed.

5

I’ve implemented consolidation in multiple S/4HANA environments and this authorization issue is very common. The problem is that SEM-BCS consolidation uses CDS views for data extraction, but the authorization model changed significantly from ECC. You need to ensure three layers of authorization are properly configured: SAP authorization objects, CDS access controls, and HANA analytical privileges. Missing any one of these causes the exact error you’re seeing.

6

Check if the CDS view has DCL (Data Control Language) defined. Use transaction RSECADMIN or SE11 to view the CDS definition. If DCL exists, you need to maintain the access control conditions in addition to standard authorizations.

7

Use transaction SU53 immediately after the error occurs to see exactly which authorization check failed. This will tell you whether it’s an SAP authorization object issue or a HANA privilege issue.