Understanding Work Order and Rate Schedule Processing

After you enter a work order header, you can use the Order Processing batch program (R31410) to attach the parts list and routing instructions for each work order or rate schedule header. If you attach the parts list and routing instructions interactively, you can use the Order Processing batch program to generate and print the shop paperwork.

The processing options for the Order Processing program enable you to perform a wide range of functions, such as:

  • Generate a parts list and routing instructions.

  • Indicate the date to use for effectivity verification.

  • Change the status code of the work orders or rate schedules that are being processed.

  • Print information about the work order or rate schedule, such as the routing, parts list, sales order text, and so on.

  • Print a shop packet summary that lists processed work orders and rate schedules.

  • Enter the unit of measure for backscheduling.

  • Issue inventory automatically.

  • Generate a shortage report for the work orders and rate schedules.

  • Indicate the versions of the associated programs that you want to access.

  • Create parts lists based on previous revision levels.

You can organize and separate these functions to accomplish different tasks by setting up several reporting versions, each with different data selections and processing option values. For example, you can set up one version to generate the parts lists and routings for work orders, another version to print shop paperwork, and another version to perform batch inventory issues.

If you use other JD Edwards EnterpriseOne systems, these integration features apply:

System

Features

Configured items integration

You use the Order Processing program to retrieve the parts lists from the Configurator Component table (F3215) and the routings from the Configurator Routings table (F3212) in order to generate the work order parts list and routing instructions. When an item is configured at order entry, the assembly inclusion rules run and the resulting parts list and routing information is stored in the tables.

The assembly inclusion rules are defined in the JD Edwards EnterpriseOne Configurator system. The P assembly inclusion rule is used to put component parts on the sales order and work order, while the Q assembly inclusion rule is used to put component parts on the work order only. The R assembly inclusion rule is used to create the routing instructions for the work order.

When a sales order is entered for a configured item, the P assembly inclusion rules may print components as separate line items on the sales order based on the setup of the assembly inclusion rules.

Running the Order Processing program generates a parts list for a configured item by using data from the Configurator Component table (F3215) to create records in the Work Order Parts List table (F3111). The F3215 records are generated when processing P and Q assembly inclusion rules in the Configured Item Revisions program (P3210) during order entry.

The system also generates a routing by using data from the Configurator Routings table (F3212) that is generated from the R assembly inclusion rules run at order entry.

The system uses the Issue Type (issue type code) and Operation Seq No. (operation sequence number) fields from the Assembly Inclusions Rules table (F3293).

JD Edwards EnterpriseOne Quality Management integration

When you process work orders, you can use processing options to set values for the status of the work order and operation lot if the components fail tests.

JD Edwards EnterpriseOne Engineer to Order integration

Transactions processing is affected by the JD Edwards EnterpriseOne Engineer to Order (ETO) system. Work orders may be locked by a project that is being processed.

When you select the Edit Tasks mode in the Project Workbench, the system places record reservation only on records that you have modified.

When you select the Edit And Lock All Tasks mode, all orders in the project are reserved by the project. All records are locked and other applications or programs will not be able to access them until you exit this mode.

When working on a project in JD Edwards EnterpriseOne ETO, the system does not let you edit a record that has been locked by a different user or application.

See "Understanding Projects" in the JD Edwards EnterpriseOne Applications Engineer to Order Implementation Guide.

JD Edwards EnterpriseOne Sales Order Management integration

When you create a work order for a kit during sales order entry, the system can build the parent item and stock it in inventory after you process and complete the work order. When you create the work order, the system subtracts the components from the on-hand quantity in inventory. After you complete the work order, the system adds the parent item to the on-hand quantity in inventory.

You must specify line type T (Text) for sales orders in the Order Processing program to avoid writing journal entries for cost of goods sold and inventory for the components when you update the sales order. This line type also ensures that the system does not again subtract components from on-hand quantity in inventory during shipment confirmation or sales update.

JD Edwards EnterpriseOne Warehouse Management integration

If you use JD Edwards EnterpriseOne Warehouse Management, when you process a work order, the system does not search for inventory. Instead, the system generates a pick request. The pick request notifies you of the need for materials from the warehouse.

After the system creates the pick request, JD Edwards EnterpriseOne Warehouse Management processes instructions and creates suggestions for you to confirm. Then, the system updates the parts list and increases the on-hand quantity for the To location and decreases the quantity on-hand for the From location.

You can specify in the processing options whether you want to print a consolidated pick list for multiple work orders, or individual pick lists for each work order.