Interface In-Service Transactions Program Doesn't Honor Project Parameter
(Doc ID 1070708.1)
Last updated on JULY 14, 2020
Applies to:Oracle Asset Tracking - Version 12.1.1 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
Interface In-Service Transactions program doesn't honor Project Parameter. When multiple instances are 'Put in Service' that belong (were originally received) to different projects, the 'Interface In-Service Transactions' program only successfully processes instances from ONE project and others are partially processed and left hanging / stuck. i.e. cannot be re-processed and do not get interfaced to Projects.
Interface In-Service Transactions program should honor the Project parameter AND, if no parameter is specified, should process all of the eligible records for each project respectively and correctly.
Steps to Reproduce:
1. Put mulitple instances (related to multiple projects) in Service at the same time.
2. Run 'Interface In-Service Transactions' program either with no parameters OR with one of the projects as a parameter (no task parameter)
3. Run 'PRC: Transaction Import'
Only the transactions from one of the projects will have expenditure lines successfully reversed and re-created using the net zero functionality, the others will appear to have been processed (i.e. Transaction Status = INTERFACED_TO_PA), but they will not be processed.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!