Common Terminology Used in the Fusion Accounting Hub Integration

This table defines commonly-used terms in the Fusion Accounting Hub to PeopleSoft General Ledger integration:

Field or Control Description

Accounting Lines, Accounting Entries, and Journal Entries

Accounting lines are created from source transactions and reside within Fusion Accounting Hub until they are transformed into accounting entries and stored in the 3rd Party Interface table (FAH_ACTG_LINE). This interface table is then used to transfer the accounting entries to the PeopleSoft External Accounting Entry record (FAI_ACCTG_LINE), which Journal Generator uses to create the PeopleSoft journal entries.

Chart of Accounts

This common term refers to the entirety of all values that are used in categorizing an accounting entry or journal line. For PeopleSoft, that would be all of the ChartFields. For Fusion, this would be all of the Segments.

Fusion Accounting Hub Journal

A journal within Fusion Accounting Hub is not the same as a PeopleSoft General Ledger journal. While other documentation may refer to transactions in Fusion Accounting Hub as journals, these are considered accounting entries from a PeopleSoft General Ledger perspective.

ODI

Oracle Data Integrator (ODI) is the vehicle through which transactions are extracted from Fusion Accounting Hub and transported to PeopleSoft General Ledger. ODI is included as part of the Fusion Accounting Hub installation.

Segments (Fusion)

Segments are fields within the Fusion accounting structure and are the Fusion equivalent to PeopleSoft ChartFields. Segments, just as ChartFields, are used to categorize financial or statistical data to record transactions on ledgers or subledgers for the ultimate purpose of meeting reporting requirements. Segments can be fields such as Company, Department, Account, Sub Account, and so on.

SetID

Element of the PeopleSoft architecture that enables the sharing of control data across entities and also enables alignment of certain static data to specific entities. For example, Business Unit US001 can use the shared Account ChartField values from the CORP SetID, but select to use the US001 SetID for its Department ChartField values. Due to this structure, the concatenation of ChartField and SetID represents the equivalent of the Fusion Value Set.

Value Set (Fusion)

Element of the Fusion architecture that describes a group of values for a chart of accounts segment. For example, the Corporate Cost Centers value set holds all of the cost center values for the corporate chart of accounts. A single value set can be assigned to each chart of accounts segment for a ledger. The values are not distinguished by business unit.