Obsolete statements in ECC with respect to 4.5b

Hi Gurus,
This is really very urgent.i need an information on Obsolete Statements in ECC 6.0 with respect to 4.5B R/3 Version.please help me..
Full marks would be rewarded 100%
regards
Sahil

Hi
check the table PRGN_CORR2 which gives the list of transactions that were changed from different versions from 3.1G to 4.70 and also above versions
Pls check this
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
Reward if useful
Regards
Raghav T

Similar Messages

Obsolete statements in ecc and higher

can anybody tell me about the obsolete statements that are caught by transaction code uccheck(such as open data set,concordinate,translate)function modules ws_upload ws_download)

Hi,
Check these links,
Hope this helps,
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb33cc358411d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb3294358411d1829f0000e829fbfe/content.htm
Regards,
Pritha.
Reward points if helpful.

Key Differences in ECC 6.0 and 4.6C with respect to SAP SD Module

Dear All,
I would like to know the know the Key Differences in ECC 6.0 and 4.6C with respect to SAP SD Module. I have already gone throught the release notes and
upgrade erp in service.sap.com. I have also checked solution browser.
Its Urgent.
Regards,
Rakesh

Hi Rakesh,
Some of the differences are:
1. Document Flow
In ECC 6.0, The flow of sales documents is seen much better and improved as compared to 4.6C. Once You look at the screen, You will clearly figure out the difference.
2. Sales Order Look and Feel
There are more tabs in ECC 6.0 for Item Level Details.
The Sales Doc. appears as supremely perfect.
3. ECC 6.0 is built on NetWeaver Technology (that possess SOA i.e. service oriented architecture) , Hence more reliable and Improved as compared to previous one.
Hope this will help you. Reward if found useful
Regards,
Gaurav Raghav

REG: Obsolete statements in SLIN ecc 5.0

Hi all,
When i am executing the ABAP EPC for obsolete statements.(with Also display Hidden Messages)
I get the 2 Obsolete statements and as following :
 Program: ZXXXXX Row: 652
The current ABAP command is obsolete and problematic, especially so in ABAP
Objects
An explicit work area is necessary in the OO context. Use "APPEND wa TO S_WERKS
[SORTED BY]".
(The message can be hidden with "#EC *)
Program: ZXXXXX Row: 2558
The current ABAP command is obsolete and problematic, especially so in ABAP
Objects
At "LOOP AT itab", one of the additions "INTO", "ASSIGNING", or "TRANSPORTING NO
FIELDS" is required. in the OO context.
(The message can be hidden with "#EC *)
Though i put the "#EC after above variable still i can see it in the SLIN overview.
Pls help me to hide these Obsolete statements.
Thanks and Regards
Srikanth.P

Lest you find yourself labelled as "out of date" or "obsolete", perhaps you could spend a little time to bring your coding practices up to the state of the product. A LOT of things used in ABAP within my 12 years are now obsolete. For instance, the "Official ABAP Programming Guidelines" by SAP Press, written by Drs. Thummel and Keller, describes FORM....ENDFORM and REFRESH as obsolete.
In current versions, we loop at ...assgining <Field-symbol> or into structure....
We do read table into structure or assigning <field-symbol> or (where possible) transporting no fields.
We don't have tables with header rows, since those can't be used in OO.
We don't use REFRESH, we use CLEAR tabname[].
In OO, we use the SoC, software layering concepts, with GUI, Application and Persistence level Class definitions and implementations.
We used class-based exception handling where possible to avoid abends which are, of course, detrimental to our users' experiences.
etc.

PROBELM WITH TYPE X VALUE '20' IN CONCATENATE STATEMENT in ECC version

Hi EXPERTS,
 I am working in ECC 6.0 version.
 PROBELM WITH TYPE X VALUE '20' IN CONCATENATE STATEMENT in ECC version
 C_DEL TYPE X VALUE '09' having solution --C_DEL TYPE C VALUE CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB,
 If C_DEL TYPE X VALUE '20' what was the solution in ECC version.
 Please let me know. I am awaiting for ur answers
<REMOVED BY MODERATOR>
Message was edited by:
 Alvaro Tejada Galindo

Hi
welcome to SDN forum
move that X field to a char field and use in concatenation
CONCATENATE works only with CHAR fields
Regards
Anji

Stock Uploading with respect to Old Material Number of Legacy System

Hi Experts,
Need Your valuable Inputs,
As we are Going Go-Live in ECC6.0
As we have already Uploaded Material Master with the New Material Number (Internal Number Range generated by system ) Material Type, Valuation Class and Moving average indicator and related Fields in Material Master in ECC 6.0.with respect to old material number of Legacy system,
Now we need to Upload the Stocks and Values with respect to Old Material Number by Using 561 Movement Type in the New system of ECC 6.0 , This New material number and old material number Stock and its Values should match in the New ECC 6.0 .
As from the Old Legacy system we have only Old Material Number, Description and its stock, Value, How can we Upload the Stock with respect to Old Material Number ?
Kindly assist your Inputs.
Best Regards
Javeed Ahamed

you have to have a mapping from old number to new number.
you can either do it already in your source or you find the number in SAP itself with an ABAP command.
Usually the old material number is stored in field MARA-BISMT
if you want add the number in the source, assuming its Excel, then you you can download via SE16 from MARA just 2 fields: MATNR and BISMT. in Excel you can then use the formula VLOOKUP to get the MATNR by looking it up with old number.
if you are a little familiar with ABAP, and you load stocks by using LSMW, then you can easily get the new material number by adding an ABAP statement to find a material number by old number
select single MATNR from mara into wa_MATNR
where BISMT = oldmaterial.

Replacement of SEARCH ITAB statement in ECC 6.0

Hello Experts,
Can anybody tell me, which statement i can use to replace an obsolete statement i.e. SEARCH ITAB in ECC 6.0?
Thanks in advance!!
Best Regards,
Bhupinder

Hello,
While using FIND statement, i am getting bellow syntax error
As line type of the table "ITAB" in the CHAR MODE a indication-like and/or in the BYTE MODE a byte-like field was expected.
My statement is
FIND FIRST OCCURRENCE OF 'WHERE'
IN TABLE ITAB
What should i do to resolve this sytax error?
Best Regards,
Bhupinder

Basic questions with respect to ABAP WebDynpro Application

Hi All,
I have two basic questions with respect to an ABAP WebDynpro application :
a) If an ABAP WebDynpro application has been developed, how could it be made available to the end user?
b) Can an ABAP WebDynpro application be developed in ECC or is it only applicable for version 4.6c?
Thanks & Regards,
Sushanth Hulkod

Sushanth Hulkod wrote:
> a) If an ABAP WebDynpro application has been developed, how could it be made available to the end user?
>
> b) Can an ABAP WebDynpro application be developed in ECC or is it only applicable for version 4.6c?
a) If an ABAP WebDynpro application has been developed, how could it be made available to the end user?
Answer - By providing direct link of the WD application created in SE80, creating iView for webdynpro abap application in the portal environment and NWBC environment
b) Can an ABAP WebDynpro application be developed in ECC or is it only applicable for version 4.6c?
Answer - Yes it can be developed in ECC. Webdynpro ABAP is introduced in NW 2004s (SAP NetWeaver 7.0 or ECC 6.0)
Thanks,
Chandra

Better replacement for Obsolete statement

Hi ,
During upgradation to ECC 6.0 , at many places in order to correct the Unicode error we need to use the Move statement. Since the Move-Corresponding is an obsolete statement now , so we can't use it any more. It is very difficult and highly time consuming to move huge structures and internal tables field by field . Is there any alternative to this ?

Move-Corresponding is an obsolete statement now
Who said ????
at many places in order to correct the Unicode error we need to use the Move statement
What type of error ?

PNPCE - Obsolete Statements

Hi,
I am using PNPCE logical data base in my prog.
For this I defined the following.
Nodes: Peras.
Tables: Pernr.
Infotypes: 0002.
Is it mandatory to use Tables: Pernr. (Without this selection-screen is not coming)?
Also the statement Infotypes is Obsolete. Any alternate for this?
This statement creates infotype internal tables with header line which is not supported in OO context.
So what is the alternate for this?
Still lot of obsolete statements are shown in extended check even if I use PNPCE.
How to replace them?

hi read this ..will use ful for you.......
Purpose
The PNPCE logical database supports the evaluation of HR master data. It includes the functions of the PNP logical database and offers additional evaluation options. Therefore, you should use the PNPCE logical database instead of the PNP logical database for all new developments.
The enhanced functionality of PNPCE in comparison to PNP essentially concerns the evaluation of Concurrent Employment, that is the possibility to group evaluate several assignments/personnel numbers of a person. The new events 'GET PERSON' and 'GET GROUP' as well as an enhanced syntax for the INFOTYPES statement (addition AS PERSON TABLE) for the procurement of infotype data enable you to use the new functionality. The use of these new functions is optional. You can run a PNPCE report that does not use the new events and the addition for the INFOTYPES statement in a PNP-compatible session. Since the PNPCE also has an improved selection screen, each report benefits from this even if the report does not use the functions for evaluating Concurrent Employment.
Prerequisites
A report that wants to use the PNPCE must enter this in its report attributes under Logical database.
In addition, the PERNR structure must be declared in the report using the 'TABLES PERNR' statement. You can only use the PERNR structure again in certain circumstances. The use of the 'GET PERNR' event is therefore forbidden. Instead, use the 'GET PERAS' event. Except for the PERNR-PERNR component, all other components of the PERNR structure are no longer filled and have initial values. This kind of programming (with the exception of PERNR-PERNR) therefore not permitted.
In addition to the 'GET PERAS' event, you can also use the GET PERSON' and 'GET GROUP' events. To be able to use these events, you must declare them using the NODES statement (NODES PERSON', 'NODES GROUP', or. NODES PERAS').
Explanation of Terms
If the 'GET PERSON' and 'GET GROUP events and the 'AS PERSON TABLE' addition for the INFOTYPES statement are not used, the report indicates that it does not require the functionality for evaluating Concurrent Employment. In this case, the report runs in a PNP-compatible session. This is referred to as PNP mode in the following documentation. On the other hand, if the report uses the functionality for evaluating Concurrent Employment we refer to CE mode.
Features
Process of an Evaluation
The PNPCE selection screen offers you as standard a range of functions that you can use to restrict the personnel number and person selection. These are discussed in more detail in the following sections. The process is initially as follows regardless of whether the report runs in CE or PNP mode. All available functions and selection conditions leads to the selection of personnel numbers. If you use the sorting function, this set of personnel numbers is then sorted according to the sort criteria you selected. In PNP mode, the GET PERAS event is triggered as a result for each personnel number.
In CE mode, the persons belonging to the personnel numbers are determined first for all personnel numbers selected. The GET PERSON event is then triggered for each person. The person ID is specified in the OBJID component of the PERSON structure. PERNR_NUM contains the total number of personnel assignments (= personnel numbers) that this person has and the ALL_PERNRS table, which contains a list of these personnel numbers regardless of whether they were actually selected or not. The SELECTED flag is set to X for the personnel numbers selected. The flag is initial for all personnel numbers that are not selected. The PROCESS flag specifies whether the personnel number should be processed in the rest of the process. This flag is set to X by default for the personnel numbers selected. However, the report can set or delete this flag at the GET PERSON event for all personnel numbers. In this way, report and logical database communicate with each other which enables the report to control the rest of the process.
In the next step, the logical database groups all personnel numbers of a person that are to be processed (that is, all personnel numbers that have the PROCESS flag set). The report can control the type of grouping using the PNPCE_GROUPING_FROM_PAYROLL flag (normal or payroll grouping) and using the PNPGPRSN (grouping reason) and PNPGPVAL (grouping value) parameters of the selection screen. The GET GROUP event is triggered for each group of personnel numbers determined. The GROUPING_REASON and GROUPING_VALUE components contain the grouping reason and grouping value of this group. The number of personnel numbers that belong to this group and that are processed subsequently is in PERNR_NUM. The included ALL_PERNR table contains a list of these personnel numbers with additional information. The SELECTED flag specifies whether the current personnel number was originally selected (flag is set) or was marked by the report as to be processed. GROUPING_BEGDA and GROUPING_ENDDA contain the validity period that the personnel number has for this grouping. The NO_AUTHORITY flag is set if there is insufficient authorization for a personnel number. This personnel number is not processed further. The SORT component defines a standard sort order for the personnel numbers of a group. The report can change this by overwriting the values. In this way, report and logical database communicate with each other, which controls the further processing sequence of the personnel numbers.
The GET PERAS event is then triggered for all personnel numbers of the group (with the exception of the personnel numbers for which no authorization exists) in the sequence defined by the SORT component (see above). The SELECTED, GROUPING_BEGDA, and GROUPING_ENDDA components have the same meaning here as with the GET GROUP event. The PROCESSED_BEFORE flag specifies whether the personnel number has already been processed once before (it is possible that the personnel number belongs to several groupings and has been therefore been processed several times).

Freight condition type-With respect to kilometer

Hi,
I am working on freight related condition type,my requirement is we have to calculate freight cost based on kilometer or miles.But for us the standard condition type is KF00 which is with respect to Gross Weight.
Is there any condition type which calculates Freight based on miles/kilometer covered.If so kindly throw some ideas on it.
My doubt is do we require transportation management.
Pradeep

Hi Pradeep,
without transport management, maybe you need a different approach of calculating freight.
instead of calculating price per Km/Mile by distance, apply cost based on origin - destination of you sold-to and ship-to.
You know Price per km/Mile. You can ask distance between origin and destination points and calculate freight cost then.
The important point here is to determine the different origins and destinations, refine, group, regroup to end in something that may look like:
Origin: country-state-region-city-zip code... (and even sold-to)
Destination: country-state-region-city-zip code ... (and even ship-to)
Freigth cost: (unit cost x distance)
Once you´ve mapped this in an Excel file, you can think of creating a price condition for your freight costs in SAP based on your mapping.
Regards,
JM

Backend price update with respect to plant

Hi SRM Guru's
Is it possible to update backend price for the material with respect to Plant.
We are in Classic scenario.
Currently Report EBP_GET_BACKEND_PRICES updating price for a material average of all plants from ECC to SRM.
But we need the price for the material to be updated plant wise.
Is it Possible.
Thanks
With Regards
Sri.
Edited by: sri ram on Mar 26, 2009 8:52 AM
Edited by: sri ram on Mar 26, 2009 11:22 AM

HI
first of all you need to make the plant as the valuation area in the ecc and do the delte download for the material master update through CRM parameters. here you must be very care full about the system. you need to seleted the delta down in the srm crm paratmeter not initial down load.
in the delta down load the system will update the current setting in the ecc for the materil. then you will get the exact price for the material what you have sent for the plant.
Regards
Satish

Obsolete statements

Hi,
I am the beginner of ABAP Programming.I want to know the detail description of the Obsolete statements(Like 46c to ECC6.0) with examples.
(For Example:In 46c Ranges but Ecc6.0 Type/Like range of ).
Thanks
Chandramohan.

- Look at sap documentation, in [ABAP Statements - Overview |http://help.sap.com/abapdocu_70/en/ABENABAP_STATEMENTS_OVERVIEW.htm] look for [Obsolete Statements |http://help.sap.com/abapdocu_70/en/ABENABAP_OBSOLETE.htm]
- Search at sdn, there are many threads and some wikis like [Obsolete FM and Statement replacements|http://wiki.sdn.sap.com/wiki/display/ABAP/ObsoleteFMandStatementreplacements]
Regards,
Raymond

Hi removing the obsolete statements.....

Hi all
when i am running the EPC i am gettting obsolete statements for these statements
here is the code where it was showing the obsolete status
can any body help me in correcting this:
FORM alv_init_report_events TABLES ot_events TYPE slis_t_event.
CLEAR ot_events.
REFRESH ot_events.
ot_events-name = slis_ev_user_command.
ot_events-form = 'USER_COMMAND'.
APPEND ot_events.
ot_events-name = slis_ev_pf_status_set.
ot_events-form = ''. "'PF_STATUS_SET'.
APPEND ot_events.
ot_events-name = slis_ev_top_of_list.
ot_events-form = 'TOP_OF_LIST'.
APPEND ot_events.
ot_events-name = slis_ev_end_of_list.
ot_events-form = 'END_OF_LIST'.
APPEND ot_events.
ot_events-name = slis_ev_top_of_page.
ot_events-form = 'TOP_OF_PAGE'.
APPEND ot_events.
ot_events-name = slis_ev_end_of_page.
ot_events-form = 'END_OF_PAGE'.
APPEND ot_events.
ot_events-name = slis_ev_foreign_top_of_page.
ot_events-form = ''.
APPEND ot_events.
ot_events-name = slis_ev_foreign_end_of_page.
ot_events-form = ''.
APPEND ot_events.
ot_events-name = slis_ev_top_of_coverpage.
ot_events-form = ''.
APPEND ot_events.
ot_events-name = slis_ev_end_of_coverpage.
ot_events-form = ''.
APPEND ot_events.
ot_events-name = slis_ev_before_line_output.
ot_events-form = 'BEFORE_LINE_OUTPUT'.
APPEND ot_events.
ot_events-name = slis_ev_after_line_output.
ot_events-form = ''.
APPEND ot_events.
ot_events-name = slis_ev_caller_exit_at_start.
ot_events-form = ''.
APPEND ot_events.
ot_events-name = slis_ev_list_modify.
ot_events-form = ''.
APPEND ot_events.
ot_events-name = slis_ev_subtotal_text.
ot_events-form = ''.
APPEND ot_events.
ENDFORM. "ALV_INIT_REPORT_EVENTS
i am getting this error
The current ABAP command is obsolete and problematic, especially so in ABAP
Objects
An explicit work area is necessary in the OO context. Use "APPEND wa TO OT_EVENTS
[SORTED BY]".
(The message can be hidden with "#EC *)
 Program: ZF_NOTA_FISCAL_REPORT_BRZL Row: 1242
The current ABAP command is obsolete and problematic, especially so in ABAP
Objects
An explicit work area is necessary in the OO context. Use "APPEND wa TO OT_EVENTS
[SORTED BY]".
(The message can be hidden with "#EC *)

Hi,
declare ot_events as below
Data: ot_event type table of slis_alv_event,
 wa_event type slis_alv_event.
CLEAR wa_events.
REFRESH wa_events.
wa_events-name = slis_ev_user_command.
wa_events-form = 'USER_COMMAND'.
APPEND wa_events to ot_events.
Reward Points if this helps,
Satish

Inner join and select for all entries with respect to performance

Hi Friends,
I just want to know which is more efficient with respect to performance the Inner join or select for all entries?which is more efficient? and how? can you explain me in detail ?
Regards,
Dinesh

INNER JOIN->
The data that can be selected with a view depends primarily on whether the view implements an inner join or an outer join. With an inner join, you only get the records of the cross-product for which there is an entry in all tables used in the view. With an outer join, records are also selected for which there is no entry in some of the tables used in the view.
http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ec77446011d189700000e8322d00/content.htm
FOR ALL ENTRIES->
Outer join can be created using this addition to the where clause in a select statement. It speeds up the performance tremendously, but the cons of using this variation are listed below
Duplicates are automatically removed from the resulting data set. Hence care should be taken that the unique key of the detail line items should be given in the select statement.
If the table on which the For All Entries IN clause is based is empty, all rows are selected into the destination table. Hence it is advisable to check before-hand that the first table is not empty.
If the table on which the For All Entries IN clause is based is very large, the performance will go down instead of improving. Hence attempt should be made to keep the table size to a moderate level.
Not Recommended
Loop at int_cntry.
Select single * from zfligh into int_fligh
where cntry = int_cntry-cntry.
Append int_fligh.
Endloop.
Recommended
Select * from zfligh appending table int_fligh
For all entries in int_cntry
Where cntry = int_cntry-cntry.

Obsolete statements in ECC with respect to 4.5b

Similar Messages

Maybe you are looking for