Incidence in Fallback Classes for BAdIS 1.1

By mistake the Fallback classes of BAdIS for the new XML version 1.1 (product version 1.7.4) have been created with the Final flag marked. This means that they cannot be used as inheritance for other classes.

This is a problem, because if a BAdI needs to be implemented, the right thing for the Z class that implements these BAdIS, would be to inherit from the standard to reuse the methods that do not want to be redefined.

To solve it the following temporary solution can be performed:

• Create a repair in the fallback classes and deselect the final flag:

Classes to be repaired /EDGE/CL_SII_SII_MAPEOS_FE_1_1, /EDGE/CL_SII_MAPEOS_GEN_1_1 and /EDGE/CL_SII_MAP_FE_FICA_11 (if ISU module is being used).

T-code SE24. Enter the name of the standard class to be repaired. Press change.

If the namespace is closed in the system, you cannot change an /edge/ standard object. The message that will come out is this:

To be able to edit this standard object go to transaction SE06 and press System Change Option:

Search for the namespace /EDGE/ which will be in "Not Modifiable":

Change it to "Modifiable" and save.

Return to class /EDGE/CL_SII_SII_MAPEOS_GEN_1_1 and press modify again. This time the message that will come out is as follows:

The standard class can be edited now.

In the properties tab, uncheck the FINAL check:

Activate the class.

Saving and activating the class will save the changes in a repair transport request that must be transported to the different environments for its correct functioning.

This issue will be corrected in version 1.7.5 so that, when importing the new version 1.7.5, it will replace this repair and return to the standard /EDGE/ object with the correct setting of the "No Final" class.

If during the SPAU phase of the new SP (version 1.7.5), this object needs to be adjusted, it should be returned to the original (reset to original), so that the standard class is again as product defines and ignores the repairs made to this object in the system.

Thus, during the time that version 1.7.4 is active in the system, this issue is resolved, and at the time of the 1.7.5 upgrade, the standard objects will be reset as defined in the product with the fix.