By Annemarie Provisero-Oracle on Mar 07, 2016
- Cash Management
- Collections (coming soon)
- E-Business Tax
- Reporting Ledger
- Sub-Ledger Accounting
- Internet Expenses
The integration between the Accounting Hub Reporting Cloud Service and E-Business Suite Release12 continuously streams balances from EBS,
We encourage you to benefit and improve your business with Oracle ERP Cloud Service.
Check this Whitepaper today!
The details and important benefits of that critical release and how it works can be found in detail in this blog post from back in Nov-14.
The only limitation to the functionality released back then was that it was only available when accounting transactions in "Online Mode". Now we are happy to announce that the second phase of this enhancement is also available.
On 06-Feb-2015, the "Batch Mode" version of this enhancement was released via patch 20427746. This patch introduces an entirely new concurrent process: "Payables Upgrade SLA Distributions for Historical Referenced Transactions". This process should be run in tandem with the "Create Accounting" program. It can be run independently prior to running "Create Accounting", or they can be run together as a request set.
The parameters of the new program are similar to those used by the "Create Accounting" process to identify unaccounted events to process.
In Oracle Payables, a payment has a functional dependency on invoice, i.e. the payment needs to be accounted to same liability account as the invoice has been accounted for. In such a scenario, invoice is referred to as the upstream transaction and the payment as the downstream transaction.
In a business flow prior entry application, the upstream accounting is mandatory for the downstream transaction accounting to go through. The accounting journals must be created in each ledger (primary, ALC and secondary) for all upstream transactions to have the accounting to be created in all the related ledgers of primary ledger for the downstream transaction.
Similar dependencies are there for other transactions also like Invoice Cancellation, Prepayment Application, Payment Cancellation, Payment unclearing etc.
Business flow failures generally have the error:
In order to resolve this situation, users needs to identify and account all upstream transactions before accounting the downstream transactions. This was more complex for transactions that referenced one or more 11i transactions as the upstream transaction and in some cases it was mandatory to have Hot Patch applied or SLA: Upgrade Historical Subledger Transaction Accounting Program ran to cover the period related to the upstream transaction. This was required even for accounting a single downstream transaction.
With the exciting enhancement delivered via Patch 19568225, downstream transactions failing business flow for an upgraded upstream transaction can be successfully accounted using ON-LINE accounting of the downstream transaction.
With on-the-fly upgrade, a new profile option SLA: On-the-fly Upgrade of Historical Subledger Accounting Distributions is introduced which when set to Yes will cause a dedicated procedure to identify the few upstream
transactions missing XDL and populate them on the fly, prior to
accounting the downstream transaction, and this is transparent to the user.
Thus the volume of transactions which "require" upgrade is reduced from
a huge number (across multiple years and applications) to just a few
upstream transactions which are related to the current downstream
Please review R12: Important Enhancement ON-THE-FLY Upgrade of Historical SLA Distributions (Doc ID 1938253.1) for full details.
If you have any questions or comments on this new functionality please post in the dedicated Payables Community thread.
On July 2014 was published The Second Resolution of Modifications to the Mexican Fiscal Code establishing, among other regulations, that taxpayers required to keep accounting books and records must use electronic systems and accounting programs that would be able to generate the files in XML format.
The mentioned provisions refer to:
Need to meet these requirements regarding compliance and delivery of accounting information through electronic media?
To understand better the implications of this legislative update and follow-up the formal Enhancement Request raised with Oracle, please visit these documents today!
E-Business Suite Release 12: Mexico Electronic Accounting, 2014 (Doc ID 1918417.1)
R12: Mexico Electronic Accounting : Does New Functionality Exist? (Doc ID 1921779.1)
Be the first one to know when the functionality becomes available! Bookmark this Enhancement Request now!
Visit the newly released White Paper on 'Oracle Online Accruals In Purchasing' Doc ID 1666593.1. The document provides a broad overview of the Online Accrual and Online Accrual accounting process in Release 12. It also provides explanations of common terms and concepts to include
accrual, accrual accounting, types of purchase accruals in Oracle
Applications and the modules involved.
This white paper is intended to aid users in verifying common setup steps and provide usage relating to accrual methods and processes. The document takes users through a complete cycle of Online Accruals covering all relevant aspects. The scope of this document is ideal for all users, consultants and support analysts of the Oracle Procurement Application, with a basic knowledge of Oracle Application setup steps and a firm understanding of accounting principles.
Visit Doc ID 1666593.1 today to review this valuable paper!
Projects Support has a published document with a consolidated listing of mandatory code and data fixes for Project Costing. Generic Data Fix (GDF) patches are created by development to fix data issues caused by bugs/issues in the application code. The GDF patches are released for download via My Oracle Support which are then referenced in My Oracle Support documents and by support to provide data fixes for known code fix issues.
Consolidated root cause code fix and generic data fix patches will be superceded whenever any new version is created. These patches fix a number of critical code and data issues identified in the Project Costing flow.
This document contains a consolidated list of code and data fixes for Project Costing. The note lists the following details:
Visit DocID 1538822.1 today!
Subledger Accounting (SLA) is a rule-based accounting engine that centralizes accounting for Oracle E-Business Suite products in R12. Subledger Accounting is not a separate product in itself.
Together with the new ledger support, Subledger Accounting enables support of multiple accounting requirements concurrently in a single instance. Different accounting regulations can be satisfied by maintaining and applying different sets of rules to different sets of transactions, or accounting for the same transaction with multiple methods. Subledger accounting options define how journal entries are generated from subledger transactions at the subledger application level.
Note: SLA replaces the different accounting engines available in 11i e.g., the AP accounting engine, FA accounting engine, Global Accounting Engine (AX), and so forth.
This white paper that was recently updated is very comprehensive and describes the setup of the Payables Subledger Accounting feature that is available in Release 12. It includes a step by step guide on how to configure the SLA feature for business transactions.
Payables SLA allows users to personalize their accounting setup according to business needs and this updated white paper now includes 8 test cases together with setup demonstration and results.
Find out all about SLA setup and configuration by reviewing the white paper:
Subledger Accounting Setup for Oracle Payables (with examples) (Doc ID 1612433.1)
Encumbrance Accounting has always been one of those tricky areas to understand and it is often quite complex and time consuming to resolve issues that arise. Having a detailed understanding of how Encumbrance Accounting works in General Ledger, Payables and Purchasing will get you on the right track faster.
Recently a new document was created that attempts to pull together all the information that relates to Encumbrance Accounting so that you can understand everything from what it is, to how the applications are setup to use it, to using diagnostic tools and checking patch levels when something doesn't work just how you expect it to.
Please review R12: MASTER TROUBLESHOOTING GUIDE (MTG) for Encumbrance Accounting Issues in Oracle PO and AP (Doc ID 1578275.1) available on MyOracleSupport which discusses the following topics:
One of the additional resources referenced within the above document is R12 Encumbrances Accounting Bulletin (Doc ID 1583781.1). This interactive document allows you to filter the knowledge based on a topic of choice and includes Encumbrance Transactions for both Accrue on Receipt and at Period End and shows you the transactions you would see and the values of DR and CR that would be inserted into the XLA tables at the various stages.
Together these two fantastic documents should enlighten the reader and provide a detailed understanding of Encumbrance Accounting in Oracle Applications.
Are you using procurement accounting processes? Then don’t delay, be proactive and apply these necessary patches to avoid known issues.
So many known issues have been resolved by applying the collection of recommended patches in Doc ID 1594111.1. Procurement, Costing, Payables and SLA Development teams have collaborated to give you this consolidated list. Now I know you're thinking that it requires a lot of effort to apply big patches, but while a patch may contain several hundred files, the impact on your system is most likely far less. Patches contain hard prerequisites that are intended to make a patch work on a very low code baseline, so there is a link to the Patch Wizard so you can perform an impact analysis. So if you are using Procurement Accounting Flows (Encumbrance and Accruals) make sure and review the note where the steps are clear and to the point:
Don’t delay check out Doc ID 1594111.1 today!
Date: January 29, 2014 at 11:00 am ET, 9:00 am MT, 4:00 pm GMT, 9:30 pm IST
This one-hour session is recommended for technical and functional users who are familiar with the basics of Subledger Accounting (SLA) and its setup and want a better understanding of the Release 12 accounting process. We will discuss General Ledger (GL) transfer and drilldown and touch upon common errors and their resolution.
To gain a basic understanding of SLA, its setup and data model, join us on 22-Jan-14 for the Oracle Subledger Accounting (SLA) Basics: Overview, Setup & Data Model webcast or after 23-Jan-14, access the recording via the Archived 2013 Tab in Doc ID 1455839.1.
Details & Registration: Doc ID 1598862.1
Date: January 22, 2014 at 11:00 am ET, 9:00 am MT, 4:00 pm GMT, 9:30 pm IST
Get a basic overview of Subledger Accounting (SLA) and its setup. Learn about the SLA data model and how to customize the Application Accounting Definition. This one-hour session is recommended for technical and functional users looking for an overview of SLA setup and customization of SLA Rules. The session is also helpful if you have recently (or plan to) upgraded to Release 12 and want a basic understanding of the accounting process using SLA.
For a closer look at the SLA accounting flow, transfer and drilldown, join us on 29-Jan-14 for the Oracle Subledger Accounting (SLA): Accounting Flow, Transfer & Drilldown webcast.
Details & Registration: Doc ID 1598868.1
Date: October 10, 2013 at 11 am ET, 10 am CT, 9 am MT, 8 am PT
Curious about Oracle Financials Accounting Hub (FAH)? Join us live to discover the fundamentals and ask questions. This one-hour session is recommended for technical and functional users who would like to understand the basis of Oracle Financials Accounting Hub (FAH).
For more details and how to register see Doc ID 1577621.1
Date: September 4, 2013 at 11 am ET, 10 am CT, 9 am MT, 8 am PT
Learn how Subledger Accounting(SLA) allows you to select accounting combinations from a variety of sources. Get an overview of the components of SLA and how they can be used to influence the accounting created by the sub-ledgers. This one-hour session is recommended for technical and functional users of Receivables, Payables, Fixed Assets and the other subledgers who would like more information on using SLA to override accounting created by AutoAccounting in Release 12. We will discuss Journal Line Types, Account Derivation Rules, Mapping Sets, Journal Descriptions and the use of Descriptive Flexfields. Illustrative examples showing account replacement will also be provided.
For more details and how to register see Doc ID 1564394.1
The Create Detailed Distributions check box in the Receivables system options form was created as part of the "Merge Distributions Enhancement" (Bug: 7559194: LINE LEVEL DISTRIBUTIONS NOT NEEDED FOR HEADER LEVEL CASH APPLICATION/ADJUSTMENT). Distributions were getting created at the level of granularity of an invoice line. This would result in a large number of distributions/meta data being passed to the Sub ledger Accounting Module.
When the checkbox is checked, Receivables will create detailed invoice line level distributions. These detailed distributions allow the system to create line level applications for receipts and adjustments.
You should CHECK this checkbox if any of the conditions below are true:
1. If the Primary or Secondary ledgers associated with the operating unit is using one of the following subledger accounting representations:
2. If you want to apply receipts or adjustments to invoice lines using Line level Cash Application feature or Line Level Adjustment feature.
3. If you want to derive account code fully or partially from the invoice lines when accounting for adjustments or receipt applications.
Keep in mind that checking this box could cause performance issues. There will be a larger volume of distribution records, which could potentially cause performance issues during the Submit Accounting or Create Accounting process for Receipt Applications. There are two patches that will aid in performance issues (Patch 16198666 and Patch 16060007) See Doc ID 1534178.1 and Doc ID 1481222.1 for more details in preventing any performance related issues.
When the checkbox is UNCHECKED, Oracle Receivables will create summarized distributions. The receivable distributions for adjustments and applications are not maintained at the invoice line level, instead a summarized receivable distribution is created at the invoice header level. Adjustments and receipt applications are not pro-rated across the invoice lines. This is same way the receivable distributions are created in Release 11i.
Following is the impact of having the checkbox UNCHECKED:
For an explanation on the validation that takes place when checking and unchecking the box see Doc ID 1081657.1.
Welcome to the EBS Support Blog where Oracle insiders share news and information about EBS products including new releases, tips and tricks, troubleshooting guides, upcoming webcasts and links to EBS Communities.