Overview
This document provides a comprehensive overview of all error messages explicitly defined within the integration code. Its purpose is to maintain clarity, accuracy, and consistency across all error handling. Each error entry includes the error title, detailed message, trigger condition, and the proposed resolution.
Supported Flows
Stock Item To iPaaS
Sales Order From iPaaS
Transaction Tracking Number From iPaaS
Error Collection
Stock Item To iPaaS
Polling Exception
Got Exception in {Identity.AppName} Products while Polling which is : ", $"{ex.Message}.
Description: This issue may occur in the polling for Products to iPaaS flow when the integration encounters an exception during polling, typically caused by unexpected system errors, configuration issues, or invalid or missing data returned from the source application. The polling process fails and throws the exception message captured as: {ex.Message}, which helps identify the underlying cause for troubleshooting and resolution.
Resolution: To avoid this error, ensure the {Identity.AppName} Products polling configuration is correctly set up, and all required product data is available and valid at the source. Verify application credentials, permissions, and connection settings, and confirm that the source system is returning complete and expected product records.
Sales Order From iPaaS
Missing Sale Order Details
Transaction cannot be {Created/Updated} in Acumatica of Type {ActionType} because there is no LineItem/Detail found for SaleOrder!
Description: This issue may occur when the integration attempts to create or update a transaction in Acumatica with action type “Order” but the source Sales Order does not contain any Line Items or Detail records. Since Line Items are mandatory for creating or updating a Sales Order transaction, the system prevents the transaction from being created.
Resolution: To avoid this error, ensure that the Sales Order includes at least one valid Line Item/Detail before initiating the transaction sync. Verify that product lines are correctly created and mapped in the source system, and confirm that the integration mapping is configured to accurately transfer Line Item details. Reprocess the transaction after validating that the Sales Order contains complete and valid Line Item data.
Order Creation Failed
Transaction could not be created in Acumatica of this Type: Order.
Description: This issue may occur in Acumatica when attempting to create a transaction of type Order. The transaction creation fails if required details, such as LineItems, amounts, or other mandatory fields, are missing or invalid, preventing the system from processing it.
Resolution: To avoid this error, ensure that all mandatory fields for the transaction type Order are correctly populated, including at least one LineItem or Detail, before attempting to create the transaction in Acumatica.
Transaction Tracking Number From iPaaS
OrderNbr Required
Required: OrderNbr
Description: This error occurs in Acumatica when creating or updating a shipment that requires an associated order number (OrderNbr). The operation fails if the OrderNbr field is missing or left empty, as the system cannot link the transaction to the corresponding order.
Resolution: To resolve this error, ensure that the OrderNbr field is populated with a valid order number before creating or updating the shipment in Acumatica. Verify that the referenced order exists and is active in the system.
Tracking Required
Required: Tracking #
Description: This error occurs in Acumatica when creating or updating a shipment. The error is triggered because the Tracking # field is required for forming the external ID. If this field is missing or left empty, the system is unable to process or track the shipment properly.
Resolution: To resolve this error, ensure that the TrackingNbr_Package field is populated with a valid tracking number before creating or updating the shipment in Acumatica.
Status Missing
Status is null/empty from mappings
Description: This error occurs in Acumatica when creating or updating a shipment. The error is triggered because the Status field is missing. If this field is missing or left empty, the system is unable to process or track the shipment properly with same status.
Resolution: Ensure that the Status field is populated with a valid value before creating or updating the shipment. This allows the system to correctly process and track the shipment with the intended status.
Status Mismatched
A shipment was attempted with status {Status} but the order already has a shipment with another status which is not supported. The shipment may already be completed in Acumatica.
Description: This error occurs in Acumatica when a shipment is attempted for an order that already has an existing shipment with a different status. The system does not allow multiple shipments for the same order if the statuses are conflicting, such as trying to create a new shipment when the existing one is already completed or in an unsupported status.
Resolution: To resolve this error, verify the existing shipment status in Acumatica before creating a new shipment. Ensure that shipments are only attempted for orders with eligible statuses, and avoid creating duplicate shipments for orders that are already completed or otherwise finalized.
Sequence Number Missing
A shipment was attempted with status {Status} but the order already has a shipment with another status which is not supported. The shipment may already be completed in Acumatica.
Description: This error occurs in Acumatica when a shipment is attempted for an order that already has an existing shipment with a different status. The system does not allow multiple shipments for the same order if the statuses are conflicting, such as trying to create a new shipment when the existing one is already completed or in an unsupported status.
Resolution: To resolve this error, verify the existing shipment status in Acumatica before creating a new shipment. Ensure that shipments are only attempted for orders with eligible statuses, and avoid creating duplicate shipments for orders that are already completed or otherwise finalized.
Shipment Not Found
Unable to locate Acumatica shipment details by Shipment Number {ShipmentRequest.ShipmentNbr}. Please make sure that the shipment has lines from the related Sales Order {this.OrderNbr}.
Description: This error occurs when a shipment is being processed, but Acumatica cannot find any shipment records associated with the provided shipment number. It usually happens if the shipment was never created, the shipment number is incorrect, or the related sales order does not have any lines assigned for shipment.
Resolution: Verify that the shipment number {ShipmentRequest.ShipmentNbr} is correct and that the related sales order {this.OrderNbr} contains shipment lines in Acumatica. Ensure the shipment has been properly created in the system before attempting any processing.
Transaction Lines Not Found
Unable to locate TransactionLines by TransactionId [{this.iPaaS_LineItemId?.Split("|")?[0]}]. Please make sure that iPaaS_LineItemId is populated on the Tracking record.
Description: This error occurs when the system attempts to retrieve transaction lines using the provided TransactionId, but no matching records are found. This typically happens if the iPaaS_LineItemId field is missing, incorrect, or not properly linked to the tracking record.
Resolution: Verify that the iPaaS_LineItemId is correctly populated on the tracking record. Ensure the ID corresponds to a valid transaction line in the system before attempting to process the transaction.
Missing BoxId
Error: The required custom field BoxId is missing. It must be populated before proceeding.
Description: This error occurs when the system attempts to process a shipment or related operation, but the BoxId field is empty or null. BoxId is necessary for identifying the shipment in Acumatica.
Resolution: Verify that BoxId is correctly populated in the custom fields before processing. Ensure that every shipment has a valid BoxId value to avoid validation errors.
Missing WarehouseId
Error: The required custom field WarehouseId is missing. It must be populated before proceeding.
Description: This error occurs when the system attempts to process a shipment or related operation, but the WarehouseId field is empty or null. WarehouseId is necessary for identifying the warehouse location of the shipment in Acumatica.
Resolution: Verify that WarehouseId is correctly populated in the custom fields before processing. Ensure that every shipment has a valid WarehouseId value to avoid validation errors.
Transaction Not Linked
Error: Transaction Tracking Number {TransactionID} is not linked to any Transaction.
Description: This error occurs when the system attempts to process a tracking number, but it cannot find any corresponding Transaction in the system.
Resolution: Verify that the Transaction Tracking Number exists and is properly linked to a valid Transaction in the system before processing.
Shipping Method Not Found
Error: Shipping Method {Type} needs to be created manually in iPaaS first.
Description: This error occurs when the system tries to assign a shipping method that does not exist in iPaaS.
Resolution: Create the shipping method {Type} in iPaaS before attempting to process the shipment.