Results for “prorate_convention_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKX_AST_CT_BK_DFS_V is a valid APPS-owned database view within the OKX – Contracts Integration product of Oracle E-Business Suite (12.1.1 and 12.2.2). Its documented purpose is to provide default depreciation rules based on asset category and book, and it is consumed by the Contracts Integration flow at the time an asset line is created. In practice, the view serves as a filtered, contract-facing projection of Oracle Assets category book defaults, allowing the OKX integration layer to derive the depreciation parameters that should be applied to a newly created asset line without querying the full FA_CATEGORY_BOOK_DEFAULTS table directly.

The view is particularly relevant to searches involving “bonus_rule,” because BONUS_RULE is one of the depreciation attributes it surfaces. Oracle Assets uses BONUS_RULE to associate a bonus depreciation rule with a category/book combination, and by exposing this column the OKX view lets contract-driven asset creation inherit that bonus rule automatically.

Underlying Base Objects

The view is defined over a single documented base object: FA_CATEGORY_BOOK_DEFAULTS, referenced through a SYNONYM in the APPS schema. FA_CATEGORY_BOOK_DEFAULTS is the Oracle Assets table that stores default depreciation attributes for each asset category and book pair, keyed logically by CATEGORY_ID and BOOK_TYPE_CODE along with effective start and end periods (START_DPIS, END_DPIS). OKX_AST_CT_BK_DFS_V does not introduce joins to additional tables; it is a direct projection of that table’s columns, aliased as FACBD in the view text. Because it rests on a synonym to the underlying FA table, the view inherits the standard Oracle Assets multi-organization and security behavior of that base object.

Key Columns

• NAME / DESCRIPTION — Hard-coded to '#' in the view text, enabling the OKX integration to satisfy any not-null or display requirements without altering the underlying defaults.
• CATEGORY_ID — Asset category identifier; the primary driver of the default lookup.
• BOOK_TYPE_CODE — Depreciation book (for example, a corporate or tax book) for which the defaults apply.
• START_DPIS / END_DPIS — Effective date range of the default row, expressed in date-placed-in-service terms.
• LIFE_IN_MONTHS, DEPRN_METHOD, PRORATE_CONVENTION_CODE — Core depreciation parameters inherited by new asset lines.
• BONUS_RULE — The bonus depreciation rule associated with the category/book; central to “bonus_rule” lookups.
• ITC_ELIGIBLE_FLAG, USE_ITC_CEILINGS_FLAG, CEILING_NAME, BASIC_RATE, ADJUSTED_RATE — Investment tax credit and rate attributes.
• DEPRECIATE_FLAG, RETIREMENT_PRORATE_CONVENTION, PRICE_INDEX_NAME, USE_STL_RETIREMENTS_FLAG, STL_METHOD_CODE, STL_LIFE_IN_MONTHS — Depreciation and retirement treatment controls.
• SUBCOMPONENT_LIFE_RULE, MINIMUM_LIFE_IN_MONTHS, PRODUCTION_CAPACITY, UNIT_OF_MEASURE — Subcomponent, life, and production-based depreciation settings.
• CAPITAL_GAIN_THRESHOLD, USE_DEPRN_LIMITS_FLAG, ALLOWED_DEPRN_LIMIT, SPECIAL_DEPRN_LIMIT_AMOUNT, PERCENT_SALVAGE_VALUE — Limit, gain, and salvage attributes.
• CUA_LIFE_END_DATE, CUA_RULE_SET_ID — Custom/advanced rule set and life end references.
• ID1 / ID2 — Composite identifiers built from CATEGORY_ID and BOOK_TYPE_CODE concatenated with START_DPIS, used by the OKX integration for keying.

Common Use Cases and Queries

The principal scenario is defaulting depreciation attributes, including BONUS_RULE, when an asset line is created from a contract. A representative query returning the bonus rule and depreciation method for a category and book is:

• SELECT category_id, book_type_code, start_dpis, end_dpis, life_in_months, deprn_method, bonus_rule FROM apps.okx_ast_ct_bk_dfs_v WHERE category_id = :p_category_id AND book_type_code = :p_book;
• SELECT category_id, book_type_code, bonus_rule FROM apps.okx_ast_ct_bk_dfs_v WHERE bonus_rule IS NOT NULL; — identifies category/book combinations with an assigned bonus rule.
• SELECT id1, id2, name, description, bonus_rule FROM apps.okx_ast_ct_bk_dfs_v WHERE category_id = :p_category_id; — retrieves the OKX-facing key and display columns alongside the bonus rule.

Additional uses include validating that a category/book has effective defaults for a given placed-in-service date, auditing the depreciation attributes that contract-created assets will inherit, and troubleshooting bonus depreciation discrepancies between a contract asset line and the Oracle Assets category setup.