Skip to Content

Transaction Template Structures

Datafile Software

Transaction Template Structures

Most Datafile applications are based on linked master and detail databases, so the Datafile XML template generally matches to a similar model, being primarily driven by, or related to, the master file of the pair. In fact, all the current XML transactions match to one of five different types of template:

Type 1, create input records (for example, sales orders). From a header/detail-style of XML file, this creates a single temporary database, each record containing the master (order header) elements as well as the details for that particular order line. Datafile master/detail records (orders, say) are then created from that via a standard Datafile batch update accessory, such as the SOP batch update accessory.

Type 2, output from master/detail files (for example, outgoing XML files such as sales acknowledgements and delivery notifications, or purchase orders). This is driven by processing the master file, picking up the associated details on the way.

Type 3, output only transactions (for example, invoices and credit notes). These are driven from the master file (sales accounts file, say), but only output the transaction details in a header/detail style of XML file. The XML transaction header is created from one type of transaction (type 1 or 3, say) and the XML transaction details from another (type 9s, in this case).

Type 4, update records (such as purchase order responses). This is designed to update details in an existing master/detail file combination. These XML file types generally only occur in the purchase order cycle, and the transactions are designed to chain out to a suitable Datafile application document option as each XML document is deconstructed, to complete input processing before moving on to the next document.

Type 5, create transactions only (such as purchase invoices and credit notes direct into the purchase ledger). This type creates transaction data direct in the purchase ledger, without going via purchase orders (see type 4). In this case the type 1/3 records, together with their associated type 9 records, are created from XML header and details elements respectively.
  • Release ID: Standard