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

Fiscal Year Change (AJRW)

 

1. From a system perspective, a fiscal year change represents the creation of a new fiscal year for a company code.
2. At the fiscal year change, the asset values from the previous fiscal year are carried forward cumulatively into the new fiscal year.
3. 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.
4. The fiscal year change can only be carried out (even in test mode) for the new fiscal year.
5. The earliest that you can carry out a fiscal year change is in the last month of the old fiscal year.
6. 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.
7. No business transactions can be posted in a new fiscal year before the fiscal year change.
8. You can continue to post in the old fiscal year, even after the fiscal year change.
9. The system automatically corrects any values that have already been carried forward and that are affected by postings in the past.
10. 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.
11. 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).
12. 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).
13. No more than two fiscal years, however, can be open at the same time.
14. 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
15. 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)

 

1. You can use the year-end closing program to close the fiscal year for one or more company codes from an accounting perspective.
2. Once the fiscal year is closed, you can no longer post or change values within Asset Accounting (for example, by recalculating depreciation).
3. The fiscal year that is closed is always the year following the last closed fiscal year. You cannot close the current fiscal year.
4. The year-end closing in Asset Accounting must be performed before the year-end closing in General Ledger Accounting.
5. The fiscal year change has to be carried out in Asset Accounting before the year-end closing (SAP FI-AA).
6. 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.
7. 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.

 

8. 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.
9. You can undo a year-end closing that has already been performed.
10. You might need to do this if you establish that fixed assets do have to be corrected after all.
11. You can undo the year-end closing for the entire company code (OAAQ) or for each depreciation area (OAAR).
12. 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:

 

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