ERP Push (Materials)
Confirmed materials dockets go to COINS as goods receipts. They use the same push as labour and plant dockets: the same review step, the same batches, and the same retry and un-push. This page covers what is particular to materials: how a docket gets its project stage, what holds it, and what each receipt line carries.
Who can push
Roles with ERP export can push. Supervisors cannot; they use the Material Dockets Export CSV instead.
How to push
- Open the Docket Workbench’s Materials view and select confirmed dockets.
- Open Export ▾ and choose Push to COINS.
- Review the dockets. For dockets on one stage, View XML shows the goods receipt COINS will receive.
- Push.
A docket can be pushed when all of these hold:
- It is confirmed.
- It has not been pushed before.
- Its supplier is on an ERP purchase order for the project.
Push materials dockets separately from labour or plant dockets.
Receipts migrated from Lacroo Core are not confirmed, so they are never pushed from Lacroo.
Project stage
A materials docket takes the project stage of its material lines’ activities. That stage’s COINS CID goes on the receipt.
| The docket’s lines | Result |
|---|---|
| All on activities of one stage | Pushes under that stage. |
| On activities of two or more stages | Held because the docket spans more than one project stage. Split it so each docket stays in one stage. |
| None on an activity with a stage on this project | Held because the docket is not attributed to a project stage. |
| Any line with no activity, or a blank cost code | Held with: “Docket has a material line with no cost code. Give each material line an activity that has a cost code.” |
Only live lines and live activities count. An activity on another project never gives a docket a stage.
A held docket blocks the push. Fix it, or leave it out of the selection and push the rest.
What each receipt line carries
Each material line becomes one receipt line.
| In COINS | From Lacroo |
|---|---|
| Purchase order number | The part before : in the key of the purchase-order line behind the line’s rate. |
| Purchase order line | That purchase-order line’s number. |
| Quantity delivered | The material line’s quantity. |
| Unit | The purchase-order line’s unit, in capitals. |
| Cost code | The cost code of the material line’s activity. |
| Supplier reference | The docket number and a key unique to the line, so COINS can tell two receipts apart. |
| Delivery date | The docket’s date. |
| Company (CID) | The project stage’s COINS CID. |
The header comes from your organisation’s COINS connection. The password is always masked.
A material line reaches a purchase-order line only after the contract’s rate line has been allocated to one. An unallocated line is left off the receipt, and the review step shows a warning for it.
View, copy and download the XML
In the review step, View XML shows the goods receipt for the selection. From that view:
- Copy XML copies it.
- Download XML saves it as
Dockets Export.xml.
This is the document you reviewed, with the connection details masked. Do not import it into COINS by hand: Push to COINS sends the real receipt. If the selection spans several stages, the XML lists every docket under one stage’s CID; the push sends one receipt per stage.
A pushed batch’s page lets you download the receipt that was sent, as coins-batch-<batch>.xml.
Related
- ERP Integrations: connecting COINS, batches, retry and un-push.
- Material Dockets Export: every delivery in a date range as a CSV.
- Contracts: rate lines and their purchase-order allocation.
- Dockets: the Materials view and the docket lifecycle.