Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

sap clients?

Former Member
0 Likes
727

hi,

actually there are some multiple clients in the R/3 system,,wats the use?moreover in all business process there will b dev,qa,prd..wats the necessary for shifting frm dev to qa?as already the everything will b tested sidebyside by the functional guy etc?

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
624

Client signifies group of users with similar authorizations on data. To give an example, the developers and the functional consultants should have different authourizations on data and hence they have different clients to work on.

Coming to the need of having multiple systems, it is a regular practice to maintain the integrity of data to have different systems. Pr4oduction data is the data of the real business scenarios. Now the point is why should we have QA. Well the QA system by convention has the near replica of the production data and if the testing is done in the server that have the closest replica of the production data, the programs written will have least chance of failing in production.

Hope this clarifies

Naveen

hi,

actually there are some multiple clients in the R/3 system,,wats the use?moreover in all business process there will b dev,qa,prd..wats the necessary for shifting frm dev to qa?as already the everything will b tested sidebyside by the functional guy etc?

4 REPLIES 4
Read only

RichHeilman
Developer Advocate
Developer Advocate
0 Likes
624

In some landscapes, the DEV instance will have less or hardly any data, the actual testing is done in QA, which is usually a copy of PRD done on a regularly basis, maybe quarterly. This is the reason for a QA system.

In my case, the DEV and QA systems are one in the same, we do our development and all testing in one system. When it is ready, then we move to PRD.

Regards,

RIch Heilman

Read only

abdul_hakim
Active Contributor
0 Likes
624

Hi

With Client Concepts you can maintain several separate enterprise in one system..

Cheers,

Hakim

Mark all useful answers..

Read only

Former Member
0 Likes
625

Client signifies group of users with similar authorizations on data. To give an example, the developers and the functional consultants should have different authourizations on data and hence they have different clients to work on.

Coming to the need of having multiple systems, it is a regular practice to maintain the integrity of data to have different systems. Pr4oduction data is the data of the real business scenarios. Now the point is why should we have QA. Well the QA system by convention has the near replica of the production data and if the testing is done in the server that have the closest replica of the production data, the programs written will have least chance of failing in production.

Hope this clarifies

Naveen

Read only

0 Likes
624

the previous answer helped me the concept of the process .as everything is framed in dev,how they ll move all the developd 1 to QA?eg:in case of security guy,he ll transport the role created in dev to qa.similarly how it wrks for other consultants like pogrammer,functional..