Skip to Content
Technical Articles

Error when resetting DataSource XXX_ATTR – XYZCLNT000 to the active version and Master Data Datasources are inactive after patch upgrade

Brief description about the application, system, and device: Error when resetting DataSource XXX_ATTR XYZCLNT000 to the active version and Master Datasources are inactive when system is SAP BW on Oracle DB.

Issue: There is a load failure to a master data attribute, upon checking it has been found that the error occurs due to inactive datasource and this datasource has become inactive after patch upgrade in SAP BW.

You cannot use SAP standard program to activate this inactivate datasources, you will get below error while activating it.

You cannot import this datasource from Dev/Quality to Prod as TR import gets failed without any error log. Below is error screenshot while importing this datasource from Dev to Prod.

Solution: First of all, open the client with help of Basis team in Prod/Pre-Prod/Quality. Replicate the data source, then make some changes randomly in data source like check flag PSA in CHAR format, then activate.

Once activated, then revert back the changes and re-activate it, this will generate a PSA entry in RSTS table for that affected datasource and it will become active now. Thereafter trigger the data load.

Additional comments/information: This step does not have any impact on delta loads. Mostly, this error occurs for master data datasources when it has older dataflow like infososource.

Why this problem occurs: This error occurs when there is a patch upgrade and the datasource is having older version of dataflow mostly.

Out of scope: Installing business content datasource will not be feasible, it might miss delta records.

Conclusion:

Whenever this error occurs, please open the client. Then activate the datasource. Not sure if there is any SAP note to correct this error.

2 Comments
You must be Logged on to comment or reply to a post.
  • 2496984 – Errors RSO404 / RSO410 when activating Data-source

    Refer this note for correct solution. Ideally opening a productive client to activate the data-source is not suggestible option.

    Thanks,

    Bhavin

  • Hi Bhavin,

    Thanks for this SAP Note. But, the dastasource had delta records and Basis team could not able to take back up of content, hence we had to open the client to activate it. Delta records were intact.

    Regards,

    Arup Choudhuri