SAP Technical Glossary
This is an evolving page which aims to define all the technical terms within the R/3 environment. If you have any suggestions or corrections, please mail me.
A
B
C
D
E
F
G
Graphical User Interface. (e.g. SAPGUI - the interface between humans and R/3)
H
I
J
K
L
A method of preventing users writing to objects within the database which are currently being written to by another user. See also EnqueueWorkProcess
?.
M
R/3 process controlling communication between R/3 instances. The message server generally runs on the Central Instance.
A change to any repository object which was originally created by SAP.
N
O
Object Linking/Embedding
?
An R/3 function which can dynamically switch work processes from being batch to dialog and vice versa. This can be done either automatically by use of a timetable, or manually using the Contol Panel in CCMS.
P
Process After Input. ABAP code which is executed after a screen of information has been sent to the application server by the presentation server. This can include some validation, prior to progress to the next screen, or the end of the transaction.
Process Before Output. ABAP code executed before a screen is sent back to the presentation server.
An computer running the R/3 graphical user interface.
A transaction within R/3 which creates user profiles, and assigns them to users based upon activity groups.
Q
R
- /RelationDataBaseManagementSoftware?
Relational Database Management Software. (e.g. Oracle or MS SQL)
A change to any object in a system other than the system which 'owns' it.
Remote Function Call. R/3 supports a number of open communication standards. RFCs allow external systems to connect to R/3 over a network, execute code on the R/3 system, and have the results sent back over the network.
S
Systems, Application and Products (in data processing)
System Identifier. A three character name which identifies a system.
Spool work process. Responsible for formatting output requests for printers, and forwarding the output to the host operating system.
Text file containing profile parameters configuring how a specific instance within one system starts up.
An R/3 environment comprising of one or more instances of R/3 which share a common database server.
A two digit number which is used to identify a system. For different systems on different boxes, the system number can potentially be the same, but is usually different. For multiple instances on the same box, the system number must be different for each instance/system. The system number indicates what TCP/IP services are used by SAP processes. e.g. where nn is the system number, the dispatcher uses service 32nn. A list of these services can be found in the 'services' file on any machine which has had SAPGUI installed on it.
T
Usually under the directory path \usr\sap\trans, and the share/network mount point '\\sapserver\sapmnt\trans', the transport directory is an operating system storage area for data and programs being copied from one R/3 system to another in a Transport Group.
A number of R/3 systems whose transport system is administered by a common Transport Domain Controller.
- /TransportDomainController?
An R/3 system elected by the administrator as the one which will be used as the central administration system for the structure of the Transport Domain.
A number of R/3 systems which share a common transport directory.
Defines the route via which repository objects are transported once exported from the consolidation system.
See Change Request.
- /TransportManagementSystem?
Transport Management System. A set of transactions within R/3 which allow administrators to easily transport customising and development from one system to another within a system landscape.
U
To write data to the database, or an entity which requires writing to the database.
Work process responsible for writing V1 updates to the database.
Work process responsible for writing V2 updates to the database.
User defined ABAP/4 code which is executed by SAP original programs via pre-defined exit points.
V
Primary (usually time-critical) portion of an update.
Secondary (usually statistical - less important than V1) portion of an update.
W
Workbench Organiser. An R/3 transaction used for managing change requests involving client independent objects which can be transported. Transaction SE10
?
An R/3 kernel program providing a specific service within an instance.
X
Y
Z
This work is licensed under a Creative Commons Attribution-ShareAlike 2.5 License.