EBS And Demantra Data Is Not Matching For 'Bill to' Customer Instead Of 'Ship to' Customer
Last updated on JANUARY 01, 2015
Applies to:Oracle Demantra Demand Management - Version 126.96.36.199 and later
Information in this document applies to any platform.
We bill to one customer A and ship to another customer B and also sometimes we Bill to customer B and ship to customer B.
We expect the forecast to be separately to Customer A and Customer B.
If Demantra forecasts to that ship to location and we move one level above it generates a forecast to default
bill to of that ship to. We will not be able to distinguish history for various actual bill to customers.
It would be good if the product actually looks at the sales order and map the demand at the lowest grain bill to and ship to of actual sales orders.
Which will generate accurate forecast and will have accurate history reported.
Shipment data to be collected by the 'Bill to' customer instead of 'Ship to' customer
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