Overview:
This article provides a glossary of errors encountered during order creation in Xvantage for Associates, describing each error's cause and solution. It covers issues like restricted SKUs, backorder limitations, incorrect customer or contact IDs, invalid characters, payment term mismatches, shipping address problems, and system timeouts, guiding associates on how to resolve them effectively.
Process:
Term | Description | Solution |
|---|---|---|
| Error in terms not allowed for this customer, conflict with different shipping address. | If the "Ship To Suffix" field in the "Addresses" tab is not filled in, "000" should be added to it. |
| This SKU is restricted from backordering. | Purchasing must be asked to change this setting to allow it and resubmit the order in CRM or Xvantage for Associates > Order Management |
| Error because the client is in HOLD in IMPULSE since it is not properly released from credit. | Request that the loan officer release the funds correctly. |
| They are different vendors; they cannot be combined because it generates a different PO. Each vendor must have their own order. | |
| More stringent payment terms are applied than those accepted/allowed by the customer | |
| Cost override, the price at which it is being sold is above cost | |
| The SKU is restricted from creating orders. | Request the buyer to release the SKU in MDG and resubmit in CRM or X4A > Order Management |
| Vendors GDS with expired Deal ID | The validity period needs to be updated with purchases for the order to be processed. |
| The end user was added incorrectly. | Remove the End User information from the Quote's "Summary" tab and delete the value in the "End User Account" field. |
| Why it appears: The quantity of SKUs is greater than the maximum allocated quantity (MAX ALLOC Qty) in Impulse | What to do: You can decrease the quantity in the IM360 order and resubmit it. |
| Why it appears: The payment terms for the IM360 order do not match the terms configured in Impulse for that customer. In most cases, the payment terms were updated on the same day the order was placed. | What to do: |
| Why it appears: | What to do: |
| Why it appears: | What to do: |
| Why it appears: | What to do: |
| Why it appears: | What to do: |
| Why it appears: | What to do: |
| Why it appears: | What to do: |
| Why it appears: | Manually check if you can send the same quantity in a manual order. If not, check the limit and split the quantity in X4A across two lines. If this isn't due to the quantity, you should open a support ticket. |
| Serialized product SKUs are limited to 2500 units per line. Note: This is the current configuration as of March 9, 2023. It may change in the future. | Divide the line into 2, 3, etc., separate lines so that each one has ≤ 2500 units before shipping the order. |
| The applied EU is incorrect (it does not exist on the client or it is not correctly created in the SSEU database in Impulse). | Apply or create a different EU from the SSEU database. |
| One or more L type SKUs are forced as a dropshipping order. | Change the order type to stock or check if the SKU settings are correct for the order you are trying to place. |
| The promise date stated on the summary page is in the past. | Remove the promise date value or change it to a future date. |
| It should only appear on license provider orders. The selected EU contact does not have the required ID. | Try reselecting the contact and sending the order again. If the problem persists, try recreating the contact by slightly changing the name or phone number. |
| It should only appear in license provider orders. The selected EU contact does not have the required ID or is not correctly linked to the selected EU. | Search by the SSEU's ACOP ID; the contact will likely not be available. If so, a new contact must be created. If this doesn't help, try recreating the entire EU. If the problem persists, an Incident Report (INC) should be submitted to the EU Engine team for resolution. |
| There can be several reasons. The most common are: | Change the SKU indicator or remove them from the order. |
| There is a special character in a field that is not supported by the Impulse instance for the respective country. The character may be, among others: /, \, accented characters, etc. The field may be any field where you have manually added information: Ship To, PO, comment lines, etc. | Check if there are any special characters in any field and remove them or replace them with others. |
| There is information in the order that is missing or does not comply with the customer and/or SKU configuration. An example for France is the missing FF code in an order when it is mandatory for the selected customer. | For France only: Add an FF code to see if that resolves the issue. If not, and for any other country, raise an issue so the API teams can help. |
| There was a problem with the pricing engine during order submission. | Wait 10-15 minutes and try sending the order again. If the error persists, open a support ticket. |
| This error can appear in B2B or dropshipping orders. This occurs because one or more suppliers in the order are not linked in the Impulse VLNK table. This table links different supplier codes so they can be included in the same dropshipping order. Typically, the linking is done at the supplier master code level. | When you receive this error, you should check the VLNK table in Impulse. Business managers or your local IM360 project manager should have access to and knowledge of this screen. If all the vendor codes in the order are already linked, you should contact your local IM360 representative to perform the same check in the Order Submission API. |
| The order shipping terms have changed, and the user attempting to place the order does not have the necessary access in Impulse to change them. | If you don't plan to access Impulse, leave the "Freight Terms" field blank on the summary page. The order will then be submitted successfully. If you still need to change the freight charges, you must request this directly from someone with access to Impulse. |
| The End User was not applied correctly to the order line(s) or header. | Find and reapply End User to the problematic lines and/or headers |
| This error can occur for two reasons. The first is that the Ship Via selected in the IM360 order does not match the order type or address. The second occurs when no carrier has been selected in the IM360 order. In these cases, the customer's default carrier is used. If you receive this error, it means that the default carrier is not compatible with the order type or address. | Change the carrier code in the summary section. |
| The Order Submit API is currently offline. | Please try resubmitting your order in 1 or 2 minutes. If you receive the same error again, you can contact your local IM360 project manager. |
| There's a problem with the Ship to address. It could be in any of the fields on the Addresses tab. The most common problem is the postal code, which is either in the wrong format or not accepted by Impulse. | Please check the delivery address for any errors. If there are no errors, you can check if you can place an order with Impulse using the same address. |
| There is a problem with the SKU configuration causing the error. The branch is closed or not open for that SKU. | Contact your local purchasing/SKU management team to modify the settings. Once this is done, you will be able to submit the order. |
| This could be because the account is not active in Impulse. Another possibility is that the "ship to suffix" in the order does not exist in Impulse. If the account is active in Impulse or the "ship to suffix" exists, this indicates a problem with the account details in IM360. | If the account is not active in Impulse, you can change it in the order or reactivate it. If the ship-to-suffix does not exist in Impulse, you must select a different one or delete it (using the Override Ship function). If the account is active and the ship-to-suffix exists, you must contact your local IM360 representative so they can resolve the issue. |



































