SAP FI - AA : Parallel Currencies in Asset accounting

You can portray parallel accounting in your SAP system.

This enables you to perform valuations and closing preparations for a company code according to the accounting principles of the group as well as other accounting principles, such as local accounting principles.

Click here

SAP FI SD: Useful SAP Credit Management Programs

In the present modern era of credit & economic crisis, credit management can plays a vital role in day-today business. So, it is essential for the business to have right things right. Streamlining the credit will assist you in streamlining the business process.

Also, Credit management gives you an opportunity to know your customer better in terms of financial facts & payment behavior.

So, you can't achieve all success, if a proper mechanism is not in place. Like

- kind of credit check you want
- the events where you want these checks
- change customer creditworthiness
- reorganizing the credit data
- period for which you are look the data

so forth and so on.

Following are some Useful program in SAP Credit Management which can come handy.

Continue reading here

SAP: Change Documents for SAP Objects (Master Data / Transactional Data)

Program- RSSCD100 (Display Change Documents) : can display the Change Documents related to any master or transactional data in SAP. Yes, that's true… you can display ALL the details of ALL change documents related to few SAP Object, onto a single screen.

Table - TCDOB : To find the Object id for the relevant master data / transactional data table.

Continue reading here

SAP FI MM : MR11 : GR/IR Clearing : Possible Scenarios

Possible Scenarios in relation to GR/IR Clearing :

1) Invoice received is Greater than Goods Received (More number of Goods Invoiced).

2) Invoice received is Greater than Goods Received (GR =I R goods receipt, Invoice contains Freight Charges, transportation charges and any other charges)

3) Goods Received is Greater than Invoice Received.

4) Invoice Received and Goods not received

5) Goods Received, Invoice Received but invoice cleared not against the PO

6) Goods Received, Invoice Not Received

Please continue read HERE

source: sdn. sap. com

SAP - AA : Legacy Asset Data Transfer Configuration Steps

Transaction Code

SPRO Set Company Code Status

OAYE Specify Sequence of depreciation areas

SPRO Specify Transfer Date / Last Closed Fiscal Year

OAYC Specify Last Period Posted in Prv. System (Transf. During FY)

OAYD Transfer Foreign Currency Values

OAYF Recalculate Depreciation for Previous Years

OAMK Set Reconciliation Accounts (Manually)

Set Company Code Status:

SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Set Company Code Status

You use this indicator to specify the status of the company code from the point of view of Asset Accounting:

Test status - You can change values by transferring asset data from a previous system, or by posting.
Transfer status - You can enter and change values by transferring asset data from a previous system, but posting is not possible.
Production status - The asset data transfer is complete. You can only change values by posting. Before the system goes live, it is essential that you set the system status to "production" (not test).

This rule applies even if you transfer asset data from your previous system in several phases over the course of time. If you do transfer data in this way, you have to temporarily remove the "production" setting of the the company code status.

Company code status is generally set to '2' for conversion purposes. This identifies the company code as being in test with data transfer always allowed. This should be the start-up position for the asset company codes.
In the Production system, this setting should be changed to "0 – Asset data transfer completed" once all data takeover activities are completed for each company code.
Once the SAP company code has had at least one Quarter end reported and verified after go-live, and the assets data is deemed stable, the company code status will be set to '0'.
0 Asset data transfer completed
1 Asset data transfer not yet completed

2 Test company code with data transfer always allowed

3 Company code deactivated - reporting allowed

Specify Sequence of Depreciation Areas:

SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Specify Sequence of Depreciation Areas

In this field you define the order in which you want to update depreciation areas with values during legacy data transfer. You determine this sequence by entering a relative number in this field.
During the transfer of legacy data, the first depreciation area to be transferred is generally the book depreciation area.
In this step, the sequence of the depreciation areas for the data takeover transaction is specified. If there are additional depreciation areas for local / fiscal purposes, the sequence for the depreciation areas may be impacted.

Specify Transfer Date/Last Closed Fiscal Year:

SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Parameters for Data Transfer > Date Specifications > Specify Transfer Date/Last Closed Fiscal Year Status

In this step, the asset transfer date for conversions is specified. This setting is maintained in each client to facilitate test conversion activities.

This configuration is mostly maintained directly in each client. You have to enter this date before starting the asset data transfer. In most cases, the transfer date will be the last day of a fiscal year. All transactions starting in the new fiscal year are then carried out only in SAP Asset Accounting. The values transferred are the cumulative values at the end of the fiscal year.

The transfer date can also be during the fiscal year. When the transfer date is within the fiscal year, the values transferred are the values as they stand at the end of the last closed fiscal year before the transfer date. The transactions since the start of the current fiscal year, however, also have to be transferred. This is necessary in order to create the asset history sheet.

This field is only ready for input if the company code is not yet live. The system uses this date to determine the last closed fiscal year.

Specify Last Period Posted in Prv. System (Transf. During FY):

SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Parameters for Data Transfer > Date Specifications > Specify Last Period Posted in Prv. System (Transf. During FY)

The following step is only necessary if you want to perform an old assets data takeover during the fiscal year. In this case, you must specify the period up to which depreciation was posted in the previous system. This period refers to the posted depreciation that is to be transferred during old assets data takeover.

In this field, the system enters the period, for which depreciation was last posted. If the legacy data transfer is carried out during the fiscal year, you must update this field manually.
This field is not available for input if there is no legacy data transfer during the fiscal year, or if depreciation is not posted in this depreciation area.

If the asset takeover date is during a fiscal year, e.g. 31.03.2006, then the last period in which depreciation postings were made in the legacy system must be specified. This setting is maintained in each client.
This configuration is maintained directly in each client.

Transfer Foreign Currency Areas:

SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Options > Transfer Foreign Currency Areas.

You only need to carry out this step if you manage depreciation areas in foreign currencies.

In this step, you determine that foreign currency areas can receive values during old assets data takeover. Then the depreciation areas are not supplied with values from another area by the system, although they are defined as dependent areas by the Customizing settings. This specification can only be made for areas that are managed in foreign currency.

Using this indicator, you specify that you will provide values for the foreign currency area during the legacy data transfer. The system then does not provide values itself for the area (by taking over values from another area, with no changes allowed) as it normally would.

You can only make an entry in this field for an area which is managed in foreign currency.
For any Depreciation area with foregin currency values fixed at the Group Rate as at the takeover date, the takeover values for this depreciation area is calculated manually/automation tool.

Please note that if any change to depreciation area sequence is undertaken, that the manually input flag will change position and will require updating.

Recalculate Deprecation for Previous Years:

SAP Reference IMG > Financial Accounting > Asset Accounting > Asset Data Transfer > Parameters for Data Transfer > Options > Recalculate Depreciation for Previous Years

Set this indicator if you want the system to newly calculate accumulated depreciation from past years during the legacy asset data transfer.

You can recalculate the accumulated depreciation from the past, based on SAP depreciation rules, when a depreciation area is newly entered the values from a depreciation area should be recalculated in the R/3 system.for example, conversion data is not available for this depreciation area for these assets

This recalculation is based on the condition that the acquisition value was acquired completely at the time of capitalization. However, for the book depreciation area, this is only possible in company codes that are still in test mode.
You can also recalculate accumulated past depreciation for individual assets using the transaction "change old assets" (Function: recalculate values) after the takeover of data from your previous system.

Set Reconciliation Accounts (Manually) :

SAP Reference IMG > Financial Accounting > Asset Accounting > Preparing for Production Startup > Set Reconciliation Accounts - TCODE: OAMK (OAK5 - for automatically set)

This step is required for conversion purposes. Carried out directly in client during cutover. By default the relevant GL accounts will have been created as reconciliation accounts. As part of the conversion, the flag is removed from the GL accounts per asset class per company code. After the balances have been loaded, the reconciliation flag is reset. OAMK allows this to be carried out manually. Once they are set as reconciliation accounts, the system will only post to them via Asset Accounting from this point onwards. This is maintainable in each client except production where this step is managed by the cutover strategy.

SAP FI-AA: Year End Closing Procedure

==> Settle the Assets under Construction (SAP FI-AA transaction AIAB, AIBU) - Settle the Auc settlement before you do dep.run in each period. So, that the new assets created also consider for depreciation based on the requirement.

==> Execute the depreciation run (report RAPOST2000 or transaction AFAB) (SAP FI-AA) - Execute the dep.run in each period without errors. System will not allow to post the depreciation documents with errors. This has to be finished successfully for all the periods.

==> Run the fiscal year change in Asset Accounting (transaction AJRW) (SAP FI-AA) - Execute the FY change only after depreciation posting without errors. System not allows you to change FY with errors.This process creates the balance carry forwards for Asset Accounting. We recommend that you execute this run on the first day of the new fiscal year. Note: by this time, you should have completed year-end closing for Asset Accounting of the previous year.

==> Carry out period asset postings (report RAPERB2000 or transaction ASKB) (SAP FI-AA)- This is usually done in the client where the derived depreciation area' used. Derived depreciation area amounts posted periodically to the G/L. For posting the documents in this transaction, you need to give the document type and that should be external number range. Same like as depreciation run, this also should end with out errors.

==> Run Account Reconciliation (transaction ABST2) (SAP FI-AA) - Once the above steps are through in green, you can run this report to know about the differences between the FI-GL balances and FI-AA balances.This program selects the asset summary records (ANLC), summarizes the values on G/L account and business area levels, and writes the summarized values to table EWUFIAASUM.

==> Execute the year end closing program (transaction AJAB) - After all successful steps you can close the FI-AA year.

Batch specific units of measure- step by step configuration for Steel industry

Introduction:

In some industry sectors (for example, the pharmaceutical, chemical, steel, or paper industry sectors), the composition or attributes of products vary to some degree. Therefore, you cannot use a fixed conversion factor to convert quantities of these products into various units of measure. Instead, each batch has to be given an individual conversion factor.

This component allows you to handle materials like these throughout the entire logistics chain.

Batch specific unit of measure:

Alternative units of a material for which the conversion ratio to the base unit of measure can be defined on a batch-specific basis.

Click here for full story

Author: Raja

Source: sdn.sap.com

How to approach multiple currencies for Net order value in PO Release strategy?

Introduction :

In PO release strategy Net order value is the main criteria to decide the release level .If company exists in multiple countries ,we have to use local currency for day to day transaction .If we use multiple currencies based on the country ,it is important to configure release strategy in such a way that it meets all the countries requirement without compromise .we could use only one currency in one characteristic (CEKKO-GNETW) and approval limit values vary as per the country requirement .In this regard how to approach this scenario .

Click here for full story

source : sdn.sap.com

Integration of FI-AA with Real Estate

Asset Accounting (FI-AA) manages fixed assets on a value basis from the accounting point of view.

In Asset Accounting. You have to enter the number of the business entity as an asset group number to set up a link between the Business entity & Asset.

You categorize and structure the objects in to different asset types such as buildings, properties or assets under construction by using asset classes.

Using the asset classes, you control the calculation type for the automatic determination and posting of depreciations, interest and evaluations.

The calculation type for these values is in addition to the legally defined guidelines; it is a customer-specific value range for determining depreciations, calculating interest, insurance values or investment grants. This allows you to define the tax or balance sheet, depreciation and valuation method for internal cost accounting.

A property or building can be assigned more than one asset. To specify the account determination, you have to identify one of the assets as leading.

Customizing settings

FI-AA is activated in Real Estate Customizing
The asset class of the leading asset is set as Real estateA main usage type (for the purpose of account determination) is set for the leading asset ( Main Usage Types); the account determination for the debit position of lease-outs may depend on the main usage type; if no asset is assigned to the building or property, the main usage type is derived from the asset class of the leading asset according to the rule defined in Customizing

The Property, Building text and Main usage type fields are automatically updated under the General Data tab depending on the asset class.

Text field in FI Document automatically from MIRO line item

When a purchase order is created to a cost centre, G/L account and cost centre are entered manually. Often Purchase Order only uses short text field as reference, i.e., Material is not mandatory.

MIRO process is then done for PO after GR, and the PO text (short text) is copied into MIRO.

G/L account line items can be displayed in FBL3N, detailing the document numbers related to the invoice/PO once posted.

The field "Text" is defaulted as blank, even if created with reference to a PO, which contains text. Does anybody know of a way to automate process so that the text field is populated with the text from MIRO?

You can transfer what ever the data from the MIRO to accounting document-using BTE.

Go to SE37 - SAMPLE_PROCESS_00001120 (this is the standard BTE for account document posting). Copy this with ZSAMPLE_PROCESS_00001120.

In this you cannot modify the tables t_bkpf and t_bseg. you can use t_bkpfsub and t_bsegsub.

For this a little bit config is required.

1) Go to t-code FIBF-> settings->Products->... of a customer.

Click new entries -> product name- ZPRODUCT, text - any text, RFC dest - ZSAMPLE_PROCESS_00001120, A - enable check box -> save.

2) Go back -> settings -> P/S Modules -> ... of a customer.

Click new entries -> event - 00001120, Product - ZPRODUCT, Ctr - Country key, Appl - FI-FI, Function module - ZSAMPLE_PROCESS_00001120 -> save.

3) Go back -> settings -> Process Modules -> ... of a customer.

Click new entries ->Process - 00001120, Ctr - Country key, Appl - FI-FI, Function module - ZSAMPLE_PROCESS_00001120, Product - ZPRODUCT -> save.

Now go to SE37->ZSAMPLE_PROCESS_00001120 logic.

loop at t_bkpf.

loop at t_bkpfsub.

move 'your value' to t_bkpfsub-value.

modify t_bkpfsub index sy-tabix.

endloop.

loop at t_bseg.

loop at t_bsegsub.

move 'your value' to t_bsegsub-value.

modify t_bsegsub index sy-tabix.

endloop.

''Your value' is imported value.

No need to worry about modified values. After execution of BTE it will go to standard program and copy the values of t_bkpfsub] and t_bsegsub to SAP tables. So please be perfect with code. SAP wouldn't allow change the values in t_bkpf and t_bseg values. you can add your own fields in bkpf_subst and bseg_subst.

But make sure that; please write the code in FM with conditions like company code doc type etc. because this BTE is very important. It will execute before acc doc is posted. If you do not specify any conditions it will execute for all co codes in acc doc. it will affect business. You can debug this BTE. Put a break point in FM and see the values while post the MIRO.

Once import the values free memory id and clear the variables whatever you used in BTE.

SAP Tables for Technical Consultants & also for Function Consultants !!!

Tables on below topics :

Authorisation, objects, Batch input map's, Batch jobs,Correction & transport, Countries, Currency, Data elements, Development classes, Domains, Dynpro areas, Filenames, Function modules, Function groups, Icons, Logical databases, Matchcodes, Messages, Programs, Repository objects, Purchase Requisition, SAPscript, Spool, Status (menu), Switch objects, Tables and views, Texts, Transactions, User parameters, Variants, Accounting, Accounting documents, Bill Of Material, Classification, Classification characteristics, Configurator, Cost elements, centers, activities, Customer,Equipment, Equipment status, Function location, Customising tables, General ledger accounts, Goods movement, Customising, Inventory document, Maintenance Order, Material, Material document, Notifications, Orders,Personel, Production resource tools, Customising tables, Project, Purchase Requisition, Purchasing document, Purchasing info record, Reservation, Sales Document, Sales requirements, Storage locations and stocks, Tasklist, Transfer requirement, User data, Vendor master, WM transfer, Other tables, Useful Transactions, Function modules, Standard data transfer, Helpful reports.

Click on SAP Tables for the document.

Why do we need to DEBUG : BREAK POINT : WATCH POINT

DEBUG

We write programs to achieve certain functionality and like other actions, we make mistakes while writing the code. If they are not trapped at the right time, problem becomes bigger, and bigger and bigger.

BREAK POINT

The BREAK POINT is a debugging aid. When we run a program normally, it is interrupted at the statement, and the system automatically starts the debugger, allowing you to display the contents of any fields in the program and check how the program continues. If the program is running in the background or in an update task, the system generates a system log message.

SAP- CO : Some of the Product Cost Approaches

§ Finished Goods Inventory in Production Plant AAAA

Valuation at moving average price per batch (FIFO batch valuation)
A new batch number will be generated for each production order (work order) producing the finished product
Each batch will have a unique material cost
The material cost of a batch is calculated from semi-finished goods and raw materials that are directly constituting to the finished product according to the BOM

§ Semi-finished Goods Inventory in Production Plant AAAA

Valuation at standard price updated from standard cost estimates
All inventory of each semi-finished product will be valuated the same (at the defined standard cost)
The standard cost can be updated either: 1) manually, or 2) automatically from the cost roll-up (can be using weighted average) of the lower levels of the BOM and can be selectively updated only for certain semi-finished products.
Re-valuation of existing inventories for semi-finished product will happen whenever the standard cost is updated. The gain or loss will post to the P/L accounts

§ Raw Materials Inventory in Production Plant AAAA

Raw materials will be valuated for each batch of the receipts of purchase using the purchase order price.
The batches of raw materials will be issued to production orders at FIFO.
No re-valuation of raw materials will be required.

§ All Inventory in Branches

Inventory will be valuated for each batch of the receipts of STO using the STO price (transfer prices plus the landed costs).
The batches of goods will be delivered to customers at FIFO.
No re-valuation of inventory will happen.

Fiscal Year Change (AJRW) & Year-End Closing (AJAB)

Fiscal Year Change (AJRW)

From a system perspective, a fiscal year change represents the creation of a new fiscal year for a company code.
At the fiscal year change, the asset values from the previous fiscal year are carried forward cumulatively into the new fiscal year.
Once the fiscal year change takes place, you can post to assets using value dates in the new fiscal year. At the same time, you can, however, continue to post in the previous fiscal year, provided this has not been closed as a result of the year-end closing.
The fiscal year change can only be carried out (even in test mode) for the new fiscal year.
The earliest that you can carry out a fiscal year change is in the last month of the old fiscal year.
Before you can change to fiscal year YYYY, you must have already closed fiscal year YYYY-2. You can have a maximum of two fiscal years open for posting at one time.
No business transactions can be posted in a new fiscal year before the fiscal year change.
You can continue to post in the old fiscal year, even after the fiscal year change.
The system automatically corrects any values that have already been carried forward and that are affected by postings in the past.
The fiscal year change has to be carried out as background processing for performance reasons. You can carry out test runs with fewer than 1,000 assets in the foreground.
If the company code has been set to "production" (company code status = blank), you cannot carry out the fiscal year change until the last month of the current fiscal year (in update mode).
If the company code is a test company code (company code status = 2), you can change the fiscal year as and when required. You set the company code status in Customizing for Asset Accounting (OABP).
No more than two fiscal years, however, can be open at the same time.
Carry out the fiscal year change as a test run. If more than 1,000 assets exist in the system, you have to start the program by choosing Program ® Execute in Background. The section on depreciation posting runs contains information on monitoring the job and spool. If fewer than 1,000 assets exist in the system, you can also start the report online
If you started the report in update mode, the asset values from the previous fiscal year are carried forward cumulatively into the new fiscal year. Postings can now be made to the new fiscal year.

Year-End Closing (AJAB)

You can use the year-end closing program to close the fiscal year for one or more company codes from an accounting perspective.
Once the fiscal year is closed, you can no longer post or change values within Asset Accounting (for example, by recalculating depreciation).
The fiscal year that is closed is always the year following the last closed fiscal year. You cannot close the current fiscal year.
The year-end closing in Asset Accounting must be performed before the year-end closing in General Ledger Accounting.
The fiscal year change has to be carried out in Asset Accounting before the year-end closing (SAP FI-AA).
You have to carry out the year-end closing as background processing for performance reasons. Start the program, therefore, as a background job (on the selection screen for the program: Program ® Exec. in Background). You can carry out test runs with fewer than 1,000 assets in the foreground.
The system only closes a fiscal year in a company code if

· The system found no errors during the calculation of depreciation (such as incorrectly defined depreciation keys)

· Planned depreciation from the depreciation areas to be posted has been completely posted to the general ledger

· Balances from depreciation areas that are posted periodically have been completely posted to the general ledger

· All assets acquired in the fiscal year have already been capitalized. Since this check does not make sense for assets under construction, you can prevent it from being performed for these assets by means of the asset class.

· All incomplete assets (master records) have been completed.

The system lists any assets that do not meet the above requirements in the year-end closing log. The log also shows the reason for the errors.
You can undo a year-end closing that has already been performed.
You might need to do this if you establish that fixed assets do have to be corrected after all.
You can undo the year-end closing for the entire company code (OAAQ) or for each depreciation area (OAAR).
If you have performed the year-end closing in update mode, you can no longer post to the closed fiscal year.

Depreciation: AFAB

Use

o A posting to a fixed asset initially causes the planned depreciation to change in Asset Accounting.

o The accumulated depreciation accounts and depreciation accounts of the balance sheet and profit and loss statement are not updated immediately, however. The total planned depreciation is not posted to Financial Accounting until the periodic depreciation-posting run is executed.

o The depreciation posting should be run periodically (annually, semi-annually, quarterly, or monthly).

o When executed as an update run, the program has to be started in the background.

o The system creates posting documents for each depreciation area and account group in accordance with the posting cycles specified in Customizing.

o As the posting date, the system uses

· The last day of the period for normal periods (no special periods)

· The last day of the fiscal year for special periods

Prerequisites

o Document type AF has to define for posting depreciation.

o In definition of the document type, number range 03 has to specify with external number assignment.

o Also specify that the depreciation in depreciation areas

- 01 (book depreciation),

- 03 (reserves for special depreciation), and

- 20 (cost-accounting depreciation) is posted in the general ledger.

o Define the depreciation posting cycle by specifying the length of time in posting periods between two posting runs. The system is set in such a way that depreciation is posted monthly. You do not have to keep strictly to this posting cycle.

o You can also choose an unplanned depreciation-posting run using an indicator on the initial screen of the depreciation posting run. When you set this indicator, you can skip over several periods and post the total depreciation for all of the skipped periods in one period.

o The system supports two different procedures for distributing the forecasted depreciation over the posting periods.

o The difference between the two procedures becomes evident when you process acquisitions within the fiscal year or handle post-capitalization.

o With the catch-up method, depreciation due on a transaction within the fiscal year (from the depreciation start date, according to period control, up to the current period) is posted in one total. The depreciation posting program posts this amount in the period in which the posting date of the acquisition lies.

o With the smoothing method, the annual depreciation amount determined is distributed equally over the periods from the current posting period to the year-end.

o For each depreciation area, you have to specify whether depreciation is to be posted to the cost center and/or to the order. This information is taken from the asset master record and passed on to Financial Accounting as an additional account assignment.

o For depreciation area 20, the system is set to assign the cost-accounting depreciation and interest to the cost center.

Planned Posting Run

You can post to the next period that is specified according to the posting cycle. During a regular posting run of this kind, the system does not allow you to limit the run to particular assets.

Repeat Run

You can request a repeat posting run for the last period posted. You might need to carry out a repeat run if the depreciation terms were changed for individual assets in connection with the year-end closing, for example. During a repeat posting run, the system only posts the differences that resulted between the first posting run and the repeat posting run. You can limit the run to particular assets.

Restart

If a posting run terminated for technical reasons and changes had already been made to the database, you have to restart the program in restart mode. Using the restart mode ensures that all system activities that were interrupted by the termination are repeated.

Unplanned Posting Run

If, for whatever reason, you want to skip over one or more posting periods, you can do this by specifying an unplanned posting run. The system then creates postings for all the periods that were skipped, as well as for the period entered. The posting period that you specify, however, must fit into the posting cycle. If you specify period 7 for a quarterly posting cycle, for example, no posting occurs.

Once you have made all the necessary entries, execute the depreciation posting run in the background (Program ® Execute in Background). You can monitor the job scheduled in the background.

The job always appears under the name RAPOST2000. The Status column shows the current status of the job. Choose Refresh or F8 to update the information. As soon as the status of the job is "Finished", select your job and choose Spool.

To go from the overview to your list, choose F6. When this list was generated, the fixed assets in question were also updated to include the posted depreciation. The planned depreciation for every complex fixed asset is not totaled for each posting level and posted directly to Financial Accounting until the periodic depreciation posting run has been executed.

Result

The planned depreciation is posted to the accounts defined in Customizing. Note that the system always creates collective documents (not individual documents for each asset) when posting depreciation.

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:

For installing ECC 6.0 you required a solution manager key. With out solution manager key you cannot install ECC6.0.
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.
ECC6.0 supports UNCODE & 4.6C supports NONUNICODE.
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