R12: AP/IBY: IBY_EXT_BANKACCT_PUB.UPDATE_EXT_BANK_BRANCH Fails with "This record in table hz_contact_points cannot be locked" when EFT_SWIFT_CODE or EFT_USER_NUMBER are Already Populated (Doc ID 2990235.1)

Last updated on JULY 22, 2024

Applies to:

Oracle Payments - Version 12.1.1 and later
Oracle Payables - Version 12.1.1 and later
Information in this document applies to any platform.

Symptoms

When attempting to call the IBY_EXT_BANKACCT_PUB.UPDATE_EXT_BANK_BRANCH API the following error occurs if there are already existing EFT numbers:

This record in table hz_contact_points cannot be locked as it has been updated by another user.

To replicate run the following for a branch that has the EFT number populated.
The following will attempt to change the name of the branch to a new name you choose.

Cause

	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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

R12: AP/IBY: IBY_EXT_BANKACCT_PUB.UPDATE_EXT_BANK_BRANCH Fails with "This record in table hz_contact_points cannot be locked" when EFT_SWIFT_CODE or EFT_USER_NUMBER are Already Populated (Doc ID 2990235.1)

Applies to:

Symptoms

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!