Results for “excel_id”

22 results




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

Overview

MRP_EXCELS is a seed data table owned by the MRP schema within the Master Scheduling/MRP (MRP) product of Oracle E-Business Suite. As documented in the ETRM metadata, its stated purpose is to hold seed data needed for generating graphs. In practice, the table stores definitions for the spreadsheet extracts and graphical output templates that the Oracle planning applications — primarily Oracle Materials Requirements Planning and Oracle Master Scheduling — use to publish planning results in formatted, chart-ready form. Each row represents a named extract definition that ties a logical output (a graph or worksheet) to an underlying program and file.

From a heuristic Data Vault modeling perspective, the metadata classifies MRP_EXCELS as standalone, with no mined foreign key relationships to parent or child objects. This suggests treating it as an independent reference (satellite-style) table keyed on its own business identifier, rather than as a hub or link participating in a broader integration schema.

Key Information Stored

The table comprises 16 documented columns. The most significant are:

  • EXCEL_ID — the surrogate primary key, enforced by the MRP_EXCELS_PK constraint. It uniquely identifies each extract or graph definition.
  • EXCEL_NAME — the business-key candidate, enforced by the unique index MRP_EXCEL_U1. This is the user-facing or programmatic name of the extract.
  • BLOCK_NAME — identifies the logical block or grouping to which the extract belongs, allowing multiple related extracts to be organised together.
  • DESCRIPTION — free-text description of the extract's purpose or content.
  • APPLICATION_SHORT_NAME — the owning application (for example, MRP, BOM, or WIP) whose data the extract draws upon.
  • FILE_NAME — the physical or logical file associated with the definition, used when writing output.
  • INITIAL_SHEET — the initial worksheet or tab used when the extract is generated.
  • PROGRAM_ID and PROGRAM_APPLICATION_ID — identify the concurrent program that generates or consumes the definition.
  • REQUEST_ID and PROGRAM_UPDATE_DATE — standard concurrent-manager context columns.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — the standard EBS audit columns tracking who created and last modified each row.

Common Use Cases and Queries

The principal use case is enumerating the available extract and graph definitions for a given module or block, either for documentation or for validation before running a planning report. A typical query is:

  • SELECT excel_id, excel_name, block_name, file_name FROM mrp.mrp_excels WHERE application_short_name = 'MRP';
  • SELECT excel_name, description FROM mrp.mrp_excels WHERE UPPER(excel_name) LIKE '%GRAPH%';
  • SELECT * FROM mrp.mrp_excels WHERE excel_id = :excel_id; — retrieval by primary key.

Because the table usually contains only seed rows, it is rarely joined to transactional planning tables directly. It is most useful as a lookup to resolve an EXCEL_ID or EXCEL_NAME reference appearing elsewhere in the planning output pipeline. Reporting use cases include auditing which graph definitions exist, verifying that PROGRAM_ID values point to valid concurrent programs after an upgrade, and confirming that FILE_NAME and INITIAL_SHEET values remain correct following a patch or a move to a new file server.

Related Objects

No foreign key relationships were mined from the schema, consistent with its standalone classification. The following dependencies are therefore inferred from the seed-data role and standard MRP conventions rather than from documented constraints:

  • FND_CONCURRENT_PROGRAMS — joined on PROGRAM_ID and PROGRAM_APPLICATION_ID to resolve the generating program.
  • FND_APPLICATION — joined on APPLICATION_SHORT_NAME to identify the owning application.
  • FND_USER — joined on CREATED_BY and LAST_UPDATED_BY for audit tracking.
  • MRP_EXCEL_HEADERS and other extract-related MRP tables — for the wider graph-generation data model.
  • MRP_GROUPS and MRP_SCHEDULE_DESIGNATORS — planning entities that may reference extract definitions by name.

The unique index MRP_EXCEL_U1 on EXCEL_NAME should always be treated as the authoritative business key when populating or querying this table.