1. Get rid of all advertisements and get unlimited access to documents by upgrading to Premium Membership. Upgrade to Premium Now and also get a Premium Badge!

Oracle Apps WIP KEY Tables

Discussion in 'Oracle Apps Technical' started by Sadik, Dec 21, 2008.

  1. Sadik

    Sadik Community Moderator Forum Guru

    Likes Received:
    Trophy Points:
    Oracle Apps WIP KEY Tables


    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 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 and
    backflush 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 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 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 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.