Datafix/Root-Cause: Uncosted Transaction Error: CST_INVALID_ACCT_ALIAS / The Account Alias Is Not Defined For This Org [Video]
(Doc ID 428403.1)
Last updated on APRIL 24, 2019
Applies to:Oracle Inventory Management - Version 220.127.116.11 and later
Information in this document applies to any platform.
FORM:INVTVTXN.FMB - View Transactions
This document includes all versions of 11i
This document includes all versions of R12.0.x, R12.1.x, and R12.2.x.
Find uncosted transactions with the following error in the Material Transactions (INVTVTXN.fmb) form.
Error (Error Code: CST_INVALID_ACCT_ALIAS)
See the costing error with the following steps BUT users could not replicate the issue at will:
- Navigate to Inventory > Transactions > Material Transactions
- The find window appears
- Enter the query criteria.
- Press Find.
- Navigate to the Reason, Reference tab.
- Review the error code / error explanation.
Steps: Forcing the Issue
Support engineers were able to force the issue to happen with 2 scenarios. In scenario #1, the engineer used Help > Diagnostics > Examine to clear the account alias source id. The record saved and caused the data corruption. In scenario #2, the navigation including a backwards tab allowed the engineer to clear the source.
Scenario #1: Help > About
This is not a recommended and NOT a supported approach but discussed here to show how the issue could be tested.
Video - Issue With Help > Diagnostics (02:45)
Scenario #2: Backwards Tab
This is not a recommended approach but discussed here to show how the issue could be tested. You start to enter a transaction, go back to the header information and backward tab to the date. After this, you can perform a transaction without the source entered.
Users cannot close the related inventory period related to the transactions. All transactions must be costed before the period can close.
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
|1. Check the data.|
|2. Backup data.|
|3- Run the datafix script.|
|4- Check the data.|
|B. Preventing the Issue|