Transactions Form Issue: Transaction Type Does Not Consistently Default From Transaction Source Setup
(Doc ID 970602.1)
Last updated on FEBRUARY 14, 2019
Applies to:Oracle Receivables - Version 12.0.0 and later
Information in this document applies to any platform.
Form:ARXTWMAI.FMB - Transactions
In Transactions Workbench, from a responsibility having access to multiple operating units, transaction type does not get re-defauled as per Transaction Batch Source setup, when the Batch Source value is changed to one that belongs to a different Operating unit but having the same name.
The following illustrates the issue:
Responsibility: Receivables Manager
Navigation: Setup > Transactions > Sources
- Batch Source setup#1
Name = MANUAL
Standard Transaction Type = INV_TYPE1
Operating Unit = OU1
- Batch Source setup#2
Name = MANUAL
Standard Transaction Type = INV_TYPE2
Operating Unit = OU2
Navigation: Transactions > Transactions
- Source defaults to MANUAL batch setup for OU1, as per value of Profile AR: Transaction Batch Source and MO: Default Operating Unit = OU1. Transaction type defaults to INV_TYPE1, all ok
- Change Source to MANUAL batche setup for OU2, Transaction type remains INV_TYPE1, this is the issue.
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