Last updated on MARCH 11, 2016
Applies to:Oracle Fusion Product Model - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
On : 126.96.36.199.0 version, Manage Product/Service Data-Manage Revisions/Versions
The behavior is inconsistent: the first revision for the item in the master organization is created with the current date/time, but the first revision for the item in the child organization is created with the date from the import file. It is also not consistent with the online behavior. When you assign an item to an organization, the system creates the first revision with an effective date that is equal to the current date/time. The expected behavior is that the first revision of an item (or item org) is always created with an effective date set to the current date/time.
Date handling should be consistent within each process and between assocated processes.
The issue can be reproduced at will with the following steps:
1. Test Case 1: Import a new master item with the first revision => Success (current date)
2. Test Case 2: Import a the child item with the first revision => Failure (date from import file)
3. Test case 3: Assign an item to an organization => Success (current date)
4. Test Case 4: Same as 2, but without mapping of the revision effective date in the import map => Success (current date)
Note: Scenario is to include the revision effective date in the import map, because also using the import map to create other revisions for the items and those revisions should include the effective date.
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