Job Data Component Interfaces: Ben Prog Key Structure Inconsistencies
Last updated on MARCH 06, 2017
Applies to:PeopleSoft Enterprise HCM Human Resources - Version 9.1 and later
Information in this document applies to any platform.
Job Data Component Interfaces: Ben Prog key structure inconsistencies
HRMS Bundle #10 has modified the Job Data CIs. The key structure for the CWR Job Data component interface has been changed for the Benefit Program record (BEN_PROG_PARTIC).
This has been changed to include the COBRA_EVENT_ID field as a key property. This is actually correct as it reflects the key structure for the record. However, it is now inconsistent with the other Job Data CIs, in particular the CI used to create employees (as opposed to contingent workers).
This is an issue because users should have the same functionality when using CIs regardless of whether they are loading an employee or a contingent worker.
Also, as delivered the CI for updating Job Data (CI_JOB_DATA) does not contain the Benefit Program record at all. Ie there is no facility provided to allow this to be updated via a CI
Customer uses the following:
CI_JOB_DATA - BEN_PROG_PARTIC collection does not exist
CI_JOB_DATA_EMP - COBRA field does not exist which is incorrect
CI_JOB_DATA_CWR - COBRA field exists which is correct
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