ORACLE FUSION

Subledger Accounting (SLA)

Support Training
Mihai Fildan
Principal Technical Support Engineer

Fusion Financial Support

GL, SLA, Tax
Agenda
1. What is SLA
2. SLA Components
3. SLA Issues
4. Create Accounting
5. SLA Troubleshooting
6. XLA Tables
7. SLA Queries
8. TEST CASE: SLA Configuration in AR
 1. What is SLA

Subledger Accounting (SLA) ... SLA is a

common rule-based accounting engine used by
Oracle products that posts accounting entries
into Oracle General Ledger. Rules are user
defined, and reside in a common repository for
all subledger applications such
as Oracle Payables, Oracle Receivables,
Oracle Cost Management.
 Why need SLA
To separate the Transaction from the Accounting
To Create Accounting for any condition or regulation

Transaction
Create Accounting

SLA Journal Entry

Journal Import

GL Journal Entry

Posting

GL Balances
Technical Architecture of SLA
 SubLedger Accounting
Sources
Payables
Receivables Manual
Journals
Assets SLA
Spreadsheet
Cash Management (APPLICATION_ID)
GL Journals

Projects
EVENT_ID
EVENT_TYPE_CODE
Copy
Cost Management Journals

Payroll
2. SLA Components
 SLA Components
Accounting Method (AM)
Standard Accrual
Cash
Encumbrance
Subledger Journal Entry Rule Sets (SJERS)
Journal Line Rules (JLR)
Account Rules (AR)
Description Rules (DR)
Supporting Reference (SRef)
 SLA Components
Subledger Journal Entry Rule Sets (SJERS)
JLR+AR+DR+SRef

Journal Line Rules (JLR)

Amount (Entered, Accounted)
Amount Side (DR or CR)
Currency
Account combination

Account Rules (AR)

Account combination
Segment
Value Set

Description Rules (DR)

Header and Line description

Supporting references (SRef)

Are data items that:
Store additional transaction information, at header or line level, to be used for analytical
purposes
Maintain account balances for a specific ledger at period level for every combinations of SRef
+ Code combination ID (CCID)
 3. SLA Issues
Create Accounting ends in error due incorrect
SLA configuration
How can configure SLA?

Overview of Subledger Accounting Setup,

Processes and Reports in Oracle Fusion
(Doc ID 1344473.1)
 4. Create Accounting
1) Online Accounting (for single entity)
2) Create Accounting process (for more entities)

DRAFT will create Journal Entries, which are NOT final, which
means they are NOT ready to be transferred to GL.
You can see the accounting in XLA_AE_HEADERS and
XLA_AE_LINES.
XLA_AE_HEADERS.accounting_entry_status_code is 'D'
XLA_EVENTS.process_status_code is 'D'
XLA_EVENTS.event_status_code is 'U'
You can run create accounting on this transaction again and again,
which will delete the old journal entries and create new ones.
You can't transfer these journal entries to GL.
 Create Accounting

FINAL will create journal entries, which can be transferred to GL.

You can see the accounting in XLA_AE_HEADERS and
XLA_AE_LINES.
XLA_AE_HEADERS.accounting_entry_status_code is 'F'
XLA_EVENTS.process_status_code is 'P'
XLA_EVENTS.event_status_code is 'P'

Once it is finally accounted you can NOT run create accounting on

the particular transaction (specifically on that event).

You can transfer them to GL using Transfer Journal Entries to GL

program.
 Create Accounting
POST TO LEDGER will create journal entries in Final Mode, Transfer
them to GL and Post them.
You can see the accounting in XLA_AE_HEADERS and
XLA_AE_LINES.
XLA_AE_HEADERS.accounting_entry_status_code is 'F'
XLA_EVENTS.process_status_code is 'P'
XLA_EVENTS.event_status_code is 'P'
Once it is finally accounted you can NOT run create accounting on the
particular transaction (specifically on that event).
It will transfer the journal entries to GL using Journal Import and you
can find the data in GL_JE_HEADERS and GL_JE_LINES.
XLA_AE_HEADERS.transfer_status_code is Y.
It will post to gl_balances also (GL_JE_HEADERS.status is 'P').
 Create Accounting Process

55845 Create Accounting (XLAFSNAPRPT)

55846 Create Accounting Subprocess (XLAFSNAPENG)
55847 Post Subledger Journal Entries (XLAGLTRN)
55848 Post Subledger Journal Entries Subprocess (XLAGLTRNW)
55949 Import Journals: Child (JournalImport)
55850 Post Journals for Single Ledger (PostingSingleLedger)
55851 Maintain Payables Trial Balance Report (TrialBalMaintain)
55852 Create Accounting Execution Report (XLAFSNAPRPTRPT)
Create Accounting Parameters
Create Accounting common errors
Error code or message
ERROR:ESS-07034 Job logic indicated a business
error occurred while executing an asynchronous java
job for request 498804. Job error is: BIP job failed.
The Company segment value in the account
10.0000.27050.0.0.0.99.99999 is not assigned to the
ledger
The LEGAL ENTITY segment value in the account
XXX-XXX-..-XXX is not assigned to the ledger .
Subledger Accounting was unable to retrieve a value
for the accounting flexfield account rule
The account XXX-XXX-XXX-XXX is not enabled.
The combination cannot be used, it either does not
exist or using it is not permitted.
Account rule errors
Investigation, possible causes
Reviewing:
- bipublisher.log:
- bi_server1-diagnostic.log
- bi_server1.out
(SQL query time exceeds the limit (600 sec)
https://docs.oracle.com/middleware/12212/bip/BIPAD/GUID-A9AF337A-
7A62-4BCB-B22A-7ECBCCB2869E.htm#BIPAD4858
BSV is not assigned to Ledger. Accounting Configuration
was changed
Accounting configuration was changed (BU assigned to
LE in Business Unit Functions task)
Account rule issue
Inactive account (Disabled or end-date)
The account code combination did not have allow posting Yes.
COA Security rule
Cross validation rules
Reviewing SLA Setup (Account rule setup and conditions)
 5. SLA Troubleshooting
Troubleshooting

1.) Review the 'Create Accounting Execution Report,' ideally at

a detail level
2.) Identify the event (type) where the report indicates an error
3.) Confirm the customer's current SLA setup for the ledger
against which they are running Create Entries
4.) Match the failed event(s)/type(s) with the current setup and
determine the change based on your needs
5.) SLA Accounting Event Diagnostic Report
6.) SQL Query analysis (XLA_EVENTS, XLA_AE_HEADERS,
XLA_AE_LINES)
Create Accounting Execution Report
Accounting Event Diagnostic Report (XLAAPDIAG)
XLA_DIAGNOSTIC_MODE profile
Accounting Event Diagnostic Report (XLAAPDIAG)
6. XLA TABLES
 XLA TABLES

Payables
 XLA TABLES
XLA_EVENTS
EVENT_STATUS_CODE Meaning
Event type code

I Incomplete
N No action
P Processed
U Unprocessed

PROCESS_STATUS_CODE Meaning
Processing status code
D Draft

E Error

I Incomplete

P Processed

R Related event in error

U Unprocessed
 XLA TABLES
XLA_AE_HEADERS
XLA_ACCOUNTING_ENTRY_STATUS

CODE MEANING

D Draft

F Final

I Invalid

N Incomplete

R Invalid Related Entry

 7. SLA Queries
-- RECEIVABLES TRANSACTION ACCOUNTING LINES

SELECT
xv.EVENT_DATE,
xv.ENTITY_ID,
xv.EVENT_STATUS_CODE,
xv.PROCESS_STATUS_CODE,
xah.event_id,
xah.event_type_code,
xah.gl_transfer_status_code,
xah.ACCOUNTING_ENTRY_STATUS_CODE,
xah.PRODUCT_RULE_CODE,
xah.description,
xal.ae_line_num,
xal.ACCOUNTING_CLASS_CODE,
gcc.segment1 || '-' || gcc.segment2 || '-' || gcc.segment3 || '-' || gcc.segment4 || '-' || gcc.segment5 || '-' || gcc.segment6 account,
xal.entered_dr,
xal.entered_cr,
xal.accounted_dr,
xal.accounted_cr,
xal.gl_sl_link_id
FROM xla_ae_lines xal,
gl_code_combinations gcc,
xla_ae_headers xah,
xla_events xv
WHERE 1=1
and xal.code_combination_id = gcc.code_combination_id
and xal.ae_header_id = xah.ae_header_id
and xah.event_id = xv.event_id
and xal.application_id = 222
and xv.event_id in
(select event_id from RA_CUST_TRX_LINE_GL_DIST_ALL where CUSTOMER_TRX_ID = 300000006248619)
order by ae_line_num
 SLA Queries
-- RECEIPTS NOT PROCESSED TRANSFERRED TO GL
select *
from XLA_EVENTS xe,
AR_CASH_RECEIPT_HISTORY_ALL acrh,
AR_CASH_RECEIPTS_ALL acr
where 1=1
and xe.event_id = acrh.event_id
and acrh.cash_receipt_id = acr.cash_receipt_id
and xe.application_id = 222
and xe.event_status_code <> 'P'
and xe.event_date between '01-JUl-2017' and '31-JUL-2017'
and xe.event_type_code like 'REC%'
 SLA Queries
-- PAYABLES INVOICE TRANSACTION ACCOUNTING LINES
SELECT
xv.EVENT_DATE,
xv.ENTITY_ID,
xv.EVENT_STATUS_CODE,
xv.PROCESS_STATUS_CODE,
xah.event_id,
xah.event_type_code,
xah.gl_transfer_status_code,
xah.ACCOUNTING_ENTRY_STATUS_CODE,
xah.PRODUCT_RULE_CODE,
xah.description,
xal.ae_line_num,
xal.ACCOUNTING_CLASS_CODE,
gcc.segment1 || '-' || gcc.segment2 || '-' || gcc.segment3 || '-' || gcc.segment4 || '-' || gcc.segment5 || '-' || gcc.segment6 account,
xal.entered_dr,
xal.entered_cr,
xal.accounted_dr,
xal.accounted_cr,
xal.gl_sl_link_id
FROM xla_ae_lines xal,
gl_code_combinations gcc,
xla_ae_headers xah,
xla_events xv
WHERE 1=1
and xal.code_combination_id = gcc.code_combination_id
and xal.ae_header_id = xah.ae_header_id
and xah.event_id = xv.event_id
and xal.application_id = 200
and xv.event_id in
(select accounting_event_id from AP_INVOICE_DISTRIBUTIONS_ALL where INVOICE_ID = 300000005625262)
order by ae_line_num
 SLA Queries
-- PAYABLES PAYMENT ACCOUNTING LINES
SELECT
xv.EVENT_DATE,
xv.ENTITY_ID,
xv.EVENT_STATUS_CODE,
xv.PROCESS_STATUS_CODE,
xah.event_id,
xah.event_type_code,
xah.gl_transfer_status_code,
xah.ACCOUNTING_ENTRY_STATUS_CODE,
xah.PRODUCT_RULE_CODE,
xah.description,
xal.ae_line_num,
xal.ACCOUNTING_CLASS_CODE,
gcc.segment1 || '-' || gcc.segment2 || '-' || gcc.segment3 || '-' || gcc.segment4 || '-' || gcc.segment5 || '-' || gcc.segment6 account,
xal.entered_dr,
xal.entered_cr,
xal.accounted_dr,
xal.accounted_cr,
xal.gl_sl_link_id
FROM xla_ae_lines xal,
gl_code_combinations gcc,
xla_ae_headers xah,
xla_events xv
WHERE 1=1
and xal.code_combination_id = gcc.code_combination_id
and xal.ae_header_id = xah.ae_header_id
and xah.event_id = xv.event_id
and xal.application_id = 200
and xv.event_id in
(select accounting_event_id from AP_INVOICE_PAYMENTS_ALL where INVOICE_ID = 300000006299261)
order by ae_line_num
8. TEST CASE SLA CUSTOMIZATION

Receivables
8. TEST CASE: SLA Configuration in AR

1. Create new Accounting Method (AM)

2. Create new custom SLJERS and assign to AM
3. Create new custom JLR
4. Assign AM to Ledger
5. Create Account Rule and assign to JERS
6. Test custom SLA
Subledger Accounting Method Setups Report
QUESTIONS
ANSWERS