Professional Documents
Culture Documents
Worldwide +1-701-281-6500
www.microsoft.com/dynamics
This document is provided as-is. Information and views expressed in this document, including URL and
other Internet Web site references, may change without notice. You bear the risk of using it.
Some examples depicted herein are provided for illustration only and are fictitious. No real association or
connection is intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property in any Microsoft
product. You may copy and use this document for your internal, reference purposes.
Microsoft, Microsoft Dynamics, and the Microsoft Dynamics Logo are trademarks of the Microsoft group
of companies.
Enter parameters
Use parameters to configure Retail Scheduler for your particular business. Parameters provide
default settings and values that can often be changed in individual records.
Note
For more information about the record types mentioned in this topic, see the
appropriate topics later in this part.
1. Click Retail scheduler > Setup > Parameters.
2. Enter information referring, if necessary, to the following.
Distribution types
The distribution type for a table controls how that table is distributed. The following distribution
types are available:
All distribution locations Changes to records in the table are sent to all locations.
Same as parent distribution Changes are distributed based on the distribution type of the
table that is the parent of the table. Use this distribution type for records that must always
be accompanied by other records. For example, items and bar codes for the items must
have the same data distribution. If you select this distribution type, you cannot set up
Groups to distribute to lists for specific records in the table.
Important
If you select this distribution type, you must set up table links that describe the
relationship between the child table and its parent table. For more information, see
"Set up table links" later in this topic.
By distribution groups Changes are distributed based on the Groups to distribute to list
for the changed record in the table. For example, changes made to an item are sent only to
the distribution locations that are included in the groups list for that specific item.
Important
Typically, you select this distribution type only for tables at the top of the table
distribution hierarchy.
Before selecting this distribution type, verify that a Groups to distribute to list is
available for the records contained in the table. You must set up the Groups to
distribute to list for every record in the table, either in the individual record or in a
groupsuch as a store group or retail hierarchy groupthat contains the individual
record. Records for which the groups list is not set up are not distributed. For more
information, see "Set up the 'Groups to distribute to' list for each record" later in
this section.
No distribution Changes to the table are not distributed, regardless of the Groups to
distribute to list for the changed record. If a table with this distribution type is the parent of
another table and the child table is set to Same as parent distribution, changes to the child
table are not distributed.
Types of jobs
There are four types of jobs:
Action (A) jobs A jobs send data from the head office to stores. The changes included in
the jobs are those that have been tracked by the action filters that you set up. The locations
that receive the jobs are determined by the distribution settings for the changed records (or
their parent records).
Custom (C) jobs C jobs run a specified custom class. Custom classes can be created by
Microsoft partners and must contain support to be run in Retail Scheduler. Two C jobs are
included in Retail Scheduler by default, C-1000 (Send email receipts) and C-1020 (Convert
Preactions).
Normal (N) jobs N jobs are not dependent on actions. They delete all existing data in the
destination tables and then insert updated data. N jobs send data from the head office to
the locations specified in the include list for the job.
Pull (P) jobs P jobs pull datasuch as sales and inventory data from the distribution
location specified in the job and insert it into the head-office database. You need one P job
for each terminal or store database.
Replication counters
A replication counter is a marker that is used by an A job or P job to determine which records to
process. Replication counters are specific to each subjob within the job.
For A jobs, the record ID of the last processed action is stored in a table in the head-office
database. The subsequent run of each job starts with the next action after that. Typically, you do
not need to set up these replication counters; however, if you want to, click Retail scheduler >
Setup > Initial replication counters.
For P jobs, the previous replication counter is stored in the source table in the terminal or store
database. The next run of the P job starts with the replication counter that is one higher than
that value.
Configure subjobs
To configure a subjob, complete the following tasks:
Create or modify a subjob.
Set up the transfer field list for each subjob.
Note
You can reuse a single subjob in several jobs.
Configure jobs
Jobs should contain subjobs that are related. For example, the Currency job contains subjobs
that update currencies and exchange rates. Jobs should also contain subjobs that use replication
methods that are consistent with the type of job. As a general rule, N jobs and P jobs should
contain subjobs with Normal replication, and A jobs should contain subjobs with By actions
replication.
1. Click Retail scheduler > Common Forms > Scheduler job.
2. Press CTRL+N to create a new job or select the job that you want to modify.
3. Enter information referring, if necessary, to the following.
Monitor jobs
Use the Scheduler log form to check job status.
1. Click Retail scheduler > Common Forms > Scheduler job.
2. Select the job that you want, and then click Scheduler log.