XML Document Control
You use this program to configure how you want SYSPRO to process incoming, outgoing and failed XML documents.
These documents arise from the electronic exchange of information between different companies (e.g. sales orders and purchase orders) in a process that is commonly referred to as Business-to-Business Trading. Using SYSPRO's Document Flow Manager, you can automate this flow as well as transform documents into a format compatible with that of the receiving company.
This program is used to configure how XML documents are handled by the Document Flow Manager. This configuration should be done before using the DFM.
Menu and Toolbar
| Field | Description |
|---|---|
| Save | This saves the details you entered or changed. |
Document Control Setup
| Field | Description |
|---|---|
| History details | |
| Keep history of incoming documents |
Retains a history of documents that are received from an external source. |
| Keep history of outgoing documents |
Retains a history of documents that are output or exported. |
| Keep copy of XML documents |
Retains a copy of each outgoing XML document that is processed. The files are stored in the destination folder specified at the History path field. If you select this option together with the option: Keep history of incoming documents, then you can view the incoming documents in the XML Document Query program. |
| Number of days to keep history |
The number of days that you want to retain documents before they are purged. When you run the XML Document Purge program and select the Delete XML History document details option, all documents which are older than this number of days are removed. |
| History path |
The destination path and folder in which you want to store copies of incoming and outgoing documents. |
| Next XML document number |
The next XML document number that will be assigned to outgoing documents automatically. This number is incremented by 1 each time an XML document is created. The XML document number can be up to 8 digits and forms part of the XML document name (e.g. APOnnnnnnnn.XML, where A indicates the company id; PO indicates a purchase order export file and nnnnnnnn indicates the XML document number. |
| Customer destination path | |
| Default |
The default folder for customer documents, if a specific path has not been assigned to the customer. |
| Specific paths |
The folder to which you want documents to be sent for specific customers. |
| Supplier destination path | |
| Default |
The default location for supplier documents if a specific path has not been assigned to the supplier. |
| Specific paths |
The folder to which you want documents to be sent for specific suppliers. |
| Failed document details | |
| Number of days to keep unactioned documents |
The number of days to retain failed documents that have not been actioned (i.e. unactioned documents). When you run the XML Document Purge program and select the Delete XML Failed document details option, all documents which are unactioned and are older than this number of days are removed. |
| Number of days to keep actioned documents |
The number of days to retain actioned documents. When you run the XML Document Purge program and select the Delete XML Failed document details option, all documents which are actioned and are older than this number of days are removed. |
| Failed documents path |
The folder to which documents that have failed during processing must be written. |
| Next Failed document number |
The number that will next be assigned to a failed document received by the system. It is used to build up the file name of failed documents. When a document fails to be processed, three files are generated. For example: If you enter 8 here, then the next document to fail processing would generate the following files in the failed folder:
|