Open topic with left hand navigation

Line Item Detail Viewer - Transactions Tab

Each allocation belongs to a transaction batch. Proliance generates a transaction batch whenever someone performs an action that changes a document with allocations. A transaction batch contains the transactions associated with the change of a document's status.

Transaction batches can be triggered when a user performs the following actions:

• Activates or Deactivates a BCM Line item
• Changes the Workspace Currency Amount
• Changes the Cost Account
• Changes the BCM Column
• Changes the Book Type
• Changes the Project

Transactions Tab Information

The Transactions tab of the Line Item Detail Viewer shows the following information for each transaction. By default, the transactions are sorted by batch, but you can sort the transactions by any of the columns:

• Batch ID: An identification number for the transaction batch. Proliance creates this number. You cannot edit it. The Batch ID is unique within your workspace.
• Amount / Variance: The amount of money added to or subtracted from the allocation by the transaction. A subtracted amount is shown as a negative value and an added amount as a positive value.
• Batch Date/Time: The date and time of the transactions in the transaction batch.
• Batch Action / Description: A description of the action that caused the transaction batch that the transaction belongs to. For example this may be as a result of a 'State Change' or other similar event.
• Company: The Company that the Transaction was logged against.
• User: The User that logged the transaction.
• Transaction Description: A description of the what the Transaction actually achieved. For example in a state change transaction, this field may have a value of "Inactive -> Active" which records that the contract in question moved from an Inactive to an active state.
  This description will provide details pertinent to the type of transaction it refers to.
• ACR Column: The ACR column that the allocation was assigned to when the transaction was completed.
• Cost Account Ref: The cost account affected by the transaction.
• BCMUOM: The BCM Unit Of Measurement for the transaction.
• BCM Quantity: The BCM Quantity involved in this transaction.
• Quantity Variance: Quantity Variance is the difference between old and new Quantity values in the specific BCM line item.
  
  For example, if there is a BCM line item with a Unit Price = 10 and Quantity = 5, and Amount = 50.
  
  If a user changes the Unit Price = 20 and leaves Quantity = 5, the Amount will change to 100.
  
  In this case then, the Amount Variance = 50, the Unit Price Variance = 10 and the Quantity Variance = 0.
• Unit Price:The Unit Price involved in the BCM Transaction.
• Unit Price Variance:Unit Price Variance is the difference between old and new Unit Price values in the specific BCM line item.
  
  For example, if there is a BCM line item with a Unit Price = 10 and Quantity = 5, and Amount = 50.
  
  If a user changes the Unit Price = 20 and leaves Quantity = 5, the Amount will change to 100.
  
  In this case then, the Amount Variance = 50, the Unit Price Variance = 10 and the Quantity Variance = 0.
• Currency Rate: The exchange rate used for converting the defined currency to the workspace currency.
• Currency Rate Variance: Currency Rate Variance is the difference between old and new Currency Rate values in the specific BCM line item.  
• 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.
• Project:The Project associated with the BCM line item transaction.
• 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.
• Book Type: The book type of the allocation when the transaction was completed.
• Pivot Type: The value that remains constant when Proliance recalculates the formula:
  
  Amount = Quantity * Unit Price
  
  This constant value, known as the pivot type, is used as the default when Proliance creates Allocated BCM child rows for the allocation.
• Drawdown Type: Specifies whether the draw down is by lump sum or by quantity.
• Transaction ID: An identification number for the transaction. Proliance creates this number. You cannot edit it. The Transaction ID is unique within your workspace.