Browser version scriptSkip Headers

Oracle® Fusion Applications Financials Implementation Guide
11g Release 7 (11.1.7)
Part Number E20375-08
Go to Documentation Home
Home
Go to contents  page
Contents
Book<br />List
Book
List
Go to Feedback page
Contact
Us

Go to previous page
Previous
Go to previous page
Next
PDF

38 Define Budget Configuration

This chapter contains the following:

Budget Uploads: Overview

Importing Budget Data from a Flat File: Explained

Loading Data to the Budget Interface Table: Explained

Importing Budget Data from a Spreadsheet: Explained

Budget Correction with Oracle ADF Desktop Integrator: Explained

Creating Budget Data Security: Worked Example

Oracle Hyperion Planning: Overview

Integration with Hyperion Planning: Overview

Budget Uploads: Overview

In Oracle Fusion General Ledger, you load budget data to perform variance reporting.

If you use a third party budgeting system or if you don't use a budgeting system, there are three ways to load budgets in the to the balances cube in the General Ledger.

The figure above is the process of
loading the budget using an ADFdi Spreadsheet and ending with reporting
and analysis.

Note

Create reports in Smart View or Financial Reporting to verify that the budget data was loaded correctly.

Importing Budget Data from a Flat File: Explained

Use the Upload Budgets processes to integrate budget information from other budgeting application such as Oracle Hyperion Planning, Fusion Edition. You can load your budget amounts to the General Ledger balances cube by populating the GL_BUDGET_INTERFACE table and running the Validate and Upload Budgets process. You can load budgets for multiple periods and for multiple ledgers with the same chart of accounts in a single load process. Note that the budget data is not loaded to the GL_BALANCES table and only loaded to the balances cube for variance reporting purposes.

Note

You can load data to interface tables using predefined templates and the Load Interface File for Import scheduled process, which are both part of the External Data Integration Services for Oracle Cloud feature. For other implementations, optionally use this feature only if you have SFTP configured for it.

Assigning Values for Columns in the GL_BUDGET_INTERFACE Table

You must enter values in all the columns of the interface table that require values, which includes all of the not null columns, in order for the budget import to be successful.

Enter values in the following required columns of the interface table:


Column Name

Values

RUN_NAME

Enter a name to identify the budget data set being imported.

STATUS

Enter the value NEW to indicate that you are bringing new budget data.

LEDGER_ID

Enter the appropriate ledger ID value for the budget amount. You can view the ledger ID for your ledgers in the Manage Primary Ledgers page. The ledger ID column is hidden by default, but you can display it from the View > Columns menu. If you enter multiple ledgers for the same run name, all of the ledgers need to share the same chart of accounts.

BUDGET_NAME

Enter the appropriate budget name value for the budget line. You define your budget names in the Accounting Scenario value set.

PERIOD_NAME

Enter the period name that you are loading the budget data for. Note that you can load budget data regardless of the period status.

CURRENCY_CODE

Enter the currency code for your budget.

SEGMENT1 to SEGMENT30

Enter valid enabled account value for each segment in your chart of accounts.

BUDGET_AMOUNT

Enter the amount in the ledger currency for account types, expense and assets.

OBJECT_VERSION_NUMBER

For Oracle Cloud implementations, leave this field blank as the application will automatically populate this when you load the data from the secure FTP server to the interface table. For other implementations, you can default the column with a value of 1.

The following columns should be left as null as the budget import process uses these columns for internal processing or does not use them in the current release.

Loading Data to the Budget Interface Table: Explained

Load the budget amounts to the interface table by following the steps below.

  1. Export budget data from your budgeting application to a comma separated values (csv) file. You can use the sample csv file or xls file that is provided in Oracle Enterprise Repository (OER) for Oracle Fusion Applications as a reference.

  2. Upload the comma separated values (csv) file to the secure FTP server.

  3. Select the parameters:

  4. After the data is loaded to the interface table, you can run the Validate and Load Budgets process to load the budget amounts to the General Ledger balances cube.

  5. Review the logs for validation errors. If there are validation errors, use an ADF Desktop Integrator (ADFdi) correction worksheet to download and correct the rows with errors. Then resubmit the data using ADFdi.

The figure shows the process to load
budget data using a flat file. The file is loaded to the GL Budget
Interface, validated, and uploaded to the GL Balances Cube.

Importing Budget Data from a Spreadsheet: Explained

Use Oracle Application Development Framework (ADF) Desktop Integrator to enter, load, and correct budget data. This functionality uses a new interface table called the GL_BUDGET_INTERFACE and requires the duty role, Budget Entry Duty.

Budget Import

Budget Import Oracle ADF Desktop Integrator import functionality is similar to the journal import sheet in Oracle Fusion General Ledger. You may use this tool to create and upload budget data. From the General Accounting Dashboard page, download the import worksheet.

The budget import uses the Accounting Scenario value set for the budget being loaded. The Run Name is used as an identifier for the imported data set. The Oracle ADF Desktop Integrator budget import functionality:

The figure shows the process to enter
and upload budget data into the GL Balances Cube using an ADFdi spreadsheet.
After the data is loaded into the spreadsheet, upload the spreadsheet
to the GL Budget Interface, validate, and run the Upload Budgets process
to load the data into the GL Balances Cube. Log files are provided
on both the validate and the upload processes to facilitate error
correction.

Note

The ADF Desktop Integrator spreadsheet contains a Record Status column that shows if the rows upload successfully or with errors. Corrections are done in the same spreadsheet as the entered data.

Budget Correction with Oracle ADF Desktop Integrator: Explained

Oracle ADF Desktop Integrator correction functionality is similar to the journal correction sheet in Oracle Fusion General Ledger. You use this tool to correct the flat file import errors.

The correction spreadsheet functionality:

Correcting Data

To use the correction spreadsheet functionality perform the following steps:

  1. From the General Accounting Dashboard page, you set the data access set and download the correction worksheet.

  2. After the correction worksheet is downloaded, you query for the rows in error. Pick the run name for which there are validation errors and click on the Search button. This populates the budget rows in error.

  3. Correct the rows in error or mark for deletion and submit the journal correction spreadsheet. Any errors will be reported on the worksheet.

  4. If the row status indicates an error, double click on it to see the error details and take necessary action. You can use the list of values to quickly correct data that is in error.

Creating Budget Data Security: Worked Example

You are in charge of your company's data security and must secure your budget data. You can secure budget data by using segment value security for the value set, Accounting Scenario. To meet this need for security, you create two data security policies.

The following budget version values from the accounting scenario value set must be secure:

The following data security must be configured:

In this example, launch the task Define Budget Scenarios to open the value set page from the Setup and Maintenance work area.

  1. Click the Edit icon.

  2. Check Security Enabled.

  3. Enter the Data Security Resource name, if not populated: ACCOUNTING_SCENARIO.

  4. Click on Edit Data Security to set up the data policies.

Setting up Policy 1: Full Access to All Budget Versions

  1. Click on the Policy tab.
  2. Click on Create.
  3. On the General Information tab, enter Name, Start and End Dates, and Module equal to General Ledger.
  4. On the Role tab, add one or more roles. In this case add the Chief Finance Controller for Vision Foods USA.
  5. On the Rule tab, select Row Set equal to All Values.
  6. Save and Submit the policy.

Setting up Policy 2: Access to One or More Budget Versions

  1. Click on the Condition tab to create a filter for the multiple values.
  2. Set Match to Any to start OR Boolean operator. If you set Match to All, AND Boolean operator is used.
  3. Enter two rows with Column Name: Values. Operator: Equal to, and Value: Original Budget on first line and Revised Budget on the second line. Note that you can also use the tree operators.
  4. Click on the Policy tab.
  5. Click on Create.
  6. On the General Information tab, enter Name, Start and End Dates, and Module equal to General Ledger.
  7. On the Role tab, add one or more roles. In this case add the General Accounting Manager for Vision Foods USA.
  8. On the Rule tab, select Row Set equal to Multiple Values.
  9. Select the Condition Filter
  10. Save and Submit the policy.

    Note

    You can also set up single access by using a policy with Row Set equal to Single value. You must use SQL to get the value ID and enter the value ID.

    Note

    The value set, Accounting Scenario, is not typically associated to a chart of accounts segment. To publish the budget data security policies to the cube, run the job, Publish Chart of Accounts Dimension Members and Hierarchies. For the run parameters, select any value set assigned to one of the chart of accounts segments of your ledger. For the second parameter, Publish Detail Values Only, select Yes. The process runs faster if you select to publish only the detail values.

Oracle Hyperion Planning: Overview

Oracle Hyperion Planning, Fusion Edition is a comprehensive, web based, budgeting and planning application. Planning can be licensed and integrated with the Oracle Fusion Accounting Hub to provide expanded budgeting and planning functionality.

Oracle Hyperion Planning, Fusion Edition:

The following table provides installation and configuration activities and documentation references.


Activities

Documentation

Installation of Planning

Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide for Oracle Hyperion Enterprise Performance Management

Configuration of Planning

Oracle Hyperion Planning, Fusion Edition Administrator's Guide for Oracle Hyperion Planning

Integration of Planning

Oracle Hyperion Financial Data Quality Management ERP Integration Adapter for Oracle Applications Administrator's Guide

Integration with Hyperion Planning: Overview

For Oracle Cloud implementations, integrate with on-premise Oracle Hyperion Planning for advanced budgeting by loading actual balances from Oracle Fusion Accounting Hub to Oracle Hyperion Planning so you can use the actual data in the budgeting process. You can also load budget data from Oracle Hyperion Planning to Oracle Fusion Accounting Hub through the Budget Interface to perform budget variance reporting within Oracle Fusion Accounting Hub.

For other implementations, Oracle Fusion Applications provides integration between Oracle Fusion Accounting Hub and Oracle Hyperion Planning through Oracle Financial Data Quality Management ERP Integrator adapter. To complete the post-installation setup for the ERP Integrator adapter, see Oracle Hyperion Financial Data Quality Management ERP Integrator Adapter for Oracle Applications Administrator's Guide.