Documentos de Académico
Documentos de Profesional
Documentos de Cultura
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
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
EXTERNAL SYSTEM
WIP_ENTITIES
WIP_DISCRETE _JOBS
WIP_OPERATIONS
WIP_REQUIREMENT _OPERATIONS
WIP_OPERATION_ RESOURCES
DISCRETE WORKSTATION
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
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 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.
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
Exercises
1. Write a script that inserts data into the PDOI tables and import them as Standard Purchase Orders.
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 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
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.
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
10
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
11
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
12