Difference between Golden Client and Master Client

Dear,
What is the Difference between Golden Client and Master Client?
Thanx & Regards,
Mohammad Nabi,
[email protected]

Golden Client is similar or is the the same as Development Client, which should not be used for testing.
Master Client ???
Note on SAP Landscape:
Landscape is like a server system or like a layout of the servers or some may even call it the architecture of the server’s viz. SAP is divided into three different landscape DEV, QAS and PROD.
-  DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test.
-  QAS may again have multiple clients for ex: 300- Integration Test, 700 to 710 Training.
-  PROD may have something like a 200 Production.
These names and numbers are the implementer's discreet on how they want it or they have been using in their previous implementations or how is the client's business scenario. 
Now whatever you do in the Sandbox doesn't affect the other servers or clients. Whenever you think you are satisfied with your configuration and you think you can use it moving forward, you RE-DO it in the golden client (remember, this is a very neat and clean client and you cannot use it for rough usage). As you re-do everything that you had thought was important and usable, you get a transport request pop up upon saving every time. You save it under a transport request and give your description to it. Thus the configuration is transported to the Unit Test client (180 in this example). 
You don't run any transaction or even use the SAP Easy Access screen on the 100 (golden) client. This is a configuration only client. Now upon a successful transport by the Basis guy, you have all the configuration in the Testing client, just as it is in the Golden client. The configuration remains in sync between these two clients. 
But in the Testing client you can not even access SPRO  (Display IMG) screen. It's a transaction only client where you perform the unit test. Upon a satisfactory unit test, you move the good configuration to the next SERVER (DEV). The incorrect or unsatisfactory configuration is corrected in Golden (may again as well be practised in the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular config is satisfactory. 
The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference client for all the good, complete and final configuration that is being used in the implementation.
In summary:
Landscape : is the arrangement for the servers
IDES : is purely for education purpose and is NOT INCLUDED in the landscape.
DEVELOPMENT ---> QUALITY -
> PRODUCTION
DEVELOPMENT : is where the the consultants do the customization as per the company's requirement.
QUALITY : is where the core team members and other members test the customization.
PRODUCTION : is where the live data of the company is recorded.
A request will flow from Dev->Qual->Prod and not backwards.
1. Sandbox server: In the initial stages of any implementation project, You are given a sandbox server where you do all the configuration/customization as per the companies business process.
2. Development Server: - Once the BBP gets signed off, the configuration is done is development server and saved in workbench requests, to be transported to Production server.
3. Production Server: This is the last/ most refined client where the user will work after project GO LIVE. Any changes/ new development is done is development client and the request is transported to production.
These three are landscape of any Company. They organized their office in these three way. Developer develops the program in Development server and then transport it to test server. In testing server tester check/test the program and then transport it to Production Server. Later it will deploy to client from production server.
Presentaion Server- Where SAP GUI has.
Application Server - Where SAP Installed.
Database Server - Where Database installed.
Regards,
Rajesh Banka
Reward points if helpful

Similar Messages

  • Difference between system copy and Remote Client copy?

    Hi,
    Can any body suggest me , What are the major difference between System copy and Remote Client Copy.
    As per my knowledge , Both are different
    1.In system copy  entire data recovered mean copy from Source to target
    2.In Remote client copy All  Client data can't me import if you choose SAP_ALL profile also
          I hope Transaction data and user data can't copied
    Anybody share this Question and Give me some idea about this
    If anybody  give brief explanation that is very gratefull.
    regards,
    Balaram

    Hi,
    System copy will replicate all database from source to target system.
    In remote copy only client in which you are performing the copy will get refresh. Also, remote client copy will be done between systems on same patch level. with SAP_ALL profile you can bring all data in target system including your transactional data.
    Thanks
    Sunny

  • Difference between Body pages and Master Pages in Adobe forms?

    Hi SAP Gurus,
    Please can any one tell me the difference between the Body pages and Master Pages in Adobe Forms?
    In what scenarios we use Body pages and Master pages?
    And also please tell me what is Boiler plates? When these used?
    Thanks and Regards
    Abinava Siri..

    Hi,
    Master Pages:
    Does not included in the content area
    Master page we will design logo,company address and header information
    Here we can desing footer information
    whatever you desing in the master page it will show for all the body pages
    Body pages:
    Included in the content area
    Where we can design table data, it should repeat for line times.
    Regards
    Ramakrishna Pathi

  • Defferece between cost centre and Master Cost Centre

    Can any body explain defferece between cost centre and Master Cost Centre.
    Appreciate your help.
    Kavitha

    Hi kavitha
                     I dont think there is difference between Cost centre and master Cost Centre.
    It may be Possible that under Cost Centre Hirarchy One Cost Centre is at Top node and other is Child of that Cost Centre.
    Thank YOu.
    Thank YOU.

  • Difference between native client and workstation client.

    hi,
    I am confused with the difference between native client and workstation client.In
    some docs,it is said that native client is one which run on the same system as
    the server,in other it is said running on other machine in the same domain.So
    what about workstation client?So can anyone please helpme out in knowing this
    difference?

    subhash wrote:
    hi,
    I am confused with the difference between native client and workstation client.In
    some docs,it is said that native client is one which run on the same system as
    the server,in other it is said running on other machine in the same domain.So
    what about workstation client?So can anyone please helpme out in knowing this
    difference?The simple answer is that /WS clients are compiled with the -w option.
    The complicated answer has to do with how the client connects to Tuxedo during the
    tpinit(), and all subsequent traffic. A Tuxedo Domain (instance) has a Bulletin
    Board, which is a chunk of shared memory with all kinds of information about Servers
    and Clients. A Native Client, since it is running on the same machine that the
    Bulletin Board exists on, can directly access the shared memory. However, /WS client
    (also called a remote client) cannot access this shared memory. Instead, we have the
    WSL server to make connections with, and then WSH processes that access the Bulletin
    Board on behalf of the remote client.
    So Native Clients run on the same machine as the Servers and where the Bulletin Board
    is located, and have direct access to shared memory and other IPCs. Workstation
    Clients/WS Client/Remote Clients (all the same thing) cannot access IPCs and have the
    WSH do it on their behalf.
    In NT, the Tuxedo IPC Service mimics Unix IPCs, and so all the above is still true.
    Brian Douglass
    Transaction Processing Solutions, Inc.
    8555 W. Sahara
    Suite 112
    Las Vegas, NV 89117
    Voice: 702-254-5485
    Fax: 702-254-9449
    e-mail: [email protected]
    [briand.vcf]

  • Difference between system refresh and client refresh

    Hi all,
         I have one dout what is the difference between system refresh and client refresh,kindly tell me the answer?
    BR
    krishnamurthy.

    Hi,
    Client is part of a system.
    Client copy :Can happen within a single system(local client copy)  or to other system (i.e b/w systems) .
    Here we have some profiles to extract the data depending on the need.
    System Copy: We are copying the entire system to other system.we get the entire systems data (DB) .
    In both the cases we have to make sure that they are on same application component and are on same patch level.
    Thanks!!
    Edited by: Vani n on Jun 27, 2008 2:45 PM

  • Diff between Thin client and Rich client

    Hi Everyone,
              Can someone give me a clear picture of the what is the diff between Thin client and Rich client.
    Thanks,
    Krishna

    Hi,
    thick client (rich client) has/stores all the data inside itself
    so it can do application processing without the server with data
    thin client uses resources from host computer (from server)
    and wihtout that you are not able to work with that kind of client
    does that answer your question ?
    Regards,
    michal

  • Difference between Business Partner and Customer Master repository

    What is the difference between Business Partner and Customer Master repository ?
    Is the Business Partner repository to be used in case CRM is also in landscape ? or Customer master repository is good enough ?
    Sandesh

    Hi,
    If the landscape has both CRM and SAP ECC a business partner repository model should be good.
    If it has ECC alone.a Customer Repository is needed.
    But when there are many legacy systems which also contains master data fields, the standard business repository provided by SAP wont provide a good solution as it wont cover the legacy master fields..In this case its better to go for a customized repository and you can use the standard repository as a reference.
    Thanks

  • Network bandwidth requirement between MDM server and MDM Clients

    The MDM Sizing document for 5.5 states that  'a network connection between MDM Servers and MDM clients should be at least 100 Mbps'. Is this true? This would preclude MDM being offered as a hosted service. I'm interested in MDM Catalogue for SRM, so the catalogue content managers would need the import and data manager clients.

    One factor I noticed, in our project...
    I would recommend a 4 GB RAM for someone who is working with Import Manager.
    As far as the Network connection goes, I am not sure what the requirements are.
    We have faced several issues when the end user's laptop are less than 2 GB.
    If someone is working with Image Manager, then I would recommend 4GB.
    For bulk imports, I would use Import Server.

  • Difference between system status and user status.

    Can someone explain to me the difference between system status and user status in details

    Hi,
    As you mentioned there are 2 status can be maintained for documents like Equipment Master, Notification, Maintenance Order & other important business documents.
    In case, client feels that system status is not enough to capture the details of the object, then user status can be used.
    System statuses will be updated automatically based on business transactions which will be done on SAP.
    For example, once the equipment is created, System status would CRTD (Created). If you install the same to some superior equipment or FL, then status would be INST (Installed).
    If you keeping that equipment in Spare, then for that, you have to maintain separate User Status like AVLB (Available in Stock / Spare) so that through IH08, by using User status, you can the report which is available as spare.
    These user status as per the name, should be updated by the user manually.
    Regards,
    Maheswaran.

  • Exact difference between System status and the user status

    Hi,
    Please tell me the exact difference between System status and the user status .
    how we customize the both in the system
    Thanks & Regards
    Prajith P
    Moderation: Locked. Please, try to find an answer first. See rules of engagement
    Edited by: Joaquin Fornas on Feb 23, 2012 11:14 AM

    Hi,
    As you mentioned there are 2 status can be maintained for documents like Equipment Master, Notification, Maintenance Order & other important business documents.
    In case, client feels that system status is not enough to capture the details of the object, then user status can be used.
    System statuses will be updated automatically based on business transactions which will be done on SAP.
    For example, once the equipment is created, System status would CRTD (Created). If you install the same to some superior equipment or FL, then status would be INST (Installed).
    If you keeping that equipment in Spare, then for that, you have to maintain separate User Status like AVLB (Available in Stock / Spare) so that through IH08, by using User status, you can the report which is available as spare.
    These user status as per the name, should be updated by the user manually.
    Regards,
    Maheswaran.

  • Wat is the exact differences between clustered table and pooled table

    hi,
       can you tell me ravi...wat is the exact differences between clustered table and pooled table
    with regards//
    anilreddyg

    Hi Anil Reddy
    Pooled Tables, Table Pools, Cluster Tables, and Table Clusters
    These types of tables are not transparent in the sense that they are not legible or manageable directly using the underlying database system tools. They are managed from within the R/3 environment from the ABAP dictionary and also at runtime when they are loaded into application memory.Pool and cluster tables are logical tables. Physically, these logical tables are arranged as records of transparent tables. The pool and cluster tables are grouped together in other tables, which are of the transparent type. The tables that group together pool tables are known as table pools, or just pools; similarly, table clusters, or just
    clusters, are the tables which group cluster tables.Not all operations that can be performed over transparent tables can be executed over pool or cluster tables.
    For instance, you can manage these tables using Open SQL calls from ABAP, but not Native SQL.These tables are meant to be buffered and loaded in memory, because they are commonly used for storing internal control information and other types of data with no external (business) relevance. SAP recommends that tables of pool or cluster type be used exclusively for control information such as
    program parameters, documentation, and so on. Transaction and application data should be stored in transparent tables.
    Table Pools
    From the point of view of the underlying DBMS as from the point of view of the ABAP dictionary, a table pool is a transparent table containing a group of pooled tables which, when created, were assigned to this table pool.
    Field Type Description
    TABNAME CHAR(10) Table name
    VARKEY CHAR(n) Maximum key length n =< 110
    DATALN INT2(5) Length of the VARDATA record returned
    VARDATA RAW(m) Maximum length of the data varies according to DBMS
    Table Clusters
    Similarly to pooled tables, cluster tables are logical tables which, when created, are assigned to a table cluster. Therefore, a table cluster, or just cluster, groups together several tables of type clusters.Several logical rows from different cluster tables are brought together in a single physical record. The records
    from the cluster tables assigned to a cluster are thus stored in a single common table in the database.A cluster contains a transparent cluster key which must be located at the start of the key of all logical cluster tables to be included in the cluster. As well, a cluster contains a long field (VARDATA), which contains the
    data of the cluster tables for this key. If the data does not fit into a field, continuation records are created.
    Field Type Description
    CLKEY1 CHAR(*) First key fields
    CLKEY2 CHAR(*) Second key field
    CLKEYN CHAR(*) nth key field
    PAGENO INT2(5) Number of the next page
    TIMESTMP CHAR(14) Time stamp
    PAGELG INT2(5) Length of the VARDATA record returned
    VARDATA RAW(*) Maximum length of the data section; varies according to database system
    Working with Tables
    The dictionary includes many functions for working with tables. There are five basic operations you can perform on tables: display, create, delete, modify, copy. Please do not confuse displaying a table with displaying the table entries (table contents). In order to display a table, it must previously exist; otherwise the system will display an error message in the status bar. For the following example, the table TABNA is used. To display this table, from the main dictionary screen, enter the table name in the Object name
    input field with the radio button selected next to Tables. Then, click on the Display button at the bottom of the screen, or press the F7 function key, or, alternatively,
    select Dictionary object Display from the menu.
    In this screen, you can see table information such as
    ¨ Table type, shown next to the name of the object. In the example, it is a transparent table.
    ¨ Short text description.
    ¨ Name of the user who made the last change, and the date of the change.
    ¨ Master language.
    ¨ Table status. On the screen, you can see this table is saved and active.
    ¨ Development class. For information on development classes, refer to Chap. 6.
    Delivery class, which sets the maintenance group for the table. It controls how tables will behave during client copy procedures, upgrades, and so forth.¨
    Tab. Maint. Allowed flag, which indicates whether you can generate a screen for maintaining table entries.
    ¨Then, on the lower part of the screen, you can see the table fields with all associated characteristics such as:
    ¨ Field name.
    ¨ Key indicator. When set, this field is the primary key, or part of it.
    ¨ Data element.
    ¨ Basic data type.
    ¨ Length.
    ¨ Check table.
    ¨ Short text, describing the field.
    Additional information about the table can be displayed by selecting the corresponding functions from the menu or directly from the application toolbar, such as keys, indexes, or technical settings
    Standard table:
    The key access to a standard table uses a sequential search. The time required for an access is linearly dependent on the number of entries in the internal table.
    You should usually access a standard table with index operations.
    Sorted table:
    The table is always stored internally sorted by its key. Key access to a sorted table can therefore use a binary search. If the key is not unique, the entry with the lowest index is accessed. The time required for an access is logarithmically dependent on the number of entries in the internal table.
    Index accesses to sorted tables are also allowed. You should usually access a sorted table using its key.
    Hash table:
    The table is internally managed with a hash procedure. All the entries must have a unique key. The time required for a key access is constant, that is it does not depend on the number of entries in the internal table.
    You cannot access a hash table with an index. Accesses must use generic key operations (SORT, LOOP, etc.).
    Index table:
    The table can be a standard table or a sorted table.
    Index access is allowed to such an index table. Index tables can be used to define the type of generic parameters of a FORM (subroutine) or a function module.
    Just have a look at these links:
    http://help.sap.com/saphelp_nw04/helpdata/en/90/8d7304b1af11d194f600a0c929b3c3/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/74/83015785d811d295a800a0c929b3c3/frameset.htm
    Regards
    Sreeni

  • What is difference between hostd, Vpxa and vpxd.

    what is difference between hostd, Vpxa and vpxd. whats there purpose in esx

    Hi....
    VPXD-It is Vcenter Server Service. If this service is stopped then we will not able to connect to Vcenter Server via Vsphere client.
    VPXA-It is the agent of Vcenter server. also known as mini vcenter server which is installed on the each esx server which is managed by Vcenter server. What are the management action we are performing on top of the vcenter server. (Like:- Increasing/Decreasing RAM & HDD, Making any type of changes in cluster,
    doing vmotion. This agent collects all information from the vcenter server and pass this information to the kernal of the esx server.
    HOSTD- This is the agent of ESX server, here VPXA pass the information to the HOSTD and hostd pass the information to ESX server.
    Hope this one give you clear explanation about the difference in between each of them.
    Vijay Bhardwaj

  • Difference between connection pooling and simple connection

    Anybody please tell me what is the Difference between connection pooling and simple connection and also where we define connection pooling and how.
    Thanks
    Please reply soon
    amitindia

    Creating and closing connection to the database is a relatively slow process. Equally connections use database resources so you can't just open as many as you want.
    A connection pool maintains a number of open connections throughout the lifetime of the application. Instead of opening and closing the connections your application just "borrows" them from the pool when they're needed.
    If the pool runs out of connections it will usually create new ones as needed until you reach some predefined upper limit.
    A good connection pool will also manage connections which have failed for any reason, and report code which fails to return connections to the pool (ie connection leaks).
    The number of connections created at startup is referred to as the "low water mark" and the maximum number that the pool will allow to be opened at any given time is the "high water mark". If no connections are available client code will generally block until one is released.
    If by "defined" you mean where can you get a working implementation then your database or application server vendor is likely to provide one. Also the Apache Jakarta Commons includes [url http://jakarta.apache.org/commons/dbcp/]an implementation which you can use with any JDBC driver.
    Dave.

  • Difference between unit testing and integration testing

    What is the difference between unit testing and integration testing in SAP? Is unit testing takes place in Dev client and integration testing takes place in QA system?
    Please clarify
    thanks

    Hello Krishen,
    unit testing means veryfiingsmall / the smallet pieces of software, while integration testing checks the overall functionality of applications. Within the AS ABAP the tool ECATT + manual tests is used for integration tests and the ABAP Unit language integration for unit testing.
    When, Who, Where tests are carried out is ultimately a personal decision. As unit tests are operate even under heavy development they are often the first choice for developers, but the unit tests can also serve for regression tests over a long period. Integration tests tend too be created and executed in later stages as they require often a certain majurity of the software under test.
    Beside the mentioned links you may check out ABAP Unit infos also in the Wiki.
    https://wiki.sdn.sap.com/wiki/display/HOME/ABAP+Unit
    Best Regards
      Klaus

Maybe you are looking for