cancel
Showing results for 
Search instead for 
Did you mean: 

Repository Tables

Former Member
0 Kudos

Hi all,

I want to know about the different types of tables in repository.

And also i want to know its fucntionalty and usage.

Related links, documents & PPT are highly appreciated.

Please dont send help.sap.com link.

Regards,

Vijay

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Vijay,

I want to know about the different types of tables in repository.

And also i want to know its fucntionalty and usage.

Related links, documents & PPT are highly appreciated

First of all SAP explanation about the types of tables in MDM:

Table Type

Description

Main table and subtables

Flat

Main table or subtable. A flat table has the standard, rectangular SQL structure consisting of records and fields (rows and columns). The main table of an MDM repository is always a flat table.

Hierarchy

Subtable. A hierarchy table organizes information in a hierarchy, where each record is related to a parent record (even if the only parent is the root) and may also be related to sibling records and/or child records. The main table in an MDM repository typically contains some fields whose data may be hierarchical in nature.

For example, a Manufacturer field may need to accommodate division and subdivision information for manufacturers.

This hierarchical information is stored in a separate, hierarchy subtable associated with the Manufacturer lookup field in the main table.

Most of the hierarchy tables used in an MDM repository contain lookup information for fields in the main table. Other hierarchy tables in MDM include taxonomy tables, the Masks table, and the Families table, described below. MDM supports hierarchies with an unlimited number of parent/child levels.

Taxonomy

Subtable. A taxonomy is the classification scheme that defines the categories and subcategories that apply to a collection of records. Categorizing records enables you to isolate subsets of records for various organizing, searching, editing and publishing purposes.

A taxonomy table in MDM stores a hierarchy of categories and subcategories and also supports attributes, u201Csubfieldsu201D that apply to particular categories rather than to the entire collection of records. MDM supports multiple simultaneous taxonomies.

Qualified

Subtable. A qualified table in MDM stores a set of lookup records, and also supports qualifiers, u201Csubfieldsu201D that apply not to the qualified table record by itself, but rather to each association of a qualified table record with a main table record. MDM supports multiple simultaneous qualified tables.

Qualified tables can be used to support product applications and application-based search, and also to store any large set of subtable records that contain fields whose values are different for each main table record, such as multiple prices for different quantities, divisions, regions, or trading partners, cross-reference part numbers, and additional distributor/supplier/customer-specific information for different distributors, suppliers, or customers.

Object tables

Images

A single table named Images. Stores image files, where each image is stored as a record in the table

Sounds

A single table named Sounds. Stores sound files, where each sound file is stored as a record in the table

Videos

A single table named Videos. Stores video files, where each video file is stored as a record in the table

Binary Objects

A single table named Binary Objects. Stores other binary object files, where each binary object file is stored as a record in the table

Text Blocks

A single table named Text Blocks. Stores blocks of text, where each text block is stored as a record in the table

Copy Blocks

A single table named Copy Blocks. Stores blocks of text interpreted as copy, where each text block is stored as a record in the table

Text HTMLs

A single table named Text HTMLs. Stores blocks of text interpreted as HTML, where each text block is stored as a record in the table

PDFs

A single table named PDFs. Stores PDF files, where each PDF is stored as a record in the table

Special tables

Image Variants

A single table named Image Variants. Used to define the structure and format of each of the variants for each image. Each variant is a modified version derived from an original image; the original image is never modified. This table is managed in the MDM Console and is not visible in the MDM Client.

Masks

A single hierarchy table named Masks. In concept, a mask acts like a stencil, in that it blocks (u201Cmasksu201D) all main table records from view except the defined subset of records that are included in the mask, to allow the subset to be viewed and manipulated as a whole. A mask is a static snapshot of the set of records that are included in the mask (as opposed to a view or a named search, where the results set is determined dynamically every time the search is run). Each record in the Masks table is the name of a subset of main table records. MDM supports an unlimited hierarchy of masks.

Families

A single hierarchy table named Families. Used to further partition main table records in each category into smaller groups based upon the values of other fields and/or attributes. You can associate family data (a paragraph, an image, bullets) once with a family of products rather than with each individual product, and also define the table layout of the field and/or attribute data (field order; stack, vertical, and horizontal pivots; and other display options). This table is available only in Family mode.

Relationships

A single table named Relationships. Used to define each of the different record-level relationships. Each relationship can be either bidirectional (sibling) or unidirectional (parent-child). This table is managed in the MDM Console and is not visible in the MDM Client, although the relationships between records can themselves be created and edited in Record mode.

Workflows

A single table named Workflows. Stores the workflows of an MDM repository, where each workflow is stored as a record in the table. Workflows are created and edited in the MDM Client.

Named Searches

A single flat table named Named Searches. A named search is a static snapshot of the search selections that were in effect when the named search was created (as opposed to a mask, which is a snapshot of the subset of records), where the results set itself is determined dynamically when it is selected. Each record in the Named Searches table returns a subset of main table records. MDM supports 400 named searches per repository.

Data Groups

A single hierarchy table named Data Groups. (Does not appear anywhere in the MDM Console.)

Stores the hierarchy of data groups used to break the entire set of objects in the MDM repository into manageable subgroups.

Validation Groups

A single hierarchy table named Validation Groups.

Stores the hierarchy of validation groups used to organize multiple validations for subsequent execution as a group.

System tables

Roles

A single table named Roles. (Appears in the MDM Console under the Admin node and cannot be deleted.)

One of three tables used to implement MDM repository security and access control. Each role can selectively grant or deny access to any MDM function and to any table or field. This table is managed in the MDM Console and is not visible in the MDM Client.

Users

A single table named Users. (Appears in the MDM Console under the Admin node and cannot be deleted.)

One of three tables used to implement MDM repository security and access control. Each user can have one or more roles. This table is managed in the MDM Console and is not visible in the MDM Client.

Connections

A single table named Connections. (Appears in the MDM Console under the Admin node and cannot be deleted.)

One of three tables used to implement MDM repository security and access control. Contains an entry for each MDM client application currently connected to the repository. This table is not visible in the MDM Client.

Change Tracking

A single table named Change Tracking. (Appears in the MDM Console under the Admin node and cannot be deleted.)

Allows you to specify the fields for which adds, modifies, and deletes should be tracked and stored in the Change Tracking table.

Remote Systems

A single table named Remote Systems. (Appears in the MDM Console under the Admin node and cannot be deleted.)

Used to define the different Remote Systems for import and export. Each specifies whether it supports inbound, outbound, or both. This table is managed in the MDM Console and is not visible in the MDM Client.

Ports

A single table named Ports. (Appears in the MDM Console under the Admin node and cannot be deleted.)

Used to encapsulate the logistical and configuration info for inbound and outbound processing of MDM data, for consolidation and distribution respectively. This table is managed in the MDM Console and is not visible in the MDM Client.

Links

A single table named Links. (Appears in the MDM Console under the Admin node and cannot be deleted.)

Used to specify the URLs that can be used as the target of an embedded browser in the Web tab in the MDM Client. This table is managed in the MDM Console and is not visible in the MDM Client.

XML Schemas

A single table named XML Schemas. (Appears in the MDM Console under the Admin node and cannot be deleted.)

Used to identify the XML schemas for import and syndication. Each XML schema is the name of an .xsd file. This table is managed in the MDM Console and is not visible in the MDM Client.

Reports

A single table named Reports. (Appears in the MDM Console under the Admin node and cannot be deleted.)

Contains an entry for each report file generated by the various MDM repository operations, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.

Logs

A single table named Logs. (Appears in the MDM Console for each MDM Server rather than each MDM repository.)

Contains an entry for the log files generated by the MDM Server, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.

Qualifed Tables are complex to work as compared to Main Table and Look-up flats. Hence I would suggest you to go through the Qualified specially.

Now here are few links to know about them more and to use them :

Qualifed Tables & Main Table:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c03240fa-cc3e-2b10-aa9a-a5798e31...

Using Table Joins and Lookups in Qualified data Import:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1012f58f-a6e6-2a10-7caf-a46b7ad0...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00a15239-684e-2b10-b8ae-b936b7d1...

SAP Network Blog: So is that the qualifier or the non-qualifier?:

Relationship Table in MDM - Part 1:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e001fc23-704e-2b10-7092-86e574e2...

Hiearchy & Taxnomies:

Master Data Management Importing of Hierarchies or Taxonomies:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903c9530-52be-2a10-7d97-a48dc808...

Master Data Management Syndicator u2013 Flattening a Hierarchy Field into Single Field:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/003c0df5-1503-2b10-21ab-c976bfc8...

Remote system & Ports

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30843106-5539-2b10-75a9-da483911...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7051c376-f939-2b10-7da1-c4f8f9ee...

Import of Pdfs.https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c01f54a2-99f1-2a10-5aa5-dcc50870...

*How to Avoid Problems with your Data Model in SAP NetWeaver MDM u2013 Dou2019s and Donu2019ts (NW7.0)

*

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0d8aa53-b11d-2a10-aca2-ff2bd42a...

The last link will give you guidelines that you should follow while designing a data model.

Hope this info helps.

Thanks and Regards

Nitin Jain

Former Member
0 Kudos

Hi Vijay,

Plz refer to the following link.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e8d76c89-0a01-0010-b4b7-e1a...

Hope it helps.

Thanks,

Minaz

Former Member
Former Member
0 Kudos

Hi

MDM Repository mainly consists of following tables

1.Main Table(Products)

2.Look up Table( reference table)

3.Object Tables

4.System table

5.Special table

Main table stores the entire information about the record.Every repository has only one main table.

Look tables are used as reference or check table.They are of 4 types

a.Flat (for set of fixed values say eg.countries)

b.Qualified(for multivalued eg price of product depending on region and tax)

c.hierarchy(to create a hierachy of products)

d.Taxonomy-again hierarchy with special attribute for each node

Object table is used to store objects like images,pdfs,textblocks,copy blocks etc.Each time you create a repository server automatically creates instance of object table,system table and special table.

System table store info abt roles and users (security),Remote system that connect to MDM ,ports thru which remote system connect to MDM,Reports abt MDM repository,Logs abt MDM server.

Special tables are like image variant(holds info abt structure of image),Masks(to restrict users to view records),Family(to categorize records),Workflows(data governance),Data groups(Container for objects) etc.

Regards

Nisha

Edited by: Nisha L on Aug 21, 2008 9:29 AM

Former Member
0 Kudos

Hi Nisha,

Thanks for your reply.

Its would be very useful for me when you send me any documents related to this.

If you can please send to my personal ID.

I wil give you are interested.

Regards,

Vijay