Transaction Details Import Definitions

• • Often the Transaction information imported into Moorgate is aggregated from the individual client data

  • There are situations where having access to this underlying data can be useful in identifying why transactions and confirmations don't match exactly

  • Moorgate allows you to import the details records and map them to the correct transaction

  • Navigate to Setup>Transaction Detail Imports to configure an import

  • Navigate to Setup>Transaction Detail Mapping to configure the correct mapping

Transaction Detail 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

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

Transaction Details Mapping

• The Transaction details are imported and linked to the correct transaction records based on the mappings

• Mappings should be unique enough to ensure the correct details are associated with the correct transactions

• The mapping is used when the user requests to see the details, not on import