Using a Job No on Sales Orders

Looking for either an Add-On or a work around for using Job No. on the Sales Order. Any ideas and/or solution would be greatly appreciated Thanks _________________________ Wendy O’Connor - co moderator Attain/Financials - End User Questions NOLUG

The Job itself is handled like a sales order. Add everything to that Job, assign the entries to be chargeable or not and use the “Get Job usage” function from the sales invoice. Good luck Walter

I most likely did not make myself clear. But my customer uses jobs to record service related time entries which have flowed through from Navision Payroll module. Then their customers place orders to buy certain stock items and in some cases also require the item to be pre-serviced or to be installed. So what you have in reality is an sales order which they would like to record not only the items being sold but the service elements. Navision does not provide a reason why there is not a feature to get usage from the sales order. I was just wondering if anyone had modified Navision to do so or could provide any suggestions for a work around solution. I know that version 3.0 (Attain) provides a service module but my customer is on 2.60CA and will be for a little while yet. _________________________ Wendy O’Connor - co moderator Attain/Financials - End User Questions NOLUG

Hello Wendy There’s a test in codeunit 80 that the document type must be credit invoice or invoice if there’s a jobno. at the line. After disabling this test You can invocie the resources an items and link the orderline to a job. The above solution creates job ledger entries with transaction type “Sale”. You probalby also wan’t the usage posted to the job. To do this You can look in cu80 how the sales entries are created and simply add a few lines after the job.journal line is posted. It should look something like this: IF SalesHeader.“Document type” = SalesHeader.“Document type”::Order THEN --BEGIN ----JobJnlLine.“Entry Type” := JobJnlLine.“Entry Type”::Usage; ----JobJnlPostLine.RUN(JobJnlLine); --END; This way You get two transactions posted to the job. One with the sales and one with the usage. There are probably some more tests that should be done and maybe som more fields than just the entry type that should be different frpm the sales transaction, but i think You get the ponit. Play around and see if this is what You need. //Lars Edited by - Lars Westman on 2001 Aug 19 22:42:18

Thanks Lars, I will get my developers to test this out in a CRONUS DB using your suggestions. Wendy _________________________ Wendy O’Connor - co moderator Attain/Financials - End User Questions NOLUG