PRC:PO: Transaction Account Builder - Common Error Messages And Solution
(Doc ID 2941250.1)
Last updated on MAY 16, 2023
Applies to:
Oracle Fusion Purchasing Cloud Service - Version 11.1.10.0.0 to 11.13.23.01.0 [Release 1.0]Oracle Fusion Self Service Procurement Cloud Service - Version 11.1.10.0.0 to 11.13.23.01.0 [Release 1.0]
Oracle Fusion Purchasing - Version 11.13.19.01.0 to 11.13.21.10.0 [Release 1.0]
Oracle Fusion Self Service Procurement - Version 11.13.17.08.0 to 11.13.21.10.0 [Release 1.0]
Information in this document applies to any platform.
Symptoms
Common Error Messages in Transaction Account Builder while creating Requisition or Purchase orders.
- Error: The validation failed for one or more errors {0}. (XLA-870336)
- A system error occurred. Contact your help desk. (XLA-870557)
- XLA-870946 The activation of the transaction account definition has failed
- Charge account does not change when user changes the requisition category.
- The value of the attribute Charge Account isn't valid FND FLEX-VALUE DOES NOT EXIST VALUESET DPW_FIN_GLB_COA_CO SEGMENT Company VALUE "XXXX"
- Charge account isn't valid. (POR-2010312)
Possible reasons are the account combination has expired , Allow Posting option isn't selected, or a segment in it isn't accessible to you for security reasons . Contact your general accounting manager. - When I use Validate button on purchase order, Charge account does not change as per expectation.
- Transaction Submission error complaining account is not valid.
- Charge account code combination/Segment value does not get inherited from Employee's expense account even after valid employee expense account and all valid account rules.
Changes
TAD Rules
Cause
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
Symptoms |
Changes |
Cause |
Solution |