Client has two invoices in Flexible Billing. One printed for $0.00 while the other printed correctly with the correct dollar values. Both of these are Construction Billing invoices. When they run the Invoice and Adjustment Posting, they receive PC Message 0063 referencing BI/INVOICE-REGISTER. Having seen that error in the past, I deleted the record from Project Controllers Parameters and asked them to try again.
The error reoccurred, so I started digging. What I found was:
1. the $0.00 value invoice had a record in PJINVHDR, but no records in PJINVDET. However, there were records in PJBILLCH and PJBILLCN for the invoice. Something must have cause the process to stop, before creating the PJINVDET records.
2. the Invoice and Adjustment Posting process is looking at both invoices, but when it runs into the missing PJLABDET records it aborts. At least that is my assumption.
My questions are:
1. what caused the problem to start with?
2 how can I now clear the issue up, reprint the first invoice with the correct values and move forward with posting?
If its construction billing,
You'll have to look at the billing application that created the draft and why it may not have created any detail, Printing one of these creates the next entry (application)
Did this create a subsequent application? The original (one that's zero) should have its invoice number assigned on the Const. Billing entry screen, If there are any billings created after the bad one, they have to be reversed.
You don't say if its the same project...if it is, then yes you'll have to reverse all the billings that created drafts after it, and fix the one...but I'm not sure whats wrong with it. Did the AIA work on this invoice at print?
Maybe you can just create a draft manually ? Or set the draft to In process.(this would be in SQL) ..add the billing, then go print it through the regular print and post , but I'm going under assumption that the print job was good on the original.
The records, both invdet/invhdr and the next application are created during the CB print job as final. Something would have had to happen during that process, my guess is that it failed before the invoice detail insert?
Business Applications communities