Dear SDN fellows,
Currently in my project I encountered the case where 1 BW system is shared by 2 source systems (R/3 and ECC6) and the master data from the 2 source systems are overlapped (eg. same material no from R/3 and ECC6 have different meaning).
One of the suggestions is to concat master data value with source system ID as prefix. For example:
Material 4711 from ECC6 Source System = AB_4711
Material 4711 from R/3 Source System = CD_4711
However, I found that some master data having data type NUMC (eg. 0EMPLOYEE) that:
u2022 We need to use numeric value so that the prefix is consistent to all master data, hence we can no
longer use symbol like dash, underscore to separate prefix and master data value. This requires
thorough observation to all master data values, for example if we use prefix '99', whether this is safe and
doesn't overlap with existing master data that is not prefixed (we might only prefix master data for the
newly added R/3 source system, and if there is other new source system added in future; so that the
existing master & transaction data that have been live for 2 years using ECC6 source system are
not interrupted).
u2022 Some master data may have been populated with values with maximum length, thus to add the prefix
we need to extend the length of InfoObject (eg. 0COMP_CODE is CHAR(4) and normally uses
values: 1000, 1100, 1200, etc.). To be able to extend the length we have to delete all records in master
data, and consequently we have to delete transaction data in cubes that use master data as well, thus it
still impacts existing data.
Thanks alot.
regards,
arie
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.