Settings
Check that the settings contain "goodsReceiptEnabled": true,
GET '.../purchaseorders/settings'
{
"poMatchOnAllInvoices": true,
"nsAccountsInPoCategory": true,
"autoPostOnEntry": true,
"autoPostWhenApproved": true,
"goodsReceiptEnabled": true, <--------
"matchingQualityMin": 81.0,
"unitPricePostingDeviationMax": 1.0,
"roundingToleranceForMatchedLinesSum": 1.5,
"roundingToleranceForInvoiceNetAmount": 1.5,
"roundingToleranceForTotalAmount": 1.5,
"numberOfDigitsToleranceForQuantityDecimals": 2,
"quantityIsDeviation": true,
"unitPriceIsDeviation": true,
"netAmountIsDeviation": true,
"totalAmountIsDeviation": true
}
Adding a PO with GRN
Upserting
The entire PO will have to be included in the request body in order to add a GRN.
Since each goodsReceiptNumber is required to be unique per client, there is no need to include old or closed GRNs in this list.
It is still possible to use the same GRN across multiple PO lines.
It is still possible to use the same GRN across multiple PO lines.
Note: SEMINE will instantly run the PO matching routine after receiving a new GRN
[
{
"purchaseOrderNumber": "20201108-16",
"orderDate": "2020-10-23T00:00:00",
"erpVendorId": "999888777",
"currency": "NOK",
"purchaseOrderLines": [
{
...
"goodsReceipts": [
{
"goodsReceiptNumber": "39341",
"quantityReceived": 1.0,
"status": "Open"
}
]
},
...
],
"status": "Open"
}
]
Success
If the GRN is unique for the client, the GNR will be added to the PO.
{
"succeeded": [
{
"purchaseOrderNumber": "20201108-17",
"message": "Success",
"validationMessages": null
}
],
"failed": []
}
Failure
GRNs have to be unique per client + supplier + po.
{
"succeeded": [],
"failed": [
{
"purchaseOrderNumber": "20201108-17",
"message": "Fail",
"validationMessages": [
"Good receipt number/s is already existed in database. You cannot use it again. (PurchaseOrderLineNumber : -bca7afec-4131-4c99-8c82-67a72cb89f7b-) GoodsReceivedNumber/s : 39341"
]
}
]
}
Kommentarer
0 kommentarer
Artikkelen er stengt for kommentarer.