Results for “msc_abc_classes”

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

Overview

MSC_ABC_CLASSES is a reference and classification table within the MSC schema, owned by the Advanced Supply Chain Planning (ASCP) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definition of ABC classification codes used to categorize inventory goods into Class A, Class B, and Class C groupings. These classifications represent a standard inventory segmentation technique in which high-value or high-velocity items are designated Class A, moderately significant items Class B, and lower-value items Class C. Within ASCP, ABC classes drive planning prioritization, safety stock treatment, and targeted exception reporting.

The table functions as a controlled vocabulary of classification codes that planning engines and reporting layers reference rather than duplicating classification logic across the application. Because multiple source instances can feed a single ASCP instance, the table is scoped by source instance so that classifications remain unique per source system.

From a Data Vault modeling perspective, the documented foreign key structure suggests that MSC_ABC_CLASSES behaves as a hub-leaning entity. It is referenced by other tables through a stable business concept (the ABC class) and carries its own descriptive attributes, making it a natural candidate for a hub with an associated satellite for the descriptive columns.

Key Information Stored

The table contains eleven documented columns. The most significant are:

• ABC_CLASS_ID — The surrogate identifier for the classification record and part of the composite primary key.
• SR_INSTANCE_ID — Identifies the source instance the classification belongs to; combined with ABC_CLASS_ID, it forms the primary key MSC_ABC_CLASSES_PK.
• ABC_CLASS_NAME — The user-facing name of the ABC class (for example, "A", "B", or "C"). It participates in the unique index MSC_ABC_CLASSES_U2 together with ORGANIZATION_ID and SR_INSTANCE_ID, making it a strong business-key candidate.
• ORGANIZATION_ID — The inventory organization to which the classification applies, allowing organization-specific class definitions.
• DESCRIPTION — Free-text descriptive text explaining the purpose of the class.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard audit columns that track record creation and modification for audit and interface purposes.

Two unique indexes are documented: MSC_ABC_CLASSES_U1 (ABC_CLASS_ID, SR_INSTANCE_ID) reinforces the surrogate key, while MSC_ABC_CLASSES_U2 (ABC_CLASS_NAME, ORGANIZATION_ID, SR_INSTANCE_ID) represents the natural business key. The surrogate key uniquely identifies a row technically, whereas the business key guarantees uniqueness of the meaningful classification per organization and source instance.

Common Use Cases and Queries

ABC classifications are most commonly consumed when joining planned or on-hand inventory data to the classification that governs it. A typical query resolves the class name for a given inventory item:

• Reporting: "List all ABC classes defined for a given organization" — filter by ORGANIZATION_ID and SR_INSTANCE_ID.
• Item segmentation: joining MSC_SYSTEM_ITEMS to MSC_ABC_CLASSES on ABC_CLASS and SR_INSTANCE_ID to attach a class label to planned items.
• Data validation: confirming that every value in MSC_SYSTEM_ITEMS.ABC_CLASS has a matching, active classification record.
• Cross-instance consolidation: grouping class definitions by SR_INSTANCE_ID to compare classifications across multiple source systems.

A representative pattern filters on the source instance and organization to retrieve the class ID and name for downstream joins or lookup code translation. Because the table is small and relatively static, it is typically joined rather than aggregated.

Related Objects

The principal dependent object is the item master table, which references this classification through a foreign key relationship:

• MSC_SYSTEM_ITEMS — Holds the item records and links to MSC_ABC_CLASSES through MSC_SYSTEM_ITEMS.ABC_CLASS and MSC_SYSTEM_ITEMS.SR_INSTANCE_ID, matching the composite key defined by MSC_ABC_CLASSES_PK. This is the most authoritative integration point for classification data.

Additional planning and reporting objects in the MSC schema, including planning detail tables and ASCP exception views, frequently join to MSC_SYSTEM_ITEMS and inherit the ABC classification through that relationship. Organizations should treat MSC_ABC_CLASSES as a foundational reference table and avoid modifying classifications directly, relying instead on the standard ASCP setup interfaces that populate this and related planning entities.