Package management issue

[Former Member]

The general recommendation from SAP seems to be turning the package check switch OFF, in order to avoid issues with missing interfaces and use accesses for custom packages.

If this is done as a temporary solution, and then turned ON some time in the future, will it cause errors if the same interfaces and use accesses have not been defined in the meantime? Or will previously imported packages continue to work as before, even if functionality is called from outside the custom package? Does anyone have experiences from live scenarios?

Regards,

Trond

[andrea_galluccio2]

Hi,

simply speaking, the new package concept have visibility section, and other features.

So you can decide in "package design" time, witch objects "see" others (for example, you have two includes in two different packages and you don't want that the main program - development in another package - can use these two includes).

Dont' worry about your existing class. If you don't touch the visibility section, there aren't problems.

Look in future if you want use this new features and all yopur future developments will follows the new rules.

Bye

Andrea

[Former Member]

Hello Andrea,

not sure if we understand each other correctly: my current issue is that we're receiving activation errors for some objects due to the package check being ON. I can turn it OFF, and thereby avoid having to define interfaces etc. before successfully activationg my objects. However, if I do this, and some time in the future turn the checks back ON, will my already activated objects start throwing errors (or is the check only done once, at activation)?

Regards,

Trond

[andrea_galluccio2]

Hi,

sorry but i don't have a "direct" experience on that.

Probably will you not have any problem until you modify the program again.

Bye

Andrea

[Former Member]

I would recommend leaving it ON in the first place, as OFF is anti-cyclic to what SAP is doing.

The activation error corresponds to a syntax warning at runtime. Once SAP have completed all package interfaces and removed all syntax warnings of their own and a complete set of released BAPI's are available for the package and and and... somewhere down the line... they might change the runtime package warning to an error as well. I think that is the trend, but whether this will be a per package switch or a global switch at a major release or still happen during our lifetimes, I don't know.

But it is coming (like global warming is as well...

Cheers,

Julius