Search Results msc_res_basis_type

Overview

APPS.MSC_COMPONENTS_SC_V is a reporting view within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. The "SC" designation denotes a supply chain planning context, and the view exposes bill-of-material component data enriched with descriptive attributes resolved through the MSC_GET_NAME package. Its primary purpose is to flatten the relationship between a planned assembly, its components, and the surrounding planning metadata — item descriptions, organization codes, operation sequence numbers, lookup meanings, and category information — into a single queryable structure. In releases 12.1.1 and 12.2.2, this view serves as a stable integration and reporting layer, insulating downstream queries and extracts from the underlying normalized planning tables.

Underlying Base Objects

The view is defined over the following documented objects:

• MSC_BOM_COMPONENTS (SYNONYM) — supplies the core component rows, including quantity, sequence, planning factor, and scaling attributes.
• MSC_BOMS (SYNONYM) — provides bill header information such as the alternate BOM designator.
• MSC_SYSTEM_ITEMS (SYNONYM) — joined multiple times (aliases DRV and ASSY_NAME) for driving item and assembly item details.
• MSC_ITEMS (SYNONYM) — resolves the component item name.
• MSC_ITEM_CATEGORIES (SYNONYM) — supplies the SR category ID and category set ID.
• MSC_TRADING_PARTNERS (SYNONYM) — referenced for organization type resolution, which gates the scaling-type display logic.
• MFG_LOOKUPS (VIEW) — resolves lookup meanings for supply types, scaling types, and resource basis types.
• MSC_GET_NAME (PACKAGE) — supplies the OR_CODE, OP_SEQ_NUM, ITEM_DESC, and LOOKUP_MEANING functions used to derive display values.

The view therefore sits atop the core ASCP planning schema, with the package and lookup tables performing the descriptive translation at query time.

Key Columns

• INVENTORY_ITEM_ID, ORGANIZATION_ID, PLAN_ID, SR_INSTANCE_ID — the composite planning identity for the component row.
• COMPONENT_SEQUENCE_ID, BILL_SEQUENCE_ID, USING_ASSEMBLY_ID — BOM structural identifiers linking component to parent assembly.
• USAGE_QUANTITY, PLANNING_FACTOR, COMPONENT_YIELD_FACTOR — planning quantity determinants.
• OPERATION_OFFSET_PERCENT — the offset within the routing operation at which the component is consumed.
• SCALING_TYPE — the value most relevant to the user's search term. When the organization type is 2, the view decodes SCALING_TYPE and its meaning is retrieved against the lookup type MSC_RES_BASIS_TYPE, exposing the resource basis interpretation (for example, fixed or proportional). A complementary decode against SYS_YES_NO drives a related indicator column.
• FROM_UNIT_NUMBER, TO_UNIT_NUMBER, EFFECTIVITY_DATE, DISABLE_DATE — date and unit effectivity controls.
• WIP_SUPPLY_TYPE, ALTERNATE_BOM_DESIGNATOR, OPTIONAL_COMPONENT, USE_UP_CODE — descriptive manufacturing attributes.
• REVISION, LAST_UPDATE_DATE, CREATED_BY — audit and revision tracking.

Common Use Cases and Queries

Typical consumers use this view for component explosion reporting, planning parameter audits, and integration extracts. A frequent scenario is identifying resource basis types across planned assemblies:

SELECT inventory_item_id,
       organization_id,
       plan_id,
       component_sequence_id,
       scaling_type
FROM   apps.msc_components_sc_v
WHERE  plan_id = :p_plan_id
AND    sr_instance_id = :p_instance_id;

To surface the decoded resource basis meaning directly, filter or group by the scaling type and reconcile against MFG_LOOKUPS:

SELECT l.meaning,
       COUNT(*)
FROM   apps.msc_components_sc_v v,
       apps.mfg_lookups l
WHERE  l.lookup_type = 'MSC_RES_BASIS_TYPE'
AND    l.lookup_code = TO_CHAR(v.scaling_type)
GROUP  BY l.meaning;

Because MSC_GET_NAME is invoked per row for descriptions, name, and operation sequence, high-volume extracts should filter aggressively on PLAN_ID and ORGANIZATION_ID to control cost. The view is read-only and intended for querying, not for direct DML.