SLA Accounting Setup — Oracle EBS R12 & Fusion Cloud

Three Modes — One Tool

● Oracle EBS R12

Generates setup instructions using R12 SLA Workbench navigation — Accounting Methods Builder, Journal Line Types, Account Derivation Rules, and Subledger Accounting Methods. All 7 R12 subledgers covered including Payroll and Projects costing.

● Oracle Fusion Cloud

Generates setup instructions using Fusion Accounting Methods Builder (AMB) terminology and navigation paths. Covers Fusion-specific differences in event class structure, journal entry rule sets, and SLAM assignment through Accounting Configuration.

● R12 → Fusion Migration

Uses the R12 question set and adds migration impact notes throughout — identifying which ADRs, JLDs, and AADs must be manually recreated in Fusion AMB, which seeded Fusion rules may replace custom R12 rules, and where terminology differs between platforms.

Why migration mode matters for SLA Accounting Setup Custom SLA rules do not migrate from R12 to Fusion. Every ADR, JLD, and AAD must be recreated from scratch in the Fusion Accounting Methods Builder using different terminology and a different rule hierarchy. Migration mode surfaces these gaps at every configuration step so nothing is missed during cutover.

How This Fits in the SLA Workstream

SLA setup has two distinct phases. Use them in order.

Step 1 — First: SLA Rules Design

Determine what SLA rules your implementation needs and why. Covers all subledgers at once in a broad design session. Produces a stakeholder sign-off document that gates the start of configuration. Use this first.

Go to SLA Rules Design →

Step 2 — This Guide: SLA Accounting Setup

Configure each individual rule in the system. One subledger at a time. Collects exact technical parameters — event class, ADR type, JLD name, accounting class, SLAM effective dates, mapping set rows — and produces a 6-step configuration spec.

Example workflow You run SLA Rules Design and decide you need a custom AP supplier routing rule and a custom FA asset category rule. You get sign-off on that design. Then you run this guide twice — once for AP, once for FA — to produce the technical setup specs for each rule.

The SLA Hierarchy

This guide walks you through every layer of the SLA stack, bottom to top. Each layer depends on the one below it.

ADR

→

Account Derivation Rule — how to derive the account (constant, source, mapping set, prior entry)

JLD

→

Journal Line Definition — which journal line uses the ADR, natural side, accounting class

AAD

→

Application Accounting Definition — the complete set of JLDs for an event type

SLAM

→

Subledger Accounting Method — the collection of AADs for all event types in an application

Ledger

Ledger Assignment — the SLAM is assigned to the ledger to activate the custom rules

7 Subledgers Covered

APAccounts Payable — Invoice, Payment, Prepayment, Credit Memo, Withholding Tax

ARAccounts Receivable — Invoice, Receipt, Adjustment, Credit Memo, Bills Receivable

COSTCost Management — WIP, Inventory, PO Write-Off, Receiving events

FAFixed Assets — Addition, Adjustment, Depreciation, Retirement, CIP

POPurchasing / Receiving — Receiving Inspection, Accrual, Write-Off, Unordered Receipt

PAYPayroll — Regular, Retro Pay, Payroll Payment, Payroll Accrual

PAProjects — Expenditure, Burden, Revenue, Adjustment events

What You Get

AI-authored executive summary interpreting your SLA configuration profile and scope
SLA architecture narrative — how your specific ADR, JLD, AAD, and SLAM fit together
6-step setup runbook with specific navigation paths and parameter values
Required Oracle profile option settings with recommended values
GL transfer runbook — online vs. batch vs. standalone procedures for your subledger
Testing procedure — draft accounting, final accounting, and reconciliation steps
Risk assessment with mitigations (SLAM effective dates, retroactive processing, mapping set gaps)
Event and journal line matrix — which event classes affect which journal line types
Mapping set rows (if applicable) — captured inline during the session
Suggested naming conventions for ADR, JLD, AAD, and SLAM
Migration notes for R12 → Fusion teams
Print to PDF directly from the browser

When to Use This Guide

Use this guide when you have a specific rule to configure Run it once per rule change. If you need to change AP invoice accounting by supplier type AND change FA depreciation by asset category, run it twice — once for each. This keeps each configuration spec clean and reviewable.

Run SLA Rules Design first if you haven't already If you haven't done SLA Rules Design (Step 1), do that first. It answers the "what do we need?" question. This guide answers the "how do we configure it?" question. They are designed to be used together.

Ready to Configure Your SLA Rule?

15–25 minutes per rule. All 7 subledgers. Generates a professional 6-step setup spec.

$499 Free Limited time — no account required

Launch SLA Accounting Setup → See a sample report →