Demantra S&OP Integration with

ASCP
An Oracle White Paper
Nov 2011
Demantra S&OP Integration with ASCP

Contents
Introduction ......................................................................................................... 3
Integration Setup ................................................................................................ 3
Troubleshooting Tips......................................................................................... 5
EBS integration patch required for Demantra S&OP collections ............. 7

Demantra S&OP Integration with ASCP Page 2

Demantra S&OP Integration with ASCP

Introduction

The scope of this document is to outline Demantra Inbound RTS&OP integration with a
standalone EBS Planning instance. The Demantra Sales and Operations Planning integration with
EBS leverages and extends the existing integration between EBS and Demantra Demand
Management. Setting up this integration in a standalone VCP instance has been a recurring issue.
For customers using EBS Order Management some of the steps are run as part of running
Standard Collections, however, customers using Custom Collections to bring Shipping/Booking,
Item and Location data have to run these steps manually.

Integration Setup

1. Run 'Update Synonyms' request:

From 'Demand Management System Administrator' go to
Others --> Requests --> Submit New Request --> Single Request

Choose 'Update Synonyms' program.

The Update Synonyms concurrent program has a hidden parameter p_schema_name. If

the user has only one Demantra schema then the user can leave the parameter to be hidden.
If the user has multiple Demantra schemas then user can enable hidden parameter to be
visible.

From System Administrator Responsibility go to

Concurrent --> Program --> Define

Demantra S&OP Integration with ASCP Page 3

 After enabling the parameter, when the user submits the concurrent program then the user
can specify against which Demantra schema user wishes to run the concurrent program.

2. Run 'Configure Legacy Profiles' request

From 'Demand Management System Administrator' go to
Others --> Requests --> Submit New Request --> Single Request

Choose 'Configure Legacy Profiles' program, parameters to this program are:

a. Instance - legacy source instance
b. Master Organization - Master organization where items, item attributes, product
category assignments are defined.
c. Category Set Name - item category set name (optional)

3. (Pre-VCP 12.1.3) Run 'Push (Legacy) Setup Parameters' manually

Run the following from APPS schema on the APS instance:
apps.msd_dem_push_setup_parameters.push_legacy_setup_parameters( errbuf, retcode,
sr_instance_id);

parameter1 - OUT parameter of type VARCHAR2

parameter2 - OUT parameter of type VARCHAR2
parameter3 - sr_instance_id of the legacy source instance chosen in previous step
Check that the table MSD.MSD_DEM_SETUP_PARAMETERS is populated.

(VCP 12.1.3 and above)

Running 'Push (Legacy) Setup Parameters' manually is not required on VCP 12.1.3.x
On VCP 12.1.3.x and they should be using the seeded flat file load program to load data
into Demantra. As a result of the above, it (Push Legacy Setup Parameters) will be run
automatically when flat file load (DemHistory.dat) is done, you don't need to run it manually.

4. Bounce the Demantra application server

5. Download Plan Scenarios workflow, runs MSD_DEM_SOP.LOAD_PLAN_MEMBERS

to load enabled plan Ids, ASCP plans marked Use for Sales & Operations Planning under
Plan Options.

Demantra S&OP Integration with ASCP Page 4

 6. Download Plan Scenario Data workflow runs the CollectData stored procedure step
MSD_DEM_SOP.LOAD_PLAN_DATA (<supply_plan_id>), to load data for the
selected supply plan.

<supply_plan_id> - supply_plan_id from the table supply_plan for the ASCP plan for
which download is being run.

Workflow populates the following tables:

T_SRC_ITEM_TMPL
T_SRC_LOC_TMPL
T_SRC_SALES_TMPL
BIIO_SUPPLY_PLANS
BIIO_SUPPLY_PLANS_POP
BIIO_OTHER_PLAN_DATA
BIIO_RESOURCES
BIIO_RESOURCE_CAPACITY
BIIO_SCENARIO_RESOURCES
BIIO_SCENARIO_RESOURCE_POP

Please note that Item and Location data load may need to be customized based on the
hierarchy changes made to the Demantra Data model CustomHooks package in the Apps
schema can be used to populate custom hierarchy levels.

Troubleshooting Tips
If the Demantra staging tables are not populated with data correctly review the checklist below:

1. Check that AppServerURL parameter is setup correctly in Demantra in SYS_PARAMS

table.

2. Check for locks on Demantra staging tables You may need to wait for certain processes
to finish or kill hung processes.

3. Insufficient privileges to Demantra/Apps schema users:

Demantra S&OP Integration with ASCP Page 5

 a. Demantra schema should have UTL_HTTP/ACL privileges - Run the
SYS_GRANTS.sql script that comes as part of the Demantra installer to grant
privileges to the Demantra schema user.

b. Demantra schema should have insert/delete/select privilege on

MSD.MSD_DEM_DATES table

c. APPS schemas require execute permission on

API_NOTIFY_APS_INTEGRATION,
API_MODIFY_INTEG_SERIES_FDATE in Demantra schema.

4. Check for profile MSD_DEM_MASTER_ORG in MSD_DEM_SETUP_PARAMETERS,

this profile is required and is used to determine item to product family/category rollups.

5. If DATA_CLEANUP.CLEAN_LEVEL_DATA script was used to clean level members

from the Demantra schema, check for missing scenario status codes in scenario_status
table, default members could have been removed by the clean up script - Run
Call_Data_Model procedure to validate the schema and insert missing default level
members.

6. Check msc_sales_channel and msc_demand_classes tables, at least dummy entries are

required to be setup and collected into ASCP. If there are no demand classes / sales
channels setup in EBS create one dummy entry each and collect them.

7. If series quantity (query the views below) have a very large value, it may exceed size of
series columns in Demantra staging tables (BIIO_Other_Plan_Data).

List of views to check for data:

Constrained Shipment Forecast MSD_DEM_CONSTRAINED_FORECAST_V

Planned Production
Available Resource Capacity
Required Resource Capacity
Available Supplier Capacity
Required Supplier Capacity
Safety Stock
Beginning On-hand
MSD_DEM_PLANNED_PRODUCTION_V
MSD_DEM_AVAIL_RESOURCE_CAP_V
MSD_DEM_REQR_RESOURCE_CAP_V
MSD_DEM_AVAIL_SUPPLIER_CAP_V
MSD_DEM_REQR_SUPPLIER_CAP_V
MSD_DEM_SAFETY_STOCKS_V
MSD_DEM_BEGINING_ONHAND_V

Demantra S&OP Integration with ASCP Page 6

 Dependent Demand MSD_DEM_DEPENDENT_DEMAND_V
Planned Shipments MSD_DEM_PLANNED_SHIPMENTS_V

EBS integration patch required for Demantra S&OP collections

accurate as of May 2011
For Demantra 7.3.0.2 EBS VCP instance supported is 12.1.3

For Demantra 7.3.1 EBS VCP instance supported is 12.1.3.2

Refer to MOS DOC ID 470574.1 (List Of High Priority Patches For Oracle Demantra Including
EBS, Siebel and E1 Integrations) for current information and details.

Demantra S&OP Integration with ASCP Page 7

Demantra S&OP Integration with ASCP
May 2011

Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.

Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com

Copyright 2007, Oracle. All rights reserved.

This document is provided for information purposes only and the
contents hereof are subject to change without notice.
This document is not warranted to be error-free, nor subject to any
other warranties or conditions, whether expressed orally or implied
in law, including implied warranties and conditions of merchantability
or fitness for a particular purpose. We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document. This document
may not be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without our prior written permission.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
Other names may be trademarks of their respective owners.