what is mean by Repository?

[Former Member]

hi friends

what is mean by Repository?

please explain me in detail?

[Former Member]

Hi,

Im working with A leading IT comp as SAP MDM consultant.

Pls go thru the following link.It gives Repositiry definition wrt MDM.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/607beabe-950f-2b10-7687-8256ace1...

Also pls go through following def'n..it will make ur concept more clear.

What is an MDM repository?

This is an appropriate place to begin, since

An MDM repository certainly includes a database of information

consisting of text, images, PDFs, and other data about each record, up

to millions of records for some repositories. But a master data repository

is much more than just a large database, and size by itself does not

make a database a master data repository; rather it is the richness and

complexity of the underlying information itself and the ways it can be

searched and published and not simply the number of records that

uniquely characterize an MDM repository.

Moreover, when an MDM repository of product information is published

as a catalog, the repository of master data is also a sales tool, which

lists the products offered for sale by a vendor and allows potential

customers to browse those products in a convenient way. Often, the

published catalog is the only point of contact a customer will have with a

vendor, which makes the presentation of the product information u2013 the

organization and the design of the published catalog u2013 critically

important to creating brand recognition and a distinct vendor identity. So

a published catalog is also about creating and reinforcing a corporate

image.

Hundreds of details, large and small, must be addressed to turn a

database into a meaningful master data repository, including:

u2022 Rich master data. Rich structured, master data is the essential

lifeblood of a usable MDM repository. For example, an MDM

repository of product information must contain much more than basic

transactional data consisting of just a part number, a price, and a

forty-character description for each product. Master data must

include not only fields of information common to all the products in

the repository, such as part number and price, but also detailed

product specifications (attributes) that may apply to only a subset of

the products. Master data should also include rich content such as

images, text blocks, and PDFs (for MSDS and other data sheets).

u2022 Classification. Rich master data is not enough. The records need to

be organized and classified into a taxonomy consisting of an arbitrary

hierarchy of categories and subcategories, the hierarchy may contain

any number of levels, and multiple simultaneous taxonomies may

coexist in the same MDM repository. And a single category must be

able to appear in multiple places within the hierarchy. For example,

in an MDM repository of product information, a printer accessories

category might be placed under both a printers category and an

accessories category.

Part 1: Basic Concepts

22 MDM Console

u2022 Product families. A printed catalog of product information provides

an excellent model for how information on groups of records within

an MDM repository of product information should be organized into

product families (also called units, presentations, or modules), which

further partition the products in each category into smaller groups of

products based upon the values of other fields and/or attributes. In

addition to the individual products that comprise the family, a product

family includes the family data (such as an image, a descriptive

paragraph, and feature bullets) as well as detailed specifications on

each of the products arranged into a well-structured tabular layout.

u2022 Product relationships. As a sales tool, a published catalog of

product information requires the wide variety of product relationships

that are essential for effective selling. Relationships include structural

relationships, such as assemblies (a u201CSKU of SKUsu201D), kits (a u201CSKU of

non-SKUsu201D), bundles (a u201Cnon-SKU of SKUsu201D), and matching sets

(e.g. nuts and screws), as well as merchandising relationships, such

as cross-sells, up-sells, accessories, and consumables. An MDM

repository of product information must be able to capture and

represent all of these product relationships.

[Former Member]

Hi Ramchandra,

This is a forum fro Master Data Mangement.

Whenever we speak about Data,we also need to talk about the storage of data.

Repository is a term used for storing data in an effective and structured form in the form of Tables and Fields.

A reository is nothing but a structure that has differnt types of tables and each table a number of fields where data corresponding to that can be placed.

Hope it helps

Kindly reward points if found useful

Thanks

Simona

[Former Member]

Hi Ramchandra,

I think MDM Repository is an appropriate place to begin, since the incorrect or at best incomplete answer is often that a master data repository is simply a database, and also since a SQL-based RDBMS is often used for managing master data.

An MDM repository certainly includes a database of information consisting of text, images, PDFs, and other data about each record, up to millions of records for some repositories. But a master data repository is much more than just a large database, and size by itself does not make a database a master data repository; rather it is the richness and complexity of the underlying information itself and the ways it can be searched and published and not simply the number of records that uniquely characterize an MDM repository.

Moreover, when an MDM repository of product information is published as a catalog, the repository of master data is also a sales tool, which lists the products offered for sale by a vendor and allows potential customers to browse those products in a convenient way. Often, the published catalog is the only point of contact a customer will have with a vendor, which makes the presentation of the product information u2013 the organization and the design of the published catalog u2013 critically important to creating brand recognition and a distinct vendor identity. So a published catalog is also about creating and reinforcing a corporate image.

Hundreds of details, large and small, must be addressed to turn a database into a meaningful master data repository, including:

Rich master data

Rich structured, master data is the essential lifeblood of a usable MDM repository. For example, an MDM repository of product information must contain much more than basic transactional data consisting of just a part number, a price, and a forty-character description for each product. Master data must include not only fields of information common to all the products in the repository, such as part number and price, but also detailed product specifications (attributes) that may apply to only a subset of the products. Master data should also include rich content such as images, text blocks, and PDFs (for MSDS and other data sheets).

Classification

Rich master data is not enough. The records need to be organized and classified into a taxonomy consisting of an arbitrary hierarchy of categories and subcategories, the hierarchy may contain any number of levels, and multiple simultaneous taxonomies may coexist in the same MDM repository. And a single category must be able to appear in multiple places within the hierarchy. For example, in an MDM repository of product information, a printer accessories category might be placed under both a printers category and an accessories category.

Product families

A printed catalog of product information provides an excellent model for how information on groups of records within an MDM repository of product information should be organized into product families (also called units, presentations, or modules), which further partition the products in each category into smaller groups of products based upon the values of other fields and/or attributes. In addition to the individual products that comprise the family, a product family includes the family data (such as an image, a descriptive paragraph, and feature bullets) as well as detailed specifications on each of the products arranged into a well-structured tabular layout.

Product relationships

As a sales tool, a published catalog of product information requires the wide variety of product relationships that are essential for effective selling. Relationships include structural relationships, such as assemblies (a u201CSKU of SKUsu201D), kits (a u201CSKU of non-SKUsu201D), bundles (a u201Cnon-SKU of SKUsu201D), and matching sets (e.g. nuts and screws), as well as merchandising relationships, such as cross-sells, up-sells, accessories, and consumables. An MDM repository of product information must be able to capture and represent all of these product relationships.

Hope this will assist you inunderstanding about Repositoty.

Regards,

Krutarth

[Former Member]

Hi,

1. A Repository is a database where we make an unstructured information into a Structured form. To make this data into structured form we use various types of tables which are provided in the repository.

It is simply a database.

2. A master data repository is much more than just a large database, and size by itself does not make a database a master data repository; rather it is the richness and complexity of the underlying information itself and the ways it can be searched and published and not simply the number of records that uniquely characterize an MDM repository.

We can perform various functions on a repository:

1. Archive and Unarchive Repository

2. Unlock Repository

3. Update Repository

4. Duplicate Repository

5. Compact Repository

6. We can make Master and Slave Repositories.

Regards

Richa

[Former Member]

Repository is like database just the MDM uses term Repository for storing tables and fields or say schema.

See this link:

http://help.sap.com/saphelp_mdm550/helpdata/en/25/75ad42e473b111e10000000a155106/content.htm

BR,

Alok