R12: How To run a Supplier Merge process for Multiple Operating Units Using a MOAC Responsibility
(Doc ID 1318718.1)
Last updated on FEBRUARY 12, 2019
Applies to:Oracle Payables - Version 12.0.0 to 12.1.3 [Release 12.0 to 12.1]
Information in this document applies to any platform.
On application version 12.1.3 find that when we try the supplier merge for a supplier/site that exists across multiple operating units, get errors in the supplier merge (APXINUPD) program as below. This occurs even when using a MOAC-enabled responsibility:
MSG-07164: Checking for the existing party sites which is having same address name... and party_site_id is null.
MSG-07160: After call to create vendor site: l_return_status: E
MSG-07170: After call to create vendor site: l_vendor_site_id:
MSG-07180: After call to create vendor site: l_party_site_id:
MSG-07190: After call to create vendor site: l_location_id:
MSG-07200: Error after AP_VENDOR_PUB_PKG.Create_Vendor_Site...
MSG-07210: Error message... l_msg_data:This record in table HZ_PARTIES cannot be locked as it has been updated by another user.
MSG-07210: Error message... l_msg_data:Invalid Payee context values. Org parameters exist only with party site and supplier site.
MSG-07230: Error after create vendor site... Update process flag to N
MSG-07460: Error in function Duplicate_sites
MSG-03060: Failure in function BeforeReport
REP-1419: 'beforereport': PL/SQL program aborted.
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP-1419: MSG-03000: Start Before Reports Trigger.
Steps to reproduce
1 - Select suppliers and sites for merging
2 - Click 'Merge' to kick off the Supplier Merge (APXINUPD) program
3 - Program fails with the error reported in the logs.
Have to merge using the the individual operating unit (OU) responsibility and merge the vendors one OU at a time.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document