Hi all,
Our implementation partner is embarking on DM of product data containing a legacy item number (six digit numeric number) and a legacy product number (30 char string) to F&O as Released Engineering Products and product respectively. We are currently finding this very difficult using OOB data entities. There's 1:1 relation between the item number and the product number.
We want to take legacy product number across as PRODUCT in F&O and the legacy item number as it's released engineering product.
When we use Released Engineering Products Creation data entity to load our product we face following issues,
1. If number sequence for released product is automatic, once products and versions are loaded using the above entity, the newly created released engineering product get sequential number.
2. If number sequence for released product is manual, once products and versions are loaded using the above entity, the newly created released engineering product number is the same as the product number we imported.
Both scenarios do not meet our requirements that we want to preserve the 1:1 relationship between the legacy item number and legacy product number in F&O after migration and currently, we are unable to link the legacy numbers together during the DM process.
Has anyone come across this issue?
Is there a workaround instead of data entity development?
Thanks