Demantra is a stand-alone application that Oracle purchased back in 2006.

It specializes in creating demand forecast using a combination of advanced statistical tools. It is this forecast that Demantra interfaces to the Advance Supply Chain Planning (ASCP) module. It also can interface forecast variability or forecast error to the Oracle Inventory Optimization module but in our project we are only concerned with the forecast.

Demantra Integration With EBS - Forecast Flow To generate this forecast, Demantra will need three pieces of information from Oracle EBS. It will need to know what to forecast. It will need to know where the products are typically sold (i.e. sales channel, customer, planning organization). And, it will need to know historical sales information.

Demantra Integration With EBS - Forecast Data Elements The item and demand class information will provide the what for the forecast. The customer, organization, sales channel, and trading zone will provide the where for the forecast. To provide historical sales data, Demantra will load shipment and booking information from the Order Management and Shipping modules. Lets first look at how Demantra integrates the what and where information.

Integrating EBS Master Data (Customer, Organization, Items) into Demantra

Demantra loads the what and where data into two tables. The first one is for items (the what) and the second one is for location (the where). Using a data warehouse technique, the information from EBS de-normalized and inserted into a single record in the item and location table.

Demantra Integration With EBS - Forecast Item And Location Dimension For items you will have a record for each item, product category, product family, demand class combination. Demantra also creates a hierarchy for item.

Demantra Integration With EBS - Item Dimension Data For location, you will have a record for each customer site, customer account, customer, customer class, sales channel, trading zone, planning organization, operating unit, legal entity, business group combination. Demantra also creates hierarchies for customer and organizations.

Demantra Integration With EBS Location Dimension Data To interface master data from EBS to Demantra, you need to run the standard collection program set.

Demantra Integration With EBS - Standard Collections The data will not come directly from the Inventory, AR, or HR tables but will first be populated into the ASCP tables. Entity Item ASCP Table MSC_ITEMS ASCP Column to be Looked upon ITEM_NAME , DESCRIPTION

Sales Channel Organization Customer

MSC_SALES_CHANNEL MSC_TRADING_PARTNERS MSC_TRADING_PARTNERS

SALES_CHANNEL PARTNER_NAME PARTNER_NAME

Once you have the master data loaded into Demantra, you can interface the historical sales data.

Integrating EBS Transactional Data (shipments and booked orders) into Demantra
To interface transactional data from EBS to Demantra, you need to run the sales history program set. This set of programs will load staging tables and then run the load program. Integrating EBS Supporting Data (price lists, UOM conversion, currency, calendar) into Demantra There are separate load programs for the price lists, unit of measure, currency, and calendar data. This data helps convert different units of measure and helps convert days into fiscal periods.