Sla Practices PDF

Chinmayee Pattanaik

Oracle Global Support :

Principal Support Engineer

Expertise :

EBS - Financials Receivables

2 | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. | Confidential - Oracle Internal

SLA - Best Practices Why?

Central Source of Truth

Industry Specific Accounting Requirement

Do’s & Don'ts

Check list of 10 Best Practices


Agenda

What Is SLA?

10 Best Practices

Where to look for more information?

Q & A


What is SLA?


Which EBS modules in R12?

Payables

Assets

Purchasing

Projects

Inventory

Receivables

Leasing

Payroll


What is SLA?


10 Best Practices

1 • Upgrade - Considerations for SLA

2 • Set Up Components Reusability

3 • Naming Conventions

4 • Judicious JLT and ADR Definition

5 • Minimal Usage of Constant Values

6 • Minimal Usage of Custom Sources

7 • Judicious Use Of Summarization

8 • Supporting Reference

9 • Receivables Merge Distributions

10 • Performance Guidelines


• Upgrade - Considerations for SLA Upgrade

Considerations

• Set Up Components Reusability

• Naming Conventions

• Judicious JLT and ADR Definition

• Minimal Usage of Constant Values

• Minimal Usage of Custom Sources

Setup Considerations

• Judicious Use Of Summarization

• Supporting Reference

• Receivables Merge Distributions

• Performance Guidelines

Features

10 Best Practices


• Upgrade - Considerations for SLA

Upgrade Considerations


Best Practice 1

Upgrade - Considerations for SLA

Evaluate business requirements – Can impact increased data volume / system resources

How far back?

Only upgrade the data that you need.

For E.g. Open transactions / Last successfully reconciled period



To upgrade historical data after R12 upgrade

- Run SLA hot patch

OR

- "Upgrade Historical Subledger Transaction Accounting

Program” (Introduced in R12.1.2)

Before running SLA post-upgrade - Enter Initial Date

Profile Option “SLA: Initial Date for Historical Upgrade”


Best Practice 1


FAQ for the SLA Pre Post-Upgrade & Hot Patch –

Doc ID 604893.1

Upgrade Historical Subledger Transaction Accounting Program –

Doc ID 1376752.1

Oracle Apps Release 12 Upgrade Sizing and Best Practices –

Doc ID 399362.1


Best Practice 1







10 Best Practices

Best Practice 2

Set Up Components Reusability

Quickly create rules, copy and reuse to meet similar,

yet distinct requirements.

Enables to separately define & reuse setups for each

component of a journal entry, such as the journal line types,

journal line descriptions etc.


Accounting Method Builder - AMB


Best Practice 2

GL Account on Distribution for Invoices, Debit Memos, Deposits, Guarantees, and Charge backs Distributions

Source: Transaction Distribution GL Account


Best Practice 2

Naming Conventions

Define self explanatory naming conventions

Use consciously for all setup components.

Should be consistent

Follow standard Oracle naming standards.

Good Example: AP_BANK_ERRORS_NAT_ACCT

Best Practice 3


Judicious JLT and ADR Definition

Single JLT - If different attributes like Side, Balance Type are same

Don't group together significantly different JLTs

Maximize use of mapping sets and/or conditions at the ADR level.

Benefits :

Increases functional component reusability.

Reduces maintenance.

Reduces the AAD package size.

Best Practice 4


Best Practice 4 Journal Line Type - Definitions


Minimal Usage of Constant Values

Minimize hard coding constant values in the setup.

Can use in an ADR if 2/3 possible values

Use sources instead.

Making them reusable:

1. saves functional effort

2. reduces the size of the AAD package.

Best Practice 5



Best Practice 5

Minimal Usage of Custom Sources

Use the custom sources as little as possible.

Use transaction object (Extract View) instead, if possible.

This will improve the performance of the accounting program

Best Practice 6






Features

10 Best Practices


Judicious Use Of Summarization

The Journal Entry Summarization Option –

Determines amount of summarization done when

subledger journal entries are transferred to GL

It can be set to the following values: Summarize by GL Date

Summarize by GL Period

No Summarization

Level of summarization has a direct impact on Data growth in the XLA and GL tables

Create Accounting Performance.

Best Practice 7



To access this screen, from the GL Super User Responsibility:

(N) Setup ~ Financials ~ Accounting Setup Manager ~ Accounting Setups ~

Subledger Accounting Options, and select specific sub-ledger

Best Practice 7



Note: The Journal Entry Summarization option shouldn't be confused

with the “Merge Matching Lines” of the JLT that summarizes journals

lines within XLA tables.

Best Practice 7



The 2 options work together as shown in the following table:

GL Journal Entry

Summarization

JLT -Transfer to GL Expected behavior

Summarize

(By GL Date or Period)

Summary Summarized at both

GL_JE_HEADERS and

GL_JE_LINES

Summarize

(By GL Date or Period)

Detail Summarized at

GL_JE_HEADERS, detail

GL_JE_LINES

No Summarization Detail Detailed at

GL_JE_HEADERS

and GL_JE_LINES

No Summarization Summary Detailed at

GL_JE_HEADERS

and GL_JE_LINES

Best Practice 7



FAQ on Transfer to GL in R12 –

Doc ID 876190.1

What Do Group By GL Date And Group By GL Period Options

In Accounting Setup Manager Do? –

Doc ID 1289618.1

Best Practice 7


Supporting Reference

Stores additional source information about subledger

journal entry either at the header or line level.

Allows to ‘tag’ transactions for reporting –

for which SLA will maintain balances

Review before implementing Supporting Reference.

Not maintained in ‘Entered Currency’.

Not posted to Oracle General Ledger.

Tracks balances only at the period level

Best Practice 8


Supporting Reference

FAQ about Supporting References – Doc ID 790978.1

Best Practice 8


Receivables Merge Distributions

Merge Distributions feature - Summarized Distributions for

adjustments & applications created at invoice header level.

Driven by the checkbox “Create Detailed Distributions”

on the System Options form.


Best Practice 9

Benefits of Business Solution

Significant performance gain - creating accounting

Limits the growth of data volume.

Summary distributions are easier to interpret


Best Practice 9


Merged Distributions feature should not be enabled if using

Cash Basis Accounting

Multi-Fund Accounts Receivable

Line Level Cash Applications


Best Practice 9


System Options Form: What is the Checkbox 'Create

Detailed Distributions' for? –

Doc ID 1081657.1

New Feature Release: Receivables Merged Distributions –

Doc ID 1374115.1

Best Practice 9


Performance Guidelines

Apply the latest performance patches.

Setup parallel processing in Create Accounting

Accounting Setup Manager – update >

Subledger Accounting Options - update >

Update System Options (for the application).

Note:

Parallelization is limited to Accounting program processing

Not extended to GL Transfer/Posting.

This is applicable per ledger per application.

Best Practice 10

Performance Guidelines

How to Improve Performance in SLA & FAH –

Doc ID 791049.1

Performance issues on SLA tables for 11.2.0.3 Database –

Doc ID 1465689.1


Best Practice 10

• Upgrade - Considerations for SLA Upgrade

Considerations











Features

10 Best Practices


Looking for more information?

Latest Financials Recommended Patch Collections –

Doc ID 954704.1

Advisor Webcasts-Current Schedule & Archived Recording –

Doc ID 740966.1

Refer My Oracle Support Communities –

Doc ID 973667.1

Subscribe to Oracle Support Newsletters


Chinmayee Pattanaik

Oracle Global Support :

Principal Support Engineer

Expertise :

EBS - Financials Receivables


Sla Practices PDF

Documents

Transcript of Sla Practices PDF