My Oracle Support Banner

XITEM API Child Item LAST_UPDATE_DATETIME Not Updated after Parent Item Is Updated (Doc ID 2242689.1)

Last updated on NOVEMBER 07, 2018

Applies to:

Oracle Retail Merchandising System - Version 14.1.2 and later
Information in this document applies to any platform.

Symptoms



XITEM API- Child item's LAST_UPDATE_DATETIME is not getting updated after the parent item is updated.

When a parent item's FORECAST_IND is updated thru the XITEM API, this update is also applied to it's child items, as expected.
However, the LAST_UPDATE_DATETIME column only gets updated for the parent item, leaving this column inconsistent for the child item.

Steps to Reproduce:
1. Create a parent item thru the xitem API (xitemcre), with FORECAST_IND=N.
2. Create a child item for this item through the xitem API (xitemcre).
3. Update the parent_item through the xitem API(xitemmod), setting it's FORECAST_IND to Y.
4. Check the ITEM_MASTER table, the LAST_UPDATED_DATETIME will be incorrect for the child item.

Relying on this field to control changes to item data.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.