3761320 - Guidelines for Resolving Configuration Errors for SAP Group Reporting Data Collection (GRDC) customer cases (connecting to SAP S/4HANA, Cloud, private edition)

• Errors like  "Can't get/retrieve the global parameters from the S/4HANA system." or "Cannot load metadata" or different HTTP  or RFC errors are resulting from a missing or wrong configuration of the Connection between the Custom Managed App SAP Group Reporting (GRDC), the IDP set up, SAP Cloud Connector and S/4HANA Private Cloud or On Premise.
• SAP Technical Support is dealing with Product Errors and not in the position to do or handle extensive requests for checking configuration while starting to implement SAP GRDC.
• If there are errors during productive usage or application testing where the root cause is possibly lying in configuration changes (certificate renewal, SCC update, ) SAP needs an overall view on your set up as BTP subaccount and SAP Cloud Connector cannot be accessed remotely.
• SAP Support will also request traces to find errors in configuration more easily. This information is dependant on the software layer it is affecting. A common KBA to summarize the information about Traces and Logs should be provided in this KBA.

• SAP Group Reporting Data Collection
• SAP Cloud Connector
• SAP S/4HANA Cloud, Private Edition or SAP S/4HANA On Premise

grdc, group reporting data collection, can't get global parameters, http 401 unauthorized, intermediary is not trusted, icm/trusted_reverse_proxy, principal propagation, certrule, cloud connector, rfc initialization failed, s4hanacconsoendpoint_rfc, name or password is incorrect, ssl headers removed, icm trace, trust configuration, http 500,  , KBA , FIN-CS-CDC , Fin.Consolidation - Cloud Data Collection , Problem