How to mirror PeopleSoft General Ledger into E-Business Suite General Ledger

Following the FAH to PeopleSoft GL integration pack post, I''ll now highlight how to set up E-Business Suite General Ledger, within the context of a FAH to PeopleSoft General Ledger implementation.

Note that this article is written from an E-Business Suite perspective, and that it covers only a certain aspect of the integration. If you wish to understand the other aspects as well, you can find the implementation guide (version 2.5) in the AIA documentation library.

First we need to understand PeopleSoft's Set ID feature.

For the purpose of our integration, I'll use an example to illustrate this conceptually.

The shared Set ID resembles data which can be used by all business units.

Then you can make up Set ID's for whatever levels you like e.g. continent, country, region, etc.

The lowest possible value at which Set ID can be used, is at business unit level.

Set ID's make it very easy to re-use data across the application, which is why this concept is also present in Fusion Applications.
For our purpose, the following would be an example of Set ID usage:

Here the accounts are shared by all, products are business unit specific, and cost centers are country specific.

This means that for instance business unit "US002", makes use of the values highlighted in yellow:

Now how does this PeopleSoft feature translate to the E-Business Suite Financials world?

The magic formula is:

Applying this to our example, we get the following:

So each combination of PeopleSoft Chartfield and Set ID, results into an E-Business Suite Value Set.

The E-Business Suite accounting flexfield for business unit "US002", is using Value Sets: Account-SHA / Product-US002 / Center-US.

This means that if one or more PeopleSoft chartfields are using Set ID at the lowest possible level, which is the business unit level, then in E-Business Suite you'll be setting up a separate accounting flexfield for each PeopleSoft business unit.

The PeopleSoft business unit concept is richer compared to what we call a business unit in E-Business Suite. In PeopleSoft the opening / closing of accounting periods, can for instance happen at business unit level. While in E-Business Suite this is held at ledger level.

Then a PeopleSoft ledger is used to hold a certain representation of a business unit's account balances (e.g. actuals, budget, ...).

Throwing this all together, we get the following formula:

Meaning that every combination of PeopleSoft business unit and PeopleSoft ledger, results in an E-Business Suite ledger.

But hold on, does this tie in with the first formula?

Let's assume the scenario where one or more PeopleSoft chartfields are using Set ID at the business unit level.

As explained above, in such case we would set up a separate E-Business Suite accounting flexfield per business unit, which results in a separate E-Business Suite ledger per PeopleSoft business unit.

This indeed ties nicely together with the other formula, which states that we need at least an E-Business Suite ledger per PeopleSoft business unit.

You won't necessarily always run into this particular scenario, because I've encountered PeopleSoft GL implementations where all chartfields were happily being shared across the board.
So to mirror that, you would set up a single accounting flexfield in E-Business Suite, and use this single accounting flexfield for all your E-Business Suite ledgers / PeopleSoft business units.

In a future post, I'll explain how the above can have an interesting impact on your FAH rules design.