Obsolete keywords/techniques in ABAP HR

hi experts,
i am working on PY and time implimentation on ECC 6.0 , i need to have a refrence of
Obsolete keywords/techniques in ABAP HR.
kindly provide me the same or link to source to get the same.
regards,
Rahul

Check OSS notes and ECC Documentation for the same.

Similar Messages

Obsolete keywords/techniques in ECC 6

Hi Experts,
I have developed few HR Payroll reports in R/3 4.7.
Currently I am developing Payroll reports for ECC 6.
I found that most of Hr keywords/techniques I used with R/3 4.7 are obsolete with ECC6.
If so, are there any alternative techniques proposed for these obsolete techniques?
If LDBs obsolete, what is the alternate solution?
When performed an extended check for report in ECC6, following are few errors...
u2022 The current ABAP command is obsolete
Within classes and interfaces, you can only use "TYPE" to refer to ABAP Dictionary
types, not "LIKE" or "STRUCTURE".--->refers to line in code "NODES: pernr."
u2022 The current ABAP command is obsolete
"INFOTYPES" is not supported in the OO context.
Internal Message Code: INFOTYPES 004--->refers to line in code INFOTYPES :
I have been through few threads on forum but could not come to any solution.
Points will be rewarded.
Achyut

I have several custom payroll reports that were developed back in 4.6 and 4.7 and they work fine in ECC 6.0 systems. They use the logical database - both PNP and PNPCE - for employee selection, and then some custom function modules that in turn call standard SAP function modules and methods. Yes, the extended syntax check in ECC 6.0 warns about a few things, but everything runs fine.
My longer term goal is to move all the custom function module work to classes & methods, as time allows. That is definitely the more standard, new way to program HR/Payroll reports. But... the older methods should still work fine for now.

Obsolete Keywords from SAP version 4.6C to ECC 6.0

Hi ,
I want to upgarde my sap system from version 4.6c to ECC 6.0.
Can anyone provide me the list of obsolete keywords that are in 4.6c and the new keyword for tht in ECC6.0?
Thanks in advance

> Can anyone provide me the list of obsolete keywords that are in 4.6c and the new keyword for tht in ECC6.0?
Read
Note 367676 - Release upgrade from 4.6 to 6.10 for customer programs
Note 689951 - Release upgrade from 6.20 to 6.40 for customer programs
Note 857904 - Upgrade from Release 6.40 to 7.0:for customer programs
Markus

File Processing Techniques in ABAP

Hi, Friends,
Can any one let me know the file processing techniques used in ABAP.
Open/Close , Read/Write . are these used for file processing, if so can you explain me this syntax and scenario.
please let me know.
Regards,
Roberts.K

Hi Roberts
For file operations at application server layer, we use mainly OPEN DATASET, TRANSFER, CLOSE DATASET and DELETE DATASET statements.
For more information follow <a href="http://help.sap.com/saphelp_47x200/helpdata/en/fc/eb3c8c358411d1829f0000e829fbfe/frameset.htm">this link</a> .
Regards
*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a>

Estimation Technique for ABAP programmimng

Hi,
I would like to know if there are any formal software estimation techniques that may be used for ABAP development.The commonly used estimation techniques such as Function Point/LOC etc do not seem to fit in.We currently use WBS methodology but here again it is left to the discretion of the developer to estimate for the lower level tasks .
Any suggestions on a technique that would best suite the vast style of programming varying from reports to module pools/ sapscripts/bdc/user exits etc etc...
Regards
Rani

Thanks Serdar for the link . I will take a look at it.
In the recent past I have faced several instances where I have had to give estimates to the clients for ABAP development. Though we use WBS (Work Breakdown structure), but that also is gut feel based and based on the experience of the developer involved.I discussed this with several friends in the SAP world but no one had a real answer.
I tried using FPA which is a more unversally acceptable estimation technique.
The main problem I run into when trying to do some kind of estimation for ABAP development using FPA technique is:
1. There is no logical data model available in SAP
2. As a developer building custom programs, there is already so much code/functions available , the varying levels of reuse makes it difficult to estimate
3. Several program such as for BDC the code gets automatically generated and then we adapt this code further based on the requirements, so again estimation becomes difficult.
I would request some one from SAP to respond on how they do estimation & what technique do they use :
1) for new modules & functionalities that they build
2) for enhancement/bug fixes that they do to existing applications
Rather I would like to use the SDN forum as a means to formulate an estimation technique suitable for ABAP devlopment.
Hoping to receive some wonderful suggestion from all the brilliant people out there.
Cheers
Rani

Techniques in ABAP program

What are the techniques involved in using SAP supplied programs? do you prefer to write your own programs to load master data? why ?

Chandru,
What are the techniques involved in using SAP supplied programs?
The above question is not clear,what actually you are looking for.
Do you prefer to write your own programs to load master data? why ?
To load transaction data we can use LSMW,SCATT,BDC or BAPI.
BDC is mostly used when uploading data is w.r.t some validations.If it is just a simple upload then we can use LSMW or SCATT.If a BAPI is available then it is the best way to upload data.
K.Kiran.

OBSOLETE KEYWORDS IN ECC 6.0

HI ALL
PLEASE SEND ME THE REPLACEMENT OF FOLLOWING KEYWORDS IN ECC 6.0
1. DEFINE
2. DESCRIBE
3. IMPORT DIRECTORY INTO
4. EXEC SQL
5. SUBMIT
6. TRANSLATE
7. DELETE FROM DATABASE
8. ASSIGN

I DONT KNOW

Obsolete list - keywords , Fm's etc

Hello ,
Is there any link in service market place or any official links of SAP that describes the list of obsolete keywords , Function modules and any other objects types that is obsolete w.r.t ERP6.0 . I need the exact list of all obsolete sap objects .
Appreciate ur response .
Thanks,
Jee.R

Hi Jeeva,
It's quite difficult to find all the obsolete FM and statments in ABAP at a single place..
Check these links for few :
https://www.sdn.sap.com/irj/scn/wiki?path=/display/abap/new%252bfm%252bin%252bplace%252bof%252bobsolete%252bfm
/people/community.user/blog/2008/08/28/sap-obsolete-functions-1--popuptoconfirm
Sachin

ABAP Programming Guidelines not showing in ABAP Keyword Documentation

We are currently in the process of upgrading to Netweaver 7.0 EhP2
I have seen mentioned that the ABAP Keyword Documentation and ABAP Examples are now all provided in an improved ABAPDOCU transaction. In addition, the ABAPDOCU transaction is meant to also have a section on ABAP Programming Guidelines.
I have seen a screen example of what the ABAPDOCU screen now looks like (as shown in the mockup below). Our ABAPDOCU screen looks very similar except that there is no node for ABAP Programming Guidelines.
That is an area that I would like to have a closer look at. Have we missed something. Is this available as part of the standard 7.0 EhP2 install or does it need to be installed separately (or perhaps is this only available in a higher EhP). I've tried finding further information on this option but have not been able to come across anything. Does anyone know what would be involved (or if it is possible) to make this available in EhP2
Greg Milici
ABAP Developer
...V...ABAP Keyword Documentation
.......>...ABAP Overview
.......>...ABAP - Reference
.......>...ABAP - Short Reference
.......>...ABAP - Release-Specific Changes
.......>...ABAP Programming Guidelines
............ABAP Glossary
............ABAP Index
............ABAP Subject Directory
etc.

Hi Greg,
When [searching|http://help.sap.com/search/sap_trex.jsp] the [documentation for NW 7.0.2|http://help.sap.com/nw702/] for ABAP keyword there are several documents that mention how you can find more details about ABAP keywords. For example, [Data Consistency|http://help.sap.com/saphelp_nw70ehp2/helpdata/en/41/7af4b6a79e11d1950f0000e82de14a/frameset.htm] mentions a menu in the ABAP Editor, and [New Features in Web Dynpro ABAP for Enhancement Package 2 (EhP2)|http://help.sap.com/saphelp_nw70ehp2/helpdata/en/54/07ec96bd5a4764be4996fff231b4de/frameset.htm] mentions the ABAPHELP transaction.
I suppose you could try to find if the documentation you need is installed on your system. Perhaps the [how do I Install SAP Document CD and SAP Library|how do I Install SAP Document CD and SAP Library; thread might be of help.
Best regards,
Rossen

ABAP keyword 'BUILD'

Hi Guru's,
I would like to know if ther is any keyword 'BUILD' in ABAP.
If yes please let me know how it is used.
regards
Sunil Kumar P

Hi,
The statement has been used in one of the program which has to be upgraded to ECC6.0.
I could not replace this BUILD statement. Below is the code
REPORT zghgtmrg .
merge trkorr-list into a single transport
TABLES: e070, e070c, e071, e071k.
PARAMETERS: p_sfile RADIOBUTTON GROUP a,
            p_slist RADIOBUTTON GROUP a.
SELECTION-SCREEN SKIP 1.
PARAMETERS: p_file                     LIKE rlgrap-filename.
SELECTION-SCREEN SKIP 1.
SELECT-OPTIONS: p_list FOR e070-trkorr.
PARAMETERS: p_trkorr LIKE e070-trkorr DEFAULT 'CD1K90????'.
DATA: BEGIN OF wk,
               rec(255),
               p1(32),
               p2(32),
               p3(32),
               p4(32),
               p5(32),
               p6(32),
               p7(32),
               p8(32),
               p9(32),
               trkorr                  LIKE e070-trkorr,
               ctr                     TYPE i,
               as4pos                  LIKE e071-as4pos,
               errsw,
      END   OF wk.
DATA: BEGIN OF wk_thiskey,
                 pgmid                 LIKE e071k-pgmid,
                 object                LIKE e071k-object,
                 objname               LIKE e071k-objname,
      END   OF wk_thiskey.
DATA: BEGIN OF wk_lastkey,
                 pgmid                 LIKE e071k-pgmid,
                 object                LIKE e071k-object,
                 objname               LIKE e071k-objname,
      END   OF wk_lastkey.
DATA: fe071 LIKE e071 OCCURS 100 WITH HEADER LINE,
      fe071k LIKE e071k OCCURS 100 WITH HEADER LINE,
      te071 LIKE e071 OCCURS 3000 WITH HEADER LINE,
      te071k LIKE e071k OCCURS 3000 WITH HEADER LINE.
DATA: BEGIN OF ifile OCCURS 500,
                 rec(255),
      END   OF ifile.
DATA: x09 TYPE x VALUE '09'.
*Begin Of Change by v02.01MA3
DATA L_P_FILE TYPE STRING.
     L_P_FILE = p_list.
RANGES: i_list FOR e070-trkorr.
START-OF-SELECTION.
Check input parameters:
IF NOT p_slist IS INITIAL.
    DESCRIBE TABLE p_list LINES wk-ctr.
    IF wk-ctr EQ 0.
      MESSAGE i368(00) WITH 'Specify trkorrs in list'.
      EXIT.
    ENDIF.
ELSE.
    IF p_file IS INITIAL.
      MESSAGE i368(00) WITH 'Specify filename'.
      EXIT.
    ENDIF.
ENDIF.
IF NOT p_slist IS INITIAL.
use p_list from selection screen:
Check selected transports:
    LOOP AT p_list.
      IF p_list-option NE 'EQ'.
        MESSAGE i368(00) WITH 'Do not use generic selections'.
        MOVE 'X' TO wk-errsw.
        EXIT.
      ENDIF.
    ENDLOOP.
ELSE.
Build p_list from (P_FILE).
This last statement has to be replaced.
Can anyone guide me on this.
Regards
Sunil kumar P

Keyword documentation is not visible....

When I press F1, only the keywords on the ABAP keyword documentation are visible. The documentation is not visible on the right. It is blank.
what may be the problem...
Thanks in advance for ur help...
Rajkamal

Hi Rajkamal,
Firstly when you press F1 on a keyword it will popup a window with the list statements for that keyword with the information which statement is used and which had been made obsolete, then clicking on them will take to the documenation of that keyword in a new window.......
With luck,
Pritam.

Obsolete tables in ECC6.0

Hi All,
Please let us know the list of obsolete tables in ECC6.0 (after an upgrade from 4.6c).
We already have TVARV & BP000 in our list.
Thanks & Regards
Anjali

Hi Anjali,
Check below thread:
Obsolete Keywords from SAP version 4.6C to ECC 6.0
Thanks
Sunny

Performance and tuning techniques

Hi Experts,
Good moring, please help me to send what are performance and tuning techniques in abap programming.
how to improve the performance of abap program please give reply asap.
Regards
Venkat

Did you notice that your previous 6-odd questions were deleted by the moderators for breaking the rules of this forum? If you do not read the rules and abide by it, you will surely lose your account here in SCN.
pk

Delete obsolete combinations in /SAPAPO/MC62 - how to use?

Hello SAP-experts,
We are using SAP APO Demand planning SAP SCM 7.0 with SP 15 for most of components.
I have some questions related to the button "delete obsolete combinations" in TA /SAPAPO/MC62. We want to use option "list combinations without planning data" to reduce CVC's quantity. What I have read it checks for CVC's without any entries at key figures. It sounds useful, but it doesn't seem to work in our company for some reason.
1. Where exactly does system check if there are key figures for the selected CVC's? In livecache directly? Or in an internal generated info cube for the planning area? Is it possible to view these key figures (on same base as done from system with option "list combinations without planning data") before using the deletion? Is there a report / table to do so? What's the best practise for this check (maybe on daily base)?
2. I have (some) CVC's without any key figure filled (for my opinion...). At the moment I check this with an info cube used for daily backup (means I see always the data from last night and I know that noone changed data because of blocked planning access). But it isn't found with "list combinations without planning data". When displaying the data in this backup-cube all key figures are shown as zero (the one which are shown for deletion and in same way the cvc's which are not shown). In the key figure settings "differentiation between zero and initial value" is not marked... I think this is correct, but maybe I have a misunderstanding here... any ideas about this setting? I don't believe this setting is wrong, because it shows me some CVC's to be deleted, but some of them are not shown (the setting should work for all cvc's in same way...?).
All ideas are most welcome, thank you all in advance!
Best regards
Harald Leissl

Hello Ali,
thank you for your reply!
My plan was to use standard tool, because it's available since some releases. I don't prefer to implement own programming instead of using an existing tool (talking about the built ABAP tool, the idea with alert makro sounds good).
Is the standard tool effective??? Good question. We talk about 2 steps.
If the mentioned function "delete obsolete" would work like designed (maybe it does, but I don't understand how...) it would do 2 steps combined:
- find out obsolete CVC's (your alert makro)
- delete obsolete CVC's (your ABAP tool)
Combining these 2 steps would be really effective, but it doesn't work for some reason. My estimation is that standard is not effective, because complete process of deletions of CVC's is very slow and causes sometimes performance trouble.
But this is the reason why I search for a standard tool to run periodically (maybe each week) for a check of "old" CVC's. I think our problem of slow running deletions is caused by too many CVC's in an planning object structure (together with the fact that our CVC's have a lot of key figures / characteristics).
To be honest my main task is to find the best possibility to delete a list of completely different CVC's (no unique selection possible). I tested a lot of things found in SCN (realignment, background deletion,...), but all the solutions have s lack in performance (at least in our system...).
Regards
Harald

What are the various system variabels in ABAP

What are the various system variabels in ABAP?

u can view all the system variables in SYST TABLE Also   ...............
ABAP System Fields
ABAP system fields are always available in ABAP programs. The runtime system fills them according to context. They can then be used in programs to query the system status. System fields are variables but you should always treat them as though they were constants, and only read them. If you change their values, important information for the flow of the program may be lost. In exceptional circumstances, system fields may be overwritten in an ABAP program to control the system for example, SY-LSIND (for navigating to a detail list).
With one exception the names and data types of the system fields are stored in the ABAP Dictionary in the SYST structure and realized as components of the predefined structure SY in ABAP programs.
The system field SY-REPID is not part of SYST or SY. Instead, every program contains the predefined constants SY-REPID and SYST-REPID, which both contain the name of the corresponding program. Furthermore, there are two predefined types of the same name, SY-REPID and SYST-REPID.
All system fields are addressed using SY field name and their types using SYST field name.
                                                                                Alphabetical Overview
The following table lists the definitions of the structure SYST in the ABAP Dictionary alphabetically. The character in the first column indicates how you can use the corresponding system field in ABAP programs. Name is the name of the component, Type is the Dictionary data type, and Length is the field length defined in the Dictionary. The Use column shows in which environment the system fields are set. The Description indicates the content.
Name
Type
Length
Use
Description
ABCDE
CHAR
26
Constants
Alphabet (A,B,C,...)
APPLI
RAW
2
Obsolete
BATCH
CHAR
1
Background processing
Program runs in the background
BATZD
CHAR
1
Obsolete
BATZM
CHAR
1
Obsolete
BATZO
CHAR
1
Obsolete
BATZS
CHAR
1
Obsolete
BATZW
CHAR
1
Obsolete
BINPT
CHAR
1
Batch input
Program runs under batch input
BREP4
CHAR
4
Obsolete
BSPLD
CHAR
1
Obsolete
CALLD
CHAR
1
ABAP Program
Call mode of ABAP program
CALLR
CHAR
8
Printing Lists
ID for print dialog function
CCURS
DEC
9
Obsolete
CCURT
DEC
9
Obsolete
CDATE
DATS
8
Obsolete
CFWAE
CUKY
5
Internal
CHWAE
CUKY
5
Internal
COLNO
INT4
10
Creating Lists
Current column in the list
CPAGE
INT4
10
List processing
Current page number
CPROG
CHAR
40
ABAP Program
External procedure call
CTABL
CHAR
4
Obsolete
CTYPE
CHAR
1
Obsolete
CUCOL
INT4
10
Screens
Horizontal cursor position at PAI
CUROW
INT4
10
Screens
Vertical cursor position at PAI
DATAR
CHAR
1
Screens
Displays user input
DATLO
DATS
8
Date and time
Local date of user
DATUM
DATS
8
Date and time
Current (application server) date
DAYST
CHAR
1
Date and time
Daylight saving time flag
DBCNT
INT4
10
Database accesses
Number of processed table rows
DBNAM
CHAR
20
ABAP Program
Linked logical database
DBSYS
CHAR
10
R/3 System
Name of central database system
DCSYS
CHAR
4
Obsolete
DEBUG
CHAR
1
Internal
DSNAM
CHAR
8
Internal
DYNGR
CHAR
4
ABAP Program
Screen group of current screen
DYNNR
CHAR
4
ABAP Program
Number of current screen
ENTRY
CHAR
72
Internal
FDAYW
INT1
3
Date and time
Factory calendar weekday
FDPOS
INT4
10
Character strings
Offset in character strings
FFILE
CHAR
8
Internal
FLENG
INT4
10
Internal
FMKEY
CHAR
3
Obsolete
FODEC
INT4
10
Internal
FOLEN
INT4
10
Internal
FTYPE
CHAR
1
Internal
GROUP
CHAR
1
Internal
HOST
CHAR
8
R/3 System
Name of application server
INDEX
INT4
10
Loops
Current loop pass
INPUT
CHAR
1
Internal
LANGU
LANG
1
R/3 System
Current language
LDBPG
CHAR
40
ABAP Program
Program of logical database
LILLI
INT4
10
List processing
Selected list row
LINCT
INT4
10
Creating Lists
Page length of list
LINNO
INT4
10
Creating Lists
Current row
LINSZ
INT4
10
Creating Lists
Column width of list
LISEL
CHAR
255
List processing
Content of selected row
LISTI
INT4
10
List processing
Index of selected list
LOCDB
CHAR
1
Obsolete
LOCOP
CHAR
1
Obsolete
LOOPC
INT4
10
Screens
Number of rows visible in table
LPASS
CHAR
4
Internal
LSIND
INT4
10
List processing
Index of detail list
LSTAT
CHAR
16
List processing
ID for list levels
MACDB
CHAR
4
Obsolete
MACOL
INT4
10
Printing Lists
Columns from SET MARGIN statement
MANDT
CLNT
3
R/3 System
Client number from logon
MARKY
CHAR
1
Obsolete
MAROW
INT4
10
Printing Lists
Rows from SET MARGIN statement
MODNO
CHAR
1
R/3 System
Index of external modes
MSGID
CHAR
20
Messages
Message class
MSGLI
CHAR
60
Messages
Message line
MSGNO
NUMC
3
Messages
Message number
MSGTY
CHAR
1
Messages
Message type
MSGV1
CHAR
50
Messages
Message variable
MSGV2
CHAR
50
Messages
Message variable
MSGV3
CHAR
50
Messages
Message variable
MSGV4
CHAR
50
Messages
Message variable
NEWPA
CHAR
1
Internal
NRPAG
CHAR
1
Internal
ONCOM
CHAR
1
Internal
OPSYS
CHAR
10
R/3 System
Operating system of application server
PAART
CHAR
16
Print parameters
Print formatting
PAGCT
INT4
10
Obsolete
PAGNO
INT4
10
Creating Lists
Current page:
PAUTH
NUMC
2
Internal
PDEST
CHAR
4
Print parameters
Output device
PEXPI
NUMC
1
Print parameters
Retention period
PFKEY
CHAR
20
Screens
Current GUI status
PLAYO
CHAR
5
Internal
PLAYP
CHAR
1
Internal
PLIST
CHAR
12
Print parameters
Name of spool request
PNWPA
CHAR
1
Internal
PRABT
CHAR
12
Print parameters
Part of cover sheet
PRBIG
CHAR
1
Print parameters
Selection cover page
PRCOP
NUMC
3
Print parameters
Number of copies
PRDSN
CHAR
6
Print parameters
Name of spool dataset
PREFX
CHAR
3
Obsolete
PRI40
CHAR
1
Internal
PRIMM
CHAR
1
Print parameters
Print immediately
PRINI
NUMC
1
Internal
PRLOG
CHAR
1
Internal
PRNEW
CHAR
1
Print parameters
New spool request
PRREC
CHAR
12
Print parameters
Recipient
PRREL
CHAR
1
Print parameters
Delete after print
PRTXT
CHAR
68
Print parameters
Text for cover sheet
REPI2
CHAR
40
Internal
REPID
CHAR
40
ABAP Program
Current main program
RSTRT
CHAR
1
Internal
RTITL
CHAR
70
Print parameters
Title of printing program
SAPRL
CHAR
4
R/3 System
Release status R/3 System
SCOLS
INT4
10
Screens
Number of columns
SFNAM
CHAR
30
Obsolete
SFOFF
INT4
10
Internal
SLSET
CHAR
14
Selection screens
Name of variant
SPONO
NUMC
10
Printing Lists
Spool number
SPONR
NUMC
10
Obsolete
SROWS
INT4
10
Screens
Number of rows
STACO
INT4
10
List processing
First displayed column
STARO
INT4
10
List processing
Uppermost displayed row
STEPL
INT4
10
Screens
Index of current table row
SUBCS
CHAR
1
Internal
SUBRC
INT4
10
Return value
Return value after ABAP statement
SUBTY
RAW
1
Internal
SYSID
CHAR
8
R/3 System
Name of R/3 System
TABID
CHAR
8
Internal
TABIX
INT4
10
Internal Tables
Current row index
TCODE
CHAR
20
ABAP Program
Current transaction code
TFDSN
CHAR
8
Obsolete
TFILL
INT4
10
Internal Tables
Current number of rows
TIMLO
TIMS
6
Date and time
Local time of user
TITLE
CHAR
70
Screens
Text in header line
TLENG
INT4
10
Internal Tables
Row size
TLOPC
INT4
10
Internal
TMAXL
INT4
10
Obsolete
TNAME
CHAR
30
Obsolete
TOCCU
INT4
10
Obsolete
TPAGI
INT4
10
Obsolete
TSTIS
INT4
10
Internal
TTABC
INT4
10
Obsolete
TTABI
INT4
10
Obsolete
TVAR0
CHAR
20
Creating Lists
Text variable for headers
TVAR1
CHAR
20
Creating Lists
Text variable for headers
TVAR2
CHAR
20
Creating Lists
Text variable for headers
TVAR3
CHAR
20
Creating Lists
Text variable for headers
TVAR4
CHAR
20
Creating Lists
Text variable for headers
TVAR5
CHAR
20
Creating Lists
Text variable for headers
TVAR6
CHAR
20
Creating Lists
Text variable for headers
TVAR7
CHAR
20
Creating Lists
Text variable for headers
TVAR8
CHAR
20
Creating Lists
Text variable for headers
TVAR9
CHAR
20
Creating Lists
Text variable for headers
TZONE
INT4
10
Date and time
Time difference to Greenwich Mean Time
UCOMM
CHAR
70
Screens
Function code that triggered PAI
ULINE
CHAR
255
Constants
Horizontal line with length 255
UNAME
CHAR
12
R/3 System
Logon name of user
UZEIT
TIMS
6
Date and time
Current (application server) time
VLINE
CHAR
1
Constants
Vertical line
WAERS
CUKY
5
Obsolete
WILLI
INT4
10
Obsolete
WINCO
INT4
10
Obsolete
WINDI
INT4
10
Obsolete
WINRO
INT4
10
Obsolete
WINSL
CHAR
79
Obsolete
WINX1
INT4
10
Obsolete
WINX2
INT4
10
Obsolete
WINY1
INT4
10
Obsolete
WINY2
INT4
10
Obsolete
WTITL
CHAR
1
Creating Lists
Flag for standard page header
XCODE
CHAR
70
Internal
XFORM
CHAR
30
Internal
XPROG
CHAR
40
Internal
ZONLO
CHAR
6
Date and time
Time zone of user
Key:
The system field is set by the runtime environment. Its content can be evaluated in the ABAP program but not changed.
The system field is set by the runtime environment. Its content can be changed in the ABAP program to influence the runtime environment.
The system field must be set in the ABAP program. It can then be evaluated by the runtime environment or the program.
The system field is only for internal use and must not be used in ABAP programs.
The system field is obsolete and its content is not set. It cannot be used in ABAP programs.
                                                                                Thematic Overview
The following is a thematic summary of the system fields with notes on their use:
System information
·        Information on the current R/3 System
·        Information on the user session
·        Date and time information
·        Information on the current ABAP program
·        Background processing
·        Batch input
ABAP programming
·        Constants
·        Character strings
·        Loops
·        Internal Tables
·        Database accesses
·        Return value
Screens
·        Screens
·        Selection screens
·        Lists
·        Messages
Internal system fields
Obsolete system fields
                                                                                System Information
Information on the Current R/3 System
SY-DBSYS
Central database system, for example INFORMIX, ORACLE
SY-HOST
Application server, for example HS0333, PAWDF087
SY-OPSYS
Operating system of application server, for example HP-UX, SINIX
SY-SAPRL
Release status of R/3 System, for example 30D, 46A
SY-SYSID
Name of R/3 System, for example B20, I47
Information on the User Session
SY-LANGU
One-digit language key, for example D, E, F. Either logon language of user or set using the SET LOCALE LANGUAGE statement.
SY-MANDT
Client number the user logged on with, for example 000, 400.
For database accesses with Open SQL, SY-MANDT is used as the first key field of the WHERE clause.
SY-MODNO
Indexes external modes. Zero in first mode. In new modes, opened using the Create Mode function or by calling a transaction using /o, it is raised by 1. If previous modes were deleted, the free numbers are used first. Modes opened using CALL TRANSACTION STARTING NEW TASK start back at 0.
SY-UNAME
Logon name of user, for example KELLERH, BC400-01.
Date and Time Information
The following system fields are always set automatically. If necessary, the GET TIME statement synchronizes the application server time with that of the database server and writes it to the system field SY-UZEIT. SY-DATUM and the system fields for the local time zone, that is SY-TIMLO, SY-DATLO, and SY-ZONLO are also reset.
SY-DATLO
Local date of user, for example 19981129, 19990628.
SY-DATUM
Current (application server) date, for example 19981130, 19990627.
SY-DAYST
During daylight saving time X, otherwise empty.
SY-FDAYW
Factory calendar weekday, Sunday 0 Saturday 6.
SY-TIMLO
Local time of user, for example 154353, 225312.
SY-TZONE
Time difference to Greenwich Mean Time (UTC) in seconds, for example 3600, 10800.
SY-UZEIT
Current (application server) time, for example 164353, 215312.
SY-ZONLO
Time zone of user, for example CET, UTC.
Information on the Current ABAP Program
SY-CALLD
SY-CALLD contains SPACE if the program is the first and only program in a call chain. SY_CALLD contains 'X' if the program is a called program in a call chain (see ABAP Calls Overview).
·        SY-CALLD is set to X in a program called using CALL TRANSACTION, CALL DIALOG, or SUBMIT AND RETURN.
·        SY-CALLD is set to SPACE in a program called using LEAVE TO TRANSACTION, entering a transaction code on a screen, and processing batch input folders.
·        With SUBMIT (without RETURN) SY-CALLD retains the previous value.
SY-CPROG
In externally called procedures, the name of the calling program, otherwise the name of the current program. If an externally called procedure calls another external procedure, SY-CPROG keeps the name of the first main program and is not given the name of the main program of the further caller.
SY-DBNAM
With executable programs this is the linked logical database.
SY-DYNGR
Screen group of current screen. You can assign several screens to a common screen group. You can use this, for example, to modify all of the screens in the group in a uniform way.
SY-DYNNR
Number of current screen During the selection screen processing, SY-DYNNR contains the screen number of the current selection screen. During list processing, SY-DYNNR contains the number of the container screen. While a subscreen is being processed, SY-DYNNR contains its screen number. This also applies to tabstrips.
SY-LDBPG
With executable programs, the database program of the linked logical database.
SY-REPID
Name of current ABAP program. With externally called procedures this is the name of the procedures main program.
If SY-REPID was transferred to an external procedure as an actual parameter before Release 6.10, the formal parameter was not given the name of the caller, but the name of the procedures main program. SY-REID had to be transferred to an auxiliary variable before the call or you had to use SY-PROG.
As of Release 6.10, SY-REPID is a separate constant that is no longer part of the structure SYST or SY. It can be transferred to external procedures directly.
SY-TCODE
Name of current transaction code.
Background Processing
SY-BATCH
SY-BATCH is set to X in an ABAP program running in the background. Otherwise it is empty.
Batch Input
SY-BINPT
SY-BINPT is set to X during processing of batch input folders and in ABAP programs called with CALL TRANSACTION USING. Otherwise it is empty.
·         OPTIONS FROM in the CALL TRANSACTION USING statement can set SY-BINPT to empty for the whole program execution, as well as at the end of the BDC data.
·         In CATT procedures, SY-BINPT is always empty.
                                                                                ABAP Programming
Constants
SY-ABCDE
Contains the Alphabet. Can be used to access individual letters independently of the codepage by specifying offset.
SY-ULINE
Contains a horizontal line with length 255. Can be used when creating the list.
SY-VLINE
Contains a vertical line (|). Can be used when creating the list
Loops
SY-INDEX
SY-INDEX contains the number of loop passes in DO and WHILE loops, including the current loop pass.
Character Strings
SY-FDPOS
Found location for operations with character-type fields.
·        If the operators CO, CN, CA, NA, CS, NS, CP, NP are used in comparisons, SY-FDPOS is assigned offset values depending on the comparison result.
·        SEARCH FOR sets SY-FDPOS to the offset of the found search string.
Internal Tables
SY-TABIX
Current line in an internal table. With the following statements SY-TABIX is set for index tables. With hashed tables, SY-TABIX is not filled or it is set to 0.
·        APPEND sets SY-TABIX to the index of the last table row, that is the total number of entries in the target table.
·        COLLECT sets SY-TABIX to the index of the existing or appended table row. With hashed tables, SY-TABIX is set to 0.
·        LOOP AT sets SY-TABIX to the index of the current table row at the beginning of every loop pass. After leaving a loop, SY-TABIX is set to the value it had before entering the loop. With hashed tables, SY-TABIX is set to 0.
·        READ TABLE sets SY-TABIX to the index of the table row read. If no row is found with binary search while reading, SY-TABIX contains the index of the next-highest row or the total number of rows +1. If no row is found with linear search while reading, SY-TABIX is undefined.
·        SEARCH 0). Each time an interactive list event occurs, the system automatically increases SY-LSIND by 1. SY-LSIND can be changed in the ABAP program to navigate between detail lists. Changes to SY-LSIND are not taken into account until the end of the list event. Therefore, any manipulation of SY-LISND should be done using the last command of the processing block.
SY-LSTAT
ID for list levels within the program. SY-LSTAT can be filled with values during list creation in the ABAP program. The value valid when the list is completed is saved with the list. In the case of an interactive list event, SY-LSTAT is set to the value it was assigned during the creation of the list from which the event takes place. SY-LSTAT is no longer maintained and should therefore no longer be used.
SY-STACO
Number of the first displayed column of the list from which the event was triggered. Counting starts at 1.
SY-STARO
Number of the upper-most displayed row of the upper-most page of the list, from which the event was triggered. Counting begins at 1. This does not include the page header.
Printing Lists
When printing lists, the spool and runtime systems require certain internal information, which is available in the following system fields and is set during print activation.
SY-CALLR
Contains a value that displays where printing was started, for example NEW-PAGE for program-controlled printing or RSDBRUNT for printing from the selection screen.
SY-PRDSN
Contains the name of the spool file during printing.
SY-SPONO
Contains the name of the spool number during printing.
SY-MAROW, SY-MACOL
The SET MARGIN statement fills the system fields SY-MAROW and SY-MACOL, which determine the number of lines on the upper margin and the number of columns on the left margin when printing.
Print Parameters
The print parameters are transferred to the spool system by the runtime system in a structure of dictionary type PRI_PARAMS. Before this structure was used, its purpose was served by system fields. Today a subset of the PRI_PARAMS structure is still written to system fields with the same names when printing is activated. This information is redundant and should not be used.
Messages
If you execute the MESSAGE statement, the following system fields are set. If you execute the MESSAGE RAISING statement in function modules and methods, these fields are also set in the calling program, if it handles the exception.
SY-MSGID
SY-MSGID contains the message ID.
SY-MSGNO
SY-MSGNO contains the message number.
SY-MSGTY
SY-MSGTY contains the message type.
SY-MSGV1,,SY-MSGV4
SY-MSGV1 to SY-MSGV4 contain the field contents that are used for the messages placeholders.
Special Actions that Fill Message Fields
·        If you request database locks using the ENQUEUE function module, the field SY-MSGV1 contains the name of the user who holds the lock, in the case of the FOREIGN_LOCK exception.
·        IN the case of CALL TRANSACTION or CALL DIALOG with the USING addition, a message displayed during the called screen sequence is returned in the fields SY-MSGID, SY-MSGTY, SY-MSGNO, SY-MSGV1, ... , SY-MSGV4.
·        During Remote Function Call (RFC), error messages are transferred from the remote system to the calling system and SY-MSGID, SY-MSGTY, SY-MSGNO,SY-MSGV1, SY-MSGV2, SY-MSGV3, SY-MSGV4 are set. If short dumps or type X messages occur, the system also sets the fields.
                                                                                Internal System Fields
Internal system fields are only for internal use in the ABAP runtime environment and are defined in the kernel. Under no circumstances must they be overwritten in ABAP programs and they should also not be read (processed).
SY-CFWAE
Undocumented
SY-CHWAE
Undocumented
SY-DEBUG
Undocumented
SY-DSNAM
Name of spool output file.

Obsolete keywords/techniques in ABAP HR

Similar Messages

Maybe you are looking for