Fusion PIM: When Importing New Item Revision Timestamp Of Effective Date Is Not Imported With Import Maps
Last updated on JANUARY 19, 2016
Applies to:Oracle Fusion Product Hub - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
The system does not import the time of effective date when importing a new revision for an existing item. It only imports the date, but not the time.
The issue can be reproduced at will with the following steps:
1. Add the desired timestamp (dd-mm-yyyy HH:mm:ss) format to EGI_TIME_STAMP lookup
2. Define import map that includes revision code and revision effective date
3. Create Item Batch and upload a new revision for an item with effective date as: 25-06-2014 15:58:56
4. Run item import
5. Note that revision effective date is 25-06-2014 00:00:00. The time has been ignored
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms