Work with transaction origins (AACD10701)

Related topics

Setting up DC1 Asset Management

These entries represent the different transactions that are created in DC1 Asset Management, one origin per G/L posting. The origins are predefined and you can only change their descriptions. You can obtain a printout of the contents in the table from the Table printout program selection.

A transaction like the acquisition can, e.g., be represented by two transaction origins:

The acquisition balance account posting
The financial movement posting

The transaction origins are fixed numerical values, but you may define a G/L transaction type which will represent the transaction origin in the account code used in DC1 Asset Management. The G/L transaction type is the fixed part of the account code.

The system is preloaded with suggestions for G/L transaction types, but you may change them as you may change the descriptive text. The new G/L types must then first be established in Work with G/L transaction types.

The following transaction origins exist:

Origin	Description
001	Preliminary acquisition balance
002	Acquisition balance
011	Depreciation balance
012	Depreciation credit 1
013	Depreciation debit 1
014	Depreciation credit 2
015	Depreciation debit 2

102	Disposal reverse acquisition
111	Disposal reverse depreciation

121	Disposal sales value
122	Disposal profit
123	Disposal loss

132	Disposal P/L acquisition
141	Disposal P/L depreciation

202	Financial movement acquisition
211	Financial movement depreciation

302	Asset movement acquisition
311	Asset movement depreciation

411	Disposal transfer depr

The origins 001 and 002 are used during asset entry into the Asset file. If the Wait file is used, then the preliminary account will not be necessary. If the transaction types for both origins (001 and 002) are equal, then no transactions will be generated during the asset entry.

The origins 011 to 015 are connected to the depreciation run. The balance account is used if the depreciation is an external depreciation. The depreciation amount 1 is connected to origins 012 and 013. The amount 2 is connected to origins 014 and 015.

The disposal routine will create transactions with origin 102 and 111 reverse the acquisition and the balance depreciation. The origins 121, 122 and 123 are used if the disposal calculation code is 1 in the ASM control file. The origins 132 and 141 are used if the disposal calculation code is 2 in the ASM control file.

The codes 1 and 2 have the following meaning:

Code	Description
1	Profit and loss calculations
2	Only reversal of balances

The financial movement of the acquisition value is performed with the origin 202. This is the case when the acquisition value booked in the A/P differs from the information in DC1 Asset Management. The balance depreciation is moved with origin 211.

The origins 302, 311 and 411 are used to handle the balances in the DC1 Business Information Warehouse application.

The asset movement of the acquisition value is performed with the origin 302. It will work in a similar way as code 202 for account movements, but regards movements between statistical keys in DC1 Business Information Warehouse that are not necessarily accounting related, for example asset quality. The asset depreciation is moved with origin 311.

The origin 411 is a system internal help transaction code for balance file updating. It is used to take care of disposals that will not have depreciation balances reversed when disposed, i.e. depreciation types marked as internals.

Options

Selection fields

Origin: This column lists the predefined transaction origins.

Description: Displays the description of the related transaction origin.

G/L type: Displays the type from Work with G/L transaction types defined for the related transaction origin.

Work with transaction origins (AACD10704)

Function keys

Transaction origin: This field is protected and represents the transaction origin you are maintaining.

G/L transaction type: You may change to another type from Work with G/L transaction types. If left blank, then the transactions created will have no G/L postings.