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

Similar Messages

Difference between SAP version 4.7EE and ECC 6.0.

Hi All,
Could you please tell me the major difference between SAP version 4.7EE and ECC 6.0? Also let me know why the industries should go for ECC 6.0?
Waiting for an early response from you.
Thanks a lot in advance!

http://solutionbrowser.erp.sap.fmpmedia.com/Default.aspx
Please use above mentioned link, you will find the delta functionalities between various SAP Versions.
Regards,
Ravi

Functional transactional difference between SAP version 4.7 and ECC 6.0

Hi Experts,
Can you Pls tell the Functional transactional difference between SAP version 4.7 and ECC 6.0 in case of Sales and Distribution module.
Like VA05n is one transactional difference,Pls tell the others?
Regards,
Rohan

Hi,
there are lot of changes like i observe
1, in rebates there is no advanced rebate processing in 4.7
2. there is no scale group field in condrecords of agrement in rebate agreement.
3. there are lot of new reports available in SIS
4. in sales returns process also seperate config available in 6.0
regards,
sk

SAP version 4.7 and ECC 5.0

HI Friends,
Could you plz help me out to know what are overall commonalities and differences and in view of SD module also in SAP R/3 Version 4.7 and ECC 5.0?
Thanks in advance.
Regards,
Vamsi P.

hi,
check this link http://solutionbrowser.erp.sap.fmpmedia.com/ u can get the delta here
saurabh

Italian tax reports - differences from SAP version 4.71 to 4.72

Hi,
Does anybody have the knowledge or documentation regarding the main differences between version 4.71 and version 4.72 from Insurance, regarding the Italian taxes report?
Thanks
Cristina

better to raise this issue to SAP itself otherwise wait for posts who comes across this issue.
Regards
Prabhu

Upgrade from SAP 4.7 EE to ECC 6 while working with CRM 4.0

Hi All,
Presently we are using R/3 version 4.7 EE with CRM 4.0 and now we are planning to upgrade R/3 4.7 to ECC.6.0. My question is, are there any problems working on CRM 4.0 with ECC 6.0 and what are the limitation we face when we work on CRM 4.0 with ECC 6.0 ?. Please provide some inputs on this ASAP.
Thanks in advance,
J M.

Hi,
There is no problem to work on CRM 4.0 with ECC 6.0.
I am using from long time CRM 4.0 with ECC6.0
BR,
Darshan..

Sales Order replication issue from SAP CRM (7.0) to ECC

Hi,
I have issue in replicating the sales order from CRM to ECC below are the issue details ...
Issue:
Sales Order is created in CRM and Mbdoc is generated with status:001 (Yellow state),Order is not replicated to ECC system.
I am trying to Replicate the sales Order1.Created Trnascation type: ZLS1 in CRM
2.Number range assigned as Internal in CRM and External number range in ECC
3.Item categories has been defined in Both the system.
4.SMOEAC settings are completed successfully.
5.Maintained table:SMOFPARSFAin both systems.
Checked Couple of things:
1.No items found in SMQ1 (Out bound queue ) in CRM
2.Checked in SMQS,none of the entries found.
Please let me know if i missed any of the settings to replicate the sales OrderPlease help us on this regards ASAP
Thnaks.
CRM Consultant.

>
Robert Kunstelj wrote:
> Check in status shema of that order that it doesn't block distribution to R3.
>
> Also check that you don't have any fillters set in R3AC1.
>
> And also tell me, do you see in SMW01 CSA mbdoc for that orders? If yes, are they in red state and when you select one and click on button Show bdoc message extended data, do you get structure or not?
>
> Regards.
Hello Robert,
Here is the answers for the questions raised...
1. I checked status schema ,understand distribution status is " To be distributed " in the sales order in CRM
2.In R3ac1 ,standard document "SALESDOCUMENT " doesn't have the any filter setttings related to my transaction type.
3.Mbdoc (Notification ) is generated in SMW01 with status " 001 " (Yello state),failed to reprocess the Bdocs.I coudn't able to find the Outbound queue in CRM for the corresponding order in CRM.
4.I can see the Bdoc structure in the extended data in SMW01.
Thanks.
Sathya.

Key functional differences between SAP ECC Version 6.0 and SAP Version 4.6

Hi Forum,
As we are currently updgqrading to SAP ECC Version 6.0 from SAP Version 4.6, could someone please identify what are the new functionalities are being offred in SAP ECC 6.0.
Please let me know or guide me in a right direction - my email address is [email protected] or simply reply to the forum.
Thank you
Yogesh

Dear Yogesh,
Please go through Upgrade info @ service.sap.com.
http://help.sap.com/saphelp_erp2005vp/helpdata/en/43/6880cbb88f297ee10000000a422035/frameset.htm
http://solutionbrowser.erp.sap.fmpmedia.com/
Major difference is ECC6 is netwear product having WASJAVA+ABAP
secondly support unicode apart from this we have other diff. you can get fom master guide from service.sap.com/instguides
For installing ECC 6.0 you required a solution manager key.With out solutionmanager key you cannot install ECC6.0.
For ECC 6.0 is called netweaver component here you have ABAP+JAVA stack.
ECC6.0 supports UNCODE.
For installing 4.6 you don't required solution manager key.It only having ABAP stack.
4.6C supports NONUNICODE.
Hope this would add some more info.
Regards,
Naveen.

Data types in SAP version 4.0

Hello
I have a requirement of copying a program from SAP version 4.7 to version 4.0.However String data type is not supported by version 4.0.
What are the data types in version 4.0.?
Is there any substitute of using sring data type in version 4.0 as I have to store a value
whose length can be even more than 500 characters.
Thanks and Regards

Check the links:
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/difference-between-the-sap-40b-and-sap-47-ver-567929
http://www.jt77.com/human/resources-23860.html
http://www.thespot4sap.com/Articles/SAP_Enterprise_4point7.pdf
Need advice/assistance with kernel upgrade planning
Reward if useful

Upgrading sap programs from one version to another version

Hi All,
I want to know how to upgrade sap programs from one version to another version,Please help me...
Regards,
Raj.

The seriousness and the complexity of the upgrade is primarily dependent on the version of the older SAP system. The Upgrade from 4.6 -> 4.7 is relatively easier and faster than that of an upgrade from 3.0 -> 4.7.
Most of the function modules in the older system have been reworked and would be marked as obsolete in the target version. (This could be seen in EPC Error Analysis & warnings).For example Function modules like Upload, Download, WS_Download, WS_Upload,WS_File_Delete, WS_Filename_get, Popup_to_confirm_step etc. These obsolete Fm's can be easily replaced with Fm's like Gui_Upload,Gui_Download, etc. There are few other complex Fms for which you have to do through R&D to find out the replacements.
Apart from replacing obsolete Fms one has to correct those syntax errors that may occur in the target version. There is a lot of variations in Syntax standards across versions.
Further more many transactions would have been reworked. Some Fields would be missing in the old system or a field would have been made a Key-Field in the new version , some screens would be missing or would have been addded. Also some Tables would have been flagged as obsolete and we need to find replacement for those obsolete Database tables.
It would be wise to do a R&D for all the programs in the system before Upgradation. This would really give us an idea about the complexity of the task and we can plan our Upgrade work effectively.
regards,
cartik

We have to upgrade from SAP 4.0 version to ECC6.0(only EDI/IDOC effects)

Hi All,
We have to upgrde a system from SAP 4.0 version to ERP6.0, is there any difference in EDI and IDOC
tables or their types in ERP6.0 from the 4.0 version, which we have to also consider or not.
but if differences are there but SAP itself is taking care for that, then how the sap is taking care of that ..?
Regards,
Rohit Sharma
Edited by: rohit sharma on Jun 19, 2008 1:26 PM

I´m not sure what you mean by "old table to new table".
The general table structure is not changed, VBAK + VBAP are still there. They may have been extended by additional fields, depending on how your system is implemented. It´s also possible, that if you activate any business function after the upgrade, that tables will get appends.
The old IDOC structures working before the upgrade should work after the upgrade the same way since those structures are not touched.
Markus

Need to transfer data records from one version of sap to another version of

hello,
i have a requirement where i need to transfer the tables with the records in it from sap r/3 4.7 version to sap ecc 6.0 version,now the present issue is how to tranfer the data records from old version to new version......kindly help me in this requirement

Hi,
Write a program in SAP 4.7 to download all records to a flat file. Then write a program in ECC6 to upload all records from the flat file...........
Thanks,
Aditya.

Distribute different versions of data to 3rd party systems from SAP ERP2004

Dear fellow SDN users
I am working in a large retail company where we are about to implement a new store system. The new system should be implemented in phases, where each phase covers one or multiple countries. Until the implementation is complete, our old store system should still be supported.
My problem is that we also need to support multiple versions of the systems, which is something we have never done before. Do any of you guys have any experience in how to differentiate versions of the data being sent from SAP to 3rd party systems? The scenario today is:
SAP ECC 6.0 -> SAP PI 7.0 -> STORE SYSTEM1
And the scenario we would like in the future:
SAP ECC 6.0 -> SAP PI 7.0 -> STORE SYSTEM1/STORE SYSTEM2
(Where it is possible to send several versions of data: e.g. ARTMAS ver. 1 to SYSTEM1 and ARTMAS ver. 2 to SYSTEM1 and ARTMAS ver. 1 to SYSTEM2)
The first thing that came to my mind was to differentiate on IDOC extension and then program different routines per extension when sending the idocs, but I guess there should be an easier way.
Any idea is greatly appreciated.
Best regards,
Chris

Hi Chris
I guess it depends on how the information you want to send to various partner systems differs, but have you considered using reduction?
I am at a client currently where we need to send similar information to a number of systems - for example Customer information using the DEBMAS message type, is going to three seperate systems.
To do this we defined 3 reduced messages - Tcode BD53. This not only reduces the load placed on PI/whatever middleware system is used by eliminating unnecessary data from each message variant, but allows the message to be treated differently by PI, using different data mappings, distribution models etc.
Hope this helps

Trouble importing keywords/photos from old version of iPhoto

I'm trying to import photos with their ratings & keywords from my old Mac that has iPhoto version 6.0.6. I copied the iPhoto folder from old Mac to Pictures folder in User on new Mac, then imported that folder from new iPhoto. It only imported a fraction of the photos and none of the keywords or ratings came with.
Help and suggestions are most appreciated!

There's no importing involved.
Simply copy the iPhoto Library from the Pictures Folder on the old Machine to the Pictures Folder on the new Machine.
Then launch iPhoto. That's it.
This moves photos, events, albums, books, keywords, slideshows and everything else.
You do not +import it to the new iPhoto+. You simply open the LIbrary with the new iPhoto and that updates it.
Regards
TD

SAP version difference from 4.0 to recent

Hello Friends,
I just want to know the difference between SAP versions 4.0, 4.7 & 5.0, please compare all with 4.0 version and post the reply.
Regards,
ninad kshirsagar

hi
Following are the basic differences as far as MM Module is concerned;
Pickup list - Batch where-used list display in transaction MB56
u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
Usability enhancements for transaction MIGO for the posting of goods movements
u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
u2022 User changes the default values in the menu path "Settings -> Default Values."
u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
Goods receipt
Goods issue
Transfer posting
Remove from storage
u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
New report : display list of invoice documents (MIR5)
u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
u2022 In the output list, the report shows both posted and held invoices.
u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
Requirement prioritizations in materials management
u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
Mass maintenance of outline agreements
The following two transactions available:
u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
Commitment plan for purchase contracts
u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
u2022 This commitment plan itself can have any number of items.
u2022 User can define a value and a validity date for each commitment plan item.
u2022 This enables user to pre plan different values for different periods of time.
u2022 The software generates an earmarked fund document for a defined commitment plan item.
u2022 This earmarked funds document can in turn contain several different items with different account assignments.
u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
u2022 Account assignment to a different account assignment object is then no longer allowed.
Availability check in "Enjoy purchase order and requisition"
u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
u2022 Two settings are possible with availability check:
Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
Delivery proposal - Full confirmation
External services: putting service items in the purchase order on hold (changed)
User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
Customizing transactions OX18 replaced by view
The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
Goods receipt: new movement types in inventory management
The following new movement types are available in inventory management:
107: Goods receipt to valuated goods receipt blocked stock
109: Goods receipt from valuated goods receipt blocked stock
Prepayment of invoices
This functionality is characterized as follows:
u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
u2022 When the software posts invoices, it continues to execute the standard checks.
u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
Purchasing accounting information to the former SAP Business Information Warehouse
u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
u2022 Functionality for report RMMR1MRS is enhanced.
u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
u2022 To do so, set the relevant indicator on the initial screen of the report.
Parking service items
It is now possible to put service orders without errors or with commitment errors on hold.
Report MB5B : Stock on Posting Date
u2022 This Report is available with "Non-Hierarchy" display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
u2022 This functionality is not available in Release 4.7.
Stock Transfer between Storage Locations
u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
u2022 As a result of which user can input issuing storage location with supplying plant.
u2022 Facility of using different delivery types for different issuing storage locations is available.
u2022 Shipping Point data can also be determined based on the issuing storage location.
Upgrading notes 4.6 to ECC6
http://www.sap.com/services/servuptech/bestpractices/index.epx
Solution Browser would give the differences (Features):
http://solutionbrowser.erp.sap.fmpmedia.com/ Give source and target versions.
Release Info:
ECC 6.0:
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
ECC 5.0:
http://help.sap.com/saphelp_erp2004/helpdata/en/c6/feda40ebccb533e10000000a155106/frameset.htm
You can find the difference in release notes of each SAP version.
Here are the links.
http://help.sap.com/saphelp_47x200/helpdata/en/fc/e3003deddfae4de10000000a114084/frameset.htm
http://help.sap.com/saphelp_scm50/helpdata/en/28/b34c40cc538437e10000000a155106/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
Regarding Upgradition From 4.6C to ECC6.0
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm

Obsolete Keywords from SAP version 4.6C to ECC 6.0

Similar Messages

Maybe you are looking for