Purchase Orders
Newly created and modified purchase orders will be exported from Sage and converted to the Yooz PO CSV data format. The resulting file will then be uploaded to Yooz using the POST /orgUnits/{orgUnitCode}/importPurchaseOrders
API call.
Requirements & Assumptions/Assertions
- Purchase orders will be uploaded to Yooz once they have been received in Sage.
- The received quantity of each PO line will be dispatched to Yooz as the ordered quantity. For types of PO line that cannot be received in Sage (e.g. non-stock lines), the ordered quantity will be dispatched to Yooz.
- Sage permits POs to be partially received. If the received quantity of any line alters, it will prompt an update to be dispatched to Yooz.
- A new line will be incorporated into the CSV file for each purchase order item.
- A distinct CSV file will be generated for each Sage company. Each file will be uploaded to the corresponding Yooz organisation.
- The CSV file name format will adhere to the following structure,
{yyyyMMddHHmmssffff}.csv
- The ‘yyyyMMddHHmmssffff’ is the timestamp format. An example of a file name would be, 202204191529002124.csv
- Each CSV file may contain items from multiple purchase orders, but not from different Sage companies. They are uniquely identified by a combination of purchase order number and line number.
Zynk Process
- Export newly created/altered purchase orders from Sage
- Convert the Sage purchase orders to Yooz PO CSV format.
- Upload the PO CSV to Yooz via the API.
Data Format
- The CSV separator is TAB.
- The CSV row ending is CR LF.
- The CSV does not require a header row.
- The CSV date format is yyyyMMdd, e.g. 20220420
- The CSV amount format is 0.00
- The CSV currency format is ISO 4217, e.g. EUR
- The CSV boolean format is 1 or 0 (with 1 representing true and 0 representing false).
- If any string values contain TAB, CR or LF characters, they will be stripped from the data (rather than surrounding the string with quotes).
Scheduling
The default schedule for this solution point is to run daily at midnight and 6am.
Field Mappings
Yooz Column | Yooz Column Description | Sage 200 Professional PO Field | Notes |
---|---|---|---|
1 | Action | Always set to ‘CREATE’ | --- |
2 | Vendor code | Order Details → Account Selection → Code | --- |
3 | Vendor name | Order Details → Account Selection → Name | --- |
4 | Order number | Order Details → Order no | --- |
5 | Order date | Order Details → Document Date | --- |
6 | Amount (incl. taxes) | Order Details → Totals → Gross | --- |
7 | Amount (excl. taxes) | Order Details → Totals → Net | --- |
8 | Currency | Order Details → Account Selection → Currency | Currency values will use the ISO 4217 standard (3 chars), e.g. GBP |
9 | Order creator | N/A, will be left blank | --- |
10 | Order approvers | N/A, will be left blank | --- |
11 | ERP order status | N/A, will be left blank | --- |
12 | Line number | Set to the numeric position of the line within the PO. | --- |
13 | Client item code | Order Details → Line → Product Code | --- |
14 | Item description | Order Details → Line → Description | --- |
15 | Item unit price | Order Details → Line → Unit price | --- |
16 | Quantity ordered | Order Details → Line → Received | Certain types of line can’t be received in Sage (e.g. non-stock items). In these cases, we will populate the quantity received column with the quantity ordered. |
17 | Quantity received | N/A, will be left blank | --- |
18 | Quantity charged | Order Details → Line → Invoiced | --- |
19 | Amount (excl. taxes) charged | Order Details → Line → Net Value | --- |
20 | Discounted amount | Order Details → Line → Unit discount | --- |
21 | Tax profile code | Order Details → Line → Tax Code | --- |
22 | T amount | Order Details → Line → VAT Value | --- |
23 | GL account charged | Order Details → Line → Nominal Code Order Details → Line → Cost Centre Order Details → Line → Department |
The nominal code, department and cost centre will all be in a single column, separated by forward slashes, such as "4000/COS/DEP". Please note that the department and cost centre fields can be blank. |
24 | Dimensions codes | N/A, will be left blank | --- |
25 | Cost centers codes | N/A, will be left blank | --- |
26 | Subsidiary | N/A, will be left blank | --- |
27 | Vendor item code | N/A, will be left blank | --- |
28 | Header level custom data | N/A, will be left blank | --- |
29 | Line level custom data | N/A, will be left blank | --- |
30 | Reception comment | Details → Line → Comment 1 | --- |
31 | Last reception date | N/A, will be left blank | --- |
32 | Planned delivery date | N/A, will be left blank | --- |
33 | Enable the reception | N/A, will be left blank | --- |
34 | TYPE OF PO | N/A, will be left blank | --- |