Question Re: SAP DRC RFC oAuth2 code 404 in Technology Q&A

SAP DRC RFC oAuth2 code 404

Axel_DESGLAND — Mon, 29 Jun 2026 08:16:10 GMT

Hello the community,

First time here and I'm asking to myself if someone has the same case than me.

I did all the configuration for SAP DRC relevant for our SAP ECC6 EHP8 (SP24) system.

The connection from Cloud Connector to the backend is OK and the ressource is available. The connection from BTP to the backend through the dedicated destination is OK when I test it. My issue is located on the created RFC type G I had to create with the oAuth2 configuration. I did all the chapter "Managing RFC Connections for SAP Document and Reporting Compliance, Cloud Edition" of the documentation : https://help.sap.com/docs/cloud-edition/sap-document-and-reporting-compliance-cloud-edition/managing-rfc-connections-for-sap-document-and-reporting-compliance-cloud-edition?locale=en-US

I first met two scenarios.

When I first tested the connetion, I met an error Create failed: plugin not active

So I checked note https://me.sap.com/notes/0003412080/E without success.

Then, I figured out that I didn't have both certificate G3/G5 in my STRUST. So I put them and I've retested the connection. I went from Create failed: plugin not active to error code 404 and not 401 as mentioned in the documentation

I really don't know where I failed. In SE80, all is done for the dedicated package.

In OA2C_CONFIG, I mentioned the clientID, clientSecret and the related URLs.

Authorization Endpoint : <enterprise>-drc-cloud-dev.authentication.eu02.hana.ondemand.com/oauth/authorization

Token Endpoint : <enterprise>-drc-cloud-dev.authentication.eu02.hana.ondemand.com/oauth/token

And the RFC configuration as been done as described...

Type : G

Host : drcc-test.c-257d320.kyma.ondemand.com

Path Prefix : /

Port : 443

Logon with User : Do not use a user

=> OAuth Settings => OA2C profile selected

Security Options, SSL Active

=> SSL Certificate ANONYM SSL Client, in which the ISRG Root X1 certificate has been set.

All the relevant oAuth2 SICF services seem to be activated.

The report OA2C_GENERIC_ACCESS return seems to be OK.

I'm still checking with SAP through a dedicated case but I don't know if I'm well understanded.

Thank you for your time and thank you if someone can help.

Have a nice day.

Regards.

Axel .

Re: SAP DRC RFC oAuth2 code 404

martinlitalin — Tue, 30 Jun 2026 20:43:23 GMT

Hi, does your company have the DRC Cloud Edition license?

Re: SAP DRC RFC oAuth2 code 404

Axel_DESGLAND — Wed, 01 Jul 2026 12:35:36 GMT

Hello @martinlitalin. Yes, our BTP subaccounts have all been configured accordingly.

Re: SAP DRC RFC oAuth2 code 404

martinlitalin — Wed, 01 Jul 2026 13:45:20 GMT

Thank you. If you have an OSS ticket open then support should get to your issue. Patience is required due to the high ticket volume.

Re: SAP DRC RFC oAuth2 code 404

Maxime_Rousseau — Thu, 02 Jul 2026 21:17:41 GMT

Hello,

Try removing the "=> OAuth Settings => OA2C profile selected" in the SM59 connection.
You will get a prompt to enter logon data and if you click "cancel" you get 401

The selection of the OAuth setting in the documentation is not mentioned (counter intuitive as we just created the profile before) https://help.sap.com/docs/cloud-edition/sap-document-and-reporting-compliance-cloud-edition/creating-rfc-connection-http-connection-to-external-server-sap-erp?locale=en-US

Kind regards,
Maxime

Re: SAP DRC RFC oAuth2 code 404

Axel_DESGLAND — Fri, 03 Jul 2026 06:04:30 GMT

@Maxime_Rousseau Waw! True. But... Why must we cancel this popup ? Should we be able to use the clientID/Secret to logon when prompted ? I don't really understand why even with the oAuth2 profile created we don't have to set it up in the RFC configuration. Maybe the RFC will use them automatically when needed. It's a little bit mind blowing to me haha... Kind Regards. Axel.

Re: SAP DRC RFC oAuth2 code 404

Axel_DESGLAND — Thu, 09 Jul 2026 09:27:44 GMT

Hello everyone,

SAP finally answered to my case with the following : "I have verified the configuration of [your dedicated] RFC Destination and it is giving me the 404 error. Which signified that the connection is working fine. Refer screenshot."

So, even if in my case I used the oAuth2 authentication method instead of the certificate one, and even if the official documentation says that I should have the return code 401, the 404 seems to be also OK.

Kind Regards.

Axel.