A client represents a completely independent business entity.
A client has its own database.
A client corresponds to a customer.
A client may represent an entire company.
From SAP Easy Access: SM04
From SAP Easy Access: search_sap_menu
Load balancing possible
Dialog work process
Update work process
Internet Communication Manager (ICM)
Background work process
Spool work process
Client independent customising, user data, and application data
Client-dependent customising, user data, and application data
Customising objects and repository objects
Only user data that was entered in this client
Because of the special data structure in SAP systems
To enable preparation and testing of release upgrades
To sell more licenses
Because you can only create one client in each SAP system
Developers release their tasks.
The development project leader releases the entire transport request.
The system automatically releases the transport request once all tasks are released.
For defining the technical attributes of a field
For including a foreign key dependency
For defining the semantic attributes of a field
For entering data in a table
Maintaining customer data in the production system requires a Customizing request.
A transport request can contain one or more tasks.
A task can always be assigned to only one developer.
The transport of objects is divided into Export, Storage, and Import phases.
Import to the target system always takes place automatically at 00:00 system time.
The transport directory is determined by parameter DIR_TRANS in the SAP system.
During transport, the following standard rule applies: The target client is the same as the source client, unless something to the contrary is defined.
Design Time Repository (DTR)
Object Development Tool (ODT)
Component Build Service (CBS)
Change Management Service (CMS)
Central Make Tool (CMT)
HTTP (HyperText Transfer Protocol)
SMTP (Simple Mail Transfer Protocol)
RFC (Remote Function Call)
BAPIs (Business Application Programming Interfaces)
XDTP (Extended Data Transfer Protocol)
STP (SAP Transfer Protocol)
Request data from an SAP system
Pass data to an SAP system
Transfer SAP screen images to third-party applications (such as Microsoft Word)
Access business processes in SAP systems
Exchange data only between SAP systems, as long as they have the same release status
Exchange data across system boundaries, but only between SAP applications
Exchange data between collaborating enterprises, using certain formats and technologies
To communicate between different systems of your system landscape
Update your order data using the appropriate BAPI, only once every 24 hours
A SAP solution manager
Transaction S_LIFECYCLE in any AS ABAP-based SAP system
System Landscape Directory (SLD)
SAP Advanced Landscape Optimizer (SAP ALO)
SAP Landscape Planning Tool - Version 1 (LPT1)
The Internet Communication Manager (ICM) distributes HTTP requests to all available application servers on your SAP system.
The ABAP Message Server can distribute requests to all available application servers during logon with the SAP GUI.
The ABAP dispatcher distributes user requests to the work processes of the present application server.
The SAP Web Dispatcher can distribute HTTP requests to different application servers of an SAP system in succession.
Root Cause Analysis
IT Service Management
SAP Support Packages contain error corrections and legal changes.
Importing SAP Support Packages is a purely voluntary measure.
SAP enhancement packages are cumulative.
SAP enhancement packages can add new functions to the SAP system.
Everyone who is interested in SAP
Only SAP employees