Setting Up the PeopleSoft Enterprise Treasury with JD Edwards EnterpriseOne General Accounting Integration

This chapter provides an overview of setup and implementation considerations and discusses how to:

Set up the Treasury integration in the PeopleSoft Enterprise database.
Set up the cash position worksheet integration.
Set up the Treasury integration in the Integration Server.

Understanding Setup and Implementation Considerations

The PeopleSoft Enterprise Treasury to JD Edwards EnterpriseOne General Accounting integration functions based on these assumptions:

Banks and bank account information is not synchronized between the two systems. The accounts must be entered into each system manually.
The JD Edwards EnterpriseOne General Accounting system validates accounting entries and creates intercompany accounting entries if needed. The Inter/Intraunit Processor and Combination Editing processes should be disabled in the PeopleSoft Enterprise system.
All bank statement processing and reconciliation should be done in the JD Edwards EnterpriseOne General Accounting system.
PeopleSoft Enterprise and JD Edwards EnterpriseOne calendars must be synchronized manually.
All journal entries will create entries using the AA ledger type only.
No specific ChartField (chart of account) configurations are be required for this integration.
The PeopleSoft Enterprise Treasury system does not perform any document sequencing for integration transactions. Document sequencing is done in the JD Edwards EnterpriseOne system.
Both systems store appropriate keys to reference the transactions in the other system. For example, the JD Edwards EnterpriseOne journal ID is stored in the PeopleSoft Enterprise Treasury system and the batch and accounting ID are stored in the JD Edwards EnterpriseOne system.

Setting Up the Treasury Integration in the PeopleSoft Enterprise Database

This section lists prerequisites and discuss how to:

Set up Treasury installation options.
Activate integration transactions for the Treasury integration.
Activate messages for the Treasury integration.
Activate message channels for the Treasury integration.
Add channels to permissions for the Treasury integration.
Activate message subscriptions for the Treasury integration.

Prerequisites

Before you complete the tasks discussed here to set up the integration environment in the PeopleSoft Enterprise Financials/SCM database:

Set up the local gateway in the PeopleSoft Enterprise Financials/SCM database.

See Setting Up the Local Gateway.
Activate the PSFT_E1 message node.

See Activating Message Nodes.
Identify the properties and provide a designated URL for the PSFT_E1 node.

See Setting Up Node Definitions.

Pages Used to Set Up the Treasury Integration in the PeopleSoft Enterprise Database

Access these pages in the PeopleSoft Enterprise Financials/SCM database.

Page Name	Object Name	Navigation	Usage
Installation Options	INSTALLATION_TR	Set Up Financials/Supply Chain, Install, Installation Options, Treasury	Set up installation options to enable the Treasury integration.
Node Definition - Transactions	IB_NODETRXLIST	PeopleTools, Integration Broker, Integration Setup, Node Definitions, Transactions tab	Activate the messages used to pass data between PeopleSoft Enterprise Treasury and JD Edwards EnterpriseOne General Accounting.

Setting Up Treasury Installation Options

Access the Installation Options page – Treasury tab.

Enable Accounting Integration

Select this option to enable the accounting integration.

Integration Engine Run Option

Select an option to indicate whether the integration application engine should use the process scheduler or run immediately after accounting.

Note. If your connection fails and you are using a DB2 database, you will need to modify the AddToPath variable supported by the application server domain configuration file (psappsrv.cfg). Include the bin and function path that contain files to access DB2. Proceed to application server domain administration (psadmin) and reconfigure this domain. Select AddToPath settings and add the additional paths separated by a semicolon. Reload the new configuration and boot the domain.

Activating Integration Transactions for the Treasury Integration

Access the Node Definition - Transactions page.

These messages must be activated.

Transaction Name	Version	Transaction Type
BANK_STATEMENT_LOAD	VERSION_2	OutAsync
GET_TR_ACCTG_BATCH_STATUS	VERSION_1	InAsync
GET_TR_ACCTG_HDR_STATUS	VERSION_1	InAsync
SYNC_TR_ACCTG_TXN	VERSION_1	OutAsync
MARKET_RATE_FULLSYNC	VERSION_1	InAsync
MARKET_RATE_SYNC	VERSION_1	InAsync

See Setting Up Integration Transactions.

Activating Messages for the Treasury Integration

Verify that these messages are active:

BANK_STATEMENT_LOAD
GET_TR_ACCTG_BATCH_STATUS
GET_TR_ACCTG_HDR_STATUS
MARKET_RATE_FULLSYNC
MARKET_RATE_SYNC
SYNC_TR_ACCTG_TXN

See Activating Messages.

Activating Message Channels for the Treasury Integration

Verify that these message channels have a message channel status of Run:

BANK_STATEMENT
TREASURY
MARKET_RATES

See Activating Message Channels.

Adding Channels to Permissions for the Treasury Integration

To integrate PeopleSoft Enterprise Treasury with the JD Edwards EnterpriseOne system, you must set the channel permissions for these channels:

MARKET_RATES
BANK_STATEMENT
TREASURY

See Adding Channels to Permissions.

Activating Message Subscriptions for the Treasury Integration

Verify that these message subscriptions are active:

Message Name	Subscription Name
MARKET_RATE_FULLSYNC	MarketRateFullSync
MARKET_RATE_SYNC	MarketRateSync
GET_TR_ACCTG_BATCH_STATUS	GET_TR_ACCTG_BATCH_STATUS
GET_TR_ACCTG_HDR_STATUS	GET_TR_ACCTG_HDR_STATUS

See Activating Message Subscriptions.

Setting Up the Cash Position Worksheet Integration

The section provides an overview of the CPW integration process and lists the pages used to map the CPW integration.

Understanding the CPW Integration Process

PeopleSoft Enterprise Cash Management uses the JDBJ Java API to access the JD Edwards EnterpriseOne database directly to generate a CPW. To accomplish this, PeopleSoft Enterprise setIDs, business units, and accounts must be mapped to corresponding fields in the JD Edwards EnterpriseOne system. This table lists the records involved in the CPW integration.

JD Edwards EnterpriseOne Source Record	PeopleSoft Enterprise Target Record
F0411	TR_CPW_INT_AP
F03B14	TR_CPW_INT_AR

This table lists the functional mapping between the two systems.

JD Edwards EnterpriseOne Field	PeopleSoft Enterprise Field
Company ID	SetID
Business Unit	Business Unit
Currency	Base Currency
Account Short ID	Account
Accounts Unit\Account Object \ Account Subsidiary	Account Description

The PeopleSoft system delivers the necessary code mapping between JD Edwards EnterpriseOne records and fields and the corresponding PeopleSoft Enterprise records and fields. Use the pages listed in this section to access the data used in the preconfigured CPW integration process. For example, the payables record in the JD Edwards EnterpriseOne database is F0411, and in the PeopleSoft Enterprise database is TR_CPW_INT_AP. The JD Edwards EnterpriseOne field MCU is mapped to the PeopleSoft Enterprise field TR_CPW_INT_AP.EONE_BU that is mapped to the position field type in PeopleSoft Enterprise as BUSINESS UNIT.

Pages Used to Map the CPW Integration

Access these pages in the PeopleSoft Enterprise Financials/SCM database.

Page Name	Object Name	Navigation	Usage
Position Source	POS_SOURCE_TBL	Setup Financials/Supply Chain, Product Related, Treasury, Position Source	Provide a more intuitive list of fields from which to select in the Position Manager. Use these alias names when entering selection criteria for position nodes. Note. The PeopleSoft system delivers the ENTERPRISEONE -AP and the ENTERPRISEONE - AR position sources with the preconfigured default mappings for the CPW integration.
Position Manager Records	POS_EXT_DATA_REC	Setup Financials/Supply Chain, Product Related, Treasury, Position Manager Records	View the records involved in the CPW integration process.
Position Field Types	POS_FIELD_TYPE_PNL	Setup Financials/Supply Chain, Product Related, Treasury, Position Field Types	Define the sets of table fields that are available to the position management tool.
Position Manager Field Map	TR_INT_MAP	Setup Financials/Supply Chain, Product Related, Treasury, Position Manager Field Map	View the field mappings between the JD Edwards EnterpriseOne and PeopleSoft Enterprise payables and receivables records. Note. The PeopleSoft system delivers the E1_AR_MAP and the E1_AR_MAP integration maps preconfigured for the CPW integration process.

Setting Up the Treasury Integration in the Integration Server

This section provides an overview of utility services, lists prerequisites, and discusses how to:

Enable JD Edwards EnterpriseOne Adapter Listener Notifications for the Treasury integration.
Set up integration options for the Treasury integration.

Understanding Utility Services

The Treasury integration uses these utility services:

PSFT_Enterprise_Treasury.utils:determineExchangeRate
PSFT_Enterprise_Treasury.utils:getTREConstants
PSFT_Enterprise_Treasury.utils:transformDateAndTimeFieldsToDateTime

Prerequisites

Before completing the tasks in this section:

Enable dependent packages.

See Setting Up Dependent Packages.
Enable the JD Edwards EnterpriseOne Adapter and the JD Edwards EnterpriseOne Adapter Listener.

See Enabling the JD Edwards EnterpriseOne Adapter.

See Enabling the JD Edwards EnterpriseOne Adapter Listener.

Enabling JD Edwards EnterpriseOne Adapter Listener Notifications for the Treasury Integration

Enable the listener and these listener notifications within the PSFT_JD Edwards EnterpriseOne_AdapterServices package:

AdapterServices.Notification.LearningManagement:notifyCurrencyRateEvent
AdapterServices.Notification.Financials:notifyBatchJournalEntryStatus
AdapterServices.Notification.Financials:notifyJournalEntryPostStatus

See Enabling JD Edwards EnterpriseOne Adapter Listener Notifications.

Setting Up Integration Options for the Treasury Integration

This section lists the integration options for these integration points:

Currency Rates
Treasury Journal Entries
Batch Journal Entry Status
Journal Entry Post Status
Bank Statements

Currency Rates

The integration of currency rates requires these integration options:

Navigation	Integration Option	Usage
PSFT_JD Edwards EnterpriseOne_Treasury, InitialBatchLoads, E1_Currency_Rates_To_E_Market_Rates, convert_E1_Currency_Rates_To_E_Market_Rates	Export Directory	Specify the location of the F0015 Exchange Rate Upload.txt file that is generated by the Currency Exchange Batch Upload program (R8900F0015). This value is an example: \\machinename\pyexport.
PSFT_JD Edwards EnterpriseOne_Treasury	From Node	Specify the JD Edwards EnterpriseOne node. This value must be the same value that is set up for this node in the PeopleSoft Enterprise Integration Broker. This value is an example: PSFT_E1. This value is used only when sending a message to the PeopleSoft Enterprise system. For flows that originate in the PeopleSoft Enterprise system, this value is used to send a success or error response back to the PeopleSoft Enterprise system.
PSFT_JD Edwards EnterpriseOne_Treasury	To Node	Specify the PeopleSoft Enterprise node. This value must be the same value that is set up for this node in the PeopleSoft Enterprise Integration Broker. This value is an example: PSFT_EP. This value is used only when sending a message to the PeopleSoft Enterprise system. For flows that originate in the PeopleSoft Enterprise system, this value is used to send a success or error response back to the PeopleSoft Enterprise system.
PSFT_JD Edwards EnterpriseOne_Treasury	Gateway URL	Specify the URL of the local gateway in the PeopleSoft Enterprise system. This value is an example: http://sunrise/PSIGW/PeopleSoftListeningConnector
PSFT_JD Edwards EnterpriseOne_Treasury	Transaction Transport	Specify the protocol of transport that is used to get the message to the PeopleSoft Enterprise Integration Broker (for example, HTTP or JMS). The default value is http.
PSFT_JD Edwards EnterpriseOne_Treasury	PSCAMA Class	The PSCAMA class is required by the PeopleSoft Enterprise messaging system. The default value is R and should not be changed.
PSFT_JD Edwards EnterpriseOne_Treasury	Base Language	Specify the base language of the JD Edwards EnterpriseOne database. This is used by generic, full-table subscription PeopleCode to help determine which tables to update. The default value is ENG (English).
PSFT_JD Edwards EnterpriseOne_Treasury	Language	Specify the language in which the messages that are sent to the PeopleSoft Enterprise system are generated, so that PeopleSoft Enterprise can take that information into account when processing the message. The default value is ENG (English).
PSFT_JD Edwards EnterpriseOne_ELM	Market Rate Index	Specify the market rate index for market rates that are sent to the PeopleSoft Enterprise system. The default value is TEST_INDEX.

Treasury Journal Entries

The integration of Treasury journal entries requires these integration options:

Navigation	Integration Option	Usage
System	E1 Date Pattern	Specify the date pattern that is set up in the JD Edwards EnterpriseOne system (for example, MM/dd/yyyy).
PSFT_JD Edwards EnterpriseOne_Treasury	From Node	Specify the JD Edwards EnterpriseOne node. This value must be the same value that is set up for this node in the PeopleSoft Enterprise Integration Broker. This value is an example: PSFT_E1. This value is used only when sending a message to the PeopleSoft Enterprise system. For flows that originate in the PeopleSoft Enterprise system, this value is used to send a success or error response back to the PeopleSoft Enterprise system.
PSFT_JD Edwards EnterpriseOne_Treasury	To Node	Specify the PeopleSoft Enterprise node. This value must be the same value that is set up for this node in the PeopleSoft Enterprise Integration Broker. This value is an example: PSFT_EP. This value is used only when sending a message to the PeopleSoft Enterprise system. For flows that originate in the PeopleSoft Enterprise system, this value is used to send a success or error response back to the PeopleSoft Enterprise system.
PSFT_JD Edwards EnterpriseOne_Treasury	Gateway URL	Specify the URL of the local gateway in the PeopleSoft Enterprise system. This value is an example: http://sunrise/PSIGW/PeopleSoftListeningConnector
PSFT_JD Edwards EnterpriseOne_Treasury	Transaction Transport	Specify the protocol of transport that is used to get the message to the PeopleSoft Enterprise Integration Broker (for example, HTTP or JMS). The default value is http.
PSFT_JD Edwards EnterpriseOne_Treasury	PSCAMA Class	The PSCAMA class is required by the PeopleSoft Enterprise messaging system. The default value is R and should not be changed.

Batch Journal Entry Status

The integration of the batch journal entry status requires these integration options:

Navigation	Integration Option	Usage
System	E1 Date Pattern	Specify the date pattern that is set up in the JD Edwards EnterpriseOne system (for example, MM/dd/yyyy).
PSFT_JD Edwards EnterpriseOne_Treasury	From Node	Specify the JD Edwards EnterpriseOne node. This value must be the same value that is set up for this node in the PeopleSoft Enterprise Integration Broker. This value is an example: PSFT_E1. This value is used only when sending a message to the PeopleSoft Enterprise system. For flows that originate in the PeopleSoft Enterprise system, this value is used to send a success or error response back to the PeopleSoft Enterprise system.
PSFT_JD Edwards EnterpriseOne_Treasury	To Node	Specify the PeopleSoft Enterprise node. This value must be the same value that is set up for this node in the PeopleSoft Enterprise Integration Broker. This value is an example: PSFT_EP. This value is used only when sending a message to the PeopleSoft Enterprise system. For flows that originate in the PeopleSoft Enterprise system, this value is used to send a success or error response back to the PeopleSoft Enterprise system.
PSFT_JD Edwards EnterpriseOne_Treasury	Gateway URL	Specify the URL of the local gateway in the PeopleSoft Enterprise system. This value is an example: http://sunrise/PSIGW/PeopleSoftListeningConnector
PSFT_JD Edwards EnterpriseOne_Treasury	Transaction Transport	Specify the protocol of transport that is used to get the message to the PeopleSoft Enterprise Integration Broker (for example, HTTP or JMS). The default value is http.
PSFT_JD Edwards EnterpriseOne_Treasury	PSCAMA Class	The PSCAMA class is required by the PeopleSoft Enterprise messaging system. The default value is R and should not be changed.

Journal Entry Post Status

The integration of the journal entry posting status requires these integration options:

Navigation	Integration Option	Usage
PSFT_JD Edwards EnterpriseOne_Treasury	From Node	Specify the JD Edwards EnterpriseOne node. This value must be the same value that is set up for this node in the PeopleSoft Enterprise Integration Broker. This value is an example: PSFT_E1. This value is used only when sending a message to the PeopleSoft Enterprise system. For flows that originate in the PeopleSoft Enterprise system, this value is used to send a success or error response back to the PeopleSoft Enterprise system.
PSFT_JD Edwards EnterpriseOne_Treasury	To Node	Specify the PeopleSoft Enterprise node. This value must be the same value that is set up for this node in the PeopleSoft Enterprise Integration Broker. This value is an example: PSFT_EP. This value is used only when sending a message to the PeopleSoft Enterprise system. For flows that originate in the PeopleSoft Enterprise system, this value is used to send a success or error response back to the PeopleSoft Enterprise system.
PSFT_JD Edwards EnterpriseOne_Treasury	Gateway URL	Specify the URL of the local gateway in the PeopleSoft Enterprise system. This value is an example: http://sunrise/PSIGW/PeopleSoftListeningConnector
PSFT_JD Edwards EnterpriseOne_Treasury	Transaction Transport	Specify the protocol of transport that is used to get the message to the PeopleSoft Enterprise Integration Broker (for example, HTTP or JMS). The default value is http.
PSFT_JD Edwards EnterpriseOne_Treasury	PSCAMA Class	The PSCAMA class is required by the PeopleSoft Enterprise messaging system. The default value is R and should not be changed.

Bank Statements

The integration of bank statements requires these integration options:

Navigation	Integration Option	Usage
System	E1 Date Pattern	Specify the date pattern that is set up in the JD Edwards EnterpriseOne system (for example, MM/dd/yyyy).

Enable Accounting Integration	Select this option to enable the accounting integration.
Integration Engine Run Option	Select an option to indicate whether the integration application engine should use the process scheduler or run immediately after accounting.