My Oracle Support Banner

Fusion Absence Management: What Database Item (DBI) is Needed for Plan Entries based on the Absence Entry ID to Improve Performance of the Fast Formula when Running an Absence Extract? (Doc ID 2713365.1)

Last updated on MARCH 08, 2022

Applies to:

Oracle Fusion Absence Management Cloud Service - Version and later
Oracle Fusion Absence Management - Version and later
Information in this document applies to any platform.
This note was created for Release The note has been reviewed and is current for release


What Database Item (DBI) is needed for Plan entries based on the Absence Entry ID to improve performance of the Fast Formula (FF) when running an Absence Extract?


An HCM Absence Extract was scheduled to run every 15 mins in Changed Attributes mode when it went live. The extract used to finish within 5 to 8 minutes in Changed Attributes mode at that time. Now that extract is taking more than 15 mins to complete. The user increased the duration to schedule the extract every 30 mins. However, this adjustment is impacting downstream systems.

The user wants the Absence Extract to run faster as before. The Absence Extract uses a Fast Formula.

This fast formula is using a value set to get absence hours for a given person_id. The issue is related to the use of the value set that is causing the delay and the suggestion is to use a DBI instead.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.