Get Started with Redwood: Oracle Cloud SCM and Purchasing
Requirement to Migrate POs with the Creation Date as Back Dated from Legacy system using FBDI.
in Purchasing
Summary:
During the migration of Purchase Orders (POs) from the legacy system to Fusion, there is a requirement to have the Creation Date backdated. However, we noticed that the PurchaseOrderImportTemplate.xlsm does not contain a specific field to capture the creation date.
Content (please ensure you mask any confidential information):
The client has a requirement that the converted Purchase Orders (POs) reflect their legacy system creation dates. This is to ensure that the migrated POs are not confused with newly created POs in the system.
Could you please advise on the approach to handle this requirement?
Version (include the version you are using, if applicable):
Tagged:
0