Transaction Id

Some Accounting objects use the <transactionId> element. It is not included in the data map tables, as it resides in the <header> part of the EagleML message.

Xpath: EagleML/accountingTransaction/header/identifier/transactionId

For example, Accounting Cash Expense

<EagleML xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" eaglemlVersion="2-0" eaglemlType="AccountingTransactionMessage" xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0 eagleml-main-2-0.xsd" xsi:type="AccountingTransactionMessage">
<accountingTransaction>
    <header>
        <identifier>
            <transactionId>A8QOPENFRKOING23</transactionId>
        </identifier>
        <objectType>AccountingCash</objectType>
    </header>
    <accountingCash>
        <entityId>QAEMLTST</entityId>
        <cashTransactionType>MISCEXP</cashTransactionType>
        <tradeDate>2004-12-26</tradeDate>
        <units>93.12</units>
        <cashCurrency>THB</cashCurrency>
        <autoSettleIndicator>N</autoSettleIndicator>
        <recPayCategory>ACCOUNTING FEES</recPayCategory>
        <custodianBankCode>1AA</custodianBankCode>
        <custodianBankName>1AA</custodianBankName>
        <custodyBankAccount>1AA</custodyBankAccount>
        <cashAccountName>CASH</cashAccountName>
        <cashAccountNumber>1</cashAccountNumber>
        <originalTradeTicketNumber>1</originalTradeTicketNumber>
        <ledgerNoteDescription>AAA</ledgerNoteDescription>
    </accountingCash>
</accountingTransaction>
</EagleML>

TransactionId should be unique for a record.

When you load a message with <transactionId> not defined, its value is generated as GUID (rule file: set_transaction_id_content.inc):

<COL TAG="25" EXPRESSION="Iif(StringLength(|transactionId|)>0, |transactionId|,Iif(StringLength(|transactionId2|)>0, |transactionId2|,GUID()))" CONTENT="TRANSACTION_ID"/>

It is mapped into tag 25.