Thursday 13 October 2011

Lock a client so configuration changes cannot be made in SAP







*** Before adding a new client you should first ask if it will be used in communications with other clients (Central User Administration, source for client copies, etc.)  If so, the new client will need to be assigned a Logical System ID that is unique among all the SAP systems in the landscape.  It is recommended that all new clients be assigned to a Logical System ID as soon as they are created. ***

1.               Log on to any customizable client in the appropriate SAP system.
2.               Go to transaction SCC4.
3.               On the Display View “Clients”: Overview screen, click the pencil and glasses picture-icon to switch into change mode.
4.               On the Display View “Clients”: Overview popup, click the green √ to dismiss the informational message.
5.               On the Change View “Clients”: Overview screen, click the New Entries button.
6.               On the New Entries: Details of Added Entries screen, fill in Client number and description and the City.  Use the Logical system dropdown to assign a logical system ID to the client.  Type “USD” in the Std currency box.  Select a Client role from the client role dropdown (remember that there can only be one Productive client per SAP system).  In the Changes and transports for client-specific objects, Client-independent object changes, Protection: Client copier and comparison tool, and Restrictions when starting CATT and eCATT sections, select the necessary restriction levels from the provided dropdowns.  Once all information has been provided, click the Save picture-icon.
7.               You will see a Data saved in the status bar at the bottom of the screen.  You may now leave the SCC4 transaction.


1.               Log on to the client to be deleted.
2.               Go to transaction SCC5.
3.               On the Delete Client screen, verify that you are deleting the correct client.  If you also want the client deleted for T000 (ie the scc4 entry), put a √ in the □ to the left of Delete entry from T000 by clicking the □.  Click the Background button.
4.               On the Schedule Client Copy in Background screen, use the Background server dropdown to select the background server on which the job is to run.  There should only be one server available in the dropdown.  Click the Schedule job button.
5.               On the Verification popup, check that everything is correct and click the Continue button.
6.               On the Start Time popup, if you want the client delete job submitted right away, click the Immediate button.  To schedule the delete for a later date and/or time, click the Date/Time button.  In the Date/Time section, provide the Scheduled start Date and Time.  If you are unsure as to the format of date and time, click on the top-most menu bar System User profile Own data.  Click on the Defaults tab to see your default date format.  Click the Save picture-icon.
7.               On the Background Print Parameters popup, select an Output device from the dropdown.  Click the green √ to continue.
8.               You will receive a client copy confirmation message.  Don’t panic, it looks like a client copy confirmation and says nothing about this being a delete job.  You can monitor this copy by using transaction SCC3.  You may now leave the SCC5 transaction.





      When adding a new client to a SAP system, the information listed in
      the SCC4 can be confusing.  This is a brief explain of the
available client restrictions.

      Client role:

            The category indicates the role of the client in your R/3
            system.

     Possible roles are:

            *     Production client
            *     Test client
            *     Training client
            *     Demo client
            *     Customizing client
            *     SAP reference client

            This field should be maintained by the customer for
Documentary purposes. Release 3.0 also ensures the following:

If there is a productive client in the target system, no client copy (remote copy) which also selects cross-client customizing objects may be imported into the system. If cross-client settings are imported, inconsistencies may occur in all clients.

In a productive client, customizing settings that can be maintained as "current settings" can be excluded from a client lock or transport links; this means current settings (e.g. exchange rates, posting periods) can always be maintained in a productive client without recording changes. SAP is planning to link further effective functionality to this flag, to enable adequate protection of a productive client in a system with further (test) clients.

     
Other settings for a client:

            Change and transports for Client Dependent Objects
                 
Changes without automatic recording – the client can be customized although the system will not generate change requests.
           
Automatic recoding of changes – the client can be customized and all changes are generated into change requests.

No changes allowed – no modifications can be made to the client – it is protected or locked.  This is the usual configuration for a production client where customization should not be performed.

                  No transports allowed – changes are allowed but cannot be
                  transported.

            Client-Independent Object Changes

Changes to repository and client-independent customizing allowed – no restrictions on this client for changes and development.

No changes to client-independent customizing objects - allows for development on repository objects but not client-independent customizing.

No changes to repository objects – lets users perform client-independent customizing but no development or modifications to repository objects.

No changes to repository and client-independent customizing objects – this setting prohibits any client-independent modifications and is common on Production systems.

No comments:

Post a Comment