Results for “pull_sequence_id”

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

Overview

MTL_KANBAN_CARD_PRINT_TEMP is an inventory module table owned by the INV schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. As its name and the ETRM description indicate, the table is a temporary staging object used to print kanban cards. Kanban functionality in Oracle Inventory supports pull-based replenishment, in which kanban cards represent replenishment signals between supplying and consuming organizations. When a user initiates the kanban card print process from the Oracle Forms interface, the runtime engine populates this table with the set of cards selected for that printing run, and the report or concurrent program thereafter consumes the staged rows to produce the physical card output.

The table is intentionally short-lived in nature. Because the report identifier (REPORT_ID) groups rows belonging to a single print request, records written for one execution of the print program are logically isolated from other executions, and they are of no continuing transactional value once the cards have been printed. From a data modeling perspective, the ETRM metadata classifies MTL_KANBAN_CARD_PRINT_TEMP heuristically as standalone in Data Vault terms. This classification should be read as a modeling suggestion rather than a physical constraint: because the table carries only three documented columns and functions purely as a transient print buffer, it does not naturally decompose into a hub, link, or satellite structure, and it is best treated as a disposable staging object rather than a subject-oriented historical entity.

Key Information Stored

The documented physical schema for this table contains only three columns. Each plays a distinct role in the print process:

• REPORT_ID — Identifies the specific print run or report execution. All rows generated by one invocation of the kanban card print program share a REPORT_ID, which allows the report to select precisely its own staged rows and allows cleanup to be scoped to a single run.
• PULL_SEQUENCE_ID — Foreign key to MTL_KANBAN_PULL_SEQUENCES. It links each staged row to the kanban pull sequence that defines the replenishment relationship — the supplying organization, the consuming organization, the source and destination subinventories, and the kanban size/quantity attributes used when the card is generated.
• KANBAN_CARD_ID — Foreign key to MTL_KANBAN_CARDS. It identifies the individual kanban card being printed, tying the staged row directly to the card master record that holds the card number and status.

No surrogate primary key is documented for this table, which is consistent with its role as a temporary staging structure — uniqueness is achieved operationally through the combination of REPORT_ID with the referenced card identifier, rather than through a single-column system-generated key. The only documented integrity constraints are the two foreign keys to MTL_KANBAN_PULL_SEQUENCES and MTL_KANBAN_CARDS, making both referenced identifiers the effective business-key candidates.

Common Use Cases and Queries

The primary use case is diagnostic: when a kanban card print request fails, produces a blank report, or omits cards expected by the user, the staged rows in this table reveal exactly which cards were selected by the process. The following pattern retrieves the contents of a specific print run:

• SELECT report_id, pull_sequence_id, kanban_card_id FROM inv.mtl_kanban_card_print_temp WHERE report_id = :report_id; — inspect the row set for one print execution.
• Joining to MTL_KANBAN_CARDS on KANBAN_CARD_ID to retrieve card numbers and statuses, and to MTL_KANBAN_PULL_SEQUENCES on PULL_SEQUENCE_ID to retrieve the supplying/consuming organization and item context, provides an audit view of a print run.
• A grouped query such as SELECT report_id, COUNT(*) FROM inv.mtl_kanban_card_print_temp GROUP BY report_id is useful for identifying stale or orphaned staged rows left behind by interrupted print processes.

Because the table is transient, it should not be used as a reporting source of record. Operational housekeeping — deleting rows for completed or abandoned report runs — is a routine maintenance consideration, and administrators should not treat residual rows as evidence of outstanding replenishment demand.

Related Objects

The table's dependencies are defined by its two foreign keys and the surrounding kanban inventory infrastructure:

• MTL_KANBAN_CARDS — referenced through KANBAN_CARD_ID; the master card definition printed by the process.
• MTL_KANBAN_PULL_SEQUENCES — referenced through PULL_SEQUENCE_ID; defines the kanban replenishment relationship and quantities.
• MTL_KANBAN_CARD_PRINT_TEMP is populated by the kanban card print concurrent program/report in the INV module; the report definition itself is the principal consuming component.
• MTL_SYSTEM_ITEMS_B, MTL_ITEM_LOCATIONS, and MTL_PARAMETERS are commonly joined indirectly through the card and pull sequence records to supply item, locator, and organization context in audit queries.
• MTL_KANBAN_CARD_PRINT_TEMP has no dependent child tables documented; as a standalone staging object it is referenced by nothing else, which is expected for a print buffer.