Now that Job Cost is in business framework one would think that you can have user defined fields updated all the way to job transaction detail file to be used on reports. There is no way to link PO fields or user defined fields entered in purchase order module to job transaction detail file. I guess it is still in legacy mode. What makes this worse is that I cannot link the PO receipt history file to the job transaction detail file as one cannot link to the specific line of the receipt as the line number/sequence is not in the job transaction detail file.
Please create fields for the receipt of goods number, PO number in jc_transactiondetail file instead of concatenating the fields in the comment field. This will prevent the need to create formulas to extract the fields and link them to PO files via sub reports. I was under impression that business framework would make life easier.
by: Avron K. | over a year ago | Payroll / Job Cost
Comments
It would be useful to link the job transaction detail fike to get the originating transaction (eg AP Invoice History Detail). This is only possible if the AP Invoice has one line posting to a specific job, cost code and cost type. If there are more lines on invoice that goes to same job, cost code and cost type there is no way to link to the specific line from ap invoice history detail to the corresponding job transaction detail record. Therefore if one wants the description you have to manually look up the invoice to find it out. A custom report will not work as you will get duplicates depending on lines in AP invoice with same job,cost code and cost type.
FYI, this IS possible--at least on Sage 100 2021. I have a UDF holding the Item Description (especially helpful for miscellaneous items, for whom the item number is meaningless) flow from SO_InvoiceDetail using SO_SalesJournal_upd, and then on to the Job Transaction Detail Work table so it can appear on my reports. I DO this the item description should be included by design, however, so we're not required to create this complicated workaround. Or at the very least, publish clear instructions on how to do it as I had to figure it out the hard way!