Transaction Workbench Issue: Why Are Duplicate Transaction Type Names Allowed Across Different Operating Units (Doc ID 1366207.1)

Last updated on FEBRUARY 20, 2023

Applies to:

Symptoms

Why does the system allow duplicate Transaction Type names to be entered for different Operating Units without giving any error message?
Whereas, in release 12.0.4, it used to raise an APP-AR-201995 error.

Then if a transaction type name X, is used across multiple operating units, and you attempt to change it via one operating unit, you get the following error when you attempt to save the changes:
APP-AR-294572: You can change the Transaction Type only if it is used in one operating unit and not across multiple operating units  

Steps to reproduce:
Responsibility: Receivables Manager with access to OU1
Navigate to the Setups -> Transaction Types
Create a Transaction Types with name = 'TEST1'

Responsibility: Receivables Manager with access to OU2
Navigate to the Setups -> Transaction Types
Create a Transaction Types with name = 'TEST1'

Now go back to OU1 and try to change the Transaction type name, and you get the error:
APP-AR-294572: You can change the Transaction Type only if it is used in one operating unit and not across multiple operating units 

Cause

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