404 Errors when using SAP OData Connector

Question

When connecting to our SAP S/4 Hana Public Cloud instance, I am able to make the connection on both Appflow and Glue using the SAP OData Connector.  But when I got to specify the table name or run the connection I am receiving a 404 'Service Not Found' error.  The full error message is below.

*Error while communicating to connector: com.amazonaws.sandstoneconfigurationservicelambda.coral.model.ConnectorServerException: Client error: The request to SAP failed with the status code: 404 and SAP error message: Not Found.*

We have been using the same service as the one I am trying to connect to with multiple other applications, using all the same parameters and authentication methods.  It is just AWS that we are having an issue with.

I have followed the documentation to a tee, so it would be good to know if others have experienced the same problem and how they solved it.

Thanks.

re:Post Agent · Answer

This 404 "Service Not Found" error when using the SAP OData connector with AppFlow or Glue typically indicates an issue with the service path configuration or accessibility.

Here are some potential causes and solutions:

1. **Incorrect Application Service Path**: Ensure you've entered the correct catalog service path. For Amazon AppFlow, this should be something like "/sap/opu/odata/iwfnd/catalogservice;v=2" and not a specific object path. Amazon AppFlow doesn't accept specific object paths.

2. **Entity Name Format**: If you're using AWS Glue, check that your ENTITY_NAME is correctly formatted. The path should be complete and properly structured (e.g., "/sap/opu/odata/sap/[service_name]").

3. **Service Activation**: Verify that the OData service you're trying to access is properly activated in your SAP system. The catalog service must be enabled.

4. **Authentication Issues**: Confirm that the user credentials you're using have sufficient permissions to access the specific OData service.

5. **Network Connectivity**: If your SAP system is not directly exposed to the internet and is only accessible within your intranet, you may need to set up a private connection. For AppFlow, you can use AWS PrivateLink by providing your VPC Endpoint service name. For environments where SAP is only accessible via corporate network, consider using AWS Client VPN to maintain connectivity.

6. **OData Version Compatibility**: Ensure your SAP system is using a compatible OData version (V2.0 or V4.0) that works with the AWS connectors.

7. **URL Accessibility**: The application host URL must be accessible over the public internet for non-PrivateLink connections. Try accessing the OData service URL directly in a browser to verify it's reachable.

If you've verified all these points and still encounter issues, you might want to check the SAP Gateway logs for more detailed error information about why the service is not being found.  
**Sources**  
[SAP OData connector for Amazon AppFlow - Amazon AppFlow](https://docs.aws.amazon.com/appflow/latest/userguide/sapodata.html)  
[Data integration - General SAP Guides](https://docs.aws.amazon.com/sap/latest/general/data-integration.html)  
[SAP connectivity issues | AWS re:Post](https://repost.aws/questions/QUXmoZRcEAQfGbyOcY-PJqig/sap-connectivity-issues)

404 Errors when using SAP OData Connector

Add your answer

Relevant content