Reason for Inactive Infoset Post Upgrade

[Former Member]

Hi,

As a part of Upgrade testing, I have observed this in all the systems that Infosets turn Inactive Post Upgrade. And i realise this only when i Execute a Query on an Infoset; it gives me a warning that I need to activate the underlying Infoset.

I am keen on finding the root of this error so that we can take care of these in the systems that have to be upgraded in future.

Any Pointers ?

Regards

Shweta

[Former Member · Accepted solution]

Hi,

it might be necessary to activate all existing InfoSets and MultiProviders based on them after upgrading to NetWeaver 2004s.

Reason:

Infosets are sometimes deactivated because additional checks are available after the upgrade or because new attributes become part of your info-object.

Also,an object can be inactive after upgrade even if the objct contained any custom objects in it. You may have to activate it or run RSRV check.

If there is any change(custom object etc) in InfoSet, it is automatically inactivated and you have to reactivate it.

To activate all such InfoProviders there are programs in SE38 like RSDG_CUBE_ACTIVATE,RSDG_MPRO_ACTIVATE,RSDG_ODSO_ACTIVATE

Hope this explaination helps!

[Former Member]

Swetha,

There is a need to run certain programs after technical upgrade. The objects will still be in 3.5. for them to work one needs to runs certain programs. You can go thru upgrade specifics doc for the post upgrades activities .....

[Former Member]

Using transaction code RSISET you can repair the infoset and activate it again.

Hope this helps.