What is the main difference between client setting (scc4) and system change option (se06)?

Say, I close the client setting from scc4 (for both client dep. and indep. objects). Why do we still need worry about system change option (se06) ?

Or maybe se06 is only useful when the client is open ?
 

SCC4 used for to define the client and SE06 used for processing after installation for CTO (system landscape)

What I meant was se06 and then click system change option button, System Change Option provides granularity on what Repository and cross-client customizing objects can be modified. This is more of a global setting (regardless of the client) and is only for client-independent objects. In here, Repository objects are further subdivided into groups so you can set only which group can be changed.

SCC4 sets whether the changes allowed in System Change Option are applicable for a particular client, and also if changes for client-dependent objects are allowed.

The two actually work in tandem. If you allow changes in System Change Option, you still have to set a client in SCC4 where these changes can be actually made. But even if you "open" a client for client-independent changes, if the System Change Option doesn't allow it, you actually can not change client-independent objects.

If you close "all" clients in SCC4, you don't need to worry about System Change Option because closing all clients mean you don't plan to change anything in your system. It's when you need to change client-independent objects that you have to worry about System Change Option plus SCC4.

RFC Connection to another SAP Application Server

Need help on setting up a RFC connection to another SAP Server within the same LAN.

I've created the TCP/IP connection to the server in SM59. Need some helps on what other information need to be entered.
 

Using sm59 create a new RFC connection. The type should be 3 since it is a R/3 to R/3 connection.

Fill in the description, language and client number for the target R/3 system. Also fill in a user name and password valid in both source and target systems. It is best to use a user with a user type of communication so the remote connection is transparent.

After all that, hit enter. Your screen will show new sections which must now be filled in with either the IP address, host name, and system number of the target system. After you fill in this information, save. Then click the Test connection button. You should show statistics on how fast the connection was made. Go back and click the Remote logon button. If you entered a user with communication type earlier, you should see nothing different happen except maybe a blink. If your user was a dialog user, however, you will see a logon screen for the target system.

Hope this helps!
 

Thanks A lot, it really helps a lot!!!

Now I need to think of how to create the program now..
 

small correction:
the interface user/password have to be legal only in the target system.
...and try use different users for different interfaces and to minimalize the interface users
rights. In other case you cuold never find out who, why and how modified your data.
 

Beam Back to Basis Index SAP Cafe for Basis Components Beam Back to Main Index SAP Cafe for SAP Professional