Troubleshooting Industries Order Management

The topics in this section cover some common troubleshooting tips for Order Management and Order Management Plus.

DataMapper Updates on FulfilmentRequestLine__c Fail
To successfully update FulfilmentRequestLine__c and InventoryItem__c records using OmniStudio DataMapper, Order Management (OM) must be in the same attribute model as CPQ. Use the V2 attribute model for both CPQ and OM.
Amend Supplemental Action Fails to Propagate to FRL During Decomposition
Fulfillment Request Lines (FRLs) aren't created when you disconnect an order line item.
Amend Action Fails to Propagate to Fulfillment Request Lines During Decomposition
The amend supplemental action fails to propagate to the child Fulfillment Request Line (FRL) if the FRL attributes remain unchanged. This issue prevents the child FRL from inheriting the Amend action even though the parent attributes have changed.
Apex CPU Time Limit Exceeded Error in Industries Order Management
When submitting an order, if you get an error saying Apex CPU time limit exceeded, the most likely cause is that the LoggingEnabled custom setting is set to true. To resolve the problem, set LoggingEnabled to false.
Supplemental Order Orchestration Failures
The supplemental order decomposed, but the orchestration plan is frozen or its items were incorrectly canceled.
Supplemental Order Creation Failures
Deleting orchestration item definitions while an inflight order is in progress causes an attempt to de-reference a null object error when creating a supplemental order.
Troubleshooting Order Management Heap Size Issues
When submitting an order, a System.LimitException: Apex heap size too large error indicates that a transaction has exceeded Salesforce governor limits for memory, causing the order to fail before it reaches the orchestration or fulfillment stage. In Industries Order Management, these heap spikes typically occur during the Decomposition or Orchestration Plan Composition stages as the system processes large record volumes or complex attributes. These transactions are strictly subject to a 6 MB limit for synchronous processes and a 12 MB limit for asynchronous processes.
XOM Administration Panel Shows Not Configured for OM Standard
You've upgraded or installed OM, and clicked the Configure for Order Management Standard button on the XOM Administration panel. But the panel says that OM Standard is not yet configured. By changing a couple of settings, you can fix the issue and complete your OM configuration.
OM Plus: Attribute Values aren't Visible in a Log
In Order Management Plus, attribute values are hidden when they're printed to a log. This is a security feature that protects personally identifiable data from inappropriate access.
Cannot Change Tab Names in the All Tabs Page in Salesforce
You can only change tab names if they are part of a visual force page. You cannot change tab names if they have been automatically generated by Salesforce based on Object Type names.
After You Set the Language to Hebrew, Orders No Longer Decompose Properly
If you have changed the language to Hebrew, submitted an order, and clicked View Decompose, the product might not decompose, remaining in Draft status instead of In Progress. You can resolve this issue by changing a few settings.
OM Plus: ? Appears on Some Buttons or Labels
Vlocity Order Management Plus shows all untranslated labels in debug mode, so if the “?” character appears on some of the buttons in the Vlocity Order Management Plus UI, then turn off debug mode as follows:
OM Plus: Delta Sync Doesn't Show Change to Email Address Field for User
Currently, Salesforce does not invoke any triggers when an email address is changed for a user. This means that the sync delta doesn't show email address changes. This limitation is something to be aware of, but there is no workaround at this time.
OM Plus: Order Sync Failure
After all the orchestration items are completed, if some of the Salesforce order records aren't activated, check the Odin page for fallouts on those orders. You can submit the fallout orders to Salesforce for reconciliation.
Run a Background Job to Fix Stuck Orchestration Plans
In rare cases, an orchestration plan has completed all its tasks, but is still in the In Progress state. You can run a background job that marks such plans as complete.
Unable to Obtain Exclusive Access to FulfilmentRequest records
When a swim lane finishes, its associated FulfilmentRequest, OrderItem, and FulfilmentRequestLine records are activated. If multiple Orchestration items finish near the same time, they sometimes try to activate the same FulfilmentRequest records, and run into this exception.
Unable to Obtain Exclusive Access During Staged Assetization
This issue can happen when there are multiple staged assetizations running in parallel, or some orchestration items are locking an account record.
Unable to Obtain Exclusive Access During Order Submission
When multiple orders in the same account are submitted in parallel, they sometimes try to access the same parent records. They can't all access those records at the same time.
Incorrect Modify Action on a Fulfillment Request Line
There's been no change, but a FRL is still showing the Modify action. This situation can happen for a couple of reasons, described in this topic.
Rollback Orchestration Items Not Associated with an Order Item or Fulfillment Request Line
This issue can happen when orchestration scenarios still evaluate to True during the Cancel order submission.
Orchestration Items are Stuck in the Ready State
Orchestration items, such as auto tasks or callouts, can get stuck if any jobs with the OrchestrationEventHandler class are in a failed state and showing exceptions.
Supplemental Order Submission Failed and the Orchestration Plan is Stuck in the Frozen State
This situation can happen when one or more of the orchestration items associated with the orchestration plan is missing a definition.
Fulfillment Request Lines Aren't Linked to Inventory items or Are Missing Inventory Id during Assetization
This issue can happen if there are changes in DecompositionRelationship records that don't match the InventoryItemDecompositionRelationship.
Orchestration Plan Is Not Visible
Sometimes an orchestration plan doesn't appear, even when the record exists, because some a definition of an orchestration item within the plan has been deleted.
DML Operations on the Order Cause Row Lock Exception
When multiple orders are submitted in parallel under the same account, each order attempts to acquire a lock on the same account, leading to a row lock exception.