"auto-report as finsihed" and master scheduling

(0) Share

Report

Posted on by Cardona

Hi all!

I have a scenario including auto-report as finished and master scheduling. This was possible in AX3, but does not seem to exist in AX2012. Well, the do individually but do not seem to be working together like they used to in 3.0..

We want to set up item FG1 with components BOM1 and BOM2. FG1 will be ticked as a "auto-report” as finished.

When creating a sales order for FG1 we want the master scheduling to acknowledge the requirements, so we purchase items BOM1 and BOM2. But this is no longer working.. Could someone please confirm that AX2012 does not Support this scenario anymore?

And if so, do you have any other suggestion on how to handle the requirements for items BOM1and2?

We do not wand the components for FG1 to be specified on the sales order process, just FG1. And we do not want to start a production order for FG1.

Thanks!

Einar

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

andlit 15 on at

Like (0)

Report

Hi!

I have the same problem. When "Auto report as finished", the master planning is not suggesting an order for the BOM items.

Does anyone got a solution for this?

Was this reply helpful? Yes No
Suggested answer

Brandon Wiese 17,788 on at

Like (1)

Report
I used Auto report as finished quite a bit in AX 4.0, but not so much lately, so I was surprised by the post that it no longer generated a Planned production order. My first thought was maybe the item marked as Auto report as finished might have a default order type of Purchase order. When I tried it in AX 2012 R3 CU8, sure enough it did not generate a Planned production order. How odd. How else does one realize demand for components of the Bill of material?

Searching quickly through the Req classes, I found only two places where the AutoReportFinished field on InventTable was referenced.

The first is on Classes\ReqSetup\mustItemBeCovPlanned(). Below you can see I commented out the branch returning false so they these items will be coverage planned. This was enough for me to get a Planned production order for the item.

public boolean mustItemBeCovPlanned() { // if (this.inventTable().AutoReportFinished) // return false; return true; }

The other place is Classes\ReqSetup\mustBeDerivedDirectly(..). Below you can see the exception case for AutoReportFinished items behaving differently than typical items. Also that Phantom, Pegged supply, and Vendor types on Bill of material lines behave the same. I don't know enough about this code to recommend changing it.

public boolean mustBeDerivedDirectly(BOMType _bomType) { switch (_bomType) { case BOMType::Phantom : case BOMType::PeggedSupply : case BOMType::Vendor : return true; } if (inventTable.AutoReportFinished) return true; return false; }

This is all for educational purposes only. Use at your own risk. Definitely do way more testing than I did if you're interested in a code change.

Was this reply helpful? Yes No
Mark Prouty 1,312 on at

Like (0)

Report

Are you able to also set the Phantom field at same time?

Was this reply helpful? Yes No
Brandon Wiese 17,788 on at

Like (0)

Report

Phantom controls how the item is used when it is a component within a bill of material, while Auto report as finished causes a Report as finished journal to be created anytime the item is invoiced (this should be packing slip in my opinion, and that's a modification I commonly make). They do different things.

I suppose if you put an Auto report as finished item that was also marked as Phantom in a bill of material (at which time the Phantom status should copy to the bill of material line itself), then the constructed bill of material at usage should not contain the item at all, but instead its component items. Phantom "flattens" bills of material, by allowing a middle-tier of items to work with that don't transact.

Was this reply helpful? Yes No