Scheduler subjobs (form)

  • Article

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack

Click Retail > Setup > Retail scheduler > Scheduler subjobs. Click New to create a new subjob.

Retail Scheduler can monitor specific tables and table fields for modifications, and then use subjobs to distribute the modifications to stores that are affected by those modifications. Use this form to create subjobs that distribute data modifications in selected tables to specific locations.

Task that uses this form

Configure jobs and subjobs in Retail Scheduler

The following tables provide descriptions for the controls in this form.

Tabs

Tab

Description

Setup

Enter details about the tables, locations, and replication method that are used to distribute data to stores.

Replication

This control is available only in AX 2012 R2 and AX 2012 Feature Pack.

Set limits for action and replication counters.

Buttons

Button

Description

Transfer field list

Open the Field list form, where you can map the source table fields to destination table fields. You can also select a conversion type, if the values must be converted.

From table filters

This control is available only in AX 2012 R2 and AX 2012 Feature Pack.

Open the From table filters form, where you can create a filter to limit the table records that are included in the subjob.

Copy scheduler subjob

Copy the settings of the selected subjob to a new subjob.

Create staging table

If a destination table is specified in a job, and if the Pull data check box is selected for the job, create a staging table for the destination table.

In Microsoft Dynamics AX 2012 R3, the Application Object Server (AOS) uses staging tables before it writes transactions to the database.

In AX 2012 R2 and AX 2012 Feature Pack, Synch Service uses staging tables before it writes transactions to Microsoft Dynamics AX. You must create a staging table every time that you change a job that pulls data into the Microsoft Dynamics AX database.

Scheduled by

Open the Scheduled by form, where you can view the jobs that include the selected subjob.

Fields

Field

Description

Subjob number

Enter a unique identifier for the subjob.

Description

Enter a name for the subjob. The name can contain only alphanumeric characters. The name cannot contain spaces.

Reference only

This control is available only in AX 2012 R3.

This field is available only in environments that use multi-version POS support.

When this check box is selected, it indicates that the table is used only for reference when determining the data changes that must be distributed through Commerce Data Exchange.

For example, assume that the data to be distributed is contained in Table A. To calculate the changes in Table A, both Table A and Table B must be analyzed. In this case, you would create subjob A to distribute data from Table A. You would also create subjob B and mark the reference-only check box. Changes are tracked for Table B, but no data is distributed from Table B.

Replicate DataAreaID

Select this check box to replicate the company account for jobs that send data from the Microsoft Dynamics AX database.

In most cases, this option should not be selected. Select this option only if the Microsoft Dynamics AX table is organization-wide (does not have a DataAreaId column) and the table in the channel database is company-specific (has a DataAreaId column).

In AX 2012 R3, this field is available only in environments that use multi-version POS support.

Pull data

Select this check box only for subjobs that read data from the channel database and write data to the Microsoft Dynamics AX database.

Retail channel schema

Select the type of channel that the subjob is for. The following channel types are available:

  • AX 2009 POS – A POS channel in AX 2009.

  • AX 2012 Feature Pack POS – A POS channel in AX 2012 Feature Pack.

  • AX 2012 R2 Online Channel – An online channel in AX 2012 R2.

  • AX 2012 R2 POS – A POS channel in AX 2012 R2.

  • AX 2012 R3 – A POS or online channel in AX 2012 R3.

Channel table name

The name of the table in the channel database.

Microsoft Dynamics AX table name

The name of the table in the Microsoft Dynamics AX database.

Temporary table

The name of the staging table.

In Microsoft Dynamics AX 2012 R3, the Application Object Server (AOS) uses staging tables before it writes transactions to the database.

In AX 2012 R2 and AX 2012 Feature Pack, Synch Service uses staging tables before it writes transactions to Microsoft Dynamics AX.

Field for DataAreaID

This control is available only in AX 2012 R2 and AX 2012 Feature Pack.

Select the field that contains the identifier for the company account.

This field is not usually required. However, this field can be used for tables for which the SaveTableByCompany property is set to No, but that contain DataAreaId as a foreign key.

Replication method

This control is available only in AX 2012 R2 and AX 2012 Feature Pack.

Select the method that is used to determine which data is distributed:

  • Normal – Replicate all records from the source table to the destination table for the selected distribution location. Jobs that use this replication option delete the data in the destination table and replace it with the data from the source table. Use this option to replicate data to a new location, and to update a location with a full data set. You can use this option for jobs that send data from the Microsoft Dynamics AX database, and for jobs that pull data from distribution locations into the Microsoft Dynamics AX database.

  • By actions – Replicate only the records that have been modified since the last replication. Use this option together with action filters and table distributions to collect modifications that are made to specific tables and specific table fields. Use this option for jobs that send data from the Microsoft Dynamics AX database to distribution locations.

Delete

This control is available only in AX 2012 R2 and AX 2012 Feature Pack.

Select this check box to delete records in the destination table before data is inserted.

Insert

This control is available only in AX 2012 R2 and AX 2012 Feature Pack.

Select this check box to add the source records as new records in the destination table.

Note

The Delete and Insert check boxes do not apply to jobs that use a replication method of By actions. For most jobs that use a replication method of Normal, select both the Delete and Insert check boxes. For jobs that pull data into the Microsoft Dynamics AX database, select only Insert.

Enabled

This control is available only in AX 2012 R2 and AX 2012 Feature Pack.

Select this check box to include the subjob in a scheduler job.

Transfer field list exists

This control is available only in AX 2012 R2 and AX 2012 Feature Pack.

A selected check box indicates that the list of transfer fields contains data.

From/to filters exist

This control is available only in AX 2012 R2 and AX 2012 Feature Pack.

A selected check box indicates that you have selected table filters for a subjob.

Action counter interval

This control is available only in AX 2012 R2 and AX 2012 Feature Pack.

Enter the number of actions to process at the same time. Use this field to process actions in batches to improve performance. Enter 0 (zero) to process all actions that have been performed since the previous run.

Replication counter

This control is available only in AX 2012 R2 and AX 2012 Feature Pack.

From the fields in the table that you selected in the From table field, select a field that contains a sequential number.

This field applies only to jobs that pull data into the Microsoft Dynamics AX database.

Replication counter interval

This control is available only in AX 2012 R2 and AX 2012 Feature Pack.

Enter the number of transactions or other records to pull at the same time. Use this feature to pull records in batches to improve performance. Enter 0 (zero) to pull all actions that have been performed since the previous run.

This field applies only to jobs that pull data into the Microsoft Dynamics AX database.

Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).