1,245
I have an invoice with status as Posted. Invoice amount on BI.BAM.00 does not match Invoice Print (BI.INV.00) report. I checked the PjInvDet table for this invoice to find that certain lines are marked as "NP" in in_id18 field and BI.INV.00 report specifically excludes such lines. Few questions I have are:
1) What does this field do and
2) What does value "NP" mean? Not Posted I guess?
3) Why and when this field gets marked as NP?
Thanks in advance
Nayan
*This post is locked for comments
Just had this issue again - and deleting the pjinvdet records that did not have a CpnyID or acct populated and the FiscalNo was bad data as well. Those records also showed in_id18 as NP. After deleting the user was able to process the transaction normally from within SL.
I recently encountered this and noted that my records came from allocations... no sure why it's marked, NP or how it got Marked NP, but I am going to remove the NP.
crtd_prog amount units in_id18 acct acct_rev adj_amount adj_units amount bill_status
PAPRO 0 0 NP TRANSPORTATION UNBILLED REIMB 22.79 0 0 S
The deletion of the suspicious record allowed the user to print the invoice in final mode.
delete pjinvdet where draft_num = 'xxxxxxxxxx' and acct = '' and in_id18 = 'NP'
Laura
Hi Laura,
Since that record has so many fields missing data, you could try and delete it and see if the draft will print. It doesn't sound like a valid record. If it still won't print after deleting the bad record, you could pull up the draft in Invoice and Adjustment Maintenance and scan for other lines with missing data.
Let me know how it goes.
No errors at all. Nothing goes into the print queue but the Invoice Print screen shows prinitng completed. That record just looks totally incorrect with so many of the fields blank.
I am able to run it in preliminary mode and print it to the screen, but when we go to print in final mode it won't print.
We've checked the printer and other things print to it. I changed the printer in SL and it's the same result.
Since there is no acct Cpnyid and the date created is when the user went to print I was thinking it is a bad record.
Laura
Hi Laura,
That one line with the NP value in in_id18 should not prevent the entire invoice from printing. Do you get any errors when trying to print the invoice?
Carolyn,
We have an invoice that won't print. It is approved but will not print in the Invoice Print (BI.INV.00)screen in Flexible Billings.
Upon reviewing PJINVHDR and PJINVDET for the draft, I noticed a record that is pretty much zeros; no acct or acct_rev, cpnyid etc, but as Nayan noted the in_id18 field is set to NP. All other records for this draft have in_id18 as blank.
Your response implies that the record with a NP and zero's for the various fields cause a problem. Am I right to assume that this record can be deleted from PJInvDet?
Your response would be greatly appreciated.
Laura Vogel
Hello Nayan,
I'm sorry for the delay in our response.
This field tells the system what lines to print. NP stands for No Print.
Typically invoice detail is created by either running allocation processor or running billings transaction load. You can manually enter detail lines in the billing and adjustment maintenance screen though. This is not a typical procedure because manually entering items will not update the project summary and rollup tables. As an example, if you enter a detail line in the BI.BAM.00 screen for LABOR, it will show up on the invoice, but it has not updated the LABOR account category in project controller.
When I have seen the problem you are describing, I have generally found that items have been entered manually in the BI.BAM.00 screen, and then both the qty and amount was set to zero. As an example, if you manually enter an item with a quantity of 40.0 and an amount of 1000.00 and then decide you don't want to invoice that after all, you can delete the line item and it won't cause a problem. If you set both the quantity and cost to 0.00, the system sets the in_id18 field to NP and it's these NP lines created in BI.BAM.00 that seem to cause a problem.
The next time you have one of these invoices that won't print, run a query like this. In this query, I've used a draft number of 0000080123. Replace that with the actual draft number.
select crtd_prog, amount, units, * from PJInvDet where draft_num = '0000080123' and in_id18 = 'NP'
See if the crtd_prog is BIBAM and see if the amount and units are both 0.00.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (