You are on page 1of 2

Issuing material to a job creates a material transaction Completing an assembly at an operation creates a move and possibly a backflush t ransaction

Finishing an assembly creates a completion into inventory and possibly a backflu sh transaction issue and return components to and from jobs and schedules on the production flo or: Material issue transactions fulfill work in process requirements for jobs or sch edules Intraoperation Steps Queue: Assemblies in this step are waiting for work to be performed. Queue is th e default intraoperation step for every operation in a routing. Run: Assemblies in this step are ready to be worked on. You can move assemblies from the Run step to any other enabled intraoperation step in the routing. To Move: Assemblies in this step have been completed and are waiting to be moved to the next operation. Moving and Completing Operations Move Moves assemblies within and between routing operations. You can move assemb lies forward or backward. Complete Completes assemblies from any routing operation and intraoperation step into inventory. Assembly move completions move assemblies from the current operation, to the To Move intraoperation step of the last operation, then comple te them into inventory. Assemblies are completed into the default completion subinventory and locator specified for the job or schedule. Where applicable, mo ve completion transactions also charge move based resources and overheads, and create backflush transactions for components with supply types of Assembly and Component Pull. Return Returns assemblies from inventory to any routing operation and intraopera tion step. Assembly move returns first return assemblies from the job completion subinventory, to the To Move intraoperation step of the last operatio n, then move them into the operation and intraoperation step you specify. Where applicable, move return transactions also create transactions that reverse charges to move based resources, and reverse backflush transactions for compone nts.

Completing Assemblies An assembly completion transaction is a material transaction where you receive a ssemblies into inventory from a job or schedule when manufacturing is finished: All assembly pull material designated on the bill of material is backflushed. The quantity in the To Move step of the last operation is decreased if there is a routing. The Quantity Complete field on the job is increased. If the quantity completed equals the start quantity for a discrete job, the job status is changed to Complete. Returning Assemblies An assembly return transaction is moving it back from inventory to work in proce ss: All backflush transactions that took place during the corresponding completion t ransaction are reversed. The Quantity Complete field is reduced. The quantity in the To Move step of the last operation in the routing is increas

ed if there is a routing. The job s status is changed back to Released. Backflushing Components During Moves You can initiate a backflush from several sources, including manual issue transa ctions and automatic transactions when moving or completing assemblies. Backflus h transactions occur for operation pull and assembly pull supply types: Operation Pull - Move transactions that complete an operation backflush all components with a s upply type of operation pull. - The backflush occurs only at routing operations with a backflush type of Yes. The backflush transaction backflushes all operation pull components at all appro priate previous operations in the routing. - Components with a supply type of operation pull defined for an operation with a backflush type of No, are backflushed after completing an operation with a bac kflush type of Yes later in the routing. Assembly Pull WIP completion transactions backflush all components with a supply type of assembly pull. Performing Move Transactions For move transactions, you choose either a sales order, repetitive line, assembl y, or job record and then select information in the following fields: Move Transaction Type From and To operation Sequence numbers From and To operation Step You can select any operation on the routing including preceding operations. If you move assemblies within an operation (intraoperatio n), the To operation sequence must be the same as the From operation sequence. For example, you can move assemblies from the Queue to Reject intraoperation step of the same operation. Count Point The system defaults the To operation sequence as the next count poin t operation. For example, you have three operations at sequences 10, 20, and 30 defined as count point, non-count point, and count point respectively. When you select operation 10 as the From operation, the system automatically defaults operation 30, the next count point operation, as the To operation. You can over ride this default and choose operation 20, if required. If