Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Generate Report in BI 12
Submit Extract 12
Create BI Report 14
Create Extract 19
Generate Report in BI 30
Submit Extract 30
Create BI Report 31
BEN_EXTRACT_JOINED_UE 32
BEN_EXT_ENRT_RSLT_UE 35
BEN_EXT_ENRT_DPNT_UE 38
BEN_EXT_ENRT_BNF_UE 42
BEN_EXT_ENRT_RTCVG_UE 46
1. Use Fusion Benefits Extract aka BENXML to populate the stage tables, and then use HCM extracts to pull the
staged data. HCM Extract will use user entity BEN_EXTRACT_JOINED_UE as the main data group. You
need the carrier and effective dates to be passed as parameters.
2. Use four benefits user entities for direct use in HCM extracts. These UEs query the actual benefits transaction
tables to pull in data from enrollments, dependents, beneficiaries and rates along with few additional
supporting tables. There are over 400 DB items covering almost all attributes such as basic person details,
enrollment Results, person events, covered dependents, beneficiaries, person habits, participant rate and
coverage. You could use other BEN database items via formulas. The support for Benefits UE starts from
release 9.2 upwards. The four UEs are
BEN_EXT_ENRT_RSLT_UE - Enrollment Results
BEN_EXT_ENRT_DPNT_UE - Enrollment Results + Dependents
BEN_EXT_ENRT_BNF_UE - Enrollment Results + Beneficiaries
BEN_EXT_ENRT_RTCVG_UE - Enrollment Results + Rate + Coverage
BENXML will populate the benefits stage tables filtered by Carrier, which is the carrier configured using the
Manage Plan Carriers task in the Plan Configuration work area. Using BEN_EXTRACT_JOINED_UE in HCM
Extract requires additional parameter carrier_id, which is the same carrier id used by BENXML.
This user guide will skip the management of Carrier, for more details please consult the Configuring Benefits Data
Extract for Plan Carriers: Procedure topic in the Cloud Documentation library
(http://docs.oracle.com/cloud/latest/globalcs_gs/docs.htm).
The nature of this option is submitting an extract job of Extract Benefits Data, then use HCM Extract to pull the
data from the previously submitted extract job.
And here, we need to submit a new extract by clicking the Submit button.
Once the extract process is completed, you will see this submitted extract on Extract Benefits Data page.
In the Data Exchange work area, we click Manage Extract Definitions. And then click Create to create a new
extract definition. Here we name the new extract definition as “BEN_JOINED_EXT” and use HR Archive type in
this demonstration.
In this extract definition, we need to use the user entity BEN_EXTRACT_JOINED_UE, which requires carrier_id
and effective_date as input parameters. We will add a new parameter carrier_id, as effective_date is already
created by default. Click Add to add a new parameter entry. Notice that Tag Name must be “carrier_id”, the input
parameter is case sensitive. Data Type is Number, Display Format is Text. Later a new parameter Carrier Id will
show up on the extract submit page.
First we need to create a root data group to contain BEN_EXTRACT_JOINED_UE and name it as BEN_DG. We
configure the data group as follows. Here we use BEN_EXTRACT_JOINED_UE as the source of benefits data.
And we make this data group as Root.
After saving, we can come to the Extract Execution Tree by clicking it on the left panel. Then we will click
Compile All Formula to compile the formulas. When the compilation is done, the green tick shows after the
formula text. You can click Validate to validate the extract definition. If the validation is fine, you may click Export
XML Schema to download a schema xsd file which will be used later to build up RTF template for the report.
If installation is correct. You will find one more tab appears on Microsoft Word.
Generate Report in BI
Submit Extract
Before generating report in BI, the data should be prepared. So we will submit an Extract.
We name this flow as “HY_JF_08”. The name of the flow will be used in Apply Extract Flow and View Report. Be
aware that Process End Date will affect the effective date of processing the extract flow. In the case of
BEN_EXTRACT_JOINED_UE, the user entity will pull the data from the staged table populated after the Process
End Date. Carrier Id’s appearance is responding to the “carrier_id” we added to the extract definition. Then click
Next until you can Submit.
If the extract flow is executed correctly, you will see the following in View Extract Results.
Since we already have generated an RTF template, we can cancel this wizard.
Now we are going to upload the RTF template we generated to build a layout for our report. Clicking the upload
icon, select the generated RTF file and complete the remaining fields as follows then click Upload.
In this section, we will walk through the details of creating an extract definition of the four new benefits user
entities, and use this extract definition to generate a person’s benefits report.
The extract definition we are going to define is more complicated than that in BEN_EXTRACT_JOINED_UE case.
The extract definition has the following structure.
Extract Definition
Employee Block(PER_EXT_SEC_PERSON_UE)
Block Criteria to filter Person Type = ‘EMP’ and Person Id = 300100026493599
Employee Record
Data Elements (Person Full Name)
Benefit Enrollment Results Block
Block Link (Person’s Person Id = Benefits’ enrolled Person Id)
Enrollment Result Record
Data Elements (Life Event, Plan, Program)
Person Dependent Record
Benefit Dependent Enrollments Block
Block Link (Person’s Person Id = Benefits’ enrolled Person Id)
Dependent Enrollment Record
Data Elements (Dependent Name, Life Event, Plan, Program)
Person Beneficiary Record
Benefits Enrollments Beneficiaries Block
Block Link (Person’s Person Id = Benefits’ enrolled Person Id)
Enrollment Beneficiaries Record
Data Elements (Life Event, Plan, Program, Beneficiaries)
Person Rate Coverage Record
Benefit Enrollment Rate Coverage Block
Block Link (Person’s Person Id = Benefits’ enrolled Person Id)
Enrollment Coverage Record
Data Elements (Plan, Program, Rate Value, Coverage Start Date, Life
Event)
Create Extract
Find the Data Exchange in Workforce Management from the Navigator
In the Data Exchange work area, we click Manage Extract Definitions. And then click Create to create a new
extract definition. Here we name the new extract definition as “SIMPLE_BEN_EXT_01” and use HR Archive type
in this demonstration.
On the left of the extract definition work area, we click Data Group to start creating data groups. Data Group is the
element where we associate our user entities. To create a new Data Group, we click Create button.
To properly use PER_EXT_SEC_PERSON_UE, we need to add a filter criteria condition for this data group. To
add a new filter criteria condition, we click Add, a new filter criteria will be created. Then we click the Edit icon, to
add conditions. We configure the condition as follows.
We need to filter the person type “EMP”, note the single quote mark around “EMP” for string data type, and no
single quote mark for person id for number data type. Adding person id here is for demo purpose, to quickly test
and precisely fetch the person data we want.
Now we will link Employees and Benefit Enrollment Results in the correct order. We need to click the target
data group first and then add the connection.
To properly use Benefits Extract user entity, we need to link Benefits Extract data group and its parent data group
with Person Id.
And configure the new record as follows. Be aware to set Next Data Group to Benefit Enrollment Results. It’s
another mandatory step to correctly link two data groups. If Next Data Group is empty, you may need to save the
extract, exit, and then find this extract and come back again.
Then we make the connection for the new created data groups just like Benefit Enrollment Results, as follows.
Then we will complete the details. For demo purpose, we will extract person’s full name from Employee Record
as the header of each employee.
Now we are ready to create record for Benefits Extract data groups. First let’s create a new record for Benefits
Enrollment Results.
Then we do the same for the remaining data groups Benefits Enrollments Beneficiaries, Benefit Enrollment
Rate Coverage and Benefit Dependent Enrollments.
Now it’s time to go to Extract Execution Tree to examine our extract structure. If everything is correctly
configured, the extract structure should look like the following. (Don’t worry about the error mark icon) T hen we
click Compile All Formula, and then we wait a while then check compilation status by clicking Refresh.
Before we go to the next step, we need to download the extract’s XML schema by clicking Export XML Schema.
Clicking Export XML Schema will do the job. The downloaded XML schema file is like this
Here we use a shortcut to add all data into this template, then we keep what we want and remove the rest.
Here there is no Carrier Id input. Be aware that Process End Date will affect the effective date of processing the
extract flow. Then click Next until you can Submit.
If the extract flow is executed correctly, you will see the following in View Extract Results.
Extract Guide.zip
XML schema and RTF template.
You can import the extract definition XML by clicking Import Extract as follows.
BEN_EXTRACT_JOINED_UE
BEN_EXT_ENRT_RTCVG_UE
C ON N E C T W I TH U S
blogs.oracle.com/oracle Copyright © 2015, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
facebook.com/oracle fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
twitter.com/oracle means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
oracle.com
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.0115