Unable To Close Costing Period Due To Stuck SFO Transactions Raised As Exceptions
Last updated on NOVEMBER 16, 2017
Applies to:Oracle Fusion Cost Management Cloud Service - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On : 184.108.40.206.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
This is a spin off from 3-15627146471
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
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms