Logical 02305 - Retail Transaction - Header View

Top  Previous  Next

Subject Area Concepts

The Logical 02305 - Retail Transaction - Header View subject area narrows the context of the overall retail transaction macro view to focus on the entities and relationships that identify and describe a retail transaction.  The header view provides a set of entities to describe properties of retail transaction that apply to all components of the transaction (i.e. things that do not vary by transaction line item).  These include relationships to customers, currency used in the transaction, as well as the general entities used to fully describe the supertype, Transaction entity type.

TransactionAssociation and TransactionAssociationType allow transactions to be related to each other for various retailer defined reasons. (for example, a suspend/resume POS function may create a new transaction rather than continue the suspended transaction.);

RetailTransactionLineItemAssociation  and RetailTransactionLineItemAssociationType perform the same function for individual line items in a retail transaction. The two associated line items do not have to come from the same RetailTransaction.  The most common use for this association is when a sale type of SaleReturnLineItem from a previous transaction validates a return type of sale return line item;

RetailTransactionType classifies the retail transaction into retailer defined types. For example:

Sale: where the sum of all line items is a positive balance;

Refund: where the sum of all line items is a native balance; and

Exchange where an item is both Sold and Returned creating a transaction with a zero balance.

RetatilTransactionLineItemAssociate records those workers (Worker entity type) who were involved in making the sale. (For example: a salesman who gave pre-sales demonstration and the worker who closed the sale). This data is processed at the corporate office to calculate applicable commissions on commission sales;

RetailTransactionTotal contains a record of various transaction totals as reported by the POS even if those totals are incorrect; and

Currency refers to the default currency used to settle the transaction. All unqualified monetary amounts in the transaction are deemed to be amounts in this currency.

Retail Transaction Amendments and Overrides

This view highlights the handling of changes made to transactions and transaction line items.  For audit and control purposes, transactions and transaction line items cannot be modified directly.  Instead they are amended through separate, related transactions and line items that through a reference to the original transaction or line item define the intended change.  Transaction amendments are supported through the TransactionAssociation entity type.  The nature of the amendment is defined in the TransactionAssociationType entity type.

Transaction line item amendments are supported through the RetailTransactionLineItemAssociation and the RetailTransactionLineItemAssociationType entity types.  A reason code attribute within the RetailTransactionLineItemAssociation entity enables a retailer to explain the basis for the amendment.  This amendment may affect an original line item in the same transaction or a different transaction.  The ability to amend line items across transactions provides retailers with a way to handle after-purchase price protection promotions, merchandise returns for individually identified items, etc.

For scenarios where a retail transaction line item is entered or amended in a way that exceeds the authority of a terminal operator to process an exception the model provides the RetailTransactionResourceOverride entity.  The entity captures the reason for the override, the resource being accessed through the override, the individual approving the override and the entry method for capturing the override.  This kind of information is very critical for detection and limitation of exposure to fraud and errors.