R12 Payables: JBO-25013 error is thrown when selecting supplier relationship

A few months ago there was an article I put up about several IBY tables and article "R12.1:22878464:Error JBO-25013 On Supplier When Selected The Supplier Relationship Tab" on My Oracle Support via document number 2115923.1 was just solved today but what I think is important from this is finding out a new IBY table AND another instance of something that needs to be added to your testing suites!

R12.1.3 Purchasing: System checks that prevent PO from being merged

In R12.1.3 do you know "What checks are Done to a Prevent PO From Being Merged When Running Supplier Merge"?  Find out via My Oracle Support document ID 2095172.1 tonight so you can tell the business why the data might not be in the right conditions to let this happen!

R12 Purchasing: Error when merging Supplier

Make sure you get the patches associated with MOS article "Supplier Merge with Global Agreement - Error The Supplier and/or Site cannot be merged." from document ID 2017875.1 if you encounter this problem merging a supplier which is tied to multiple organizations!

R12 Payables: Error APP-SQLAP-10065 if supplier name changes

Have you ever seen "APP-SQLAP-10065: The Supplier Name Has Changed Since Payment Creation" that is being reported via MOS document ID 2032954.1?  It looks like this is a rather benign issue, but it does help point out another way that testing suites can help out by looking at how we can change the data and see how it affects the EBS application!

Weekend Learning: iProcurement and Oracle Exchange supported SSL certifications

Do you know "Which Type Of Certificates Are Supported By Oracle Exchange And iProcurement Punchout. Does It Support SHA 256RSA ?"  If you answered no, then check out note 1999543.1 on My Oracle Support to find out the answer and learn if you need to be making extensive plans to test and work with your suppliers/vendors and what conditions require different certification paths!

R12: Unable to change Supplier information

Since I'm on an A/P bug kick, and I've shared with you some knowledge about Supplier changes in R12, I should probably also clue you in on another item to add to your testing suite!  The other day A/P was in the web portal trying to change the inactivation date on a Supplier record when they received an error message indicating "Context Value Doesn't Exist In Value Set $FLEX$.DF_CONTEXTS" and the form wouldn't let them actually save their changes.  MOS note 1458183.1 indicates this happens because setup wasn't migrated over, or because there was a decision made to not migrate data, so you get two solutions: one if you want to fix your DFF and the other if you want to get a bugfix.

If you aren't testing the removal (or change) of information to your migrated data for A/P you should probably start trying to break the system by doing it, and even branch out to test other application data that was migrated because you might be able to introduce patches to your code base early in the process to prevent re-testing.

Weekend Learning: Employee Supplier in R12

Have you ever wanted to learn more about the R12 architecture changes with respect to suppliers and how Employee Suppliers exist now?  Well friends, look no further!  I had to do some research on this last week, and stumbled upon MOS note 1377888.1 which has a GREAT breakdown of the changes that have taken place on several "standard" tables as well as being able to introduce the new vendor information so it is very easy to understand.  Even for me.  It probably helps that it has pictures huh?  :}

I know it's not the weekend yet, but my 4 day weekend starts tonight so I'm in that mode here on the blog!

Supplier issue in Expense Report Import

This post will run closer to the type of things I deal with daily, and hopefully will be helpful to everybody out there that runs into the same type of problem!  Our business ran the Expense Report Import, just like they usually do every day, but encountered the following error message on this run:

Next import invoice: 6196224
Getting work location address
Validating vendor
Getting Create Sites Error...
BEGIN  AP_UTILITIES_PKG.AP_Get_Message(:msgbuf_err); END;
This Site name already exists for this supplier.  
Re-enter.
APP-SQLAP-10916: apiivs/3:ORA-20001: APP-SQLAP-10357: This Site name already exists for this supplier
Cleaning allocated memory

In my research on My Oracle Support I found and used the following Oracle notes:

Expense Report Import Errors With APP-SQLAP-10916: apiivs/3:ORA-20001: APP-SQLAP-10357 [ID 1228868.1] - this was more on point and useful
"Expense Report Import" Is Finishing In Error When No Purchasing Sites Available For Supplier [ID 1351417.1]

Which helped me understand that I had to run this script to find the expense information in question:

select * from ap_expense_report_headers_all
where report_header_id = 6196224

That lead me to the supplier information from the expense report:

select a.* from po_vendors a, ap_expense_report_headers_all b
where a.vendor_id = b.vendor_id
and b.report_header_id = 6196224

Then I was able to use this script to find the supplier site information:

select a.* from po_vendor_sites_all a, ap_expense_report_headers_all b
where a.vendor_id = b.vendor_id
and a.vendor_site_id = b.vendor_site_id
and b.report_header_id = 6196224

With the information we've gathered at this point, we know that the supplier site has been end dated for the OFFICE site that the Expense Report Import expects to be open when it runs.  Having the business remove the end date via the application allowed them to re-run the Expense Report Import without any further issues!