Disable package check errors for specific packages

[former_member184711]

Hi,

we are using package checks for our custom developments. Now we have the problem, that there are some older (self programmed) modules which we are using.

Since they have not published all their "API" objects in package interfaces, we get package check errors when using these objects.

Now we are in the situation that the real (new introduced) package violations are getting hidden in the flood of "legacy" errors.

Is there a possibility to tell the package check to ignore errors from specified packages?

[Peter_Inotai]

I don't think it's possible, package check is activated on system level.:(

What you could do (and this is what we've also done) to write a generation program, which updates table PERMISSION (yes, it's dangerous, but you have to test it carefully) and get to the situation where everything is clear, and then you can start new developments.

[larshp]

not possible AFAIK

Working as a consultant I have a tough time convincing customers to activate it at a system level, so I started implementing it in custom code, see http://docs.abapopenchecks.org/checks/61/ sorry its not documented or fully implemented yet, pull requests welcome 🐵

[fabianlupa]

I think there might be (or might have been) some undocumented ways to achieve this as SAP themselves probably faced this problem when introducing the package checks concept.

To ignore development objects in package checks there are some candidates:

- Table IFOBJSHORT, column PAKNOCHECK (domain has fixed values)
- Table PACKCHECK_EXCEPT

These might have been deprecated at some point and not work anymore or only work in SAP internal systems. To have package checks behave like TR_SYS_PARAMS-SYSTEMTYPE = 'SAP' you can use PAKPARAM parameter SAP_DEV_SYSTEM = X.

Unfortunately looking at how SAP did things for package checks to separate SAP_BASIS / SAP_APPL / ... does not really help as structure package BASIS and its package interfaces are hardcoded into the package checks...