Why should they have?
GDPR is rather legal subject, with very little relevnce to technical implementations. It's a company lawer which must understand it, not a report developer.

And - do you have such an understanding yourself?
Can you give a definition for "data subject"?
Is it a EU citizen, as described in one part of the legislation, or a EU resident, as described in another part?
After it's clarified - how can you tell that a customer record in your database contains personal data for such a "data subject"? How do you or your BI developer should know if a record with a dodgy family name belongs to a EU citizen, or to a contractor residing in an EU country for a limited time, or a gastarbeiter from Ukraine on a work permit with no residential rights?
How DBA's in Ali Express suppose to know which personal records in their database belong to citizens of which EU countries? Did you ever submit your citizenship information when buying something online? And even if you did - how a vendor suppose to verify correctness of such information? Get direct access to Intenal Affairs databases of every EU country???

Right-to-be-Forgotten.
What if I want to be forgotten by a Police department?
What about a private investigator database?  Their normal operations definitely "require regular and systematic monitoring of data subjects". So, according to GDPR, I must be able to force them to "forget me".
It's also interesting how they plan to enforce this right for the private information of EU citizens  collected by FSB (better known as KGB) or CIA?
And if FSB could not be forced to open their data collections for inspections by EU authorities, why Facebook must be any different? Especially - there is no solid proof that the personal records held by Facebook are of actual EU citizens.