You must not specify Job No. in Sales Line Document

imurphy

If you modify the order form to display the Job Nº and Task Nº fields and then fill them in, when you create an invoice from this offer Nav 5.0sp1 displays this error:

You must not specify Job No. in Sales Line Document Type='Order',Document No.='1',Line No.='10000'.

Now I could understand it simply ignoring the field, but displaying an error saying that it should be empty?

I want to put the job number in the order and add code in the invoice to automatically create project cost previsions from there. However this seems to be a bit of a showstopper given that we can't modify the sales header table to add a column.

Anyone know why this may be?

Ian

kine

In the CU80 there are these lines:

IF NOT ("Document Type" IN ["Document Type"::Invoice,"Document Type"::"Credit Memo"]) THEN
  SalesLine.TESTFIELD("Job No.",'');

As you can see, the Job No. can be filled only on Invoice or Credit Memo (NAV version 4.0x). You can bypass this test,but the result is on you... ;-)

imurphy

Do you know if any good reason why this test is here?

If it was not important to be empty then the contents of the field would not be checked, no?

Only two reasons to have a check like this occur to me
1) Something non-obvious breaks if you fill in this field
2) Marketing

Ian

kine

I do not know, I have not found any objective reason for this test... We removed the test because we needed to use the field for our purposes too... :-) but you know, you need to test and to know, that there is no side effect of this... responsibility is on you... 8)

nunomaia

In Navision 5.0 you could only make sales of jobs in invoices. Probably isn’t support yet using orders.
Don’t forget that in job lines you have related document. Changing to orders it’s a risk. I never tested in NAV 5.0 SP1.

kine

nunomaia wrote:

In Navision 5.0 you could only make sales of jobs in invoices. Probably isn’t support yet using orders.
Don’t forget that in job lines you have related document. Changing to orders it’s a risk. I never tested in NAV 5.0 SP1.

We are working with 4.x... thus very limited connection between sales and jobs. I do not know which version is using imurphy... 8)

nunomaia

kine wrote:

nunomaia wrote:

In Navision 5.0 you could only make sales of jobs in invoices. Probably isn’t support yet using orders.
Don’t forget that in job lines you have related document. Changing to orders it’s a risk. I never tested in NAV 5.0 SP1.

We are working with 4.x... thus very limited connection between sales and jobs. I do not know which version is using imurphy... 8)

Is using Nav 5.0sp1

imurphy

We have some extensions supplied by Afirma as part of a Microsoft program to push Nav in spain.

One of the extensions is the ability to invoice directly against a job - something pretty much vital for an IT services company and it seems to work very well.
However they have only implemented invoicing against jobs and not offers/orders against jobs.

This makes me suspicious. If they haven't done it, it may be because there are problems elsewhere.

nunomaia

Has I have said. This was a limitation of Jobs I NAV 5.0. I can’t confirm if this limitation is still in NAV 5.0 SP1.

David_Cox

I am not sure but I would test the Sales Order functions and Ship, Part Ship, then Invoice from the Order and also test the use of the Get Shipments on an Invoice to see if they update the Job ledgers correctly, or the link gets lost somewhere.

And it could also be that they thought you would run your jobs posting usage via journals, and then from the Invoice functions "Get Job Usage" so they likely did not see why you would want to use a "Job No." on a Sales Order.

The Jobs have not really changed that much and it seems that the theory would be that you would create your Budgets, then consume the Usage via the Journals, then when it came to Invoicing you would either get Job Usage, or just Invoice against the job number as standard, so Orders were not realy in the workflow, baring in mind that the Job Module was so low cost.

David

nunomaia

David Cox wrote:

And it could also be that they thought you would run your jobs posting usage via journals, and then from the Invoice functions "Get Job Usage" so they likely did not see why you would want to use a "Job No." on a Sales Order.

David

During NAV 5.0 release I also loose many time to finger out were that feature had been placed.
Get Job Usage has been gone in NAV 5.0

David_Cox

nunomaia wrote:

David Cox wrote:

And it could also be that they thought you would run your jobs posting usage via journals, and then from the Invoice functions "Get Job Usage" so they likely did not see why you would want to use a "Job No." on a Sales Order.

David

During NAV 5.0 release I also loose many time to finger out were that feature had been placed.
Get Job Usage has been gone in NAV 5.0

Oh well it was there for 15 years so it has likely been moved to a menu somewhere, It's nice when thay add new stuff but a pain when they just remove it, if I had been using Jobs for the last 10 years I would be pretty unhappy with 5.00 :sick:

nunomaia

Jobs structure have been dramatically changed in version 5.0. You can’t invoice jobs lines that aren’t in planning lines. So, when you make an consumption it won’t go to planning lines except if you change during posting line type.

imurphy

Well, thanks for the help everyone. I managed to get this working... though I still have to do testing to check the amounts and quantities are consistent.

The module we have from Afirma does the following:

When you post an invoice it inserts a row for each Sales Line into the Job cost planning table and associates the two rows using the Job contract Entry No. field in the sales line - pulled from the new Job Cost planning line.

It permits generating invoices against Jobs, but not orders.

The complication with orders is that you can do partial invoicing of the order.

To get this working I had to remove the checks in the posting code which verified that the Job No. etc were blank.

I then had to add a small section to the Job Cost Posting function which updated the quantities and amounts in the Job Cost Planning lines from the Sales Line depending on the amount billed to date.
Thus each partial invoice increases the costs assigned to the job until the last bit of the order is invoiced.

Ian