Results for “serial_prefix”

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

Overview

The WIP.WIP_LPN_COMPLETIONS_SERIALS table is a Work in Process (WIP) transaction table that stores serial number information for materials processed through WIP LPN completions in the Oracle Mobile Supply Chain Applications (Mobile Apps) framework. It is an operational staging and validation table used when finished goods or assemblies are completed into a License Plate Number (LPN) via mobile devices, and where the items being completed are serial-controlled. Each row represents a discrete serial record captured during the LPN completion transaction, including the originating header reference, serial number values, edit-status flags, and error details returned by the mobile completion process.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. This suggests the table functions as a transaction or staging entity in its own right rather than as a conformed hub, link, or satellite in an enterprise Data Vault model. Practitioners may nonetheless choose to treat it as a satellite-like staging source for serial completion events, since it carries descriptive attributes (dates, status codes, attributes) surrounding a business key.

Key Information Stored

The primary key is defined by the constraint WIP_LPN_COMPLETIONS_SERIALS_PK, which is a composite key on (FM_SERIAL_NUMBER, HEADER_ID). This composite serves as the documented unique identifier for each row. In the context of the user's search for "fm_serial_number," FM_SERIAL_NUMBER is the "from" serial number — the starting serial value of the range being completed. It is a business-key candidate and one half of the composite primary key.

• FM_SERIAL_NUMBER — The from-serial number; part of the composite primary key and the primary business identifier.
• HEADER_ID — The transaction header reference linking the serial record to its parent LPN completion transaction; the second component of the composite primary key.
• TO_SERIAL_NUMBER — The ending serial number when a contiguous serial range is being completed, paired with FM_SERIAL_NUMBER.
• SERIAL_PREFIX — The prefix applied to serial numbers generated or validated during completion.
• PARENT_SERIAL_NUMBER — The parent serial for hierarchical or lot-based serial structures.
• LOT_NUMBER — The lot associated with the serialized material.
• TRANSACTION_QUANTITY — The quantity moved for the serialized transaction line.
• STATUS_ID / STATUS_CODE — The processing status of the serial record within the completion flow.
• ERROR_CODE — The validation error returned when the serial fails mobile completion processing.
• ORIGINATION_DATE — The date the serial record originated.
• SERIAL_ATTRIBUTE_CATEGORY — The descriptive-flexfield context for serial attributes.
• C_ATTRIBUTE1–20, N_ATTRIBUTE1–10, D_ATTRIBUTE1–10 — Character, numeric, and date descriptive flexfield segments.
• Audit/Concurrent columns — REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• Lifecycle counters — TIME_SINCE_NEW, CYCLES_SINCE_NEW, TIME_SINCE_OVERHAUL, CYCLES_SINCE_REPAIR, NUMBER_OF_REPAIRS, and similar metrics for serialized asset tracking.

Common Use Cases and Queries

The table is typically queried during mobile completion troubleshooting and serial validation reporting. A frequent pattern is to trace failed completions by error code, or to enumerate all serials tied to a given header.

• Retrieve all serials for a completion header: SELECT FM_SERIAL_NUMBER, TO_SERIAL_NUMBER, STATUS_CODE, ERROR_CODE FROM WIP.WIP_LPN_COMPLETIONS_SERIALS WHERE HEADER_ID = :p_header_id;
• Look up a specific serial by its business key: ... WHERE FM_SERIAL_NUMBER = :p_serial AND HEADER_ID = :p_header_id;
• Report failed mobile completions: ... WHERE ERROR_CODE IS NOT NULL;
• Audit by concurrent program: ... WHERE REQUEST_ID = :p_request_id;

Related Objects

The documented foreign-key structure marks this table as standalone, so no FK-based parent tables are enumerated in the metadata. In practice, the following objects are commonly referenced alongside it:

• WIP.WIP_LPN_COMPLETIONS — the parent completion transaction, joined via HEADER_ID.
• WIP.WIP_LPN_COMPLETIONS_SERIALS_PK — the primary-key constraint on (FM_SERIAL_NUMBER, HEADER_ID).
• MTL_SERIAL_NUMBERS — master serial repository, joined on serial number value.
• MTL_LOT_NUMBERS — lot master, joined via LOT_NUMBER.
• WIP_DISCRETE_JOBS — the job context for the completion transaction.
• FND_CONCURRENT_REQUESTS — resolves REQUEST_ID to the submitting program.