When entering a POA Receipt today, one of our staff selected an AP Vendor on the Header tab and then went to the Details Tab. There they somehow managed to changed the Vendor Type "Sundry Vendors". We don't actually have any Sundry Vendors and don't use them. They added multiple details line items and somehow figured out a way to force it past an error saying "the Sundry Vendor does not exist" and posted the receipt as a delivery note.

POA integrity check is now reporting errors, "DA7570 Sundry Vendor does not exist for RC-00003517. There is also batch in ledger now that was retrieved from IR that contains errors. The debit amount to account 1300 (Inventory) does not have a matching credit amount to 2015 (Receipt Credit).

Should I just edit the batch in Ledger to add the Credit amount to 2015? I'm pretty sure this will correct the accounts. How do I get rid of the errors in POA? Since the receipt is already posted I can't edit it. When I attempt to invoice the receipt, even though there are amounts in the line items, the total tab comes up at zero, showing the name of Vendor, with the Vendor code DA7570 but with the type of Vendor set to "Sundry Vendor".

I cannot restore from a back up because this receipt was posted early this morning and since then we've had a full day of data entry. The only way I can think of to fix this is to post the receipt as an invoice at zero. Enter the payable directly into payables. Edit the ledger batch to add the credit entry to 2015 and post it. Then wait until eventually the receipt moves to history so it will stop reporting errors in POA integrity check.

Any other suggestions or ideas would be greatly appreciated!

Thanks,

Hi Susan

Yes you can just fix the GL entry.

Why don't you try creating a sundry vendor DA7570. I think that will solve the data integrity problem.

You are correct that you will have to enter the invoice in AP since transactions posted to sundry vendors in POA do not pass through to AP.

Steve

I tried adding the Sundry Vendor but it said it already exists in AP. Maybe I could try renaming the Vendor in AP with Toolkit?

Yes, try that, but I'm worried that it might change the vendor on the PO as well.

Running the Toolkit will change the vendor on the PO as well. You really need to talk to your Adagio Dealer because this sounds like the configuration needs to be corrected as well as the data.

Steve's suggestions are correct to deal with manually outside of POA, except you cannot have a sundry vendor with the same code as AP vendors. By design, this was disallowed so that there would be no confusion over haveing the same vendor in sundry vendors or Payables Vendors.

I suppose you could leave and hope that eventually the problem will go away, if you like to keep data integrity issues in your data. It wouldn't be our first choice.

I might also suggest that if you (or your staff) see errors appearing on the entry screen(s), you might deal with them at the time and call for support instead of forcing them through. Hoping that the error will safely land is not normally the best practice, and will cost you more in the long run to correct.

Brian

I didn't run the Toolkit... I've corrected the batch in ledger and posted and manually created the Payable and posted. Obviously I prefer not to have data integrity errors but I don't see a way around it. I agree with the staff calling for support before forcing the entry through and I've reviewed this with the guilty person. 8)