SAP Client

 The SAP Client is a fundamental organizational unit within an SAP system. It acts as a self-contained, independent business entity with its own master data, transactional data, and user master records. All customizing settings that are not client-independent (i.e., settings that apply globally to the system, like ABAP programs) are also stored at the client level.

Transaction SCC4 (Client Maintenance) is the central point in SAP Basis for creating, copying, deleting, and managing client-specific settings.

---

Understanding the SAP Client Concept

• Logical vs. Physical Separation: Clients provide logical separation of data and processes within a single physical SAP instance. This allows multiple, distinct business units or environments (e.g., Development, Quality Assurance, Training, Production) to coexist on the same SAP system.
• Data Isolation: Data created in one client (e.g., Client 100) is completely isolated from data in another client (e.g., Client 200). A user logging into Client 100 cannot access data in Client 200.
• Customizing: Most customizing settings (e.g., company codes, sales organizations, purchasing groups) are client-specific.
• User Masters: User IDs and their assigned roles/authorizations are client-specific. A user JDOE in Client 100 is distinct from JDOE in Client 200.
• Client 000, 001, 066:
  • Client 000 (Original Client): Delivered by SAP. Used for system upgrades, client copies (as a source for standard customizing), and initial configuration. It contains basic customizing and master data. Should not be used for daily operations.
  • Client 001 (Default Client): Also delivered by SAP. Contains a copy of Client 000 customizing. Can be used as a source for client copies or as a customizing client. Should not be used for daily operations (user logging in).
  • Client 066 (SAP EarlyWatch Client): Used by SAP for remote support and performance analysis. Should be secured and not used for regular activities.

---

Client Creation (SCC4) - Step-by-Step

Creating a new client in SCC4 involves defining its properties. The actual data population is done through a Client Copy (transaction SCCL, SCC9, or by importing a transport).

Steps to Create a New Client Entry in SCC4:

1. Execute SCC4: Log in to an existing client (e.g., client 000 or a client with sufficient authorizations like SAP_ALL or S_TCODE for SCC4, S_CTS_ADM for transport management).

2. Display Mode First: SCC4 usually opens in display mode. Click on the "Display <-> Change" button (pencil icon) to switch to change mode. You might be prompted for a modifiable transport request if you are in a non-production system.

3. New Entries: Click on the "New Entries" button.

4. Enter Client Details:

   • Client: A three-digit numeric identifier (e.g., 300, 400). Choose a number not already in use.
   • City: Geographical location (e.g., Thane).
   • Logical System: CRITICAL! Enter a unique logical system name (e.g., PRDCLNT300, DEVCLNT400). This links the client to specific configurations in integration scenarios (ALE, RFC, Workflow). It must be unique across all connected SAP systems.
   • Cur. (Currency): The default currency for the client (e.g., INR, USD).
   • Name: A descriptive name for the client (e.g., Production Client - India, Development for Project X).
   • Valid From / To: Date range for the client's validity (usually left as default).
   • Client Role:
     • Production: For live business operations.
     • Customizing: For making configuration changes.
     • Test: For functional and integration testing.
     • Development: For ABAP development and initial customizing.
     • Training: For user training.
     • Sandbox: For ad-hoc testing and exploration.
     • Consolidation: Used in transport routes.
     • Recommendation: Set this accurately as it influences default settings for change options.

5. Client-Specific Settings (Crucial!): This section defines how changes are allowed within this client.

   • Changes and Transports for Client-Specific Objects:
     • No changes allowed: Most restrictive. No customizing or repository changes. Ideal for Production clients.
     • Changes without automatic recording: Changes are allowed but not automatically recorded in transport requests. Use with extreme caution (e.g., for very specific sandbox testing, but generally avoid in quality/production).
     • Changes with automatic recording: (Default for customizing/development clients). All changes are recorded in transport requests. Standard for Development and Customizing clients.
     • No changes to Repository and cross-client Customizing objects: Allows client-specific changes but prevents changes to global objects. Good for Test clients where only client-specific data changes are expected.
   • Changes to Repository and Cross-Client Customizing Objects:
     • No changes to Repository and cross-client Customizing objects: (Default for Production/Test). Prevents changes to dictionary objects, programs, and global customizing (e.g., RFC destinations, logical systems).
     • Changes to Repository and cross-client Customizing objects: (Default for Development/Customizing). Allows changes to dictionary objects, programs, and global customizing. This should only be allowed in designated development/customizing clients.
   • Protection: Client Copy:
     • Protection from overwriting by client copy: Prevents this client from being overwritten by a client copy. Important for critical clients (e.g., Production).
     • Protection from being overwritten by client copy if target client is not empty: A less strict protection.
     • No protection: Allows overwriting.
   • CATT and eCATT Restrictions: Define restrictions for test script execution (usually left as default for new clients unless specific requirements exist).
   • Restriction when starting ABAP Workbench: Typically set to 1 (No restriction).

6. Save: Click the "Save" button.

7. Transport Request: If you are in a modifiable system, the changes to SCC4 are cross-client and will be recorded in a transport request. Assign it to an appropriate transport request.

---

Critical Configuration Considerations (SCC4)

1. Logical System Name (LS):

   • Uniqueness: The Logical System name MUST be unique across your entire SAP landscape and any connected non-SAP systems. This is fundamental for ALE, Workflow, and other integration scenarios.
   • Creation (BD54): The Logical System name is defined in transaction BD54 first, then assigned to the client in SCC4. If BD54 is not done, you cannot assign it in SCC4.
   • Naming Convention: Establish a clear naming convention (e.g., <SID>CLNT<ClientNo>).

2. Client Role:

   • While not strictly enforced, the client role gives a clear indication of the client's purpose and influences default settings. Setting it correctly is good practice.

3. "Changes and Transports for Client-Specific Objects" & "Changes to Repository and Cross-Client Customizing Objects":

   • Security and Stability: This is arguably the most critical section. Incorrect settings here can compromise the stability and integrity of your system.
   • Production Clients: Should always be set to "No changes allowed" for client-specific objects and "No changes to Repository and cross-client Customizing objects." This prevents accidental or unauthorized changes in the live system.
   • Development Clients: Should allow "Changes with automatic recording" for both client-specific and cross-client/repository objects.
   • Quality/Test Clients: Often set to "No changes to Repository and cross-client Customizing objects" and "Changes with automatic recording" for client-specific objects. This allows testing of customizing changes via transport imports but prevents direct changes to global objects or repository.
   • Sandbox/Training Clients: May have "Changes without automatic recording" if changes are ephemeral and not to be transported, but this is generally discouraged for any client that might later be copied or used for reference.

4. Protection: Client Copy:

   • Overwriting Prevention: For critical clients (especially Production), set "Protection from overwriting by client copy." This prevents accidental deletion of a production client's data through a client copy operation.

---

Common Issues and Troubleshooting Steps (SCC4)

1. Issue: Cannot save new client entry in SCC4.

   • Reason: SCC4 is in display mode, insufficient authorizations, or Logical System not defined.
   • Troubleshoot:
     • Change Mode: Click the "Display <-> Change" button.
     • Authorizations: Ensure your user has SAP_ALL or relevant authorization objects (S_TCODE for SCC4, S_CLIENT with activity 01 (create) or 02 (change)).
     • Logical System: If the issue is during saving after entering the Logical System, ensure the Logical System is already defined in transaction BD54. You must create it there first.

2. Issue: Logical System dropdown is empty or cannot find desired Logical System.

   • Reason: The Logical System has not been created in transaction BD54.
   • Troubleshoot:
     • Go to transaction BD54.
     • Click "New Entries."
     • Enter the desired Logical System name (e.g., PRDCLNT300) and a descriptive text.
     • Save the entry.
     • Return to SCC4 and retry.

3. Issue: Error "Client XXX already exists" when trying to create.

   • Reason: The client number you chose is already in use.
   • Troubleshoot:
     • Choose a different, unused three-digit client number. You can see existing clients in the main SCC4 screen.

4. Issue: Cannot change client settings (e.g., "Changes and Transports for Client-Specific Objects").

   • Reason: System is locked for changes (e.g., client role is production and set to no changes, or SE06 is not modifiable for cross-client objects).
   • Troubleshoot:
     • SE06 (System Change Option): Ensure the "Global setting" for "Software Component" SAP_APPL (or relevant) is set to "Modifiable" and the "Namespace" is set to "Modifiable". This is a system-wide setting.
     • Authorizations: Ensure sufficient authorizations.
     • Client Role vs. Change Options: Be aware that certain client roles might default to stricter change options. You can still manually override them in SCC4 if SE06 allows.

5. Issue: Client created but no data (e.g., no users, no customizing).

   • Reason: Creating the client entry in SCC4 only defines the client's properties. It does NOT populate any data.
   • Solution: You must perform a Client Copy after creating the client in SCC4 to populate it with data (customizing, master data, user masters).
     • Transaction SCCL: For a local client copy (within the same system).
     • Transaction SCC9: For a remote client copy (from another system).
     • Transport of Copies: For copying specific customizing or master data via transport requests.
     • Data Migration Tools: For new implementations, data is migrated using tools like LSMW, LTMC, or external ETL tools.

---

Post-Client Creation Activities (Essential!)

After creating the client entry in SCC4, these steps are crucial:

1. Perform a Client Copy (SCCL/SCC9): Copy data from a suitable source client (e.g., Client 000 or an existing customizing client) using a relevant copy profile (e.g., SAP_ALL for a full copy, SAP_CUST for customizing only).
2. Create SAP and DDIC users:* After a client copy, the standard SAP users SAP* and DDIC will exist with their default passwords (if copied). You can log in using these to create your initial administration users.
3. Create Initial Admin User: Create a new dialog user with SAP_ALL profile (or specific Basis roles) for daily administration. Change SAP* and DDIC default passwords and restrict their use.
4. Configure Logical System (BD54) and Assign in SCC4: Already mentioned, but re-emphasizing its importance.
5. Set Up Client-Specific Transport Layer/Route: In STMS, ensure the new client is part of the correct transport route (e.g., development clients are sources for transport, QA/Production clients are targets).
6. Client-Specific Number Ranges: Review and adjust number ranges for various business objects (e.g., sales orders, purchase orders) in the new client if necessary.
7. SGEN (Load ABAP Programs): After a client copy, it's often recommended to run SGEN to regenerate ABAP loads for better performance, especially if the target client's kernel/database is different.
8. Security Audit (SM20/SM19): Ensure audit logging is configured for the new client as per security policies.
9. Time Zone: Verify the client's time zone settings (STZBC).

Proper client creation and management are foundational to a well-structured and secure SAP landscape.