Results for “budget_amount_tc”

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

Overview

AMS_DELIVERABLES_INFO_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the AMS (Marketing) product family and presents a consolidated, denormalized picture of marketing deliverables — the individual items (collateral, kits, funded activities, and similar outputs) that a marketing campaign or program plans to produce and track. Rather than requiring consumers to join the deliverables base tables to category, status, and resource lookups manually, the view performs those joins internally and exposes a single flattened row per deliverable.

The view carries a VALID status in the data dictionary and is defined over four underlying objects. It is a read-only construct intended for inquiry, reporting, and inbound integration rather than for direct DML. Because it resolves the category and sub-category identifiers into descriptive names and resolves the owner user identifier into a full name, it is particularly convenient for ad hoc queries, custom Oracle Reports, OBIEE/BI Publisher data models, and interface extracts. Users who search on the term "deliverable_category" are typically looking for the descriptive category name associated with a deliverable, which this view exposes as the DELIVERABLE_CATEGORY column.

Underlying Base Objects

The documented base objects for the view are:

• AMS_DELIVERABLES_VL (VIEW) — the primary source (aliased B), supplying all deliverable-level attributes. The _VL suffix indicates a view with language/translation handling.
• AMS_CATEGORIES_TL (SYNONYM) — joined twice (aliased C1 and C2) to translate CATEGORY_TYPE_ID into DELIVERABLE_CATEGORY and CATEGORY_SUB_TYPE_ID into DELIVERABLE_SUB_CATEGORY.
• AMS_USER_STATUSES_VL (VIEW, aliased ST) — supplies the descriptive user-defined status name exposed as USER_STATUS.
• AMS_JTF_RS_EMP_V (VIEW, aliased U) — the JTF resource/employee view supplying the owner's full name exposed as OWNER.

The join predicates link B.CATEGORY_TYPE_ID to C1, B.CATEGORY_SUB_TYPE_ID to C2, the deliverable's USER_STATUS_ID to ST, and OWNER_USER_ID to U. Because two of the referenced objects are themselves views, and because the joins depend on language-code and effective-date logic inside those views, query performance should be validated in each environment.

Key Columns

Frequently referenced columns include:

• DELIVERABLE_ID, DELIVERABLE_NAME, DELIVERABLE_CODE — primary identity of the deliverable.
• DELIVERABLE_CATEGORY, DELIVERABLE_SUB_CATEGORY (from CATEGORY_TYPE_ID and CATEGORY_SUB_TYPE_ID) — the descriptive category and sub-category looked up from AMS_CATEGORIES_TL; these are the columns most relevant to a "deliverable_category" search.
• USER_STATUS, STATUS_CODE, STATUS_DATE — workflow/user status name plus the seeded status code and its effective date.
• OWNER, OWNER_USER_ID — the owning resource's full name and identifier.
• ACTIVE_FLAG, PRIVATE_FLAG, KIT_FLAG — enablement, visibility, and kit indicators.
• ACTUAL_AVAIL_FROM_DATE, ACTUAL_AVAIL_TO_DATE, FORECASTED_COMPLETE_DATE, ACTUAL_COMPLETE_DATE — availability and completion tracking dates.
• BUDGET_AMOUNT_TC, BUDGET_AMOUNT_FC, ACTUAL_COST, FORECASTED_COST, CHARGEBACK_AMOUNT — budgeting and cost measures in transaction and functional currency.
• INVENTORY_FLAG, INVENTORY_ITEM_ID, CAN_FULFILL_ELECTRONIC_FLAG, CAN_FULFILL_PHYSICAL_FLAG — fulfillment and inventory characteristics.
• ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY — the standard DFF extension columns.

Common Use Cases and Queries

Typical uses include listing active deliverables by category, reporting owner workloads, and extracting budget versus actual cost. For example, to retrieve deliverables in a specific category:

• SELECT deliverable_name, deliverable_category, deliverable_sub_category, owner, user_status FROM apps.ams_deliverables_info_v WHERE deliverable_category = 'Collateral' AND active_flag = 'Y';
• SELECT owner, deliverable_category, budget_amount_tc, actual_cost FROM apps.ams_deliverables_info_v WHERE TRUNC(creation_date) >= TRUNC(SYSDATE)-30;

Filter by category, status, owner, or date range, and always qualify the view with the APPS schema. Because the view is read-only and consumes DFF attributes, it should not be used for updates; DML must target the base AMS_DELIVERABLES tables directly.