SLA Process Design Flaw_Allowing Manual Journal Entries in Subledgers

Background: In R12, Oracle dramatically changed their subledger architecture by introducing SLA
Sub-Ledger Architecture. This change helps to standardize the way accounting is stored and transferred
to the General Ledger and also allow multiple accounting methods for subledger activity. In the SLA
architecture and design of function security, Oracle introduced some significant flaws. We will look at
three issues:

Ability to create a manual journal entry through the subledgers

Ability to create a manual journal entry through an inquiry menu
Inconsistencies in the design of subledger menus and seeded responsibilities

Critical function: SLA: Create Subledger Journal Entry

First, a demonstration of how to enter a manual journal entry at the subledger level

ERPRA 2011

Choose Journal Entries and you will receive this screen:

Press the Create Journal Entry button and you will receive this screen:

ERPRA 2011

You can create a Journal Entry here as follows:

Press Continue and you will receive this screen:

ERPRA 2011

Press the Finish button and you will receive this message:

ERPRA 2011

Journal Sources Configuration

ERPRA 2011

Examples of seeded menus / responsibilities with this flaw

Note inconsistency within Oracle in how these are handled
Project Costing Super User
with Function Exclusion

Payables Manager
w/o function exclusion, but with the function

ERPRA 2011

Receivables Manager:
w/o function exclusion, but with the function

Cash Management:

ERPRA 2011