- For years SAP has stated that all of a prospect’s existing applications were legacy.
- In this article, we review the accuracy of this claim.
What SAP Said About All of an SAP Prospect’s Existing Applications are Legacy
Beginning in the 1980’s SAP used the logic that all the systems that were pre-existing systems at the prospect were legacy. This meant that 100% of the systems needed to be decommissioned, and 100% of the functionality mapped to what was available in SAP. This would be possible because, according to SAP, SAP had all of the functionality that the prospect would need, and SAP was entirely built upon best practices. This meant that anything the candidate was doing in their current systems would be inferior to the output of the functionality within SAP.
See our references for this article and related articles at this link.
The Truth About All of an SAP Prospect’s Existing Applications are Legacy?
As covered in the article How SAP Used and Abused the Term Legacy, this did not come true. The most common outcome was for it to be learned during the SAP implementation that the software had significantly been oversold. And that the pre-existing or “legacy” systems that the customer had contained functionality that SAP did not have and that there was nothing particularly best practice about SAP’s functionality. This lead to many “legacy” applications being integrated into SAP and or applications being rewritten into SAP’s programming language.
Conclusion and Calculation
SAP receives a 0% accuracy rating for its use of the term legacy to describe all systems that weren’t SAP.
Link to the Parent Article
This is one of many research articles on a specific topic, that support a larger research calculation. For the overview of the research calculation for all of the SAP topics that were part of the study, see the following primary research A Study into SAP’s Accuracy.