OracleFree referencePDF, Excel, Word exportOracle E-Business Suite

Oracle EBS WIP Tables Reference (Work in Process)

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.

Download:

Table	Area	Purpose	Key columns
WIP_ENTITIES	Jobs	Master record for each job, schedule or flow schedule, holds the name and type	WIP_ENTITY_ID, ORGANIZATION_ID, WIP_ENTITY_NAME, ENTITY_TYPE, PRIMARY_ITEM_ID
WIP_DISCRETE_JOBS	Jobs	Discrete job header: status, quantities, dates, accounting class	WIP_ENTITY_ID, ORGANIZATION_ID, STATUS_TYPE, CLASS_CODE, START_QUANTITY, QUANTITY_COMPLETED, QUANTITY_SCRAPPED
WIP_OPERATIONS	Routing	Operations copied onto a job	WIP_ENTITY_ID, ORGANIZATION_ID, OPERATION_SEQ_NUM, DEPARTMENT_ID, QUANTITY_IN_QUEUE, QUANTITY_COMPLETED
WIP_OPERATION_RESOURCES	Routing	Resources required at each job operation	WIP_ENTITY_ID, ORGANIZATION_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, RESOURCE_ID, USAGE_RATE_OR_AMOUNT
WIP_OPERATION_RESOURCE_USAGE	Routing	Scheduled resource usage by time	WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM, START_DATE, COMPLETION_DATE
WIP_OPERATION_NETWORKS	Routing	Operation network links between job operations	WIP_ENTITY_ID, ORGANIZATION_ID, PRIOR_OPERATION, NEXT_OPERATION
WIP_REQUIREMENT_OPERATIONS	Materials	Component requirements for a job	WIP_ENTITY_ID, ORGANIZATION_ID, OPERATION_SEQ_NUM, INVENTORY_ITEM_ID, REQUIRED_QUANTITY, QUANTITY_ISSUED
WIP_DISCRETE_CLASSES	Setup	Discrete accounting class attributes	CLASS_CODE, ORGANIZATION_ID
WIP_ACCOUNTING_CLASSES	Setup	Accounting class definitions and default accounts	CLASS_CODE, ORGANIZATION_ID, CLASS_TYPE
WIP_PARAMETERS	Setup	WIP parameters per organization	ORGANIZATION_ID
WIP_LINES	Setup	Production line definitions used by repetitive and flow	LINE_ID, ORGANIZATION_ID, LINE_CODE
WIP_REPETITIVE_ITEMS	Repetitive	Items built on production lines	WIP_ENTITY_ID, LINE_ID, ORGANIZATION_ID
WIP_REPETITIVE_SCHEDULES	Repetitive	Repetitive schedules	REPETITIVE_SCHEDULE_ID, WIP_ENTITY_ID, LINE_ID, ORGANIZATION_ID
WIP_TRANSACTIONS	Transactions	Resource and overhead transactions charged to jobs	TRANSACTION_ID, WIP_ENTITY_ID, ORGANIZATION_ID, TRANSACTION_TYPE, TRANSACTION_DATE
WIP_MOVE_TRANSACTIONS	Transactions	Processed move transactions between operations	TRANSACTION_ID, WIP_ENTITY_ID, ORGANIZATION_ID, FM_OPERATION_SEQ_NUM, TO_OPERATION_SEQ_NUM
WIP_TRANSACTION_ACCOUNTS	Accounting	Accounting lines for WIP transactions	TRANSACTION_ID, WIP_ENTITY_ID, ORGANIZATION_ID, ACCOUNTING_LINE_TYPE, REFERENCE_ACCOUNT
WIP_PERIOD_BALANCES	Accounting	Period balances of job cost by element	WIP_ENTITY_ID, ORGANIZATION_ID, ACCT_PERIOD_ID
WIP_SCRAP_VALUES	Accounting	Scrap cost values by job and operation	WIP_ENTITY_ID, ORGANIZATION_ID, OPERATION_SEQ_NUM
WIP_JOB_SCHEDULE_INTERFACE	Interface	Open interface to import jobs, schedules and job updates	GROUP_ID, PROCESS_PHASE, PROCESS_STATUS, LOAD_TYPE, ORGANIZATION_ID
WIP_JOB_DTLS_INTERFACE	Interface	Operation, resource and material detail rows for imported jobs	GROUP_ID, PARENT_HEADER_ID, LOAD_TYPE, PROCESS_PHASE, PROCESS_STATUS
WIP_MOVE_TXN_INTERFACE	Interface	Open interface for move and completion transactions	TRANSACTION_ID, GROUP_ID, PROCESS_PHASE, PROCESS_STATUS, WIP_ENTITY_ID
WIP_COST_TXN_INTERFACE	Interface	Open interface for resource and overhead transactions	TRANSACTION_ID, GROUP_ID, PROCESS_PHASE, PROCESS_STATUS, WIP_ENTITY_ID
WIP_TXN_INTERFACE_ERRORS	Interface	Error messages for rejected WIP interface rows	TRANSACTION_ID, ERROR_COLUMN, ERROR_MESSAGE
WIP_INTERFACE_ERRORS	Interface	Error messages for rejected job and schedule import rows	INTERFACE_ID, ERROR_TYPE, ERROR
WIP_SHOP_FLOOR_STATUS_CODES	Setup	Shop floor status code definitions used to hold or restrict operations	STATUS_CODE, ORGANIZATION_ID
WIP_SHIFT_TIMES	Setup	Shift start and stop times by calendar	CALENDAR_CODE, SHIFT_NUM, FROM_TIME, TO_TIME

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.

Shop floor questions answered from WIP data

Optional: a walkthrough of read-only natural-language reporting on Oracle WIP tables.

Optional. The tool and every export work without this. No spam.

How to use the table list

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

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.

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

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

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.

Frequently Asked Questions

Which table holds the Oracle EBS discrete job status?

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?

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?

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?

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.

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.

Talk to an Expert Explore More Free Tools

Related Tools

Oracle

More Oracle tools

See all

Back to All Tools