FUSION PAYROLL: Payroll Process Cannot Access A Costing Segment Values Set That Has Security Enabled (Doc ID 2194386.1)

Last updated on AUGUST 17, 2017

Applies to:

Oracle Fusion Global Payroll Cloud Service - Version 11.1.11.1.0 to 11.1.11.1.0 [Release 1.0]
Information in this document applies to any platform.
This solution may not apply to Release 12

Symptoms

On : 11.1.11.1.0 version, Global Payroll

ACTUAL BEHAVIOR
---------------
Payroll Process cannot access a Costing Segment Values Set that has security enabled

Payroll is utilizing the same value sets that Finance uses on their Accounting Key Flexfield for their Cost Allocation Key Flexfield. Due to a Finance requirement, they have enabled security on one of the values sets, Cost Center.

Payroll is using the same value set.

We have assigned the correct security role to the payroll user and they can successfully access the value set for costing setups, both at the Department level and the Element level. However, when we run a payroll process or quickpay, the process cannot validate the cost center entries.

It appears that it does not have access to the values stored in the Cost Center value set.


When running a Quickpay, the following Warning Message is received:

FLEX-VALUE DOES NOT EXIST {VALUESET}=Cost Center YRCW {SEGMENT}=Cost Center {VALUE}=Y126
invalid code combination
YRCF.422010.LH.Y126....
FLEX-VALUE DOES NOT EXIST {VALUESET}=Cost Center YRCW {SEGMENT}=Cost Center {VALUE}=9999
invalid code combination
YRCF.211401.99.9999.999999.9999.999.9999



EXPECTED BEHAVIOR
-----------------------

Expect the costing entries to not go to the suspense account


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

Security is enabled on one of the value sets used by the Cost Allocation Key Flexfield.
Finance has established all of the value sets for the Accounting Key Flexfield. Payroll is using the same value sets when defining the Cost Allocation Key Flexfield.
Due to an accounting requirement, Finance has turned on security for one of their segments, Cost Center, which Payroll uses for its value set. Below are the screen prints of the Cost Center YRCW value set, which controls the pick list for Cost Center

Security has been enabled.

There are no cross validation rules on the Payroll side and dynamic insertion is allowed.
Cost Centers are entered at the Department level for the Costed side of costing. The balancing segment also includes Cost Center.

Both of these cost centers are valid and exist in the value set Cost Center YRCW.
We also setup suspense and default accounts at the payroll level.
When running a quickpay using the same user id, the value set validation fails with the following warnings and the suspense accounts are activated:

[the above Warning Message is displayed]

The actual costing data generated are the suspense entries:


LOG FILE
-----------------------

See the following:

statistics group id 50159
FLEX-VALUE DOES NOT EXIST
{VALUESET}=Cost Center YRCW
{SEGMENT}=Cost Center
{VALUE}=9999
FLEX-VALUE DOES NOT EXIST
{VALUESET}=Cost Center YRCW
{SEGMENT}=Cost Center
{VALUE}=Y126

Ended processing at : 06-10-2016 16:12:56
Total Pay Relship count : 1
Total Action count : 2
Successfully processed : 2
Skipped : 0
Unprocessed : 0
Errored : 0




BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, costing entries are placed in the suspense account instead of the desired account

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