Obsolete ABAP commands

hi friends,
Is it poosible to find out what are the Obsolete ABAP commands and Statements by comparing two different versions? an old version and an advanced version??
Is it stored in any table?
Pls Help
Regards
Dinesh

Hi,
Just check this link
http://www.nikat.org/www.geocities.com/victorav15/sapr3/abapobs.html
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb33cc358411d1829f0000e829fbfe/content.htm
You may have an overview wirth Solution Browser tool (at the solution point of view) in order to compare functionality between your current system and the ERP 2005.
at:
http://solutionbrowser.erp.sap.fmpmedia.com/
You can get the detailed release information from the following link.
http://service.sap.com/releasenotes.
A release note is a brief explanation of new features or changes to the system since the last software release. A release note typically describes a new function or an existing function that has been enhanced or changed.
Regards,
Padmam.

Similar Messages

In ECC 6.0 I am getting Slin Error -ABAP command is obsolete

Hi All,
In Hr ABAP we will start basic coding with
TABLES pernr .
infotypes:0002.
By using this I am getting the following SLIN Error :
Program: ZHCP0026 Row: 32
he current ABAP command is obsolete
Within classes and interfaces, you can only use "TYPE" to refer to ABAP Dictionary
types, not "LIKE" or "STRUCTURE".
nternal Message Code: MESSAGE G/B
(The message cannot be hidden using pseudo-comment "#EC .., bzw. durch SET
EXTENDED CHECK OFF/ON)
INFOTYPES : 0380,
The current ABAP command is obsolete
Tables with headers are no longer supported in the OO context.
Internal Message Code: MESSAGE G1D
(The message cannot be hidden using pseudo-comment "#EC .., bzw. durch SET
EXTENDED CHECK OFF/ON)
Can some one help me , how to rectify this slin error ?
Thanks,
Suresh.
Edited by: suresh kumar on Feb 25, 2009 2:22 PM

Hi Suresh,
Am too facing the same problem. if you could find a solution, pls let me know.

The current ABAP command is obsolete

Hi Experts,
please let me know how this error can be removed.
The current ABAP command is obsolete
The variant " WITH KEY k" is no longer supported in the OO context. Use an
explicit key specification instead . . . .
Internal Message Code: READ 022
(The message cannot be hidden using pseudo-comment "#EC .., bzw. durch SET
EXTENDED CHECK OFF/ON)
Thanks and Regards,
Johny

Hi Experts,
Iam having no key to compare with.
The scenario is as follows:
*If it is PaymentLot,retrieve Payment method,Gpart,Banknumber,Bank accountnumber,paymentcard number and amount
from DFKKZP and DFKKOP for the cleared document
CALL FUNCTION 'FKK_PAYMENT_BATCH_FIND_PAYMENT'
EXPORTING
i_opbel = wa_cleareditem-augbl
IMPORTING
e_dfkkzp = et_dfkkzp
EXCEPTIONS
not_found = 1
OTHERS = 2.
IF sy-subrc <> 0. "#EC NEEDED
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF et_dfkkzp-bankl IS NOT INITIAL. "Check for Bank key and Card number
lv_bankl = et_dfkkzp-bankl.
ENDIF.
IF et_dfkkzp-ccnum IS NOT INITIAL.
lv_ccnum = et_dfkkzp-ccnum.
ENDIF.
IF et_dfkkzp-bankl IS INITIAL AND et_dfkkzp-ccnum IS INITIAL. "If both bank key and Card number are initial
e_pymet = c_pymet. "Populate payment method as 'K'
ENDIF.
*For the obtained Business partner,fetch Bankdetails id and Payment card id from
*exporting parameters of F.M 'FKK_BUPA_READ_SINGLE'
CALL FUNCTION 'FKK_BUPA_READ_SINGLE'
EXPORTING
i_partner = lv_partner
i_xbank = 'X'
i_xccard = 'X'
TABLES
t_bank = it_bank
t_ccard = it_ccard
EXCEPTIONS
partner_not_found = 1
partner_in_role_not_found = 2
internal_error = 3
OTHERS = 4.
IF sy-subrc <> 0. "#EC NEEDED
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
READ TABLE it_bank INTO wa_bank WITH KEY bankl = lv_bankl BINARY SEARCH. "Pick the entry which has bankl value as from et_dfkkzp
IF sy-subrc = 0.
e_pymet = c_pymetb.
e_bkvid = wa_bank-bkvid.
ENDIF.
READ TABLE it_ccard INTO wa_ccard WITH KEY ccnum = lv_ccnum BINARY SEARCH. "Pick the entry which has ccnum value as from et_dfkkzp
IF sy-subrc = 0.
e_pymet = c_pymetd.
e_ccard_id = wa_ccard-ccard_id.
ENDIF.
ENDIF.
ENDFORM. " ORIGINKEY_V1

ECC 6.0 Upgrade from R/3 4.6B - Obsolete ABAP Language

Hello all,
I am part of a team that is performing an upgrade to ECC 6.0 from R/3 4.6B. I was wondering if all of the reports, FM, etc. that were developed under "old" ABAP will have to be modified in order to comply with the <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca">Obsolete ABAP Language Constructs</a>.
If the code still works after the upgrade is it necessary to perform all these modifications?
Thank you very much in advance,
Best Regards,
Ezequiel

I would say that is is not necessary. From the second paragraph of your link:
"Although you are generally not forced to modify your existing programs to represent these changes, it would be a very good practice to implement these rules and constructs with any new code development and coding samples."

How to run others applications with abap commands

Is there a mothed that can use it to run an application with abap statement?
for example: how to open a text file in program with abap command?
thank you very much.

CALL FUNCTION 'WS_EXECUTE'
EXPORTING
DOCUMENT = ' '
CD = ' '
 COMMANDLINE = ''
INFORM = ' '
 PROGRAM = 'NOTEPAD'
STAT = ' '
WINID = ' '
OSMAC_SCRIPT = ' '
OSMAC_CREATOR = ' '
WIN16_EXT = ' '
EXEC_RC = ' '
IMPORTING
RBUFF =
EXCEPTIONS
FRONTEND_ERROR = 1
NO_BATCH = 2
PROG_NOT_FOUND = 3
ILLEGAL_OPTION = 4
GUI_REFUSE_EXECUTE = 5
OTHERS = 6
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Here...
In the CommandLine you can give the path where the file is located like for Example
C:\Test\Hello.txt.
In the Program you need to give the application that you want to open that file.
if helpful reward points...
Regards,
Vivekananda Varma Dandu

Obsolete ABAP statements in OOPs context

Obsolete ABAP statements in OOPs context

hi,
Check t-code UCCheck.
Put the program name in the t-code and you will get the obsolete statements.
Also check table radir.
Reward points if useful.

Comparison between ABAP command statements in different versions

Hi,
I'm looking for information on version wise difference in ABAP statements. Can someone provide help in this area.
I need a list of Commands along with there syntax in different versions of ABAP (ECC 5.0 and 4.7).
Is there any system table where this information is maintained?
Regards,
Gajendra Bhatt

Hi Gajendra ,
I doubt if SAP has some document which shows the history of all ABAP commands as to how they behaved in which version. The only option you have is go through the following notes and compile the info manually -
0000178452 Release upgrade from 4.0 to 4.5 for customers prog
0000452229 Release upgrade from 6.10 to 6.20 for customer pro
0000178725 Release upgrade from 4.5 to 4.6 for customer progr
0000689951 Release upgrade from 6.20 to 6.40 for customer pro
0000178482 Rel. upgrade from 3.0 to 4.0 for customer programs
0000857904 0003 0.460 Upgrade from Release 6.40 to 7.0: Customer program
0000367676 0061 0.450 Release upgrade from 4.6 to 6.10 for customer prog
0000099025 0004 0.340 Change from 4.0A/B to 4.5A for customer programs
Cheers.

Obsolete ABAP statements/FM/BAPI in sap 4.7

dear experts
pls gv me the details of obsolete ABAP statements/FM/BAPI in sap 4.7 and their replacement in ECC 6.0,the statements should be related to MODULE POOL ,reports

Hello
ERP 6.0 implies Unicode as well. Therefore have a look at [ABAP and Unicode|http://help.sap.com/saphelp_nw04/helpdata/en/62/3f2cadb35311d5993800508b6b8b11/content.htm]
You will find useful documentation in the ABAP keyword documenation (ERP 6.0) as well:
Obsolete Statements
The statements described in this subnode are obsolete and are only still available for reasons of compatibility with releases prior to 4.6 or 6.10. You may still come across these statements in old programs but you should not use them in new programs.
Most of the obsolete statements listed here are syntactically forbidden in ABAP Objects or in Unicode programs. As a result, they can now only be used outside of classes or non-Unicode programs. There are replacement constructions for all obsolete statements which improve the efficiency and readability of programs.
Apart from the obsolete statements listed in this node, there are also obsolete variants and additions for non-obsolete statements. These cannot be used in ABAP Objects and Unicode programs either. They are detailed in the description of the corresponding statements.
Regards
Uwe

Urgent: About Obsolete ABAP statements in Netweaver 4.0?

Can any body please help us about the obsolete ABAP statements in Netweaver 4.0 corresponding to SAP 4.6?

Hi,
Pls read first the rules of engagement.
Anyway, open an editor and choose Utilities->Help on->New features in ABAP.
Or check notes like
367676 and 689951
Eddy

Obsolete ABAP objects

Hi Experts:
Can anyone provide list of obsolete objects for ECC6.0?
Thanks,

Hi,
Please check this link for Obsolete ABAP Language Constructs.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
Regards,
Ferry Lianto

ABAP Command

Hi friends,
     is there any ABAP command or Function module to run the another ABAP Program(not Transaction code or area menu).
Thanks & Good regards,
vallamuthu.M

Hi,
You can use SUBMIT statement with VIA SELECTION-SCREEN option. Please check this sample code.
SUBMIT demo_program_submit_rep1 VIA SELECTION-SCREEN
                      WITH paramet eq 'Selection 1'
                      WITH selecto IN seltab
                      WITH selecto ne 3
                      AND RETURN.
Regards,
Ferry Lianto

ABAP command "import from database..."

Can someone in this forum explain to me the low level details behind the ABAP command "import from database"?
The select in tables like stxl, indx, moni just retrieves data in hex format for the fields of type raw or lraw.
But the command import from database works fine!
What's the magic? Compression? Hash algorithms? etc?
Thanks!

When you import a field from a database, it should be the same name and format when it was exported. These databases are a cluster table where data is stored in raw. I assumed it will read the cluster portion of the record and convert it into the field structure byte by byte. These tables have field CLUSTR which store the byte size of the record. So if you are willing to program the read, where you find out the length of the field you want to IMPORT, then read that number of byte from the cluster data, move it to the field you are importing, you should be able to do your own read. However, if we can do it in 1 statement using IMPORT, we don't need to program it.
Cluster table is used to save space since you don't need to create a new database record for each line of internal table you stored into them. Hope this helps.

Re : The ABAP Command

Is there is any ABAP Command such that my input is program name and output is the program output

Hi ,
There is no such ABAP command, but you can create a function module and call it from anywhere with your import parametres. You can get back the output using export parameteres of function module. Syntax is as below.
CALL FUNCTION 'XYZ'
IMPORTING
EXPORTING
Also, You can call a public Method implemeted in a class.
Regards,
Harpal

What are abap commands that link to a layout set

hi
what are abap commands that link to a layout set

Hi,
Script Commands:
ADDRESS : Formatting of Address
BOTTOM, ENDBOTTOM : Define Footer text in a window
BOX, POSITION, SIZE : Boxes, Lines and Shading
CASE, ENDCASE : Case Distinction
DEFINE : Value assignment to text symbols
HEX, ENDHEX : Hexadecimal values
IF, ENDIF : Conditional text output
INCLUDE : Include other texts
NEW-PAGE : Explicit forms feed
NEW-WINDOW : Next window main
PRINT-CONTROL : Insert print control character
PROTECT...ENDPROTECT : Protect from page break
RESET : Initialize outline paragraphs
SET COUNTRY : Country-specific formating
SET DATE MASK : Formating of date fields
SET SIGN : Position of +/- sign
SET TIME MASK : Formating of time fields
STYLE : Change style
SUMMING : Summing variables
TOP : Set header text in window MAIN
Regards,
Bhaskar

ABAP commands are obsolete.

Hi all,
Currently my firm is doing the 4.6C to ECC6 upgrade, there's a few programs having obsolete errors and I'm tasked to correcting the coding of this certain program. Here is the coding and the errors i encounter:
report YPU0014 line-size 360
               line-count 65
               no standard page heading.
selection-screen begin of block b1 with frame title text-010.
select-options: s_banfn for eban-banfn,                "PR No
                s_badat for eban-badat,                "PR Create Date
                s_ekgrp for eban-ekgrp,                "PR Purch Group
                s_frgkz for eban-frgkz,                "PR Rel Ind
                s_werks for eban-werks,                "PR Plant
                s_matnr for eban-matnr,                "PR Material
                s_lgort for eban-lgort.                "PR Stor Loc
selection-screen end of block b1.
selection-screen begin of block b2 with frame title text-020.
parameters:     prs01 radiobutton group prst default 'X',
                prs02 radiobutton group prst,
                prs03 radiobutton group prst.
selection-screen end of block b2.
selection-screen begin of block b3 with frame title text-030.
parameters:     pos01 radiobutton group post default 'X',
                pos02 radiobutton group post,
                pos03 radiobutton group post.
selection-screen end of block b3.
* INTERNAL TABLES
data: begin of ITAB occurs 0,   *(error: Tables with headers are no longer supported in the OO context.)*
            BANFN LIKE EBAN-BANFN,            "PR No
            BADAT LIKE EBAN-BADAT,            "PR Date
            MATNR LIKE EBAN-MATNR,            "Material No
            TXZ01 LIKE EBAN-TXZ01,            "Short Text
            LFDAT LIKE EBAN-LFDAT,            "Delv Date
            MENGE LIKE EBAN-MENGE,            "Requested Qty
            MEINS LIKE EBAN-MEINS,            "Unit of Measure
            PREIS LIKE EBAN-PREIS,            "Price Unit
            WAERS LIKE EBAN-WAERS,            "Currency
            AFNAM LIKE EBAN-AFNAM,            "Requistioner
            BNFPO LIKE EBAN-BNFPO,            "Item No
            BEDAT LIKE EBAN-BEDAT,            "PO Date
            BSART LIKE EBAN-BSART,            "Doc Type
            BSMNG LIKE EBAN-BSMNG,            "Ordered Qty
            MEIN2 LIKE EBAN-MEINS,            "PR UOM
            EBELN LIKE EBAN-EBELN,            "PO No
            EBELP LIKE EBAN-EBELP,            "PO Item No
            EKGRP LIKE EBAN-EKGRP,            "Purch Group
            EKORG LIKE EBAN-EKORG,            "Purch Org
            EMLIF LIKE EBAN-EMLIF,            "Vendor
            FRGDT LIKE EBAN-FRGDT,            "Release Date
            FRGGR LIKE EBAN-FRGGR,            "Release Grp
            FRGKZ LIKE EBAN-FRGKZ,            "Release Ind
            FRGZU LIKE EBAN-FRGZU,            "Release Stat
            INFNR LIKE EBAN-INFNR,            "Info Rec
            KNTTP LIKE EBAN-KNTTP,            "Acct Assgn Cat
            LGORT LIKE EBAN-LGORT,            "Storage Loc
            LOEKZ LIKE EBAN-LOEKZ,            "Deld Indicator
            GSFRG LIKE EBAN-GSFRG,            "Overall PR Rel
            STATU LIKE EBAN-STATU,            "Processing Stat
            WAER2 LIKE EBAN-WAERS,            "Currency
            WEBAZ LIKE EBAN-WEBAZ,            "GR Process Time in Days
            WERKS LIKE EBAN-WERKS,            "Plant
       end of ITAB.
data: prfnd(1) type c,
      pofnd(1) type c.
*top-of-page
top-of-page.
format color col_heading.
     write: /1 sy-repid, 150 'Allied Technologies (S) Pte Ltd',
            314 'Date:',
            320 sy-datum.
     write: /1 sy-uname,
            160 'PR Listing',
            314 'Time:',
            320 sy-uzeit.
     write: 330 'Page:', sy-pagno.
     uline.
     write : /1 'PR No', 11 'PR Date', 22 'Material', 42 'Short Text',
             65 'Deld Date', 84 'Qty Reqd', 95 'UOM', 103 'Price Unit',
             115 'Curr', 120 'Requisitioner', 134 'Itm No',
             141 'PO Date', 152 'DocType', 161 'Ord Qty', 175 'UOM',
             180 'PO No', 192 'Itm No', 200 'PurGrp',
             208 'PurOrg', 216 'Vendor', 228 'Rel Date',
             239 'RelGrp', 246 'RelInd', 254 'RelStat',
             263 'Info Record', 278 'AA Cat', 285 'Str Loc',
             295 'Deleted', 304 'Overall Rel', 316 'Procd Stat',
             328 'Curr', 334 'GR Time', 344 'Plant'.
uline.
skip.
end-of-selection.
perform get_data.
perform output_data.
*      Form get_data
form get_data.
clear itab.
select * from eban where banfn in s_banfn and   *(error: SELECT without an INTO clause is not supported in the OO context. Use "SELECT... INTO wa".)*
                           badat in s_badat and
                           frgkz in s_frgkz and
                           werks in s_werks and
                           matnr in s_matnr and
                           lgort in s_lgort and
                           ekgrp in s_ekgrp.
      move 'N' to prfnd.
    if prs01 = 'X' and eban-loekz = 'X'.
      move 'Y' to prfnd.
      perform get_porecord.
    endif.
    if prs02 = 'X' and eban-loekz ne 'X'.
       move 'Y' to prfnd.
       perform get_porecord.
    endif.
    if prs03 = 'X'.
       move 'Y' to prfnd.
       perform get_porecord.
    endif.
    if prfnd = 'Y' and pofnd = 'Y'.
        move-corresponding eban to itab.
        select single * from ekko where ebeln = eban-ebeln.    *(error: SELECT without an INTO clause is not supported in the OO context. Use "SELECT... INTO wa".)*
          if sy-subrc = 0.
            move ekko-lifnr to itab-emlif.
          endif.
        append itab.    *(error: An explicit work area is necessary in the OO context. Use " APPEND wa TO ITAB [SORTED BY])*
        clear itab.
    endif.
endselect.
endform.
form get_porecord.
      move 'N' to pofnd.
      if pos01 = 'X' and eban-statu ne 'B'.
         move 'Y' to pofnd.
      endif.
      if pos02 = 'X' and eban-statu = 'B'.
         move 'Y' to pofnd.
      endif.
      if pos03 = 'X'.
         move 'Y' to pofnd.
      endif.
endform.
* Output selected records to screen
form output_data.
sort itab by banfn badat matnr.
loop at itab.               *(error: At "LOOP AT ITAB", one of the additions "INTO", "ASSIGNING", or "TRANSPORTING NO FIELDS" is required. )*
    write: /1(10) itab-banfn, 11(10) itab-badat, 22(18) itab-matnr,
           42(20) itab-txz01, 65(10) itab-lfdat,
           78(15) itab-menge decimals 2,
           95(3) itab-meins, 100(14) itab-preis, 115(3) itab-waers,
          120(12) itab-afnam, 134(5) itab-bnfpo, 141(10) itab-bedat,
          152(4) itab-bsart, 158(15) itab-bsmng decimals 2,
          175(3) itab-mein2, 180(10) itab-ebeln, 192(5) itab-ebelp,
          200(3) itab-ekgrp, 208(4) itab-ekorg, 216(10) itab-emlif,
          228(10) itab-frgdt,
          240(2) itab-frggr, 248(1) itab-frgkz, 256(8) itab-frgzu,
          266(10) itab-infnr, 280(1) itab-knttp, 287(4) itab-lgort,
          298(1) itab-loekz, 308(1) itab-gsfrg, 320(1) itab-statu,
          329(5) itab-waers, 335(3) itab-webaz, 345(4) itab-werks.
endloop.
skip 1.
write: /25.
May i know how do i recode the areas with the errors?
Thank you for all the help i could get.

From this message ("error: Tables with headers are no longer supported in the OO context."), I'm thinking you are pasting this code inside a Class method. Do not.
But if you intend to make this as an individual report, it should work. Should it still show the same errors as "error: At "LOOP AT ITAB", one of the additions "INTO", "ASSIGNING", or "TRANSPORTING NO FIELDS" is required.", please add the TABLES statement at the top of your code.
(to show:)
report YPU0014 line-size 360 line-count 65 no standard page heading.
TABLES:
    itab
selection-screen begin of block b1 with frame title text-010.
Or better yet, see these changes
OLD
       data: begin of ITAB occurs 0,   *(error: Tables with headers are no longer supported in the OO context.)*
            BANFN LIKE EBAN-BANFN,            "PR No
            BADAT LIKE EBAN-BADAT,            "PR Date
            MATNR LIKE EBAN-MATNR,            "Material No
       end of ITAB.
NEW
       TYPES:
           begin of STAB,
            BANFN LIKE EBAN-BANFN,            "PR No
            BADAT LIKE EBAN-BADAT,            "PR Date
            MATNR LIKE EBAN-MATNR,            "Material No
          end of ITAB
       DATA:
         itab TYPE TABLE OF stab
As for the SELECT statements
OLD
    select * from eban where banfn in s_banfn and...
    " *(error: SELECT without an INTO clause is not supported in the OO context. Use "SELECT... INTO wa".)*
NEW
    DATA: wa_eban TYPE eban.
    select * from eban INTO wa_eban where banfn in s_banfn and...
    " and replace all uses of "eban" inside the select loop with wa_eban
   if prs01 = 'X' and wa_eban-loekz = 'X'.
    " DO THE SIMILAR THING WITH THE OTHER SELECT STATEMENTS
As for itab
OLD
loop at itab.
*(error: At "LOOP AT ITAB", one of the additions "INTO", "ASSIGNING", or "TRANSPORTING NO FIELDS" is required. )*
NEW
DATA: wa_tab LIKE LINE OF itab.
LOOP AT itab INTO wa_tab.
    " replace all occurences of tab with wa_tab inside the loop
   write: /1(10) wa_tab-banfn, 11(10) wa_tab-badat,...
ENDLOOP.
would really make me smile today
Edited by: Thomas Zloch on Jul 13, 2010 11:45 AM

Obsolete ABAP commands

Similar Messages

Maybe you are looking for