"WS_QUERY" is obsolete in ECC 6.0

Hi Guys
Which is the correct Function module in ECC 6.0 is related to "WS_QUERY"
Thanks,
Gourisankar.

Refer to this thread in sdn
CALL FUNCTION 'WS_QUERY'
or refer
Use the appropriate module from the function group SFES.
The appropriate function modules from funciton group SFES.
GUI_GET_DESKTOP_INFO
GUI_GET_FILE_INFO
GUI_EXEC
GUI_RUN etc
The Equivalent Function Module for in ABAP 4.7 is
WS_QUERY-File Exist is CL_GUI_FRONTEND_SERVICES=>FILE_EXIST , or ,
WS_QUERY-Directory Exist is CL_GUI_FRONTEND_SERVICES=>DIRECTORY_EXIST.
Reward if useful.

Similar Messages

'FM HELPSCREEN_CREATE is obsolete in ECC 5.0 version'

Hi all,
I am upgrading SAP from 3.1I to ECC 5.0. I am getting the error that 'FM HELPSCREEN_CREATE is now obsolete in ECC 5.0 version'.
can anyone suggest the equivalent FM for the above in ECC 5.0.
thanks
Rakesh

Hi Rakesh,
Im using ECC 5.0 version, it is not telling this FM HELPSCREEN_CREATE is obselete.
Regards,
Senthil

This Funtion POSTING_INTERFACE_START is Obsolete in ECC 6.0

Hi,
Someone know if this function is obsolete in ECC 6.0
Wait you help.
Thanks

No, it's still used, but it's not released for direct customer use either...

ACCMAP: Obsolete in ECC.. Any other wayout possible??

Hey Guys
A. Prior to ECC version, say, in 4.7 - There used to be a T code ACCMAP.. Here in, my client did as below
Company code 2030
Dep Area 01: Book dep Area
Dep Area 20: Parallel dep area
Dep Area 55: Delta Dep Area..
Company code 9030
Due to ACCMAP settings, when AFAB is run in 2030, it posts the Dep Area of 01 + Dep Area of 55 to Company code 9030 in Spl Purpose Ledger
B. Our client has just upgraded to ECC 6.0 and still not using New GL...
C. Now in ECC, the ACCMAP is no longer availalbe as SAP says you can map Dep Area to parallel ledger... But our requirement is to map Dep Area 55 of 2030 to Dep Area 01 of 9010 company code
Is this no longer possible in Standard SAP?
Do we have any other way of doing this?? (Since the comp code 9010 not only manages the asset related postings but also many other postings, it will be very difficult to migrate from using a New Company code to using a Parallel Ledger in same company code)
br, Ajay M

Hi Ajay,
I can provide you some background information regarding ACCMAP that may help for better understanding:
Why is ACCMAP (concept of the accounting principle) obsolete in ECC 6.0. and why it is no longer needed? It was used in previous releases to "filter" which values and from what depr.area should go to the special ledger. In this way, let´s say, you linked the depreciation area to the accounting principle and this to the special ledger in order for the information to flow from the specific area to the specific "special ledger".
This logic has changed. Now you link the depreciation area to the parallel ledger directly in OADB (no need of accounting principle).
The parallel ledger solution is, in fact, a development of the special ledger concept.
I strongly advise you check SAP's online documentation in the SAP library under:
Asset Accounting (FI-AA) > Integration > Parallel Ledgers in Asset
Accounting.
Regards,
Brigitte

Ws_query function module obsolete in ECC 6.0

HI experts,
   V r upgrading system from 4.6 to ecc 6.0 . In one of the programs FM ws_query is obsole, pls let me know the replacement of it.
form process_selections_filen.
call function 'WS_QUERY'
       exporting
            filename = p_filen
            query    = 'FE'
       importing
            return   = g_subrc
       exceptions
            others   = 1.
check syst-subrc ne 0 or g_subrc ne 1.
message e000(zz) with p_filen text-e01.
endform.

You must OO ABAP.
You can use a method of CL_GUI_FRONTEND_SERVICES class to do the same process. This is the new class for handling files.

REJECT statment to break GET event is Obsolete in ECC 6.0 - Alternative?

Hi Developers,
REJECT statment is used to break from GET event (say GET PERNR event in Logical Database) used to process for an Employee.
This REJECT statement is Obsolete . Is there any alternative for this ?
If so, please reply at the earliest as it is very Urgent.
Regards,

Hi Suma,
The REJECT statement was specially developed for leaving GET event blocks. Unlike CHECK and EXIT, REJECT always refers to the current GET event block. If CHECK and EXIT occur in a loop, they refer to the loop, and in a subroutine, they always refer to the subroutine. The REJECT statement, on the other hand, allows you to exit a GET event block directly from a loop or a called subroutine.
The statement
REJECT [dbtab].
always terminates the processing of the current line of the node of the logical database. Without the optional dbtabspecification, the logical database automatically reads the next line of the same node, and the next GET event at the same hierarchy level is triggered. If you use the optional dbtab specification, the logical database reads the next line of the node dbtab. The node dbtab must occur above the current node in the logical database hierarchy.
Example
The following executable program is connected to the logical database F1S.
REPORT EVENT_DEMO.
NODES: SPFLI, SFLIGHT, SBOOK.
GET SFLIGHT.
SKIP.
WRITE: / 'Carrid:', SFLIGHT-CARRID,
'Connid:', SFLIGHT-CONNID,
'Fldate:', SFLIGHT-FLDATE.
ULINE.
GET SBOOK.
PERFORM SUB.
FORM SUB.
WRITE: / 'Bookid:', SBOOK-BOOKID.
REJECT 'SFLIGHT'.
ENDFORM.
This program reads and displays only the first booking for each flight, since the logical database reads the next line of SFLIGHT after the REJECT statement.

WS_EXCEL is Obsolete in ECC 6.0

Hi Guys,
Could you plese suggest me, which is similar function module in ECC 6.0.
Thanks,
Gourisankar.

Hi Gourisankar,
We have created a ZWS_EXCEL containing GUI_DOWNLOAD + CL_GUI_FRONTEND_SERVICES=>EXECUTE for opening Excel
CALL FUNCTION 'GUI_DOWNLOAD'
    EXPORTING
      FILENAME                = TMP_NAME            "'EXCEL.DAT'
      FILETYPE                = 'DAT'
    TABLES
      DATA_TAB                = DATA
    EXCEPTIONS
      FILE_WRITE_ERROR        = 1
      NO_BATCH                = 2
      GUI_REFUSE_FILETRANSFER = 3
      INVALID_TYPE            = 4
      NO_AUTHORITY            = 5
      UNKNOWN_ERROR           = 6.
and
CALL METHOD CL_GUI_FRONTEND_SERVICES=>EXECUTE
    EXPORTING
      DOCUMENT    = TMP_NAME          "'EXCEL.XLS'
     APPLICATION = 'EXCEL'
*    PARAMETER =
      OPERATION   = 'OPEN'.

REJECT is obsolete in ECC 6.0 - Any Alternative?

Hi Developers,
REJECT statment is used to break from GET event (say GET PERNR event in Logical Database) used to process for an Employee.
This REJECT statement is Obsolete . Is there any alternative for this ?
If so, please reply at the earliest as it is very Urgent.
Regards,

Use check statement.
Demo is as follows -
constants: c_1(1) type c value '1' .
Start-of-selection.
get pernr.
Read Infotype 0
rp-provide-from-last p0000 space pn-begda pn-endda.
check pnp-sw-found eq c_1. "it will check if record is there,if not it will go to next pernr

SAPWL_STATREC_READ_FILE Obsolete in ECC 6.0

Hi All,
We are working with upgrade from 4.5 b to ecc 6.0.
SAPWL_STATREC_READ_FILE
TABLE_DECOMPRESS
HELP_VALUES_GET_EXTEND
Above Function modules are absolte.Please specift the corresponding funciton modules of ECC 6.0.
Thanks in Advance
Regards,
Padmaja.

There are several functions that will get the statistics records in NetWeaver. Browse the function modules looking for SAPWL_* or SWNC_*
One FM that is close to what you were using SAPWL_STATREC_READ_REMOTE. This gets the recs for the current instance.
SWNC_GET_STATRECS_FRAME will get you records for all instances in a system. And the subrecords are nested under the main so you don't have to mess with the index map.
Tim

Are Business Areas obsolete with ECC 6.0 and the new GL?

I have long heard that SAP is not planning on supporting Business Areas long term. Howver in the help documenation they still have them listed.
One solution offered to remove them is: With the advent of new GL in ECC; the field profit center and the PCA ledger is now an integral part of new gl (FAGLFLEX). profit center and other custom fields can now easily be defined as a zero balance entity - which means it works exactly in similar fashion as BA use to work. In addition, you can mantain a PCA hierarchy and it is an attribute that appears on key objects in SAP i.e. material master, production order, purchase order etc.
However, for customers that are using both BA's and PC's already (for example using BA's to represent plant groupings and PC's along product lines) is there a real need to make a change and remove the BA's from the current system to avoid future problems?

Hi,
The answer is most probably Yes. However, those who are having business area and those who like the concept can continue. New GL has revolutionised the segmental concept which is very much needed for the day to day running of business and to meet the accounting standards which are becoming more rigid due to the prevalance of fraud across the world.
Trust this helps much!
Cheers!

Table Parameters are obsolete in ECC 6.0

hello All,
I have created a function module in ECC6.0 and I need an internal table as a parameter but SAP will not allow it to be created as a tables parameter only as a changing parameter. How do you do this as a changing parameter. I am using structure type MMPUR_TEXTLINES.
Thanks

Use tables tab instead of changing.
then use
MMPUR_TEXTLINES LIKE MMPUR_T_TEXTLINES
a®

Repalcing Obsolete command STOP in ECC 6.0

Hello all,
I am working on the upgrade from 4.6 to ECC 6.0.
Can any one of you tellme the replacement for the command STOP in ECC 6.0 as it is obsolete in ECC 6.0.
<REMOVED BY MODERATOR - REQUEST OR OFFER POINTS ARE FORBIDDEN>
Regards,
Arun
Edited by: Alvaro Tejada Galindo on Jan 8, 2009 4:34 PM

hi,,,,,,,,,,,,
too dont remember the exact solution for this.......one i have found it ...just check whether this will work or not!!
Replace the STOP statement with the statement LEAVE TO SCREEN SY-DYNNR if the STOP statement is within a steploop.
Execute the program in previous version and replace the STOP statement with an appropriate LEAVE TO SCREEN statement.
<REMOVED BY MODERATOR - REQUEST OR OFFER POINTS ARE FORBIDDEN>
cheers,
rekha
Edited by: Alvaro Tejada Galindo on Jan 8, 2009 4:35 PM

Obsolete Transactions in ECC 6.0

Dear All,
How to find what are the Transactions are obsolete in ECC 6.0 ?
Note:PRGN_CORR2 Table doesn't contains all Transaction Details. and RODIR table contains only obsolete Function Module names.
Thanks in Advance.
Kanagaraja L

Hi,
check here
https://wiki.sdn.sap.com/wiki/display/ERP6/TransactionsChangedinECC6.0
OR
check release notes for ERP 6 at http://service.sap.com/releasenotes.
Regards,
Amit

WS_FILENAME_GET is obsolete function module in ECC 6.0

Hi Guys,
The function module "WS_FILENAME_GET" was obsolete in ECC 6.0, could you please suggest me which is relevant function module in ECC 6.0.
Thanks,
Gourisankar.

Hello,
Take a look at class CL_GUI_FRONTEND_SERVICES.
Regards,
John.

Obsolete function module in ECC 6.0 - BAPI_COSTESTIMATE_CREATE_SPLIT

Hi Guys,
The above function module obsoleted in ECC 6.0, I need related function module in ECC 6.0.
Could you please suggest me, which is the related function module in ECC 6.0?
Please take a high priority. Advance thanks guys.
Thanks,
Gourisankar.

Hello,
Take a look at class CL_GUI_FRONTEND_SERVICES.
Regards,
John.

"WS_QUERY" is obsolete in ECC 6.0

Similar Messages

Maybe you are looking for