Map Maintenance

The Map Maintenance window facilitates to control how dimension members are shared among users within an information domain. You can map multiple hierarchies to user groups available in OFSAAI so that the mapped members only can be viewed by the users belonging to that user group. You can set a mapper definition as the default Security mapper for an information domain. Based on the members mapped in a security mapper, the hierarchy browser window in OFSAAI framework displays the members of the hierarchy along with its descendants.

Note: Since a hierarchy’s member security is maintained at user group level, the member maintenance related functions like add, edit, copy, and delete will be the same for all users across all the enabled members in the hierarchy maintenance window.

To access the Map Maintenance window, you should be mapped to Access role. To create, modify, and delete a mapper, you should be mapped to Write role. To view a mapper, you should be mapped to Read Only role. The roles mapped to Map Maintenance are Mapper Access, Mapper Advanced, Mapper Authorize, Mapper Phantom, Mapper Read Only, and Mapper Write.

The Map Maintenance window displays the Name, Version, Description, Dynamic, Inherit Member, Map Type, and Database View name for the available mapper definitions created in the selected Segment and Infodom. Segments facilitate classification of related metadata in a single segment. You have access to only those metadata objects that are mapped to the same segment that you are mapped to.

Create Mapper Definition
Mapper Maintenance
Default Secure Map
Modify Mapper Definition
Copying Mapper Definition
Delete Mapper Definition

Create Mapper Definition

This option allows you to create a mapper definition by selecting the required hierarchies. You can create a data filter or security filter type mapper definition. For a security filter mapping, you should select the default user group hierarchy present in OFSAAI as a hierarchy. You can select up to 9 hierarchies in a mapper definition.

To create a new mapper definition from the Map Maintenance window:

Click Create new Map button from the tool bar. The Mapper Definition screen is displayed.

All BMM Hierarchies including the default user group hierarchy for the selected infodom are listed under the Members pane.

Enter the mapper definition details as tabulated:

Field	Description
Fields marked in red asterisk (*) are mandatory.
Description	Enter a description for the map definition in this field.
Dynamic	By default, the checkbox is selected and you do not have the option to deselect this. The dynamic attribute is associated with a mapper definition which facilitates the accommodation of latest members of a slowly changing dimension by leveraging the push down functionality.
Map Type	This drop-down list is enabled only if the Dynamic checkbox is selected. Otherwise, data filter is selected and this field is disabled. Select the Map type. The available options are: Data Filter: Select this option to define a data filter type mapping, which does not require a user group hierarchy to be selected among the participating hierarchies. Security Filter: Select this option to define a security filter type mapping, which can be used to restrict access to members of a hierarchy based on user groups. For a security filter, the user group hierarchy should be attached with the definition. You can add other hierarchies to this definition and will not have the option of saving the mapper definition without using a User Group hierarchy.
Pushdown	Select the checkbox if you want implicit push down of the mappings whenever mappings are modified and saved through the Mapper Maintenance window.
Database Entity Name	Enter the name for the table/entity to be created in the atomic schema that will be used to store the exploded mappings. The database entity name can be alpha numeric, however should not start with a numeric character.
Comments	Enter any additional information about the mapper definition.
View Name	Enter the view name of the selected database entity.

Click the required hierarchies from the Members pane. The selected hierarchies are displayed under the Selected Members pane.

Note the following:

- User group hierarchy should be selected for a security mapper definition. If not selected then a validation message providing information about the User Group hierarchy to be selected is displayed back to the user during the save operation.
- The Hierarchies selected in the Mapper Definition window should not contain special characters “~” (Tilda) and “$” (Dollar) in their node descriptions.

Click Save to save the map definition details.

The Map definition is saved with the version number as 1 in the authorized state.

Mapper Maintenance

The Mapper Maintenance feature allows you to define the mappings among the participating hierarchies in the Mapper Definition window. You should select at least one member from each hierarchy to define a mapping. You can add multiple mappings among the hierarchies. The mappings will be stored in the database entity/table you have created during the mapper definition for further processing i.e. push down operation. After defining all mappings, you can push down the mappings to be effective in the system (The push down will be implicit if the same was opted at the mapper definition time).

To define the mappings:

From the Map Maintenance window, select the mapper definition and click Mapper Maintenance. The Map window is displayed.

Based on the hierarchies participating in the mapper definition, the search fields will be displayed.

Click Add on the Member Combinations toolbar.

The hierarchies that were selected in the Mapper Definition window appear in the Add Mappings window, along with their members.

Select the required hierarchy members from each hierarchy and click View Mappings to view the already available mapping combinations with the selected hierarchy members. The View Mappings window is displayed.
To add a new mapping, select the required hierarchy members from each hierarchy and the corresponding user group to which you want to map in case of security mapper and click Go. Each mapping definition gets listed in the below grid. You should select at least one member from each hierarchy to obtain a complete mapping.

Note: If a child is mapped and parent is not mapped, the parent will be displayed as disabled in the hierarchy browser window.

Enter the mapping details as tabulated:

Field	Description
Fields marked in red asterisk (*) are mandatory.
Macro	This drop-down list allows you to define conditions based on which the members will be mapped. The options are: Self Only: Select this option if you want only the selected member to be mapped. If this option is selected, the hierarchy browser will display the selected member in enabled mode. If it has any descendants, those will be displayed in disabled mode. Self & Desc: Select this option if you want the selected members along its descendants to be mapped.
Exclude	Select Yes if you want to exclude certain members from being mapped. For example, if you want to map a hierarchy to all user groups except one user group say UG1, then map the hierarchy to UG1 and select the Exclude option as Yes. This will ensure that all users belonging to user groups except UG1 can access all the members of the hierarchy.

Click Save. All the mappings will be listed in the Member Combinations pane.
You can use the copy functionality to copy an already created mapping and edit the required fields. To copy a mapping:

Select the mapping you want to copy, from the Member Combinations grid and click Copy. The Copy Mapping window is displayed with all Hierarchies participating in the mapping.
Select the Macro and Excluded information for the mapping and click Save. The copy of the mapping will appear in the Member Combinations grid.

Click Pushdown to refresh the mapping of participating hierarchies available in the system. A service will push down the mappings based on config schema data (used combinations having macros) in to the atomic schema (exploded mappings). The pushed down mapping i.e. the exploded mappings will be displayed in the Mapped Members pane.
Select a mapping from the first panel and click Remove if you want to remove the mapping from the mapper. You should click Pushdown to effect these changes in the system.

Default Secure Map

This option allows you to set a mapper definition as the default security mapper at infodom level. You can have different security filter type mapper definitions but in OFSAAI platform, the default security mapper is used to provide hierarchy member security. If a mapper is not set as a default security mapper, hierarchy browser will display all the members of the hierarchy in enabled mode and hierarchy member security will not be available under such circumstances.

Click Default Security Map on the toolbar to set a mapper as a default secure mapper. Once selected, this information will be displayed in the mapper summary window. A delete icon will also be available adjacent to it to remove the default security map from the system.

Note: A Security Filter type mapper definition having the user group hierarchy (seeded by OFSAAI) in its definition can only be identified as a default security mapper and this validation will be performed by the application. When a mapper is set as the default security map in an information domain, it overrides the existing default security map if present in the infodom.

Modify Mapper Definition

You can update only the Comments field and the pushdown option. You need to have Write role mapped to your user group to modify a Mapper definition.

To update the Map Maintenance details in the Map Maintenance screen:

Select the checkbox adjacent to the required Mapper code.
Click Edit from the tool bar. The Mapper Definition screen is displayed.
Update the Comments field or the push down option as desired (The push down option will be available for edit only in case of dynamic mapper definitions and this option will be disabled in case of non dynamic mapper definitions). For more information, see Create Mapper Definition.
Click Save and update the changes.

Copying Mapper Definition

The Copy Mapper Definition allows you to quickly create a new Mapper Definition based on the existing hierarchies and mappings. You cannot remove the existing hierarchies, but can add up to 9 hierarchies (including the existing ones). If you are adding a new hierarchy to the Mapper definition, which is already mapped, then you should select a hierarchy that has default data. Otherwise, an alert message is displayed prompting you to select a hierarchy with default data.

You cannot edit the fields Dynamic and Map Type.

To copy an existing Mapper Definition in the Map Maintenance window:

Select the checkbox adjacent to the Mapper Name which you want to copy.
Click Copy in the tool bar. The Copy button is disabled if you have selected multiple checkboxes. The Mapper Definition- Copy window is displayed.
Specify a new Description and Database Entity Name.
Select the required hierarchies from the Members pane. The selected hierarchies are displayed under the Selected Members pane. For more information, see Create Mapper Definition. Click Save.

The new Mapper definition details are displayed in the Map Maintenance window. Select the new Mapper and click Mapper Maintenance button on the tool bar to add mappings to the newly added hierarchies.

Delete Mapper Definition

You can remove the Mapper definition(s) which are created by you and which are no longer required in the system by deleting from the Map Maintenance screen. You need to have Delete Mapper definition function role mapped to delete a Mapper definition.

To delete a Mapper definition from the Map Maintenance screen:

Select the checkbox adjacent to the required Mapper definition code.
Click Delete in the tool bar. A confirmation dialog is displayed.
Click OK. The Mapper definition details are deleted.