Error
Error Code:
4673
SAP S/4HANA Error 4673: Data Source Not Found
Description
This error indicates that the SAP S/4HANA system or an application attempting to access data cannot locate the specified data source. It typically occurs during data provisioning, reporting, or analytical processes when a requested data source is missing or inaccessible.
Error Message
ERR_DATAPROV_DATASOURCE_DOES_NOT_EXIST: Data source does not exist
Known Causes
4 known causesIncorrect Data Source Name
The name of the data source specified in the application, query, or configuration might be misspelled or incorrect, preventing the system from finding it. 💻
Data Source Not Created or Activated
The required data source may not have been properly created, deployed, or activated within the SAP S/4HANA system or its connected components. ⚙
Missing or Insufficient Permissions
The user account or system process attempting to access the data source lacks the necessary authorization to view or use it. 🔒
Data Source Deleted or Moved
The data source might have been inadvertently deleted, archived, or moved from its expected location, making it inaccessible to the system. ⚠
Solutions
3 solutions available1. Verify Data Source Configuration in BW/4HANA or SAP Analytics Cloud medium
Ensures the data source is correctly defined and accessible by the reporting tool.
1
Log in to your SAP BW/4HANA system or SAP Analytics Cloud tenant.
2
Navigate to the Data Source administration or modeling area. This will vary depending on the specific tool being used (e.g., BW Modeling Tools in Eclipse for BW/4HANA, or the Modeling perspective in SAC).
3
Search for the data source that is reported as missing (e.g., by its technical name or description).
4
If the data source is not found, it needs to be created or restored. This typically involves defining the underlying InfoProvider (e.g., ADSO, CompositeProvider, HANA View) and its properties.
5
If the data source exists but is inactive or has configuration errors, activate it and resolve any reported issues.
6
Once confirmed to be active and correctly configured, attempt to run the report or access the data source again.
2. Check Data Source Activation and Transport Status medium
Confirms that the data source object was successfully transported and activated in the target system.
1
Log in to your SAP S/4HANA system (or the system where the data source is expected to be).
2
Use transaction code `SE11` to check for the existence of the underlying SAP HANA view or ABAP Dictionary object that the data source refers to. The naming convention can vary, but often it's a HANA view (e.g., `_SYS_BIC.<package>/<view_name>`) or a CDS view (`I_...` or `C_...`).
3
Use transaction code `SE80` to navigate to the package of the data source or related objects. Check if the data source object (or its underlying objects like CDS views) is present and active.
4
Check the Transport Management System (`STMS`) for recent imports related to BW objects or CDS views. Ensure that the transport containing the data source was successfully imported into the target system.
5
If the object is missing or inactive, re-import the relevant transport or perform an activation process for the CDS view or HANA view.
6
Verify the activation status of the CDS view using transaction `SE11` (enter the CDS view name and click 'Display', then check the activation status). For HANA views, you might need to check in HANA Studio or SAP HANA Cockpit.
3. Validate Data Source Name and System Alias easy
Ensures the report or query is referencing the correct data source name and system alias.
1
Identify the report, query, or analytical application that is failing with error 4673.
2
Access the configuration of this report/query/application. This might be in transaction `SQ01` (SAP Query), `SE38` (ABAP Report), SAP Analytics Cloud, or other reporting tools.
3
Locate the setting where the data source is specified. Pay close attention to the exact technical name of the data source.
4
If the report is connecting to a remote system (e.g., using a system alias for BW or another HANA system), verify that the system alias is correctly configured in the reporting tool and that it points to the intended system.
5
Cross-reference the data source name in the report configuration with the actual existing data source names in the source system. Typos or version mismatches are common causes.
6
Correct any discrepancies in the data source name or system alias configuration.