Process Orders for JOP Extension for Microsoft Dynamics 365 Business Central

Process Order Header

FastTab: General

This FastTab includes basic identifiers and structural data for the process order:

• No. — Unique identifier of the process order, based on a number series.

  The number series used for generating Process Order numbers can be defined either:

  • Globally in the JOP Setup
  • Individually in the Responsibility Center

  If both are configured, the setting in the Responsibility Center takes precedence. This allows for center-specific numbering when managing multiple production sites.

• Description — Optional descriptive label for the process order.
• No. of Items — Quantity of physical items to be processed. This may influence scheduling and capacity planning.
• Routing No. — Reference to the selected routing that defines the sequence of work steps.
• Routing Version Code — Specifies the version of the routing used for this order.
• Rework — Indicates if the process order is part of a rework flow rather than standard production.
• Status — Lifecycle state of the process order (e.g., Planned, Planned, Released, Finished).

  The initial status of a newly created Process Order is determined by the configuration in the Responsibility Center. This allows different plants to define their preferred workflow stage—such as Planned, Firm Planned, or Released—for newly generated process orders.

• Process Folder No. — If this process order is part of a grouped production batch, this field links it to the corresponding Process Folder.

FastTab: Order Data

This FastTab captures the customer and sales context that triggered the creation of the process order:

• Order Date — Date when the originating sales order was created.
• Order No. — Sales Order number that this process order is linked to.
• Responsibility Center — Operational unit or plant responsible for executing the process order.
• Production Department — Specific department or section within the plant.
• Customer No. — Customer from the original sales order.
• Customer Name — Display name of the customer for visibility and filtering.
• Customer Group Code — Grouping key for customer classification and rule logic.
• JOP Item No. — Reference to the JOP Item that served as the blueprint for this process order.
• Service Code — Code identifying the service to be performed (e.g., coating, hardening).
• Service Group Code — Higher-level classification of the service.
• Product Code — Indicates which product is being processed.
• Product Group Code — Used for grouping logic and pricing rules.
• Material Code — Specifies the material used for the product.
• Material Group Code — Material category for grouping and property rules.

Process Order Lines

Each process order line represents a specific work step within the production sequence. The following fields are available to define operational, technical, and formatting aspects of each step:

• Operation Code — Identifies the step in the routing or work process.
• Method Code — Specifies the technique or method to be applied during this operation.
• Description — Descriptive text for the work step.
• Confirmation — Indicates that confirmation is required before progressing to the next step.
• Optional Confirmation — If enabled, the step may be optionally confirmed without blocking process flow.
• Batch Operation — Marks the step as batch-related, i.e. several items are processed together.
• Batch Assigned — Indicates whether the step is already assigned to a specific batch execution.
• Finish — Identifies the final step of the process order; triggers output registration and completion logic.

  Important: Exactly one line in the process order must have Finish = Yes. This marks the final step of the process and is required to complete the order properly.

• Test Plan Mandatory — Indicates that a test plan must be executed before the step can be completed.
• Test Plan Template No. — Reference to the predefined test plan to be used during this step.
• Process Time — Expected duration of the operation (in minutes, hours, etc.).
• Minimum Process Time — Lower time boundary for quality tracking or performance evaluation.
• Maximum Process Time — Upper time boundary for acceptable execution of the step.
• Print Date/Signature — Specifies whether the step should print date/signature fields for documentation.
• Sales Factor — Fraction used to allocate sales revenue to this operation. Useful in multi-machine processes. The sum of all sales factors in a process order should equal 1.0.
• Bold, Italic, Underline — Formatting options for how the operation is presented in printed documents.
• New Page — If checked, this step will start on a new page in print outputs (e.g., process order sheets).
• Planned Division Code — Indicates the internal division where the step is to be executed.
• Planned Machine Group Code — Identifies the target machine group for scheduling or reporting.
• Planned Machine Code — Indicates the specific machine assigned to the task.

Actions in the Process Order page

The JOP extension adds several header-level and line-level actions to the Process Order page in order to manage execution, tracking, and reporting more effectively.

Header Actions

• Split Proposal — Suggests a distribution of the process order into smaller units, based on lot size or routing logic, to support optimal workload distribution or batch creation.
• JOP Entries — Displays process-related entries for the order, including outcome quantities (e.g., good, scrap, non-conforming).
• Quarantine Entries — Lists items flagged during the process as non-conforming and transferred to quarantine for further action.
• Process Output Entries — Shows detailed results recorded when the Finish step is executed. Includes:
  • Process Order No.
  • Batch No. (if batch-related)
  • Outcome Type — Good, Scrap, or Non-Conformance
  • Non-Conformance Code
  • Extra Cost Code — Contains issue type, responsible department, suggested actions, and defect source
• Print — Opens the print dialog for generating the process sheet.

Line Actions

• Post Operation — Confirms the completion of the current operation. This action is used to record output and advance processing.
  It can only be executed for operations that are not assigned to a batch. For batch operations, confirmation must be done through the corresponding batch.
• Create Batch

  The Create Batch action is used to group multiple process orders or process order lines into a single batch for operations that are performed collectively, such as heat treatment or coating..

  This function is especially relevant when the process step is marked as a Batch Operation. Instead of handling and confirming each item individually, the system allows you to create a batch that represents a shared operation context — such as a furnace load or coating chamber cycle.

  Once the batch is created:

  • Each related process order line is linked to the batch.
  • Confirmation and reporting can be performed at the batch level.
  • All entries (e.g., Process Output, Inspection Certificates) will be generated collectively for the batch.

  This approach improves efficiency, ensures consistency, and provides clear traceability for grouped processing steps. It is particularly useful in environments where multiple items are treated identically in a single machine or production cycle.

  Note: Only operations marked with Batch Operation = Yes are eligible for batching.

• Create Rework Process Order — Generates a new process order to rework items that failed inspection or require corrections.
• Batches — Opens a list of batches associated with the selected operation. Includes processing status and traceability data.