Skip to Content
avatar image
Former Member

Error in Transporting ADSO to Q environment. Can you please confirm if it is a authorization issue?

Error when resetting DataStore Object (advanced) ZPO_AD10 to the active version

Message no. RSO410

Diagnosis

Errors arose when activating DataStore Object (advanced) ZPO_AD10. An active version already existed before the activation.

System Response

DataStore Object (advanced) ZPO_AD10 could not be reset to the old active version. Since the generated objects no longer correspond to the old active version, they were reset to inactive.

Procedure

The old active version of DataStore Object (advanced) ZPO_AD10 can no longer be used. Remove the cause of the activation error and activate DataStore Object (advanced) ZPO_AD10 anew.

error.png (55.4 kB)
su53.png (68.8 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Oct 26, 2017 at 08:07 PM

    Hi Experts,

    The ADSO is being moved first time to Q system with system user ID TMSADM. The ADSO activation failed. I can see the SE11 tables are generated and active in Q. Found below blog mentioning it could be authorization issue. Our security team is looking into it.

    Meanwhile appreciate if you can confirm this is the issue.

    https://archive.sap.com/discussions/thread/3865602

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 26, 2017 at 08:15 PM

    Hi Kannan,

    We had a similar problem with one of our ADSOs, we started using the table instead of the external view. We switched off the external view and sent another transport which activated it.

    In the case of infoobject it makes is good to have an external view enables, since that would have the attribute and text join built in. But in the case of ADSO, the table and the external view both are the same.

    This was also recommended to us by SAP when they came in for a performance audit.

    To add to that: when transporting an ADSO, the ADSO gets activated in less than a minute, but the activation job keeps running to perform the RS2HANA check. The amount of time this job runs depends is based on the number of user. You can also manually activate the ADSO which would try to insert entries into the RS2HANA_AUTH_STR table.

    Thanks,

    Kumar APP

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Kumar,

      I tried importing the ADSO without the external view setting. The import failed with the same error.

      Anything else I should try?

      Thanks,

      Kannan N.