Managing Master Data

Nota:

• first you load the data into staging tables then you use a staging process to load the data into MDS models

1. Manage Leaf and Consolidated members
2. Update Attributes
3. Designate relationships to explicit hieracrhies
4. Entity
   1. stg.entityname_Leaf
      1. stg.entityname_Consolidated
         1. stg.entityname_Relationship

1. MDS Web Service
2. Subscription Views
   1. Expose
      1. All leaf members and their attributes
      2. All consolidated members and their attributes
      3. All collections and their attributes
      4. The members explicitly added to a collection
      5. The members in a derived hierarchy, in either a parent/child or level format
      6. The members in all explicit hierarchies for an entity, in either a parent/child or level format

1. Administrators
   1. MDS System Administrator

      Nota:

      • Only one system administrator , account have full access to everything even the explorer area
   2. Model Administrators

      Nota:

      • Have access to update Models , but only on the top level. The Model Administrator still requires access to functional areas. 
2. Regular Users
   1. Functional Area Access
      1. Explorer
      2. Version Management
      3. Integration Management
      4. Administration
      5. User and Group Management
   2. Model Object Permission

      Nota:

      • Access to model objects up to attribute level for granularity
      • Model object permissions apply to all entities , derived hierarchies, explicit hierarchies and collections of that model
      1. Overlapping Permisions

         Nota:

         • MDS will use the most restrictive
   3. Hierarchy Member Permission