Skip to main content
2023-R2Manufacturing

Manufacturing: DeviceHub Support for the Print Production Orders Form

Last updated: 31 October 2025

Manufacturing: DeviceHub Support for the Print Production Orders Form

Manufacturing: DeviceHub Support for the Print Production Orders Form

In previous versions of MYOB Acumatica Manufacturing Edition, the ability to automate production order printing was limited and inconsistent with the printing capabilities for other processing forms in MYOB Acumatica; also, this functionality did not use the DeviceHub feature.

In MYOB Acumatica Manufacturing Edition 2024.1.1, additional UI elements have been added to the Print Production Orders (AM511000) form to support the ability to print production order tickets by using automated schedules. These elements are visible after the system administrator enables the DeviceHub feature on the Enable/Disable Features (CS100000) form.

DeviceHub Settings for Manufacturing

In MYOB Acumatica Manufacturing Edition 2024.1.1, before the new DeviceHub UI elements can be used on the Print Production Orders (AM511000) form, the DeviceHub application must be installed.

The DeviceHub feature should also be enabled on the Enable/Disable Features (CS100000) form (see the following screenshot).

Figure 1. The enabled DeviceHub feature on the Enable/Disable Features form

Use of the New DeviceHub Elements on the Print Production Orders Form

To support the automation of printing production orders, in MYOB Acumatica Manufacturing Edition 2024.1.1, the following elements have been added to the Print Production Orders (AM511000) form (see the following screenshot):

  • The Print with DeviceHub check box
  • The Define Printer Manually check box
  • The Printer box
  • The Number of Copies box

Figure 2. The new UI elements on the Print Production Orders form

Now a user can select the Print with DeviceHub check box if they want to print with DeviceHub. With this check box selected, DeviceHub prepares the production order ticket to be printed and prints it automatically.

The user can also manually specify the printer to be used by selecting the Define Printer Manually check box and then selecting the printer in the Printer box. If the Define Printer Manually check box is cleared, the system inserts into the Printer box the default printer specified on the User Profile (SM203010) form for this user. If a printer is not specified on the User Profile form for this user, then the user must select the Define Printer Manually check box on the Print Production Orders form and specify the printer. Also, the user can specify the number of copies to be printed in the Number of Copies box.

Automation of the Printing of Production Orders

In MYOB Acumatica Manufacturing Edition 2024.1.1, to support the printing of production orders by using an automation schedule, the system administrator can create an automation schedule on the Automation Schedules (SM205020) form. On this form, the administrator can do the following:

  • Select Print Production Orders in the Screen ID box to print production orders (see Item 1 in the following screenshot)
  • In the row with Print with DeviceHub specified in the Field Name column, select the Value check box to print with DeviceHub (Item 2)
  • In the row with Define Printer Manually specified in the Field Name column, select the Value check box to define the printer manually on the Print Production Orders (AM511000) form (Item 2)
  • In the row with Number of Copies specified in the Field Name column, specify the number of the copies to be printed in the Value box (Item 2)
  • In the row with Printer specified in the Field Name column, specify the printer to be used in the Value column (Item 2)

Figure 3. An automation schedule for printing production orders on the Automation Schedules form

Once the schedule has been created, the printing of production orders will be processed automatically, and the printing task will be sent to the specified printer.

Additional Information

For details on DeviceHub, see ../UserGuide/IS__how_Connect_DeviceHub.html.