My Oracle Support Banner

Why do Distributed Costs go unexpectedly to the suspense account ? (Doc ID 1490203.1)

Last updated on DECEMBER 08, 2020

Applies to:

Oracle Payroll - Version 12.1.3 and later
Information in this document applies to any platform.


If an element is setup to have distributed costing, and none of the elements in the distributed element set have run results, then the costing amounts get costed to the suspense account.

The following message appears in the Costing logfile when LOGGING is enabled:


i/p id = 601, RR id = 383947220, type id = 262, link id = 1275, cost type = D, g
l flag = Y, creator type = N, entry type N, value = 210.68
run_source_id = 107798
Costing normally
In { pycosdis
In { pycosdset
look for distribution set = 19086 date = 2012/08/31
found distribution set = 19086
Out } pycosdset
Sum of run results null or zero in distribution set
In { pycossup
assign action : 2457461XXX has invalid costflex, using suspense account

Is this standard functionality to send to suspense account when no run results for elements to which costs should be distributed?



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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.