Automatic issue of purchases for jobs ?

bob_up

One of our clients is unhappy with the way the standard system handles receipt of goods for jobs. It seems that when goods are received on a purchase order line which has been assigned to a job, the goods are automatically issued. In reality the goods may be in the warehouse until some later date. This is leading to confusion.

Is there any way to prevent this automatically happening ?

nTAo+

Hi. i'm facing the same problem here. I'm still thinking the best workaround for this 'issue'.
i think NAV do the automatic issue of purchases for jobs is to prevent the wrong inventory is taken so that's will effect the item costing. CMIIW.
My client wants to receive the goods at the company's headquarter Warehouse first and then it will be transferred to the site's warehouse. but if we make a PO and link it to the jobs, the goods are automatically issued.

have u the workaround for this? thank you

bob_up

No, I'm afraid we havent resolved this yet.

My thinking so far is to add a new, additional field to the purchase order line for entry of the job number. The user would enter the job number into this field instead of the standard field. Thus the automatic issue of good to the job would be avoided. I would then modify the posting codeunit to use this new field to populate the job number on ledger entries etc. I havent looked in detail to see if this would fully meet the client's requirements though.

nTAo+

I've think to modify the PO too. But my client process is a little more complex because they have Purchase Requisition. so i think i'll have to add the extra field at PR too and make sure that the link between PR-PO-Jobs is okay.
Thank you for your reply, maybe we can share the solution when it's already done.

rhpnt

bob_up wrote:

One of our clients is unhappy with the way the standard system handles receipt of goods for jobs. It seems that when goods are received on a purchase order line which has been assigned to a job, the goods are automatically issued. In reality the goods may be in the warehouse until some later date. This is leading to confusion.

Is there any way to prevent this automatically happening ?

Why would you want to change/prevent something that's by design and working? If the items are stored in a warehouse and consumed later then don't assign a job number to the PO line. There's nothing confusing about that.

bob_up

The client wants to be able to see the job number on g/l entries etc. for analysis/reporting purposes.

rhpnt

bob_up wrote:

The client wants to be able to see the job number on g/l entries etc. for analysis/reporting purposes.

I don't see a problem here. Why do you want to change the PO functionality when we're talking about g/l entry analysis? When the consumption of the goods is posted via the jobs journal everything you need for your analysis is in written to the g/l entries.