The program description is divided up as follows:
The data of the Data Feed Parameter can be updated, i.e. created, changed or deleted, with this program. Data which has already been stored can also be displayed.
The MICROS Retail OSCAR POS application allows statistics data, status data and transaction data to be transferred permanently from the sub-installation to the main installation. Normally, this data is transferred to head office with function "getStatistic" after a new day in the sub-installation.
Note!
After creation of this program the data is only exported or imported after the branch status has been changed, i.e. after end of day. This ensures that the data import is not continued during a running day or after an abort on the same day.
Click on
the graphic for further help with creating Data
Feed Import.
The following description deals with all available options for update of this basic data.
As with nearly all other programs the following also applies here:
Entry range permitted: numeric 1 - 99999
Number of the installation for data feed import parameter.
Entry range permitted: alphanumeric max. 20 pos.
The directory path of the XML files must be entered in this field for data export and/or data import.
Please note:
The debug parameter " DATAFEEDDEBUG=255" in file "..\bin\oscar.ini" defines whether these files are also stored in this directory after being sent via Message Queuing.
Permanent storage of XML files is possible in file ..\bin\oacsr.ini as a result of the following parameter:
DATAFEEDDEBUG=255
Entry range permitted: alphanumeric max. 20 pos.
The name (hostname) of the target processor (main installation/head office) should be entered in this field for a sub-installation (branch).
Entry range permitted: alphanumeric max. 20 pos.
The name of the remote queue must be entered in this field for a sub-installation. The spelling of this name must be identical with the name of the local queue for the main installation.
Entry range permitted: numeric 1 - 999999
A value for the maximum length (in KB) of the XML file for export can be entered in this field. A new data record is created with an ascending number if the maximum file length is exceeded.
The file names of the XML files to be exported are assigned as follows:
File prefix |
Date of booking period |
Message number |
DF |
YYYYMMDD |
NNNN |
Entry range permitted: numeric 1 - 99999
The entry in this field can be a value in minutes for the interval before data feed import starts. The data is sent via message queuing after this interval has elapsed.
Entry range permitted: numeric 1 - 99999
The entry in this field can be a value in seconds for the interval before data feed import starts. The data is sent via message queuing after this interval has elapsed.
Button active: Data export
is done via Message Queuing.
Button deactivated: Data export is not done via Message
Queuing.
Button active: Statistics
data is exported via Message Queuing.
Button deactivated: Statistics data is not exported via
Message Queuing.
Please note:
If one of the three options Statistics, Status or Transaction is not active, no branch status will be sent to head office (main installation). This implies that the missing data has to be transferred to head office with function "getStatistic".
Button active: Status data
is exported via Message Queuing.
Button deactivated: Status data is not exported via
Message Queuing
Please note:
If one of the three options Statistics, Status or Transaction is not active, no branch status will be sent to head office (main installation). This implies that the missing data has to be transferred to head office with function "getStatistic".
Button active: Transaction
data is exported via Message Queuing.
Button deactivated: Transaction data is not exported via
Message Queuing
Please note:
If one of the three options Statistics, Status or Transaction is not active, no branch status will be sent to head office (main installation). This implies that the missing data has to be transferred to head office with function "getStatistic".
Button active: Log data is
stored to allow transaction data to be sent
Button deactivated: No log data is stored to allow transaction
data to be sent.
Please note:
Log data can be viewed via program Application -> Installation -> Button "RTDF Log" .
Button active: Log data is
stored for receipt of transaction data.
Button deactivated: No log data is stored to allow transaction
data to be received.
Please note:
Log data can be viewed via program Application -> Installation -> Button
"RTDF Log".