Administration, Core Financials, and Project Accounting

[oyama]

Is there any way we can print customer item IDs on the invoice? I know customer item IDs can be printed on both  packing list and packing list summary, but I could not find an option to print on the invoice.

I am talking about those customer item IDs that can be set up at "Inventory Management \ Maintenance \ Maintain Customer Items".

[Ralph]

Try this.  Edit arztc001.rpt and add tarInvoiceDetl, linked to tarPrintInvoiceHdrWrk by InvcKey.   Then add timCustItem, and link it to tarInvcDetl by ItemKey.   Then add timCustItem.CustItemNo to either the 'Details a' or 'Details b' section of the report.

EDIT:  This only works if the particular item is only associated with a single customer in Maintain Customer Items.  If the item is associated with mulitple customers, you get additional lines on the invoice.   I'm going to look at it again to see if there is a way to make it work even if the item is associated with multiple customers.

[oyama]

Yep, that is my issue right now. I need a field that has custkey in it so I could pinpoint which record I need for the timCustItem table.

[Ralph · Accepted solution]

In addition to the changes I described above, I've just added tarCustomer as well.

Linked tarCustomer to tarPrintInvHdrWrk using CustID.  Then linked tarCustomer to timCustItem using CustKey.   Granted I've only tested a single invoice, but it seemed to work.

[oyama]

All right, we have a solution!

Actually, I got lucky because we were already using the tarCustAddr table that has CustKey in it. I linked it in and it works!

Thank you very much!

On the other hand, in the tarInvoiceDetl table there is a field called ItemAliasKey. That can be directly linked to the timCustItem table. The only problem is that all the ItemAliasKey fields are blank in tarInvoiceDetl table in our database! 

That, would have been the best solution....

[emurphy]

Whenever you link tables using ID rather than Key fields, you should also include CompanyID (in case the other ID value appears in more than one company).  Linking using Key fields is ideal because it doesn't have this issue.