Oracle Financial Applications

Integration to Fusion Accouning Hub from your EBS or PeopleSoft Ledger (Co-Existence Strategy)

on Tuesday, 02 February 2016. Posted in Solution & Business Architecture, Blog, Oracle Financial Applications

Integration to Fusion Accouning Hub from your EBS or PeopleSoft Ledger (Co-Existence Strategy)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Co-existence approach implies that a customer is not upgrading but they will keep adding Fusion Application solutions (see diagram about Fusion Topology). In that case customers will always look for opportunities that Fusion brings that address their critical needs while minimizing the risk to their current Applications investment. This is the focus of the co-existence adoption model.

A question that has been coming often lately is about integrating multiple non Oracle financial systems to fusion accounting hub. Below is a visual architecture example How to implement Fusion Accounting Hub by utilizing your current as is systems - multiple sources with different formats and loading it with SQL Loader. into FAH. The main advantage of this approach is that you can continue using your E-Business Suite or PeopleSoft applications for your procurement, supply chain, payables, receivables without disruptions.

 

Below is an example of an integration with multiple inputs:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Oracle Business Flow: Project Expenditure to Revenue Recognition

on Friday, 17 October 2014. Posted in Oracle Project Suite, Blog, Oracle Financial Applications

Oracle Business Flow: Project Expenditure to Revenue Recognition

 

 email15-oct

In this article I share the Oracle business flow: Project expenditure to revenue recognition business process with the associated enterprise roles. The Oracle Business Flows— Enable you to relate your business requirements to the E-Business Suite functionality. I recommend these flow models to assist you with the project scope and increase end-user  awareness of the project. It also establishes a common understanding of the integrations required to deliver the project.

Be aware not all consultants have this information, E-Business Suite accelerators are available from Oracle Consulting and other approved partner channels.

Slide1

Slide2

Oracle AR Customer Overview

on Tuesday, 01 January 2013. Posted in Blog, Oracle Financial Applications

 
The attached file explains the basics and intricacies of Oracle AR.

Oracle AP important concepts

on Tuesday, 01 January 2013. Posted in Blog, Oracle Financial Applications

 

The attached file explains the different concepts of Oracle Payables, the module helps sustain financial discipline,  regulatory compliance and optimize your business process.

 Oracle AP Download

 

Steps to maintain Tax books in FA

on Tuesday, 01 January 2013. Posted in Business Analysis, Blog, Oracle Financial Applications

 

1.Companies can Create as many Tax Books as are needed:
 
1) Associate the new Tax Book to a corporate book.
Choose a depreciation calendar.
Corporate and Tax Books can have different calendars.
2.2) Set up asset categories for the new Tax Book:
Define default depreciation rules for each category.
Categories in corporate and Tax Books have 1:1 mapping.
3.3) Initially add assets to new Tax Book using Initial Mass Copy.
4.4) Perform asset additions and maintenance in the corporate book.
5) Periodically update Tax Book with new assets and transactions from the corporate book. 
6.6) Run depreciation for the Tax Book.

Starting point for an upgrade to Oracle 12 Financials

on Tuesday, 01 January 2013. Posted in Oracle Financial Applications

If you are planning an Oracle upgrade, a good starting point is the Oracle -Business Suite Upgrade Plan on Metalink's knowledge base.There is a lot of information it is important to filter your information and create a plan that is specific to your requirements. No 2 upgrades are the same.

 

AR Closing Process

on Tuesday, 01 January 2013. Posted in Blog, Oracle Financial Applications

 

Some of these steps are optional, but within most organizations the process should be as follows:
 
·         Complete All Transactions for the Period Being Closed
·         Reconcile Transaction Activity for the Period
·         Reconcile Outstanding Customer Balances
 ·         Review the Unapplied Receipts Register
·         Reconcile receipts.
 ·         Reconcile Receipts to Bank Statement Activity for the Period
 ·         Post to the General Ledger
·         Reconcile the General Ledger Transfer Process
·         Reconcile the Journal Import Process
·         Print Invoices
·         Print Statements (Optional)
·         Print Dunning Letters (Optional)
·         Close the Current Oracle Receivables Period
·         Reconcile Posted Journal Entries
·         Review Items that are not posted Report
·         Open the Next Oracle Receivables Period
·         Run Reports for Tax Reporting Purposes (Optional)
·        Run Archive and Purge programs (Optional)
 

Asset Workbench Process Overview

on Tuesday, 01 January 2013. Posted in Blog, Oracle Financial Applications

 

 
Use the Assets Workbench windows to add new assets to the system, and to perform transactions, such as retirements, adjustments, source line adjustments, and transfers. The workbench can also be used to review asset detail, financial, and assignment information.
asset

Set Up Steps for version 12.1 Complex Purchase Orders and Retainage

on Tuesday, 01 January 2013. Posted in Blog, Oracle Financial Applications

There are two setups steps that are required if the complex purchase orders and retainage feature will be used.

 

1.       Create a document style in Oracle Purchasing.
Responsibility: Purchasing
Navigation: / Setup / Purchasing / Document Styles  à Create
Define whether the complex PO can include advances, retainage, and progress payments.

complexpo

         

Pay Items can be Milestone, Rate, or Lump Sum.  For Fixed Price Services, rate based pay items will be considered quantity based matches and milestone and lumpsum will be considered amount-based matches when evaluating billed, planned, and tolerances.

 

Milestone pay items are based on a milestone in the contract or event that needs to be fully complete before the contractor can claim the associated payment.

 

Rate pay items are based on a ‘Rate’ of work completion. Payments for these can be claimed as units of work are completed.

 

Lump Sum pay items, as the name suggests, are based on a ‘Lump Sum’ amount allocated to a portion of work. Progress payments can be released for these pay items based on the level of completion.  

 

                                

If the “Treat Progress Payments as Contract Financing” option is selected, then pay items entered follow the Financing Complex Work case.  If the option is not selected, then pay items follow the Actual Complex Work case.

 

Note: The profile option POR: Amount Based Services Line Type specifies how services are to be quantified and ordered on the transaction document. In order to use the Complex Services functionality, the value for this profile option should be set to ‘Fixed Price Services’, which means that services will be ordered as an amount.  This setup is found performed in the System Administrator responsibility under System Profiles.

 

 

 

 

2.       Create a retainage account in Financials Options setup.

Responsibility: Payables
Navigation: / Setup / Options / Financials Options
Enter the retainage account to use during accounting.

complexpo1

 

Note: Historically the prepayment account entered here would default to the supplier site and be used when creating prepayments for the supplier.  However, the new Advances and Contract Financing prepayments introduced with this solution will use the distribution account on the Purchase Order and not the supplier site.

Be patient and give yourself time before implementing MOAC in Release 12.1

on Tuesday, 01 January 2013. Posted in Blog, Oracle Financial Applications

 

Multi-Org Access Control enables companies that have implemented a shared services operating model to efficiently process business transactions by allowing them to access, process, and report on data for an unlimited number of operating units within a single applications responsibility. That was a major limitation in R11.

 

MOAC will automatically increase the productivity of shared service centers, as users and processes no longer have to switch applications responsibilities when processing transactions for multiple operating units at a time. The data security and access privileges are still maintained using security profiles that now support a list of operating units.

 

The user level preferences must be well thought out and can optionally be set to access a subset of operating units.

 Profile option ‘MO: Security Profile’:Profile option ‘MO: Security Profile’ controls what security profile is active for a session 

moac

 

This is how MOAC works in Release 12 when the value of “MO: Security Profile” is set. The important point to note here is that the profile “MO: Operating Unit” is ignored when the profile “MO: Security Profile” is set. This enables us to use both R12 MOAC behavior and 11i behavior simultaneously in R 12. You can also choose to completely use one of them. Take your time and think it through when designing your solution.

 

Deploying Oracle Report Manager R12.1

on Tuesday, 01 January 2013. Posted in Blog, Oracle Financial Applications

Oracle Report Manager is the online report distribution system that provides a secure and centralized location to produce and manage point-in-time reports. Reports can be published and presented to certain responsibilities without additional security or a variety of security models can be applied, allowing only authorized users to view entire reports or parts of reports. In addition, we can use specific templates to integrate reports displayed by Report Manager using the organization's individual style. The key benefit of Report Manager in R 12.1 is that the report can be directly viewed and opened in Excel (as against earlier releases wherein it can be viewed only in PDF or html).  

The approach to deploy should begin by looking at the Menu Functions that are available. Oracle does not seed specific responsibility for being used to run Report Manager, as the reports could be called and published from any of the base application’s responsibility. Hence, the suggested approach of Oracle is to add these functions to the appropriate responsibility. 

 1. Financial Report Template Editor

2. Financial Report Submission

3. Report Set Publish

4. Report Set Publishing Options

5. Ad Hoc FSG Submission

6. Security Workbench

7. Repository Management

8. Upload File

9. Standard Report Submission

10. Request Set Publishing Options

11. Variable Report Submission

 The following table lists, one of the suggested approach to associate the above Functions to specific responsibility: 

Responsibility Menu Function to be added to it from above
General Ledger Financial Report Template Editor
  Financial Report Submission
  Report Set Publish
 

Report Set Publishing Options

 

Ad Hoc FSG Submission

  FSG Drilldown: Launch Page *
  FSG Drilldown: Select Content Set Rows *
  FSG Drilldown: Effective Range Selection Page *
  FSG Drilldown: Balance Inquiry Page *
  Account Analysis and Drilldown *
   

Report Manager Administration

Repository Management

 

Upload File

 

Financial Report Template Editor

   

General Operations

Standard Report Submission

 

Request Set Publishing Options

   
Financial Assets Standard Report Submission
 

Variable Report Submission

When designing a controls framework for Oracle EBS R12,consider the following controls activities

on Tuesday, 01 January 2013. Posted in Blog, Oracle Financial Applications

 

When designing a controls framework for an Oracle EBS R12 , consider the following controls activities:

- Oracle provides Edits/Validation controls throughout the modules to ensure the accuracy and completeness when entering transactions. For example with an AR invoice, critical fields are subject to edits and validation controls to validate the accuracy and completeness of invoice entries. Certain fields are required while entering or modifying invoice information (such as invoice number, price, and distributions) to validate that all the appropriate information is entered.

- Oracle also uses features such as List of Values, which present a list of data values that the user can select from versus free form typing in a field.

- Flexfield security can also be used to control where a user enters data. For instance, flexfield security can be enabled for users to only access certain GL accounts and therefore only transact to certain accounts. In addition, flexfield value security can be used in order to prevent a user from selecting incorrect data, thereby limiting what values a user can enter in flexfield pop–up windows and report parameters.

- Cross–validation rules control the combinations of values a user can create when entering values for key flexfields. This means a user can implement cross–validation rules to prevent the creation of flexfield combinations that should never exist. For example, if a company manufacturers both cars and computers, a user should never have the following combination in a flexfield: CPU Headlights.

- Security rules can also be assigned to responsibilities in order to restrict a user from entering data in a particular organization unit

- Oracle workflow is a common control mechanism that can be set up in modules to manage business processes according to rules that a user defines. Oracle workflow is most commonly used to route a user's transactions to the appropriate supervisor or manager prior to posting it in the system. Examples include:

- General Ledger for journal approvals

- Purchasing for purchase requisition or order approvals

- Expense for the approvals of employee's expenses

- Another common control mechanism in Oracle is restricting access by creating custom responsibilities that exclude either conflicting functions or removing sensitive access from a user,  such as when creating suppliers.

- Automatic Numbering or Document Sequencing can be used for invoice numbers, receipts, journals, customers, suppliers, and fixed assets, in order to account for completeness when transacting. In addition, Oracle, by default, does not allow duplicate invoice numbers, receipt numbers, journals, and customers to be processed.

· In addition to the overall controls points listed above, each individual module in Oracle contains a number of configurations (configurable controls) that can be set in order to provide a control. For example, in Accounts Payables, a configurable control is Price Tolerance. Setting a price tolerance to 5% will place an invoice on hold if the invoice price was 5% over the supplier’s purchase order price.

 

High Level Implementation Plan for Hyperion Products

on Tuesday, 01 January 2013. Posted in Blog, Oracle Financial Applications

 

As I have received multiple requests lately on Hyperion Planning, Hyperion FDM -Financial Data management and HFM - Hyperion Financial Management. I decided to provide you with the high level steps for a typical example of an HFM implementation along with estimated timeframes for each step.  Note that the Hyperion Planning and FDM follows a similar plan and these steps are based on average implementation times (Should differ by company). 

 

One important point that the company must dedicate a minimum of one resource to the project to assist with the application and rules definitions, data tie-out, report building and other tasks related to the implementation. 

 

 

-          Design Meeting and BluePrint – 10-20 days

o   This stage is designed to gather all of Companies requirements.  This will include an analysis of the current and future reporting needs as well as getting an understanding of the underlying source systems and their accounting segments. 

o   An analysis of the data load requirements as they relate to FDM is performed in the blueprint phase.

 

-          Prototyping – 20-30 days

o   During this stage a prototype of the application will be built to demonstrate the critical features of the application.  This will ensure that the requirements were properly understood, as well as solidify the design concepts to the Company personnel.

 

 

-          System Build – 60  - 90days

o   During this stage, the full application will be built and loaded with data.  The metadata will be built based on the current EBS structure.  Rules are also built to accommodate the calculations that will be required within the system.  These rules will include elements such as currency conversion, special consolidation rules (if required), cash flow calculations, validation rules, etc.

o   Historical data will also be loaded and tied out during this stage which will allow us to test the system logic.

o   The timing of this stage is quite variable, as it will depend on the availability of the company resources.  There is also a high variability based on the cleanliness of the source data.  The amount of time related to data tie out should not be underestimated.

 

-          System Testing 10-15 days

o   This stage will include a full system test with users.

-          Training 5-10 days

-          Rollout Support 5-10 days

A typical HFM implementation varies between 4- 9 months depending on the complexities and number of RICE(Reports, Interfaces and Extension).

Copyright 2015 Appsconsultant.com. All rights reserved.