Streamline Order Processing: Review Workflow for Firm Orders in Dynamics 365 Supply Chain Management

Table of Contents

Efficient order processing is the backbone of a successful supply chain operation, directly impacting customer satisfaction, inventory management, and overall operational costs. Within Dynamics 365 Supply Chain Management (D365 SCM), workflows are critical automation tools designed to manage the lifecycle of various business documents, including purchase orders, sales orders, and production orders. These automated processes ensure that transactions move smoothly through predefined stages, incorporating necessary approvals and reviews.

A well-configured workflow streamlines operations, reduces manual effort, and enforces compliance with organizational policies. However, when these workflows encounter issues, they can quickly become bottlenecks, leading to significant disruptions. Understanding and effectively managing these workflows is paramount for maintaining optimal supply chain performance.

Understanding Firmed Orders in Dynamics 365 Supply Chain Management¶

Firmed orders are a fundamental concept in D365 SCM, originating primarily from the master planning process. Master planning generates “planned orders” based on demand forecasts, current inventory, and production capacities. These planned orders are essentially suggestions for future purchases, production, or transfers.

When a planned order is deemed necessary and ready for execution, it is firmed. Firmed orders are concrete documents – they become actual purchase orders, production orders, or transfer orders that will proceed through the supply chain. This transition is a critical step, as it converts a mere suggestion into a firm commitment that consumes resources and schedules activities.

The accuracy and timely processing of firmed orders are vital. Delays at this stage can ripple throughout the entire supply chain, impacting raw material procurement, production schedules, delivery commitments, and ultimately, customer satisfaction. Therefore, ensuring that firmed orders move through their lifecycle efficiently is a top priority for any organization utilizing D365 SCM.

The Challenge: Firmed Orders Stuck in “In-review” Workflow Status¶

A common operational hurdle encountered in D365 SCM involves directly derived firmed orders becoming stuck in an “In-review” status within their associated workflow. This particular symptom indicates that while the system has recognized the need for and created the firmed order, its progression is halted, awaiting an action that is not being completed. The phrase “directly derived firmed orders” often refers to orders generated automatically by master planning or through direct user action, which are then subject to an approval workflow.

This state is problematic because an “In-review” status typically means the order requires an approval or a specific action from a designated participant to proceed. Without this action, the order remains in limbo, unable to be processed further, confirmed, or released for subsequent supply chain activities. This stagnation can lead to a cascade of negative consequences throughout the business.

Symptoms and Impact¶

The primary symptom is clear: when users check the status of firmed purchase, production, or transfer orders, they find them consistently marked as “In-review.” Despite the passage of time, these orders do not progress to statuses like “Approved,” “Confirmed,” or “Completed.” This can be observed directly on the order details page or through workflow history tracking.

The impact of such a bottleneck can be severe and far-reaching. Production lines might halt due to missing components that are tied to these unapproved purchase orders, leading to missed production targets and idle resources. Customer delivery dates could be jeopardized if sales orders cannot be fulfilled because associated production or transfer orders are pending review. Financially, this can translate into increased operational costs due to delays, potential penalties for missed supplier payments, and lost revenue from unfulfilled sales. Moreover, a persistent workflow issue erodes user trust in the system and can lead to frustration and decreased productivity among staff.

Root Causes of Workflow Stagnation¶

Identifying the precise root cause of firmed orders getting stuck in an “In-review” workflow status requires a systematic investigation. Several factors, alone or in combination, can contribute to this problem:

• Misconfigured Workflow Settings: The most frequent culprit is often an incorrectly set up workflow. This can include flawed approval conditions, an incorrectly defined approval hierarchy, or automatic actions that fail due to missing parameters. Workflow conditions might evaluate incorrectly, preventing the next step from being triggered, or a required approval step might be inadvertently skipped or set up to never resolve.

• Missing or Incorrect Approvers: Workflows rely on specific users or user groups to perform review and approval actions. If the designated approvers are incorrect, inactive, or lack the necessary security permissions, the workflow will stall. This could involve an approver who no longer works for the company, a user who hasn’t been assigned the correct role, or a participant group that is empty.

• System Integration Issues: In environments where D365 SCM integrates with other systems (e.g., for supplier portals, external planning tools, or financial systems), data synchronization problems can prevent workflow progression. If essential data required for a workflow decision is not correctly updated or transferred, the workflow might pause indefinitely. Errors in integration batch jobs or API calls can also contribute to this.

• Performance Bottlenecks: While less common for an “In-review” status, underlying system performance issues can sometimes contribute to workflow processing delays. Batch jobs responsible for evaluating workflow conditions and moving items through stages might be running slowly or failing. Heavy system load, database contention, or insufficient server resources can also impact workflow responsiveness.

• Customizations and Extensions: Organizations often implement custom code or third-party extensions to tailor D365 SCM to their specific needs. These customizations can sometimes introduce bugs or conflicts that interfere with standard workflow functionality. A recent deployment or update of a custom solution might inadvertently break existing workflow logic.

• Data Inconsistencies: The data associated with the firmed order itself can cause issues. For example, if a vendor account is inactive, an item is no longer valid, or critical fields are missing, the workflow might encounter an error when trying to process a step that relies on this data. These inconsistencies can prevent conditions from being met or actions from executing.

• Environmental Issues: Less frequently, broader environmental issues such as server instability, network problems, or unapplied D365 SCM service updates can subtly impact workflow reliability. Keeping D365 SCM up-to-date with the latest Microsoft updates and hotfixes is crucial for overall system stability, including workflow functionality.

Comprehensive Resolution Strategies¶

Resolving firmed orders stuck in an “In-review” status requires a methodical approach, starting with diagnosis and moving through potential solutions based on the identified root cause. The following steps provide a structured framework for troubleshooting and resolution.

Step 1: Diagnosing the Workflow Instance¶

The first step is to precisely pinpoint where and why the specific order’s workflow is stalled.

• Accessing Workflow History: Navigate to the firmed order in D365 SCM (e.g., Purchase Order details). On the “Header” or “Workflow” tab, locate the “Workflow history” or “View history” option. This provides a visual representation of the workflow’s path, showing each step, its status, and any associated messages or errors.
• Identifying the Stalled Step: The history log will typically highlight the exact step where the workflow is currently “In-review” or awaiting action. Pay close attention to the participant assigned to that step and any accompanying status messages or error descriptions.
• Checking Audit Trails and Error Messages: Detailed audit trails within the workflow history can reveal why a step failed or why an action wasn’t taken. Look for red exclamation marks or warning icons, which often indicate an underlying system error, a failed condition, or a missing approver. These messages are critical clues for subsequent troubleshooting.

Step 2: Reviewing Workflow Configuration¶

Once the stalled step is identified, the next logical step is to examine the configuration of the workflow template itself.

• Navigating to Workflow Settings: Go to System administration > Workflows > Organization workflows (or Module specific workflows like Procurement and sourcing > Setup > Procurement and sourcing workflows for purchase orders). Open the active version of the workflow relevant to the firmed order type (e.g., Purchase Order workflow).
• Examining Approval Steps and Conditions: Carefully review the properties of the specific approval step that is stuck. Verify the conditions configured for that step. Are they logical? Are they based on correct fields and values? Test these conditions manually with the data from the problematic order to ensure they evaluate as expected.
• Ensuring Correct Participant Assignments: Check the “Assignment” tab for the stalled step. Confirm that the assignment type (e.g., User, Role, Hierarchical, Participant) is correct and that the assigned user(s) or group(s) are valid and active. If using an organizational hierarchy, ensure the hierarchy is correctly defined and the users within it are active and possess the required permissions.

Step 3: Verifying User and Role Permissions¶

A common reason for workflows getting stuck “In-review” is that the assigned approver either doesn’t have the necessary security roles or their user account is inactive.

• Confirming Security Roles: For the user(s) identified as the approver(s) in the workflow configuration, navigate to System administration > Users > Users. Select the user and review their assigned security roles. The user must have a security role that grants them permissions to approve documents of that type (e.g., “Purchase order workflow approver” or a custom role with equivalent privileges).
• Checking User Assignments to Workflow Groups: If the workflow assigns tasks to a workflow user group, ensure that the problematic approver is correctly added to that group (System administration > Users > Workflow user groups).
• Ensuring Active User Accounts: Confirm that the approver’s user account in D365 SCM is active and not disabled or expired. An inactive user cannot perform workflow actions.

Step 4: Monitoring System Performance and Batch Jobs¶

Workflows rely on specific batch jobs to process messages and manage their lifecycle. Issues with these jobs can indirectly lead to items being stuck.

• Importance of Workflow Batch Jobs: The Workflow message processing batch job is crucial for evaluating workflow conditions and moving tasks through stages. The Workflow clean-up batch job removes completed or erroneous workflow instances but can sometimes become overloaded.
• Checking Batch Job Status and Recurrence: Navigate to System administration > Inquiries > Batch jobs. Search for “Workflow message processing” and “Workflow clean-up.” Verify that these jobs are running at appropriate intervals, are not in an Error or Withhold status, and have a Recurrence that aligns with operational needs. If these jobs are failing, investigate their execution history for error details.
• Analyzing System Logs: While less direct, reviewing general system event logs or D365 SCM trace logs (if available and configured) can sometimes reveal underlying system issues impacting workflow execution.

Step 5: Addressing Customizations and Integrations¶

If customizations are present, they should be investigated as potential sources of conflict.

• Reviewing Recent Changes: If the issue started after a recent code deployment, D365 SCM update, or implementation of a new feature, focus troubleshooting efforts on those changes.
• Disabling Customizations for Testing (in a non-production environment): In a safe test environment, temporarily disable any recent customizations related to the firmed order processing or workflow. If the workflow then functions correctly, the customization is likely the cause, requiring debugging and correction.
• Checking Integration Logs: For firmed orders that involve external systems, review the integration logs of both D365 SCM and the external system. Look for errors related to data transfer or status updates that might prevent the workflow from progressing.

Step 6: Data Integrity Checks¶

Corrupt or incomplete data on the firmed order itself or related master data can also cause workflow failures.

• Validating Master Data: Ensure that all master data referenced by the firmed order (e.g., vendor accounts, item numbers, dimensions, financial dimensions) is active, valid, and correctly configured.
• Ensuring Completeness of Order Data: Verify that all mandatory fields on the firmed order are populated and that the data is consistent. Sometimes, a missing value in a field used in a workflow condition can cause the condition to evaluate incorrectly.

Step 7: Manual Intervention (with caution)¶

While not a long-term solution, manual intervention can unblock critical orders in an emergency.

• Recalling Workflow: If an order is stuck and the approver is known, they can sometimes “Recall” the workflow. This action returns the document to its original state (e.g., Draft) and allows the originator to resubmit it, potentially pushing it through a corrected workflow path.
• Force Approving (Admin only): System administrators, or users with elevated privileges, can sometimes force approve or force complete a workflow step from the workflow history. This should be done with extreme caution and only as a temporary measure for critical business continuity. It bypasses the established approval process and should be accompanied by an immediate investigation into the root cause to prevent recurrence.

Step 8: Escalation to Microsoft Support¶

If, after thorough investigation, the issue persists and a solution cannot be identified internally, it may be necessary to escalate the problem to Microsoft Support.

• When to Escalate: Consider escalation when internal expertise is exhausted, the problem is complex, or it appears to be a core product bug.
• Information to Provide: When contacting support, provide comprehensive details: the exact KB number (if related), steps to reproduce the issue, detailed workflow history logs, screenshots, and any troubleshooting steps already attempted. This accelerates the resolution process.

Best Practices for Robust Order Processing Workflows¶

Prevention is always better than cure. Implementing best practices for workflow management in D365 SCM can significantly reduce the likelihood of firmed orders getting stuck.

• Regular Workflow Review and Optimization: Periodically review active workflows to ensure they align with current business processes and policies. Remove obsolete workflows and optimize complex ones for efficiency and clarity.
• Thorough Testing of New Workflows or Changes: Any new workflow or modification to an existing one should undergo rigorous testing in a non-production environment before deployment. This includes testing various scenarios, edge cases, and user permissions.
• Comprehensive User Training: Ensure that all users involved in workflow processes, especially approvers, are adequately trained on their responsibilities, how to access and act on workflow tasks, and how to identify potential issues.
• Proactive Monitoring: Establish dashboards or alerts to monitor workflow health, batch job statuses, and pending tasks. Proactive monitoring can help identify and address issues before they become critical.
• Establishing Clear Escalation Paths: Define clear procedures for when a workflow issue is encountered, including who to contact and what information to provide. This ensures rapid response and resolution.
• Documentation: Maintain comprehensive documentation for all workflows, including their purpose, configuration details, conditions, and assigned participants. This helps in troubleshooting and onboarding new personnel.

Visualizing Workflow States¶

Understanding the different states an order can be in during a workflow is crucial for diagnosis. Here’s a simplified overview:

Workflow State	Description
Not submitted	The document has been created but not yet submitted to the workflow.
Submitted	The document has been submitted and is awaiting the first step of the workflow.
In review	The document is currently at an approval or review step, awaiting action from a designated participant. This is the state we’ve discussed as problematic.
Pending	The document is waiting for a system action, a condition to be met, or for a participant to respond. This can sometimes be confused with “In review” but often implies an automated hold or background process.
Approved	The document has successfully completed all required approval steps.
Rejected	A participant has explicitly rejected the document, often requiring the originator to make changes and resubmit.
Completed	The workflow has run to its final successful conclusion.
Canceled	The workflow was manually canceled by a user or administrator.
Stopped	The workflow encountered an error and could not proceed. This usually requires administrative intervention to restart or correct.

This table provides a quick reference for understanding the status messages found in workflow history.

mermaid graph TD A[Order Created] --> B{Submit to Workflow?}; B -- Yes --> C(Workflow Initiated); C --> D{Condition 1 Met?}; D -- No --> E[Rejected / Back to Draft]; D -- Yes --> F(Approval Step 1); F -- Approved --> G{Condition 2 Met?}; F -- Rejected --> E; G -- No --> E; G -- Yes --> H(Approval Step 2); H -- Approved --> I(Workflow Completed); H -- Rejected --> E; I --> J[Order Firmed and Ready for Processing];
Simple example of a multi-step approval workflow for firmed orders.

Concluding Thoughts¶

The efficiency of order processing in Dynamics 365 Supply Chain Management directly impacts an organization’s ability to meet demand, manage costs, and maintain customer satisfaction. When firmed orders become stuck in an “In-review” workflow status, it signals a critical bottleneck that requires immediate attention. By systematically diagnosing the issue, reviewing workflow configurations, verifying permissions, and implementing best practices, organizations can ensure their D365 SCM workflows operate smoothly and reliably. A proactive approach to workflow management is key to unlocking the full potential of D365 SCM and maintaining an agile and responsive supply chain.

We encourage you to share your experiences with D365 SCM workflows. Have you encountered similar issues with firmed orders getting stuck? What troubleshooting steps proved most effective for your organization? Your insights can help the community better navigate these common challenges.