Fixed asset transaction

[Former Member]

I have a problem with fixed asset transaction.

I tried to dispose of the fixed asset using 210, but I met the following error message. I guess there is inconsistent data in asset master. It doesn't have depreciation area "10". Please help me.

<b>Data inconsistency: Area 10 for value takeover is missing

Message no. AAPO 105

Diagnosis

According to its formula, depreciation area 11 is defined for mandatory takeover of values from depreciation area 10. However, depreciation area 10 was not posted during the current transaction (chart of depreciation 0010). This is not allowed.

Procedure

Check the specifications for the current transaction type.</b>

[Former Member · Accepted solution]

Hi Jake,

Looks like a new depreciation area must have been added to the COD. this particular asset might have been created before the change. Hence the new area must not have come into this asset. Execute T Code AFBN, give the new dep area and COD and execute. This Transaction updates the missing Dep area in all the assets in that particular COD.

Regards

Sridhar

[Former Member · Accepted solution]

Hi Sridhar,

Thank you very much.

I've added the depreciation area to COD.

I really appreciate.

Thanks,

Jake

[Former Member]

Hello

Are you disposing with revenue or without.

Asset Sale with Customer

The system enables you to post the entry to Accounts Receivable, the revenue posting and the asset retirement in one step. In this posting transaction, you have to post the revenue (debit A/R, credit revenue from asset sale) first, and then post the asset retirement. An indicator in the posting transaction specifies that the system posts the asset retirement after the revenue posting.

The prerequisite for this is that the sales revenue account in Financial Accounting, to which the revenue should be posted, has a field status variant in its master data in which the Asset retirement field (category Asset Accounting) is defined as a required or optional entry field. You define the field status variant in Customizing for Financial Accounting (Financial Accounting Global Settings ® Document ® Line Item ® Controls).

Posting of Gain or Loss

When you use the standard transaction types, the system automatically creates a gain posting or a loss posting, as well as a revenue clearing entry, in addition to the asset and accumulated depreciation correction postings. This gain/loss posting, as well as the revenue posting, are not dependent on the transaction type. The automatic creation of these postings is controlled by the Gain/loss from retirement indicator in the definition of the transaction type. You can also choose not to set this indicator, in which case you have to enter the postings manually

Transaction Type (Prior-Year Acquisitions/Current-Year Acquisitions)

Make sure that you select the correct transaction type for both partial and complete retirement. For the complete retirement of a fixed asset acquired in previous years, always select a transaction type intended for prior-year acquisitions. A partial retirement can always relate either to prior-year acquisitions or to current-year acquisitions.

The complete retirement of a fixed asset is only possible if all transactions to the asset were posted with a value date before the asset value date of asset retirement. You must clear or reverse down payments and investment support measures, which are in the same posting year as the retirement, before you post the complete retirement.

Prior-year asset acquisitions and current-year acquisitions are shown separately from one another in the document

Check these menu paths:

SAP Easy Access screen ® Accounting ® Financial Accounting ®Fixed Assets ® Posting ® Acquisition ® External Acquisition ® Acquis. w/ Autom. Offsetting Entry

· SAP Easy Access screen ® Accounting ® Financial Accounting ®Fixed Assets ® Posting ® Transfer ® Transfer within Company Code

· SAP Easy Access screen ® Accounting ® Financial Accounting ®Fixed Assets ® Posting ® Retirement ® Retirement w/ Revenue ® Asset Sale Without Customer

Reg

*assign points id useful