My Oracle Support Banner

SOCS Is Not Able To Handle Item Price History Having Timestamp With Miliseconds (Doc ID 2905605.1)

Last updated on OCTOBER 28, 2022

Applies to:

Oracle Retail Store Operations Cloud Service - Version 22.1 to 22.1 [Release 22.1]
Information in this document applies to any platform.

Symptoms

In SOCS, when doing an Item lookup and then checking the item Pricing, SOCS returns an error every time the item has Item Price History where the UPDATE_DATE contains milliseconds (example: 28-SEP-22 10.16.47.929140 PM).

"Unparseable date: "2022-09-28T22:16:47:929Z
Could not find property iterator in class oracle.adfmf.bindings.dbf.AmxCollectionModel"

This is happening in any item which suffered a price modification via the Third Party Pricing upload and then gets the Item_Price:History table updated with new records (where update_date is being set to a value which includes milliseconds of precision).

Steps to reproduce:

1. Upload a new price via Third Party Price Import. e.g do a price change for today.
2. Verify once the job runs that record is created in ITEM_PRICE and also be created at ITEM_PRICE_HISTORY once it becomes active.
3. Check in ITEM_PRICE_HISTORY that new record is there and has the UPDATE_DATE populated with milliseconds of precision.

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
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.