Company, Business Unit and Address Book: JD Edwards' organisational spine

How JD Edwards' Company, Business Unit and Address Book decompose into D365 legal entities, sites, warehouses, financial dimensions and the Global Address Book — including the one genuinely close mapping in the whole path, and a worked decomposition of a real Business Unit.

What you will be able to do

Introduction

Three JDE master objects carry almost the entire organisational and party model of a typical estate: Company, Business Unit, and Address Book. Between them they answer "who is the legal entity," "what is the reporting and cost structure," and "who are we dealing with" — three questions D365 also has to answer, but not with a one-to-one…

Company, and the special case of company 00000

A JDE Company (F0010) is the statutory container: it carries a base currency, a Fiscal Date Pattern assignment, and the default Automatic Accounting Instructions and Next Number ranges that transactions posted under it will use unless overridden lower down.

Business Unit: the universal cost centre and account-key spine

Business Unit (data item MCU, master table F0006) is the single busiest object in JDE's organisational model, because it does three distinct jobs at once:

Branch/Plant: one JDE object, three D365 objects

A Branch/Plant is not a separate master table — it is a Business Unit that has been flagged, through F41001 Branch/Plant Constants, as also carrying inventory, manufacturing and distribution behaviour: a default location, a costing method, manufacturing constants, and the warehouse and locations that sit beneath it.

Address Book: the one genuinely close mapping

Address Book (F0101, keyed by Address Book Number, AN8) is JDE's single master for every kind of party: customers, suppliers, employees, banks, tax authorities, even competitors, all as one central record with a name, address and search type.

Category codes: JDE's open reporting axes, and how to triage them

Both Business Unit and Address Book carry up to thirty user-defined category codes each — open, UDC-validated classification fields that a site can use for almost anything: region, division, industry, risk tier, salesperson group.

Fiscal date patterns and multi-company calendars

A Fiscal Date Pattern (F0008) is a single-character code — commonly A for a standard calendar-month pattern — that defines the start and end date of every period in a fiscal year, including 4-4-5 or other non-calendar-month patterns some manufacturing and retail sites use.

Worked decomposition: one Business Unit, fully decomposed

Take a representative Business Unit, 30 — a distribution Branch/Plant for a mid-market distributor, carrying Category Code 01 (Region = West), Category Code 02 (Division = Wholesale), and flagged in F41001 as a full inventory and distribution location with its own default carrier and costing method.

Knowledge check

Summary

Company, Business Unit and Address Book carry almost the whole of JDE's organisational model, and they do not decompose symmetrically. Company maps closely onto legal entity, with company 00000 needing to be traced rather than migrated.