Hi folks,
We have an interesting problem due to having different named default schemas in each of our 3 hana systems. For example lets say these are our default schemas in our development, staging, and production HANA systems;
DEV_SCHEMA
QA_SCHEMA
PROD_SCHEMA
Each of these replicating data from their corresponding SAP source systems.
Now, we have a view that is developed on DEV hana box and uses DEV_SCHEMA. When this view content is imported to QA or PROD we handle easily with schema mapping. All is well and good although we are not really a fan of this different naming and us developers did not choose this naming (self defense plea here for us brilliant developers whom never make such mistakes... PS: HI LARS! - Go Germany!)
Now we are setting up a connection from BW into HANA using system connection and inside this is a parameter called 'db user'. Although it's called db user it's actually looking for a SCHEMA name. If BW DEV is querying from HANA DEV this schema name would be DEV_SCHEMA. However if BW_QA is querying from HANA_QA then the name would need to be QA_SCHEMA but in our BW landscape we are locked in QA and PROD and normally can not and/or do not want to edit objects in non-native systems. Ideally what we need is our default schemas in HANA to have the same exact name throughout the HANA landscape.
All this said, I can see that it would be great to re-name our entire HANA landscape however that would be a HUGE monumental undertaking as all systems would need to be re-replicated again (at least I think).
Just curious if anybody else has named their schemas differently on each tier? What are most people doing? Naming the default schemas the same consistently or are you using schema mapping?
Thanks,
-Patrick