Search This Blog

Sunday, February 6, 2011

BASIS FAQs - 4

1.      Diff between remote client copy and client transport?

In remote client copy data is transferred between source and target using RFC (remote function calls) through a network connection....and in client transport, data is exported to a file at the operating system level, at some future time the client can be imported from the file system to the target system...

 

2.      What are client settings?

The system change option controls whether Repository objects and cross-client Customizing objects are modifiable or not.

The system change option does not affect client-specific Customizing changes. To set whether these changes can be made or not

 

3.      What is client copy?

You can use the client copy to create, for example the following clients:

· New clients from the SAP reference client 000 during initial installation of an R/3 System.

· Training clients

· demo clients

· test clients

· Production clients

The source client can be in the same or another system.

 

4.      If any errors coming during transport where it will be recorded and how will you rectify?

Transport log and active log.

 

5.      Buffer monitoring?

Each SAP instance (application server) has its own buffers. These buffers are also known as client caches because they are implemented on the client, that is, the application server.

SAP buffers store frequently-used data, and make this data available to the local application server instance. This helps to reduce the number of database accesses, the load on the database server (it does not need to be accessed repeatedly to obtain the same information), and network traffic. As a result, system performance is considerably improved.

 

6.      What is the link between roles, profiles and projects?

 

·          Roles are collections of activities which allow a user to use one or more business scenarios of an organization.

·          SAP profiles are operating system files that contain instance configuration information. SAP systems can consist of one or more instances. Individual configuration parameters can be customized to the requirements of each instance. These individual parameters allow you to configure:

· The runtime environment of the instance (resources such as main memory size,     shared memory, roll size)

· Which services the instance itself provides (work processes)

· Where other services can be found (database host)
 

7.      What is the purpose of archive?

Top six reasons to archive your SAP data:

  1. To improve system performance by reducing the size of the SAP database. Data growth in the SAP system adversely affects performance.
  2. Cannot just delete certain data to government regulations, taxation (IRS) regulations, FDA requirements, internal organizational requirements, and audit requirements.
  3. To reduce the amount of time and effort required for systems administration back-ups, client copy, upgrades, month-end processes, etc.
  4. To reduce the amount of storage required for data. Significant savings in storage space are realized through archiving.
  5. To perform effective archiving the process utilized must provide the required access to the archived data in order to satisfy regulatory and organizational requirements.
  6. An effective archiving process saved expenditures in hardware (storage and processing power) in addition to making systems administration activities more efficient.

8.      What is client?

SAP systems use the client concept to allow legally and financially independent entities to coexist in a system.
 

No comments:

Post a Comment