Integrating with Microsoft Dynamics 365 Business Central

Output and consumption postings

Output and consumption postings can be seen as information about the progress of your production execution

When you post output or consumption on your production order line you basically tell your system that you started or finished an operation or that you have achieved a certain percentage of completion.

Fundamentals on output/consumption postings:

  • Output/consumption postings can happen very often, sometimes, even automatically
  • They reflect a constant data updating process
  • No impact on an existing simulation:
    • The simulation doesn't get outdated
    • The simulation doesn't get invalid
    • The progress information you see in the visual schedule is about the moment in time when you created your simulation.
    • After posting output/consumption you have to create a new simulation

The impact of the production order status

  • You can only post output and consumption to a released production order
  • Any output/consumption posting on a released production order results in showing a progress bar in the VAPS

Visualization of progress information in the VAPS

For production order routing lines of released production orders a slim progress bar is displayed below the actual bar being based on the posted quantity consumption. The color of the progress bar appears as follows: 

  • finished: black

         VPS_progress_bar_finished

  • still in progress and output/consumption <=  originally planned quantity: grey

           VPS_progress_bar_grey

  • still in progress and output/consumption > originally planned quantity: red

        VPS_progress_bar_grey

Please note, that

  • you can only post output and consumption to a released production order
  • 0perations that are already in progress, cannot be moved any more
  • the percentage of completion is shown in relation to the net working time.

Special case: Posting on an operation that is still on the standby resource

This is an absolutely rare case that normally should not happen, but you need to be aware of it.

Important to know

  • If you post output/consumption on an operation that is still on the standby resource, this operation gets automatically moved to the machine center that is specified in the routing because if an operation is started (what the posting actually means) it de facto cannot be on the standby resource any longer.
  • If there already is another operation on this specific machine, this could actually result in an overload which the planner has to fix manually.