# PurchaseOrderDocumentAttachmentsEx: Exact Online Purchase Order Document Attachments ## Documentation: Additional where-clause columns supported:chr(13) || chr(10) || chr(13) || chr(10)- divisionchr(13) || chr(10) || chr(13) || chr(10)- downloadidchr(13) || chr(10) || chr(13) || chr(10)- ordernumber_fromchr(13) || chr(10) || chr(13) || chr(10)- ordernumber_tochr(13) || chr(10) || chr(13) || chr(10)- accountcodechr(13) || chr(10) || chr(13) || chr(10)- statuschr(13) || chr(10) || chr(13) || chr(10)- document (1 ) - Catalog: `ExactOnlineXML` - Schema: `XML` - Label: Purchase Order Document Attachments The data in this table is partitioned per value of the `Division` column. - Retrieve: True - Insert: True - Update: True - Delete: False - Filters on API Server: division - downloadid - ordernumber_from - ordernumber_to - accountcode - status - document (1 ) ## Parameters of Table Function The following parameters can be used to control the behaviour of the table function `PurchaseOrderDocumentAttachmentsEx`. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values. Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three. Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third. | Name | Data Type | Required | Default Value | Documentation | |---|:---:|:---:|:---:|---| | `division` | `int32` | ☐ | | Company code. | | `Params_AccountCode` | `varchar2` | ☐ | | Customer code. | | `Params_Details` | `boolean` | ☐ | | | | `Params_Document` | `boolean` | ☐ | | Including documents. | | `Params_DownloadID` | `varchar2` | ☐ | | Data subscription token. | | `Params_OrderNumber_From` | `int32` | ☐ | | Order number (from). | | `Params_OrderNumber_To` | `int32` | ☐ | | Order number (through). | | `Params_Status` | `varchar2` | ☐ | | Multi-select; 10: open, 20: partial, 30: complete, 40: cancelled. | ## Columns of Table Function The columns of the table function `PurchaseOrderDocumentAttachmentsEx` are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `ATTACHMENTS_DOCUMENT_ORDERNUMBER_ATTR` | `varchar2` | | | The order number can be used multiple times. If a purchase order with this order number already exists, a new purchase order with the same order number will be created. When no order number is supplied, a new purchase order with the next available order number will be created. | | `ATTACHMENTS_DOCUMENT_STATUS_ATTR` | `varchar2` | | | 10=Open, 20=Partial, 30=Complete, 40=Canceled. Only used for export, imported purchase orders always get status 10. | | `DIVISION_CODE` | `varchar2` | Administration ID | ☑ | Internal unique number of the Exact Online administration. | | `DIVISION_HID` | `int64` | Administration | ☑ | Number of the Exact Online administration. Not guaranteed to be unique. | | `DIVISION_NAME` | `varchar2`(240) | Administration Name | ☑ | Name of the Exact Online administration. Not guaranteed to be unique. | | `INTERFACE_URL` | `varchar2`(4000) | Interface URL | ☑ | URL used to interface this row with Exact Online. | | `ROWNUM` | `int64` | Row Number | ☑ | Number of the row within the results, starting at 1. |