Work In Progress (WIP)

Oracle WIP Tables

WIP_PARAMETERS
WIP_DISCRETE_JOBS
WIP_ENTITIES
WIP_OPERATIONS
WIP_REQUIREMENT_OPERATIONS
WIP_OPERATION_RESOURCES
WIP_ACCOUNTING_CLASSES
WIP_EMPLOYEE_LABOR_RATES
WIP_INTERFACE_ERRORS
WIP_MOVE_TRANSACTIONS
WIP_MOVE_TXN_INTERFACE
WIP_OPERATION_OVERHEADS
WIP_OPERATION_RESOURCES
WIP_OPERATION_RESOURCE_USAGE
WIP_PERIOD_BALANCES
WIP_SHOP_FLOOR_STATUSES
WIP_SO_ALLOCATIONS
WIP_TRANSACTIONS
WIP_TRANSACTION_ACCOUNTS

Oracle Apps WIP KEY Tables

WIP_LINES
WIP_LINES stores production line information. Each row includes a line name, maximum and minimum rate information, throughput for rate based lines (lead time), and the start and stop time information that determines the amount of time per day that the line is available. Oracle Work in Process uses this information when you associate a line with a repetitive assembly and when you define a repetitive schedule on the line. Production line information is optional for discrete jobs.
WIP_OPERATIONS
WIP_OPERATIONS stores information about job and repetitive schedule operations. Each row represents a specific operation and includes an operation sequence number, which orders the operations for the job or repetitive schedule. Each row also includes the assembly quantity completed at an operation, the quantity at each intraoperation step, the department associated with an operation, the scheduled start and completion dates for an operation, the operation’s count point andbackflush types and other operation attributes. In general, Oracle Work in Process uses this information to control and monitor assembly production on the shop floor.
WIP_ENTITIES
WIP_ENTITIES stores information about jobs, repetitive assemblies, and flow schedules. Each row includes a unique entity name, the entity type,and the assembly being built. Oracle Work in Process uses this information to control production activities and to ensure that entities with duplicate names are not created.
WIP_DISCRETE_JOBS
WIP_DISCRETE_JOBS stores discrete job information. Each row represents a discrete job, and contains information about the assembly being built, the revision of the assembly, the job quantity, the status of the job, the material control method, accounting information, and job schedule dates. Oracle Work in Process uses this information to control discrete production.WIP_TRANSACTIONS
WIP_TRANSACTIONS stores information about WIP resource transactions. Each row represents a single resource transaction and includes a unique transaction Identifier, a transaction date, the job or repetitive schedule charged, the WIP operation and resource charges, and the number of units of measure applied. Oracle Work in Process uses this information to track resource charges and to calculate the values stored in WIP_TRANSACTION_ACCOUNTS.
Oracle Work in Process (WIP) Tables
wip_move_transactions
wip_discrete_jobs
wip_repetitive_schedules
wip_move_txn_interface
wip_cost_txn_interface
wip_job_shedule_interface
wip_job_dtls_interface

FIND JOB ATTACHMENTS IN WIP

SELECT WOI.ORGANIZATION_ID,
WOI.WIP_ENTITY_ID,
WOI.OPERATION_SEQ_NUM,
WOI.OPERATION_DESCRIPTION_CODE Instruction,
FDST.SHORT_TEXT Instruction_Description
FROM WIP_OPERATION_INSTRUCTIONS_V WOI,
FND_DOCUMENTS_VL FDVL,
FND_DOCUMENTS_SHORT_TEXT FDST,
WIP_ENTITIES WE
WHERE WE.WIP_ENTITY_ID = ''
AND WE.ORGANIZATION_ID = ''AND FDVL.SECURITY_ID = WOI.ORGANIZATION_ID
AND WOI.WIP_ENTITY_ID = WE.WIP_ENTITY_ID
AND FDVL.DOCUMENT_ID = WOI.DOCUMENT_ID
AND FDST.MEDIA_ID = FDVL.MEDIA_ID
AND FDVL.DATATYPE_ID= ''
ORDER BY WOI.OPERATION_SEQ_NUM, WOI.OPERATION_DESCRIPTION_CODE
/

JOB WITH SO IN WIP

SELECT DJ.WIP_ENTITY_ID WIP_Entity_ID,
MS.SEGMENT1
'.'
MS.SEGMENT2
'.'
MS.SEGMENT3 C_Sales_Order_Data,
SO.USER_LINE_NUM CI_Line,
SO.USER_DELIVERY User_Delivery,
SO.DEMAND_CLASS SO_Demand_Class,
SO.QUANTITY_ALLOCATED Allocated,
SO.QUANTITY_COMPLETED Qty_Completed
FROM MTL_SALES_ORDERS MS,
WIP_DISCRETE_JOBS DJ,
WIP_SO_ALLOCATIONS SO,
WIP_ENTITIES WE
WHERE SO.WIP_ENTITY_ID = 31649
AND SO.ORGANIZATION_ID = 207
AND DJ.ORGANIZATION_ID = 207
AND DJ.WIP_ENTITY_ID = SO.WIP_ENTITY_ID
AND DJ.WIP_ENTITY_ID = WE.WIP_ENTITY_ID
AND MS.SALES_ORDER_ID = SO.DEMAND_SOURCE_HEADER_ID
ORDER BY SO.USER_LINE_NUM
/

JOB RESERVATIONS IN WIP

SELECT DJ.WIP_ENTITY_ID WIP_Entity_ID,
WRV.DEMAND_SOURCE_LINE_NUMBER CR_Line,
WRV.DEMAND_CLASS_CODE Reservation_Demand_Class,
WRV.PRIMARY_QUANTITY Reserved_Primary_Qty,
WRV.PRIMARY_UOM_CODE Reserved_Primary_UOM,
WRV.RESERVED_LINE_UOM_QUANTITY Reserved_Line_Qty,
WRV.ORDER_LINE_UOM_CODE Reserved_Line_UOM
FROM MTL_SALES_ORDERS MS,
WIP_DISCRETE_JOBS DJ,
WIP_RESERVATIONS_V WRV,
WIP_ENTITIES WE
WHERE WRV.WIP_ENTITY_ID = 31649
AND WRV.ORGANIZATION_ID = 207
AND DJ.ORGANIZATION_ID = 207
AND DJ.WIP_ENTITY_ID = WRV.WIP_ENTITY_ID
AND DJ.WIP_ENTITY_ID = WE.WIP_ENTITY_ID
AND MS.SALES_ORDER_ID = WRV.DEMAND_SOURCE_HEADER_ID
ORDER BY WRV.DEMAND_SOURCE_LINE_NUMBER
/