QS41 in Version ECC6.0

[Former Member]

Dear all

After upgrade from R3 4.6 to ECC6.0, we can't directly create/change catalog in productive system using QS41. After click 'create/change' , the system always pop up the message 'Client xxx has status 'not modifiable'. Experts, cloud you pls tell me which basis customizng/package miss or it is impossible to create/change catalog directly in productive system under vesion ECC6.0 but transported from customzing system. By the way, we can create/change catalog and generate one request number in customing system .

Many thanks!

Edited by: pinknaive on Feb 24, 2010 8:56 AM

[Former Member]

We had our BASIS folks help us....

How to make updates to Quality Catalogs not require a transport.

1. In IMG, find the configuration line for the object (EDIT CATALOGS) and just u201Chighlightu201D the object: (like Quality Management> Quality Planning> Basic Data> Catalog> "EDIT CATALOGS"

2. From the EDIT menu, select u201CDisplay IMG Activityu201D.

3. Select the Maint. Objects Tab, then double-click on one of the u201Ccustomizing objectsu201D (in this case V_QPGR_CL).

4. On the resulting screen, make sure the u201Ccurrent settingsu201D check box is checked.

5. Do the same for the other customizing objects listed (in this case V_QPAM_CL).

Hope this helps.

Jackie SEals

[Former Member]

I found the note 376134 to solve this problem. anyway, thanks all of you!

[Former Member]

Hi.

This is because you do not have autharisation of SPRO.So better you take autharisation.for your use ID.& get midifibale custamizing client for you.. Then only you can create catlogs .

Regards

SANIL

[former_member42743]

SAP changed catalogs from master data to configuration data between 4.6b and 4.6c. The problem is due to the table attributes of your production tables used for catalogs. To make them editable in 6.0 you have to do a system modification.

Please look at OSS note 592418 for information on this. It describes the mods necessary.

Craig

[anand_rao3]

Well, I think you have to do your production client in modifiable status for this. But that would be business decision. Rather it is recommended that you should transport your defect codes, catalogues etc through requests.

Best Regards,

Anand Rao

[Former Member]

Hi,

It is giving the message because the user is not having authorization to SPRO.Ask for SPRO autho to basis.

Vishal Jonnalwar