Transaction Stuck At PA_TRANSACTION_INTERFACE_ALL Table With Error INVALID_ETYPE_SYSLINK
Last updated on JANUARY 11, 2017
Applies to:Oracle Project Manufacturing - Version 12.1.1 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
To resolve issues where transactions are stuck in the pa_transaction_interface_all table with the error - INVALID_ETYPE_SYSLINK. The reason is that the expenditure type is not tied to the Work in Process expenditure type class. However the user does NOT want to tie it to this class.
This raised two questions:
1) How can user fix these so that they will import, without having to add Work in Process to the expenditure type?
2) Need clarification on what causes an account alias issue to projects, in inventory, to have a WIP accounting class code? Is it because the item being issued to the project, is a "make item"? in order to prevent this from happening in the future, the cause needs to be defined.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms