ways to avoid cross-client problems between teams

[Former Member]

Hi. I'm a noob here. xD

There are two teams, one for implement HR and other for Logistics.

So, there are some shared (x-client) data, right?

So some customization can cause side-effects. How do you control this in your company?

Thank you.

[former_member182546 · Accepted solution]

Dear Leandro ,

        If this is the scenario , Kindly maintain clients separately for HR & Logistics. My customer also has separate clients for SD & ( MM,FI )

With Regards,

Sudhir S

[Former Member · Accepted solution]

And then, would I use ALE if I need some communication between them?

Would I be loosing integration doing this way?

[former_member182546 · Accepted solution]

Dear Leandro ,

        Yes you can use ALE . Actually we have basically the communications through two methods

1. ALE - for communications between two sap systems

2. EDI  - for communications between two ( sap  or SAP & non sap system )

So in our case you have to do the RFC configuration using the t code SM59. For this you can take the help of the BASIS person.

Please follow the below link will be helpful for you.

http://saptechnical.com/Tutorials/ALE/Guide/Index.htm

Please reward points if it is useful.

With Regards,

Sudhir S

[former_member182546]

Dear leandro,

Have individual transport requests for the customized objects separately.

With Regards ,

Sudhir S

[Former Member]

Thank you Sudhir.

But how the guy responsible for authorize the requests know that some customization can affect other system?

Suppose the HR is already in production and working fine. Then I will implement Logistics and make a change in a customization object that the HR also use. So it will be a problem, because HR would not be working correctly.