This content has been marked as final. Show 12 replies
When I trying to run the 'Supplier Merge Program' program, it errors out with the following message in log file.What is the error message?
Pl post OS details and the complete error message
I have checked the metalink and found metalink ID: 970604.1 (R12 APXINUPD SUPPLIER MERGE PROGRAMIf you get REP-1419 error (as in the R12 doc), please see (Note: 1073365.6 - APXINUPD SUPPLIER MERGE ERRORS WITH REP-1419).
COMPLETES IN ERROR REP-1419) that says similar issue in Release 12 but not in Release 11.5.10. So, please
share your knowledge.
Sorry for not posting the error message, here is the error that I am getting.
MSG-01000: Checking for duplicate tax sites...
MSG-01001: Selecting Duplicate vendor sites...
REP-1419: 'beforereport':PL/SQL program aborted.
Oracle EBS 188.8.131.52
OS: HP Unix
I have checked this note earlier. We have custom indexes but not any constraints or unique indexes, so that should rule out
the solution given in this metalink note 1073365.6
Thanks a lot for your help, I really appreciate it.
No similar issues are reported in MOS, so you may need to log a SR and see if Oracle support can help.
Just be sure, please confirm that the set of books and the default operating unit profiles are set at the responsibility from which you are running this program ?
Because most of the before report trigger failures are from missing profile setups at the resp level.
Thank you for your response. I have both profiles "GL Set of Books ID" and "MO: Operating Unit" setup for the responsibility.
But the profile "MO: Default Operating Unit" is blank at site and responsibility level, hope this should not cause any issue.
I have a from supplier whose set_of_books_id is null and to supplier whose set_of_books_id is set to 1, so my question will this
cause any issue to merge. Both Supplier sites that I am trying to merge are at same org_id level. Thanks a lot for your time and
appreciate your help.
There is function called get_company_name in the before report trigger and the function gives TRUE/FALSE output. (below is the function code)
FUNCTION get_company_name RETURN BOOLEAN IS
l_report_start_date := sysdate; -- Get the report start date from sysdate
l_sob_id := :p_set_of_books_id; -- Copy from parameter to PL/SQL variable
WHERE set_of_books_id = l_sob_id;
:c_company_name_header := l_name;
:c_chart_of_accounts_id := l_chart_of_accounts_id;
:c_report_start_date := l_report_start_date;
RETURN NULL; EXCEPTION
WHEN OTHERS THEN
Try making the set of books to be same and run the program.
Thank you for the code from the report. I tried doing the merge with both vendors having same set_of_books_id and still errors out with same
message. I don't have access to the report file, to dig the code. So waiting for the report file, so that I can dig and see what validations it has and
at what point its getting failed to determine whether its a data issue from our side or its really the program error.
Could someone tell me what is the significance of the ap_duplicate_vendors_all table, based on the name I am expecting that this will store duplicate vendor
details. The 'Supplier Merge Program' report does validation based on this table, so just wondering how to use this table to avoid any issues with 'Supplier Merge
Program'. I would really appreciate any inputs on it.
Could someone tell me what version of report file APXINUPD.rdf the 184.108.40.206 clients are using currently. We are currently
using 115.74 file version and it was applied to our instance on 12/10/2007, so wanted to know if this is the latest version
that we are support to use or is there any other patch that delivers latest version.
The report file APXINUPD.rdf (version: 115.74) has code validation in 'BEFORE-REPORT' trigger based on old tables reference
without suffix _ALL and I am suspecting that is causing the code logic to go into exception handling and throwing a error. Has
anyone of you noticed the same in their current report file APXINUPD.rdf ('Supplier Merge Program'). Any input is appreciated.