Reading Enterpryze rejections
Lesson 15 of 15 7 min read
What it means when Enterpryze refuses a document, how Supply Lens narrows down the code at fault, and how to fix the usual causes.
Sometimes everything is connected and the document reaches Enterpryze, but Enterpryze refuses it. The message that comes back can be cryptic. This lesson shows you how to read it and what to fix.
"No matching records found"
The most common rejection looks like this:
Integration error: No matching records found (ODBC -2028)
This message comes from the SAP engine behind Enterpryze, not from Enterpryze's own interface. It means one of the codes on the document does not exist in your Enterpryze company. It could be an item, a customer, a contact person, a tax code, an account or a warehouse. The message does not say which.
Supply Lens checks the codes for you
When a rejection says "No matching records", Supply Lens automatically checks every code on the document against Enterpryze, one at a time, and reports all the ones Enterpryze does not hold, in one pass. You do not fix one code only to have the document come back with the next.
| Code | Can Supply Lens check it? |
|---|---|
| Customer (card code) | Yes |
| Contact person | Yes |
| Bill-to and ship-to address codes | Yes |
| Item code | Yes. It also reports items that exist but are frozen or not a sales item, which Enterpryze also refuses. |
| Tax (VAT) code | No. Enterpryze offers nothing to check against. |
| Warehouse code | No. Enterpryze offers nothing to check against. |
If every code it can check exists, the message says so, which leaves the tax code (or a warehouse code) as the remaining suspect. Check those by hand in Enterpryze.
Other rejections and what they mean
| Ordinary invoice fails before reaching Enterpryze | fallbackWarehouseCode is blank. Enterpryze needs a warehouse on every line of an ordinary invoice. Set it, or create invoices as reserve invoices. |
|---|---|
| Custom field rejected | customFieldMapping names a custom field that does not exist in Enterpryze. Create the field in Enterpryze or correct the name. |
| Addresses rejected | With createBusinessPartnerAddresses on, Enterpryze refused the addresses. The failure is logged, and the document is still sent without bill-to or ship-to codes, so it uses the addresses Enterpryze already holds. |
| Item refused even though it exists | The item is frozen or is not marked as a sales item in Enterpryze. |
Fixing the cause
- Read the rejection and the list of codes Supply Lens reports.
- Decide where the fix belongs: in Enterpryze (create or unfreeze the item, add the customer), in the source system (correct a SKU), or in your settings (a wrong warehouse code or custom field name).
- Fix it, then re-send the document and confirm it arrives.
- If the same code could affect other documents, fix it everywhere now, not one document at a time.
Fernhill's rejected invoice
A paid web order's invoice is rejected with No matching records found (ODBC -2028). Supply Lens's check reports that item code GS-ROSE-03 does not exist in Enterpryze. It is a new gift set the team added to WooCommerce but not the Item Master. Fernhill creates the item, re-sends the invoice and it is created. Because Supply Lens listed every missing code at once, Fernhill knows there is nothing else wrong with that invoice.
Recap
- "No matching records found (ODBC -2028)" means a code on the document does not exist in Enterpryze.
- Supply Lens checks customer, contact, address and item codes automatically and lists every missing one at once.
- Frozen and non-sales items are reported too.
- Tax and warehouse codes cannot be checked automatically. If everything else exists, look there.
- Blank
fallbackWarehouseCode, missing custom fields and refused addresses each have a clear fix.
Quick guides for this topic
Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.