JDBC Driver for Oracle Fusion Cloud Financials

Build 25.0.9434

RequisitionPreferencesfavoriteChargeAccounts

Tracks a user’s most commonly used charge accounts, simplifying account selection during requisition line allocation.

Columns

Name Type Description
RequisitionPreferencesUserPreferenceId [KEY] Long The unique identifier for the requisition preferences associated with the favorite charge account. Example: 1001 for User Preference ID 1001.
UserPreferenceId Long The unique identifier for the user's requisition preferences record. Example: 2001 for the specific user's preferences.
UserPreferenceAccountId [KEY] Long The unique identifier for the account linked to the user's requisition preferences. Example: 3001 for the account associated with the user's preferences.
CodeCombinationId Long The unique identifier for the charge account combination, linking it to the accounting setup. Example: 4001 for the specific code combination.
ChargeAccountNickname String The nickname or alias given to the charge account within the requisition preferences for easier identification. Example: 'Main Office Supplies' for an account used for office supplies.
ChargeAccount String The actual account to which goods or services requested in the requisition are charged. Example: 'Office Supplies Account' for the account that handles office-related expenses.
PrimaryFlag Bool Indicates whether the favorite charge account is set as the primary account for requisitions. Example: True if this account is the primary account for the user.
Finder String A reference or placeholder used for searching and locating specific charge account records. Example: 'Search by Account Nickname' or 'Search by Charge Account'.
PersonId Long The unique identifier for the person associated with the requisition preferences. Example: 5001 for Person ID 5001.
RequisitioningBUId Long The unique identifier for the business unit associated with the requisition preferences. Example: 6001 for the Requisitioning Business Unit ID.
SysEffectiveDate Date The date from which the requisition preferences for the charge account are effective. Example: '2023-06-01' for the effective date of the preference.
EffectiveDate Date This query parameter is used to fetch resources which are effective as of the specified start date. Example: '2023-06-01' for fetching records effective from this date.

Copyright (c) 2025 CData Software, Inc. - All rights reserved.
Build 25.0.9434