In plant maintenance, is catalog a master data?

[arifsappm]

In plant maintenance, is catalog a master data? Because when we create a catalog a transport request.

For any of the master data created in plant maintenance, we don't get any transport request.

Only for catalog if we create, then we get transport request.

Why?

[arifsappm]

Hi Terence, 

If TR is created then it is a configuration data, not a master data na?

I'm confused.

Because the master data has to be uploaded in each system every time. Either it may be development, quality or production.

But the configuration data has to be moved through TR from dev-qa-prod. And so is the case of catalog moved like that.

Am I right?

If yes, then how can catalog be a master data

[MTerence · Accepted solution]

Hi,

Yes, Catalog is Master Data. Check this OSS message

3195878 - TA QS41/QS51 don't ask for Transport Request after changes

Regards

Terence

[arifsappm · Accepted solution]

Hi,

Thanks for your reply.

But i want to say whenever we create a catalog we get transport request to save. Wether it may be created in qs41 or qs21

If the transport request is created, then that means it has to be moved from one system to other system. That is from development to quality and quality to production.

[MTerence · Accepted solution]

Hi, If TR created, then you can transport from one system to another. But in case of Long Text, that you need to follow a certain step mentioned in the OSS note.

[arifsappm · Accepted solution]

Hi Terence, If TR is created then it is a configuration data, not a master data na? I'm confused. Because the master data has to be uploaded in each system every time. Either it may be development, quality or production. But the configuration data has to be moved through TR from dev-qa-prod. And so is the case of catalog moved like that. Am I right? If yes, then how can catalog be a master data

[MTerence · Accepted solution]

Hi, In older version Catalogs to be created as a Master Data in each client. SAP has provided an option this can be moved as a Transport also, which will reduce the effort you take to do the activity in each client. This depends on your system setting in SE54, if you need TR or dont need TR, its upto you to decide. Whether its Master Data or Configuration Data, this is also depends on how you take it forward and present to client. In my exp, i have both, one client this was maintained as Master Data, so they create it in each system but in another, they want to see as configuration data, so no one is allowed to change. Any change to be approved and moved to ER1

[johnstog]

It is a business decision. If you remove the transport option your systems will not be aligned. I have worked with both and I believe if you need to react to incorrect or new catalogue codes in your Production system then treat the catalogue codes as normal master data like Functional Locations or Equipment.