Results for “cummulative_pct”

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

Overview

MSC_ST_OPERATION_RESOURCE_SEQS is a staging (interface) table owned by the MSC schema within the Advanced Supply Chain Planning product of Oracle E-Business Suite. In the EBS architecture, planning data is not read directly from the transactional schemas of Discrete Manufacturing, Process Manufacturing, or Bills of Material. Instead, the data collection program extracts source records into MSC_ST_* staging tables, applies validation and transformation logic, and then loads the cleansed rows into the corresponding MSC_* planning tables. This table is the staging counterpart of MSC_OPERATION_RESOURCE_SEQS: it holds resource-level assignments that belong to a routing operation sequence, including the sequence ordering of resources within an operation, scheduling flags, offset percentages, and department references. During a planning collection run, rows are written here, checked for referential and domain integrity, and either promoted to the planning table or rejected with the appropriate error recorded by the collection program.

From a data-modeling perspective, the ETRM metadata classifies this object heuristically as standalone — it has no child tables within the mined foreign-key structure and functions as an independent staging entity. It is therefore best treated as a staging satellite of the corresponding planning resource-sequence entity rather than as a hub or link. This classification should be regarded as a modeling suggestion only, since the FK structure of staging tables is intentionally thin and does not reflect the full business relationship model of the target planning schema.

Key Information Stored

The documented physical schema comprises 21 columns. The most significant for collection and planning purposes are:

• ROUTING_SEQUENCE_ID — identifies the routing sequence (the routing header/step context) that owns the operation.
• OPERATION_SEQUENCE_ID — identifies the specific operation sequence within the routing to which the resource requirement belongs.
• RESOURCE_SEQ_NUM — the ordinal sequence of the resource within the operation, defining precedence when multiple resources are required.
• DEPARTMENT_ID — foreign key to BOM_DEPARTMENTS, identifying the department that owns the resource.
• SCHEDULE_FLAG — indicates whether the resource participates in scheduling calculations.
• RESOURCE_OFFSET_PERCENT — the offset percentage applied to a resource relative to the operation start or end.
• CUMMULATIVE_PCT — cumulative percentage used for resource offset/consumption calculations across sequenced resources.
• ACTIVITY_GROUP_ID — grouping identifier used to associate resources within an activity context.
• ORGANIZATION_ID — the inventory organization against which the resource sequence is collected.
• DELETED_FLAG — soft-delete indicator applied by the collection process.
• SR_INSTANCE_ID and REFRESH_ID — identify the source system instance and the collection snapshot under which the row was staged.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — the concurrent request and program audit trail that identifies the collection run responsible for the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — the standard EBS WHO audit columns.

No surrogate primary key is documented for this staging table, which is typical of MSC_ST_* objects: rows are keyed operationally by the combination of ROUTING_SEQUENCE_ID, OPERATION_SEQUENCE_ID, RESOURCE_SEQ_NUM, ORGANIZATION_ID, and SR_INSTANCE_ID / REFRESH_ID. The FK to BOM_DEPARTMENTS on DEPARTMENT_ID is the only documented referential constraint.

Common Use Cases and Queries

Because this is a staging table, its principal consumers are the collection programs and support/diagnostic personnel investigating planning data discrepancies. Typical uses include:

• Verifying that a collection run loaded resource sequences for a given organization and request before promotion to MSC_OPERATION_RESOURCE_SEQS.
• Identifying rejected or orphaned rows, for example resources whose DEPARTMENT_ID does not resolve in BOM_DEPARTMENTS.
• Auditing cumulative and offset percentages for resource sequencing before they influence capacity and scheduling calculations.
• Comparing staged counts against the production planning table to detect duplicate or stale snapshots.

A representative diagnostic query:

• SELECT s.ROUTING_SEQUENCE_ID, s.OPERATION_SEQUENCE_ID, s.RESOURCE_SEQ_NUM, s.DEPARTMENT_ID, s.CUMMULATIVE_PCT FROM MSC.MSC_ST_OPERATION_RESOURCE_SEQS s WHERE s.ORGANIZATION_ID = :org AND s.REQUEST_ID = :request_id ORDER BY s.ROUTING_SEQUENCE_ID, s.OPERATION_SEQUENCE_ID, s.RESOURCE_SEQ_NUM;
• To find unresolvable departments: SELECT s.* FROM MSC.MSC_ST_OPERATION_RESOURCE_SEQS s WHERE NOT EXISTS (SELECT 1 FROM BOM.BOM_DEPARTMENTS d WHERE d.DEPARTMENT_ID = s.DEPARTMENT_ID);

Related Objects

• MSC_OPERATION_RESOURCE_SEQS — the target planning table populated from this staging table.
• BOM_DEPARTMENTS — referenced via DEPARTMENT_ID; the only documented foreign key.
• MSC_OPERATION_SEQUENCES / MSC_ST_OPERATION_SEQUENCES — parent operation sequences to which resource sequences belong.
• MSC_ROUTING_SEQUENCES / MSC_ST_ROUTING_SEQUENCES — routing context for ROUTING_SEQUENCE_ID.
• MSC_ST_RESOURCE_SEQS — resource-level staging entity used by the same collection cycle.
• MSC_SYSTEM_ITEMS — item context resolved through the routing/operation chain.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to identify the collection program run.