Open topic with left hand navigation

About Transactions

When an event involving allocations occurs, Proliance records the event in a transaction record. Proliance organizes transactions in transaction batches. A transaction batch contains all of the transactions that are associated with a specific user action, such as saving the document or changing a workflow state. For example, all of the transactions that Proliance generates when you approve a contract would belong to the same batch.

The transaction list provides a complete time-stamped picture of budget/cost management (BCM) activity over the life of the workspace. You can compare periods and analyze workspace information by creating a transaction batch report or query.

Proliance creates transactions whenever one or more of the following attributes of an active allocation is updated:

• Item Amount: When the amount is changed, Proliance records the difference between the old amount and the new amount. For example, if you change the value of a line item from 100 to 90, Proliance would record a transaction value of -10.
• Cost Account: When the cost account is changed, Proliance records one transaction for removing the allocation from the old cost account and another transaction for adding the allocation to the new cost account.
• ACR Column: When the ACR column is changed, Proliance records one transaction for the removal of the value of the allocation from the old ACR column and another transaction for the addition of the value of the allocation to the new ACR column.
• Book Type: When the book type is changed, Proliance records one transaction for the removal of the allocation's amount from the old book type. Another transaction records the addition of the allocation's amount to the new book type.
• New allocation/Active allocation: When a new allocation is created or an allocation becomes active, Proliance creates a single transaction recording the amount, cost account, ACR column, and book type.

• Unit Code: The unit code that applies to the cost account allocation. The unit code identifies what is being "bought", to help you identify items across different line items in different documents in Proliance.

• Reporting Code 1: These are the reporting codes that were assigned to help categorize the cost account allocations. These codes were assigned either from the Cost Account Allocation Grid or the Schedule of Values page.

• Reporting Code 2: These are the reporting codes that were assigned to help categorize the cost account allocations. These codes were assigned either from the Cost Account Allocation Grid or the Schedule of Values page.

• Reporting Code 3: These are the reporting codes that were assigned to help categorize the cost account allocations. These codes were assigned either from the Cost Account Allocation Grid or the Schedule of Values page.

• Project: When the project is changed, Proliance records one transaction for the unlinking of the old project, and another transaction records the linking of the new project.

Some examples that can trigger an update to any one of the above are:

• An allocation is added to a document.
• A state change to a controlling document activates an allocation or change to the ACR column.
• A drawdown from the allocation occurs.
• The value of the allocation increases because it is a source cost allocation for a drawdown, and the value of the controlling line item decreased.
• An allocation on a document that affects the Budget/Cost Management module is edited.