Transaction Import Definitions

• Transaction Import Definitions are used to import the expected position of the accounts into Moorgate. This data is sourced from your internal transaction system and should match the order data submitted to the ManCo's.

• This data is typically imported daily and can de done so manually or via the Moorgate Process Schedule.

• Navigate to Setup>Transaction Import Definitions to add one

Transaction Import Definition Settings

Database Type: SQL, Oracle or Oracle Stored Procedure

Connection String: Database and Server to get the data from

SQL: Data Source=Server;UID=User;pwd=Password;Initial Catalog=Database;

Oracle: User ID=User;Data Source=Server;Persist Security Info=True;Password=Password

SQL: Query to return and map the data - see the links on the left for guidelines

Transaction Type Determines Sign: If Moorgate should use the Transaction Type to determine the sign (+ve or -ve) of each transaction. Based on the Transaction Type table mappings

Override Balance Check: Determine whether Moorgate should perform standard balance checks on each batch: Opening Balance = Previous Closing Balance and Opening Balance + Sum(Transactions) = Closing Balance

Balance Check Tolerance: Only applicable if Override Balance Check is False. Allows a small difference on the balance checks: abs(Opening Balance - Previous Closing Balance) <= Tolerance AND abs (Opening Balance = sum(Transactions) - Closing Balance) <= Tolerance. The balances from the source are preserved in both of these scenarios

Source Key Field: Unique Key in the Query to keep track of where to start the next import from.

SQL use @[SourceKeyFieldName] in the query

Oracle use :[SourceKeyFieldName] in the query

Uses a Greater than (>) relationship in the where clause

Source Key Field Type: Int or Number

Source Last Key: The Key Value of the last record imported. Moorgate will replace the Source Key Field with this value when it executes the query to get the latest data