ARTS Transaction Framework: POSLOG 6.0 and ARTS ODM V7.0/7.1
A transaction is a complete, self-contained record of business activity. ARTS supports a wide variety of transactions used to record sales, inventory receipts, transfers, tender movement, tender settlement, operator access and a lot more. ARTS POSLOG 6.0 and ODM V7.0/7.1 provide two different representations of transactions. In general, the POSLOG 6.0 representation provides a more granular treatment of transactions with a greater number of transaction sub-types than the ODM V7.0/7.1 Data Model. The POSLOG 6.0 is intended to be a complete detailed record of everything that happens within a point of sale environment over the course of day to day operations. It includes business events and activities, access control and authorization of operators, hardware and software faults, etc. POSLOG is a message specification used to contain business information that is moved from one point to another. In relative terms it is transient data. The transactions stored in the ARTS ODM V7.0/7.1 are permanent records of retail business activities. The POSLOG is intended to define the carrier messages to transport business and control data from the point of sale to the services that post that data to an ARTS relational database. As a rule when data is memorialized in the relational database not every data element from the POSLOG has to be retained. Accordingly, the data model will not have an entity and attribute for each non-business oriented POSLOG element reflected in the XML schema.
As currently modeled, there are some business content gaps between the ARTS ODM V7.0/7.1 relational model and the POSLOG. In future the ODM and POSLOG representations will be unified into a single consistent model. For now, this document will address how the ARTS ODM V7.0/7.1 treats transactions.
Figure 53 - ARTS ODM V7.0/7.1 Transaction Taxonomy With Level of Correspondence to POSLOG 6.0
The diagram here shows all of the transaction types and subtypes supported in ARTS ODM V7.0/7.1. The degree to which the transaction types in the diagram map to POSLOG 6.0 XSD elements is indicated by the colors as shown in the Color Coding Legend. Corresponding transaction types map to specific POSLOG elements. The light yellow transaction types are similar to POSLOG 6 XSD elements but not an exact match. Red outlined transaction types do not have a corresponding transaction element in the POSLOG 6.0 XSD. Note that in some instances like ItemProcessingTransaction, there may be a mapping in a different XML Schema.
Each of the transaction types along with relevant contextual entities and relationships is discussed in detail in the transaction views listed in the Logical 02200 - Transaction Macro View.