E1: 09: Overview of the Use of Subledgers within General Accounting (F0911/F0902) (Doc ID 1440893.1)

Last updated on OCTOBER 25, 2023

Applies to:

JD Edwards EnterpriseOne General Ledger - Version XE and later
Information in this document applies to any platform.

Purpose

Overview

In addition to the business unit.object.subsidiary method of account coding, you can use subledgers to code accounts. Subledgers provide the most detailed record of accounting activity for a business unit. You might use subledger accounting to track:

Revenues and expenses by account representative.
Receivables and payables by employee.
Intercompany settlements by detail entry.

With subledger accounting, you can:

Review detailed account totals for specific subledgers by grouping posted transactions with the same subledger and subledger type.
Review similar types of subledgers across accounts. For example, you can review all accounting activity by an asset ID or work order number.

Subledger Type UDC Codes (00/ST)

You can set up detailed auxiliary accounting within a general ledger account using subledger type codes in UDC table 00/ST. A subledger type code, such as A for address book, is associated with a number, such as an employee number. Subledger type codes also control how the system validates a subledger value when you create a journal entry.

Examples:

Before you can use subledgers, you must decide which subledger types to use. The system verifies the subledger number for each type against a specific master table. The following list describes the predefined, hard-coded subledger types:

Subledger Type	Master Table
A	Validates against the Address Book Master table (F0101). This type is the most commonly used subledger type. Use this type to track expenses that are associated with sales people, employees, and so on. You also use it for the detail method '2' of intercompany settlements.
C	Validates against the Business Unit Master table (F0006).
E	Validates against the Asset Master File table (F1201).
I	Validates against the Item Master table (F4101).
J	Validates against the Change Request Master Table (F5301).
L	Validates against the Tenant/Lease Master table (F1501).
O	Validates against the Sales Order Header File table (F4201).
S	Validates against the Chart of Accounts Format table (F0907). This is the structured subledger type. For more information on this, see section below "Structured (Flex Format) Subledgers".
W P	Validates against the Work Order Master File table (F4801). Validates for Revenue Performance Obligation. A new feature introduced in E1 9.1

NOTE: Since Subledger types are hard-coded to validate against certain files, there is no recommended procedure or workaround other than customization for setting up a user-defined subledger type to validate against a particular table. The only way for validation to occur on a custom subledger type is to add custom modifications to the two C standard business functions, B0000021-Format Subledger field function and X0909-ValidateSubledger function. These two business functions perform the formatting and validation for the subledger values. Customizing a C business function requires advanced knowledge of C programming. Oracle Software Support does not help with C programming, which is outside of the support scope. Please refer to <Document 963842.1> for more details.

Scope

This document provides an overview of use of Subledgers within General Accounting and discusses how to assign and modify Subledger PEC for an account, Structured (S) and Additional Subledger Types (X, Y and Z), how to inactivate Subledgers, differences between Subledger and Subsidiary Accounting and different options available for Reporting by Subledger.