Results for “wip_job_schedule_interface_v”

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

Overview

The APPS.WIP_JOB_SCHEDULE_INTERFACE_V view is a foreign-key resolution view defined over the WIP_JOB_SCHEDULE_INTERFACE table in the Work in Process (WIP) module. Its primary purpose is to present the raw interface table in a human-readable, report-friendly form by decoding internal code values into their corresponding descriptive meanings and by resolving foreign-key identifiers into their business-facing names. This view is central to the WIP job scheduling open interface, which loads production scheduling data — including job schedules, quantities, dates, and supply types — into Oracle EBS from external systems or batch processes.

Because the interface table stores uncompressed code columns (such as LOAD_TYPE, PROCESS_PHASE, and PROCESS_STATUS) and numeric IDs (such as ORGANIZATION_ID, PROJECT_ID, and TASK_ID), the view serves as the canonical layer that report writers and integration developers use to inspect, validate, and troubleshoot scheduling interface records. The object's metadata status is VALID, with the owner schema APPS, confirming it is a supported, upgrade-safe database object.

Underlying Base Objects

The view is defined primarily over the WIP_JOB_SCHEDULE_INTERFACE synonym (WJSI) and draws from a documented set of referenced base objects:

• MFG_LOOKUPS — joined multiple times (aliases ML1–ML7) to convert lookup codes into meanings for LOAD_TYPE, PROCESS_PHASE, PROCESS_STATUS, FIRM_PLANNED_FLAG, STATUS_TYPE, WIP_SUPPLY_TYPE, and SCHEDULING_METHOD.
• ORG_ORGANIZATION_DEFINITIONS (OOD) — resolves ORGANIZATION_ID to an organization code when the interface row stores an ID rather than a code.
• WIP_ENTITIES (WE) — supplies the WIP_ENTITY_NAME (job name).
• FND_USER (FU1, FU2) — resolves LAST_UPDATED_BY and CREATED_BY to user names.
• WIP_SCHEDULE_GROUPS (WSG) — supplies SCHEDULE_GROUP_NAME.
• PA_PROJECTS_ALL (PROJ), PA_TASKS (TASK), and PJM_SEIBAN_NUMBERS — resolve PROJECT_ID, TASK_ID, and project/task numbering.
• WIP_LINES (WL), WIP_DISCRETE_JOBS, HR_GENERAL, and HR_SECURITY — support line codes and organization security filtering.

The view applies DECODE and NVL logic so that when an interface row already carries a denormalized value (for example, an organization code or job name), that value is preserved; otherwise the reference join supplies it.

Key Columns

• INTERFACE_ID, REQUEST_ID, GROUP_ID — the interface row's primary identifier and its batch/request grouping.
• STATUS_TYPE_MEANING — the decoded meaning for the job's status type; this is the column most directly relevant to the searched term status_type_meaning.
• LOAD_TYPE_MEANING, PROCESS_PHASE_MEANING, PROCESS_STATUS_MEANING, FIRM_PLANNED_MEANING, WIP_SUPPLY_TYPE_MEANING, SCHEDULING_METHOD_MEANING — decoded lookup meanings for their respective code columns.
• ORGANIZATION_CODE, (WE.WIP_ENTITY_NAME, WJSI.JOB_NAME) — organization and job identification.
• START_QUANTITY, TOTAL_QUANTITY, NET_QUANTITY — quantities; TOTAL_QUANTITY is derived as PROCESSING_WORK_DAYS * DAILY_PRODUCTION_RATE.
• FIRST_UNIT_START_DATE, FIRST_UNIT_COMPLETION_DATE, LAST_UNIT_START_DATE, LAST_UNIT_COMPLETION_DATE — scheduling dates.
• CLASS_CODE, BOM_REVISION, ROUTING_REVISION, COMPLETION_SUBINVENTORY, LOCATOR — manufacturing attributes.
• PROJECT_NUMBER, TASK_NUMBER, LINE_CODE, SCHEDULE_GROUP_NAME — resolved reference names.
• CREATED_BY_NAME, LAST_UPDATED_BY_NAME — audit user names.

Common Use Cases and Queries

Typical use cases include pre- and post-load validation of the WIP job scheduling interface, reporting on pending versus processed records, and diagnosing rejected rows before they are imported.

Querying by decoded status type using the searched term:

• SELECT interface_id, organization_code, status_type_meaning, class_code FROM apps.wip_job_schedule_interface_v WHERE status_type_meaning = 'Pending';
• SELECT request_id, process_status_meaning, COUNT(*) FROM apps.wip_job_schedule_interface_v GROUP BY request_id, process_status_meaning;
• SELECT interface_id, job_name, scheduling_method_meaning, total_quantity FROM apps.wip_job_schedule_interface_v WHERE process_status = 1;

These queries illustrate how the view's decoded columns eliminate the need to join MFG_LOOKUPS manually, making it the preferred access path for reporting and integration diagnostics against the WIP job scheduling interface.