Publish to OLAP

The publishing process compares the dimensions and cubes of the OLAP model with those of the relational model. These objects are ignored or deleted according to the value of PreserveManualAddedObjects in the DEPM_MOD_MODEL metadata table.
Caution: 
The process does not check for manually added attributes, hierarchies, subsets, or rules.

You can use a non-SQL script to publish an OLAP model using the PublishCustomModelToOLAP function. In Application Engine, you can use the ModelingPublishCustomModelToOlap function.

Caution: 
Before you publish a model to OLAP, create a manual backup of the OLAP database. Ensure that only one user publishes to a particular OLAP database at any time.

If you use DEPM_MOD_FACTTABLE in your model, then the data in the cubes is overwritten by the publishing process. But, typically, you use cube mappings to load fact data because of the greater flexibility provided by the Clear, Add, and Overwrite options. In this case, the publishing process does not change existing data, unless the data structure is different.

Publishing to these applications is not supported:

  • BIFSM (FSM)
  • GHR
  • BICSI (Business Analytics)
  • BIIBP
  • DEPM

If you publish to Infor d/EPM business applications (DEPMAPPS), these rules apply:

  • Objects owned by Business Modeling are unaffected. They are managed in Business Modeling.
  • DACs and MDACs assigned to an object owned by Business Modeling are unaffected.
  • To add elements to hierarchies that are owned by Business Modeling, you must use Business Modeling.
  • You cannot assign global permissions to data roles of the business applications.
  • The only purpose of data roles that you publish to DEPMAPPS is the permission management of DAC, MDAC and TABACC cubes.