Skip to main content

Functional points

1. How to send a purchase order to Yooz without waiting for its receipt (e.g., international sourcing / imports)?​

For items managed in stock, the order is only sent to Yooz at the time of receipt. If you need to anticipate this, you must use the manual button "Send to Yooz without receipt" available on the purchase order screen. This button becomes clickable as soon as the order is signed and printed.

2. What does the error "Zone NUMORI: Receipt date must not be greater than invoice date" mean?​

This is a native Sage X3 control that enforces a strict logistics chronology: Order > Receipt > Invoice. Importing an invoice dated prior to the stock entry distorts valuation. You must either use advance invoice management or disable this control by setting the parameter value XRJ31CTLDO to "No" (a specific workaround for the connector).

3. Why do I get the error "Different invoicing supplier" when importing an invoice?​

The error occurs if the invoicing party sent by Yooz does not match the invoicing party entered on the original order/receipt in X3. The connector requires a strict match; you must correct the supplier in the database (PRECEIPT or PORDER table) or ensure that Yooz sends the correct code.

4. How to export specific fields (custom fields) from Yooz to Sage X3?​

You need to use the "Incoming Yooz custom fields" (or outgoing) function. This allows you to map identifiers (e.g., *40, *41) sent by Yooz to the correct fields in the X3 data tables. Do not modify the import template directly.

5. Error 400 indicates "Consistency error between SIRET, SIREN or VAT No." when exporting suppliers. What is the solution?​

Yooz performs a strict validation check. If a SIRET does not have 14 characters or if the VAT number is poorly formatted, synchronization is blocked. You can temporarily disable sending the SIRET by changing the parameter XRJ31SIRET to "No".

6. How to resend an entire repository (Suppliers, Accounts...) to Yooz in case of a blockage?​

You must use the "Yooz Data Recovery" (XRJ31YOOZREP) function. Select the relevant object (e.g., BPS for suppliers) and click "Send all data" or "Send unsent data".

7. What does the message mean: "This invoice from Yooz has already been imported into Sage X3. Import refused"?​

The connector checks the Chrono Yooz field (XRJ31NUMYOOZ). If this number already exists on an integrated invoice, Sage X3 blocks the import to prevent the creation of a duplicate.

8. Why do some receipts created in X3 not flow back up to Yooz?​

The items in the order must be configured as "receivable" (field [F:ITM]RCPFLG=2). If they are not (e.g., services), the purchase order is sent to Yooz as soon as it is signed and printed, without waiting for a receipt.

9. The error "Zone UOM: Required zone" or "Field UOM: Incorrect values" appears. What does it mean?​

Sage X3 expects a recognized unit of measure when importing the invoice. If the unit sent by Yooz or found on the item record is incorrect, the line is rejected. The unit of measure must be created and exist identically in Sage X3 (e.g., "UN" or "KG").

10. Error "PAYLOAD_ELEMENT_ID_NOT_FOUND", "The given repository does not exist": what is the cause?​

This happens when the X3 connector attempts to send a repository with an Organization code or a Collective Account that has not yet been created or shared in the Yooz environment. You need to check the setup associated with this information.

11. What happens when a purchase order is modified or deleted in X3?​

The connector detects the modification or deletion. In the case of a deletion, the connector sends a DELETE (A) action to the Yooz API to cancel the order. For a modification, the reprinted order is updated in Yooz.

12. The error "Zone LINORI: Line already invoiced or closed" appears during export, what should I do?​

This means that Yooz is trying to match or import an invoice to a receipt/order line that is technically already fully closed and/or invoiced in Sage X3. Check the status of the order or receipt line in X3.

13. In case of a blockage or failure when sending to Yooz, how can I identify the technical error?​

You must consult the YOOZ-LOG workflow or read the log generated by the batch server ("Read log file" function). In the event of a communication error, CURL requests and their API returns (HTTP statuses 400, 404, etc.) are recorded there in detail, and error files can be downloaded from the Yooz Interfaces function.