Skip to Content
0

Problems Generating and Activating OPI scenario

Dec 24, 2016 at 09:20 AM

65

avatar image

I have a problem either with the OPI application or HANA Studio. I am unable to Activate or Regenerate the scenario, and initially I see two revision 40 items in the History - see image. The version of 23 December is the one I want to keep and activate but I am unable to do this.

When I try to generate I get the "most likely another version of the object .. has been activated by another activation call" - see image 2

I have tried to use Team | Reset To | Active and it appears to remove the most recent Inactive version. This is not what I want, as I lose the most recent version.

After this, I can see the most recent version is removed from the Repository history, and I have lost that version, and 13 December is active.

However I still cannot Regenerate and continually get the same message as above

"most likely another version of the object .."

How can I force HANA Studio / OPI to create and Activate a new revision in the repository?

Thanks for any advice ..

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Andrew Frigaard Jan 06, 2017 at 12:39 PM
0

For the record, I resolved this myself. This is more a Studio / Repository problem than OPI, but with OPI there are a large number of dependent objects generated which make this type of problem more complex.

The root cause of the problem appears to be that I made some changes to the OPI context view and to some of the underlying views that it depends on. This were not Activating correctly, and so the Context view and OPI scenario could not activate. There appeared to be now way out of it. As a result I needed to go back to the last Base versions, and remove all the generated artefacts, and regenerate.

The learnings were to make small incremental changes and Activate all the way up through the dependencies. Also to export all views and the OPI scenario frequently during development, so that changes can be reapplied via the text/xml files as needed.

Share
10 |10000 characters needed characters left characters exceeded