You’re offline. This is a read only version of the page.
Announcements
214
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
For that, you would need a custom feature in data entity. Out of the box, there is only he option to product number match the product number in the engineering or take the next number in the number sequence.
Is a basic customization that you need to maintain your legacy numbers
#1
André Arnaud de Cal...
294,233
Super User 2025 Season 1
#2
Martin Dráb
232,982
Most Valuable Professional
#3
nmaenpaa
101,158
Moderator
Share
Report
All responses (
Answers (
