2007 Mar 13 11:29 PM
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?
2007 Mar 14 1:48 AM
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?
2007 Mar 13 11:37 PM
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
2007 Mar 14 1:19 AM
Hi
With Client Concepts you can maintain several separate enterprise in one system..
Cheers,
Hakim
Mark all useful answers..
2007 Mar 14 1:48 AM
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
2007 Mar 14 2:58 PM
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..