Oracle EBS & MS Edge

Oracle E-Business Suite Releases 12.2 and 12.1 have two interfaces: a web-based (OA Framework/HTML) model for modules such as iProcurement and iStore, and Oracle Forms/Java based model for modules such as Oracle Financials.

Edge can be used to access the web-based HTML products in Oracle EBS that use OA Framework (OAF).

However, MS Edge Chromium browser does not support NPAPI, so is not certified for running Java content using the JRE Plug-in.

New laptops are coming with both IE11 and Microsoft Edge Chromium browsers. Users don’t have to download IE11 separately (for now). MS Edge Chromium will be default browser and you can change that and make IE11 as the default browser. 

Chrome too has stopped support Java plug-ins and Firefox needs an extensive setup which may not be practical. So best bet is still IE11 (for now).

If you want your current R12 Java based application to work on MS Edge, you need to implement Java Web Start (JWS) for your application so that JRE plug-in are not required and it works with Edge.

Sub Ledger Accounting

Oracle Subledger Accounting (SLA) is a rule-based accounting engine that centralizes journal entry creation across the E-Business Suite. Acting as an intermediate step between a subledger application (such as Oracle Cash Management or Oracle Accounts Payable), and the Oracle General Ledger, Oracle Subledger Accounting creates journal entries for subledger transactions and transfers them to Oracle General Ledger.

Cash Management

Oracle Cash Management helps you manage your enterprise liquidity and cash positions.

• Manage and control your cash cycle
• Upload and reconcile bank statements
• Forecast your cash needs
• Transfer funds between bank accounts
• Manage Bank, Bank Branch and Bank Account information

Per new Bank Account Model, Banks and Bank Branches are created as Trading Community Architecture (TCA) parties (as opposed to Payables owning them in previous releases). Bank Accounts reside within Cash Management application and we can define in which applications this bank account can be used.

Reconciliation Flow:

Step 1. Receive Bank Statement --&gt Manually or automatically (via Bank Statement Open Interface). Each bank statement can refer to one or more payments, receipts, open interface, misc transactions and consists of one header and multiple bank statement lines. Bank statement line status can be - Reconciled, Unreconciled, Error, External.

Step 2. Load and Verify Bank Statement --> 

Step 3. Perform Reconciliation --> 

Step 4. Review --> 

Step 5. Create JEs and Post to GL

Cash Management and External Systems:

You can include cash flows from external systems using the External Cashflow Open Interface.

Reconciliation Open Interface can find external transactions available for clearing and reconciliation. 

Open interface view --> CE_999_Interface_V

Oracle E-Business Suite (EBS) Upgrades

Custom code can be expensive to develop but even more expensive to maintain.

Minimize EBS custom code

Try to eliminate as much custom code as possible. Research the more recent releases to see if new functionality replaces the homegrown code.

Set up queries or monitor the concurrent requests to see if reports and even interfaces are being used.

Global companies may see that the improved localization functionality in R12 can allow them to eliminate some custom code as well.

If you have taken copies of standard Oracle reports and modified them, the best practice is to take a new copy of that object from the new release and reintroduce the modifications. Don't spend inordinate amounts of time trying to get an old 11i report to work in an R12 environment.

The same recommendation holds true for workflow items.

While many standard open interfaces and APIs are typically not heavily changed during the migration to EBS R12, you may rename interfaces, and add new or additional parameters. 

Event alerts are typically disabled during the upgrade, so you may need to re-enable them prior to testing.

Customizations to Oracle Forms can be tricky, as they are probably one of the most invasive customizations besides database triggers. If your business processes require modifications to the forms, replace them with personalizations as much as possible. If you do have customized forms, look to see if those forms will exist in the new, plain-vanilla version. Some EBS modules have quite a few brand-new forms.

You should be able to replace some old forms with new OA Framework-based forms. 

Finally, consider the third-party products that you may have previously licensed. You may be spending extra money for functionality that has now been introduced into the applications. Examples include third-party form and label software, check printing software, invoice printing and delivery solutions, and more.