Planning Parameters Wrong After Collecting Shipment and Booking History (Doc ID 1382535.1)

Last updated on SEPTEMBER 08, 2016

Applies to:

Oracle Demantra Demand Management - Version 7.3.0 and later
Information in this document applies to any platform.
***Checked for relevance on 09-May-2013***

Symptoms

On : 7.3.0 version, LoadData

Notice the planning parameters max_sales_date, last_date_backup get set to the last booked order date. Also shipment quantities of zero are inserted into the shipment history. This causes the forecast based on shipment to be wrong.
To clarify. We do two collection runs. One for shipments with selection criteria for certain order types. And another for bookings with select criteria for other order types.
When we do the collection for bookings the date parameters get set incorrectly and affect the forecast. Because the bookings go all the way out to 2012 the max_sales_date gets set incorrectly. Also records with actual_quantity with non null values come over along with the bookings records.

EXPECTED BEHAVIOR
-----------------------
Expect max_sales_date to be set correctly when loading data into Demantra via Collect Shipment and Booking History

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Demand Management System Administrator
2. Nav: Collections -> Oracle Systems -> Shipment and Booking History
3. Run Collect Shipment and Booking History
4. Check to Collect Bookings Booked Items Requested Date

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms