DTM order

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 DTM order can be updated, i.e. programmed, changed or cleared, with this program. Data which has already been stored can also be displayed for information.

Buttons "From/to branch", From/to branch group" and "For all branches" can be used to copy stored DTM orders. Select the DTM order required and depress the appropriate button.

The DTM order defines which files are to be transferred automatically between head office and branches (Multi-installation) at a specified point in time.

Note:
The functionality of the DTM upgrade in the MICROS Retail OSCAR POS program is retained after entry of path ..\fglDTM in the environment variable OSCAR POS_FGLPATH in the 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 in update program System -> Menu -> Applications.

Note:
A Processing unit of type Oscar Client should be programmed for the application program type DTMClient. The name of the application (DTMClient) 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 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 a DTM order is 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 - 9999

Select the number of the target branch for which a DTM order is 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 a number for the DTM order in this field. If a new DTM order is to be programmed, a free no. should be entered in the key fields. The number must be unique.

Changes and clear operations can be carried out from entry of the data record no. in the key fields. If the number is not known, the data record can be selected with the search function.

---

Text

Entry range permitted: alphanumeric max. 30 pos.

Enter the name for the DTM order in this field. The name chosen should be informative. 

---

Date

Entry range permitted: DDMMYYYY (Tag, Monat, Jahr)

Enter the date on which the DTM order is to start.

Note:
Program DTM Preset defines the time intervals during which a search is required for unfinished DTM orders for so that they can be started. The order will only be completed when the date and time for the DTM order has been reached.

---

Time

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

Enter the time at which the DTM order is to start.

---

Time valid

Entry range permitted: numeric, 0 - 24

Enter the number of hours to define the period in which the DTM order can be started.

---

SW-Update Name

Entry range permitted: alphanumeric, max. 30 chars.

Enter the name of the file which has been stored for the software update in the appropriate source directory.

---

Int.order spec.

Entry range permitted: alphanumeric, max. 20 chars.

The name of the internal order for the type of DTM order is entered here.

The name of the internal DTM order is selected from field Defaults by clicking on the button and selecting the appropriate order from the list.

The following commands are available for DTM orders.

The following DTM orders can be used depending on the environment variables "OSCAR_OPTIONS=" :

Hinweis:

A database update of the sub-installation can be performed only if the respective system units are accessible via the TCP/IP network and a connection exists between the MICROS Retail OSCAR POS Database Server and its sub-installation. Please check in the program "system unit" of the related installation, whether the IP address is properly registered.

DTM Order	OSCAR_OPTIONS=	Description
GETSTATISTIC		GETSTATISTIC = Pick-up of statistics data from the branch processor of the selected branch. Beverage: During pick-up of transactions SupplOrder is not possible. Refund receipts are marked in head office as cashed in, if applicable.
UPDATEINSTALLATION		UPDATEINSTALLATION = Update of basic data of the branch processor in the stated branch. An update of basic data in the branch can be done with order type "UPDATEINSTREMOTE" (see UPDATEINSTREMOTE and application "Remote Update").
GETSTATISTICDATE		GETSTATISTICDATE = Pick-up of statistics data  from the branch processor of the selected branch for a specified period (from date / to date)
PUTFILE		PUTFILE = Sending of a file from central processor to the branch processor of the selected branch. (File name and source directory must be entered in the fields provided and they must exist on the hard disk of the system unit concerned).
GETFILE		GETFILE = Pick-up of a file from the branch processor of the stated branch to central processor. (File name and source directory must be entered in the fields provided and they must exist on the hard disk of the system unit concerned).
GETUPDATESTATUS		GETUPDATESTATUS = (File name and source directory must be entered in the fields provided and they must exist on the hard disk of the system unit concerned).
GETUPDATES		GETUPDATES = Pick-up of basic data changes from the main installation (head office). In this case, a DTM client must be active on the branch processor and a DTM order with command "GETUPDATES" must be programmed.
GETDTMSTATE		GETDTMSTATE = If the new method for "Update Installation" and "Get statistik" is applied the following status data can be transferred from the branch to head office with this DTM order: Process units status, Branch status, Branch status / Date, Statistics sent, Statistics received and Terminal Grand Total. These data records are marked with status Sent after successful recording in head office. Further help on this subject can be found in the documentation Data integrity MICROS Retail OSCAR POS.
UPDATEINSTREMOTE		UPDATEINSTREMOTE = Update the basic data in the branch with an application of type "RemoteUpdate". A processing unit of type Client must be programmed in the branch as this will start the application "Remote Update". Order type UPDATEINSTREMOTE in head office initiates an operation in the branch in which the log files are read remotely by head office (in blocks of 20 kb) and the database operations for update of basic data are carried out in the branch If the environment variable UPDATERDEBUG=Y is set in file "oscar.ini", the following messages are written into file "errlog": When the application starts "Remote Update". All 100 data records. When the application is ended. The normal messages are also written into the DTM Logbook.
UPDATEPRICES		UPDATEPRICES = Update of prices of a specified price list in the branch concerned.
GETCREDITCARD		GETCREDITCARD = Pick-up of all new credit card transactions (CreditCHead) in the branch by head office. Note: The functioning of this DTM order is the same as the function "Get credit cards" in program Installation.
PUSHSTOCKMOVEBROUT		PUSHSTOCKMOVEBROUT = Sending goods movements to other branches. All stock items with the status "Ready for transfer" will be moved out. NOTE: Movement data is displayed in program Stock -> Move -> Move branch
GETLOCALUPDATES		GETLOCALUPDATES = The modified basic data is transferred from a sub-installation (branch) to the main installation (head office) with this DTM order. As opposed to the Update Installation in which the modified data is transferred from the main installation (head office) to the sub-installation (branch) the modified basic data of a sub-installation (branch) are picked up with this function. Note: The functioning of this DTM order is the same as the function "Get local updates" in program Installation.
UPDATECUSTSTATE		UPDATECUSTSTATE = The status data for customers and the customer status per branch is transferred from each branch to head office with this DTM order. The customer status data whose status is newer than the one sent last will be sent to the branches.
GETTRANSITSTMOBROUT
SENDUI		SENDUI =  A frame changed by head office can be sent with this order to the branch(es). During processing the system checks which number exists in the branch for this frame and then uses this frame no. or a new one. Therefore, "normal" basic data transfer per UPDATEINSTALLATION cannot be used. Note: During an installation the numbers of the frames in head office will differ from those in the branches (different dofgl’s carried out at different times, other frames added, etc.). If, for example, individual data records of an "Article" frame meet up after a change with frame no. 4567 in the branch with frame no. 4567 – which, however, belongs to the objectt "Supplier“ the data integrity is no longer guaranteed. UIFrame changes in head office should always be carried out in single user mode only (or the database tables in program System -> Configuration -> Inst. Update Param. should be excluded from  UPDATEINSTALLATION).
PUSHTIME		PUSHTIME = This DTM order checks whether the date and the time in a branch differ from the date and the time in head office and, if applicable, the date and time in the branch will be reset.
GETCUSTSTATE
GETSTOCKITEMSTATE
UPDATESTATE	Cactus
GETSIEXPORT		GETSIEXPORT=  With this DTM-Order the status data from finance exports per branch can be transferred from each branch to the central
GETTRANSXML	GHM	GETTRANSXML = Pick-up of all XML transaction files from the branches. Note: At GHM the transactions are moved out in the branches in XML format. These files are processed by the GHM background system.
GETSTATXML	GHM	GETSTATXML = Pick-up of XML statistics data from the branches. Note: At GHM the statistics data, terminal, cashier and stock data in the branches is moved out in XML format. These files are processed in the GHM background system.
GETONLYTRANS	GHM	GETONLYTRANS = Pick-up of all transaction data which has not been moved out as XML from the branches
GETTRANSACTIONS	Backwelt	GETTRANSACTIONS = Pick-up of all recorded transactions of the current recording day for the transaction table entered under the file name. Transactions picked up in this way are then available in head office on the same day, i.e. before the evening GETSTATISTIK and no permanent  GETSTATISTIK is necessary. Note: If no table has been entered a GETTRANSACTIONS picks up all recorded transactions for the current day (backoffice and e journal). This is used by Backwelt to allow them to pick up recorded orders during the day and prior to the normal nightly DTM so that they can be handed over to SAP.
GETORDER	Beverage	GETORDER = Pick-up of supplier orders (SupplOrder) which have been recorded but not yet sent from the branches.
GETORDERGS	Beverage	GETORDERGS = Pick-up of vouchers for the current day from the branches. The transaction no. is updated in head office.
GETTREND	Beverage	GETTREND = Pick-up of the following data from the branches if the last storage took place after the last execution of this order: Item turnover per profit center (ArtTurnProC) Item period per branch (ArtTimTBrch) Item turnover per operator (ArtTurnOper) Stock article status (StockItemSt)
CREATEDELIVERY	Beverage	CREATEDELIVERY = The data records of the import table "IDelivery" with a ConfimDate equal to the day’s date become deliveries(Delivery) and delivery positions (IDelivPos -> DelivPos) in the branch.
MAKECORRDELIVERY	Beverage	MAKECORRDELIVERY = CDeliveries are correction recordings for Deliveries. They are generated from import table ICDelivery and are recorded immediately in the branch.

---

Regional center

Entry range permitted: numeric, 1 - 99999

Only enter one branch in this field if this DTM order is only to apply to this branch.

If the number is not known the data record can be selected via Search.

---

Every (specify time interval)

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

Enter a time in this field to define when the DTM order is to start.

---

Time interval

Field with firmly defined selection options

Select one of the intervals suggested by the system. This defines at what intervals a DTM order is to be executed, independent of the date and time defined.

The following intervals are offered:

• Once on = the DTM order is carried out only once at the time and on the date defined in fields "as from date" and "Time".
• Every Monday = the DTM order is carried out every Monday. This is dependent on the entries in fields "as from date" and "Time".
• Every Tuesday = The DTM order is completed every Tuesday. This is dependent on the entries in fields "as from date" and "Time".
• Every Wednesday = The DTM order is completed every Wednesday. This is dependent on the entries in fields "as from date" and "Time".
• Every Thursday = The DTM order is completed every Thursday. This is dependent on the entries in fields "as from date" and "Time".
• Every Friday = The DTM order is completed every Friday. This is dependent on the entries in fields "as from date" and "Time".
• Every Saturday = The DTM order is completed every Saturday. This is dependent on the entries in fields "as from date" and "Time".
• Every Sunday = The DTM order is completed every Sunday. This is dependent on the entries in fields "as from date" and "Time".
• Every day = The DTM order is completed every day. This is dependent on the entries in fields "as from date" and "Time".
• Daily except Sundays = The DTM order is completed every day except Sunday. This is dependent on the entries in fields "as from date" and "Time".
• Daily except Sat + Sun = The DTM order is completed daily except Saturday and Sunday. This is dependent on the entries in fields "as from date" and "Time".
• Last day of month = The DTM order is always completed on the last day of the month. This is dependent on the entries in fields "as from date" and "Time".
• First day of month = The DTM order is always completed on the first day of the month. This is dependent on the entries in fields "as from date" and "Time".
• Every 2 months = The DTM order is completed every 2 months. This is dependent on the entries in fields "as from date" and "Time".
• Every 3 months = The DTM order is completed every 3 months. This is dependent on the entries in fields "as from date" and "Time".
• Half-yearly = The DTM order is completed half-yearly. This is dependent on the entries in fields "as from date" and "Time".
• Annually = The DTM order is completed annually. This is dependent on the entries in fields "as from date" and "Time".
• As soon as possible = The DTM order is carried out for every new search for unfinished DTM orders. The time interval for a new search for unfinished DTM orders is defined in program Application -> DTM -> DTM presets. This type of time interval should only be used for DTM orders which are carried out in the branch (see Branch DTM).
• Every (specify time interval) = The DTM order will be executed at the time stated in field "Every (specify time interval) ".

---

As from date

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

The entry in this field is only possible if a DTM order of type GETSTATISTICDATE has been selected. It is then possible to pick up statistics data for a specific period of time in the past from a branch.

This method becomes necessary if the POS terminals of a branch are operated in offline mode and if the turnover data was not available on the branch server at the time data is normally transferred to head office.

---

To date

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

The entry in this field is only possible if a DTM order of type GETSTATISTICDATE has been selected. It is then possible to pick up statistics data for a specific period of time in the past from a branch.

This method becomes necessary if the POS terminals of a branch are operated in offline mode and if the turnover data was not available on the branch server at the time data is normally transferred to head office.

---

From time

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

Enter a time in this field to define the earliest time the DTM order can be started.

---

To time

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

Enter a date in this field to define the earliest date the DTM order can be started.

---

Interval (minutes)

Entry range permitted: numeric, 0 -1440

The entry in this field defines the number of minutes after which the DTM order is to be repeated. This value is only applied if a time is entered in fields "From time" and "To  time".

---

File name

Entry range permitted: alphanumeric max. 20 pos.

Enter the file name to be transferred in this field. This entry can only be made if a DTM order of type PUTFILE (= send file) or GETFILE (= pick up file) has been selected.

Note:
File names can also contain so-called wild cards, e.g. "*.txt" or "trans*.*". "*.*" must be stated if complete directories are to be sent.

---

Source directory

Entry range permitted: numeric 1 - 999

The number of the source directory which is to store the files to be transferred should be entered here.

The number for the appropriate source directory is chosen by clicking onto the button and selecting the number required from the choice offered in the window. The path for the source directory is updated with program DTM directory.

The directory must be available on the hard disk of the appropriate system unit.

---

Target directory

Entry range permitted: numeric, 1 - 999

A number should be entered in this field to identify the target directory in which the files to be transferred are to be stored.

The no.of the target directory can be selected by clicking on this button and selecting the no. required from the list which appears. The path for the target directory is updated with program DTM directory.

The directory must exist on the hard disk of the appropriate system unit.

---

Price list

Entry range permitted: numeric, 1 - 9999

---

IP address

Entry range permitted: alphanumeric, max. 20 chars.

---

Form no.

Entry range permitted: numeric, 1 - 99999999

Enter the no. of the form for the update program which is to be sent to the branch with DTM order "SENDUI".

---

Central DTM

Button activated: This DTM order can be completed in the branch (sub-installation).
Button deactivated: This DTM order can only be completed in head office (main installation).

Note:
Normally, all DTM orders are created in head office. To ensure that DTM orders can be executed in the branch they must firstly be sent to the branch with function "Update Installation". Only those orders for which the option "Central DTM" has been set can be created in the Branch DTM orders.

 Click on the graphic for further help with setting up Branch DTM orders.

The file will be deleted from the source directory after execution of this order.

---

Delete file

Button activated: The file in the source directory will be deleted after the DTM Order has been completed.
Button deactivated: The file in the source directory will not be deleted after the DTM Order has been completed.

---

Backw. Compat.

Button activated:. For compatibility purposes no test of files and folders will be done.
Button deactivated: The test of files and folders will be done.

Note:
When using the function "PUTFILE" and "SENDFILE" a test of files and folders will be done on newer MICROS Retail OSCAR POS releases due to compatibility purposes. This test must be deactivated if an update to earlier releases should be made, to avoid any errors.

---

No file no err.

Button activated:. When using the function "PUTFILE" and "SENDFILE" the order will be marked as successful, even if no file exist.
Button deactivated: When using the function "PUTFILE" and "SENDFILE" the order will not be marked as successful if no file exist.

---

Index

• As from date (GetStatistic)
• Backw. Compat.
• Branch
• Central DTM
• Company
• Date
• Delete file
• Every (specify time interval)
• File name
• Form no.
• From time
• Int.order spec.
• Interval
• Interval (minutes)
• IP address
• No file no err.
• Order (internal)
• Order ID no.
• Price list
• Regional center
• Source directory
• SW-Update Name
• Target directory
• Text
• Time
• Time interval
• Time valid
• To date (GetStatistic)
• To time

---

MICROS Retail Deutschland GmbH
Salzufer 8
D-10587 Berlin

-Germany-