Results for “mrp_assignment_sets”

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

Overview

MRP_ASSIGNMENT_SETS is a Master Scheduling/MRP (MRP) module table that stores sourcing assignment sets used by Oracle E-Business Suite's planning and sourcing engines. An assignment set is a named grouping that determines which sourcing rules and bills of distribution apply during planning, scheduling, and sourcing calculations. The table resides in the MRP schema and is owned by the MRP product, with status VALID in both 12.1.1 and 12.2.2 releases. The object carries 28 documented columns in the 12.2.2 physical schema.

From a data modeling perspective, the mined Data Vault classification is hub-leaning. Treated as a modeling suggestion, this reflects that MRP_ASSIGNMENT_SETS functions as a business entity hub keyed by a single surrogate identifier, with dependent descriptive attributes and two downstream tables referencing it. It is not a transactional link table or a pure satellite, because assignment sets retain durable identity independent of the plans or assignments that point to them.

Key Information Stored

The most significant columns are:

• ASSIGNMENT_SET_ID — the surrogate primary key, defined by MRP_ASSIGNMENT_SETS_PK. This is the value propagated to child tables.
• ASSIGNMENT_SET_NAME — the business-key candidate, enforced by unique index MRP_ASSIGNMENT_SETS_U1 (and noted as a second unique index, MRP_ASSIGNMENT_SETS_U2, on ASSIGNMENT_SET_ID). This is the user-recognizable identifier for the set.
• DESCRIPTION — free-text description of the assignment set's purpose.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns tracking row and user identity.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the request and program that last wrote the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns, allowing customer-specific extensions without schema change.

Common Use Cases and Queries

Assignment sets are consumed when defining which sourcing logic a plan should use. Planners, sourcing administrators, and reporting developers commonly query this table to list available sets, resolve names for downstream records, and audit changes. A typical lookup joins the name back to its surrogate key:

• Retrieving all assignable sets: SELECT assignment_set_id, assignment_set_name FROM mrp.mrp_assignment_sets;
• Resolving the set used by a plan: join MRP_PLANS.ASSIGNMENT_SET_ID to MRP_ASSIGNMENT_SETS.ASSIGNMENT_SET_ID.
• Resolving the set applied to sourcing assignments: join MRP_SR_ASSIGNMENTS.ASSIGNMENT_SET_ID to MRP_ASSIGNMENT_SETS.ASSIGNMENT_SET_ID.
• Auditing recently modified sets using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Because ASSIGNMENT_SET_NAME is uniquely indexed, it can safely be used as a filter or export key in reporting queries.

Related Objects

Two documented foreign keys reference MRP_ASSIGNMENT_SETS, and both are essential to interpretation:

• MRP_PLANS — references ASSIGNMENT_SET_ID on MRP_PLANS.ASSIGNMENT_SET_ID; identifies the sourcing assignment set associated with each plan.
• MRP_SR_ASSIGNMENTS — references ASSIGNMENT_SET_ID on MRP_SR_ASSIGNMENTS.ASSIGNMENT_SET_ID; links individual sourcing rules to their owning assignment set.

These relationships make MRP_ASSIGNMENT_SETS the parent hub for both planning definitions and sourcing-rule membership, so any query returning plan-level or rule-level sourcing behavior should resolve names through this table.