External System Financial TransactionsAdapter

External System Financial TransactionsAdapter

ContentsExternal System Financial Transactions Adapter 2

Commercial In Confidence 3

External System Financial Transactions Adapter 4

Overview 4

Process 4

OAGIS Message 4

Foreign Keys 4

Concurrent Updates 5

Methods 5

Post 5

Post Message Mapping 5

Notes 7

Acknowledge 7

Acknowledge Message Mapping 7

Notes 7

Message Examples 8

Notify 8

Post 9

Acknowledge 11

Commercial In ConfidenceCopyright 2016 ABB

All Rights Reserved

Confidential and Proprietary

Legal Disclaimer

The product described in this documentation may be connected to, and/or communicate information and data via, a networkinterface, which should be connected to a secure network. It is your sole responsibility to ensure a secure connection to thenetwork and to establish and maintain appropriate measures (such as but not limited to the installation of firewalls, applicationof authentication measures, encryption of data, installation of antivirus programs, etc.) to protect the product, the network,your systems, and the interface against any kind of security breach, unauthorised access, interference, intrusion, leakage,damage, or corruption or theft of data. We are not liable for damages or losses related to any such security breach,unauthorised access, interference, intrusion, leakage, damage, or corruption or theft of data.

External System Financial Transactions Adapter

OverviewWith the standard Finance integration model for Ellipse 8+, the Financial Transactions Integration will include Journal entriesbeing sent from Ellipse to the Master system.

For the External System Financial Transactions adapter, the Ellipse business elements outlined below can be accessed:

• General Ledger TransactionsAll fully posted financial transactions that are generated in Ellipse are sent to the ERP in the form of Journals to update thefinancial balances of ERP Accounts for financial reporting purposes. There is a provision to excludes certain transactions frombeing exported from Ellipse to the ERP. This is managed by a flag setting on the expense element and general ledger codes inEllipse.

All Ellipse journal transactions (MSF900) will be the basis of the finance data to be transferred to the external ERP All Ellipsetransactions apart from invoice approval transactions for Suppliers flagged as External Suppliers (and so maintained in theexternal ERP rather than Ellipse), will be processed as a Journal into the external ERP. Invoice Approval transactions for ExternalSuppliers will be processed as an Invoice in the external ERP.

There are two new Ellipse transactions that will not be processed into any external ERP as a result of the integration. One onthe transfer of the invoice to clear the AP account, and the other on the payment confirmation where Ellipse generates atransaction to clear the Payment Clearing account to Invoices Paid account. The accounts Payment Clearing and Invoices Paidare new control accounts and are only applicable for the integration.

The adapter relies on the Ellipse Transaction Interface (MSBISA) process being executed to create the date to be processed inthis interface. The Transaction Interface (MSBISA) process will read through the Journal transactions (MSF900) starting at thelast transaction that it read. It will process the journal transaction (MSF900) records and either update the Transaction Interfacetables (MSFISA or MSFISB) tables depending on whether the transaction set has been posted. The Transaction Interface(MSBISA) process will only write a complete set of successfully posted transactions to MSFISA table. Transactions posted withwarning are not written to Transaction Interface (MSFISA) table. All transactions within the transaction group key must havebeen posted. The external ERP system will receive a complete balanced set of accounting transactions within a transactiongroup. The external ERP system will acknowledge the transaction group as either having been successfully processed or not.The status of the transaction group in Ellipse will be updated to reflect the processing in the external ERP system.

The transactions extracted by MSBISA are able to be viewed in Ellipse via MSEISA application. This application details thenormalized data and the status of the transaction in regards to integration.

ProcessThe External System Financial Transactions adapter has been developed to operate within an end-to-end integration solutionwith an external ERP system.

An overview of the expected end-to-end process is as follows:

• Transactions are generated in Ellipse as per standard Ellipse processing.

• Transactions are posted via the Batch Posting Update (MSB900) process.

• Complete sets of successfully posted transactions are written by the Transaction Interface (MSBISA) process.

• These transactions are marked with a status of 'I', ready to import.

• The External System Financial Transactions adapter pushes ready to import transaction data to the ERP.

• These transactions are then marked with a status of 'S', sent to ERP.

• The ERP is expected to acknowledge the transactions it has received from Ellipse as either processed successfully orunsuccessfully.

• The External System Financial Transactions adapter then updates the status of the journal transaction data on theTransaction Interface (MSFISA) table as either 'X' (Exported) or 'A' (Aborted).

OAGIS MessageJournalEntry noun The OAGIS standard contains a noun called JournalEntry, this has been used to represent the EllipseJournal Transaction entity. Only some of the Ellipse attributes held for a Journal Transaction entity can be mapped to attributesunder the JournalEntry noun. Where Ellipse attributes cannot be mapped to attributes under the JournalEntry noun, this hasbeen extended through the use of Extension/AnyExtension group.

The OAGIS verbs Post and Acknowledge will also be supported.

Foreign KeysN/A

Concurrent UpdatesN/A

Methods

PostThe post method calls the following Ellipse service to extract the data required:

• ExternalSysFinancialTransactionsFor the initiation of post processing in EIP there are 2 options available:

1. Polling

2. Trigger MessageWhere the polling option is required this is controlled via a timer process in EIP. To enable the extract of Journal transactions 2properties must be set:

1. mib.finance.journalExtract=true

2. mib.finance.journalTimer=0 */60 * * * ?The timing of this will be configurable via the property mib.finance.journalTimer. The property value set must be a valid cronexpression. It is recommended that the cron expression defines a time to begin adapter extract execution after the Ellipsebatch Transaction Interface process (MSBISA) has run. In addition the property mib.finance.journalExtract must be set to true.

Where the extract of Journal transactions is not required the properties should be set as follows:

1. mib.finance.journalExtract=false

2. mib.finance.journalTimer=59 23 31 12 0 ?In addition the following properties will need to be defined via the EIP console to provide the credentials that will be used tologin to Ellipse when the ExternalSysFinancialTransactions is called to extract the data from Ellipse:

1. ellipse.proxyUser

2. ellipse.proxyDistrict

3. ellipse.proxyPositionWhere the trigger message option is required this is controlled by an external system sending a message to a queue in EIP. Toenable the extract of Journal Transactions the external system must send a NotifyJournalEntry message to theMIB.JOURNAL.GW queue in EIP. This message must contain an Authorisation element with the credentials that will be used tologin to Ellipse when the ExternalSysFinancialTransactions is called to extract the data from Ellipse. An example of this elementis as follows:

<ip1:AuthorizationContext xmlns:ip1="http://www.ventyx.com/IP/1"> <ip1:Proxy> <ip1:UserID>INTEGRAT</ip1:UserID> <ip1:OrgID>R100</ip1:OrgID> <ip1:Role>INTEGRAT</ip1:Role> </ip1:Proxy></ip1:AuthorizationContext>

For either the Polling or Trigger Message initiation options, a new Notify Journal Entry message is sent to the MIB.JOURNAL.GWqueue. The adapter is initiated (by the Notify Journal Entry message on the MIB.JOURNAL.GW queue) and the post methodretrieves a single group of transactions from the Transaction Interface table (MSFISA). The transaction details are output in aPostJournalEntry message that is placed on the MIB.JOURNAL.REPLY queue for consumption by the ERP system. A new NotifyJournal Entry message is then placed on the MIB.JOURNAL.GW queue. The adapter post method then attempts to retrieve thenext group of transactions from the Transaction Interface table (MSFISA) process.

• Where there is a transaction group with a status of 'I', ready to import the process above is repeated.

• Where there is no transaction group with a status of 'I', ready to import the adapter stops processing.

Post Message MappingMapping of Ellipse web service attributes to OAGIS PostJournalEntry message.Field Description Validation Service Attribute<JournalEntry> <JournalEntryHeader> <DocumentDateTime>dateTime Creation Date and Time ExternalSysFinancialTransactions creationDate / creationTime <EntryCreator> <ID>string Creation By User creationUser </EntryCreator> <GLEntityID>string District Code districtCode <SourceDocumentReference>

<DocumentDateTime>date Transaction Date transactionDate <Type>string Document Type documentTypeIsa <DocumentID> <ID>string Transaction Group Key transactionGroupKey </DocumentID> <ID>string Transaction Group Key (alternate element) transactionGroupKey </SourceDocumentReference> <CurrencyExchangeRate> <SourceCurrencyCode>string Invoice Currency invoiceCurrency <RateNumeric>decimal Exchange Rate exchangeRate </CurrencyExchangeRate> <AccountingDate> <PeriodID>string Fiscal Period Id fiscalPeriod <Year>string Fiscal Year fiscalYear <PostDateTime>string Posting Date postingDate </AccountingDate> <Party> <PartyIDs> <ID>string Supplier Number supplierNo </PartyIDs> </Party> <Extension> <AnyExtension> <InvoiceReference> <DocumentDateTime>date Invoice Date invoiceDate <DocumentID> <ID>string Invoice Number invoiceNumber </DocumentID> </InvoiceReference> <ProcessDateTime>string Process Date processDate <Rec900Type>string MSF900 Record Type rec900Type <ExternalSystemId>string External System COA Reference externalSystemId <ProcessStatus>string Process Status from MSFISA record procStatusIsa <EntryCreator> <UserNumber>string User Number userNumber </EntryCreator> </AnyExtension> </Extension> </JournalEntryHeader> <JournalEntryLine> <TaxBaseAmount>decimal Tax Amount taxAmount <FunctionalAmount>decimal Invoice Amount invoiceAmount <GLAccount> <GLNominalAccount>string Account Code accountCode </GLAccount> <EnterpriseUnit> <GLEntityID>string District Code districtCode <CostCentreID>string Cost Centre Cost Centre </EnterpriseUnit> <Amount>decimal Transaction Amount transactionAmount <Extension> <AnyExtension> <SourceDocumentReference type=''> Transaction Type tranType <ID>string Transaction Number transactionNumber <Description>string Transaction Description tranTypeDesc <SequenceCode>string Transaction Sequence No transactionSequence </SourceDocumentReference> <ProcessDateTime>date Process Date processDate <Rec900Type>string MSF900 Record Type rec900Type <Tax> <ID>string Additional Tax Code ataxCode <Calculation> <RateNumeric>decimal Additional Tax Rate additionalTaxRate </Calculation> </Tax> <Indicators> <ExportExclude>string Export Exclude Switch exportExcludeSwitch <DebitCredit>string Debit / Credit Indicator debitCreditIndicator </Indicators> <Return> <Code>string Return Code returnCode <Description>string Return Code Description returnText </Return> <SentDateTime>dateTime Sent Date / Time sentDate / sentTime <Invoice> <InvoiceHeader> <DocumentID> <ID>string Invoice Number invoiceNumber

</DocumentID> <ReceiptDate>date Invoice Receipt Date invoiceReceiptDate </InvoiceHeader> </Invoice> <AssetID>string Asset Id assetNumber <SubAssetID>string Sub-Asset Id subAssetNumber <CustomerAccountID>string Customer No customerNumber <EquipmentID>string Equipment Number equipmentNumber <ItemNumber>string Item Number itemNumber <ProjectNumber>string Project Number projectNumber <PurchaseOrderReference> <Note>string Purchase Order Item purchaseOrderItem <DocumentID> <ID>string Purchase Order Number purchaseOrderNumber </DocumentID> </PurchaseOrderReference> <RelatedEntityCode>string Related Entity Code relatedEntityCode <StockCode>string Stock Code stockCode <Party> <PartyIDs> <ID>string Supplier Number supplierNo </PartyIDs> </Party> <WorkOrder>string Work Order Number workOrder <AccountsReceivable>string Accounts Receivable Invoice Number accountsReceivableInvoiceNumber <Requisition> <Item>string Requisition Item Number requisitionItem <DocumentID> <ID>string Requisition Number requisitionNumber </DocumentID> </Requisition> </AnyExtension> </Extension> </JournalEntryLine></JournalEntry>

NotesTransaction Group

The adapter will return all transactions in a single Transaction Group for each PostJournalEntry message.

AcknowledgeThe acknowledge method calls the following Ellipse service to update the data required:

• ExternalSysFinancialTransactionsFor each Transaction Group passed to the external ERP system via a PostJournalTransaction message, it is expected that theERP will acknowledge the transaction group as either having been successfully processed or not. The ERP will return anAcknowledgeJournalEntry message that is placed on the MIB.JOURNAL.ACK queue for consumption by the Ellipse system. Theacknowledgement messages returned from the external ERP system will be used to update the status of the transaction groupin Ellipse to reflect the processing in the external ERP system.

Acknowledge Message MappingMapping of OAGIS AcknowledgeJournalEntry message attributes to Ellipse web service.

Field Description Validation Service Attribute<JournalEntry> <JournalEntryHeader> <SourceDocumentReference> <DocumentID> <ID>string Transaction Group Key ExternalSysFinancialTransactions transactionGroupKey </DocumentID> </SourceDocumentReference> <AccountingDate> <PeriodID>string Period id value. fiscalPeriod <Year>string Year id value. fiscalYear </AccountingDate> </JournalEntryHeader></JournalEntry>

NotesResponse Criteria

In addition to the passing of the Transaction Group Key value in the message sent to Ellipse, the status of the update of this inthe ERP is required. The status of the update passed back in the acknowledgement must be either 'Accepted' or 'Rejected'.This is required to be supplied as followed in the Acknowledge message under the DataArea element as follows:

Accepted:

<oa:Acknowledge> <oa:ResponseCriteria> <ResponseExpression actionCode="Accepted">ID=R10020120504362753100006KJIM </ResponseExpression> <ChangeStatus> <Reason></Reason> </ChangeStatus> </oa:ResponseCriteria></oa:Acknowledge>

Rejected:

<oa:Acknowledge> <oa:ResponseCriteria> <ResponseExpression actionCode="Rejected">ID=R10020120504362753100006KJIM </ResponseExpression> <ChangeStatus> <Reason></Reason> </ChangeStatus> </oa:ResponseCriteria></oa:Acknowledge>

Fiscal Periods

Some journal transaction groups can have transactions that are split across fiscal periods. Where the Finance system is Oracle,the acknowledge of journal transactions may need to be processed using the transaction group AND the fiscal periods. Wherethis is required the fiscal period and year details should be included in the acknowledgement message.

An example of the additional details is as follows:

<AccountingDate> <PeriodID>09</PeriodID> <Year>2012</Year></AccountingDate>

Where the Finance system is SAP, only the Transaction Group id value is required to be provided.

Message Examples

NotifyNotify message to initiate extraction of Transaction Groups.

<?xml version="1.0" encoding="UTF-8"?><NotifyJournalEntry xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ip="http://www.ventyx.com/IP/JournalEntry/1" xmlns:oa="http://www.openapplications.org/oagis/10" xsi:noNamespaceSchemaLocation="file:///C:/git-clones/mib/mib-common/schema/IP/1_0_0/BODs/NotifyJournalEntry.xsd"> <ApplicationArea> <oa:Sender> <oa:LogicalID>JournalTransactions</oa:LogicalID> <oa:TaskID>Scheduler</oa:TaskID> <oa:ReferenceID>NotifyJournalEntry</oa:ReferenceID> </oa:Sender> <oa:CreationDateTime>2014-06-04T11:17:03</oa:CreationDateTime> <oa:BODID>JUnit Test</oa:BODID> <oa:Extension> <oa:AnyExtension> <ip1:ServiceContext xmlns:ip1="http://www.ventyx.com/IP/1"> <ip1:ServiceName>NotifyJournalEntry</ip1:ServiceName> <ip1:ServiceVersion>1.0</ip1:ServiceVersion> <ip1:MessageType>JournalEntry</ip1:MessageType> </ip1:ServiceContext> <ip1:AuthorizationContext xmlns:ip1="http://www.ventyx.com/IP/1"> <ip1:Proxy> <ip1:UserID>INTEGRAT</ip1:UserID> <ip1:OrgID>R100</ip1:OrgID> <ip1:Role>INTEGRAT</ip1:Role> </ip1:Proxy> </ip1:AuthorizationContext> </oa:AnyExtension> </oa:Extension> </ApplicationArea> <DataArea> <oa:Notify> <oa:ActionCriteria>

<oa:ActionExpression actionCode="Get"></oa:ActionExpression> </oa:ActionCriteria> </oa:Notify> <JournalEntry> <JournalEntryHeader/> </JournalEntry> </DataArea></NotifyJournalEntry>

PostPost a Transaction Group.

<?xml version="1.0" encoding="UTF-8"?><PostJournalEntry xmlns:ip="http://www.ventyx.com/IP/JournalEntry/1" xmlns:oa="http://www.openapplications.org/oagis/10" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="file:///C:/git-clones/mib/mib-common/schema/IP/1_0_0/BODs/PostJournalEntry.xsd"> <oa:ApplicationArea> <oa:Sender> <oa:LogicalID>MIB</oa:LogicalID> <oa:ComponentID>JournalEntry</oa:ComponentID> <oa:TaskID>Post</oa:TaskID> <oa:ReferenceID>PostJournalEntry</oa:ReferenceID> </oa:Sender> <oa:Receiver> <oa:LogicalID></oa:LogicalID> </oa:Receiver> <oa:CreationDateTime>2014-07-21T10:35:49</oa:CreationDateTime> <oa:BODID>82a6f82f-fd02-4549-8ee8-0b47b28798dc</oa:BODID> <oa:Extension> <oa:AnyExtension> <ip1:ServiceContext xmlns:ip1="http://www.ventyx.com/IP/1"> <ip1:ServiceName>ShowChartOfAccounts</ip1:ServiceName> <ip1:ServiceVersion>1.0</ip1:ServiceVersion> <ip1:MessageType>ChartOfAccounts</ip1:MessageType> </ip1:ServiceContext> <ip1:AuthorizationContext xmlns:ip1="http://www.ventyx.com/IP/1"> </ip1:AuthorizationContext> </oa:AnyExtension> </oa:Extension> </oa:ApplicationArea> <DataArea> <oa:Post></oa:Post> <JournalEntry> <JournalEntryHeader> <DocumentDateTime>2014-07-16T03:28:50</DocumentDateTime> <EntryCreator> <ID>MSBISA</ID> </EntryCreator> <GLEntityID>R100</GLEntityID> <SourceDocumentReference> <DocumentDateTime>2014-01-24</DocumentDateTime> <Type>JN</Type> <DocumentID> <ID>R1002014012440941420000V4WNR</ID> </DocumentID> <ID>R1002014012440941420000V4WNR</ID> </SourceDocumentReference> <CurrencyExchangeRate> <RateNumeric>0</RateNumeric> </CurrencyExchangeRate> <AccountingDate> <PeriodID>09</PeriodID> <Year>2012</Year> <PostDateTime>2012-09-30</PostDateTime> </AccountingDate> <Party> <PartyIDs> <ID>000006</ID> </PartyIDs> </Party> <Extension> <AnyExtension> <ProcessDateTime>2014-01-24</ProcessDateTime> <Rec900Type>R</Rec900Type>

<ProcessStatus>I</ProcessStatus> <EntryCreator> <UserNumber>V4WN</UserNumber> </EntryCreator> </AnyExtension> </Extension> </JournalEntryHeader> <JournalEntryLine> <TaxBaseAmount currencyID="AUD">0</TaxBaseAmount> <FunctionalAmount currencyID="AUD">0</FunctionalAmount> <GLAccount> <GLNominalAccount>GL0001</GLNominalAccount> </GLAccount> <EnterpriseUnit> <GLEntityID>R100</GLEntityID> </EnterpriseUnit> <Amount currencyID="AUD">20000</Amount> <Extension> <AnyExtension> <SourceDocumentReference type="SRD"> <ID>40941420000</ID> <Description>Stock Receipt Direct Onsite</Description> <SequenceCode>0000000001</SequenceCode> </SourceDocumentReference> <ProcessDateTime>2014-01-24</ProcessDateTime> <Rec900Type>R</Rec900Type> <Tax type="atax"> <Calculation> <RateNumeric>0</RateNumeric> </Calculation> </Tax> <Indicators> <ExportExclude>N</ExportExclude> <DebitCredit>DR</DebitCredit> </Indicators> <SentDateTime>2014--0-7-T00:27:43</SentDateTime> <PurchaseOrderReference> <Note>002</Note> <DocumentID> <ID>P01595</ID> </DocumentID> </PurchaseOrderReference> <StockCode>A00001720</StockCode> <Party> <PartyIDs> <ID>000006</ID> </PartyIDs> </Party> </AnyExtension> </Extension> </JournalEntryLine> <JournalEntryLine> <TaxBaseAmount currencyID="AUD">0</TaxBaseAmount> <FunctionalAmount currencyID="AUD">0</FunctionalAmount> <GLAccount> <GLNominalAccount>GL0015</GLNominalAccount> </GLAccount> <EnterpriseUnit> <GLEntityID>R100</GLEntityID> </EnterpriseUnit> <Amount currencyID="AUD">20000</Amount> <Extension> <AnyExtension> <SourceDocumentReference type="INP"> <ID>40941860000</ID> <Description>Credit to Invoice Pending</Description> <SequenceCode>0000000002</SequenceCode> </SourceDocumentReference> <ProcessDateTime>2014-01-24</ProcessDateTime> <Rec900Type>Z</Rec900Type> <Tax type="atax"> <Calculation> <RateNumeric>0</RateNumeric> </Calculation> </Tax> <Indicators> <ExportExclude>N</ExportExclude> <DebitCredit>CR</DebitCredit>

</Indicators> <SentDateTime>2014--0-7-T00:27:43</SentDateTime> </AnyExtension> </Extension> </JournalEntryLine> </JournalEntry> </DataArea></PostJournalEntry>

AcknowledgeAcknowledge a Transaction Group successfully processed.<?xml version="1.0" encoding="UTF-8"?><PostAcknowledgeJournalEntry xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ip="http://www.ventyx.com/IP/JournalEntry/1" xmlns:oa="http://www.openapplications.org/oagis/10" xsi:noNamespaceSchemaLocation="file:///C:/git-clones/mib/mib-common/schema/IP/1_0_0/BODs/PostAcknowledgeJournalEntry.xsd"> <oa:ApplicationArea> <oa:Sender> <oa:LogicalID>Finance</oa:LogicalID> <oa:ComponentID>ExternalSysFinancialTransaction</oa:ComponentID> <oa:TaskID>PostAcknowledge</oa:TaskID> <oa:ReferenceID>JournalEntry</oa:ReferenceID> </oa:Sender> <oa:Receiver/> <oa:CreationDateTime>2013-12-13</oa:CreationDateTime> <oa:BODID>JUnit Test</oa:BODID> <oa:Extension> <oa:AnyExtension> <ip1:ServiceContext xmlns:ip1="http://www.ventyx.com/IP/1"> <ip1:ServiceName>AcknowledgeJournalEntry</ip1:ServiceName> <ip1:ServiceVersion>1.0</ip1:ServiceVersion> <ip1:MessageType>JournalEntry</ip1:MessageType> <ip1:DocumentName>JournalEntry</ip1:DocumentName> </ip1:ServiceContext> <ip1:AuthorizationContext xmlns:ip1="http://www.ventyx.com/IP/1"> <ip1:Proxy> <ip1:UserID>INTEGRAT</ip1:UserID> <ip1:OrgID>R100</ip1:OrgID> <ip1:Role>INTEGRAT</ip1:Role> </ip1:Proxy> </ip1:AuthorizationContext> </oa:AnyExtension> </oa:Extension> </oa:ApplicationArea> <DataArea> <oa:PostAcknowledge> <oa:ResponseCriteria> <oa:ResponseExpression actionCode="Accepted">ID=R1002014012440941420000V4WNR</oa:ResponseExpression> <oa:ChangeStatus> <oa:Reason>{ "Request ID": "", "Status": "" }</oa:Reason> </oa:ChangeStatus> </oa:ResponseCriteria> </oa:PostAcknowledge> <JournalEntry> <JournalEntryHeader> <SourceDocumentReference> <DocumentID> <ID>R1002014012440941420000V4WNR</ID> </DocumentID> </SourceDocumentReference> </JournalEntryHeader> </JournalEntry> </DataArea></PostAcknowledgeJournalEntry>

Acknowledge a Transaction Group successfully processed for a specific fiscal period.<?xml version="1.0" encoding="UTF-8"?><PostAcknowledgeJournalEntry xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ip="http://www.ventyx.com/IP/JournalEntry/1" xmlns:oa="http://www.openapplications.org/oagis/10" xsi:noNamespaceSchemaLocation="file:///C:/git-clones/mib/mib-common/schema/IP/1_0_0/BODs/PostAcknowledgeJournalEntry.xsd"> <oa:ApplicationArea> <oa:Sender> <oa:LogicalID>Finance</oa:LogicalID> <oa:ComponentID>ExternalSysFinancialTransaction</oa:ComponentID> <oa:TaskID>PostAcknowledge</oa:TaskID> <oa:ReferenceID>JournalEntry</oa:ReferenceID>

</oa:Sender> <oa:Receiver/> <oa:CreationDateTime>2013-12-13</oa:CreationDateTime> <oa:BODID>JUnit Test</oa:BODID> <oa:Extension> <oa:AnyExtension> <ip1:ServiceContext xmlns:ip1="http://www.ventyx.com/IP/1"> <ip1:ServiceName>AcknowledgeJournalEntry</ip1:ServiceName> <ip1:ServiceVersion>1.0</ip1:ServiceVersion> <ip1:MessageType>JournalEntry</ip1:MessageType> <ip1:DocumentName>JournalEntry</ip1:DocumentName> </ip1:ServiceContext> <ip1:AuthorizationContext xmlns:ip1="http://www.ventyx.com/IP/1"> <ip1:Proxy> <ip1:UserID>INTEGRAT</ip1:UserID> <ip1:OrgID>R100</ip1:OrgID> <ip1:Role>INTEGRAT</ip1:Role> </ip1:Proxy> </ip1:AuthorizationContext> </oa:AnyExtension> </oa:Extension> </oa:ApplicationArea> <oa:DataArea> <oa:PostAcknowledge> <oa:ResponseCriteria> <oa:ResponseExpression actionCode="Accepted">ID=R1002014072184569950000SN0LM</oa:ResponseExpression> <oa:ChangeStatus> <oa:Reason>{ "Request ID": "", "Status": "" }</oa:Reason> </oa:ChangeStatus> </oa:ResponseCriteria> </oa:PostAcknowledge> <JournalEntry> <JournalEntryHeader> <SourceDocumentReference> <DocumentID> <ID>R1002014072184569950000SN0LM</ID> </DocumentID> </SourceDocumentReference> <AccountingDate> <PeriodID>09</PeriodID> <Year>2012</Year> </AccountingDate> </JournalEntryHeader> </JournalEntry> </oa:DataArea></PostAcknowledgeJournalEntry>