Difference between ECC 6.0 vs 4.7EE - SAP FI / SD / MM / ABAP (Functional & Technical)

ECC means Enterprise Central component.

SAP R/3 4.7 is based on the 3-tier architecture. SAP is continuously upgrading the software, which is called as release versions for example SAP R/3 4.6C, SAP 4.7....

 

Now SAP evolved into using the Internet technology and is called as service oriented architecture (SOA). There are lots of functionalities available in ECC 5.0 and ECC 6.0 compared to R/3 in integrating with other systems. Probably to understand the specific release dependent changes, you can go thro the help documentation. For example to understand the diff between ECC 6.0 and ECC 5.0 please go thro the link:

 

Release Notes for SAP ERP Central Component (English) – Click here

 

Some of the differences in SD Module 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 Net Weaver Technology (that possess SOA i.e. service oriented architecture), Hence more reliable and improved as compared to previous one.

Release Notes for SAP ERP Central Component (English) – Click here

 

Some of the differences ABAP Module side:

 

1. For installing ECC 6.0 you required a solution manager key. With out solution manager key you cannot install ECC6.0.
2. ECC 6.0 is called net weaver component here you have ABAP+JAVA stack & for installing 4.6 you don't require solution manager key. It only having ABAP stack.
3. ECC6.0 supports UNCODE & 4.6C supports NONUNICODE.
4. Major difference is ECC6 is net weaver product having WASJAVA+ABAP - secondly support Unicode apart from this we have other diff. you can get from master guide from service.sap.com/instguides.

5.      In terms of ABAP some function modules are obsolete in 4.7. e.g. WS_UPLOAD, WS_DOWNLOAD etc. You can find the list of obsolete FMs in the table RODIR. These need to be replaced in the ECC System.

6.      Also ECC is very strict in case of EPC Errors. You need to check the EPC and remove the call function interface errors where it says SLIN observes catching of a runtime error. These might work with no issues in 4.7 but will short dump in ECC.

7.      If you are doing to a Unicode conversion also. You need to check the transaction UCCHECK for Unicode errors. You also need to replace obsolete statements like >< and => , =< etc.

8.      If you want to know more ABAP changes go to transaction ABAPDOCU and there is a node ABAP Changes by Release. You can see more ABAP Changes version by version here.

9.      ECC is more towards OOPS concepts, ECC is very developer friendly

10.   It has new debugger.

11.   New Enhancement Framework is introduced in ECC.

12.   It is more efficient to use Adobe forms in ECC.

13.   5.0 ECC - Build in Net Weaver Platform & 6.0 ECC - Build in Net Weaver Platform with Solution Manager

14.   ECC has new options in BADIs where you can create your own badis and implement it.

15.   You have new concept called Implicit and explicit source code plugins in ECC.

16.   Has webdynrpo component accessible from SE80 transaction Itself.

 

Some of the differences FI Module side:

 

 

1.      ECC 6.0 enables Business area posting - Segment reporting made easy.

2.      Profit center accounting is through new GL.

3.      Document splitting: Split of entry to post assets and liabilities to respective profit centers. (Balance sheet items)

4.      Enables commitment of FM, improved CRM feature & Mobile sales feature

Here are the list of Transactions not their in ECC 6.0

QAS1 Download Insp. Specs. (Obsolete)
QAS2 Download Basic Data (Obsolete)
QAS3 Upload Results (Obsolete)
QAS4 Upload UD (Obsolete)

WLF1K Report used to generate WLF1K is: SAPLWLF1
O07C Report used to generate O07C is: SSFPSEMAINT

 

 

Check the below links to download the PDF files for the release notes of MM Module:

ECC 5.0 - MM Module Release notes

SAP R/3 MM Module Release notes

 

Some of the differences Basis/Technical Module side:

 

If you're "Basis/Technical", focusing on the underlying technical "Basis" or "NetWeaver" versions will help you stay on the right track. Technically, ECC 6.0 is 2 "technology" versions higher. Following is the terminology/version information for the last 3 ERP product versions:

SAP R/3 Enterprise (4.7x)
SAP BASIS 6.20

SAP ERP 2004
SAP NetWeaver 2004 (BASIS 6.40)
ECC 5.0

SAP ERP 2005
SAP NetWeaver 2004s (BASIS 7.00)
ECC 6.0

The main technology feature delivered with NetWeaver is the integrated J2EE engine (Web Application Server Java).

 

You can use the below link for finding the differences between the 2 versions.
http://solutionbrowser.erp.sap.fmpmedia.com/

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.html

http://help.sap.com/saphelp_scm50/helpdata/en/28/b34c40cc538437e10000000a155106/frameset.html

http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.html

SAP: Asset Accounting: Reversing Documents

You can reverse documents that originated in Asset Accounting.

TCODE: AB08 -> Posting -> Reverse Document.

When you call up the reversal transaction, the system shows you all the transactions for the asset. Select the transaction you want to reverse, and choose the Reverse function.

Postings that Cannot Be Reversed in Asset Accounting

The following postings cannot be reversed in Asset Accounting. They have to be reversed in the integrated application in which they were posted:

• Acquisition with vendor (Accounts Payable)

• Acquisition with purchase order (goods/invoice receipt)

• Retirement with customer (Accounts Receivable)

• Stock withdrawal (Materials Management)

Reversal Indicator

 

Along with the special reversal transaction, the initial screen of the FI-AA posting transaction also offers a reversal indicator. When you set this indicator, you can create a posting that corresponds to the selected posting transaction, but has reversed positive/negative signs.

 

This posting, however, has no relation to the original document. In addition, when you use this posting, the system newly calculates the proportional value adjustments in accordance with the asset value date of the posting. This is different from the procedure with an actual reversal.

 

Reversal of the Settlement of an Asset under Construction

 

There is a separate transaction for reversing the settlement of an asset under construction. Enter the number of the asset under construction that was settled. The system then reverses all documents that were posted during the last settlement. If you want to reverse a settlement that was posted before the most recent one, you first have to reverse all the settlements, which were posted after the one you want, in chronological order.

 

You cannot use this transaction to reverse the settlement of assets under construction that were only managed for cost accounting.

SAP: Dates in Asset Accounting

Asset Value Date: is the value date of an asset transaction from the asset accounting point of view. Each transaction on a capitalized asset triggers the automatic calculation of depreciation on the posting amount. The asset value date, corrected by the period control of the depreciation key, is the key factor in determining the depreciation start date.

Default Values for Asset Value Date

Since the asset value date has a direct influence on the amount of depreciation, the system creates a default value for this date when it can. The overview that follows shows the default asset value date for the most important asset transactions:

Initial acquisition ->	Capitalization date from master record (if in same FY, otherwise posting date)
Subsequent acquisition in the same year->	Asset value date of initial acquisition
Subsequent acquisition in later years->	Document date
Down payment->	Capitalization date from master record (if in same FY, otherwise posting date)
Investment support->	Capitalization date from master record (if in same FY, otherwise posting date)
Revaluation->	Date of revaluation measure
Credit memo at time of invoice receipt->	Value date of the invoice receipt (if in same FY, otherwise posting date)
Later revenue/costs from retirement->	Date of last retirement (if in same FY, otherwise posting date)
Manual adjustments->	First day of fiscal year
Retirement/transfer->	No default value (required entry)
Settlement of AuC->	Posting date

If the capitalization date is not set in the asset master record after the initial acquisition, or if this date is not in the current fiscal year, the system uses the logic below to determine a default value for the asset value date:

• If the document date and the posting date are both in the current fiscal year, the system uses the earlier of these two dates as the default asset value date.

• If the document date is in a past fiscal year, the system uses the posting date as the default asset value date.

Automatically Set Asset Value Date

In the following posting transactions, you cannot enter an asset value date directly. The system therefore uses the default asset value date automatically. It determines which date it uses based on the table below:

 

Goods receipt (valuated) ->	Posting date
Invoice receipt with ref. to purchase order(valuated)->	Posting date of goods receipt (if in same FY, otherwise posting date)
Invoice receipt without reference to purchase order (valuated)->	Posting date
Invoice receipt (difference post.)->	Posting date of goods receipt
Stock withdrawal->	Posting date

 

Defining Your Own Logic for Determining the Asset Value Date

You can set up your own the method for determining the asset value date in Customizing for Asset Accounting (choose Transactions). Or you can use a customer enhancement project (transaction CMOD).

 

Capitalization Date

You can enter the capitalization date manually when you create the asset master record. The system uses this date as the default asset value date when you post the first acquisition to the asset. If you do not enter a capitalization date in the asset master record, the system automatically adopts the asset value date of the first acquisition posting as the capitalization date. The system inserts the asset value date of the first acquisition posting in the capitalization date field (Capitalized on...) in the asset master record, when a capitalizing transaction type is used.

 

Depreciation Start Date

The system determines the start period for depreciation calculation from the asset value date and the period control specified in the depreciation key (period control method) of the transaction category. The depreciation start date is the first day of the start period. The system determines the book value of an asset at the point of retirement In a similar fashion.

 

Date Asset Is Ready for Operation

Along with the date specifications already mentioned, you can also enter the date the asset is ready for operation in the asset master record (in the detail specifications of the depreciation areas). This date is for informational purposes only, and has no influence on the calculation of depreciation. If you do not make an entry in this field, the system automatically enters the capitalization date.

 

Fiscal Years That Can Be Posted

In the FI-AA component, it is possible to post to the current fiscal year and all previous fiscal years back to the date of the legacy data transfer for assets. When you post to past fiscal years, the system automatically updates all the relevant values in the subsequent fiscal years. Therefore, it is possible to make correction postings in the previous fiscal year, even after the fiscal year change (but before the year-end closing). However, after posting in a previous fiscal year, you need to run the depreciation posting program again for that year and all the following fiscal years up to the current fiscal year.

It is no longer possible to post to fiscal years that have been closed using the report for this purpose (refer to Year-End Closing).