Our support engineers have assembled the top recommended solutions for you.
Microsoft Dynamics AX 2012CRM Connector in Microsoft Dynamics AX 2012Financials Management in Microsoft Dynamics AX 2012Upgrading to Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2009
Application Object Server (AOS)
Enterprise Portal and Role Centers
Inventory Costing in Microsoft Dynamics AX 2009
SSRS and SSAS Integration
We implement Dynamic AX 2009 , and user auto BOM when
we posting the invoice it work probably , but when I want to post
Picking list the error message appear:
"The MOB Item 2124040 Is automatically begin reported as finished and can not used with output orders .
instead the BOM should be exploded
Item Number : 2124040
a maximum number of 0.00 can be entered"
Is the report as finished flag set on the item?
Has anyone found a fix to this error? We have the exact same problem when our company upgraded from AX3 SP2 to AX 2009. Any BOM item that has the "auto-report as finished" flag checked on will display that error message when I try to post a pro-forma picking list, or regular picking list.
We didn't get this problem in AX3, although when I briefly looked at the source code in AX3 and AX2009, I get the impression that posting a picking list with BOM items flagged as "auto-report as finished" should have also failed in AX3.
I've been doing a lot of investigation into this issue. If a Microsoft expert is reading this, I have a couple of questions (from the back-end on the technical side, and the front-end on the data side)
1. Why does AX3 not crash with the warning, even though the BOM items have the Auto-report checkbox ON?
2. Is there some kind of posting or validation rule / parameter that is turned OFF in AX3, which allows the system to bypass the checkNotAutoReportAsFinished method or Validate method of WMSOrderCreate?
3. Is the Validate method even being run on the call stack when posting picking lists?
4. During the upgrade from AX3 to AX2009, is there some kind of “fix” within the codebase itself that is now enforcing the validation, or did the process “reset” some kind of parameter / rule to force this validation?
AX 2009 does not support this functionality any more, and it requires that you explode the BOM. I believe way back when I was upgrading a client from 4.0, I changed the code to bring back the functionality.
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13