Customize SLA Oracle Appication

 Subledger Accounting (SLA) is a dynamic feature of Oracle® R12 that you can use for meeting the accounting needs of the business.

Overview

By using SLA, you can easily modify all the accounting requirements by following a few steps. In this post, I offer five easy steps to customize SLA. By implementing these steps, you can modify the accounting process according to your business needs.

Business Requirement

To illustrate with an example, assume Company ABC Ltd. has included a company, account, and cost center in their chart of account structure, and they use standard accrual at the ledger level for their accounting method.

When they enter a standard invoice in the payables module, SLA generates the following standard accounting entry:

Expense: 001.10100.0001.00000 DR (Manually entered combination)
Liability:  001.20000.0000.00000 CR (Derived from the Supplier/Supplier Site or Financial Options)

The business’s finance department wants the process to pick the Cost Center Segment from the Expense Account entered at the invoice distribution level. Thus, the third segment’s value should be changed from 0000 to 0001 on the Liability account combination.

Solution

To fulfill this business requirement, you need to customize SLA to implement the desired accounting process by using the following steps:

STEP 1: CREATE A NEW ACCOUNT DERIVATION RULE (ADR)

Select Payables > Setup > Accounting Setups > Subledger Accounting Setup > Accounting Method Builder > Journal Entry Setups > Account Derivation Rules.

The rule explains that SLA should pick the value from the standard Oracle source, Invoice Distribution Account, for the COST CENTER segment.

STEP 2: CREATE A JOURNAL LINE DEFINITION (JLD)

A JLD is a set of all the Journal Line Types (JLT) defined for a specific Subledger module.

1. Select Payables > Setup > Accounting Setups > Subledger Accounting Setup > Accounting Method Builder > Methods and Definitions > Journal Line Definitions.

2. Copy the Standard Oracle JLD and create a new JLD, as shown in the following example:

   

3. After you copy the definition, add the ADR rule you created for the COST CENTER segment in Step 1 and save the definition.

Because the example is on the Liability account, you will use the JLT as a Liability, Basic.

STEP 3: CREATE AN APPLICATION ACCOUNTING DEFINITION (AAD)

An AAD is a set of Event Classes or Event Types and JLDs.

1. Select Payables > Setup > Accounting Setups > Subledger Accounting Setup > Accounting Method Builder > Methods and Definitions > Application Accounting Definitions.

2. Copy the Standard Oracle AAD and create a new AAD, as shown in the following example:

   

3. After you copy the definition, add the JLD created in Step 2 and save the definition. You can individually attach the JLD to all the Event Classes. For this session, you can use Event Class as Invoices.

STEP 4: CREATE A SUBLEDGER ACCOUNTING METHOD (SLAM):

A SLAM is a group of AADs defined for the Subledger modules.

1. Select Payables > Setup > Accounting Setups > Subledger Accounting Setup > Accounting Method Builder > Methods and Definitions > Subledger Accounting Method.

2. Copy the standard Oracle SLAM (Standard Accrual) and create a new SLAM, as shown in the following image.

   

3. After you copy the definition, add the AAD you created in Step 3 against the Payables application and save the definition.

4. To run the Validate Accounting Definitions program for Payables, select Payables > View > Request > Submit a New Request.

STEP 5: ATTACH THE SLAM TO THE LEDGER

1. Select Payables > Setup > Accounting Setups > Ledger Setup > Define > Accounting Setups.

   

2. Attach the SLAM created in Step 4 and complete the Ledger setups.

Validation

To validate your SLA setup, create a new invoice, validate it, and run the Create Accounting program.

You can now see the change: The Cost Center value has been changed from 0000 to 0001 for the Liability String.

Expense: 001.10100.0001.00000 DR (Manually entered combination)
Liability:  001.20000.0001.00000 CR (Derived from the SLA)

Conclusion

In R12 Oracle, SLA is one of the most well-organized methodical approaches to confront the accounting needs that various businesses require. Understanding the requirement is the key to this process. After you have a plan ready, you can effortlessly customize the SLA by using the steps in this post to meet your business requirements by customizing SLA.

How To active Audit For Period Status And How To Get Audit Report Oracle fusion Application GL

 How to enable Audit for Period status and how to get audit report for the same?

Please follow below steps to Enable Audit

1) Go to the task Manage Audit Policies

2) Click on Configure Business Object Attribute

3) Select Product as General Ledger

4) Select the Object "Accounting Calendars" to enable the Audit on Accounting Calendar Setup and Period Status

5) In right side the same screen select the audited attributes.

6) Save the work.

To view the Audit report:

1)From homepage > Navigator, select Audit reports under tools.

2)Select the product as 'General Ledger'

3)Business object type 'Period Status'

4)Click on search to see the audit report.

5)Select the show attribute details > All attributes to see the details.

Create analysis using Subject Area ‘General Ledger- Balances Real Time’ In Oracle Fusion

1.      Run or schedule Process “Create Balances Cube” In ESS. This process create Essbase cube.

2.      Run or schedule Process “Create Rules XML File for BI Extender Automation”

3.      Run or schedule Process “Import Oracle Fusion Data Extensions for Transactional Business Intelligence”

4.      Mandatory parameters to use the subject area as follows:-

i)        Navigate to Ledger folder and pull Ledger Name, Chart of Accounts

ii)      Navigate to Time folder and pull Name, Accounting Period Name column.

iii)     Navigate To Currency folder and pull Currency, Currency Type column

iv)     Navigate to Amount Type and pull Amount Type column

v)      Navigate to Scenario folder and pull Scenario column.

vi)     Navigate to Balance folder and pull Beginning Balance and Ending Balance

vii)   Navigate to Cost Center Segment folder and pull Cost Center Code

viii)  Navigate to Natural Account Segment folder and pull Account Code

ix)     Navigate to Balancing Segment folder and pull Balancing Segment Code

x)      Filter on Chart of Accounts

xi)     Filter on Fiscal Calendar Name

xii)   Filter on Accounting Period name for a period which has balances.

xiii)  Run the report.

GL Cross Validation Rules in Oracle Fusion Cloud

Business Requirement : 

If Busines has Cost Center Segment values with Common for Balance sheet and this should not use for P&L Account 

Then business may require COA Restriction required for entering Cost Center as 000- Common and GL Project 0000-Common for all Expense and Revenue GL Account.

Go to System and Maintenance >  Manage Cross-Validation Rule

s

Create Rule :for Example

• Code: CC01_BS
• Description  Common(000)GL Costcenter Restriction for all Expense and Revenue Account
• Effective Date from
• Effective Date to
• Enable : yes
• Filter Conditions : Select where condition GL Account or any Segment on which base system should trigger cross validation rule.
• Ex: Filter Condition Details: account Greater than or equals to 30000000 ( Make sure if this is restricted Account for which Common cost center should not allow)

Condition Filter 1 Filter Conditions Defined Condition Details account Greater than or equals to 30000000 Error Message Name GL_CVR_1005121_300000922647489

Then enter Validation for which system to restrict or allow the Code for any segment:

For this case we need to excluse Common Cost center should not allow for Above GL Account greather than or equal to 30000000 

*Validation Filter	1 Filter Conditions Defined
Validation Details	costCenter Not equals to 000

Finally Check in journal page

 

Oracle Fusion Finance Important Roles

Accounts Payables – User Role

Role	Description
Payables Specialist	Enters invoices ensuring accuracy, uniqueness, and completeness. Matches invoices to correct purchase orders or receipts ensuring that invoices comply with company policy.
Payables Supervisor	Oversees the activities of Accounts Payables Specialists. Initiates and manages pay runs. Resolves non-data entry holds.
Payables Manager	Manages Accounts Payable department and personnel. Overrides exceptions, analyzes Oracle Fusion Payables balances and submits income tax and withholding reports to meet regulatory requirements.

Fixed Assets – User Role

Role	Description
Asset Accountant	Performs asset transactions including additions, adjustments, transfers, and retirements, ensuring accuracy and completeness. Verifies asset information, transaction details, and accounting entries through inquiry and reports.
Asset Accounting Manager	Manages fixed assets department and personnel. Monitors and performs asset transactions, maintain asset books and setups in Oracle Fusion Assets, and views asset information and accounting entries.

Receivables – User Role

Role	Description
Accounts Receivables Specialist	Manages and implements all customer payment activities, including receiving customer payments and electronic remittance advice, performing cash handling activities, processing customer payments, and applying payments to customer accounts
Accounts Receivables Manager	Manages all accounts receivable activities, including defining policy and controls, establishing processes and procedures, resolving issues, monitoring and analyzing accounts receivable balances, and creating reports and business intelligence

Cash Management – User Role

Role	Description
Cash Manager	Protects and develops the company’s liquid assets maximizing their use and return to the organization.

Expenses – User Role

Role	Description
Employee	Identifies the person as an employee
Line Manager/   Approver	Identifies the person as a line manager
Expense Manager	Manages the company’s expense policies and processes. Reviews and proposes changes to expense policies.
Expense Auditor	Reviews and audits expense reports on a daily basis to ensure compliance with the company’s reimbursement policy.
Corporate Card  Administrator	Oversees the functioning of corporate card travel programs and procurement card programs. Provides support to cardholders and assures payments are made timely and no delinquencies are incurred.

Tax – User Role

Role	Description
Tax Manager	Defines the tax policies and the most efficient tax configuration. Sets up relatively stable entities that seldom require updates, such as tax regimes and taxes.
Tax Administrator	Sets up technical areas and the integration with tax service providers
Tax Specialist	Maintains tax configuration, especially the variable entities that require periodic updates, such as tax rates and tax jurisdictions.
Tax Accountant	Prepares and files tax returns and reports for an enterprise, including country, federal, state, and local corporate, payroll, and transaction taxes.

How to apply prepayment invoice to Standard invoice where Invoice currency is different ? Cross Currency Prepayment Application

 

Issue

There are many prepayment invoices in foreign currency which need to be applied to a ledger currency standard invoice but not being able to do this.
Is this the expected behavior?

Solution

Prepayment Invoice can be applied when invoice currency is same as standard invoice

Case: If you pay a prepayment in a currency that is different from the invoice currency, you can apply the prepayment to an invoice provided the invoice currency of the invoice and the invoice currency of the prepayment are the same.

For example, if you have the following payable documents:

  Invoice: Invoice currency = INR, payment currency = USD

  Prepayment: Invoice currency = SAR, payment currency = SAR

You can apply the prepayment to the invoice because both payables documents have an invoice currency of INR

Enable DFF's/KFF's In OTBI Need to enable these attributes in OTBI. These are example DFF's. But this is generic to all DFF's and KFF's that need to be enabled in BI.

 Need to enable these attributes in OTBI. These are example DFF's. But this is generic to all DFF's and KFF's that need to be enabled in BI.

1) Go to  Navigate To Manage Key FlexFields Task, search for GL#

2) Go to Manage Structure Instances task and search for your Chart of Account

3) Edit the segments, CHECK BI Enable check-box

4) Save the changes and deploy the flexfield.

5) Run 'Import Oracle Fusion Data Extensions For Transactional Business

Intelligence' Ess Job.

6) Once Job completes, navigate to Subject area, you should be able to see

missing segments."

Note: All DFF's and KFF's which are edited should be deployed successfully before running the Import process.

usion OTBI How To Avoid Grouping Of Rows Together

Following steps need to be performed in the analysis (before exporting to Excel) to avoid this issue:

1. Move the mouse to the right end of the person number column

2. There would be a pop-up menu displayed, from this menu select Column Properties

3. Click on Column Format tab

4. Under Value Suppression section, click on Repeat radio button

5. Save the analysis and view the results

6. Export to Excel and confirm whether the issue is resolved or not.

EBS to FUSION PA (Project Accounting) Table Changes

 

EBS to FUSION PA (Project Accounting) Table Changes

EBS Tables -----------------------------------------	FUSION Tables -------------------------------------------
PA_PROJECTS_ALL -----------------------------------------	PJF_PROJECTS_ALL_B PJF_PROJECTS_ALL_TL -------------------------------------------
PA_PROJECT_TYPES_ALL -----------------------------------------	PJF_PROJECT_TYPES_B PJF_PROJECT_TYPES_TL -------------------------------------------
PA_PROJECT_STATUSES -----------------------------------------	PJF_PROJECT_STATUSES_B PJF_PROJECT_STATUSES_TL -------------------------------------------
PA_PROJECT_STATUS_CONTROLS -----------------------------------------	PJF_PROJ_STATUS_CONTROLS -------------------------------------------
PA_PROJECT_ACCUM_ACTUALS -----------------------------------------	PJO_PROJECT_PLAN_ACTUALS -------------------------------------------
PA_TASKS -----------------------------------------	PJF_PROJ_ELEMENTS_B PJF_PROJ_ELEMENTS_TL PJF_TASKS_V -------------------------------------------
PA_BUDGET_TYPES -----------------------------------------	PJO_PLAN_TYPES_B -------------------------------------------
PA_EXPENDITURE_TYPES -----------------------------------------	PJF_EXP_TYPES_B PJF_EXP_TYPES_B_ST PJF_EXP_TYPES_TL PJF_EXP_CATEGORIES_B  -------------------------------------------
PA_EXPENDITURE_ITEMS_ALL -----------------------------------------	PJC_EXP_ITEMS_ALL -------------------------------------------
PA_COST_DISTRIBUTION_LINES_ALL  -----------------------------------------	PJC_COST_DIST_LINES_ALL -------------------------------------------
PA_TRANSACTION_SOURCES -----------------------------------------	PJF_TXN_SOURCES_B PJF_TXN_SOURCES_TL -------------------------------------------
PA_IMPLEMENTATIONS_ALL -----------------------------------------	PJF_BU_IMPL_ALL -------------------------------------------
PA_EXPENDITURE_COMMENTS -----------------------------------------	PJC_EXP_COMMENTS -------------------------------------------
PA_CUST_REV_DIST_LINES_ALL -----------------------------------------	PJB_REV_DISTRIBUTIONS -------------------------------------------
PA_TASKS -----------------------------------------	PJF_TASKS_V -------------------------------------------
PA_EXPENDITURE_ITEMS_ALL, PA_EXPENDITURES_ALL -----------------------------------------	PJC_EXP_ITEMS_ALL -------------------------------------------
PA_EXPENDITURE_TYPES -----------------------------------------	PJF_EXP_TYPES_B PJF_EXP_TYPES_B_ST PJF_EXP_TYPES_TL -------------------------------------------
PA_EVENTS -----------------------------------------	PJB_BILLING_EVENTS -------------------------------------------
PA_PROJECT_PARTIES -----------------------------------------	PJF_PROJECT_PARTIES -------------------------------------------
PA_PROJECT_ROLE_TYPES_B -----------------------------------------	PJF_PROJ_ROLE_TYPES_B -------------------------------------------