Brief background of the Project and current requirement.
---------------------------------------------------------------------------------
We used to have all the SAP HR data for all the active and inactive employees in SAP 4.6C system with OM data maintained in Position to Position reporting model (Multiple Managers in a given org unit ) instead of Chief Position ( Unique Manager in any given Org Unit ) model. This SAP system is very old and so many mergers and de-mergers were happened in the past. So, instead of going for a system upgrade, we have Re-Implemented a new SAP ECC system to have the clean/active configuration and ignored tonnes of old / obsolete PA/OM configuration data. We have migrated current/active Org data and latest PA data ( Top of Stack ) valid as of the go-live date. Also, we have taken care of converting the existing 'Position to Position' structured org data into 'Chief Position Model' org data, before loading into new SAP ECC system.
We initially planned to archive the historical SAP HR data in the old system into a database and provide some basic historical reporting. But, business would like to have the data retrofit capability as well on the historical data. Since SAP data is tightly integrated, we have to keep the historical data also in an SAP system to allow the data updates. So, now we are thinking about upgrading the old SAP HR box Vs setting up an entirely new client in the new SAP landscape ( both Dev, QA and Production servers ) and load the historical data into this new client. We do understand that there is considerable risk in having multiple clients in production system. As per SAP note 31557, we can have multiple clients in production system, but with few limitations.
Below are the key challenges that we are analyzing before deciding on setting up parallel / new client in the new SAP HR system.
1. In the new SAP system, OM data was loaded with 'Chief Position' model. But the data in the new client should be loaded as 'Position to Position' model. We are not pretty sure whether the standard SAP transaction in ECC will support the OM data in Position to Position model.
2. The current client in the new system will have only current/active configuration data. But the new client is going to have both active and inactive/historical configuration data.
3. If any of the transactions are using client independent tables, that might have an impact due to have multiple clients in the system.
4. Normally, all the configuration table are client dependent. If any of the configuration / custom tables are client independent, we will have an impact.
5. Are there any know SAP transactions that will make the updates in client independent tables ?
Did any of you have ever experienced or implemented multiple clients in the production system ( especially, one client with org data in 'Chief Position' model and another client with 'Position to Position' model ) and allowing the updates in both the clients ? If so, could you please share the pros and cons of the same and the challenges that were faced ?
Appreciate your inputs in this regard. Thanks.