Client creation strategy

[Former Member]

Hi all,

We have a 3 system ecc 6.0 landscape . In dev we have client 100 & 150 ( testing ) .

I have created 100 in quality & intend to create client 100 in PRD also .

Along with ECC we also MI & BI in our landscape , I intend create client 100 in all these systems .

But some of my team mates suggest that this is not a good strategy . Instead they suggest creating client 100 , 200 & 300 in Dev , Qas & PRD respectively .

Which strategy is better & why ? should i delete the already created client 100 in ECC quality system ?

[rohan_hardikar2]

Even if you have same client in whole landscape, it is not a harm. Their is something called "logical systems" by which the system will differentiate between DEV, QAS and PRD.

[Former Member]

The only one advantage (which i believe) in having different client number is that users can distinguish the systems/client usage easily. While we have multiple logins from dev, qas and prd in our desktop, it will be easy to get them picked from one another.

One of the old strategy for client number is:

DEV

-

---

100 - Development client

200 - Test client

300 - Sandbox client

QAS

-

---

400 - Quality client

500 - IDES/ training client

PRD

-

---

900 - Production client

[Former Member]

Hi,

As long as the systems are different, maintaining client 100 for DEV, QA and PROD systems is OK.

Rgds,

Soujanya

[Former Member]

HI ,

Client number will not harm your landscape... system will be identified by SID and logical name.

You can have same client no in qas and prd.

With Regards

CSK

[sunny_pahuja2]

Hi,

I don't see any harm having same client numbers in different systems. In my landscape, all production system has client 100 and it is also present in quality and development system.

Do you ask your friend why it is not good strategy ?

Thanks

Sunny