My Oracle Support Banner

PTO Model's Demand History Not Collected In Demantra (Doc ID 1953511.1)

Last updated on MARCH 26, 2019

Applies to:

Oracle Demantra Real-Time Sales and Operations Planning - Version and later
Information in this document applies to any platform.


On : version, LoadData

For some of the PTO Models , Demand history is not getting collected to Demantra staging table because that actual_shipment_date was not populated by the system for the orders for those PTO Models.
Customer has more order lines, and demand history for none of them is getting collected into staging table with one order line being exception where they have actual_shipment_date populated.

As per OM team there are some condition in OM where it happens .

The actual shipment date for top model line will not be populated for the following scenarios:
1) The included items are shipped in different deliveries.
2) Included items are shipped non-proportionally.

As per When Is The Actual Shipment Date Populated For Kit Parent Line? (Doc ID 847479.1)
SHIPPED_QUANTITY Is Not UPDATED On KIT Model If Components Of KIT Are Shipped On Different Deliveries (Doc ID 1470555.1)

PTO Models to be collected

The issue can be reproduced at will with the following steps:
1. Run Shipment and Booking History Collections
2, Check data

The issue has the following business impact:
The data is not available for users to work with


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

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