Understanding the Treasury Integration

This chapter provides discusses:

• Release levels.

• Business process.

• Integration architecture.

• Integration points.

Release Levels

This document supports the integration between JD Edwards EnterpriseOne 8.12 General Accounting and PeopleSoft Enterprise 8.9 Treasury Management.

Business Process

With the PeopleSoft Enterprise Treasury with JD Edwards EnterpriseOne General Accounting integration, you can use the PeopleSoft Enterprise Treasury system to manage your cash and manage risk to ensure sound fund management and to meet regulatory requirements while maintaining your accounting information in the JD Edwards EnterpriseOne General Accounting system.

The major tasks involved in the integration of the PeopleSoft Enterprise Treasury system with the JD Edwards EnterpriseOne General Accounting system are:

• Setting up integration options

• Setting up the integration in the PeopleSoft Enterprise database.

• Loading market rates from JD Edwards EnterpriseOne into PeopleSoft Enterprise tables.

• Synchronizing incremental changes in market rates in JD Edwards EnterpriseOne with the PeopleSoft Enterprise system.

• Sending journal entries for treasury transactions from the PeopleSoft Enterprise system to the JD Edwards EnterpriseOne system.

  The JD Edwards EnterpriseOne system sends status update messages to the PeopleSoft Enterprise system when the journal entries are written to JD Edwards EnterpriseOne staging table, transferred from the staging table to the Account Ledger, and posted to the Account Balances table.

• Sending bank statement information from the PeopleSoft Enterprise system to the JD Edwards EnterpriseOne system so that reconciliation can take place in the JD Edwards EnterpriseOne system.

• Retrieving pertinent financial information from the JD Edwards EnterpriseOne system so that the PeopleSoft Enterprise system can include that information on the Cash Position Worksheet (CPW).

Integration Architecture

This section discusses the integration architecture for the:

• Batch load of market rates.

• Incremental synchronization of market rates

• Transfer of journal entries.

• Transfer of bank statements.

• Retrieval of financial data for the Cash Position Worksheet.

Integration Architecture for the Batch Load of Market Rates

This diagram illustrates the processes of loading market rates from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system by means of a batch load:

Market Rates Batch Load process

To perform an initial load of market rates:

1. Run the Currency Exchange Batch Upload program (R8900F0015) in the JD Edwards EnterpriseOne system to extract market rates from the JD Edwards EnterpriseOne database and write the data to a flat file named F0015 Exchange Rate Upload.txt.

2. Run the E1_Currency_Rates_To_E_Market_Rates batch integration in the Integration Server to retrieve the flat file, transform it, and create the MARKET_RATE_FULLSYNC message.

3. The Integration Server Dispatcher picks up the MARKET_RATE_FULLSYNC message and sends it to the PeopleSoft Enterprise system using Integration Broker and an HTTP connector.

Integration Architecture for the Incremental Synchronization of Market Rates

This diagram illustrates the incremental synchronization of market rates from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system:

Market Rates Incremental Synchronization process

The incremental sync integration runs automatically and consists of these major steps:

1. The RTCROUT real-time event is triggered by the JD Edwards EnterpriseOne system when an exchange rate is added, deleted, or changed.

2. The real-time event triggers an adapter service, which publishes the notifyCurrencyRateEventPublishDocument.

3. The E1_Currency_Rates_To_E_Market_Rates integration flow receives the published document, and transforms the JD Edwards EnterpriseOne data to the MARKET_RATE_SYNC message.

4. The MARKET_RATE_SYNC message is retrieved by an integration point, which writes the data to the PeopleSoft Enterprise database.

Integration Architecture for the Transfer of Journal Entries

This diagram illustrates the process of sending journal entries from PeopleSoft Enterprise Treasury to the JD Edwards EnterpriseOne system:

Journal Entry Integration process

Sending journal entries from the PeopleSoft Enterprise Treasury system to the JD Edwards EnterpriseOne General Accounting system consists of these major steps:

1. A PeopleSoft Enterprise Treasury user publishes the SYNC_TR_ACCTG_TXN outbound XML message with the information to create JD Edwards EnterpriseOne journal entries.

   The PeopleSoft Enterprise system updates the Integration Status of the entries in the Treasury system to Sent.

2. The Integration Server is listening for the IP message, and triggers the E_Treasury_To_E1_GeneralLedger integration flow, which transforms the message data and inserts the data in the Journal Entry Batch table (F0911Z1).

3. The Integration Server determines whether the insert was successful and posts a GET_TR_ACCTG_BATCH_STATUS Inbound reply message to the PeopleSoft Enterprise system.

   This message contains the unique identifier for the batch and a status. The Integration Broker calls the appropriate subscription code to update the accounting integration status to either Received or Error based on the data in the message.

4. A JD Edwards EnterpriseOne user runs the Journal Entries Batch Processor program (R09110Z) to validate the data and update the Account Ledger table (F0911).

5. The Journal Entries Batch Processor program triggers the RTBJESOUT real-time event.

6. The adapter service receives the real-time event and converts it to the notifyBatchJournalEntryStatusPublishDocument.

7. The Integration Server receives the notifyBatchJournalEntryStatusPublishDocument and triggers the E1_BatchJEStatus_To_E_AccountingHeaderStatus flow, which generates the GET_TR_ACCTG_HDR_STATUS message and sends it to the Integration Broker using the dispatcher.

8. The Integration Broker updates the accounting integration status in PeopleSoft Enterprise to a status of Loaded or Error.

9. A JD Edwards EnterpriseOne user runs the G/L Post program (R09801) to post the F0911 records to the Account Balances table (F0902).

10. The G/L Post program triggers the RTPOSTOUT real-time event.

11. The adapter services receives the real-time event and converts it to the notifyJournalEntryPostStatusPublishDocument.

12. The Integration Server receives the notifyJournalEntryPostStatusPublishDocument and triggers the E1_JEPostStatus_To_E_AccountingHeaderStatus flow, which generates the GET_TR_ACCTG_BATCH_STATUS message and sends it to the Integration Broker using the dispatcher.

13. The Integration Broker calls the appropriate subscription code to update the accounting integration status in PeopleSoft Enterprise.

    At this point, the accounting lines have a status of Posted and the Treasury user is not able to edit the accounting entries from this point forward.

Integration Architecture for the Transfer of Bank Statements

This diagram illustrates the process of sending the previous day's bank statement from the PeopleSoft Enterprise Treasury system to the JD Edwards EnterpriseOne General Accounting system:

Bank Statement Integration process

Sending bank statements from the PeopleSoft Enterprise Financials system to the JD Edwards EnterpriseOne General Accounting system consists of these major steps:

1. A PeopleSoft Enterprise Treasury user imports the bank statement file by running the File Import Application Engine process (IMPORT_FILE) either manually or using the Process Scheduler.

2. The PeopleSoft Enterprise Treasury system transforms the bank statement file to the BANK_STATEMENT_LOAD message and uses that message to load the bank statement into the PeopleSoft Enterprise Treasury database.

3. After the message is processed in the Treasury database, the system publishes the BANK_STATEMENT_LOAD message.

4. The Integration Server is listening for the IP message, and triggers the E_Treasury_To_E1_BankStatementStaging integration flow, which transforms the message data and inserts the data in the Electronic Bank Statement Staging Header table (F09610) and the Electronic Bank Statement Staging Detail table (F09611).

5. A JD Edwards EnterpriseOne user runs the Load Bank Statement program (R09612) to validate the data and update the Auto Bank Statement Header table (F09616) and the Auto Bank Statement Detail table (F09617).

6. A JD Edwards EnterpriseOne user uses the bank statement data to perform reconciliation and other bank statement processes.

Integration Architecture for the Retrieval of Financial Data for the Cash Position Worksheet

This diagram illustrates the process of retrieving financial data from the JD Edwards EnterpriseOne system for the Cash Position Worksheet (CPW):

Data Retrieval for Cash Position Worksheet process

Retrieving financial data from the JD Edwards EnterpriseOne system for the CPW consists of these major steps:

1. The Cash Manager selects the worksheet to be calculated on the Position Manager page in the PeopleSoft Enterprise system, enters the required data for the worksheet, and clicks the Calculate button.

2. The PeopleSoft Enterprise Treasury system determines whether the worksheet requires data from the JD Edwards EnterpriseOne system.

3. If the worksheet requires data from the JD Edwards EnterpriseOne system, the system uses the JDBJ API to retrieve the appropriate data directly from these tables in the JD Edwards EnterpriseOne database:

   • Accounts Payable Ledger (F0411)

   • Receipts Header (F03B13)

   • Receipts Detail (F03B14)

4. The data is populated in the appropriate tables for the CPW and normal CPW processing continues.

Integration Points

This chapter lists integration points for the:

• Integration of market rates.

• Transfer of journal entries.

• Transfer of bank statements.

Integration Points for the Integration of Market Rates

This table lists the integration points used by the Treasury integration to send market rate information from the JD Edwards EnterpriseOne system to the PeopleSoft Enterprise system:

Integration Points for the Transfer of Journal Entries

This table lists the integration points used by the Treasury integration to send journal entries from the PeopleSoft Enterprise Treasury system to the JD Edwards EnterpriseOne General Accounting system:

Integration Point for the Transfer of Bank Statements

This table lists the integration points used by the Treasury integration to send the previous day's bank statements from the PeopleSoft Enterprise Treasury system to the JD Edwards EnterpriseOne General Accounting system: