BusinessObjectConfiguration table maintenance

The BusinessObjectsConfiguration table is used to store localized business object names and their language translations. Use the BusinessObjectsConfiguration table to ensure proper configuration and data flow within the system.

In the BusinessObjectsConfiguration table you define which analysis dimensions of the Infor EPM integration are mapped to business objects of Business Modeling.

To maintain the BusinessObjectConfiguration table, go to the EPM Administrationand select Dashboard > Data Integrations > Relational Modeling > EPM Integration.

This table shows the properties of the BusinessObjectsConfiguration table:

Field Description Type
DefaultNameUsage Mapping identifier to match a localized business object name with a specific business object.

You must use one of these business object names:

  • Analysis 1-5
  • Analysis 7-11
  • Segments 1-3
  • Organizations
The UnitOfMeasure is a supported value if FinancialDimensionID = NULL.		 nvarchar
Name Localized business object name.

If left blank, then the Infor EPM default business object name is used. For example, Cost Center, Project, or Region.

 nvarchar
SequenceID Numeric value that describes to which dimension an element belongs when the SourceSystemGLMovement budget BOD is being sent to a source system.

SequenceID is also used to map a source system custom dimensions to the Analysis 1-5 and Analysis 7-11 integration tables

 integer
FinancialDimensionID Indicates the number of target dimensions for the Financial Reporting model publishing.

The valid values are from 0 to 12.

The DefaultNameUsage value must point to custom business objects defined in Business Modeling.

Note: In older versions, Unit of Measure was a custom business object and it used FinancialDimensionID = 0 to map an Analysis dimension to the XPADUNITOFMEASURE dimension.

If a row with FinancialDimensionID = 13 exists, the legacy publishing or import behavior applies; otherwise, the new Unit of Measure business object drives the publishing.

In the current design, the FinancialDimensionID for the UnitOfMeasure DefaultNameUsage value must be NULL.

 integer
This table shows an example of the BusinessObjectsConfiguration table mapping:
DefaultNameUsage value Mapped to dimension FinancialDimensionID value Published in OLAP dimension
Analysis01 Intercompany 1 GLDBUSINESSOBJECT01
Analysis03 Business Unit 2 GLDBUSINESSOBJECT02
Analysis02 Business Unit Partner 3 GLDBUSINESSOBJECT03
Analysis04 Region 4 GLDBUSINESSOBJECT04
Analysis07 Regions Partner 5 GLDBUSINESSOBJECT05
Analysis05 Product 6 GLDBUSINESSOBJECT06
Analysis08 Product Partner 7 GLDBUSINESSOBJECT07
Analysis10 Project 0 GLDPROJECT

The FinancialDimensionID has a fixed assignment to the GLDBUSINESSOBJECT dimension, for example FinancialDimensionID 1 links to the GLBUSINESSOBJECT01 dimension. This order is fixed in the cube definition and displayed in the report. Assign FinancialDimensionID based on its importance. The most important analysis dimension has FinancialDimensionID 1, as it is the first choice in the context. If less important dimensions are placed between more important ones, use perspectives to hide the less important dimensions. Perspectives cannot change the order of FinancialDimensionIDs.

Validate the content of the BusinessObjectConfiguration table before publishing the model. Make sure to follow these requirements:

  • The FinancialDimensionID value must be in range 0 to 12
  • The FinancialDimensionID values cannot be duplicated
    Note: 

    The GLDBUSINESSOBJECTXX, GLDPROJECT, and XPADUNITOFMEASURE dimensions that are not targeted by the values in the BusinessObjectConfiguration table are published containing only the built-in elements.

    The XPADUNITOFMEASURE is published from the Unit of Measure business object with a derived hierarchy. See Unit of Measure for the publishing rules and hierarchy structure.