on 10-26-2006 2:40 PM
Hi,
I have one doubt, i´ve downloaded some best practices teaching how to configure middleware to synchronize business partners between ECC and CRM, and one of the steps is permit customizing on the client, but this client is not suppose to be customized.
After i setup the things it´s necessary it still allowing customization?
During the setup i´ve activated the following settings:
- Automatic recording of changes
- Changes to Repository and cross-client Customizing allowed
- eCATT and CATT allowed
Thanks,
Edu
Hi Edu,
The best practice guide talks about the dev. system where actually you need to do the customization and then transport it to QA & Prod.
So in transaction SCC4 you should have the following entries in QA & Prod:
1> No changes Allowed
2> No Changes to Repository and cross-client Customizing Objects
3> eCATT and CATT allowed
With this entries your system will be locked for the customizing.
<b>Reward points if my post helps!!</b>
Best regards,
Vikash.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Edu,
For the replication of customizing and master data objects it is not necessary to open your client for repository changes and cross-client customizing. the Best Practices guide C71 Connectivty specifies that the settings should be the way you describe. The intention here is that the customizing you would typically do in a development client is to be transported to a productive system (optionally via one or more test systems). This means that once you're done customizing, the settings can be changed again if required.
A productive client is typically closed for all customizing actions.
Hope this helps,
Kind regards,
KZ
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.