# Oracle EBS WIP Tables Reference (Work in Process) > Source: https://netray.co/tools/oracle-ebs-wip-tables-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Lookup of Oracle EBS Work in Process tables with purpose and key columns, covering discrete jobs, operations, requirements, resources and interfaces. ## Category oracle ## Erp Oracle E-Business Suite ## Audience - Oracle EBS consultant - Oracle developer - Manufacturing analyst ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Table **Key:** table **Type:** text #### Area **Key:** area **Type:** text #### Purpose **Key:** purpose **Type:** text #### Key columns **Key:** keys **Type:** text **Rows:** **Table:** WIP_ENTITIES **Area:** Jobs **Purpose:** Master record for each job, schedule or flow schedule, holds the name and type **Keys:** WIP_ENTITY_ID, ORGANIZATION_ID, WIP_ENTITY_NAME, ENTITY_TYPE, PRIMARY_ITEM_ID **Table:** WIP_DISCRETE_JOBS **Area:** Jobs **Purpose:** Discrete job header: status, quantities, dates, accounting class **Keys:** WIP_ENTITY_ID, ORGANIZATION_ID, STATUS_TYPE, CLASS_CODE, START_QUANTITY, QUANTITY_COMPLETED, QUANTITY_SCRAPPED **Table:** WIP_OPERATIONS **Area:** Routing **Purpose:** Operations copied onto a job **Keys:** WIP_ENTITY_ID, ORGANIZATION_ID, OPERATION_SEQ_NUM, DEPARTMENT_ID, QUANTITY_IN_QUEUE, QUANTITY_COMPLETED **Table:** WIP_OPERATION_RESOURCES **Area:** Routing **Purpose:** Resources required at each job operation **Keys:** WIP_ENTITY_ID, ORGANIZATION_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, RESOURCE_ID, USAGE_RATE_OR_AMOUNT **Table:** WIP_OPERATION_RESOURCE_USAGE **Area:** Routing **Purpose:** Scheduled resource usage by time **Keys:** WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, START_DATE, COMPLETION_DATE **Table:** WIP_OPERATION_NETWORKS **Area:** Routing **Purpose:** Operation network links between job operations **Keys:** WIP_ENTITY_ID, ORGANIZATION_ID, PRIOR_OPERATION, NEXT_OPERATION **Table:** WIP_REQUIREMENT_OPERATIONS **Area:** Materials **Purpose:** Component requirements for a job **Keys:** WIP_ENTITY_ID, ORGANIZATION_ID, OPERATION_SEQ_NUM, INVENTORY_ITEM_ID, REQUIRED_QUANTITY, QUANTITY_ISSUED **Table:** WIP_DISCRETE_CLASSES **Area:** Setup **Purpose:** Discrete accounting class attributes **Keys:** CLASS_CODE, ORGANIZATION_ID **Table:** WIP_ACCOUNTING_CLASSES **Area:** Setup **Purpose:** Accounting class definitions and default accounts **Keys:** CLASS_CODE, ORGANIZATION_ID, CLASS_TYPE **Table:** WIP_PARAMETERS **Area:** Setup **Purpose:** WIP parameters per organization **Keys:** ORGANIZATION_ID **Table:** WIP_LINES **Area:** Setup **Purpose:** Production line definitions used by repetitive and flow **Keys:** LINE_ID, ORGANIZATION_ID, LINE_CODE **Table:** WIP_REPETITIVE_ITEMS **Area:** Repetitive **Purpose:** Items built on production lines **Keys:** WIP_ENTITY_ID, LINE_ID, ORGANIZATION_ID **Table:** WIP_REPETITIVE_SCHEDULES **Area:** Repetitive **Purpose:** Repetitive schedules **Keys:** REPETITIVE_SCHEDULE_ID, WIP_ENTITY_ID, LINE_ID, ORGANIZATION_ID **Table:** WIP_TRANSACTIONS **Area:** Transactions **Purpose:** Resource and overhead transactions charged to jobs **Keys:** TRANSACTION_ID, WIP_ENTITY_ID, ORGANIZATION_ID, TRANSACTION_TYPE, TRANSACTION_DATE **Table:** WIP_MOVE_TRANSACTIONS **Area:** Transactions **Purpose:** Processed move transactions between operations **Keys:** TRANSACTION_ID, WIP_ENTITY_ID, ORGANIZATION_ID, FM_OPERATION_SEQ_NUM, TO_OPERATION_SEQ_NUM **Table:** WIP_TRANSACTION_ACCOUNTS **Area:** Accounting **Purpose:** Accounting lines for WIP transactions **Keys:** TRANSACTION_ID, WIP_ENTITY_ID, ORGANIZATION_ID, ACCOUNTING_LINE_TYPE, REFERENCE_ACCOUNT **Table:** WIP_PERIOD_BALANCES **Area:** Accounting **Purpose:** Period balances of job cost by element **Keys:** WIP_ENTITY_ID, ORGANIZATION_ID, ACCT_PERIOD_ID **Table:** WIP_SCRAP_VALUES **Area:** Accounting **Purpose:** Scrap cost values by job and operation **Keys:** WIP_ENTITY_ID, ORGANIZATION_ID, OPERATION_SEQ_NUM **Table:** WIP_JOB_SCHEDULE_INTERFACE **Area:** Interface **Purpose:** Open interface to import jobs, schedules and job updates **Keys:** GROUP_ID, PROCESS_PHASE, PROCESS_STATUS, LOAD_TYPE, ORGANIZATION_ID **Table:** WIP_JOB_DTLS_INTERFACE **Area:** Interface **Purpose:** Operation, resource and material detail rows for imported jobs **Keys:** GROUP_ID, PARENT_HEADER_ID, LOAD_TYPE, PROCESS_PHASE, PROCESS_STATUS **Table:** WIP_MOVE_TXN_INTERFACE **Area:** Interface **Purpose:** Open interface for move and completion transactions **Keys:** TRANSACTION_ID, GROUP_ID, PROCESS_PHASE, PROCESS_STATUS, WIP_ENTITY_ID **Table:** WIP_COST_TXN_INTERFACE **Area:** Interface **Purpose:** Open interface for resource and overhead transactions **Keys:** TRANSACTION_ID, GROUP_ID, PROCESS_PHASE, PROCESS_STATUS, WIP_ENTITY_ID **Table:** WIP_TXN_INTERFACE_ERRORS **Area:** Interface **Purpose:** Error messages for rejected WIP interface rows **Keys:** TRANSACTION_ID, ERROR_COLUMN, ERROR_MESSAGE **Table:** WIP_INTERFACE_ERRORS **Area:** Interface **Purpose:** Error messages for rejected job and schedule import rows **Keys:** INTERFACE_ID, ERROR_TYPE, ERROR **Table:** WIP_SHOP_FLOOR_STATUS_CODES **Area:** Setup **Purpose:** Shop floor status code definitions used to hold or restrict operations **Keys:** STATUS_CODE, ORGANIZATION_ID **Table:** WIP_SHIFT_TIMES **Area:** Setup **Purpose:** Shift start and stop times by calendar **Keys:** CALENDAR_CODE, SHIFT_NUM, FROM_TIME, TO_TIME **Notes:** Release 12 naming. Columns vary by release (11i, 12.1, 12.2), so check the eTRM for your version before using a column in a report or interface. ## Content **Intro:** Oracle Work in Process spreads a single job across many tables: the entity, the discrete job, operations, resources, component requirements, transactions and accounting. This list shows where each piece lives and which columns to join on. **Sections:** #### How to use the table list **Body:** Search by area, such as Interface or Materials, or by a column name to find which tables carry it. The key columns field is your join guide. Most WIP tables are keyed by WIP_ENTITY_ID plus ORGANIZATION_ID, so build the habit of joining on both. Export the filtered rows into an Excel sheet to attach to a report specification or a conversion mapping. #### Job structure from header to detail **Body:** WIP_ENTITIES stores the job name and the item being built. WIP_DISCRETE_JOBS holds status, class code, quantities and dates for discrete jobs. WIP_OPERATIONS and WIP_OPERATION_RESOURCES carry the routing copied to the job, and WIP_REQUIREMENT_OPERATIONS carries the components with required and issued quantities. Together they let you compare planned and actual usage by operation. **Bullets:** - Header: WIP_ENTITIES then WIP_DISCRETE_JOBS - Routing: WIP_OPERATIONS then WIP_OPERATION_RESOURCES - Materials: WIP_REQUIREMENT_OPERATIONS joined to the item master - Cost: WIP_PERIOD_BALANCES and WIP_TRANSACTION_ACCOUNTS #### Interfaces and error handling **Body:** Job creation and updates go through WIP_JOB_SCHEDULE_INTERFACE with detail rows in WIP_JOB_DTLS_INTERFACE, processed by the WIP Mass Load concurrent program. Move and completion transactions use WIP_MOVE_TXN_INTERFACE, resource and overhead charges use WIP_COST_TXN_INTERFACE, and material issues and completions go through the inventory transaction interface. When rows stay in the interface, read the error tables first, then check PROCESS_PHASE and PROCESS_STATUS. #### Common mistakes **Body:** Teams sometimes read quantities from WIP_REQUIREMENT_OPERATIONS and assume they equal inventory movements, but returns, scrap and backflush timing change the picture. Another error is updating job tables directly to fix a status. Use the supported forms, the WIP Mass Load interface or the documented APIs, so related accounting and scheduling data stay consistent. **Cta:** If your team spends time hand-writing joins across these tables, we can show how read-only AI queries over WIP data work on your own infrastructure. **Faq:** #### Which table holds the Oracle EBS discrete job status? **Answer:** WIP_DISCRETE_JOBS holds the status in the STATUS_TYPE column, a numeric code. Join to WIP_ENTITIES for the job name. Decode the number using the lookup or form for your release rather than guessing from memory. #### How do I import jobs into Oracle WIP? **Answer:** Load rows into WIP_JOB_SCHEDULE_INTERFACE, and detail rows into WIP_JOB_DTLS_INTERFACE if needed, then run the WIP Mass Load program. Rejected rows are listed in the interface error table with a message for each. #### Where are job component requirements stored? **Answer:** In WIP_REQUIREMENT_OPERATIONS, one row per component per operation, with REQUIRED_QUANTITY and QUANTITY_ISSUED. Join on WIP_ENTITY_ID and ORGANIZATION_ID, and to the item master for descriptions. #### Is WIP_ENTITIES used only for discrete jobs? **Answer:** No. It is the common entity table for discrete jobs, repetitive schedules, flow schedules and, in some releases, lot based jobs. The ENTITY_TYPE column tells you which kind a row is. ## Search terms oracle ebs wip tables, wip_discrete_jobs columns, wip_entities table, wip_operations table, wip_requirement_operations, wip_job_schedule_interface, oracle wip move transaction interface, oracle apps wip tables list --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json