3793933 - Data Flow from SAC to Datasphere fail after SAC update due to url change - SAP Datasphere

• Data Flows that load data from SAP Analytics Cloud (SAC) to Datasphere fail.
• Error messages observed include: “Provider /sac_public_dimensions/... is not found!”
• Error code: VAL-5000004
• Additional log detail: “Reader BODIVView1 the connection to the flowagent stream failed. Verify the IP address, port of the flowagent stream and make sure the Agent is running.”

• Product: SAP Datasphere
• Data Flow Runtime

1. Start a Datasphere Data Flow that uses SAC public dimensions as the source.
2. Run the Data Flow directly or within a task chain.
3. Observe that the run fails.
4. Open the run details or run with checkup to review diagnostics.
5. Note errors such as “Provider /sac_public_dimensions/... is not found!”, VAL-5000004, and reader BODIVView1 flowagent connection failures.

After SAC QRC3 update, dimensions move to the file repository. As a result, an extra “D” is inserted into the SAC resource URL used by Datasphere Data Flows, e.g. 't.1:<dimension>' becomes 'D:t.1:<dimension>', resulting in an invalid provider path and “provider not found” errors.

Details has also been explained in SAC Note: 3794114 - Direct URLs and bookmarks to public dimension tables in SAC stop working after the Dimensions in File Repository migration.

Remove the source dimension, and add it to the Data Flow again and the error will be gone.

In case the Data Flow has custom mappings with different source/target column names, you can also try the following steps:

1. In Data Builder, open an affected Data Flow. Open the Export menu and click Export to CSN/JSON File.
2. Edit the exported file, search for the keyword /sac_public_dimensions/t, and replace it with /sac_public_dimensions/D:t. Save the updated JSON file.
3. Navigate to the Data Builder home page. In the lower panel, open the Import menu and click Import Object from CSN/JSON File. Select the updated JSON file to import.
4. In the import dialog, select only the Data Flow and click Next. In the following prompt, select No to skip re-importing dependent objects.
5. Reopen the Data Flow. The source object will be updated with the new URL, and Data Preview should work. All mappings should be preserved. The Data Flow will have the status Changes to Deploy.
6. Deploy the Data Flow and test its execution.
7. Repeat these steps for every affected Data Flow.

For feature request, we have influence channel where you can raise feature request to our developer.Please take a look at below KBA to detail information.
3332382 - How to create an enhancement request for SAP Datasphere?

Note: 3794114 - Direct URLs and bookmarks to public dimension tables in SAC stop working after the Dimensions in File Repository migration.

datasphere, sac, task chain failure, data flow, url change, provider not found, VAL-5000004, BODIVView1, flowagent, sac public dimensions, data integration, run with checkup, graph failure, provider missing, upgrade , KBA , DS-DI-DF , Data Flow Runtime , LOD-ANA-ML-MDM , Master Data Management , Problem