SAP Client Creation (SCC4) & Logical system (BD54) in SAP
SAP Client Creation (SCC4) & Logical system (BD54) in SAP
Create Logical system for new client
SAP Client Creation (SCC4) & Logical system (BD54) in SAP
ii. No changes to repository and cross client
iii. Protection level -1 – No overwriting
iv. eCATT & CATT Not Allowed
Make login/no_automatic_user_sapstar=0
• Login to the SAP system using client 000 or 001
• Hit the transaction code ‘RZ10′
• Click Utilities and click import profiles
• Click back (F3)
• Place the cursor at profile and click f4
• Double click on Default profile
• Select the Extended maintenance and click change
• Click Parameter (Create F5)
• Place the cursor at parameter name and click F4
• Click a small triangle shape which is available on top of the
box
• Type *login* and hit enter
• Double click on ‘login/no_automatic_user_sapstar’
parameter
• Type the parameter value as ’0′
• Click ‘Copy’ Tab and click back (F3)
• Click ‘Copy’ Tab again to transfer The changed profile
• Click Back (F3)
• Click Save, Click back and Click Yes to activate the profile
• Log out from the SAP system
• Stop the SAP System
• Start the SAP System
• Now try to login as sap* and Password as ‘pass’
• Now you should be able to login to newly created client
using virtual user temporarily before doing client copy.
FAQ |
Answer |
1. What is the purpose of creating a client in SAP
using SCC4? |
A client in SAP acts as a separate, logical partition
within the same SAP system. Using transaction SCC4, administrators create and
configure clients for different business or technical purposes—such as
development, testing, or training—without interfering with each other. |
2. What are the key settings to consider when creating
a client in SCC4? |
When creating a client, you need to define parameters like
client number, name, logical system assignment, role (e.g., test,
production), and whether changes are allowed (customizing, repository). These
settings determine how the client behaves and what level of changes are
permitted. |
3. What is a logical system in SAP, and why is it
defined in BD54? |
A logical system represents a unique identifier for a
client within an SAP landscape, used for data exchange between systems. BD54
is the transaction where you define logical systems before assigning them to
clients in SCC4. It's essential for scenarios involving ALE, IDoc, or
cross-system communication. |
4. How do you assign a logical system to a client in
SAP? |
After defining a logical system in BD54, go to SCC4 and
select the client you want to assign it to. In the client settings, you'll
find a field to assign the logical system. This assignment is crucial for
proper data integration and consistency across systems. |
5. Can a logical system be reused across multiple
clients? |
No, a logical system should be unique to each client.
Reusing the same logical system across clients can cause data
inconsistencies, especially in distributed systems or during client copy
processes. Always create a unique logical system name for each client. |
Read are 5 interview questions focused on SAP
Client Creation (SCC4) and Logical System (BD54) that assess both
conceptual understanding and hands-on experience:
Interview Question |
Purpose of the Question |
1. Can you explain the steps involved in creating a new
client in SAP using transaction SCC4? |
Tests understanding of the process and familiarity with
SCC4 settings (client role, changes allowed, logical system assignment,
etc.). |
2. What is the role of a logical system in SAP, and how
is it created and assigned to a client? |
Evaluates knowledge of BD54 and the purpose of logical
systems in cross-client or cross-system communication. |
3. Why is it important to ensure a unique logical
system for each client, and what problems can arise if this is not
maintained? |
Assesses awareness of data consistency and potential
integration issues in distributed environments. |
4. How would you handle a scenario where you need to
copy data from one client to another within the same system? |
Checks practical experience with client copies, and the
understanding of prerequisites like logical system uniqueness. |
5. What is the impact of changing a logical system
after client configuration? Can it be done safely in a production
environment? |
Explores understanding of real-world risks and best
practices in system configuration and data integrity. |
0 Comments