All good morning,
In my company we have a "strict" policy against appending standard SAP tables with custom fields.
We had some specific business needs, so we ended up with countless ZTables, ZTransactions for data entry and ZReports to fulfill our business processes.
Some areas stopped using standard SAP and customized SAP was used instead. This has caused major issues in process standardization and reporting.
For example, we had a "ticketing" system in ABAP instead of using PM or service orders and a "Form" instead of using PM notifications.
Some folks on the business say that this was done because some fields need to be used for reporting and can't be thrown into the long text of the order or notification - but most of this was done back in 2000.
Right now I'm working to take some of those processes and use standard SAP whenever possible so that we have just one EAM process and can use the standard SAP list views and reports.
What is your take on when to append SAP standard tables and when to develop a custom table? If we have plans to migrate to S/4 in the next ten years, what is the best option from a technical standpoint?
I want to convince the business to append the tables in some cases, because there's a standard way of doing this in SAP https://blogs.sap.com/2014/04/20/iwo10018-user-fields-in-maintenance-order/ and I could even add some of those fields as selection inputs https://blogs.sap.com/2015/10/06/how-to-add-custom-fields-as-selection-inputs-to-iw3839/#
What do you think?
(I know there are similar posts - but the last one I found was 10 years old)
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.