My Oracle Support Banner

Concatenated_Segments Field is not Populated in pay_cost_allocation_keyflex When Creating Entries using BEE Spreadsheet (Doc ID 2171561.1)

Last updated on FEBRUARY 27, 2019

Applies to:

Oracle Payroll - Version 12.2.4 to 12.2 HRMS RUP9 [Release 12.2]
Information in this document applies to any platform.
This note provides a brief overview of and .

Symptoms

Problem Statement:

When using the BEE Spreadsheet interface to load the batch lines along with the costing information, the concatenated_segments field is not populated in pay_cost_allocation_keyflex and pay_batch_lines tables. When creating batch lines from the "Batch Lines" form or API(pay_batch_element_entry_api.create_batch_line) properly populates concatenated_segments.

pay_batch_lines.concatenated_segments
pay_cost_allocation_keyflex.concatenated_segments



Steps to Reproduce:

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

  1.  Create batch header and lines from (N) Mass Information eXchange: MIX > BEE Spreadsheet Interface.
  2.  Check pay_cost_allocation_keyflex and concatenated_segments is null.

 

Cause

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
Symptoms
Cause
Solution
References


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