Orders sent to the ERP

When writing to the ERP is on in the connector (Integration connector ▸ Writing to the ERP), every confirmed order — on the order screen, the customer’s B2B portal, the sales rep app and what came up from offline mode — enters this queue instead of becoming Confirmed. Tenka checks stock and credit in the ERP and creates the order through the Include Movements service; the number the ERP returns becomes the order’s ERP number, and the next connector load updates the same order instead of duplicating it.

Waiting: in the queue, goes out within a minute (the cap is ERP.ESCRITA_TETO_MINUTO orders per minute per company). Accepted: the ERP returned the number — the order is Confirmed with ERP status Pending. Rejected: the ERP said no (credit, stock, TOP, registration) — the order is Rejected by the ERP, editable, and is not retried on its own. Gave up: the ERP did not answer in 6 attempts (1, 2, 5, 15 and 60 minutes) — use Retry when it is back.

Before each submission Tenka asks the ERP, at that moment, for the balance of each item at the connector’s stock location and the customer’s credit limit against what they owe there. Short on stock and ERP.ESCRITA… ERP.ESTOQUE_SEM_SALDO set to BLOQUEIA (default): the order is rejected saying which items and how much there is. Over the limit: rejected with the numbers — ask for release in the ERP (or through approval levels) and resend. ERP down: it does not check and waits; it never assumes there is stock.

An order that already has an ERP number, if cancelled in Tenka, stays in the ERP until someone cancels it there — the connector only writes order creation, never deletion. The order screen warns right away with the ERP number. When the ERP cancels, the status comes back on the next read and the order becomes Cancelled in Tenka too.

The ERP rewards program tab reads the view the integrator created in the ERP (Connector ▸ Program view) and compares each customer’s balance with the balance in Tenka. When the check is right, Run the initial load credits, once per customer, "balance brought from the previous program" — with the view’s validity. From then on Tenka credits (paid sale) and debits (redemption on the order and at the POS), and the customer sees it all on the portal under My rewards.

The numbers at the top (waiting, accepted, rejected, gave up) count the company’s whole queue, with or without a filter. The list hides accepted ones to keep in view what needs action; tick "Show accepted" to see them. Discard requires a reason — without it the dialog stays open and says what is missing.

Open the order by the number in the first column: the ERP reason shows on the "In the ERP" badge and in the history. Fix what it asked for (quantity without stock, payment terms, restricted customer) or ask for release in the ERP itself, and click Confirm and send to the ERP — or Retry here. If the order should no longer go, use Discard with the reason: it goes back to quote. The portal customer is told the order needs an adjustment.