Showing posts with label Fixed Asset. Show all posts
Showing posts with label Fixed Asset. Show all posts

Friday, October 10, 2008

SAP FICO Tcodes for Configuring Assets Accounting

S.No    TCODE   PARTICULARS
1 EC08 COPY CHART OF DEPRECIATION
2 FTXP CREATION OF 0% TAX CODES
3 OBCL ASSIGN TAX CODES FOR NON-TAXABLE TRANSACTIONS
4 OAOB ASSIGN CHART OF DEP. TO COMPANY CODE
5 SPECIFY ACCOUNT DETERMINATION
6 CREATE SCREEN LAYOUT RULES
7 OAOA DEFINE ASSET CLASSES
8 AS08 DEFINE NUMBER RANGES FOR MASTER CLASSES
9 AO90 INTEGRATION WITH GL
10 OAYZ DETERMINE DEPRECIATION AREAS IN ASSET CLASSES
11 DEFINE SCREEN LAYOUT FOR ASSET MASTER DATA
12 AO21 DEFINE SCREEN LAYOURS FOR ASSET DEP. AREAS
13 FBN1 DEFINE NUMBER RANGES FOR DEP. POSTINGS
14 OAYR SPECIFY INTERVALS AND POSTING RULES
15 OAYO SPECIFY ROUND UP NET BOOK VALUATION
16 DEPRECIATION KEYS
17 DEFINE BASE METHOD
18 AFAMD DEFINE DECLINING BALANCE METHODS
19 AFAMS DEFINE MULTI LEVEL METHODS
20 AFAMP DEFINE PERIOD CONTROL METHODS
21 AFAMA DEFINE DEPRECIATION KEY
22 AS01 ASSET MASTER CREATION
23 AS11 CREATION OF SUB-ASSET
24 F-90 ASSET PURCHASE POSTING
25 AW01 ASSET EXPLORER
26 AFAB DEPRECIATION RUN
27 F-92 SALE OF ASSET
28 ABUMN TRANSFER OF ASSET
29 ABAVN SCRAPPING OF ASSET

SAP FICO Describe the T codes step wise in Asset Accounting module

Step 1 – COPY CHART OF DEPECIATION

EC08 – IMG>Financial Accounting > Asset Accounting > FI-AA Implementation Guide (Simplified Version) > Organizational Structures and Master Data > Copy reference chart of depreciation/depreciation area

Step 2 – ASSIGN COMPANY CODE TO CHART OF DEPRECIATION

OAOB – IMG > Financial Accounting > Asset Accounting > FI-AA Implementation Guide (Simplified Version) > Organizational Structures and Master Data > Assign chart of depreciation to company code

Step 3 – ASSIGN FINANCIAL STATEMENT VERSION TO EVERY DEPRECIATION AREA

OAYN – IMG >Financial Accounting > Asset Accounting > FI-AA Implementation Guide (Simplified Version) > Organizational Structures and Master Data > Specify statemement version for asset reports

Step 4 – IDENTIFY YOUR ASSET CLASSES

Step 5 – IDENTIFY YOUR ACCOUNT DETERMINATION & SCREEN LAYOUT FOR YOUR ASSET CLASSES

SPRO – IMG > Financial Accounting > Asset Accounting > FI-AA Implementation Guide (Simplified Version) > Organizational Structures and Master Data > Asset Classes > Specify required entries for asset master data

Step 6 – IDENTIFY YOUR GL ACCOUNTS FOR YOUR ASSET CLASSES

Step 7 - DEFINE YOUR NUMBER RANGE

AS08 – IMG > Financial Accounting > Asset Accounting > Organizational Structures > Asset Classes > Define number range interval

Step 8 - DETERMINE DEPRECIATION AREAS IN ASSET CLASSES AND SCREEN LAYOUT

A021 – IMG > Financial Accounting > Asset Accounting > Master Data > Screen Layout > Define screen layout for asset depreciation areas

OAYZ – IMG > Financial Accounting > Asset Accounting > Valuation > Determine depreciation areas in the asset class

Step 9 – GENERATE ASSET CLASSES FROM GL ACCOUNTS

ANKL – IMG – Financial Accounting > Asset Accounting > FI-AA Implementation Guide (Simplified Version) > Organizational Structures and Master Data > Asset Classes > Generate Asset Classes from G/L Accounts

Step 10 – COMPLETE DATA FOR ASSET CLASSES SETTING REQUIRED ENTRY FIELDS

SPRO – IMG > Financial Accounting > Asset Accounting > FI-AA Implementation Guide (Simplified Version) > Organization Structures and Master Data > Asset Classes > Specify requires entries for asset master data

OAYZ – IMG > Financial Accounting > asset Accounting > FI-AA Implementation Guide (Simplified Version) Organizational Structures and Master Data > Asset Classes > Enter default values in asset classes

AO90 – IMG > Financial Accounting > Asset Accounting > FI-AA Implementation Guide (Simplified Version) > Organizational Structures and Master Data > Assign additional G/L accounts for transactions/depreciation

Step 11 – SETTING UP SPECIAL ASSET CLASSES

OAYK – IMG > Financial Accounting > Asset Accounting > Valuation > Specify max amount for LVA + asset classes > Specify amount for low value assets

OAY2 – IMG > Financial Accounting > Asset Accounting > Valuation > Specify max amount for LVA + asset classes > Specify LVA asset classes

Step 12 – SPECIFY INTERVALS AND POSTING RULE

OAYR – IMG > Financial Accounting > Asset Accounting > FI-AA Implementation Guide (Simplified Version) > Organizational Structures and Master Data > Specify intervals and posting rules

SAP FICO Posting to Cost Center and Internal Order in SAP FICO FIXED ASSET

If you have added the field Internal order in the Asset Master as a statistical order and you want your depreciation
posted not only to the cost center but also to this order.

In transaction OAYR in the IMG you define how depreciation posts to the depreciation posting rules - there is a CO assignment box where you have to tick both cost centres and internal orders.

What is internal order? Explain with example and how it is related to cost center.

An internal order is used to accumulate cost for a specific project or task for a specific time period. An internal order is therefore used for a short period with a specific deadline.

Your internal order will usually settle to cost centers (and not visa versa) according to the settlement rule in the order setup.

An internal order can therefore be used to group all the expenses incurred to plan and hold a conference over a 3 month period. The order can be settled on a monthly basis to cost centers. When the conference is finished the order can be settled finally. The cost of the conference will then be spread over 2 or more cost centers, but can be viewed in total on the internal order when needed.

Internal Orders - It is an instrument used to monitor costs and, in some instances, the revenues of an organization.

Uses of Internal orders
- Monitoring the costs of short-term jobs
- Monitoring the costs and revenues of a specific service
- On going cost control

Internal order categories
- Overhead Orders
- Investment Orders
- Accrual Orders
- Orders with revenue

Cost centers are not for specific job. e.g If you have open Trade-fair / exhibition (1 month period), then to allocate cost, you can use Internal Orders (Say IO) you can post to IO, and from their to various cost centers. If management were to ask you the cost of that exhibition, Internal Order will help you

Cost center is a responsible center in SAP. It cannot be defined as statistical but in transactions it may become as per other co objects.You will be able to find out the performance of the cost center using activities and plan values with actual value. This is lowest cost object in SAP. This will become a statistical object when you allocate the cost to other higher objects. Cost can be allocated to other cost centers or co objects but not fi objects like GL,assets, inventory etc. can be defaulted in transactions through cost element. It cannot be a cost object for a revenue element, revenues are always taken for other higher CO objects. No budget functionality is available but planning functionality is available and is always measured for a year in business.

Internal order is the second CO object - which can be defined as statistical or real. You will be able to define Budget and planning figures - more than one year also. Can control the postings of FI through budget controls. You can have the report of Plan vs actual including commitment. Cost cannot be allocated but settled through settlement rules and profiles. The receiver of the values can be any object not like Cost center - can be CO objects and FI objects. Ideal for R&D expenses capitalisations, etc. Status profile is linked to this which controls many individual transactions in each status which is a part of this Internal order. It can also receive postings of activities from Cost center. Settlement profile is an wonderful tool for variety of settlement - needed for FI and CO - legal requirements also and Revenue requirements also for any country.

All SAP CO orders like Production order, Plant maintenance order, etc will behave like Internal order with more functinalities.

SAP FICO Process Fixed Asset Depreciation SAP FICO FIXED ASSET

Every asset transaction immediately causes a change of the forecasted depreciation. However, it does not immediately cause an update of the depreciation and value adjustment accounts for the balance sheet and profit and loss statements. The planned depreciation is posted to the general ledger when you run the periodic depreciation posting run. This posting run uses a batch input session to post the planned depreciation for each posting level for each individual asset as a lump sum amount.

The calculation and scheduling of depreciation, interest and revaluation are automatically controlled by keys in the system, or you can control them manually using a special posting transaction. In both cases, planned depreciation from Asset Accounting must be periodically posted to the corresponding asset and expense accounts of the general ledger. You carry out this posting using a batch input session. In addition to the various depreciation types, interest and revaluation, this batch input session also posts the allocation and writing off of special reserves.

When the system posts depreciation, it creates collective documents. It does not create separate documents for each asset.

Depreciation Posting Run is done via transaction code 'AFAB'.

The program creates batch input sessions for posting depreciation and interest to the G/L accounts in Financial Accounting and/or to Controlling.

Fields Description :-

Company code : Your Company Code

Fiscal Year : Your fiscal year

Posting period : Your depreciation period

Reason for posting run (choose one)

Planned posting run : X (default)

List assets : (tick if you want to see the detail)

Test run : (tick if you run in test mode else untick for production run)

Main asset number : (you can specify certain asset number if you click repeat run or test run)

Note :
Click the execute button if this is a test run.
Click the menu bar -> Program -> Execute in background if this is a production run.

You should get this message :
Background job was scheduled for program RABUCH00 and print out the output.

Release and Process the Batch Input Session in transaction code 'SM35'.

Process Session RABUCH00
X - Display errors only
Additional functions
X - Dynpro standard size

Click the Process button

If there is error, the system will pop up the error message.

Correct the error and recreate the session in transaction 'AFBD'.

Fields Description :-

Company code : Enter your company code

Fiscal year : Enter your fiscal year

Posting period : Enter your posting period

List assets : (tick if you want to see the detail)

Test run : (tick if you run in test mode else untick for production run)

Note :
Click the execute button if this is a test run.
Click the menu bar -> Program -> Execute in background if this is a production run.

You should get this message :
Background job was scheduled for program RABUCH00 and print out the output.

SAP FICO Asset Year-end Closing SAP FICO FIXED ASSET

The year-end closing enable the company to produced the final balance sheet and profit and loss statement for its annual report, which has to be created to meet the particular legal obligations in each country.

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.

AJAB - Year-End Closing Asset Accounting

Company code : Your Company code

Asset classed asset u. const. : Optional

For fiscal year : Last closed fiscal year

Uncheck 'Test run' if this is a production run

At menu bar, click Program -> Execute in background.

Perform Fiscal year close for fixed Assets.

While doing a Test run, message is that fiscal year close could not be performed but it does not display any Asset details .It says Other Error. I am not able to identify what those other Errors could be.

Also, I have checked Incomplete Assets list As well but that list is empty as well. Also while running tcode AUVA there is a tab correct incomplete Assets, can anyone tell what deos that mean and when its to be used.

You can check and edit Asset accounting closing status using tcode OAAQ.

But you seem to be not clear on process.

AJAB is for closing Asset Accounting books.
AJRW is a technical step of changing fiscal year in system. If not done, it will not allow you to view asset reports in current fiscal.

Now, your error says incomplete asset. Please run ajab in test mode, check for details. It will give you asset details and error details as well. Go to asset explorere and check if the asst in question has been fully depreciated for the year.

If not run repeat deprecation for the asset in period 12 and then try closing asset books. You can also check asset and GL inconsitency using tcode ABST.

SAP FICO Asset Reverse Year-End Closing SAP FICO FIXED ASSET

If you closed a fiscal year too soon, and still need to make corrections, you can reset the last closed fiscal year in Customizing for :-

Asset Accounting (Periodic processing -> Year-end closing -> Reverse).

Using this function, you can re-open the last closed fiscal year, either for selected depreciation areas in a company code, or for all depreciation areas in a company code. You do this by changing the field for the last closed fiscal year.

Be careful if you re-open a fiscal year only for certain depreciation areas, and you need to make adjustment postings only in these areas. You cannot use the standard transaction types for these postings, since the standard transaction types post to all depreciation areas. Instead, you have to define your own transaction types in Customizing for Asset Accounting (Transactions), limiting them to the required depreciation areas.

OAAQ - Reverse year-end closing for deprciation area

At the desired company code, change the fiscal year in 'Closed fiscal year' column.

Save entries and create a new request.

Change Asset fiscal year

AJRW - Asset fiscal year change

Company code : Your Company code

New fiscal year : Last closed fiscal year

Uncheck 'Test run' if this is a production run

At menu bar, click Program -> Execute in background.

SAP FICO Post Capitalization asset haven't been post in closed fiscal year

If you realized that there are some fixed assets that haven't been post in a closed fiscal year,

Do the following steps :-

1. Reverse fiscal year closed by following the 'Reverse Year-end Closing' procedure.

2. Open the accounting fiscal year via transactin 'OB52'.

3. Post the fixed asset acquistions in the re-open fiscal year.

4. Repeat depreciation run for the last period of that closed fiscal year.

5. Repeat depreciation run for the last period depreciation run of the current fiscal year.

6. Closed fiscal year by following the 'Year-end closing' procedure.

7. Closed the accounting fiscal year via transactin 'OB52'.

SAP FICO Mass Change For Assets and Data Reset SAP FICO FIXED ASSET

How to reset Asset Data?

You can reset the entire AA data from Img->FA-> AA-> Preparing for production startup ->Tools -> Reset
company code.

This will reset only the asset accounting data from the company code. But before you perform this you have to make sure that you reverse all the transaction you have posted and have gone to the FI. As this reset will not effect FI GL data.

You can then reset the depreciation posted and then the recon accounts.

When you reset the recon accounts, it will enable you to post directly to the account like normal GL. Then you have to post JV and rectify you GL(recon account).

Then upload the correct data. After the data is uploaded set the recon accounts. this will reconcile the amount with the assets and activate the company code (in asset area). *-- Lakshmi

Mass change for assets

I am experiencing problems in OA02, Asset Mass Change. I am using 4.6C.

What happened was that I created the Substitution, then created the Step, and I then SAVED. I am not sure if I need to create a RULE or not. I have already defined in a STEP, (using Formula Builder) that most assets belonging to a certain asset class, 9011 with a current Cost centre, Z01, are to be assigned to another Cost Centre Z02, within the same Co.
Code. I then saved the Substitution, although I noticed that there was a "?" icon next to the RULES folder. I am well aware that for Time Dependent Data, we would need to specify a "Valid From" date. (ADATU, in Table ANLZ) But, do we need to specify a "Valid To" date as well ?

My data is like this.....

PREREQUISITES: Asset Class =3D '9011'

SUBSTITUTION: Valid From is substituted by Constant '19.08.2001'
Cost Centre is substituted by Constant 'ZB02'

If I need to create a Rule, What would I need to enter ? I then created a WorkList, and assigned the Substitution to it. After this, I generated the Worklist in Background using AR31. Everything seems ok, but when I check the Assets, I still see the old Cost Centre, NOT the New Cost Centre.

--------------

Rules are not required. You get a ? because you probably started to create one and did not finish.

For a Cost centre mass change, if you want to have it time dependent, you must specify 'valid from' and 'valid to' in the substitution rule. In config you determine if you want to use the time dependency or not (default is : Yes)

SAP FICO Asset Master Data Upload SAP FICO FIXED ASSET

I am new to Asset Accounting while I have a potential job for mass upload of master data using transaction AS02. Focus is to convert the asset super number from an old reference to a new reference (to be determined by client), plus some other field modifications included in the request.

I would be using BAPI_FIXEDASSET_CHANGE for instance. What table/s I shall look into to explore the system requirements for this?

To make a mass change, you have two options:

1. If the change of the field can be put into an algorithm (e.g., enter XYZ as a super number for all assets in class 1234), you can use a mass change rule. You first define the mass change rule in the same way as you would define an asset substitution (IF something, THEN something else), then you go into the mass change transaction, select the right assets, the proper change rule ... and hit Execute.

2. Very often, it is easier to prepare the data in Excel and use transaction AS02 for the upload. Here, I can recommend transaction LSMW - you simulate (and record) the AS02 transaction on one fixed asset master, then follow all the steps proposed by the system (define fixed values, variables, etc.) and finally upload the Excel (.csv). System will automatically generate a batch input for all assets. It may take some time for you if you do it for the first time, but it is the best way if you would otherwise need to define complex algorithms.

So - use option 1 if you have a simple algorithm for many assets, and option 2 if "each case is different" or if you feel more comfortable in Excel than ABAP. Option 2 is simple, but of course takes some time to generate the upload and then run the batch sessions (while option 1 changes everything instantly in a matter of seconds).

I’ve read you post re mass changes of the fixed assets and also interesting in the transaction code for the mass changes.

Also I did not understand for LSMW how to simulate (record) AS02 transaction, could you pls describe more clear how to do it? Or better send the csv file as an example…

Here are the details:

I. To use mass change:

1. First, define a mass change rule in transaction OA02 (Accounting - Financial accounting - Fixed assets - Environment - Mass change rule). For each company code, you can define one rule (or a sequence of them). However, all of them will always be executed at the same time. Therefore, if you need to define different rules for different assets, you will have to do this repeatedly. Technically, this is done in the same way as AA substititution.

2. Once the rule is defined, you need to select assets for mass change. Go to transaction AR01 (Accounting - Financial accounting - Fixed assets - Environment - Worklist - Generate). Enter selection criteria like on any standard AA report, and run Execute. I cannot simulate this now on my system (we do not have AA), but it should ask what you want to do (mass change, mass retirement, etc.) and ask for a name of the worklist (write anything - e.g., Super number change). The system will show you a list of selected assets in a report format. Check it and make sure that it is correct. You may add or remove single assets from this (now cannot tell you how, but it is possible). If you are happy with the list, save it.

3. The last step is execution of the change. Go to transaction AR31 (same path as above), execute the report and if you are happy with the list (same as in step 2), press Save. System will show you a log of change (what went through, which errors occured). You are done.

II. LSMW
LSMW is a transaction, which will let you mass upload almost any other transaction (FB01, FD01, AS91, etc.). You do it in the following way:
1. Enter into transaction LSMW (no menu path), possibly in a development / test system
2. First, define a project, subproject and object (relatively formal task).
3. On the horizontal menu, go to Goto -> Recordings. Click on "Create recording".
4. Enter the name and description of recording (freely definable).
5. I cannot simulate this now in my system, but SAP will ask you about transaction code (AS02) and will take you into the AS02 transaction. In this step, do the change manually. Make sure you "touch" (change / write something) in all fields which you want to update.
6. Once you are done, save the recording and return on the start page of LSMW. Click "Execute".
7. You will see a list of tasks. Do them one by one. They should be relatively simple (and I cannot help you with them). Important is step 3 (maintain source fields) - here you define the columns of your excel (csv) file in the particular order. In step 5 (field mapping and conversion rule), you assign file columns to SAP fields (note that you will see only those fields which you "touched" during recording). You need to go through all the steps. In the end, you get (and run) a batch session.
8. If you did this in a development system, transport the LSMW object (menu Extras - Export project, Extras - Import project). You have to do it via file, not via standard transports of configuration (it is perhaps more simple).

Make sure you test it first in development or quality system!

SAP FICO Retire Asset with or without Revenue SAP FICO FIXED ASSET

Explain Retire Asset with Revenue and Retire Asset Without Revenue.

Asset sale

* Without customer - Transaction ABAON
- in case that a sale invoice is issued and posted in SD (or FI) and asset retirement is posted in FI-AA - Transaction ABAON.

* Between affiliated companies - Transaction ABT1N - asset transfer between company codes

* With customer known - Transaction F-92
- in case that a sale invoice is not issued and book through SD
but in FI-AA - Transaction F-92.

* The sale invoice posted in FI-AA - document posted in AA or FI (document type ZN) and issued (printed) by transaction what has to be modiffied.

Asset sale without customer - transaction ABAON (old t - ABAO)

In case you want system to calculate Gain/loss from sale for you enter Manual value (revenue amount) in specification for revenue. It is not allowed from the legal point of view for France.

If you want the asset to be retired in NBV choose which depreciation area (e.g.01 - management reporting area required) net book value should be posted.

Enter transaction type to specify the business operation you want to make.

(e.g. Retirement with revenue 210,

Retirement of new acquisition with revenue 260)

An asset retirement can refer to an entire fixed asset (complete retirement) or part of a fixed asset (partial retirement).

In case of partial retirement enter amount posted, percentage rate or quantity.

System calculates the gain/loss from the asset sale and makes posting on gain/loss on sales asset account.

The difference (gain/loss) is counted from NBV of the asset and the revenue amount (clearing account e.g.5700990)

Retirement without revenue - Transaction ABAVN

Retirement due to scrapping, donation, deficit, damage

Retirement without revenue is a removal of an asset from the asset portfolio without any revenue, for example, by scrapping. When you use this posting option, the system does not create revenue and gain/loss postings. Instead it creates a loss from an asset retirement without revenue posting in the amount of the net book value being retired.

Retirement without revenue transaction posts NBV to one account specified in account determination for each reason of disposal.

Additional account assignments with specific transaction types can be created to fullfill requirements of posting on different accounts for each or some of disposal reasons (e.g. different account for scrapping than for donation). This specific posting is allowed only for book legal depreciation area, for management area account for retirement due to all reasons is the same (e.g.5700000).

SAP FICO Tcodes for Configuring Assets Accounting

Tcodes for Configuring Assets Accounting

S.No TCODE PARTICULARS
1 EC08 COPY CHART OF DEPRECIATION
2 FTXP CREATION OF 0% TAX CODES
3 OBCL ASSIGN TAX CODES FOR NON-TAXABLE TRANSACTIONS
4 OAOB ASSIGN CHART OF DEP. TO COMPANY CODE
5 SPECIFY ACCOUNT DETERMINATION
6 CREATE SCREEN LAYOUT RULES
7 OAOA DEFINE ASSET CLASSES
8 AS08 DEFINE NUMBER RANGES FOR MASTER CLASSES
9 AO90 INTEGRATION WITH GL
10 OAYZ DETERMINE DEPRECIATION AREAS IN ASSET CLASSES
11 DEFINE SCREEN LAYOUT FOR ASSET MASTER DATA
12 AO21 DEFINE SCREEN LAYOURS FOR ASSET DEP. AREAS
13 FBN1 DEFINE NUMBER RANGES FOR DEP. POSTINGS
14 OAYR SPECIFY INTERVALS AND POSTING RULES
15 OAYO SPECIFY ROUND UP NET BOOK VALUATION
16 DEPRECIATION KEYS
17 DEFINE BASE METHOD
18 AFAMD DEFINE DECLINING BALANCE METHODS
19 AFAMS DEFINE MULTI LEVEL METHODS
20 AFAMP DEFINE PERIOD CONTROL METHODS
21 AFAMA DEFINE DEPRECIATION KEY
22 AS01 ASSET MASTER CREATION
23 AS11 CREATION OF SUB-ASSET
24 F-90 ASSET PURCHASE POSTING
25 AW01 ASSET EXPLORER
26 AFAB DEPRECIATION RUN
27 F-92 SALE OF ASSET
28 ABUMN TRANSFER OF ASSET
29 ABAVN SCRAPPING OF ASSET

SAP FICO Posting to Cost Center and Internal Order

Posting to Cost Center and Internal Order

If you have added the field Internal order in the Asset Master as a statistical order and you want your depreciation
posted not only to the cost center but also to this order.

In transaction OAYR in the IMG you define how depreciation posts to the depreciation posting rules - there is a CO assignment box where you have to tick both cost centres and internal orders.

What is internal order? Explain with example and how it is related to cost center.

An internal order is used to accumulate cost for a specific project or task for a specific time period. An internal order is therefore used for a short period with a specific deadline.

Your internal order will usually settle to cost centers (and not visa versa) according to the settlement rule in the order setup.

An internal order can therefore be used to group all the expenses incurred to plan and hold a conference over a 3 month period. The order can be settled on a monthly basis to cost centers. When the conference is finished the order can be settled finally. The cost of the conference will then be spread over 2 or more cost centers, but can be viewed in total on the internal order when needed.

Internal Orders - It is an instrument used to monitor costs and, in some instances, the revenues of an organization.

Uses of Internal orders
- Monitoring the costs of short-term jobs
- Monitoring the costs and revenues of a specific service
- On going cost control

Internal order categories
- Overhead Orders
- Investment Orders
- Accrual Orders
- Orders with revenue

Cost centers are not for specific job. e.g If you have open Trade-fair / exhibition (1 month period), then to allocate cost, you can use Internal Orders (Say IO) you can post to IO, and from their to various cost centers. If management were to ask you the cost of that exhibition, Internal Order will help you

Cost center is a responsible center in SAP. It cannot be defined as statistical but in transactions it may become as per other co objects.You will be able to find out the performance of the cost center using activities and plan values with actual value. This is lowest cost object in SAP. This will become a statistical object when you allocate the cost to other higher objects. Cost can be allocated to other cost centers or co objects but not fi objects like GL,assets, inventory etc. can be defaulted in transactions through cost element. It cannot be a cost object for a revenue element, revenues are always taken for other higher CO objects. No budget functionality is available but planning functionality is available and is always measured for a year in business.

Internal order is the second CO object - which can be defined as statistical or real. You will be able to define Budget and planning figures - more than one year also. Can control the postings of FI through budget controls. You can have the report of Plan vs actual including commitment. Cost cannot be allocated but settled through settlement rules and profiles. The receiver of the values can be any object not like Cost center - can be CO objects and FI objects. Ideal for R&D expenses capitalisations, etc. Status profile is linked to this which controls many individual transactions in each status which is a part of this Internal order. It can also receive postings of activities from Cost center. Settlement profile is an wonderful tool for variety of settlement - needed for FI and CO - legal requirements also and Revenue requirements also for any country.

All SAP CO orders like Production order, Plant maintenance order, etc will behave like Internal order with more functinalities.

SAP FICO Process Fixed Asset Depreciation

Process Fixed Asset Depreciation

Every asset transaction immediately causes a change of the forecasted depreciation. However, it does not immediately cause an update of the depreciation and value adjustment accounts for the balance sheet and profit and loss statements. The planned depreciation is posted to the general ledger when you run the periodic depreciation posting run. This posting run uses a batch input session to post the planned depreciation for each posting level for each individual asset as a lump sum amount.

The calculation and scheduling of depreciation, interest and revaluation are automatically controlled by keys in the system, or you can control them manually using a special posting transaction. In both cases, planned depreciation from Asset Accounting must be periodically posted to the corresponding asset and expense accounts of the general ledger. You carry out this posting using a batch input session. In addition to the various depreciation types, interest and revaluation, this batch input session also posts the allocation and writing off of special reserves.

When the system posts depreciation, it creates collective documents. It does not create separate documents for each asset.

Depreciation Posting Run is done via transaction code 'AFAB'.

The program creates batch input sessions for posting depreciation and interest to the G/L accounts in Financial Accounting and/or to Controlling.

Fields Description :-

Company code : Your Company Code

Fiscal Year : Your fiscal year

Posting period : Your depreciation period

Reason for posting run (choose one)

Planned posting run : X (default)

List assets : (tick if you want to see the detail)

Test run : (tick if you run in test mode else untick for production run)

Main asset number : (you can specify certain asset number if you click repeat run or test run)

Note :
Click the execute button if this is a test run.
Click the menu bar -> Program -> Execute in background if this is a production run.

You should get this message :
Background job was scheduled for program RABUCH00 and print out the output.

Release and Process the Batch Input Session in transaction code 'SM35'.

Process Session RABUCH00
X - Display errors only
Additional functions
X - Dynpro standard size

Click the Process button

If there is error, the system will pop up the error message.

Correct the error and recreate the session in transaction 'AFBD'.

Fields Description :-

Company code : Enter your company code

Fiscal year : Enter your fiscal year

Posting period : Enter your posting period

List assets : (tick if you want to see the detail)

Test run : (tick if you run in test mode else untick for production run)

Note :
Click the execute button if this is a test run.
Click the menu bar -> Program -> Execute in background if this is a production run.

You should get this message :
Background job was scheduled for program RABUCH00 and print out the output.

SAP FICO Asset Year-end Closing

Asset Year-end Closing

The year-end closing enable the company to produced the final balance sheet and profit and loss statement for its annual report, which has to be created to meet the particular legal obligations in each country.

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.

AJAB - Year-End Closing Asset Accounting

Company code : Your Company code

Asset classed asset u. const. : Optional

For fiscal year : Last closed fiscal year

Uncheck 'Test run' if this is a production run

At menu bar, click Program -> Execute in background.

Perform Fiscal year close for fixed Assets.

While doing a Test run, message is that fiscal year close could not be performed but it does not display any Asset details .It says Other Error. I am not able to identify what those other Errors could be.

Also, I have checked Incomplete Assets list As well but that list is empty as well. Also while running tcode AUVA there is a tab correct incomplete Assets, can anyone tell what deos that mean and when its to be used.

You can check and edit Asset accounting closing status using tcode OAAQ.

But you seem to be not clear on process.

AJAB is for closing Asset Accounting books.
AJRW is a technical step of changing fiscal year in system. If not done, it will not allow you to view asset reports in current fiscal.

Now, your error says incomplete asset. Please run ajab in test mode, check for details. It will give you asset details and error details as well. Go to asset explorere and check if the asst in question has been fully depreciated for the year.

If not run repeat deprecation for the asset in period 12 and then try closing asset books. You can also check asset and GL inconsitency using tcode ABST.

SAP FICO Asset Reverse Year-End Closing

Asset Reverse Year-End Closing

If you closed a fiscal year too soon, and still need to make corrections, you can reset the last closed fiscal year in Customizing for :-

Asset Accounting (Periodic processing -> Year-end closing -> Reverse).

Using this function, you can re-open the last closed fiscal year, either for selected depreciation areas in a company code, or for all depreciation areas in a company code. You do this by changing the field for the last closed fiscal year.

Be careful if you re-open a fiscal year only for certain depreciation areas, and you need to make adjustment postings only in these areas. You cannot use the standard transaction types for these postings, since the standard transaction types post to all depreciation areas. Instead, you have to define your own transaction types in Customizing for Asset Accounting (Transactions), limiting them to the required depreciation areas.

OAAQ - Reverse year-end closing for deprciation area

At the desired company code, change the fiscal year in 'Closed fiscal year' column.

Save entries and create a new request.

Change Asset fiscal year

AJRW - Asset fiscal year change

Company code : Your Company code

New fiscal year : Last closed fiscal year

Uncheck 'Test run' if this is a production run

At menu bar, click Program -> Execute in background.

SAP FICO Post Capitalization asset haven't been post in closed fiscal year

Post Capitalization (asset haven't been post in closed fiscal year)

If you realized that there are some fixed assets that haven't been post in a closed fiscal year,

Do the following steps :-

1. Reverse fiscal year closed by following the 'Reverse Year-end Closing' procedure.

2. Open the accounting fiscal year via transactin 'OB52'.

3. Post the fixed asset acquistions in the re-open fiscal year.

4. Repeat depreciation run for the last period of that closed fiscal year.

5. Repeat depreciation run for the last period depreciation run of the current fiscal year.

6. Closed fiscal year by following the 'Year-end closing' procedure.

7. Closed the accounting fiscal year via transactin 'OB52'.

SAP FICO Mass Change For Assets and Data Reset

Mass Change For Assets and Data Reset

How to reset Asset Data?

You can reset the entire AA data from Img->FA-> AA-> Preparing for production startup ->Tools -> Reset
company code.

This will reset only the asset accounting data from the company code. But before you perform this you have to make sure that you reverse all the transaction you have posted and have gone to the FI. As this reset will not effect FI GL data.

You can then reset the depreciation posted and then the recon accounts.

When you reset the recon accounts, it will enable you to post directly to the account like normal GL. Then you have to post JV and rectify you GL(recon account).

Then upload the correct data. After the data is uploaded set the recon accounts. this will reconcile the amount with the assets and activate the company code (in asset area). *-- Lakshmi

Mass change for assets

I am experiencing problems in OA02, Asset Mass Change. I am using 4.6C.

What happened was that I created the Substitution, then created the Step, and I then SAVED. I am not sure if I need to create a RULE or not. I have already defined in a STEP, (using Formula Builder) that most assets belonging to a certain asset class, 9011 with a current Cost centre, Z01, are to be assigned to another Cost Centre Z02, within the same Co.
Code. I then saved the Substitution, although I noticed that there was a "?" icon next to the RULES folder. I am well aware that for Time Dependent Data, we would need to specify a "Valid From" date. (ADATU, in Table ANLZ) But, do we need to specify a "Valid To" date as well ?

My data is like this.....

PREREQUISITES: Asset Class =3D '9011'

SUBSTITUTION: Valid From is substituted by Constant '19.08.2001'
Cost Centre is substituted by Constant 'ZB02'

If I need to create a Rule, What would I need to enter ? I then created a WorkList, and assigned the Substitution to it. After this, I generated the Worklist in Background using AR31. Everything seems ok, but when I check the Assets, I still see the old Cost Centre, NOT the New Cost Centre.

--------------

Rules are not required. You get a ? because you probably started to create one and did not finish.

For a Cost centre mass change, if you want to have it time dependent, you must specify 'valid from' and 'valid to' in the substitution rule. In config you determine if you want to use the time dependency or not (default is : Yes)

SAP FICO Asset Master Data Upload

Asset Master Data Upload

I am new to Asset Accounting while I have a potential job for mass upload of master data using transaction AS02. Focus is to convert the asset super number from an old reference to a new reference (to be determined by client), plus some other field modifications included in the request.

I would be using BAPI_FIXEDASSET_CHANGE for instance. What table/s I shall look into to explore the system requirements for this?

To make a mass change, you have two options:

1. If the change of the field can be put into an algorithm (e.g., enter XYZ as a super number for all assets in class 1234), you can use a mass change rule. You first define the mass change rule in the same way as you would define an asset substitution (IF something, THEN something else), then you go into the mass change transaction, select the right assets, the proper change rule ... and hit Execute.

2. Very often, it is easier to prepare the data in Excel and use transaction AS02 for the upload. Here, I can recommend transaction LSMW - you simulate (and record) the AS02 transaction on one fixed asset master, then follow all the steps proposed by the system (define fixed values, variables, etc.) and finally upload the Excel (.csv). System will automatically generate a batch input for all assets. It may take some time for you if you do it for the first time, but it is the best way if you would otherwise need to define complex algorithms.

So - use option 1 if you have a simple algorithm for many assets, and option 2 if "each case is different" or if you feel more comfortable in Excel than ABAP. Option 2 is simple, but of course takes some time to generate the upload and then run the batch sessions (while option 1 changes everything instantly in a matter of seconds).

I’ve read you post re mass changes of the fixed assets and also interesting in the transaction code for the mass changes.

Also I did not understand for LSMW how to simulate (record) AS02 transaction, could you pls describe more clear how to do it? Or better send the csv file as an example…

Here are the details:

I. To use mass change:

1. First, define a mass change rule in transaction OA02 (Accounting - Financial accounting - Fixed assets - Environment - Mass change rule). For each company code, you can define one rule (or a sequence of them). However, all of them will always be executed at the same time. Therefore, if you need to define different rules for different assets, you will have to do this repeatedly. Technically, this is done in the same way as AA substititution.

2. Once the rule is defined, you need to select assets for mass change. Go to transaction AR01 (Accounting - Financial accounting - Fixed assets - Environment - Worklist - Generate). Enter selection criteria like on any standard AA report, and run Execute. I cannot simulate this now on my system (we do not have AA), but it should ask what you want to do (mass change, mass retirement, etc.) and ask for a name of the worklist (write anything - e.g., Super number change). The system will show you a list of selected assets in a report format. Check it and make sure that it is correct. You may add or remove single assets from this (now cannot tell you how, but it is possible). If you are happy with the list, save it.

3. The last step is execution of the change. Go to transaction AR31 (same path as above), execute the report and if you are happy with the list (same as in step 2), press Save. System will show you a log of change (what went through, which errors occured). You are done.

II. LSMW
LSMW is a transaction, which will let you mass upload almost any other transaction (FB01, FD01, AS91, etc.). You do it in the following way:
1. Enter into transaction LSMW (no menu path), possibly in a development / test system
2. First, define a project, subproject and object (relatively formal task).
3. On the horizontal menu, go to Goto -> Recordings. Click on "Create recording".
4. Enter the name and description of recording (freely definable).
5. I cannot simulate this now in my system, but SAP will ask you about transaction code (AS02) and will take you into the AS02 transaction. In this step, do the change manually. Make sure you "touch" (change / write something) in all fields which you want to update.
6. Once you are done, save the recording and return on the start page of LSMW. Click "Execute".
7. You will see a list of tasks. Do them one by one. They should be relatively simple (and I cannot help you with them). Important is step 3 (maintain source fields) - here you define the columns of your excel (csv) file in the particular order. In step 5 (field mapping and conversion rule), you assign file columns to SAP fields (note that you will see only those fields which you "touched" during recording). You need to go through all the steps. In the end, you get (and run) a batch session.
8. If you did this in a development system, transport the LSMW object (menu Extras - Export project, Extras - Import project). You have to do it via file, not via standard transports of configuration (it is perhaps more simple).

Make sure you test it first in development or quality system!

SAP FICO Retire Asset with or without Revenue

Retire Asset with or without Revenue

Explain Retire Asset with Revenue and Retire Asset Without Revenue.

Asset sale

* Without customer - Transaction ABAON
- in case that a sale invoice is issued and posted in SD (or FI) and asset retirement is posted in FI-AA - Transaction ABAON.

* Between affiliated companies - Transaction ABT1N - asset transfer between company codes

* With customer known - Transaction F-92
- in case that a sale invoice is not issued and book through SD
but in FI-AA - Transaction F-92.

* The sale invoice posted in FI-AA - document posted in AA or FI (document type ZN) and issued (printed) by transaction what has to be modiffied.

Asset sale without customer - transaction ABAON (old t - ABAO)

In case you want system to calculate Gain/loss from sale for you enter Manual value (revenue amount) in specification for revenue. It is not allowed from the legal point of view for France.

If you want the asset to be retired in NBV choose which depreciation area (e.g.01 - management reporting area required) net book value should be posted.

Enter transaction type to specify the business operation you want to make.

(e.g. Retirement with revenue 210,

Retirement of new acquisition with revenue 260)

An asset retirement can refer to an entire fixed asset (complete retirement) or part of a fixed asset (partial retirement).

In case of partial retirement enter amount posted, percentage rate or quantity.

System calculates the gain/loss from the asset sale and makes posting on gain/loss on sales asset account.

The difference (gain/loss) is counted from NBV of the asset and the revenue amount (clearing account e.g.5700990)

Retirement without revenue - Transaction ABAVN

Retirement due to scrapping, donation, deficit, damage

Retirement without revenue is a removal of an asset from the asset portfolio without any revenue, for example, by scrapping. When you use this posting option, the system does not create revenue and gain/loss postings. Instead it creates a loss from an asset retirement without revenue posting in the amount of the net book value being retired.

Retirement without revenue transaction posts NBV to one account specified in account determination for each reason of disposal.

Additional account assignments with specific transaction types can be created to fullfill requirements of posting on different accounts for each or some of disposal reasons (e.g. different account for scrapping than for donation). This specific posting is allowed only for book legal depreciation area, for management area account for retirement due to all reasons is the same (e.g.5700000).

Archive