Manufacturing Mobile Best Practices

To take advantage of all the Manufacturing Mobile SuiteApp features, it is a good practice to review the suggested best practices:

Manufacturing Preferences

  • To help avoid potential build failure, enable the Manufacturing Preferences Allow Overage on Work Order Transactions to set the Manufacturing Issue Based on Commitment to Limit to Committed.

  • Manufacturing Mobile does not support component commitment functionality.

Manufacturing Mobile Preference Settings

Before Creating a Manufacturing Mobile Work Order, make sure you configure Manufacturing Mobile Preferences at an account level.

Trigger Builds

  • You should Trigger Builds based on how often data needs to be pushed to NetSuite.

  • By default, the Real Time Build box is checked and enabled for all types of work orders.

    You can disable the real time build feature while Creating a Manufacturing Mobile Work Order.

    Note:

    To report data through Manufacturing Mobile, do not clear the Real Time Build box.

  • To disable default real time build for all work orders create or all work orders created from sales orders, review Manufacturing Mobile Preferences.

Backflush Work Orders

  • While Creating a Manufacturing Mobile Work Order, you can automatically consume all work order components at the standard BOM quantities by checking the Backflush box.

    • You can enable backflush with or without real time build and WIP work orders.

    • After you check this box, you can only report production, not consumption, in the mobile scanner.

  • Backflush occurs at a work order level, not at a component level.

    If there are any serial controlled components, you cannot enable backflush.

  • To avoid build failures when you enable backflush, ensure that there is sufficient component quantity available in the staging bin when you report production quantity. .

For more information, see the following topics:

Report Data

  • To review common reporting and correcting scenarios, read the Manufacturing Mobile Work Messages topic.

  • To make sure that you enter the correct finished goods costing, report consumption before you report production for non-WIP work orders.

Default Work Order Location and Work Center

To assign a default work order location and work center, define at least one static employee group. For more information, see the following topics:

Over-pick Work Orders

Performance Limitations

  • Backflush Component Limit: When you backflush more than 100 components for Work in Progress (WIP) or non-WIP orders, the MapReduce script may time out, causing the build to fail. To prevent this issue, it is advisable to limit the number of backflush components to 100 or fewer.

  • Material Consumption and Production Reporting Record Limit: When working with real-time orders, submitting a large number of material consumption or production reporting records at one time may impact the build generation process. If you submit more than 200 records at one time, the build might fail or does not generate correctly. To prevent this issue, you must submit your work periodically using the Submit Work button.

    This approach allows the records to be processed in smaller, more manageable batches and this enhances the accuracy and reliability of the build process.

Mobile Customizations

Before you can enable a no-code solution supported by the SCM Mobile framework, set a maximum number of line items for a no-code solution. For more information, see

Mobile Device Requirements and Customizations.

Related Topics

General Notices