Understanding the JD Edwards EnterpriseOne General Accounting to PeopleSoft Enterprise General Ledger Integration

This chapter discusses:

Release levels.
Business process.
Integration architecture.
Field structure comparison between the JD Edwards EnterpriseOne system and the PeopleSoft Enterprise system.
Assumptions and requirements of the integration process.

Release Levels

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

Business Process

This PeopleSoft integration imports JD Edwards EnterpriseOne General Accounting data and balance information to the PeopleSoft Enterprise General Ledger. The integration is primarily intended to provide information from the JD Edwards EnterpriseOne system to perform consolidations and prepare reports in the PeopleSoft Enterprise environment.

Because information is integrated at the ledger level, the integration process effectively enables you to integrate the PeopleSoft Enterprise system with the JD Edwards EnterpriseOne feeder systems that include JD Edwards EnterpriseOne Real Estate Management (REM), Asset Management (EAM), and Manufacturing through the results of operations maintained in the JD Edwards EnterpriseOne General Accounting.

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

Setting up integration options in the JD Edwards EnterpriseOne WSG soft-coding/cross-reference database.
Setting up the integration in the PeopleSoft Enterprise database.
Loading JD Edwards EnterpriseOne General Accounting data and balance information to the PeopleSoft Enterprise General Ledger.

Integration Architecture

Information is passed in one direction only from the JD Edwards EnterpriseOne system to PeopleSoft Enterprise General Ledger by the integration process. The term source refers to the JD Edwards EnterpriseOne ledger and the term target refers to the PeopleSoft Enterprise ledger.

This diagram illustrates the basic integration process:

JD Edwards EnterpriseOne GL to PeopleSoft Enterprise GL integration process

The integration includes these basic steps:

Using functionality in the JD Edwards EnterpriseOne system, run the Generate Outbound Account Balances program (R89F0902) to create a text file named F0902_OUT.txt from the account balance information in the source Account Balances table (F0902), and store the file in an export folder (for example, C:\B9\PD9\export).
Using the Integration Server tool, run the Integration Package to retrieve the F0902_OUT.txt file, transform the data, and create a text file named PS_LEDGER_OUT-yyyymmdd-hhmmss.txt in a specified folder.
Using the PeopleSoft Enterprise system, run the Flat File Ledger Import utility to upload the PS_LEDGER_OUT-yyyymmdd-hhmmss.txt file and run the ChartField Mapping utility to convert the data to the target PS_LEDGER PeopleSoft Enterprise table.

Field Structure Comparison Between the JD Edwards EnterpriseOne System and the PeopleSoft Enterprise System

This table summarizes corresponding field structure for the JD Edwards EnterpriseOne system and the PeopleSoft Enterprise system:

JD Edwards EnterpriseOne System	Comment	PeopleSoft Enterprise System	Comment
Company	This field is right justified, zero fill alphanumeric.	Business Unit	The equivalent of the Company field in the JD Edwards EnterpriseOne system must be defined in the PeopleSoft Enterprise system for the integration.
Ledger Type	While other ledger types are available, the actual ledger type is always AA and is the default source ledger type for the integration unless you specify otherwise.	Ledger	Ledger in the PeopleSoft Enterprise system is user defined. A target ledger must be defined and specified for the integration.
Object Account and Subsidiary	A combined field length of 14 characters is possible. However, when the Object Account and Subsidiary fields are concatenated and if the combined field length exceeds 10 characters, the field value is truncated when the flat file is created to fit the 10-character format of the Account field in the PeopleSoft Enterprise system.	Account	The field length is 10 characters. You map the combined object account and subsidiary values that are passed in the flat file to the required account value of the target ledger by using field mapping functionality in the PeopleSoft Enterprise system.
Business Unit	A field of 12 characters used for cost centers. It is truncated to 8 characters for integration with the PeopleSoft Enterprise system.	Operating Unit	This field of eight characters is typically used to designate a cost center.
Subledger	This field is representative of the receiving company in an intercompany transaction.	Affiliate	This field designates the other business unit that is involved in an intercompany transaction using business unit.
Currency Code	This is either the base currency of the company (source) or the currency of the reporting (target) ledger if amounts are translated in the JD Edwards EnterpriseOne system.	Currency_Code	This is a three digit code for the currency of the ledger amounts being imported to the target ledger. Amounts can be translated to another currency in the JD Edwards EnterpriseOne system or after receiving the balances in the PeopleSoft Enterprise system. However, the currency of the source and target ledgers must initially be the same.
Century and Fiscal Year	The integration process concatenates the two fields of two characters to form a Fiscal Year field of four characters.	Fiscal Year	This is a four digit field.
Amount Codes	The amount codes in the JD Edwards EnterpriseOne system are: APYC designates a beginning balance. AN01 designates the amount net posting for period 1, AN02 is for the amount net posting for period 2, and so on. AN13 and AN14 are the two available JD Edwards EnterpriseOne adjustment periods. Their balances can be accumulated in separate PeopleSoft Enterprise adjustment periods, such as 997 and 998 or you can accumulate their combined total to 998.	Accounting_Period and Adjustment Period	The integration makes the JD Edwards EnterpriseOne accounting period APCY equal to the PeopleSoft Enterprise beginning balance represented by 0. The accounting period is made equal to 1 in the PeopleSoft Enterprise system for the AN01 amount code in the JD Edwards EnterpriseOne system, equal to 2 for AN02, and so on through AN12, which is equivalent to accounting period 12 in the PeopleSoft Enterprise system. The PeopleSoft Enterprise system has these adjustment periods: 901 through 998 are possible adjustment periods. Typically, accounting periods 1 through 12 correspond to monthly adjustment periods of 901 to 912. Period 998 is typically the default adjustment period when monthly adjustment periods are not used. Period 999 is used to store the results of year-end close for the PeopleSoft Enterprise system.
Amount	This is the net posting amount for a period.	Posted Total Amount, Posted Base Amount, and Posted Transaction Amount	All three fields are populated with the same JD Edwards EnterpriseOne amount and to a period based on the amount code passed from the JD Edwards EnterpriseOne system.

Assumptions and Requirements of the Integration Process

PeopleSoft designed the integration to be run as a batch process at the end of various periods, such as week, month, quarter, or year to move JD Edwards EnterpriseOne general ledger balances to the PeopleSoft Enterprise system. However, you can run the process on a one-time basis at any time. The primary purpose of the integration is to provide information for consolidations and reporting in the PeopleSoft Enterprise system. The integration does not support the movement of information from the PeopleSoft Enterprise system to the JD Edwards EnterpriseOne system.

Calendars, Accounting Periods, and Adjustment Periods

Calendars for the source and target ledgers must be the same–that is, they must describe identical date patterns–to use the integration process.

The JD Edwards EnterpriseOne system supports 14 periods. In the typical setup, periods 1 through 12 are used as monthly accounting periods, and periods 13 and 14 are used as adjustment periods. Another alternative setup is to maintain 13 accounting period of four weeks, which is typical in manufacturing, and use period 14 as the adjustment period. All structures can be mirrored in the PeopleSoft Enterprise system. The PeopleSoft Enterprise system uses period 0 for beginning balances, and adjustment periods 901 through 997 are available. Period 998 is the default adjustment period and period 999 is used to store the results of year-end close.

Because only one adjustment year can be open at any one time in the PeopleSoft Enterprise system, multiple years with adjustment periods cannot be transferred at the same time to the PeopleSoft Enterprise General Ledger. The Flat File Ledger Import process returns an error if adjustment periods exist for files with adjustment periods that are not open in the PeopleSoft Enterprise system. Transfer historical data for prior years with adjustment periods to the PeopleSoft Enterprise system in separate files and then close each adjustment year and open the subsequent adjustment year in PeopleSoft Enterprise General Ledger before transferring another file for a subsequent year.

See PeopleSoft Enterprise Application Fundamentals 8.9 Implementation Guide, “Defining Accounting Calendars,” Defining and Updating Open Periods and Adjustment Periods.

Field Lengths

Some field lengths vary between the JD Edwards EnterpriseOne system and the PeopleSoft Enterprise system. The expectation is that in most cases JD Edwards EnterpriseOne products will be implemented for the purpose of integration with existing PeopleSoft Enterprise products. That being the case, at installation you can set up the JD Edwards EnterpriseOne fields with lengths that correspond to the ChartField lengths in the PeopleSoft Enterprise product.

If you integrate existing installations of the JD Edwards EnterpriseOne system and the PeopleSoft Enterprise system and field lengths are already established, the integration process truncates values in JD Edwards EnterpriseOne fields to match the corresponding field lengths in the PeopleSoft Enterprise system.

For example, if the length of the combined Object Account and Subsidiary fields is greater than 10 characters, the truncation to 10 characters might result in duplicate account numbers that might also result in unwanted summarization in the PeopleSoft Enterprise system. If you want to maintain the same level of detail in the PeopleSoft Enterprise system that you have in the JD Edwards EnterpriseOne system, limit the combined Object Account and Subsidiary fields in the JD Edwards EnterpriseOne system to 10 characters.

Similarly, the truncation of the 12-character Business Unit field from the JD Edwards EnterpriseOne system to correspond to the 8-character Operating Unit field in the PeopleSoft Enterprise system might cause duplicate Operating Unit values. To avoid duplicates, you can limit the JD Edwards EnterpriseOne Business Unit field to 8 characters.

Alternatively you can use PeopleSoft Enterprise ChartField configuration functionality to increase field lengths in the PeopleSoft Enterprise system. However, this adds maintenance overhead for the PeopleSoft Enterprise products. You can avoid the additional maintenance by using the same ChartField lengths at setup or the truncation of existing field values in the JD Edwards EnterpriseOne system.

See PeopleSoft Enterprise Application Fundamentals 8.9 Implementation Guide, “Configuring ChartFields.”

Currency

The currency of the source and target ledgers must initially be the same, and you must also determine at the outset whether the translation of nonreporting currency occurs in the JD Edwards EnterpriseOne system or in the PeopleSoft Enterprise system.

If the JD Edwards EnterpriseOne ledger balances are in a different currency, it is recommended that you translate balances in the JD Edwards EnterpriseOne application before the integration. Alternatively you can set up the target PeopleSoft Enterprise ledger to use the same currency as the JD Edwards EnterpriseOne system and translate or convert to the reporting currency in the PeopleSoft Enterprise system after the balances are transferred. Regardless of whether the conversion occurs in the JD Edwards EnterpriseOne system or in the PeopleSoft Enterprise system, the currency of the source and target must initially be the same.

It follows that transfer of account balances by currency is not supported by the integration. If posting by different currencies is being used in the JD Edwards EnterpriseOne system, all balances must be converted to the common currency that is shared by the source and target ledger before integration.

See PeopleSoft Enterprise Global Options and Reports 8.9 Implementation Guide, “Processing Multiple Currencies.”

See PeopleSoft Enterprise General Ledger 8.9 Implementation Guide, “Processing Multiple Currencies in General Ledger.”