Abap system fields SY-DBSYSCentral database system (such as
INFORMIX or ORACLE)SY-HOSTApplication server (such as HS0333,
PAWDF087 )SY-OPSYSOperating system of the application server (such
as HP-UX, SINIX)SY-SAPRLR/3 Release in use (such as 30D, 46A,
)SY-SYSIDR/3 System name (such as B20, I47, ...)Information About
the Current Terminal SessionSY-LANGUOne-character language key with
the users logon language (such as D, E, F)SY-MANDTClient in which
the user is logged on (such as 000, 400)When you use Open SQL to
access the database, SY-MANDT is used as the first key field in the
WHERE clause.SY-MODNOIndex of the external sessions. The first
session has the index zero. The value is increased by one each time
you choose System Create session or start a transaction by entering
/o. If you have deleted sessions, the system fills free numbers
before increasing the count further. Sessions started using CALL
TRANSACTION STARTING NEW TASK begin again at 0.SY-UNAMEUsername of
the current user, such as KELLERH, BC400-01Information About
Current Date and TimeThe following system fields are always set
automatically. The GET TIME statement synchronizes the time on the
application server with the time on the database server and writes
it to the field SY-UZEIT. SY-DATUM and the system fields for the
local timezone (SY-TIMLO, SY-DATLO, and SY-ZONLO) are also reset.
SY-DATLOUsers local date, for example 19981129, 19990628,
SY-DATUMCurrent application server date, for example 19981130,
19990627, SY-DAYSTX during summertime, otherwise space.
SY-FDAYWFactory calendar day of the week: Monday = 1 Friday =
5.SY-TIMLOUsers local time, for example 154353, 225312,
SY-TZONETime difference in seconds between local time and Greenwich
Mean Time (UTC), for example, 360, 10800.SY-UZEITCurrent
application server time.for example 164353, 215312, SY-ZONLOUsers
time zone, for example, EST, UTC, Information About the Current
ABAP ProgramSY-CALLDX if the program was started using CALL
TRANSACTION, CALL DIALOG, or SUBMIT . Space if the program was
started using LEAVE TO TRANSACTION or using a transaction code from
a screen. SY-CALLD is always space when a batch input session is
being processed. SY-CPROGThe name of the calling program in an
external routine, otherwise the name of the current program.
SY-DBNAMThe name of the logical database linked to an executable
program. SY-DYNGRScreen group to which the current screen belongs.
You can assign several screens to one screen group, for example, to
allow you to modify them all identically. SY-DYNNRNumber of the
current screen. During selection screen processing, SY-DYNNR
contains the screen number of the current selection screen. During
list processing, it contains the number of the container screen.
During subscreen processing, SY-DYNNR contains the number of the
subscreen. This also applies to tabstrip controls. SY-LDBPGIn
executable programs, the database program of the associated logical
database. SY-REPIDName of the current ABAP program. For
externally-called procedures, it is the name of the main program of
the procedure. If you pass SY-REPID as an actual parameter to an
external procedure, the formal parameter does not contain the name
of the caller, but that of the main program of the procedure. To
avoid this, assign SY-REPID to an auxiliary variable and use that
in the call, or use the system field SY-CPROG.SY-TCODEThe current
transaction code.Background ProcessingSY-BATCHX if the ABAP program
is running in the background, otherwise spaceBatch InputSY-BINPTX
while a batch input session is running and when an ABAP program is
called using CALL TRANSACTION USING, otherwise space. OPTIONS FROM
in the CALL TRANSACTION USING statement can set SY-BINPT to space
either for the entire duration of the program, or at the end of the
BDC data. SY-BINPT is always space during a CATT procedure.
