Within Asset Accounting, asset transaction types identify individual business transactions. A transaction type has to be entered for each transaction that affects assets. Either you make this entry yourself in the posting transaction, or the entry is automatic, based on specifications made in FI-AA Customizing (Transactions).

Each transaction type is assigned to a transaction type group. The business transactions are subdivided on the basis of the transaction type group into:

• Transactions that influence the acquisition and production costs of fixed assets These include: Acquisitions, retirements, transfer postings, post-capitalization

• Down payments

• Investment support measures

• Manual depreciation

• Write-ups

The transaction type group, to which a which a transaction type belongs, determines the following:

• Which value fields are updated in the year segments

• Whether the transaction refers to the past (for example write-ups) or to the current fiscal year

• Whether the total of the transactions of a group is positive or negative with reference to a fiscal year

• According to which rule the start period for the depreciation calculation is determined

• In which G/L accounts posting is to take place

• Whether the acquisition date of the fixed asset is set on the date of the first transaction of a group

• Whether proportional accumulated depreciation can be entered for a transaction (for example during post-capitalization), or is to be determined by the system (for example with asset retirements).

The number of possible transaction type groups, as well as the characteristics of the individual groups, is specified in the system and cannot be changed.

The system carries out a check for the asset class of the fixed asset involved when you post with a transaction type of the down payment group. This means that you can only post to fixed assets using these transaction types if you defined this in the asset class.

The individual transaction types determine the following:

Some of these specifications are dependent on the transaction type group, and are mutually exclusive. You cannot make specifications that are inconsistent with the transaction type group.