Results for “transfered_flag”

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

Overview

OZF_FUNDS_ALL_VL is a multi-language (ML) validation-type view owned by the APPS schema within the Oracle Trade Management (OZF) module. In Oracle EBS 12.1.1 and 12.2.2, this view presents the complete set of funds defined in the Trade Management accrual and budget engine, joining the non-translated base entity table with its translation table to expose descriptive columns in a form suitable for direct querying, LOV (List of Values) display, and integrated reporting. The "VL" suffix indicates a "view with language" that hides the underlying translation join, allowing developers and analysts to retrieve fund header information together with its short name and description without writing an explicit join to the translation table. The view carries status VALID in the documented 12.2.2 environment, meaning it is compiled, supported, and depends only on documented base synonyms.

The view does not itself store data; it is a read-only projection over the fund header and fund translation data. Because it aggregates accrual, budget, currency, hierarchy, and accounting columns into a single relational surface, it is the primary reference object for queries, personalizations, and integrations that require fund identity and descriptive context.

Underlying Base Objects

OZF_FUNDS_ALL_VL is defined over two documented base synonyms: OZF_FUNDS_ALL_B (the non-translated fund header table) and OZF_FUNDS_ALL_TL (the translated name/description table). The join predicate is on FUND_ID and a normalized organization identifier using the pattern NVL(B.ORG_ID, -99) = NVL(T.ORG_ID, -99), which ensures that rows with null ORG_ID are matched correctly. The translation join is further restricted by language, effectively returning the language row appropriate to the session using the standard ML mechanism. The view selects all significant columns from OZF_FUNDS_ALL_B and the SHORT_NAME, DESCRIPTION, LANGUAGE, and SOURCE_LANG columns from OZF_FUNDS_ALL_TL. Each row also exposes a ROWID originating from the base table B.

Key Columns

• Fund identity and hierarchy: FUND_ID, FUND_NUMBER, PARENT_FUND_ID, HIERARCHY, HIERARCHY_ID, HIERARCHY_LEVEL, PARENT_NODE_ID, NODE_ID.
• Fund classification: CATEGORY_ID, FUND_TYPE, FUND_USAGE, PLAN_TYPE, PLAN_ID, SECURITY_GROUP_ID, APPLY_ACCRUAL_ON, ACCRUAL_PHASE, ACCRUAL_METHOD, ACCRUAL_OPERAND, ACCRUAL_RATE, ACCRUAL_BASIS, ACCRUAL_CAP, ACCRUAL_UOM.
• Lifecycle and status: STATUS_CODE, STATUS_DATE, USER_STATUS_ID, START_DATE_ACTIVE, END_DATE_ACTIVE, START_PERIOD_ID, END_PERIOD_ID, START_PERIOD_NAME, END_PERIOD_NAME, FUND_CALENDAR.
• Amounts and currency: BUDGET_AMOUNT_TC, BUDGET_AMOUNT_FC, AVAILABLE_AMOUNT, DISTRIBUTED_AMOUNT, ORIGINAL_BUDGET, TRANSFERED_IN_AMT, TRANSFERED_OUT_AMT, HOLDBACK_AMT, PLANNED_AMT, COMMITTED_AMT, EARNED_AMT, PAID_AMT, CURRENCY_CODE_TC, CURRENCY_CODE_FC, EXCHANGE_RATE_TYPE, EXCHANGE_RATE_DATE, EXCHANGE_RATE.
• Accounting: SET_OF_BOOKS_ID, ACCRUED_LIABLE_ACCOUNT, DED_ADJUSTMENT_ACCOUNT, LIABILITY_FLAG, LIABLE_ACCNT_SEGMENTS, ADJUSTMENT_ACCNT_SEGMENTS, ACCRUAL_DISCOUNT_LEVEL.
• Organization and descriptive: ORG_ID, BUSINESS_UNIT_ID, DEPARTMENT_ID, COSTCENTRE_ID, OWNER, COUNTRY_ID, TASK_ID, SHORT_NAME, DESCRIPTION, LANGUAGE, SOURCE_LANG, and ATTRIBUTE1 through ATTRIBUTE15 with ATTRIBUTE_CATEGORY.
• Audit and WHO columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, CREATED_FROM, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

The view supports reporting on fund balances and accrual activity, LOV lookups on the Trade Management fund form, and integration extracts feeding analytics or downstream accrual reconciliation. It is commonly used where fund identity, status, and descriptive text are needed in one query, avoiding the explicit ML join against OZF_FUNDS_ALL_TL. A typical query listing active funds in a business unit is:

• SELECT fund_id, fund_number, short_name, description, fund_type, status_code, budget_amount_tc, available_amount, currency_code_tc FROM ozf_funds_all_vl WHERE org_id = :p_org_id AND status_code = 'ACTIVE' ORDER BY fund_number;
• SELECT fund_id, fund_number, parent_fund_id, hierarchy_level, earned_amt, committed_amt, paid_amt FROM ozf_funds_all_vl WHERE hierarchy_id = :p_hierarchy_id AND fund_usage = :p_usage ORDER BY hierarchy_level;
• SELECT fund_number, short_name, accrued_liable_account, libale_accnt_segments, exchange_rate, currency_code_fc FROM ozf_funds_all_vl WHERE set_of_books_id = :p_sob_id;

Because the view is a read-only projection and is not key-preserved for DML, all inserts and updates to fund records must be performed against OZF_FUNDS_ALL_B and OZF_FUNDS_ALL_TL directly, or through the corresponding Trade Management APIs and forms. Queries should always constrain ORG_ID for multi-org security unless the calling context is a single-organization deployment.