Documente Academic
Documente Profesional
Documente Cultură
December 2013
Introduction ....................................................................................... 1
Batch Load Summary Extract ............................................................ 2
Getting Started .................................................................................. 2
Step 1: Create a Copy of the Seeded Extract ................................ 3
Step 2: Generate and Compile the Fast Formulas ......................... 3
Step 3: Modify the Parameter Attributes for the Extract ................. 4
Run the Extract .............................................................................. 6
Extract Output Next Steps .......................................................... 8
Summary ..................................................................................... 11
Introduction
This white paper provides background and usage of the seeded System Extract template
Batch Load Summary.
This seeded template enables File-Based Loader (FBL) integrators to extract details of any
errors that occur during batch load. The report can be extracted in the XML or BI Publisher
format.
Audience
This document is not particularly technical in nature, and is mainly of interest to integration
architects and developers needing to understand how to extract FBL error reports.
PARAMETER
DESCRIPTION
Name of the file from which the batch is loaded. It is populated in the
PARAM_VALUE column of HRC_XFER_JOB_PARAMS table. You can find
the value by looking at the Content ID column in File Import and Export
screen
Batch Name
Batch Id
Line Status
Error in Row
Ignore
New
Pending Action
Ready to Process
Successful
Getting Started
Oracle recommends that you make a copy of the seeded System Extract Batch Load Summary to use
this functionality. Adopting this approach gives you more flexibility when defining output options and
formatting choices. This white paper will lead you through the steps required to copy the extract and
then modify it to obtain the desired functionality.
The basic steps are as follows: 1. Create a copy of the seeded extract.
You must now compile the Fast Formula for the System Extract Batch Load Summary copy created in
the previous step.
1. In the Data Exchange work area, search for the copied extract and click the edit icon.
2. In the object tree browser, click Header Details within the Batch Header block.
3. From the Actions menu, select Generate Formula and then select Compile.
4. Repeat step 3 for Error Details and Error Stack within the Batch Errors block.
5. Save and Close changes and then re-query.
Confirmation of successful compilation of formula is indicated by green tick in the Extract Records
for both the Batch Header and Batch Errors blocks.
A summary of these steps is show in Figure 2 and Figure 3.
[Note: The parameters below are presented to the user each time the extract is run. The sequence
number change ensures that the relevant parameters are displayed in the correct order.]
FLOW PARAMETER CHANGES
PARAMETER
COLUMN TO CHANGE
NEW VALUE
Batch Id
Sequence
70
Batch Name
Sequence
60
Effective Date
Display
Parameter Basis
Context Bind
Basis Value
System Date
Start Date
Display
No a start date is not needed for this extract so we can hide it.
Line Status
Parameter Basis
Constant Bind
Basis Value
Error in Row
Sequence
80
Sequence
50
Sequence
90
Figure 4. Modifying Parameters for Copied Extract [Note: Payroll Flow Patterns is underlying UI]
Provide a name in the Payroll Flow field for the extract you want to create [Note:
This name is referred to when running the subsequent report.]
b. Enter a value for one or more of the following parameters [details of each provided
earlier in this document].
c.
Batch Name
Batch Id
Leave the default value Error in Row in the Line Status field [details earlier in this
document].
The Payroll Flow checklist page provides status information on the submitted extract.
Defining a Simple HR Outbound Interface Using HCM Extracts MOS Note ID 1429892.1
You can use the System Extract parameter, Process Configuration Group, for debugging.
Payroll process configuration groups provide sets of payroll action parameters, primarily related to
logging and performance, for your processes and reports [System Extract falls in this category]. When
you run a process, you can select a process configuration group. If you do not select a process
configuration group, the application uses the parameter values in the default group, which means
logging would normally be off [unless this has been modified by the customer].
Normal operation for this extract is to leave the parameter blank.
If it is required to debug an issue with this extract and the underlying data, then a Process
Configuration Group should be supplied which has had logging enabled.
Follow these steps:-
1. Navigate to the Manage Payroll Process Configuration task from the Setup and Maintenance work
area.
2. Create a new group giving it a meaningful name, Save and Close.
3. Select the newly created group and in the Configuration Group Details window below, edit
Logging Category and put in the value GF, Save and Exit
4. Resubmit your extract adding in this group when prompted in the Extract Parameters page.
The log can then be found in the System Extract Log File which is available in the Schedule Process
UI or in the Payroll Checklist UI.
3. Select Data Model, and then select /Shared Folders/Human Capital Management/Payroll/Data
Models
4. Select globalReportsDataModel.xdm and click OK.
Figure 9. Selecting the Data Model for the BI Publisher Report Definition
5. Select the Use Report Editor option and click Finish.
6. Save the report as XX Batch Error Report under Shared Folders/Custom/Human Capital
Management/
7. Click the Save icon on the top right.
10
Figure 11. Viewing the XML Output from Batch Error Report System Extract
Summary
A basic outline on how to generate an xml output from the System Extract has been provided in the
previous steps. The reader is free to generate the output in whichever format is suitable for
consumption by the source system. Full details on how to write different outputs is provided in
documentation for BI Publisher.
11
File-Based Loader
December 2013
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 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 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.
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. 0113