# JDE F0911 Table Growth Forecast Calculator

> Source: https://netray.co/tools/jde-f0911-table-growth-forecast-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Project F0911 Account Ledger size over a horizon from daily documents, lines per document, row bytes, index overhead and annual volume growth.

## Category

oracle

## Erp

Oracle JD Edwards EnterpriseOne

## Audience

- JDE CNC administrator
- DBA
- Finance systems lead

## Tool

**Kind:** calculator

**Inputs:**

#### Journal documents per working day

**Key:** docs

**Type:** number

**Default:** 2500

**Min:** 0

**Step:** 100

**Unit:** docs

#### Average lines per document

**Key:** lines

**Type:** number

**Default:** 6

**Min:** 1

**Step:** 1

**Unit:** lines

**Help:** Each line is one F0911 row.

#### Working days per year

**Key:** days

**Type:** number

**Default:** 250

**Min:** 1

**Max:** 366

**Step:** 1

**Unit:** days

#### Average row size

**Key:** row_bytes

**Type:** number

**Default:** 700

**Min:** 50

**Step:** 25

**Unit:** bytes

**Help:** Assumed figure. Get yours from the DBA: table size divided by row count.

#### Index and overhead multiplier

**Key:** index_factor

**Type:** number

**Default:** 1.6

**Min:** 1

**Max:** 4

**Step:** 0.1

**Help:** Total segment size including indexes divided by data size.

#### Annual volume growth

**Key:** growth

**Type:** number

**Default:** 8

**Min:** 0

**Max:** 100

**Step:** 1

**Unit:** %

#### Current F0911 size

**Key:** current_gb

**Type:** number

**Default:** 40

**Min:** 0

**Step:** 5

**Unit:** GB

#### Space allocated for the table

**Key:** capacity_gb

**Type:** number

**Default:** 500

**Min:** 1

**Step:** 25

**Unit:** GB

#### Forecast horizon

**Key:** years

**Type:** slider

**Default:** 5

**Min:** 1

**Max:** 10

**Step:** 1

**Unit:** years

**Outputs:**

#### New rows in year one

**Key:** rows_year

**Expr:** docs * lines * days

**Format:** integer

#### Year one growth

**Key:** gb_year1

**Expr:** rows_year * row_bytes * index_factor / 1000000000

**Format:** decimal

**Description:** GB added in the first year.

#### Total growth over horizon

**Key:** added

**Expr:** if(eq(growth, 0), gb_year1 * years, gb_year1 * (pow(1 + growth / 100, years) - 1) / (growth / 100))

**Format:** decimal

**Description:** Geometric sum of yearly additions.

#### Projected size at horizon

**Key:** projected

**Expr:** current_gb + added

**Format:** decimal

**Primary:** true

#### Headroom against allocation

**Key:** headroom

**Expr:** capacity_gb - projected

**Format:** decimal

**Primary:** true

**Description:** Negative means you run out of space before the horizon.

**Chart:**

#### Projected F0911 size vs years

**Type:** line

**X:** years

**From:** 1

**To:** 10

**Steps:** 10

**Series:**

- projected

**Disclaimer:** Sizing estimate in GB (decimal). Row size varies with description and remark fields, so calibrate with your own database statistics.

## Content

**Intro:** F0911 is the Account Ledger in JD Edwards, and for most customers it is among the largest tables because every posted journal line lands there. This forecast tells you when it will outgrow its storage so archive and purge work can be planned, not rushed.

**Sections:**

#### How to use it

**Body:** Count journal documents per day from the Account Ledger by document type or from posting statistics, and enter average lines per document. Take row size from database statistics rather than guessing. Set annual growth from the past two years of row counts. The chart shows the projected total for each horizon so you can pick the year you cross capacity.

#### The method

**Body:** Year one rows are documents times lines times days. Bytes are rows times row size times the index multiplier. Later years grow by the volume percentage, so total added over N years is the first-year amount times the geometric sum. Add that to current size to get the projection.

**Bullets:**

- Include indexes; they can rival the data itself.
- Add related tables such as F0902 separately.
- Remember database logs and backups scale with it.

#### Reading the result

**Body:** If headroom turns negative inside three years, start the archive design now. Archiving needs agreement on retention with finance and audit before anyone deletes rows. Also plan for what reports still need prior-year detail, because purging without checking those reports is how month-end surprises happen.

**Cta:** Netray can help scope archive and purge options and the reports that depend on historical ledger rows.

**Faq:**

#### Does F0911 include all my GL activity?

**Answer:** It holds the detail transaction lines. Balances live in other tables such as F0902, which you should size separately because their growth pattern differs.

#### How do I find my row size?

**Answer:** Ask your DBA for the table's allocated size and row count, then divide. Include index segments separately to derive your own multiplier.

#### Can I just archive old years?

**Answer:** Often yes, but only after finance, audit and reporting owners agree on retention and you confirm no report depends on the archived rows.

#### Is growth really geometric?

**Answer:** It is a reasonable approximation when volume grows by a steady percentage. Acquisitions or new modules cause steps that this model will not predict.

## Search terms

jde f0911 table size, jd edwards account ledger growth, jde database growth forecast, f0911 archive planning, jde database storage sizing, jde general ledger table purge

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json