Not sure if this is the correct forum, please forward if it is not.
We have 9 Z tables (several with < 10 rows) that are used exclusively by 2 custom processes. These Z tables are not used by any other process. Also, the data is time sensitive in that if the data is not in the Z table, it will take more manual effort to correct the error.
The kind of corrections that will be done after the initial load would be adding/modifying 1 or two lines to one or two of the tables and an estimate of the # of times/year that changes would be needed is probably < 6 unless our business changes substantially.
I have 2 questions:
Is it possible to transport for the initial load in a new environment and then have maintenance done directly in the production system?
Is it best practice to always transport Z tables.
>>> Is it possible to transport for the initial load in a new environment and then have maintenance done directly in the production system?
Depending on the tables Delivery Class (find it on Delivery and Maintenance tab page of se11 for this DB table), you can or cannot transport the table contents across the landscape. To be able to transport the entries, make sure to use class C (Customizing table) and "Standard recording routine" when generating the maintenance view for your table.
>>> Is it best practice to always transport Z tables.
I think it would be an abuse to say yes or no. It definitely depends on the role of the table in the system. You could have custom configuration tables (your tables seem to be one of them), where you want to maintain the entries once in the development system and have it transported. And you could have master data or transaction data custom table, where you definitely don't want the content transported.