Last updated on AUGUST 08, 2017
Applies to:Oracle Payroll - Version 12.1.3 and later
Information in this document applies to any platform.
An employee has transferred from one payroll and company to another in the middle of a calendar month pay period. Costing was done correctly by the system with some charges going to one company and some to another based on the prorated amounts paid. But when importing the payroll journal, an error is thrown. The old payroll and new payroll are mapped to different ledgers, but it appears that the journal came over from Payroll with the same ledger. There should be 2 different journals, each mapped to its respective ledger based on payroll. This is resulting in an error because one of the balancing segments is not a valid value for the ledger.
Employee transfers from Payroll A to Payroll B in the middle of the period.
Payroll A is mapped to Ledger A with costing charging company number 123.
Payroll B is mapped to Ledger B with costing charging company number 456.
Costing correctly creates journal lines for company 123 and 456, according to prorated amount paid to each.
Transfer to GL is run
Journal is imported to GL and it is found that one journal is created containing costing for companies 123 and 456, both posting to Ledger B.
It was expected that 2 journals would be created, with costing for Payroll A going to Ledger A for company 123, and costing for Payroll B going to Ledger B for company 456.
Because there are accounting rules attached to Ledger B, an error is thrown because '123' is not a valid value for company (balancing segment).
EM30 This balancing segment value is not valid for this ledger
The issue can be reproduced at will with the following steps:
1. Change employee payroll and company mid period
2. Run Payroll
3. Run Costing and Transfer to GL
4. Run Journal Import from GL and get error
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms