Costing is Charging the Suspense Account for Unknown Reason (Doc ID 1959500.1)

Last updated on JUNE 08, 2016

Applies to:

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

Symptoms

Costing segment values have been entered at various levels of the costing hierarchy, but the Suspense Account is being charged instead of the expected code combination.

In the detailed Costing log file, the following messages are noted:

FND_FLEX_KEYVAL.validate_segs mode V
invalid code combination
     Out } pycosaolplsql
   Out } pycosaol
   In  { pycossup
assign action : XXXXXXXX has invalid costflex, using suspense account

and

line_text = 56, The following required field does not have a value: [Segment Name]
 Out } pyxipmt
 In  { pylogpop
 Out } pylogpop
 In  { pyxipmt
message text = invalid code combination:

 
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login to HRMS Manager
2. Enter costing segment values at various levels of costing hierarchy
3. Run Costing
4. Review costing results and see the suspense account has been charged instead of the entered costing code values



Cause

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