Using Model Design

This document describes how Dynamic Planning integrates with Structured Planning application. This is the traditional method of integrating with Structured Planning.

• Dynamic Planning pulls data from the Structured Planning

• Users can analyze and report on the data.

• Users can drill through rollup data in Dynamic Planning to see the original data aggregated from Structured Planning.

• Users can modify the data within Dynamic Planning and then write the data back to Structured Planning.

Definitions

• Dynamic Planning: Dynamic Planning is a multidimensional engine that connects to the Financial Reporting cube in Structured Planning. It does not connect to the Sales cubes.

• Horizon: An internal name that provides a pathway to access Structured Planning for Metadata download.

• Soap: An internal name that provides a pathway to access Structured Planning for Data download.

• Tenant Code: This is the code for Structured Planning and represents the way you identify which application you want to download from. The Tenant Code is not necessarily the same as the Tenant Name for Structured Planning.

• Source model: A model called HACPM_Financial. It connects to the specified Structured Planning application and stores the entire set of metadata that exists in that application. It is the conduit to get data into the Master/Target model.

• Master model: A model with a name of your choice. It is also called the Target model as it is the target of the metadata and data to be copied from the Source model.

See:

• Connecting to the Structured Planning

• Setting up the Source Model in Dynamic Planning

• Validation Report for Duplicate Members

• Setting up the Target/Master Model using a Map