If u need it on the planned production orders then most likely you will have to enable planning by batch dimension. Either you do this or modify code to achieve the same effect. It will kill performance either way.
Otherwise at the time of firming you can just scroll up the production order hierarchy to find the sale order and hence the batch number. Since the number of firmed orders are very less this should not mucho effect on performance. Another advantage will be very few code changes. If you really really want it on the planned orders you could write a display function to scroll thru hierarchy. Remember to display this field on any tab other than the overview tab. You do have a headache when multiple requirements are grouped together for e.g. multiple sales orders or minimum stock and sales order etc. Regards Harry Ps: Everything ok over here. Now it does not matter if the stock market goes down any further, I do not have any money left to lose anyway :) From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of James Flavell Sent: Tuesday, September 16, 2008 7:02 PM To: Axapta-Knowledge-Village@yahoogroups.com Subject: RE: [Axapta-Knowledge-Village] Re: Master planning and batch number flow through Hi Harry Good to hear from you again, hope all is well for you and your family mmm I would say it would be far better to have on the planned production orders although it might be possible to get away with just at the time of firming. maybe you can explain a little more the possible pors/cons to have it on planning versus only at firming etc Thanks once again James ________________________________ From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Harry Deshpande Sent: 17 September 2008 00:17 To: Axapta-Knowledge-Village@yahoogroups.com Subject: RE: [Axapta-Knowledge-Village] Re: Master planning and batch number flow through Hi Batch number of production order and sub-items. Do you also need them for planned production orders? Or rather is it a must-have functionality that you need to see batch number on planned production orders. Or is it enough if you get the batch number on the real production orders (i.e batch number introduced at the time of firming). Regards Harry From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of James Flavell Sent: Monday, September 15, 2008 11:03 PM To: Axapta-Knowledge-Village@yahoogroups.com Subject: RE: [Axapta-Knowledge-Village] Re: Master planning and batch number flow through Thanks Steve and sorry it has taken me so long to reply (lot of things happening good and bad) I understand what you have done but my focus at this point is more on the flowing of batch number through the master planning Basically what I want to do is if I have a sales order line for an item that is a BOM and I put a batch number on it, then when I run master planning I want the batch number to be put on the planned production order for the finished good (std AX does this) but also to flow through and be put on the BOMs sub item lines. The reason is actually for project based manufacturing where material is purchased for a specific project and so the whole operations from production and purchasing need to capture and work with this information (e.g. they cannot just buy 100 tons of item A as they need to issue purchase orders per project requirement and then track their inventory per project). I could do 'per requirement' planning but the tracking is a nightmare since you will only have AX marking to go by (and all its many realted problems) So there are 2 places for the flow through of batch number the way I see it: 1) During master planning when the system sees that the planned production order has a batch number it should pass the batch number on to the planned actions for the sub items (whether the action be a another planned production order or a planned purchase order). So basically the batch number flows all the way through the planning 2)If the user creates a production order directly from the sales line, the batch number for the production order should be set from the sales line adn the the batch number on the production order's picking list lines should be populated with the batch number on the production order headed (finished good's batch number) I think point 1 is the trickier bit but again I think its just I need to find the code where the batch number is not passed on to sub items in a BOM so I hope someone familair with the master planning class might be able to help point me in the right direction Thanks James ________________________________ From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of slees32 Sent: 01 August 2008 10:06 To: Axapta-Knowledge-Village@yahoogroups.com Subject: [Axapta-Knowledge-Village] Re: Master planning and batch number flow through Hello James, I can't answer your question regarding planned orders but we are doing something similar so I thought I'd describe that and maybe it is of some help. We know our batch number when we create the sales order - in fact we are using the sales order number as the batch number. So when a sales order line is created, we have modified the code to go to the batch number table and create a new line. The modified code then also inserts the batch number in the existing field on the sales order line. At the moment we are always creating a production order from the sales order. We do not use planned orders in our process. And the batch number is automatically passed from the sales order to the production order (this is standard Axapta functionality). I do not know whether this same facility exists to pass the batch number to a planned order and then on to the purchase order - sorry. I should also add that our modified code has a bug we have not yet been able to isolate, where occassionaly, the batch number, although created, does not get added to the sales order. This is each to then add at receiving time so is not a huge issue for us - probably partly why we haven't fixed it yet. Regards - Steve AX 3.0 SP2 --- In Axapta-Knowledge-Village@yahoogroups.com<mailto:Axapta-Knowledge-Village%40yahoogroups.com>, "James Flavell" <[EMAIL PROTECTED]> wrote: > > Thanks, > > It is basically that we purchase items for a specific sales and we need that > visiblity (marking just does not cut it especially when the flow goes > through several BOm levels and marking is also rather buggy from my > experience...). So we will do something like set the batch on the sales > order equal to the sales order number and want it to flow through > > Thanks > James > > > _____ > > From: > Axapta-Knowledge-Village@yahoogroups.com<mailto:Axapta-Knowledge-Village%40yahoogroups.com> > [mailto:Axapta-Knowledge-Village@yahoogroups.com<mailto:Axapta-Knowledge-Village%40yahoogroups.com>] > On Behalf Of Krishnan > Sundararajan > Sent: 31 July 2008 18:57 > To: > Axapta-Knowledge-Village@yahoogroups.com<mailto:Axapta-Knowledge-Village%40yahoogroups.com> > Subject: Re: [Axapta-Knowledge-Village] Master planning and batch number > flow through > > > > > Hi > > Logically batch numbers are created on completion of receipt transactions. I > dont understand the need for planning wrt to the sales order batch numbers. > If you book the sales order with the batch numbers it means the material is > lying in stock and hence need not planned at all. Please let me undertand > your scenario to put my thoughts on. > > Krish > > > On 7/31/08, James Flavell <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> com> > wrote: > > > > Hi everyone, > > I would like to do modification so that the batch number from a sales order > flows all the way through master planning so that my firmed purchase order > will have the batch number. > > I know there is marking but this is not visible enough to the user so I > would like to look at using batch number. > > Can any one direct me to where in the code I can look to be passing the > batch number on to the next ReqTrans being created in the planning etc? > Of course if anyone has any other ides how to address the problem please > feel free to share > > Thanks > James >
