Need to understand Functionality Distribution schedule job

(0) Share

Report

Posted on by Community Member

We are facing a problem in N 1040 job which we are running it from batch job configured from "Distribution schedule" of Microsoft Dynamics AX R3.

Problem Description:

1) It is not sending incremental data to stores.

2) We did not create any item at HQ but whenever batch job execute as per configured schedule it sends min 1300 records to 700 records at store which is not acceptable by client.

Please help and share any available document from Microsoft which contains functionality of Distribution schedule job of DAX R3.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Solozmar 796 on at

Like (0)

Report
You're stating your AX version is R3, but you're referencing an N job, which is pre-R3. N jobs run ALL data. A jobs run incremental data.

This article on Technet explains, from which I pasted this excerpt:

Action (A) jobs – A jobs send data that has changed from Microsoft Dynamics AX to channel databases. Data modifications are tracked as actions. The locations that receive the jobs are determined by the distribution settings for the records that changed or their parent records.

Use A jobs to distribute data incrementally. A jobs can be used to transfer data to a specific channel, or to customize the way that changes to tables are distributed. If the data in a table is company-specific, an A job sends only the rows that match the legal entity of the destination.

Normal (N) jobs – N jobs send data from Microsoft Dynamics AX to channel databases. N jobs do not depend on actions. Instead, N jobs send all data in a table. N jobs delete all existing data in the destination tables and then insert data.

Use N jobs to bulk copy data to all the channel locations in your organization. If the data in a table is company-specific, an N job sends only the rows that match the legal entity of the destination.

Was this reply helpful? Yes No
Martin Dráb 237,878 Most Valuable Professional on at

Like (0)

Report

I think you mean AX 2012 R3, so let me fix your version tag from "current version".

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks for your response Solomon Maricle . Apologize for typo N I've written earlier . Our AX version is 2012 R3 and we are using 1040 from batch job from distribution schedule . Not N - 1040

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Solomon Maricle / Martin Drab

Can you please share any articles where it is mentioned that Batch job for from distribution schedule can send incremental data?

The link you have shared already from MS clearly says that incremental data is sent by SQL changed tracking but I would like to know if we do not enable change tracking in SQL DB or table level then what would be the behavior of 1040 batch job from distribution schedule?

Further, we have not enabled Change tracking in SQL DB or at table level. We can seen that currently batch job from distribution is sending less data ( NOT FULL data)

At first it sends full data but then batch job started downloading less data approx 500 to 700 records.

Was this reply helpful? Yes No
Shafeeque P. 6,533 Moderator on at

Like (0)

Report

Did you manually disable change tracking in HQ DB? Change tracking is active by default. If you don't have the change tracking enabled, system should ideally send full data by throwing a warning that change tracking info is not available for the job. Also check what is the how long does the database retain change tracking info.

If you want to see what data is being send to the store, copy the data packet from working folder and extract it using DDPackView.exe app located in the async client folder.

This blog by Stephen Mann will give you a good idea about how async works in AX 2012.

Was this reply helpful? Yes No