Transaction Codes View

Additional Fields that the Transaction should allow the user to see and edit, these include:

• Price
• Units
• Settlement Date

This holds if the Transaction directly records a Path or not:

• None
  This is the default indicating the Transaction doesn't store the Path to use to allocate the values. Instead it dynamically obtains it through the Instrument and Mappings when required.
• Auto From Instrument
  This indicates the Path should be stored against the Transaction, and is obtained from the Instrument and Mappings.
  Unlike None, this then holds the Path statically against the Transaction. If the mapping changes later this Transaction will still allocate using the old Path
• Manual
  This indicates the User should select a Path for the Transaction to use.

This indicates how the system should automate GL Postings:

• Auto
  This is the default and indicates any GL Postings configured against this Transaction Code or the Transaction Values should be automatically created
• None
  This indicates no GL Postings are allowed on these Transactions and none will be automatically created by the system
• AutoWithOverride
  This indicates the system should automatically create GL Postings but that the User can also manually override their calculated values
• Manual
  This indicates the User can manually add individual journal entries themselves

This dictates how the system should Allocate these values of the Transaction:

• None
  This is the default and indicates the Transaction doesn't store the breakdown allocations of any values. Rather they are dynamically calculated when required from the Path of the Transaction
• Automatic
  This indicates the system should breakdown the Transaction Values by the allocations acquired from the Transaction Path automatically.
  Typically used with Capital Transactions as this actually stores the allocated amount of the Transaction Values by ultimate owning entity as well as just the Transaction Values themselves.
• AutomaticWithOverride
  This indicates the system should breakdown the Transaction Values by the allocations acquired from the Transaction Path automatically. It also allows users to override those values.
• AutomaticWithOverrideAndNewEntities
  This behaves the same as AutomaticWithOverride but also allows the User to add their own ultimate owning Entities as part of the breakdown allocations even if they are not in the Path.

This indicates if this Transaction allows sub-Transactions to be created as part of it:

• None
  This is the default meaning Transactions exist stand alone
• Auto
  This indicates this Transaction can have child Transactions but that they are automatically created by custom processes
• Manual
  This indicates that this Transaction can have child Transactions and that the User can create them manually.

Sub Transactions are still real Transactions in their own right and are treated that way by reporting, etc. However they always have the same Transaction Code and other settings as the Parent Transaction, and are related to them for usability, reporting, and calculations.