Master catalog and procurement catalog?

[Former Member]

Dear Experts,

Why do we need to map master catalog and procurement catalog? What is the difference between publishing out of master catalog and procurement catalog?

Could you please help me to understand the concept here?

Thanks and regards,

Ranjan

[Former Member · Accepted solution]

Master Catalog is a Procurement Catalog. Master Catalog is the the one that users will be able to see and not the supplier catalog. Thus you will need to map the items that a Supplier Catalog has to the Master Catalog. Then you can have views created so as to restrict the users from the viewing all or some of the materials.

Regards,

Surya

[jason_boggans]

Hi Ranjan,

Galem is correct, Support for CCM ends in a few years, no further development will take place there, moving to SRM-MDM now is a better option than having to migrate 3 years down the line.

SRM-MDM is also more scaleable than it's CCM predessor, a much better option for large Enterprise operations.

Regards,

Jason

[Former Member]

It's been a long time since CCM, but here's my answer as I remember it:

The reason is that CCM is an poorly thought out product. SRM-MDM is much better.

The logic behind it is this:

If you want to publish the Master Catalog, and only have one data repository to publish...you can do that.

When you have procurement catalogs, you must publish these and the Master Catalog is no longer publishable.

All data must come in a Supplier Catalog and be mapped to the Master Catalog. Then, you may further map this product data to other procurement catalogs.

[jason_boggans]

Hi Galem,

{When you have procurement catalogs, you must publish these and the Master Catalog is no longer publishable.}

This is not correct, the master catalog is never rendered 'unpublishable'. It acts as any other procurement catalog also with the added ability of being the central repository for data.

Regards

Jason

[Former Member]

All the above discussions are very good..

Muthu

[Former Member]

aha! I stand corrected. It has been three or four years

Bottom line, get the client to upgrade to SRM-MDM anyway as CCM won't be supported forever...and you're building an obsolete skill set.

[Former Member]

Dear All,

Thanks a lot for such a lively discussion? I now got whole concept of master catalog and Procurement catalog. Whatever understanding i have of SRM MDM catalog, I feel, it is going to be catalog of choice in days to come.

Regards,

Ranjan

[former_member206388]

Hi Ranjan.

Just to add to the comments from Jason and Surya.

Master Catalog = Has all the products available in the master data which is exposed as a catalog.

Procurement Catalog = It is specific for suppliers or for a specific purpose(region/country based, criteria based etc).

Also the definition differs for each business scenario how the master data is exposed or stored.

Regards

Bala

[jason_boggans]

Hi Ranjan,

The Master Catalog, while a procurement catalog, is primarily designed to be the central repository for catalog data, the ability to create and publish subsequent procurement catalogs is to amongst other things, allow for restriction on available content without any specific need for views.

e.g. You have 3 Supplier Catalogs, lets say regional, EMEA / APJ and Americas, each has 1,000,000 items

So now, once mapped, your Master Catalog has 3,000,000 items. Publishing of this catalog would take quite some time as would definition of the views and associated rules to restrict data to individual user groups.

Now establish Procurement catalogs x 3, with same convention, i.e. Americas/APJ/EMEA and map the content from the master to these catalogs. Now publishing takes less time as you have 2/3 less content and perhaps there is not as much need for views.

Regards,

Jason