KBA-01842: XTS Change Order (CO, CCO) Troubleshooting

Question:

Why is my Owner Change Order not appearing correctly in my accounting system?

Why is my CCO not appearing in my accounting system?

Answer:

If your Change Order (owner or commitment) has been Approved in Spitfire, it is queued to be sent to your peer accounting system (such as Acumatica ERP).

If there is a problem creating the change order in the accounting system, the reason may be sent as an alert. See below for possible Alerts and explanations.

Revision already exported to Ref Num but CO Type CO# Ref Num  Status for $$, expected $$$

Where

• Ref Num is the CO Reference number in your accounting system and appears twice in the alert.
• CO Type is the class/type of this CO in your accounting system (for example, Commitment, Default).
• Status is the status of this CO in your accounting system (for example, On Hold, Closed, Open).
• $$ is the amount of the CO in your accounting system.
• $$$ is the amount of the CO in Spitfire.  Ideally $$ should match $$$.

To fix:

1. Open the CO in your accounting system.
2. Put it On Hold, if not already.
3. Adjust the rows with amounts, for example:
   1. If the amount is zero, add the correct amount.
   2. If there are multiple rows, remove the extra row(s).
   3. If the amount is off by a penny, change the amount to match Spitfire.
4. Save. You can get out of your accounting system.
5. Wait for XTS to retry. Once Spitfire sees that the amount in your accounting system is the same as the amount in Spitfire, it will sync the Change Order (and depending on your corporate SOP, release it).

Additional Comments:

• Alerts can be found in the XTS Queue tab of the Diagnostic Tools page if you are a System Admin.
• A System Admin can also make Spitfire retry a sync more quickly by clicking the running man icon in the XTS Queue tab of the Diagnostic Tools page.

KBA-01842; Last updated: August 28, 2023 at 9:22 am;
Keywords: Acumatica XTS