Client Creation

Client Creation:
Execute SCC4 to create New Clients:
  1. Click on Change–>new Entries
  2. Specify the Client Number
  3. Specify the Description: TESTING
  4. Specify the Location: HYD
  5. Specify the Currency: INR
  6. Specify the Role: SAP Provides 6 Standard Client Roles
  7. CUSTOMIZING UNIT_TESTING SAND_BOX QUALITY_TESTING TRAINING PRODUCTION
  8. CUST    TEST    SAND   QTST    TRNG   PROD
These Clients are represented with Four Characters.
  • Specify the Client Specific Changes: The Changes are allowed at Client Level
  • Specify the Cross Client Changes: The Changes are allowed at Client Level
  • Specify the Repository Object Changes: The Changes are allowed at Client Level
  • Specify the Protection Level: 0, 1, and 2:
Client Specific Options:
Changes without Automatic recording:
  • The Changes are allowed in this client but not recorded for transportation it is set for SAND/TEST Client
Automatic Recording of Changes:
  • The Changes are allowed in this client and Recorded for further transportation.it is set for CUST Client and it is the only one client in the landscape setup with option.it is also referred as Golden Client, Master Client and Parent Client
No Changes are allowed:
  • No changes are allowed in this Client .it is set for PROD/QTST/PRD Client
Changes without Automatic recording and No Transportation:
  • Changes are allowed but not recorded and also not possible for Transportation.(it is set to SAND and TEST Clients)

Changes to repository  and Cross Clients are allowed
No Changes to Cross Client Objects
No Changes to repository Objects
No Changes to repository Objects and Cross Clients are allowed

Protection Level:
These are used to set the Protection Levels for Client
  • 0: The client copy is allowed and client overwriting is also allowed
  • 1: Client Copy allowed no Overwriting
  • 2: Client Copy not allowed and No overwriting

Comments

Post a Comment

Popular posts from this blog

SPOOL WORK PROCESS

Spool Process: It is the Only Process that is used to output the documents to a Printer, fax, email etc.. Spool Work Processes are created by using parameter risp/wp_no_spo=1 it is possible to configure more than one spool work process based on available resources. Spool Process Work Flow: User Submits the request to print a Document. The Dialog Process handles the request and print directly or schedules to print in the background.The Print requests are stored in the TemSe(Temporary Sequential Files) Temporary Sequential Files are stored either at File System or at database Level which is defined by parameter rspo/store_location. rspo/store_location=”G” or ‘DB’ G means global directory stores the TEMSE in /usr/sap/SID/SYS/global db mean the Tables TST01 and TST03.(TST01 Contains Print Attributes and TST03 Contains the Spool Data to be Printed) Due to Spool in DB the DB Size Increases, as a Result, the backup time increases and Tapes may not fit with the data for S...
Read more

ENQUEUE WORK PROCESS

It is used to lock and unlock the Objects during an update.These locks are displayed in SM12 and Held for longer hours until the transaction is committed or rollback.These locks are issued from a lock table which resides in the main memory of the instance where enqueue process is created/located. Enque Processes are configured by parameter rdisp/wp_no_enq=1. Generally One Enque Process for instance is sufficient,more then one is required in a massive update system. The Lock table size on the memory ranges between 4mb to 100 MB(200 MB in the Net weaver 7.3 Systems ) It is defined by parameter enque/table_size=4 to 200 MB. For 4mb of enqueue table size, the Number of lock/owners/objects/arguments can be restricted up to 3715. Enqueue Flow: User submits the Request for an Update. The Dialog or Background Process Handles the Request Dia or BTC Processes communicates with Enqueue Process and obtains a lock on the record so that no other user has to write access to that r...
Read more

DIALOG PROCESS

Dialog Process: It is the only process that is used to communicate with end users Interactively using Classic GUI or Through RFC or through Http Protocol. The Average Response Time for each dialog step is 600 ms.it is displayed through ST03n Each Process can execute up to a maximum runtime of 600 seconds.if any process goes beyond this time an additional time of 60 seconds is given and the process is timed out.(ST22)(it is not mandatory to allocate additional 60 seconds Each Process Serves 5-10 users.(Calculated based on ST07) Each Process Requires 75mb to 300 mb Memory Each Process can Handle the requests that are initiated for background, spool & update and update them in temporary tables. Dialog Process is not restricted to a User and Users are not restricted to a process which is referred as process multiplexing Parameters to configure dialog processes is rdisp/wp_no_dia There should be at least minimum two dialog processes and maximum up to 100 processes. The ...
Read more