Info objects activation accidentally led to issues

[#1]

Hi Experts,

I did a terrible mistake that by mistakenly i have activated a info object in the Development ssystem which is being used in sevaral transfer rules and Cubes and ADSO's.Now the issue is i just activated the Info object but i didnt do any changes in the structur or settings how ever now i can see that one of the heirarchy attribute has been changed to a string which is a Char 60 before(I dint change this )now this is causing the issues in several places and leading it to the dump.

And we have some other master data attributes which are showing issue that they can be activated now.

Kindly help me how to resolve this issue without loosing any data.

Thanks in Advance,

Best regards,

Kiran

[FCI · Accepted solution]

Hi Kiranmai,

In 740, the DDIC domain RSCHAVL became a string (CHAR60 before) to handle the new max length for the infoObjects value. Normally, all infoObjects should have been activated in post-upgrade phase to reflect this change. I guess this wasn't done in your case and you have to handle now the "side effects" of this activation.

The impact is normally limited to specific ABAP that has to be corrected to support the string type.

Regards,

Frederic

[Former Member · Accepted solution]

Hi Frederic,

Thank you somuch for the answer, Yes we did observed that this issue happened due to the update, However there are some ABAP programs which are ending in dump due to this.

I did come across a note

https://launchpad.support.sap.com/#/notes/1879618 regarding this

As you mentioned above apart from correcting the ABAP code, cant this be done through changing the setting in the Hierarchy table Node name? with this do we have a chance of losing the data?

The activation has been done in Development system as of now, moreover the the confusing part is this activation dint get collected in any Transport request as it dint pop for a window to collect in TR when activated.

I can see several dumps in ST22 but most of them refering to the same Report.

Thanks and Best regards,

Kiran