Search Results p_group_id

Overview

WIP_JOB_DETAILS is an Oracle Work in Process (WIP) package body in the APPS schema that supports the bulk loading of discrete job detail records from the open interface into the production WIP tables. It is a core component of the WIP open interface processing flow, responsible for transferring validated operation, resource, and scheduling information associated with a job entity from the interface staging area into its final destination tables. The package is classified as OTHER within the ETRM taxonomy, reflecting its role as an internal interface-loading engine rather than a public business API. Its source header indicates a relatively stable code line maintained under the wipjdldb.pls module.

Key Procedures and Functions

• LOAD_ALL_DETAILS — The primary driver procedure. It orchestrates the loading of all job detail records for a given processing group. As evidenced by the header excerpt, it accepts a group identifier (p_group_id), a parent header identifier, and a standard-alone flag, and returns error and status information through out parameters. Internally it opens several cursors against WIP_JOB_DTLS_INTERFACE, filtering by group id, parent header id, process phase (WIP_CONSTANTS.ML_VALIDATION), and process status (RUNNING or WARNING), and segregates records by load type into operation and resource streams. This is the procedure most relevant to the search term p_group_id, since the group id is the central selection key for every cursor in the routine.
• DEFAULT_WIP_ENTITY_ID — A support routine that resolves or assigns a default WIP entity identifier when one is not explicitly supplied on the incoming interface rows. It ensures that detail records can be linked to a valid job entity before downstream validation and insertion.

Tables Accessed

• WIP_JOB_DTLS_INTERFACE — The primary staging table read by all cursors in LOAD_ALL_DETAILS; supplies the job, operation, and resource detail rows keyed by group id and parent header id.
• WIP_JOB_SCHEDULE_INTERFACE — Provides schedule-related interface data associated with the job load.
• WIP_OPERATIONS — The destination table for validated operation-level job details.
• WIP_OPERATION_RESOURCES — The destination table for validated resource assignments tied to operations.

All references are made through APPS synonyms, consistent with standard EBS package conventions.

Usage Notes

WIP_JOB_DETAILS is invoked from within the WIP open interface concurrent program flow, typically after records have been validated in the ML_VALIDATION phase. It is also referenced by 19 other packages, indicating that several dependent components rely on its loading routines. The p_group_id parameter is the controlling key: a group id is assigned when interface records are inserted and is used throughout to isolate a single logical load run. Customizations that populate WIP_JOB_DTLS_INTERFACE directly must supply a consistent group id, parent header id, and process phase/status values for LOAD_ALL_DETAILS to process the rows. Because the package body manipulates production WIP tables, it should be invoked only through the sanctioned interface flow rather than called directly from custom forms or ad hoc scripts.