Interface Service Cost To Projects Fails: "The Expenditure Organization Is Not Active."
(Doc ID 2413476.1)
Last updated on FEBRUARY 06, 2022
Applies to:
Oracle Field Service - Version 12.2.3 and laterInformation in this document applies to any platform.
Symptoms
Interface Service Cost to Projects fails with error after user enters wrong Expenditure Organization in a Service Request (SR).
Error:
The expenditure organization is not active.
Steps:
(R) Field Service Dispatcher
(N) Service Requests > Create Service Request
- SR # 1XXXX
- Business user incorrectly chose the WRONG Expenditure Organization => “<ORG_NAME> “
- A Task was created, and debrief completed with the incorrect Expenditure Organization
(R) Oracle Projects
(N) Requests > Run
- "Interface Service Costs to Projects"
- Param = Operating Unit = MyOU
- Completed with Status = Normal
- Results:
. # of cost records considered for insertion into Oracle Projects interface table => 2
. # of cost records successfully inserted into Oracle Projects interface table => 0
. # of cost records that failed to be inserted into Oracle Projects interface table => 2
- Details of the Cost records that failed insertion:
Cost Id = 5XXXX, SR # 1XXXX - Reject Reason = "The expenditure organization is not active."
Cost Id = 5XXXX, SR # 1XXXX - Reject Reason = "The expenditure organization is not active."
Changes
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 |
References |