Overview
This document provides an overview of all error messages defined within the Orderful integration code.
This document covers these flows:
Error Collection
Orderful Shipping Method To iPaaS
Shipping Method Not Found
Could not find any shipping method associated with the provided ID.
Location: This error occurs in the Get method of the Shipping Method model. It triggers when the system attempts to retrieve a Shipping Method, but the provided ID is null, empty, or does not correspond to any existing Shipping Method.
Resolution: Ensure that a valid Shipping Method ID is provided and that the Shipping Method exists in the source or target system before triggering the Get operation.
Orderful Transaction From iPaaS
Transaction Address Missing
Transaction could not be created because the Address information is missing.
Location: This error occurs in the Create method of the Transaction model. This error triggers when the system attempts to build N1 loop data, but the TransactionAddress collection is either null or empty. Address details are mandatory for transaction creation.
Resolution: Ensure that at least one valid Transaction Address is provided with all required address fields before triggering the Transaction Create flow.
Transaction Line Items Missing
Transaction creation failed. No line items were provided.
Location: This error occurs in the Create method of the Transaction model. It triggers when the system attempts to build PO1 loop data, but the TransactionLineItems collection is null or empty. At least one valid line item is required.
Resolution: Ensure that one or more valid Transaction Line Items are provided with all required fields (such as quantity, unit price, and product identifiers) before triggering the Transaction Create flow.
Transaction Creation Failed
Order creation in Orderful failed while executing the TransactionCreate method.
Location: This error occurs in the create method of the Transaction model. It triggers when the system does not receive a valid response or Transaction ID after attempting to create an order in Orderful.
Resolution: Verify that the Orderful integration is correctly configured and reachable. Ensure that all required Transaction data and mappings are valid, and review integration logs for any errors during the transaction creation process before retrying.
Orderful Transaction To iPaaS
Invalid Transaction Type
The Transaction Type is not valid.
Location: This error occurs in the Get method of the Transaction model. It triggers when the system successfully calls the API, but the returned Transaction response is null or does not contain a valid Transaction ID. This typically indicates that the Transaction Type is invalid or not supported by the integration.
Resolution: Verify that the Transaction Type is valid and supported for this integration. Ensure that the provided Transaction ID exists in the target system and that the correct mapping collection type is being used before retrying the request.
GetTransactionForPolling Method Error
$"An error occurred in GetTransactionForPolling (Transaction.cs): {ex.Message}"
Location: This error occurs in the GetTransactionForPolling method of the Transaction model. It triggers when an exception occurs while polling transactions, filtering by lastModifiedDT, or handling paginated API responses.
Resolution: Check that filter and lastModifiedDT values are valid, ensure API responses and pagination links are correct, and verify that proper null checks and proper exception handling are in place.
Orderful Ship Notice Transaction Tracking Number To iPaaS
Transaction not found
Transaction Tracking Number Matched with PurchaseOrderNumber clause but couldn't locate any transactions associated with the provided PurchaseOrderNumber : {PurchaseOrderNumber}
Location: This error occurs in the Get method of the transaction tracking number model. It triggers when the system tries to match a transaction via PurchaseOrderNumber (as per TransactionTrackingMatchMethod) but cannot find any transaction in the target system with that PurchaseOrderNumber.
Resolution: Verify that the provided PurchaseOrderNumber exists in the system and that the transaction has been created.
Purchase Order is null
Transaction Tracking Number Matched with PurchaseOrderNumber but the response of PurchaseOrderReference is null
Location: This error occurs in the Get method of the Transaction Tracking Number model. It triggers when TransactionTrackingMatchMethod uses PurchaseOrderNumber, but the response does not contain a valid PurchaseOrderReference.
Resolution: Ensure that the transaction contains a valid PurchaseOrderReference before attempting tracking number matching.
Shipment Identification
Transaction Tracking Number Matched with ShipmentIdentification clause but couldn't locate any transactions associated with the provided ShipmentIdentification : { ShipmentIdentification }
Location: This error occurs in the Get method of the TransactionTrackingNumber model. It triggers when the system matches a transaction via ShipmentIdentification, but no transaction exists in the target system for that shipment ID.
Resolution: Verify that the transaction exists and contains a valid ShipmentIdentification.
ShipmentIdentification is null or empty
Transaction Tracking Number Matched with ShipmentIdentification but the response of shipmentIdentification is null or empty.
Location: This error occurs in the Get method of the Transaction Tracking Number model. It triggers when TransactionTrackingMatchMethod uses ShipmentIdentification, but the response from the source does not provide a ShipmentIdentification value.
Resolution: Ensure that the transaction contains a valid ShipmentIdentification in the Ship Notice (856) data before matching.
Transaction Tracking Matched with Fallback but no Transaction found
Fallback transaction tracking number matching failed. No tacking was found using either PurchaseOrderNumber or ShipmentIdentification as search filters.
Location: This error occurs in the Get method of the Transaction Tracking Number model. It triggers when TransactionTrackingMatchMethod is set to Fallback, but the transaction cannot be found using either PurchaseOrderNumber or ShipmentIdentification.
Resolution: Verify that the transaction exists and that at least one of PurchaseOrderNumber or ShipmentIdentification is correctly populated in the transaction.
Transaction Tracking Fallback Failed
Fallback transaction tracking number matching failed.
PurchaseOrderReference is null and ShipmentIdentification did not return any transaction tracking.
Location: This error occurs in the Get method of the Transaction Tracking Number model. It triggers when TransactionTrackingMatchMethod is set to Fallback, but the system cannot resolve any transaction because both the ShipmentIdentification and PurchaseOrderReference are missing or null for the provided Transaction ID.
Resolution: Ensure that the transaction contains at least one of the following: a valid PurchaseOrderReference or a valid ShipmentIdentification. Verify that the transaction exists in the source system and that the integration mapping and settings are correctly configured for tracking number resolution.
Transaction Tracking Failed (Null/Empty Redirect to PurchaseOrderNumber)
$"Transaction tracking number transfer failed. Tracking number was null or empty, and no transaction " + $"was found for PurchaseOrderNumber '{TransactionTrackingNumber.PurchaseOrderReference_PurchaseOrderNumber}'."
Location: This error occurs in the Get method of the Transaction Tracking Number model. It triggers when TransactionTrackingMatchMethod is null or empty, causing the fallback logic to attempt matching via PurchaseOrderNumber. The transaction could not be found because the provided PurchaseOrderNumber does not exist in the target system.
Resolution: Ensure that the transaction contains a valid PurchaseOrderNumber in its PurchaseOrderReference. Verify that the PurchaseOrderNumber exists in the system and that integration mapping and configuration are correct before retrying the operation.
Transaction Tracking Failed (Null/Empty Redirect to PurchaseOrderNumber, Reference Null)
Transaction tracking number transfer failed. Tracking number was null or empty, so matching was redirected to the PurchaseOrderNumber clause, but the PurchaseOrderReference response was null.
Location: This error occurs in the Get method of the Transaction Tracking Number model. It triggers when TransactionTrackingMatchMethod is null or empty, causing the fallback logic to attempt matching via PurchaseOrderNumber. The transaction response does not contain a valid PurchaseOrderReference, so no transaction can be resolved.
Resolution: Ensure that the transaction contains a valid PurchaseOrderReference with a proper PurchaseOrderNumber. Verify that the transaction exists in the source system and that integration mapping and settings are correctly configured for tracking number resolution.
Transaction Tracking Data Not Found
The Purchase order number as well as shipping method both do not exist for the provided ID {id}
Location: This error occurs in the Get method of the Transaction Tracking Number model. It triggers when the system attempts to retrieve transaction tracking information for a given Transaction ID but cannot find either a valid PurchaseOrderNumber or shipping/tracking information. Essentially, the transaction does not contain the required data for tracking.
Resolution: Ensure that the provided Transaction ID exists and contains at least one of the following: a valid PurchaseOrderNumber or a valid ShipmentIdentification.