Unable To Close Costing Period Due To Stuck SFO Transactions Raised As Exceptions
(Doc ID 2329229.1)
Last updated on FEBRUARY 04, 2019
Applies to:Oracle Fusion Cost Management Cloud Service - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Cost Management
SFO events are stuck in 'Not Started' status
Due to this unable to close costing period due to stuck SFO transactions raised as exceptions
SFO dropship transactions are not processed, these are getting raised as costing period close exceptions.
Costing peroid close validations show error : "UNCSOSTED_TRANSACTIONS"
On Monitor financial orchestration UI see below error:
Service DocumentEnrichment request failed due to an application error:(FOS-3465059)
The issue can be reproduced at will with the following steps:
Complete Dropsihp flow, notice records are in "not started" status in MOnitor FInancial Orchcestration flow
As a result costing is incomplete for the dropship order
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