Master planning 'Plan version cleanup' batch job

(0) Share

Report

Posted on by Tim Schofield

Running a Master scheduling batch job every night. The system is generating a 'Plan version cleanup' batch job, but I am getting Alerts and records in the Batch job log that I don't really need (recording successful end).

Is there any way to control the Alter and logging behaviour of this batch job?

(and by the way, what is it doing?)

Thanks

Tim

*This post is locked for comments

I have the same question (0)

All responses (10)

Answers (0)

SYNAPIS IT 1,257 on at

Like (0)

Report

Hi Tim,

Did somebody answer you about 'Plan version cleanup' ? I'm interested also in that matter - perhaps you found explanations somewhere ?

Regards

Witold

Was this reply helpful? Yes No
Tim Schofield on at

Like (0)

Report

Hi, no. But later I found out that in AX 2012 you have Master plans, and Plan versions. Each master plan has an active version, so obviously that batch job is physically deleting records related to inactive plan versions. If you have large master plans it'd be worth checking that the delete is working correctly, especially if you're on a version before R2.

Tim

Was this reply helpful? Yes No
SYNAPIS IT 1,257 on at

Like (0)

Report

Thank you for answer, I'm working on R2 CU6 then I hope that it works properly :) How can I know which version of plan is 'active' ? Do you mean definition of plan ? or particular set of results of plan done (I mean planned orders, action etc.). Have you tried stop this cleaning ?

Looking forward for your answer :)

Witold

Was this reply helpful? Yes No
ProjMan 35 on at

Like (0)

Report

Hi I am in the same situation where MRP is now giving the following message

"active plan version does not exist for plan xxxx" (xxxx is our master plan name currently "static2"

However like yourself we cannot find where the version is controlled. I am in AX 2012 Cu1

I would be keen to see the responses too on this thread to see if this provides any answers.

Was this reply helpful? Yes No
Tim Schofield on at

Like (0)

Report

Take a look at the table ReqPlanVerion - unhelpfully the 'Active' flag isn't visible by Default.

Have you tried to fix the 'active plan version does not exist for plan' error by deleting the plan at Master planning > Periodic > Plans > Delete plan.

Was this reply helpful? Yes No
Haseeb 95 on at

Like (1)

Report

This is quite a strange problem but occurs mostly at the time of creating a new master plan. I deleted the master plan and created the new one - instantly it was active. There were two entries [REQPLANVERSION] table with the sames details but the difference was just in active tab. Hope that helps :)

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I have the same problem (getting "Active plan version does not exist for plan Default"). You say "the difference was just in active tab" - what/where is the "active tab" I can't find it anywhere.

Thanks,

Gary

Was this reply helpful? Yes No
Giridhar on at

Like (0)

Report

Hi Garys,

I face the same issue when i run the master scheduling with empty itemset. If you resolved this issue, Can you please tell me the procedure how to resolve this?

Was this reply helpful? Yes No
Suggested answer

Brandon Wiese 17,788 on at

Like (0)

Report

I would also like to get rid of the Plan version cleanup entries in the Batch log. I just did a quick source code search, and I believe (but have not yet tested), that these jobs are being scheduled in Classes\ReqBackgroundJobService\methods\addPlanVersionCleanupTask.

In particular, the line

this.batchHeader().addTask(cleanupJob);

should probably be followed by something like

this.batchHeader().parmAlerts(false, true, true, false, false);

where the first false indicates "on success". Ideally you could instead just set the alerts on the child Plan version cleanup jobs identical to the parent job so they all behave the same.

Was this reply helpful? Yes No
ron_ron 180 on at

Like (0)

Report

Hi,

Anyone resolve the issue mentioned above? The Plan version clean up job automatically created after the run of Master Scheduling batch job. Can anyone define the cause of this issue?

Thanks,

ronron

Was this reply helpful? Yes No