SAP Commerce extensions to perform table-to-table replication in single-directionally manner between two SAP Commerce instances or between SAP Commerce and an external database.
After reviewing the UAT Hybris DB and CCV2 DB, I noticed some discrepancies in column names across both environments, despite the items.xml declarations being the same.
For example, in the user table:
On-prem (UAT): Column name is UniqueID
CCV2: Column name is p_uid
This likely stems from older Hybris versions (v4 and earlier) where uuid fields were defined as UniqueID, whereas newer versions use p_uid.
Similar differences exist across other tables, such as Code (on-prem) versus p_code (CCV2) in tables like Cart, Orders, and DeliveryModes
The schema migration creates all the extra new columns (code) and brings all that data however, the type system still references (p_code), so the p_code column remains empty in ccv2, but a new column code is created with all the data.
Could be this due type system version? (migration.ds.source.db.typesystemname, db.type.system.name)
Database engine source: Oracle
After reviewing the UAT Hybris DB and CCV2 DB, I noticed some discrepancies in column names across both environments, despite the items.xml declarations being the same.
For example, in the user table: On-prem (UAT): Column name is UniqueID CCV2: Column name is p_uid This likely stems from older Hybris versions (v4 and earlier) where uuid fields were defined as UniqueID, whereas newer versions use p_uid.
Similar differences exist across other tables, such as Code (on-prem) versus p_code (CCV2) in tables like Cart, Orders, and DeliveryModes
The schema migration creates all the extra new columns (code) and brings all that data however, the type system still references (p_code), so the p_code column remains empty in ccv2, but a new column code is created with all the data.
Could be this due type system version? (migration.ds.source.db.typesystemname, db.type.system.name)