HCM - Extract - Delivery - Options - HCM Extract - Delivery Options Overview
HCM - Extract - Delivery - Options - HCM Extract - Delivery Options Overview
com
Delivery options need to be specified by users as part of the extract definition. Delivery option
parameters specify the output format, delivery method (email, ftp, etc), and other parameters required
for integration with BI Publisher layer.
For example, if FTP is selected as the delivery type, then the Server details, Remote Directory and File
Name would need to be specified.
Similarly for delivery type e-mail, mail address and attachment would be required. In case multiple e-
mail addresses have to be specified, they should be separated by a comma, For example:
[email protected],[email protected].
The delivery options details are mandatory, and need to be specified even if the user just wants an xml
output.
Report Category
Report categories help to create combinations of various delivery options under a single run process or
Report Category. This helps in delivering through a single run, multiple forms of output to multiple users
for an extract definition.
An Example:
Organization wants to extract HR Data and e-mail extracted data as a pdf report to HR, and FTP the same
data in an EFT file to a 3rd party.
To achieve this 2 delivery options are created, and grouped under a report category
To access the BI Publisher, please use ‘Reports and Analytics’ link from the navigator. Once ‘Reports and
Analytics’ page is accessible, browse through the catalog. On the catalog page, new report can be
created (3-Step process) by using menu options indicated on diagram-7 below.
While creating a new report, the application will prompt to provide details of report template and data-
model. The existing standard data model ( Available at this folder location: /Human Capital
Management/Payroll/Data Models/globalReportsDataModel) should be used for all reports.
Parameters Details
Layout Name Free text to identify the underlying report layout. This should be unique
within a report
Template File File name of the RTF/ EFT template saved on the local machine - should be
selected from the browse option
Type Select from the LoV
Locale Language - Select from the LoV
Report Name Users can specify their report name, Free Text
Report Description Optional - A description for the report can be provided
Report Path (See note-1) /Custom/<Your Folder>/<ReportName>.xdo
Note:
1. Users can create their own folder under Custom or Shared folder they have access to
Note: Once the above steps are completed, the BI report should be saved in any of the 'Shared Folders'
locations (accessible to all logins). The report should not be saved under My Folders.
After report is saved, manually schedule (refer FAQ-1) the report and see if output is delivered to
destination. Once it is done, then only, please go ahead and configure delivery options else delivery
options would fail.
e) To check if Email/SFTP is done successfully without any issues. Click on Report Edit > History and see if
process succeeds without errors.
f) If process fails, drill down to get root cause of the issue and fix the BI Server setup configuration issue.
o Link - https://stbeehive.oracle.com/teamcollab/wiki/PDIT+Oracle+Public+Cloud+%28OPC
%29:PDIT+OPC+Docs+-+Multi-Tenant+SFTP+Operational+Document
b) BIP Destination is configured to above SFTP server and will require BI Admin privilege
o Link -
http://docs.oracle.com/cd/E28271_01/fusionapps.1111/e26384/delivery_dests.htm#email_ftp
c) Once manual Scheduling works (using FAQ-1), configure Delivery options with correct server
name ‘fusion_ftp’ (not sftp.cloud.oracle.com)
c) In layout page, choose template in table, Click on output format and make sure ‘CSV’ box is checked.
d) Save report, manually Schedule and see if CSV option is available in LOV
a) While creating a new report, the application will prompt to provide details of report template and data-
model. The existing standard data model (Available at this folder location: /Human Capital
Management/Payroll/Data Models/globalReportsDataModel) should be used for all reports.
b) Simply Save Report. Do not associate/upload any template.
c) In Delivery options provide valid Report path, Output Type as ‘Data’ and Template leave template as blank.
If we need to split and deliver all the individual reports to single person, hardcode E-Mail Address field
with a specific email id (as shown in the above image).
If we need to delivery each report to different people we need to add one Data Element to the Extract
which gives us the email ids of the persons to whom we need to mail respective reports.
Use that data element as E-Mail Address as shown in the below image. But currently there is a bug and the
Busting SQL Query is not retrieving the E-Mail Address from the data element.
For Document OF Record Busting
For Documents of Record, the key additional attributes need to be specified are listed below.
In the delivery options select Delivery Type as Documents of Record.
In Additional Details, give some desired name as Document Name.
The ‘Key’ property should be assigned to Data Element which we considered to be unique value for each
person (or assignment). For example in the extract with which we tested Person Id is the unique value for
each and every block.
Person ID should contain the X-Path of the Person Id data element in the extract. (currently this value
should be x-path, but in future we can take from data element field)
Document Type ID should contain the ID of a document. Since the customer doesn’t have ID’s with them
we need to give a work around for this. The query to get Document Type ID is select
document_type_id,document_type from fusion.hr_document_types_vl;
Need to create a new Data model for each and every extract since the parameters which need to be specified for
the Busting Options comes from the extract created. (As discussed earlier we need to have a unique value, in this
case Person ID)
Split By: Should contain the X-path of a data element which has unique value for each person (or
assignment). In this case Person ID
(/DATA_DS/G_1/G_2/FILE_FRAGMENT/Changes_Only_Demo/Employee_Details_Block/Employee_Basic_D
etails/Person_ID)
Delivery By: It is almost same as Split By parameter,
(/DATA_DS/G_1/G_2/FILE_FRAGMENT/Changes_Only_Demo/Employee_Details_Block/Employee_Basic_D
etails/Person_ID)
Busting Query:
SELECT key key ,TEMPLATE,OUTPUT_FORMAT,OUTPUT_NAME,CALENDAR,'true'
SAVE_OUTPUT,DEL_CHANNEL ,PARAMETER1,PARAMETER2,PARAMETER3,PARAMETER4
,PARAMETER5,PARAMETER6 ,PARAMETER7 ,PARAMETER8 , PARAMETER9 ,PARAMETE10 ,
LOCALE,TIMEZONE
FROM FUSION.PAY_REP_DELIVERY_DTLS where payroll_action_id=:payrollActionId and
ext_delivery_option_id=:deliveryOptionId