DTM result

The program description deals with the following:

Remarks on Program function
Remarks on Data fields
Use Index to find the field details required.

Remarks on program function

The data of the DTM result can be viewed or updated, i.e. changed or cleared, with this program. Data which has already been stored can also be displayed for information.

Every result of a DTM order is written into a file protocol and the status is shown. Details on the DTM order concerned can be obtained with program DTM history by clicking onto the button DTM history. The system then changes to the update program.

Note:
The functionality of the DTM upgrades in the MICROS Retail OSCAR POS program is retained after entry of path ..\fglDTM in the environment variables OSCAR_FGLPATH of initialisation file oscar.ini. Call up the FGL file "dofglDTM.fgl" with the language required (e.g. oscar dofglDTM.fgl Deutsch) so that the windows of the DTM update programs required are generated. The application program DTM has to be configured with update program System -> Menu -> Application.

Note:
A Processing unit of type Client should be programmed for the application program type DTMClient. The name of the application should be entered in field Program name. The option "with graphic" should be set for the relevant processing unit so that the DTM order can be shown on the screen.

Remarks on data fields

The following description deals with all available options for update of this basic data.

As with nearly all programs the following also applies here:

The entry mask for this program may differ in your MICROS Retail OSCAR POS program. Some data fields may be missing.
There may be defaults or firmly defined selection options for some data fields. These cannot be updated in the current program.
Fields with enforced entry defined are to be found in the entry masks as are fields where entry is optional.
If the data record is updated over several pages of entry masks, the dialog window is reached by clicking onto the appropriate Button with <Mouse key 1>.
The same procedure also applies to call up of another update program from this program.
In some cases you may find so-called "Switches" which are activated or deactivated by the user with <Mouse key 1>, depending on the setting. Activated switches have a dark top, deactivated switches are lighter.

Company

Entry range permitted: numeric 1 - 9999

Select the number of the company for which DTM orders are to be processed. If the number is not known, the data record can be selected with the search function.

Branch

Entry range permitted: numeric 1 - 99999

Select the number of the branch for which the DTM results are to be processed. If the number is not known, the data record can be selected with the search function.

Order ID no.

Entry range permitted: numeric 1 - 99999

Enter the number of the DTM order for which the DTM results are to be processed.

Changes or clear operations can be carried out by calling up the data record from a number entry in the key fields. If the number is not known, the data record can be selected with the search function.

Order text

Entry range permitted: alphanumeric max. 30 pos.

The name of the DTM order as stored in program DTM order appears in this field.

Order (internal)

Entry range permitted: alphanumeric max. 20 pos.

The name of the internal order for the relevant DTM order appears in this field.

The name of the internal order for the DTM order is selected in field Order (internal) in program DTM order.

The following commands are possible for a DTM order:

GETSTATISTIC = picking up statistics date from the branch processor of the selected branch
UPDATEINSTALLATION = update of basic data of the branch processor in the branch selected.
GETSTATISTICDATE = picking up the statistics data from the branch processor for a specified period of time (as from date/to date)
PUTFILE = sending a file from the central processor to the branch processor of the branch selected. (File name and source directory must be entered in the appropriate fields and must be available on the respective hard disks of the system units).
GETFILE = picking up a file from the branch processor of the branch selected by the central processor (file name and source directory must be entered in the appropriate fields and must be available on the respective hard disks of the system units).

Result text

Entry range permitted: alphanumeric max. 30 pos.

The text for the result of the DTM order is displayed in this field.

The following texts appear for the result of the transfer:

OK = file or update installation transferred successfully
NoInstallation =configuration objects missing during calculation of IP no.
NoDbServer = configuration objects missing during calculation of IP no.
NoSysUnit = configuration objects missing during calculation of IP no.
NoNetAddr = configuration objects msising during calculation of IP no.
BranchDBOffline = branch OFFLINE, no communications can be established
BranchStatistic + Datum = GetStatistic completed successfully, to date all data in head office
noData = GetStatistic was successful, but no new statistics data (branch was closed or repeat dialling).
BranchDBZapped = communications established successfully, but nothing has been recorded in this branch
ErrorPutFile = repeated error in PUTFILE (access rights ??)
ErrorGetFile = repeated error in GETFILE (access rights ??)
ErrorRemoteFile = repeated error (applies to PUTFILE and GETFILE), butt error source on branch side.
TxtNoOwnBranch = a GETSTATISTIC on own branch is not permitted.

Errors with GETSTATISTIC

TxtNoLocalPayment = the base payment type of head office cannot be read.
TxtNoRemotePayment = the base payment type of branch cannot be read.
TxtOffline = OFFLINE occurred during transfer.
TxtErrorOnCommit = the table "BranchState" cannot be written in the branch

Errors with UPDATE installation

TxtOfflineRmFile = When central LOGFILES were read OFFLINE occurred.
TxtNoRmFile = System error – object for remote file access missing
TxtError1 - TxtError4 = as known (see Tips, Tricks, Error remedy, System messages Case 12)

Details of the DTM order can be obtained from program DTM history by clicking onto the button DTM history. The system then changes to this program.

Retries

Entry range permitted: numeric 0 - 99

The number of retries possible is shown in this field.

It is done

Switch active: This DTM order has been completed done.
Switch deactivated: This DTM order was not completed done.

This option is set automatically if the order has been completed or if the number of retries possible has been reached. The number of retries is set in program DTM presets. A DTM order marked as done does not necessarily mean that data transfer was successful. Only if the additional switch "Success" is on, the DTM order has been completed done successfully. Details about a successful transfer of a DTM order can be found in program DTM history.

Note:
This switch can also be used to repeat a completed DTM order. If the switch has already been set, the setting can be reversed.

Success

Switch active: This DTM order has been completed successful.
Switch deactivated: This DTM order was not completed successful.

Only if the two switches "Its is done" and "Success" is on, the DTM o rder has been completed done successfully.

Date last successful

Entry range permitted: DDMMYYYY (day, month, year)

The date of the last successful execution of this DTM order is displayed in this field.

Date no success

Entry range permitted: DDMMYYYY (day, month, year)

The date of the last unsuccessful execution of this DTM order is displayed in this field.

Date last try

Entry range permitted: DDMMYYYY (day, month, year)

The date of the last try for this DTM order is displayed in this field.

Successful at

Entry range permitted: HHMMSS (hour, minute, seconds)

The time of the last try for this DTM order is displayed in this field.

MICROS Retail Deutschland GmbH
Salzufer 8
D-10587 Berlin

-Germany-