Business Unit Common Data Node describing the location. Contains one or more of RetailStore, DistributionCenter, InventoryLocation and AdminstrativeCenter. The name of the business unit separate legal entity which conducts retail operations for the retail enterprise in some geographical location. It may be treated as a division internally - yet it is still a separate legal entity a unique line of business within a corporation Any area of a store from which particular revenues can be said to derive A grouping of items with similar point of sale control and processing attributes. This entity type may also be used to control sales that are not properly identified at the item-level. an administrative unit in a large store which certain retail functions have been grouped A warehouse or other storage facility that receives merchandise in bulk from Suppliers and supplies merchandise to RetailStores. It may be co-located at the same Site as a RetailStore or AdministrativeCenter. A group of offices at which the retail enterprise conducts administrative (non-selling) operations. May be co-located at a Site with RetailStore, DistributionCenter, or InventoryLocation. A retail outlet that sells merchandise and services through either a physical location, catalog, web page or other channel. It may or may not be identical to a Site. It may be co-located at the same Site as a DistributionCenter, InventoryLocation or AdministrativeCenter. organizational hierarchy so that destination can be targeted to individual location, region, division etc, not to be confused with reporting the entire hierarchy as is done with the Organizational Hierarchy Structure - i.e. an instance of an organization hierarchy at a particular level. The event message’s auto-incrementing sequence number so that the messages can be ordered and duplicates can be detected. Each producer should use its own sequence number, which should rollover. The date, time, and time zone when the event occurred from the producer’s perspective. Millisecond granularity. A description of the event. Logical name of the event producer. In the case of multiple instances of a producing application, the instance number so that each producer can be unique. This may be the process ID for convenience. Used for prioritizing messages in the queue. The Severity is the basic priority of the message. This is defined in ISO 2382. Enumeration - Information - data about the condition the event is reporting, e.g.temperature of a freezer or chiller - Warning - an indication of a condition which may develop into a fault at a later time - Fault – Error requiring immediate attention. TestMode, TrainingMode, or ProductionMode enum: ISO-4217 / UN/ECE REC 09 Codes Andorran Peseta UAE Dirham Afghani Leck Armenian Dram Netherlands Antillan Guilder Kwanza Argentine Peso Schilling Australian Dollar Aruban Guilder Azerbaijanian Manat Convertible Marks Barbados Dollar Taka Belgian Franc Lev Bulgarian Lev Bahraini Dinar Burundi Franc Bermudian Dollar Brunei Dollar Boliviano Mvdol Brazilian Real Bahamian Dollar Ngultrum Pula Belarussian Ruble Belize Dollar Canadian Dollar Franc Congolais Swiss Franc Unidades de fomento Chilean Peso Yuan Renminbi Colombian Peso Costa Rican Colon Cuban Peso Cape Verde Escudo Cyprus Pound Czech Koruna Deutsche Mark Djibouti Franc Danish Krone Dominican Peso Algerian Dinar Sucre Unidad de Valor Constante (UVC) Kroon Egyptian Pound Nakfa Spanish Peseta Ethiopian Birr euro Markka Fiji Dollar Falkland Islands Pound French Franc Pound Sterling Lari Cedi Gibraltar Pound Dalasi Guinea Franc Drachma Quetzal Guinea-Bissau Peso Guyana Dollar Hong Kong Dollar Lempira Croatian kuna Gourde Forint Rupiah Irish Pound New Israeli Sheqel Indian Rupee Iraqi Dinar Iranian Rial Iceland Krona Italian Lira Jamaican Dollar Jordanian Dinar Yen Kenyan Shilling Som Riel Comoro Franc North Korean Won Won Kuwaiti Dinar Cayman Islands Dollar Tenge Kip Lebanese Pound Sri Lanka Rupee Liberian Dollar Loti Lithuanian Litus Luxembourg Franc Latvian Lats Lybian Dinar Moroccan Dirham Moldovan Leu Malagasy Franc Denar Kyat Tugrik Pataca Ouguiya Maltese Lira Mauritius Rupee Rufiyaa Kwacha Mexican Peso Mexican Unidad de Inversion (UDI) Malaysian Ringgit Metical Namibia Dollar Naira Cordoba Oro Netherlands Guilder Norvegian Krone Nepalese Rupee New Zealand Dollar Rial Omani Balboa Nuevo Sol Kina Philippine Peso Pakistan Rupee Zloty Portuguese Escudo Guarani Qatari Rial Leu Russian Ruble Russian Ruble Rwanda Franc Saudi Riyal Solomon Islands Dollar Seychelles Rupee Sudanese Dinar Swedish Krona Singapore Dollar Saint Helena Pound Tolar Slovak Koruna Leone Somali Shilling Suriname Guilder Dobra El Salvador Colon Syrian Pound Lilangeni Baht Somoni Manat Tunisian Dinar Pa´anga Timor Escudo Turkish Lira Trinidad and Tobago Dollar New Taiwan Dollar Tanzanian Shilling Hryvnia Uganda Shilling US Dollar US Dollar (Next day) US Dollar (Same day) Peso Uruguayo Uzbekistan Sum Bolivar Dong Vatu Tala CFA Franc BEAC Silver Gold European Composite Unit (EURCO) European Monetary Unit (E.M.U.-6) European Unit of Account 9 (E.U.A.-9) European Unit of Account 17 (E.U.A.-17) East Caribbean Dollar SDR Gold-Franc UIC-Franc CFA Franc BCEAO Palladium CFP Franc Platinum Codes Specifically reserved for testing purposes Yemeni Rial Yugoslavian Dinar South Africa Rand Kwacha Zimbabwe Dollar A currency is a unit of exchange, facilitating the transfer of goods and/or services. It is coins and paper bills used as money. a proper description of a currency amount, usually for coins or banknotes If true, the authorization methods will run asynchronously. If false, the authorization methods will run synchronously. This property is initialized to NULL by the open method and is updated when an authorization operation successfully completes. An application can send data to the CAT device by setting this property before issuing an authorization method. Also, data obtained from the CAT device and not stored in any other property as the result of an authorization operation (for example, the account code for a loyalty program) can be provided to an application by storing it in this property. Since the data stored here is device specific, this should not be used for any development that requires portability. This property is initialized to NULL by the open method and is updated when an authorization operation successfully completes. Electronic Money Device: The balance of Credit Card. If true, the AdditionalSecurityInformation property may be utilized; otherwise it is false. If true, the authorizeCompletion method has been implemented; otherwise it is false. If true, the authorizePreSales method has been implemented; otherwise it is false. If true, the authorizeRefund method has been implemented; otherwise it is false. If true, the authorizeVoid method has been implemented; otherwise it is false. If true, the authorizeVoidPreSales method has been implemented; otherwise it is false Electronic Money Device: Show the device has charged method by cashDeposit method or not. If true, the cashDeposit method is implemented, otherwise false. If true, the CenterResultCode property has been implemented; otherwise it is false. If true, the checkCard method has been implemented; otherwise it is false. Shows the daily log ability of the device. If true, the item “Installments” which is stored in the DailyLog property as the result of accessDailyLog will be provided; otherwise it is false. Electronic Money Device: If true, the device can notify the condition of the log by the LogStatus property, otherwise false. Electronic Money Device: If true, the device can notify the condition of the log by the LogStatus property, otherwise false. If true, the PaymentDetail property has been implemented; otherwise it is false. If true, the item “TaxOthers” which is stored in the DailyLog property as the result of access DailyLog will be provided; otherwise it is false. If true, the TransactionNumber property has been implemented; otherwise it is false. If true, the TrainingMode property has been implemented; otherwise it is false. Electronic Money Device: If true, the device has a security lock and the device can release the lock using the unlockTerminal method, otherwise false. This property is updated when an authorization operation successfully completes. It shows credit card company ID. Contains the code from the approval agency. Check the approval agency for the actual codes to be stored. Stores the result of the accessDailyLog method. Electronic Money Device: This property shows the status of the DealingLog of the device. Holds the payment condition of the most recent successful authorization operation. Contains payment condition details as the result of an authorization operation. Payment details vary depending on the value of PaymentCondition. Holds the payment media type that the approval method should approve. Stores a “sequence number” as the result of each method call. This number needs to be checked by an application to see if it matches with the argument sequenceNumber of the originating method. Electronic Money Device: Setting real amount of the settlement. Stores a “slip number” as the result of each authorization operation. If true, each operation will be run in training mode; otherwise each operation will be run in normal mode. Stores a “transaction number” as the result of each authorization operation. Stores a “transaction type” as the result of each authorization operation. if true, the UnifiedPOS Service will set DeviceEnabled to false after it receives and enqueus data as a DataEvent. Before any additional input can be received, the application must be set DeviceEnabled to true. If true, then the service/device supports comparing the version of the firmware in the physical device against that of a firmware file. Identifies the reporting capabilities of the device If true, the device accumulates and can provide various statistics regarding usage; otherwise no usage statistics are accumulated. If true, then the device's firmware can be updated via the UpdateFirmware method. if true, the device statistics, or some of the statistics, can be reset to zero using the ResetStatistics method, or updated using the UpdateStatistics method. Holds the results of the most recent call to the CheckHealth method. If true, the device is claimed for exclusive access. If false, the device is released for sharing with other applications. Holds the number of enqueued Data Events. If true, a Data Event will be delivered as soon as input data is enqueued. If changed to true and some input data is already queued, then a Data Event is delivered immediately. Holds an identifier for the UnifiedPOS Control and the company that produced it. Holds the UnifiedPOS Control version number If true, the device is in an operational state. If changed to true, then the device is bought to an operational state. Holds an identifier for the UnifiedPOS Service and the company that produced it. Holds the UnifiedPOS Service version number If true, the UnifiedPOS control will not deliver events. Events will be enqueued until this property is set to false. Identifier of the most recently started asynchronous output Holds an identifier for the physical device Holds a short name identifying the physical device. Contains the type of power notification selection made by the application. Identifies the current power condition of the device, if it can be determined Holds the current state of the device An attempt was made to access a closed Device. An attempt was made to access a Physical Device that is claimed by another Control instance. The other Control must release the Physical Device before this access may be made. For exclusive-use devices, the application will also need to claim the Physical Device before the access is legal. An attempt was made to access an exclusive-use device that must be claimed before the method or property set action can be used. If the Physical Device is already claimed by another Control instance, then the status E_CLAIMED is returned instead. The Control cannot communicate with the Service, normally because of a setup or configuration error. Cannot perform this operation while the Device is disabled. An attempt was made to perform an illegal or unsupported operation with the Device, or an invalid parameter value was used. The Physical Device is not connected to the system or is not powered on. The Physical Device is off-line. The file name (or other specified value) does not exist. The file name (or other specified value) already exists. The Device cannot perform the requested procedure, even though the Physical Device is connected to the system, powered on, and on-line. The Service timed out waiting for a response from the Physical Device, or the Control timed out waiting for a response from the Service. The current Service state does not allow this request. For example, if asynchronous output is in progress, certain methods may not be allowed. A device category-specific error condition occurred. The error condition code is held in an extended error code. The requested operation can not be performed since it has been deprecated. Provides Service information directly to the application. This event provides a means for a vendor-specific CAT Service to provide events to the application that are not otherwise supported by the Control. Notifies the application that a CAT error has been detected and suitable response by the application is necessary to process the error condition. Notifies the application that the queued output request associated with the OutputID attribute has completed successfully. Notifies the application that there is a change in the power status of the CAT device. Provides Service information directly to the application. This event provides a means for a vendor-specific CAT Service to provide events to the application that are not otherwise supported by the Control. Event number whose specific values are assigned by the Service. Additional numeric data. Specific values vary by the EventNumber and the Service. This property is settable. Additional data whose usage varies by the EventNumber and Service. This property is settable. Notifies the application that a CAT error has been detected and suitable response by the application is necessary to process the error condition. Error code causing the error event. Extended Error code causing the error event. It may contain a Service-specific value. Location of the error. Error response, whose default value may be overridden by the application. (i.e., this property is settable). Notifies the application that the queued output request associated with the OutputID attribute has completed successfully. The ID number of the asynchronous output request that is complete. The EventUnits property is updated before delivering. Notifies the application that there is a change in the power status of the CAT device. Reports a change in the power state of the CATdevice. An error occurred during asynchronous action. Retries the asynchronous processing. The error state is exited. Clear the asynchronous processing. The error state is exited. An error was returned from the approval agency. The detail error code is defined in CenterResultCode. The command sent to CAT is wrong. This error is never returned so long as CAT control is working correctly. CAT was stopped during processing by CAT reset key (stop key) and so on. Communication error has occurred between the approval agency and CAT. Daily log was too big to be stored. Keeping daily log has been stopped and the value of DailyLog property is uncertain. Electronic Money Device: Because the balance is insufficient, it cannot close settlement. Electronic Money Device: A failure will occur if a settlement amount is attempted that is over the chargeable amount of the charge account. DealingLog is enough capacity. DealingLog is nearly full. DealingLog is full.