3732427 - Errors occurs when changing the authentication type from Basic to OAuth 2.0 in a connection.

• When changing the authentication type from Basic to OAuth 2.0 in an S/4HANA on-premise connection, an error occurs. The connection cannot be updated during validation:

Correlation ID: *******
HTTP Status: 400 Bad Request
Error Code: disableRemoteTablesError
Technical Message: Remote tables cannot be disabled because the connection
****** is used by the following object(s):
Remote.****** Datasphere.

• An error occurs when changing the data provisioning option from "Data Provisioning Agent" to "None":

Correlation ID: *******
HTTP Status: 400 Bad Request
Error Code: forbiddenOperation
Technical Message: Changing data provisioning option from "Data Provisioning Agent" to "None" is not allowed

• SAP Datasphere

1. Open an existing S/4HANA on-premise connection that currently uses Basic authentication.
2. Change the authentication type to OAuth 2.0 and attempt to save.
3. Observe the update failure with HTTP 400 and error code disableRemoteTablesError.
4. If attempting to change the data provisioning option from DPAgent to none, observe HTTP 400 with error code forbiddenOperation.

• The connection has dependent entities (like replication flows, remote tables, import/model artifacts) linked to the remote source. Validation blocks disabling remote tables while dependencies exist. With OAuth 2.0 selected for S/4HANA on-premise connections, remote tables and model import are not supported; dependent entities must be removed before updating.
• Directly changing the data provisioning option from "data provisioning agent" to "none" is not permitted with existing dependent objects.

1. Use impact and lineage analysis to identify all dependent artifacts of the remote source in the relevant space (for example, replication flows, remote tables, imported models, and any downstream objects consuming them).
2. Stop and remove the dependent artifacts so that no objects reference the remote source. Ensure all replication flows and data flows tied to the connection are deleted or decoupled.
3. After dependencies are removed, update the connection to use OAuth 2.0.
4.  If OAuth2 is chosen, remote tables and model import are currently not supported. When updating the connection to select OAuth2, all dependent entities of the remote source in that space have to be deleted first. If this is not feasible, a new S/4HANA on premise connection should be created selecting OAuth 2.0 from the beginning.

• SAP Help: Impact and lineage analysis
• SAP Help: Modifying objects that have dependent objects
• SAP Help: Prepare oauth 2.0 authentication for abap and s/4hana connections
• SAP Help:SAP S/4HANA On-Premise Connections

datasphere, s/4hana on-premise, connection update, oauth 2.0, basic to oauth, remote tables cannot be disabled, disableRemoteTablesError, forbiddenOperation, data provisioning option, dp agent, none, replication flow dependency, impact and lineage, authentication change blocked, abap connection, cloud connector , KBA , DS-DI-CON , Connections , Problem