How to Create an ESS Job for a BI Report in Oracle Fusion

How to Create an ESS Job for a BI Report in Oracle Fusion

If you are working with Oracle Fusion Applications, you might often need to schedule or automate BI Publisher reports. This is done by creating an ESS (Enterprise Scheduler Service) job for the BI report. In this blog, we will walk through the step-by-step process of creating an ESS job for a BI report in Fusion with best practices.

What is ESS in Oracle Fusion?

ESS (Enterprise Scheduler Service) is the job scheduling framework in Oracle Fusion. It allows you to run, schedule, and monitor background processes like:

• BI Reports

• Data loads

• Batch jobs

• Integrations

Using ESS, you can automate BI Publisher report execution and distribute outputs in formats like Excel, PDF, or CSV.

Prerequisites

Before creating the ESS job, make sure you have:

• Access to BI Publisher (Reports & Analytics).

• A saved BI Report in a custom or shared folder.

• Role with BI Administrator / ESS Administrator privileges.

Steps to Create an ESS Job for a BI Report

1. Create the BI Report

1. Login to Oracle Fusion → Tools → Reports and Analytics.

2. Create or open the BI Publisher report you want to schedule.

3. Save the report in a custom folder (not seeded folders).

2. Note the Report Path

• Go to Catalog.

• Right-click the report → Click Properties.

• Copy the Report Path (e.g., Shared Folder/Custom/Report Name.Xdo).

3. Create the ESS Job Definition

1. Navigate: Setup and Maintenance → Search: Manage Enterprise Scheduler Job Definitions and Job Sets.

2. Click Create New Job Definition.

3. Fill the details:

• Name: Report Name

• Display Name: Report Display Name

• Job Type: BIPJobType (for BI Reports)

• Parameter List: Enter if the report has parameters.

• Report Path: Paste the BI Report path copied earlier.

• Output Format: PDF / Excel / CSV as needed.

4. Save and Deploy

• Click Save and Close.

• Your ESS Job is now available in the Fusion scheduler.

5. Run the ESS Job

1. Navigate: Tools → Scheduled Processes.

2. Click Schedule New Process.

3. Search by the Display Name you created.

4. Provide input parameters (if any).

5. Submit the process.

6. Monitor under Scheduled Processes page to check status and download output.

Best Practices 

• Always save BI reports in Custom Folder, not Oracle’s seeded folders.

• Use clear job names for easy identification.

• For recurring jobs, set Schedule Options (daily, weekly, monthly).

• Test with small data before scheduling large reports.

Why use ESS for BI Reports?

• Automates repetitive reporting tasks.

• Reduces manual errors.

• Ensures timely delivery of business reports.

• Supports multiple output formats for different stakeholders.

Conclusion

Creating an ESS job for a BI report in Oracle Fusion makes reporting automated, reliable, and efficient. Whether you want daily sales data, monthly payroll, or inventory reports, ESS ensures your reports run on time without manual intervention.

By following the steps above, you can easily integrate BI Publisher reports into Fusion’s scheduler and streamline business reporting.

 

How Access Works in Oracle Cloud ERP Modules

Introduction : How Access Works in Oracle Cloud ERP

Oracle Cloud ERP is designed with robust access and security controls to ensure that users can only interact with the data and tasks that are relevant to their role and responsibilities. Access in Oracle ERP is determined by a combination of role-based access control (RBAC), data security policies, and specific module-level configurations. This blog will explore how access works across various Oracle modules like GL, AP, AR, and FA.

Role-Based Access Control (RBAC) in Oracle

Oracle Cloud applications use RBAC ( role based access control) to manage access:

• Job Roles determine what a user can do (e.g., Accountant, AP Specialist).

• Data Roles determine what data a user can access.

• Abstract Roles (like Employee or Contingent Worker) grant access to common functions.

Each module adds another layer of control via functional and data security policies.

Access in General Ledger (GL) — Data Access Sets

In GL, access to ledgers, balancing segment values, or management segment values is controlled using Data Access Sets.

Key Components:

• Ledger Access: You can grant access to one or more ledgers.

• Balancing Segment Access: Access can be limited by segment values (e.g., Company Codes).

• Read or Write Access: Permissions can be restricted to view-only or full processing rights.

Use Case:

If a user should only post journals for a specific company, you would restrict their access using a Data Access Set with the relevant balancing segment value.

Access in Fixed Assets (FA) — Asset Books

In Oracle Assets, user access is managed through Asset Books.

Key Components:

• Users are assigned access to specific asset books.

• All transactions (additions, retirements, transfers) are limited to the books they have access to.

• Segregation of access across legal entities or business units.

Use Case:

A user working on U.S. books should not have access to India-specific books. The role should only grant them access to U.S. books.

Access in Payables (AP) and Receivables (AR) — Business Units (BUs)

AP and AR access is largely determined by access to Business Units.

Key Components:

• Users are assigned roles with access to specific BUs.

• Additional segregation can be done through document security profiles (e.g., invoice or payment business functions).

Use Case:

If an AP Specialist should only process payments for one BU, assign their role to only that BU.

Other Module-Specific Access Examples

• Procurement: Access based on Procurement BU and Requisition BU.

• Projects: Controlled via project and organization hierarchy.

• Inventory: Access via Inventory Organizations.

Security Console for Access Management

Oracle Cloud's Security Console allows Admins to:

• Create and manage roles.

• Assign data roles and job roles to users.

• View role hierarchies and permissions.

Best Practices for Access Management

• Follow least privilege principle.

• Regularly review role assignments.

• Use risk management cloud for SoD (Segregation of Duties) conflict detection.

• Document and audit changes via Security Console logs.

Conclusion

Understanding how access works in Oracle Cloud ERP modules helps organizations ensure compliance, improve user efficiency, and maintain data integrity. From Data Access Sets in GL to Asset Books in FA and Business Units in AP/AR, Oracle provides granular and secure access management options.

 How to Change Asset Categories in Bulk in Oracle Cloud ERP

What is “Mass Change Category” in Oracle Fixed Assets?

The Mass Change Category feature enables users to update the category of multiple capitalized assets at once using a spreadsheet interface, with changes applied in-place, maintaining asset number and history.

Managing thousands of fixed assets in Oracle Cloud ERP can be time-consuming, especially when you need to update asset categories in bulk. Thankfully, Oracle offers a streamlined way to make mass asset category changes using the Mass Update feature or FBDI templates.

In this blog, we’ll walk you through two effective methods to update asset categories across multiple assets without manual entry — saving you time, effort, and reducing errors.

Steps to Change Asset Categories in Bulk in Oracle Cloud ERP

Mass Change Asset Category Functionalityin oracle fusion cloud

Purpose: Ability to do a Mass Change Category for multiple assets based on the Asset Selection Criteria

Procedure:

Navigate to Fixed Assets > Assets > Adjust Assets

Click Mass Tab

Select Asset Book and Transaction Type = Category Change.  Click Next

 

 

Add required information in the header and Transaction Details area

Add filters in the Asset Selection Criteria

 

Add Category Details ‘Category Filter’ and click OK

 

Click Submit

Click Search to refresh the grid until the number of Transactions are more than 0 and the Posting Status is ‘In Progress.

 

 

 Click Prepare button to open in Excel.  Log into Fusion.

      Review information in spreadsheet and change Posting Status to ‘Post’ and fill in     the Required fields.

 

Best Practices How To Change Asset Categories in Bulk in Oracle Cloud ERP

• Take a backup report of affected assets before changes.

• Always test a few records in lower environments.

• Avoid changes mid-month if depreciation is already calculated.

• Validate if new category has different accounts or depreciation rules.

Conclusion

The Mass Change Category feature in Oracle Cloud ERP is a game-changer for finance and asset management teams. It simplifies the reclassification process, ensures accuracy, and reduces audit risks—without the hassle of retire-readd workarounds.

If you're frequently performing asset reclassifications, this feature is a must-use!