
In this Document
|
Symptoms |
|
Cause |
|
1.- Cause# 1: Issue generated for Miscellaneous Issue Transactions |
|
2.- Cause# 2: Issue generated for Account Alias Transactions |
|
3.- Cause# 3: Issue generated for Material Transactions |
|
4.- Cause# 4: Issue generated Average Cost Update Transaction Type |
|
Solution |
|
1.- Resolution for Cause# 1: Issue generated for Miscellaneous Issue Transactions |
|
2.- Resolution for Cause# 2: Issue generated for Account Alias Transactions |
|
3.- Resolution for Cause# 3: Issue generated for Material Transactions |
|
4.- Resolution for Cause# 4: Issue generated Average Cost Update Transaction Type |
|
References |
Applies to:
Oracle Cost Management - Version 11.5.10.2 and later
Information in this document applies to any platform.
Symptoms
Material Transactions are not getting accounted after a particular transaction which is stuck with the following Error
ERROR
--------
CST_NO_TXN_INVALID_ACCOUNT
CSTPLCIN.COST_INV_TXN:An invalid account is associated with the item being transacted.
CSTPAVCP.COST_ACCT_EVENTS
Cause
Several reasons might be generating this situation:
1.- Cause# 1: Issue generated for Miscellaneous Issue Transactions
It was observed that in In Oracle Inventory, when performing a VMI
Issue transaction in the mobile side, the following error occurs Error=
"CST_NO_TXN_INVALID_ACCOUNT".
The following justifies how the issue is related to this specific customer:
This was same as
Bug 10147808 - MOBILE MISCELLANEOUS ISSUE SAVES NULL DISTRIBUTION_ACCOUNT_ID IN MMT which was reported in R12.0.4
In R11i this was also reported in
Bug 9360153
- RCA FOR CST_NO_TXN_INVALID_ACCOUNT COSTING ERROR FOR MISCELLANEOUS
ISSUE, but never pursued due to inactivity. So this will be a backport
from
Patch. 10147808.
This is explained in the following bug:
Bug <13654260> - 1OFF:10147808:11.5.10.2:11.5.10.2:MOBILE MISCELLANEOUS ISSUE SAVES NULL DISTRIBUTION
2.- Cause# 2: Issue generated for Account Alias Transactions
The issue is caused by the following setup:
Cost Variance Account against related transaction cost group was set
to NULL, so whenever a transaction is going to get costed and it's
related accounting distribution need to hit
a Variance Account that
is not populated there it will show error like
CST_NO_TXN_INVALID_ACCOUNT CSTPLCIN.COST_INV_TXN:An invalid account is
associated with the item being transacted
The same was pointed under
Bug 3046209 - ERRORED COST TRANSACTION WHEN PERFORMING PO RECEIPT
3.- Cause# 3: Issue generated for Material Transactions
The cause of the issue is invalid / missing DISTRIBUTION_ACCOUNT_ID
or ENCUMBRANCE_ACCOUNT in table MTL_MATERIAL_TRANSACTIONS.
The data should have DISTRIBUTION_ACCOUNT_ID / ENCUMBRANCE_ACCOUNT
Bug 5709941 -
The issue is due to Account Alias /Misc Transactions are created with user entered/setup Account
4.- Cause# 4: Issue generated Average Cost Update Transaction Type
In case of Average Cost Update transaction type the expense_account_id was missing from mtl_material_transactions table.
Customer
had On Hand Variance and it does not have On Hand Variance Account in
mtl_material_transactions table in the expense_account_id column, Due to
this when the actual worker runs, it hits the invalid account error.
Issue is described in
Bug 14197624 - CST_NO_TXN_INVALID_ACCOUNT AN INVALID ACCOUNT IS ASSOCIATED WITH THE ITEM BEING
Solution
1.- Resolution for Cause# 1: Issue generated for Miscellaneous Issue Transactions
To implement the solution, please execute the following steps::
1.1 Download and review the readme and pre-requisites for
Patch. 13654260.
1.2 Ensure that you have taken a backup of your system before applying the recommended patch.
1.3 Apply the patch in a test environment.
1.4 Confirm the following file versions:
Check the file version of the following files:-
$INV_TOP/java/invtxn/server/IssueTrxPage.java 115.101.115100.2
1.5 Retest the issue.
1.6 Migrate the solution as appropriate to other environments.
2.- Resolution for Cause# 2: Issue generated for Account Alias Transactions
To implement the solution, please execute the following steps::
2.1 Go into the responsibility: Cost Management.
2.2 Navigate to Setup > Cost group.
2.3 Query for cost group against which the issue appears and populate the value for the Cost Variance Account then save
2.4 Retest the issue , resubmitting the Transaction for costing using the Inventory> Material Transaction Form.
2.5 Migrate the solution as appropriate to other environments.
3.- Resolution for Cause# 3: Issue generated for Material Transactions
Check the following update script, please execute it on TEST INSTANCE first after taking appropriate back up.
For the failing transaction id Please follow this action plan.
3.1 Cancel the Cost Manager:
System
Administrator -- Requests -- View -- Go To Specific Request and in the
Name give Cost Manager. From here cancel the Cost Manager that is
Pending Scheduled.
3.2 Create a back up table of MMT
Create table MMT24APR as select * from mtl_material_transactions where costed_flag in('E' ,'N')
3.3 The following sql may help in finding the account_id:
select CONCATENATED_SEGMENTS, code_combination_id
from gl_code_combinations_kfv
where CONCATENATED_SEGMENTS = '&user_account'
also use the following note
<
Doc ID 400088.1> How To Determine The DISTRIBUTION_ACCOUNT_ID For Inventory
3.4 update mtl_material_transactions
set distribution_account_id = &enter_account_id
where ENCUMBRANCE_AMOUNT is not null
and ENCUMBRANCE_ACCOUNT is null
and organization_id = &org_id
and transaction_id = &txn_id
3.5 Update mtl_material_transactions
Set costed_flag = 'N',
transaction_group_id = null,
error_code = null,
error_explanation = null
where costed_flag in ('N','E');
3.6 Commit
3.7 Launch the Cost Manager
Inventory -- Setup -- Transactions -- Interface Managers --- Tools (Menu Bar) - - Launch Manager --Submit (No scheduling for the Cost Manager should be done in the Request Form)
Also
1. Find the cost group associated with the erred transaction.
2. Navigate to the cost group form via Inventory > Setup > Costs
> Costs Groups > Query up the Cost Group for the cost_group_id
associated with the erred record.
3. When more than one
organization is involved in this situation, the Account for the Cost
Group should be created in the Organization where the transaction is
being transacted. For example for Sales Orders.
4. Enter the expense account for the Cost Group and Cost Variance Account and save.
5. Resubmit the erred transaction for costing.
4.- Resolution for Cause# 4: Issue generated Average Cost Update Transaction Type
If you encounter the issue described above, please log a SR and request datafix to Oracle Customer Support (Cost Management Support Team).
Still Having Questions?
To provide feedback on this note, click on the Rate this document link.
References
BUG:10147808 - MOBILE MISCELLANEOUS ISSUE SAVES NULL DISTRIBUTION_ACCOUNT_ID IN MMT
BUG:3046209 - ERRORED COST TRANSACTION WHEN PERFORMING PO RECEIPT
Material Transactions with Error CSTPLCIN.COST_INV_TXN An Invalid Account Is Associated With The Item Being Transacted (文档 ID 429153.1) |
![]() |
![]() |