Search Results create_entity

Overview

WIP_REPETITIVE_ENTITY is an Oracle Work in Process (WIP) entity maintenance package owned by the APPS schema. It is classified by ETRM as an "OTHER" API and is responsible for the lifecycle management of repetitive manufacturing work-in-process entities. In Oracle EBS 12.1.1 and 12.2.2, a repetitive WIP entity represents a scheduled production run on a specific production line for a given assembly. The entity record ties an organization, primary item, production line, and scheduling attributes together so that the repetitive planning and execution processes can track completions, scrap, and rate-based production. WIP_REPETITIVE_ENTITY encapsulates the insert, update, and delete logic for these entities, ensuring that both the master entity row and its repetitive-line-specific detail row remain synchronized. The package uses AUTHID CURRENT_USER, meaning its unqualified references resolve against the calling session's schema and privileges rather than the definer's, a characteristic common to older Oracle EBS seed packages.

Key Procedures and Functions

The package exposes three documented procedures. CREATE_ENTITY creates a WIP entity in the WIP_ENTITIES table and the corresponding row in WIP_REPETITIVE_ITEMS. Its parameter list reflects the full repetitive-entity definition: entity row identifier and entity ID (both IN OUT NOCOPY), name and description, production line and organization, primary item and alternate BOM/routing designators, class code and WIP supply type, completion subinventory and locator, load distribution priority, primary line flag, production line rate, overcompletion tolerance type and value, and a full DFF attribute category with attribute columns 1 through 15. DELETE_ENTITY removes the entity from WIP_REPETITIVE_ITEMS; when the deleted record is the last instance remaining in WIP_REPETITIVE_ITEMS, the parent row in WIP_ENTITIES is also deleted, preserving referential consistency. UPDATE_ENTITY performs the equivalent maintenance for attributes already defined on an existing repetitive entity. No standalone functions are documented.

Tables Accessed

Through APPS synonyms the package reads and writes the following objects. WIP_ENTITIES stores the master WIP entity header, while WIP_ENTITIES_S is its corresponding key-flex or sequence-backed companion used during entity creation. WIP_REPETITIVE_ITEMS holds the repetitive-specific detail (line assignment, rate, and related scheduling data) that qualifies the entity as repetitive. MTL_GEN_OBJECT_ID_S is Oracle's generic object ID sequence, used to generate the primary entity identifier when a new entity is created. DUAL is referenced for single-row computations and sequence/ID lookups. Because WIP_REPETITIVE_ITEMS is the detail table that determines whether the parent entity persists during deletion, the package's coupling of these tables is central to maintaining data integrity across repetitive manufacturing records.

Usage Notes

WIP_REPETITIVE_ENTITY is typically invoked indirectly rather than from end-user forms. The Repetitive Scheduling and Repetitive Planning concurrent programs, as well as the Work in Process application's internal repetitive line maintenance flows, rely on the create, update, and delete operations to build and adjust entities during planning. Custom integrations and data-conversion scripts that load repetitive schedules will call CREATE_ENTITY, then UPDATE_ENTITY as schedule attributes change, and DELETE_ENTITY when a repeated production run is retired. Because the procedures accept NOT COPY IN OUT parameters for the rowid and entity ID, callers must declare and pass bind-compatible variables so the generated WIP_ENTITY_ID is returned correctly. ETRM records that no other packages reference this package, so callers must invoke it directly and are responsible for supplying valid organization, item, line, and DFF values.