Importing Flexfield View Objects

  To import the GL Accounting Flexfield view objects and map them to the corresponding GL Accounting Qualified Segment/Nonqualified Segment logical dimensions:

  1. Repeat Steps 1 through 4 in Importing BI Account View Objects through to select the Financials and Supply Chain Management connection pool as the data source to import.

  2. On the Select Metadata Objects screen, in the Import Options section, select Import selected objects only. Then, from the Data source view pane, select the view objects that you want to map to the segment dimensions in the Available list on the left.

    Figure 20. Import Metadata Wizard: Select the Flexfield Tree Code and Tree View Objects to Import for the Tree Based Segment Logical Dimensions

    This screen shot displays the Import Metadata Select Metadata Objects Wizard. Select the Flexfield Tree Code and Tree view objects to import for the Tree Based Segment logical dimensions.

    Figure 21. Import Metadata Wizard: Select the Flexfield Value Set view objects to import for the Value Set Based Segment Logical Dimensions

    This screen shot displays the Import Metadata Select Metadata Objects Wizard. Select the Flexfield Value Set view objects to import for the Value Set Based Segment logical dimensions.
  3. Select Right arrow icon. to move them to the Selected list in the Repository View Pane on the right.

  4. After you have moved all the view objects that you want to import to the Selected list, select Next to proceed.

  5. In Map to Logical Model, select Core for Business Model to Map to and verify Create Logical Joins is unchecked. By default, it sets the logical tables and columns with the same names as the imported physical tables and columns.

  6. Under Table Mapping, for each applicable physical table, select VO Type to Query Only and verify that Hierarchy is clear. Then select Icon to clear the default logic table. to clear the default logical table mapping and select the existing segment logical dimension that it should map to.

    1. Map the Flexfield Tree Code and Tree view object physical tables to their corresponding Tree Based Segment logical dimensions. Figure 22, Selecting the Tree Based Segment Logical Dimension to which the Flexfield Tree Code and Tree View Objects are Mapped shows the table mapping from the GL Balancing Flexfield Tree Code and Tree view object physical tables to the GL Balancing Segment logical table.

      Figure 22. Selecting the Tree Based Segment Logical Dimension to which the Flexfield Tree Code and Tree View Objects are Mapped

      This screen shot displays the Import Metadata Map to Logical Model Wizard for selecting the Tree Based Segment logical dimension to which the Flexfield Tree Code and Tree view objects are mapped.
    2. Map the Flexfield Value Set view object physical tables to their corresponding Value Set Based Segment logical dimensions. Figure 23, Selecting the Value Set Based Segment Logical Dimension to which the Flexfield Value Set View Object is Mapped shows the table mapping from the GL Natural Account Flexfield Value Set view object physical tables to the GL Natural Account Segment logical table.

      Figure 23. Selecting the Value Set Based Segment Logical Dimension to which the Flexfield Value Set View Object is Mapped

      This screen shot displays the Import Metadata Map to Logical Model Wizard for selecting the Value Set Based Segment logical dimension to which the Flexfield Value Set view object is mapped.
  7. Under Column Mappings, for each applicable physical table, select Icon to clear the default logic table. next to logical dimension name to clear all default logical columns that are created at the end of the wizard process. Then select the existing logical dimension column that it should map to.

    1. Map these Tree Code view object physical columns:

      Table 4. Mapping for Tree Code view object

      Physical ColumnsLogical Columns
      TreeCodeTree Code
      TreeVersionIdTree Version ID
      VersionEffectiveStartDateEffective From
      VersionEffectiveEndDateEffective To
      VersionNameTree Version Name
    2. Map these Tree view object physical columns:

      Table 5. Mapping for Tree view object

      Physical ColumnsLogical Columns
      TreeCodeTree Code
      TreeVersionIdTree Version ID
      Dep0Pk1ValueSegment Value Set Code
      DistanceFixed Hierarchy Level
      Dep0ValueSegment Code
      Dep0DescriptionSegment Description
      Dep1ValueLevel 1 Code
      Dep1DescriptionLevel 1 Description
      Dep2ValueIdLevel 2 Id
      Dep2ValueLevel 2 Code
      Dep2DescriptionLevel 2 Description
      DepnValue/DepnDescription

      Level n Code/Level n Description

      where n is an integer from 0 to 31

      Dep31ValueLevel 31 Code
      Dep31DescriptionLevel 31 Description
    3. Map these Value Set view object physical columns:

      Table 6. Mapping for Value Set view object

      Physical ColumnsLogical Columns
      ValueSegment Code
      ValueSetCodeSegment Value Set Code
      DescriptionSegment Description
  8. Select Finish to complete the import and mappings.