Hi there,
I would like to share what to me is shocking news:
We are upgrading to EHP7. We have been implementing Compensation solutions for more than 5 years and always found the SAP delivered ECM module to be quite robust and consistent. As usual, we have developed multiple custom features on top of the standard SAP delivery. In this particular case, I am only talking about ABAP (Classes in particular)
It turns out that SAP seems to have forgotten what happens when you deploy a public class, for customers to extend it, and then all the sudden you decide to remove that class. Or rename it, or change parameters for that matter.
Let me share some examples:
Class: CL_HRECM00_PLANNING_SERVICES
Method: GET_APPROVINGMGRS_OF_ORGUNIT -> has been DELETED
Method: GET_PLANNINGMANAGERS_FOR_PERNR -> has been DELETED
Method: GET_DIRECT_SUB_ORGUNITS -> has been declared PROTECTED while it has always been public
Method: GET_ELIGIBLE_EMPLOYEES -> has been RENAMED to GET_EMPLOYEES
And this seems to be just the tip of the iceberg. The deeper we look, the more CHANGES we can identify. If those changes are to be maintained, all our custom features will have to be rebuilt.
A colleague of mine created an OSS note assuming that was a mistake and providing details, and SAP replied stating that they are not responsible for any customer development.
Has anybody faced the same issue with Compensation or any other module? Is that supposed to be a new SAP approach to handle existing implementations? We have seen minor changes in some objects in the past, which is understandable when trying to improve the tool, but in this case, it seems like SAP decided to ignore all basic OO programming best practices when improving an existing module.
Not sure if there is any alternative other than to reengineer the entire solution that we built, but wanted to share in case anybody has any suggestion or any comment to explain what I missed.
Kind regards,
Miguel