Skip to Content
0
Former Member
Jun 06, 2009 at 11:41 AM

segregation factors and Single client issues

50 Views

Hi there,

we are group (3 Separate Companies) having a different characteristics, separate entities and special identification for each company.

I think in such case multiple client is suggested to segregat between the companies as best practice.

Justifecation

- 2 companies went live and at beginning of Jan 2010, 1 Company will go live and theThe implementer planning to stop the system for 3-4 days. As a consequence, all company will not be able to perform their daily duties.

- ABAP development: All specific requirements for the different comanies are hard coded into the program .

- Due to the use of a single client, features and configuration are applied to all companies. It is therefore not possible to apply specific requirements for the different companies.

- Object number range spread randomly to the different companies.

- Last OM alternative plan overriding the previous alternative plan that was activated.

- Others issues: Data maintenance, upgrade.

- We have one organization structure (one active plan) for all companies

- We create one compensation area

- We use same qualification and requirement catalogue for all companies

- One training catalogue

- We define one time sheet profile for all companies

- Same authorization master plan

- Pers. Development objects number ranges

- Documentations

We are interested in knowing if these are best practices and the consequences of using multi/Single client in SAP.

Thanks in advance 😊