Documentation/ ERP integrations/ Ágora POS
Ágora
With the Ágora connection, documents are posted straight into the system. What decides whether a sending works is that suppliers and products have their Ágora code: without them, the system does not know what anything refers to.
Delivery note list › tick › Send to Ágora
On this page
What kind of integration it is
It is direct sending. Press the button and the documents ticked are posted into Ágora and leave the pending list. The ones that fail stay.
The result allows for the partial case: part of the batch can go in and the rest stay behind. The application reports both figures.
Connecting Ágora to Dijit
The connection is set up once, in three steps. The ZIP and the details are in Dijit, in Account › Parameters, Ágora section.
- Download the custom queries ZIP and copy its 5 XML files into Ágora's custom-queries folder. Your Ágora distributor usually does this step, because you may not have access to that folder. See Ágora custom queries.
- Fill in the connection details. See Connection details in Parameters.
- Click Save at the bottom of the page.
Connection details in Parameters
These are the fields in the Ágora section and what goes in each one:
| Field | What goes in it |
|---|---|
AGORA_ENDPOINT | The URL of the Ágora server. |
AGORA_ENDPOINT_APIKEY | The password Ágora generates automatically. |
WAREHOUSE_NAME | The warehouse name. |
WAREHOUSE_ID | The warehouse id. |
WAREHOUSE_IDN_SERIE | The delivery note series. |
WAREHOUSE_IDN_LAST_NUMBER | The last number used in that delivery note series. |
AGORA_DEFAULT_CONFIRMED_STATUS | The status the delivery note is created with in Ágora: draft or posted. See The status they arrive with. |
Ágora custom queries
To read and send units of measure and purchase VAT or IGIC, the XML files must be copied into the custom queries folder on the computer where Ágora is installed: Disk › IGT Microelectronics › Agora › custom-queries.
Your Ágora distributor usually does this step, as you probably don't have access to that folder. Download the ZIP and send it to them.
The files are downloaded as a ZIP from Dijit, in Account › Parameters, Ágora section, with the Download custom queries (.zip) button. The ZIP holds 5 XML files, one per query:
| What it does | QueryGuid |
|---|---|
| List active taxes | {8BDD8D28-B7D7-43F2-AD46-ED91C9D91242} |
| List products with a purchase unit | {1694B0BA-5D22-41E6-98A9-2499A95C008A} |
| List purchase units | {01209923-694D-4784-91B8-07D6EE99A045} |
| Insert purchase units | {8AAC3D56-3040-4202-AFEA-DE1256A58F88} |
| Update a product's purchase unit | {DFD5BBAA-F4A1-4776-B323-4E9F267B1A5F} |
The Ágora codes
Every supplier and every product needs its Ágora code assigned. They are two different things and they fail separately:
| The code is missing on… | Where it is fixed |
|---|---|
| The supplier | On their record in the supplier master, in the reference field. |
| A product | On the document's line, by assigning the item from the Ágora catalogue. |
Where a product does not exist in Ágora yet, there is no need to leave the application: it can be created from the delivery note's line itself.
The warning before sending
Before sending anything, the application goes over the documents ticked and, if it finds codes not assigned, says so in detail. The messages name the document, the line and the element's name:
| Message | What it means |
|---|---|
| Ágora codes missing on suppliers | One or more suppliers with no code. |
| Ágora codes missing on products | One or more lines with no item assigned. |
| Ágora codes missing on suppliers and products | Both. |
The detail is precise: it names the document, the line number and the product with no Ágora code assigned. There is no hunting for where the problem is.
Carrying on anyway
The warning does not block the sending: it asks. It says how many documents have no Ágora codes set and whether you want to carry on sending regardless.
Carrying on is a deliberate decision, and it has a consequence: those documents will go into Ágora incomplete, or be rejected. Unless you know exactly why you are doing it, the sensible course is to cancel, assign the codes and send again.
Refreshing the catalogue
Ágora's item list is held in memory while you work. When a product is created in Ágora and does not come up in a search, the refresh button asks for the list again.
It is at the top of the ERP block in the assignment dialogue, and on the list as well. It is the first remedy for an item that "ought to be there and is not".
The status they arrive with
An integration parameter decides what status documents are posted with in Ágora: draft or posted.
| Option | Effect | When it suits |
|---|---|---|
| Draft | They go in unconfirmed, to be looked over in Ágora. | Starting out with the integration, or where you want a second check. |
| Posted | They go in already confirmed. | Where the checking is done in Dijit.app and you do not want to repeat it. |
It is set in Parameters, in the Ágora section.
The items' VAT
In the assignment dialogue, the purchase VAT field is read-only and shows the rate the item has in Ágora, not the one in Dijit.app's own catalogue.
If it shows as not set, the item has no rate defined in Ágora. The application does not invent a percentage: it is corrected in Ágora.
Equivalence surcharge
On incoming delivery notes, the equivalence surcharge now travels to Ágora with the rest of the line. It used to be left behind and had to be sorted out at the other end.
What goes across is whatever the document carries, so it is worth checking first on the header: see Equivalence surcharge.
Things that come up
| What you see | Why | What to do |
|---|---|---|
| It warns of suppliers with no code | The ERP reference is missing from their record. | Fill it in on the supplier master. |
| An item just created in Ágora does not appear | The list is held from earlier. | Press refresh and search again. |
| Ágora could not be reached | The service may be momentarily down. | Try again. If it persists, wait a few minutes. |
| The item's VAT comes out as not set | It has no rate defined in Ágora. | Give it one in Ágora and refresh. |
| Documents arrive in Ágora unconfirmed | The parameter is set to draft. | Change it to posted in Parameters, if that is the policy. |