Vous êtes sur la page 1sur 14

Contents

Introduction.....................................................................................................................................................................................1 Technical Overview .......................................................................................................................................................................2 Main Entities in Oracle WIP.........................................................................................................................................................3 BOM (Bill of Materials)...............................................................................................................................................................3 Routing.........................................................................................................................................................................................3 Discrete Job..................................................................................................................................................................................3 Exercises.......................................................................................................................................................................................5 Key Concepts in Oracle WIP.........................................................................................................................................................6 Main Interfaces...............................................................................................................................................................................7 Open Move Transaction Interface................................................................................................................................................7 Exercises.......................................................................................................................................................................................8 Open Resource Transaction Interface...........................................................................................................................................8 Exercises.......................................................................................................................................................................................8 Work Order Interface....................................................................................................................................................................8 Exercises.......................................................................................................................................................................................9 Major Processes............................................................................................................................................................................10 Intermediate Shipment................................................................................................................................................................10 Ship and Receive Intermediate workflow...................................................................................................................................10 Other important tables in this module........................................................................................................................................11 Important Profile Options...........................................................................................................................................................12

Table of Figures

PO Training PO_TRAINING.DOC

ii KPIT-Cummins Confidential - For internal use only

Introduction
Oracle Work in Process (WIP) is a complete production management system. Oracle WIP records actual production activity. It lets you report production against discrete jobs or repetitive schedules or by using work order-less completion transaction. It deals with the day-to-day activities of the shop floor like 1. 2. 3. 4. 5. Creation of the Job / Work order Releasing jobs. Material Control Material Issue Finished product receipt. Rejection / scrap. Reporting the Job progress Recording production completion.

Discrete Manufacturing Discrete production records all production activities against a discrete job, sometimes called as a work order, shop order or production order. It is a plan to produce specific quantity of item at a given date. All material issues and all resources charges are charged to specific job.

Repetitive Manufacturing It models the high volume production of standard items over a period of time. It is plan to produce an item at a given daily rate for a period of time. Material and resources are charged to the item and production line.

Flow manufacturing It is designed for the production mixed products on a production line, one at a time, at the rate of production dictated by demand.

Error! Use the Home tab to apply title to the text that you want to appear here. 77907483.doc Oracle/Client Confidential - For internal use only

Introduction

Technical Overview
MRP ORDER MANAGEMENT DEFINE DISCRETE JOB FORM

PLANNED ORDERS

SALES ORDERS

MANUAL/ NON SCHEDULE PRODUCTION

EXTERNAL SYSTEM

WIP_JOB_SCHEDULE_INTERFACE. BOM_BILL_OF_MATERIALS WIP_JOB_DTLS_INFO BOM_OPERATIONAL_ROUTINGS

WIP_ENTITIES

WIP_DISCRETE _JOBS

WIP_OPERATIONS

WIP_REQUIREMENT _OPERATIONS

WIP_OPERATION_ RESOURCES

MOVE TRANSACTION INTERFACE TABLES

MOVE TRANSACTION FORM

DISCRETE WORKSTATION

WIP MATERIAL TRANSACTION FORM

WIP_MOVE_TRANSACTIONS

MTL_MATERIAL_TRANSACTIONS_TEMP

MTL_MATERIAL_TRANSACTIONS

MTL_TRANSACTION_ACCOUNTS

WIP_PERIOD_BALANCES

Error! Use the Home tab to apply title to the text that you want to appear here. 77907483.doc Kpit Cummins Infosystems Ltd Confidential - For internal use only

Main Entities in Oracle WIP

Main Entities in Oracle WIP


Following are the main entities in Oracle WIP: 1. 2. 3. 4. 5. BOM Routings Discrete Job Repetitive Schedules Flow Manufacturing

BOM (Bill of Materials)


BOM is the list of the components and their required quantity to make the parent item. When the discrete job is created, the system explodes the assemblys effective BOM to create the material requirements for the job. If the assembly has no effective bill you will receive a warning message, but the job will be created. You can disable the items Build in WIP attribute to prevent the creation of the job when there is no BOM.

Main tables: BOM_BILL_OF_MATERIALS, BOM_INVENTORY_COMPONENTS Routing


It is a document that defines the step by step operations one need to perform to manufacture the assembly. System uses routing to create a schedule for the job. If the assembly has no effective Routing you will receive a warning message, but the job will be created. You can disable the items Build in WIP attribute to prevent the creation of the job when there is no Routing.

Main tables: BOM_OPERATIONAL_ROUTINGS Discrete Job


Discrete job is nothing but the Production order or Work Order. Discrete jobs can be created in several ways by releasing the planned orders from planning applications, by auto-creating jobs based on sales orders, by manually creating or through an interface. The definition of the Discrete job details the completion of the specific quantity of an item on specific date. You must release a job to production before transacting against it. Releasing a discrete job with a routing automatically loads the job quantity into the Queue intraoperation step of the first operation. If PO Move or PO Receipt resource requirements exist at the first operation, purchase requisitions for these resources are automatically generated. In turn Discrete Job means Definition of the demand of the item to be produced The components and resources need to produce the item over period of time. Record and reporting the progress of the item through different production stages. Inventory movements needed. Costing and variance calculations.

The Discrete Workstation provides you with a single window from which you can obtain critical production information and perform common shop floor transactions without having to return to the main menu. The workstation displays information either for a department or for a resource, depending on how you launch it, and it lists all of the job operations for immediate and future dispatch at that department or resource.
Following are the main tables for Discrete Job
Error! Use the Home tab to apply title to the text that you want to appear here. 77907483.doc Kpit Cummins Infosystems Ltd Confidential - For internal use only Main Entities in Oracle WIP 3

WIP_ENTITIES: WIP_ENTITIES is the major master table which stores the information about the entity createdinOracleWIP.ItbasicallydetailstheEntityNameandTypeofEntity.OracleWorkin Processusesthisinformationtocontrolproductionactivitiesandtoensurethatentitieswith duplicatenamesarenotcreated.ENITY_TYPEcolumnstorestheinformationaboutthetype ofentityitis.

ENTITY_TYPE
1 2 3 4

MEANING
Discrete job Repetitive assembly Closed discrete job Flow schedule

WIP_ENTITY_ID is the unique systemgenerated requisition number that identifies the entity created in WIP. WIP_DISCRETE_JOBS WIP_DISCRETE_JOBSstoresdiscretejobinformation.Eachrowrepresentsadiscretejob,and containsinformationabouttheassemblybeingbuilt,therevisionoftheassembly,thejob quantity,thestatusofthejob,thematerialcontrolmethod,accountinginformation,andjob scheduledates.OracleWorkinProcessusesthisinformationtocontroldiscreteproduction. Each row contains the Job Status (STATUS_TYPE), Supply type (WIP_SUPPLY_TYPE), Start Date, Completion date, Charge and Variances accounts, BOM and Routings referred, quantity info etc. This table corresponds to the main window of the Discrete Jobs form. WIP_OPERATIONS WIP_OPERATIONSstoresinformationaboutjobandrepetitiveschedule operations.Each row represents a specific operation and includes an operation sequence number, which orderstheoperationsforthejoborrepetitiveschedule.Eachrowalsoincludestheassembly quantitycompletedatanoperation,thequantityateachintraoperationstep,thedepartment associatedwithanoperation,thescheduledstartandcompletiondatesforanoperation,the operationscountpointandbackflushtypesandotheroperationattributes. ThevaluesofthecolumnsBACKFLUSH_FLAGandCOUNT_POINT_TYPEdecideswhether toissuetheinventoryafterthisoperationgetscompletedandwhetherthisoperationcanbe skipped. WIP_REQUIREMENT_OPERATIONS WIP_REQUIREMENT_OPERATIONS stores the information regarding the requirement of thedifferentcomponentsatvariousproductionstages(operations).Therequirementcreated when the job or schedule is created, specify the quantity, supply type, and supply subinventoryandlocatorforeachcomponent. Eachrowrepresentsamaterialrequirementandcontainsinformationaboutthecomponent item,itsusagequantities,theusingdepartment,requirementdateandthematerialcontrol method. ThecomponentsYieldfactorfromtheBOMinflatesrequirementquantities;thesequantities serves as the default for issue transactions and determine the quantities that will be backflushed. WIP_OPERATION_RESOURCES WIP_OPERATION_RESOURCES stores information about the resource requirements associated with job and repetitive schedule operations. Each row represents a resource
Error! Use the Home tab to apply title to the text that you want to appear here. 77907483.doc Kpit Cummins Infosystems Ltd Confidential - For internal use only Main Entities in Oracle WIP 4

requirementandcontainsasequencenumber,theresourcesunitofmeasure,itsusagerateor amount,andseveralotherattributesthatcontrolhowitisscheduledandcosted.

Exercises
1. 2. Write a query that lists the requisition number, line number, item, quantity, need by date and source organization for all internal requisitions not yet converted to sales orders. Write a similar query that lists the same attributes of a requisition where the requisition line is not yet converted to a PO.

Error! Use the Home tab to apply title to the text that you want to appear here. 77907483.doc Kpit Cummins Infosystems Ltd Confidential - For internal use only

Main Entities in Oracle WIP

Key Concepts in Oracle WIP


AUTOCHARGING When the operation on routings get completed, the resources defined for that operation needs to be charged. Resource charge can be Manual or Automated. Oracle refers the automated process of charging the resources as Autocharging. BACKFLUSHING Backflushing, also known as Post Deduct, automatically issues the components used in assembly after either successful completion of the operation (Operation Pull) or successful completion of the quantity of job into inventory (Assembly Pull). The assumption is that if a certain quantity has been completed, correct components were used. COUNT POINT OPERATIONS An operation where recording of the Move from and to is desired. This flag work with the Autocharge flag to control the operation sequences and to charge the resources. INTRAOPEARTION STEPS In order to control the movement of the assembly with in an operation intraoperation steps are used in Oracle WIP. There are total five steps. Among five Queue and To Move steps are system-enabled steps when operation is defined in the Routing. Rest of the three viz. Run, Scrap, Reject are optional step and need to be enabled in WIP Parameter Form window. Queue An intraoperation step in an operation where assemblies are waiting to be worked on. The default intraoperation step for every operation in a routing. Run An intraoperation step where you move assemblies that you are working on at an operation. To Move An intraoperation step where assemblies can either be completed to a subinventory or wait to be moved to another operation. Reject Assemblies in the Reject intraoperation step of an operation have been rejected and are waiting to be repaired (reworked) or scrapped. You can move assemblies from the Reject intraoperation step to any other enabled intraoperation step in the routing. Scrap An intraoperation step where you move assemblies that cannot be reworked or completed. MOVE TRANSACTIONS Move transaction enables the movement of the assembly in process, across operation (Interoperation), within operations steps (Intraoperation), backward and forward within routings. Particularly for the long lead time items, one might want to record the progress of the job through the Routing; this is the function of the Move Transaction. Move Transactions are only allowed for jobs or schedules that uses Routing, and for such job or schedule, at least one move is required prior to completion. Moving assemblies either to any intraoperation step of next operation or to one among Run, Scrap, Reject step of the same operation complete that operation. When assemblies are completed at an operation, the system automatically backflushes operation Pull components and charge resources. You can complete assemblies from any routing operation into inventory or return completed assemblies from inventory to any routing operation from the Move Transactions window. When you move assemblies into the Queue intraoperation step of an operation that has either PO Move or PO Receipt resources assigned to it (or when the job is released, depending on your setup), the system automatically creates a purchase requisition in Oracle Purchasing. When you receive assemblies back from an outside processing supplier in Oracle Purchasing, PO Receipt or PO Move resources are automatically charged at the standard or the actual rate.
Error! Use the Home tab to apply title to the text that you want to appear here. 77907483.doc Kpit Cummins Infosystems Ltd Confidential - For internal use only Main Entities in Oracle WIP 6

Main Interfaces
Oracle Manufacturing products provide a number of open interfaces so you can link them with nonOracle applications, applications you build, applications on other computers, and even the applications of your suppliers and customers. In Oracle WIP by means of Interfaces you can import the shop floor movements, resource management and discrete jobs and Repetitive schedules.

Open Move Transaction Interface


Move transaction interface is widely used source for Oracle WIP on manufacturing shop floors. One can load the movement of the components through various production interoperation, intraoperation stages from external systems such as Bar code readers, Manufacturing Cell Controllers into the Open Move Transaction Interface. All transactions are validated and invalid transactions are marked for the corrections while rest are loaded into the Oracle WIP. The Open Move Transaction Interface enables you to perform almost all of the functions possible from Move Transaction window. Move assemblies / components between operations and intraoperation steps. Scrap Assemblies. Move and completion of assemblies in single transaction. Over complete the quantity than specified in Job or Schedule. Return assemblies from Inventory and move to an operation.

Move Transaction Manager in Oracle Inventory, which in turn launches the Move Transaction worker process, the data from the Interface tables to Oracle Applications tables. The error out transactions in validating process can be seen in Pending Move Transaction window. Following tables comprises the Open Move Transaction Interface WIP_MOVE_TXN_INTERFACE A primary interface table. Contains the information about the shop floor move transactions that needs to be processed. Load program inserts single row for each Move Transaction to be imported to the system. Each row contains the transaction date, the job or repetitive schedule in which you are moving assemblies, the primary unit of measure, the actual unit of measure transaction quantities, the foreign keys necessary for WIP to process the Move transaction as well as information about the From and To operation sequence numbers, operation codes, and intraoperation steps. The column PROCESS_PHASE and PROCESS_STATUS should have value equal to 1, which means the Move Validation phase, and Pending status to eligible for the processing. CST_COMP_SNAP_INTERFACE This table should also needs to be populated along with the above table, if the transaction is of Completion or Return type and concerned organization uses Average Costing. WIP_MOVE_TXN_INTERFACE.TRANSACTION_ID and CST_COMP_SNAP_INTERFACE.TRANSACTION_INTERFACE_ID links both the table in ParentChild relationship. WIP_TXN_INTERFACE_ERRORS If any transaction failed processing due to validation or any other errors, the transaction is populated to this table, which can be seen in Pending Move Transaction window. By means of the TRANSACTION_ID one can link this table with WIP_MOVE_TXN_INTERFACE. A single transaction can result in the creation of multiple error records. Each record contains the transaction Identifier, the message name, and the name of the column containing the error. WIP_MOVE_TRANSACTIONS This is the output table for the interface.

Error! Use the Home tab to apply title to the text that you want to appear here. 77907483.doc Kpit Cummins Infosystems Ltd Confidential - For internal use only

Main Entities in Oracle WIP

Exercises
1. Write a script that inserts data into the PDOI tables and import them as Standard Purchase Orders.

Open Resource Transaction Interface


You can use external data collection devices such as bar code readers, payroll systems, and time card entry forms to collect resource and overhead transaction data, then load the data into the Open Resource Transaction Interface for Oracle Work in Process to process. You can use this interface to perform many of the same functions that you can perform from the Resource Transactions window. For example, you can Charge labor resources Charge overhead resources Charge outside processing resources Add ad hoc resources

You must write the load program that inserts a single row for each resource transaction into the WIP_COST_TXN_INTERFACE table. The Cost Manager (CMCCTM) then groups these transaction rows and launches a Cost Worker to process each group. The Cost Worker calls the WIP Transaction Validation Engine program which validates the row, derives or defaults any additional columns, and inserts errors into the WIP_TXN_INTERFACE_ERRORS table. The Cost Worker then performs the actual resource transaction, writing the transaction to history. It allocates Repetitive resource transactions to the correct Repetitive schedules, updates operation resource balances, and deletes the successfully processed transaction row from the WIP_COST_TXN_INTERFACE table. Oracle Work in Process uses this table to support all resource cost transactions including transactions loaded from other systems through the Oracle Work in Process Open Resource Transaction Interface. The error out transactions in validating process can be seen in Pending Resource Transaction window.

Exercises
Create a standard receipt against a Purchase Order and write multiple queries that verify the data inserted/updated in each of the tables listed against individual bullet points above.

Work Order Interface


The Work Order Interface enables you to import Discrete job and Repetitive schedule header information, and Discrete job operations, material, resource, and scheduling information from any source, using a single process. You can import: Planned orders for new Discrete jobs, Discrete job operations, components, resources, resource usage, and scheduling details Update and reschedule recommendations for existing Discrete jobs, and Suggested Repetitive schedules.

Work in Process then uses this information to automatically create new Discrete jobs and pending Repetitive Schedules, or to update existing Discrete jobs. The Work Order Interface consists of two tables: the WIP_JOB_SCHEDULE_INTERFACE table (Open Job and Schedule Interface table), and the WIP_JOB_DTLS_INTERFACE table (WIP Job Details Interface table). You load header information into the WIP_JOB_SCHEDULE_INTERFACE table, and operations, components, resources, and scheduling information into the WIP_JOB_DTLS_INTERFACE table. When you insert records into the Work Order Interface, you load header information into the WIP_JOB_SCHEDULE_INTERFACE table, and operations, components, resources, resource usage, and scheduling information into the WIP_JOB_DTLS_INTERFACE table. You then use the Import Jobs and Schedules window to launch the WIP Mass Load (WICMLX) concurrent program, which validates records in the Work Order Interface table and imports them into Work in Process. The WIP Mass Load program validates all required and optional data. If the required or optional data that you enter are invalid, or if required data are missing, the program updates the PROCESS_STATUS
Error! Use the Home tab to apply title to the text that you want to appear here. 77907483.doc Kpit Cummins Infosystems Ltd Confidential - For internal use only Main Entities in Oracle WIP 8

for the record to 3 (Error), and an error message tied to the row's interface ID is inserted into the WIP_INTERFACE_ERRORS table. Unsuccessfully processed rows that have a PROCESS_STATUS of 3 (Error) can be viewed, updated, deleted, or resubmitted using the Pending Jobs and Schedules window.

Exercises
Create a standard receipt against a Purchase Order and write multiple queries that verify the data inserted/updated in each of the tables listed against individual bullet points above.

Error! Use the Home tab to apply title to the text that you want to appear here. 77907483.doc Kpit Cummins Infosystems Ltd Confidential - For internal use only

Main Entities in Oracle WIP

Major Processes
Following are the few important processes in Oracle WIP described in brief. The users guide and Oracle Manufacturing APIs and Open Interfaces manual is a good source for information on them.

Intermediate Shipment
Overview This built in workflow notify the potential buyer that intermediate assemblies are ready for the outside processing and then it tracks them from shop floor to shipment dock and then to supplier. Successful completion of this process in turn calls the Ship and Receive Intermediate workflow. The workflow is activated when you move assemblies into the Queue intraoperation step of an Outside Processing operation that has a PO Move resource charge type or if the outside processing operation is the first operation. Flow It first imports the pending purchase requisitions by running the concurrent program Requisition Import. Then it finds out how many approved PO exists for the specific outside processing supplier. Process then tries to fix the default buyer for the outside processing item, if that is not found then it tries to locate the production scheduler for the same. If both are not found then process ends here. If default buyer or production scheduler is found then process notify it the status of the approved PO waiting for the outside processing.

Ship and Receive Intermediate workflow


Overview After the successful completion of Intermediate Shipment workflow (The intermediate is approved by the Buyer for the outside processing) this process notify the Shipping Manager and the Supplier that outside processing assemblies are ready for the Shipment. Flow The workflow first searches for the shipping manager, and if found then searches for the suppliers shipping address. It then notifies the shipping manager that the assemblies are ready to ship and relays the shipping address. If the shipping manager decides to proceed with the shipment, the system searches for the supplier contact. If a contact is found, he or she is notified that the assemblies have been shipped else if the supplier contact is not found, the buyer is then notified. If intermediates are received, this function activity sends a notification to the buyer.

Error! Use the Home tab to apply title to the text that you want to appear here. 77907483.doc Kpit Cummins Infosystems Ltd Confidential - For internal use only

Main Entities in Oracle WIP

10

Other important tables in this module


WIP_PARAMETERS A master table, which stores the Inventory Organization, level basic rules and defaults. Each row represents the settings for an entire organization and contains default General Ledger accounts for cost elements, scheduling methods, cost accounting methods, and material control defaults. The Work in Process Parameters window populates the data in this table. WIP_ACCOUNTING_CLASSES A Master table, which stores the data of group of GL accounts that are used for the valuation and variance reporting for different types of production. The CLASS_TYPE column uniquely identifies each class. Oracle Work in Process uses this information to create the journal entries that post cost transactions. WIP Accounting Classes window populates the data in this table. WIP_PERIOD_BALANCES WIP_PERIOD_BALANCES stores summary accounting information for jobs and schedules. Each row represents job or schedule charges within a given accounting period, and contains the summary values for each cost element. WIP_SHOP_FLOOR_STATUSES Shop floor statuses are meant for the extra control over the job or schedule during the execution at shop floor. WIP_SHOP_FLOOR_STATUSES stores the status codes that you assign to a discrete job or repetitive schedule. Each row contains the operation sequence number and intraoperation step to which you assign the status.

Error! Use the Home tab to apply title to the text that you want to appear here. 77907483.doc Kpit Cummins Infosystems Ltd Confidential - For internal use only

Main Entities in Oracle WIP

11

Important Profile Options


WIP: Discrete Job Prefix Indicates a prefix that will be used with the system-generated number that identifies a job, called the job name. WIP: Job Name Updatable This profile determines whether you can change the job name after you create the job. WIP: Requirement Nettable Option This profile control whether one can issue the component from all sub-inventories where it is available or only from the Sub-inventory which is identified ad Nettable. View only Nettable Subinventories allows only nettable subinventory to appear in View Material Requirement Window for on-hand quantities query. View all Subinventories will include all the Subinventories. WIP: Move Completion Default This Profile will determine whether the move to the To Move step of the last operation for a job will automatically attempt to complete the Quantity into Inventory or not. If Yes then it complete the transaction at the To Move stage of the last operation. WIP: Enable Outside Processing Workflows Determines whether or not outside processing Workflows are enabled. Yes enables the outside processing Workflows while No will not allow them for the processing.

Error! Use the Home tab to apply title to the text that you want to appear here. 77907483.doc Kpit Cummins Infosystems Ltd Confidential - For internal use only

Main Entities in Oracle WIP

12

Vous aimerez peut-être aussi