an overview of fusion applications
Post on 23-Feb-2018
235 Views
Preview:
TRANSCRIPT
-
7/24/2019 An Overview of Fusion Applications
1/243
An Overview of Fusion ApplicationsBy Ashish Harbhajanka (Evangelist, Cloud Consultant, Solution Architect)
Email: ashish1234u@gmail.com
This Book is an Attempt by me to explain some of the very basic concepts about few which are divided into several chapters as below:
Introduction of Why to Adopt Fusion Applications
Chapter 1: HCM Data Loader
Chapter 2: BIP Reports
Chapter 3: OTBI Reports
Chapter 4: Creating Custom ESS Jobs in Fusion Applications
Chapter 5: Fusion Absence Management
Chapter 6: Fusion Fast Formulas
Chapter 7: Fusion HCM Extracts
Chapter 8: Other Topics
-
7/24/2019 An Overview of Fusion Applications
2/243
ContentsBusiness Requirement .............................................................................................................................................................................................................................. 81
INTRODUCTION ........................................................................................................................................................................................................................................ 99
INTRODUCTION ....................................................................................................................................................................................................................................... 143
BUSINESS REQUIREMENT ........................................................................................................................................................................................................................ 144
.......................................................................................................................................................................................................................... 156
................................................................................................................................................................................................................................ 159
Formula Code :....................................................................................................................................................................................................................................... 161
Screenshot : ............................................................................................................................................................................................................................................ 162
Custom HCM Extract Creation: Available Options ................................................................................................................................................................... 165
ORACLE DELIVERED REPORTS ....................................................................................................................................................................................................... 175
NAVIGATION TO RUN DELIVERED REPORTS ............................................................................................................................................................................... 175
-
7/24/2019 An Overview of Fusion Applications
3/243
DELIVERED REPORT 1 -> USER ROLES DISPLAY .................................................................................................................................................................................. 176
DELIVERED REPORT 2 -> USER AND ROLE : ROLE DETAILS ................................................................................................................................................................ 177
DELIVERED REPORT 3 -> USER AND ROLE : USER DETAILS ...................................................................................................................................................... 179
NEED FOR A CUSTOM CONSOLIDATED REPORT ......................................................................................................................................................................... 179
SQL USED FOR USER AND ROLE DETAILS REPORT ..................................................................................................................................................................... 179
CONDITIONAL FORMATTING ............................................................................................................................................................................................................... 181
REPORT OUTPUT ................................................................................................................................................................................................................................ 182
ESS JOB CREATION ............................................................................................................................................................................................................................ 183
RUNNING SCHEDULED JOB FOR ONE PERSON ............................................................................................................................................................................. 185
-
7/24/2019 An Overview of Fusion Applications
4/243
Why to Adopt Fusion ApplicationsINTRODUCTION
Fusion as the word suggests stand for Culmination / Mix / Combination.
In context of Oracle, Fusion is referred as Fusion Applications.
So Why Fusion Applications ?
Before that lets understand What is Fusion Applications ?
Fusion Application is a new Oracle Product to cater to ERP Needs.
But we already have so many ERP Applications. Some of the most popularly used being EBS (E-Business Suite), PeopleSoft, JDEdwards to name a
few. So why a new ERP application to cater to business needs. The answer is :
Fusion Applications is an attempt ( and for that matter a very popular and widely accepted one) by Oracle . It takes the best features from EBS and
PeopleSoft and does makes life simpler for Business Users and (Both Functional and Technical) Implementation Consultants .Lets try to get into
more details of the same . We would categorize this discussion into two broad categories namely:
a)
Business Reasons ( Details about why should Business adopt Fusion)
b) Functional Reasons ( Details about why should Functional Consultant adopt Fusion)
c) Technical Reasons ( Details about why should Technical Consultant adopt Fusion)
BUSINESS REASONS
i)
Easy to use
ii)
Better Look and Feel
iii)
Better Functionality
iv)
Better User Experience
FUNCTIONAL REASONS
-
7/24/2019 An Overview of Fusion Applications
5/243
i)
Configuration is simpler ( Most configurations from Setup and Maintainenance)
Setup and Maintenance
Most of the setups start with Manage% ( screenshot below)
-
7/24/2019 An Overview of Fusion Applications
6/243
ii) Configuration is based on Train Stop Models ( First Step guides you to second step and so on)
Train Stops (First Step Takes you to second step and so on )
-
7/24/2019 An Overview of Fusion Applications
7/243
iii) Allows What IF Scenarios (Manage Enterprise Structures, Allows Multiple Combination but Loads just one)
Below Screenshots gives details of creating Enterprise Structures ( and then to view to Technical Summary Report). This would not get loaded but
would be used for comparative analysis. Screenshots displaying what-if scenarios ( ESC Setup Example) .
Example of WHAT IF SCENARIO ( Using Enterprise Structure Configurator)
WHATIFSCENARIOEXAMPLE->STEP 1:MANAGE ENTERPRISE
WHATIFSCENARIOEXAMPLE->STEP 2:MANAGE DIVISIONS
-
7/24/2019 An Overview of Fusion Applications
8/243
WHATIFSCENARIOEXAMPLE->STEP 3:MANAGE LEGAL ENTITIES
WHATIFSCENARIOEXAMPLE->STEP 4:CREATE BUSINESS UNITS
-
7/24/2019 An Overview of Fusion Applications
9/243
WHATIFSCENARIOEXAMPLE->STEP 5:MANAGE BUSINESS UNITS
WHATIFSCENARIOEXAMPLE->STEP 6:MANAGE REFERENCE DATA SETS
-
7/24/2019 An Overview of Fusion Applications
10/243
WHATIFSCENARIOEXAMPLE->STEP7:MANAGE BUSINESS UNIT SET ASSIGNMENT
WHATIFSCENARIOEXAMPLE->STEP 8:MANAGE LOCATION REFERENCE SET
-
7/24/2019 An Overview of Fusion Applications
11/243
WHATIFSCENARIOEXAMPLE->INTERVIEW RESULTS
WHATIFSCENARIOEXAMPLE->MANAGEMENT REPORTING STRUCTURE
-
7/24/2019 An Overview of Fusion Applications
12/243
WHATIFSCENARIOEXAMPLE->TECHNICAL SUMMARY REPORT
-
7/24/2019 An Overview of Fusion Applications
13/243
WHATIFSCENARIOEXAMPLE->CLICK ON DOWNLOAD TECHNICAL SUMMARY REPORT TO GET PDFREPORT
-
7/24/2019 An Overview of Fusion Applications
14/243
WHATIFSCENARIOEXAMPLE->REPORT SCREENSHOTS
-
7/24/2019 An Overview of Fusion Applications
15/243
-
7/24/2019 An Overview of Fusion Applications
16/243
-
7/24/2019 An Overview of Fusion Applications
17/243
-
7/24/2019 An Overview of Fusion Applications
18/243
-
7/24/2019 An Overview of Fusion Applications
19/243
We can configure multiple such Enterprise Values and compare before loading one. So we can have WHAT IF scenarios. This feature is not sup-
ported in older Legacy Systems ( EBS / PPLSOFT).
TECHNICALREASONS
Broad Responsibilities of any Technical Resource on any ERP Implementations are :
A) INBOUND INTEGRATION (HDLFROM RELEASE10MAKES LIFE SIMPLER,DATALOADON BUTTONCLICK)
B)
REPORTING(BIP/OTBI/OBIA)C) OUTBOUNDINTEGRATION(HCMEXTRACTS)
All the above three are very easy to implement in Fusion HCM.
So, It is for all the above stated reasons we should have Fusion Applications. Happy Adoption.Cheers
-
7/24/2019 An Overview of Fusion Applications
20/243
-
7/24/2019 An Overview of Fusion Applications
21/243
Chapter 1: HCM Data LoaderComprises Details About What an HCM Data Loader.
Why to Use HCM Data Loader
How to Configure HCM Data Loader
-
7/24/2019 An Overview of Fusion Applications
22/243
What is HCM Data Loader
INTRODUCTION
HCM Data Loader aka (also known as ) HDL is the next generation Data Loading Tool used in Fusion Applications.
Mostly used in all new implementation starting July 2015 this tool has tremendously advanced features compared to its predecessor FBL (File Based
Loader).
In this article we would t ry to understand what HDL is and also a brief understanding of key concepts associated with the same.Rolerequired for using HCM Data Loader is Human Capital Management Integration Specialist
So without much ado lets begin.
MAJOR ENHANCEMENTS OVER FBL
1. Bulk loading of HCM data from any source
2. Data-migration or incremental updates
3. Flexible, pipe-delimited file format
4. Comprehensive bulk loading capabilities
5. Automated and user managed loading
6. Stage Table Maintenance
WHILE THE ABOVE 6ARE THE ONES MOSTLY STATED AND POPULARLY ADVERTISED FEATURES IHAVE A SLIGHTLY DIFFERENT VIEW AND THEY
ARE :
1. BULK LOADING OF HCMDATA FROM ANY SOURCE
THIS POINT TO ME DOESNT SEEMS VALID AS FBLALSO USED TO DO THE SAME THING AND HENCE IWILL DISCARD THIS
-
7/24/2019 An Overview of Fusion Applications
23/243
2.
DATA MIGRATION OR INCREMENTAL UPDATES
FBLDOES THE SAME BUT IF YOU HAVE SAY NRECORDS FOR AN EMPLOYEE AND YOU WANT TO ADD ONE MORE RECORDS YOU NEED TO
PASS ALL N+1RECORDS
USING HDLYOU WOULD BE REQUIRED TO JUST PASS THE (N+1)TH RECORD SO A MAJOR ENHANCEMENT
3. FLEXIBLE,PIPE-DELIMITED FILE FORMAT
AVAILABLE IN FBLTOO HENCE DISCARDED AGAIN.
4. COMPREHENSIVE BULK LOADING CAPABILITIES
AVERY NEW ADVANCED AND ENHANCED FEATURE.
5.
AUTOMATED AND USER MANAGED LOADING
FBLCAN ALSO BE AUTOMATED USING WEB SERVICE CALL HENCE AGAIN DISCARDED.
6. STAGE TABLE MAINTAINENACE
THIS AGAIN WAS IN FBLTOO HENCE DISCARDED AGAIN.
SO NOW WE WILL PRIMARILY DISCUSS ABOUT 2POINTS NAMELY :
a)
DATA MIGRATION OR INCREMENTAL UPDATES
b)
COMPREHENSIVE BULK LOADING CAPABILITIES.
DATA MIGRATION OR INCREMENTAL UPDATES
WE WILL TAKE AN EXAMPLE OF VARIOUS EVENTS IN AN INDIVIDUALS LIFE AND CO-RELATE THE SAME AS DATA TRANSACTIONS.DETAILS OF SAME
EXPLAINED BELOW :
HIRE AN EMPLOYEE
MS.SANDRA MORA IS A LADY WHO JOINS A COMPANY AND BECOMES EMPLOYEE ON 15JUN 2003.SHE GETS A UNIQUE IDENTIFIER (LIKE SSNFOR
US,PANCARD FOR INDIA TO UNIQUELY IDENTIFY A INDIVIDUAL ,SIMILARLY EACH COMPANY HAS A UNIQUE IDENTIFIER TO IDENTIFY AN EM-
PLOYEE THIS UNIQUE IDENTIFIER IS REFERRED TO AS EMPLOYEE NUMBER )NO 12345.
-
7/24/2019 An Overview of Fusion Applications
24/243
MARITAL STATUS CHANGE
SHE GETS MARRIED ON 21STAUG 2006AND UNDERGOES FOLLOWING CHANGES IN HER EMPLOYEE RECORD:
1) TITLE:GETS CHANGED FROM MS TO MRS.
2) LAST NAME : HER LAST NAME GETS CHANGED FROM MORATO BJORK
3) EMAIL ADDRESS :HER EMAIL ADDRESS GETS CHANGED FROMSandra.mora@abc.netTOSandra.bjork@abc.net
SHE AS A RESULT OF THIS CHANGE THE PREVIOUS RECORD (HIRE AN EMPLOYEE)GETS END-DATED ON 20THAUG 2003AND A NEW RECORD GETS
CREATED ON 21STAUG 2006
MIDDLE NAME CHANGE
SHE GETS A MIDDLE NAME ADDED (SHE DECIDED TO HAVE HER HUSBANDS FIRST NAME ADDED IN HER NAME ON 16THJULY 2008)AND A NEW REC-
ORD GETS CREATED.
1)
MIDDLE
NAME
:G
ETS CHANGED FROM TOA
LBERT.
FTECAPACITY CHANGE
STARTING 25THSEP 2009SHE STARTS WORKING ONLY ON 4DAYS A WEEK INSTEAD OF INITIAL 5DAYS A WEEK SO HER FULL TIME EQUIVALENT
(FTE)GETS CHANGED FROM 1(ACTUAL DAYS WORKED IN A WEEK (5)/TOTAL WORKING DAYS IN A WEEK (5))TO NEW VALUE 0.8(ACTUAL
DAYS WORKED IN A WEEK (4)/TOTAL WORKING DAYS IN A WEEK (5))
1)
FTECAPACITY CHANGE:GETS CHANGED FROM 1TO 0.8
EMAIL ADDRESS CHANGE
SHE UNDERGOES A EMAIL ADDRESS CHANGE AS ON 17THMARCH 2012
1)
EMAIL ADDRESS:GETS CHANGED FROM SANDRA.BJORK@ABC.NET TO SANDRA.BARON@ABC.NETMIDDLE NAME CHANGE
SHE GETS A MIDDLE NAME ADDED (SHE DECIDED TO HAVE HER FATHERS FIRST NAME ADDED IN HER NAME ON 12THDEC 2003)AND A NEW RECORD
GETS CREATED.
MIDDLE NAME:GETS CHANGED FROM ALBERT TO FRANK.
THE SAME DETAILS REPRESENTED IN A TABULAR FORMAT FOR EASIER UNDERSTANDING.
mailto:Sandra.mora@abc.netmailto:Sandra.mora@abc.netmailto:Sandra.mora@abc.netmailto:Sandra.bjork@abc.netmailto:Sandra.bjork@abc.netmailto:Sandra.bjork@abc.netmailto:Sandra.bjork@abc.netmailto:Sandra.mora@abc.net -
7/24/2019 An Overview of Fusion Applications
25/243
COMPREHENSIVE BULK LOADING CAPABILITIES
-
7/24/2019 An Overview of Fusion Applications
26/243
-
7/24/2019 An Overview of Fusion Applications
27/243
DATA LOADER PROCESS FLOW DIAGRAM
HCMDATA LOADER SUPPORTED BUSINESS OBJECTS
-
7/24/2019 An Overview of Fusion Applications
28/243
FLEXIBLE PIPE-DELIMITED FILE FORMAT
-
7/24/2019 An Overview of Fusion Applications
29/243
AUTOMATED OR USER MANAGED PROCESSING
IMPORT AND LOAD DATA
-
7/24/2019 An Overview of Fusion Applications
30/243
PROGRESS ICONS
FILE LINE COUNTS
-
7/24/2019 An Overview of Fusion Applications
31/243
OBJECT COUNTS
OBJECT ERRORS
-
7/24/2019 An Overview of Fusion Applications
32/243
STAGE TABLE MAINTAINENANCE
-
7/24/2019 An Overview of Fusion Applications
33/243
HDLFEATURE GUIDELINES
-
7/24/2019 An Overview of Fusion Applications
34/243
WHILE PERFORMING CONVERSION :STEP 1->CONFIGURE SOURCE SYSTEM OWNER
THERE COULD BE MULTIPLE SOURCES FROM WHICH DATA CAN BE MIGRATED TO FUSION ,HENCE A SOURCE SYSTEM OWNER NEEDS TO BE CON-
FIGURED FOR UNIQUE IDENTIFICATION OF LEGACY DATA SOURCE.BELOW SCREENSHOT SHOWS HOW TO CONFIGURE THE SAME.
-
7/24/2019 An Overview of Fusion Applications
35/243
WHILE PERFORMING CONVERSION:STEP 2->CONFIGURE HCM DATA LOADER
-
7/24/2019 An Overview of Fusion Applications
36/243
HCMDATA LOADER :ERROR REPORTS GENERATION USING DELIVERED HCMEXTRACTS
As with all delivered HCM Extracts, it i s recommended that you make a copy of the HCM Data Loader Data Set Summary extract and alter the out-
put to your requirements.
Navigate to the Manage Extract Definitions task available from the Data Exchange work area.
Query the HCM Data Loader Data Set Summary extract.
You click the copy icon to copy the seeded extract, supply your name for the copied extract.
Once your copy is successfully created you can retrieve it by searching for it by name. Click on the name in the Search Results to make your re-
quired changes
-
7/24/2019 An Overview of Fusion Applications
37/243
IMPLEMENTATION DECISION POINTS
Last but not the least Human Capital Management Integration Specialist isthe RoleRequired to Perform Conversion.. That brings me to end
of the topic.
Thanks a lot for all your time .. Have a Nice Day!!!!!!!!!!!!!
Why To Use HCM Data Loader
Customers currently provisioned on Release 9 will require a configuration change.
All environments provisioned in Release 10 will be defaulted to HDL.
-
7/24/2019 An Overview of Fusion Applications
38/243
Existing Customers may continue using File Based Loader (FBL) but should begin evaluating HDL to plan a migration in the future, where applica-
ble.
There are a few scenarios where HDL may not be recommended, and an exception may be considered, for both, existing and new Customers.
SITUATIONS WHERE HCMDATA LOADER MAY NOT BE RECOMMENDED
a)
An existing customer using File-Based Loader who purchases additional test environment that is created on R10.
b) The customer must log an SR to change the default setting of Full to Limited to match other environments.
c) Customers with PeopleSoft Integration.
d) Customers with Taleo Integration via Taleo Connect Client (TCC) and File-Based Loader.
MIGRATING FROM FILE-BASED LOADER TO HCMDATA LOADER
1. Is File-Based Loader used for migration only? If so, once migration is complete, then HCM Data Loader could be considered.
2.
Is File-Based Loader used for ongoing integration? If so, then there will need to be rework of processes and a cutover decision.
3. How are File-Based Loader data files generated? Whatever method is used for generating the File-Based Loader data files will need to be
reworked to generate the correct HCM Data Loader format.
4.
The complexity of the integration will need to be taken into account to determine who does the rework of the extract mechanism.
5.
Are you loading objects outside of File-Based Loader and HCM Spreadsheet Data Loader (via SR requested scripts)? If this is causing delays
and issues related to lack of automation, then HCM Data Loader should be considered.
6. Are there users who load data using HCM Spreadsheet Data Loader? A move to HCM Data Loader in R10 would disable this
7.
Functionality, so it would probably be worth waiting for spreadsheet support. HCM Data Loader migration should be treated as an implemen-
tation with a proper project plan. File-Based Loader GUID values can continue to be used with HCM Data Loader. A process can be run to
convert the File-Based Loader GUID into a source key that HCM Data Loader can recognize.
8. HR spreadsheet loaders in the Data Exchange work area will not be available to use in conjunction with HCM Data Loader
9.
HCM Data Loader and File-Based Loader cannot be used at the same time for objects supported by both.
10.
Payroll batch loader is still required for some payroll object loads.
11. Environment refresh will overwrite HCM Data Loader settings if the source environment uses File-Based Loader. You will
have to follow the process again to enable HCM Data Loader and convert File-Based Loader GUIDs and source keys.
12. Once HCM Data Loader is enabled in a test environment, no additional File-Based Loader load testing will be possible
NEW IMPLEMENTATION CONSIDERATIONS
1)
Customers who have recently started implementing and have not yet gone live should consider switching to HCM Data Loader if their time-
lines can accommodate it.
-
7/24/2019 An Overview of Fusion Applications
39/243
2)
This will mitigate the need for conversion to HCM Data Loader later in the project lifecycle. Project plans should be reviewed to incorporate
the migration to HCM Data Loader, taking into account:
3) Training on the new tool
4) Rework of the extract mechanism to get data in the HCM Data Loader format
5) The need to test the migration and integration processes using HCM Data Loader instead of File Based Loader
6)
The need to fit in with major implementation milestones
CONSIDERATIONS FOR EXISTING CUSTOMERS
1. Existing live customers already using File-Based Loader and HCM Spreadsheet Data Loader should defer the switch to HCM Data Loader.
2. Customers who are not yet live should evaluate whether to rework their implementation to use HCM Data Loader or continue using File-Based Loader and HCM Spreadsheet Data Loader.
3. The main work involved in using File-Based Loader and HCM Data Loader is the extract of the data from a source system to the correct for-mat ready for loading. Since this is not part of Oracle Fusion, Oracle does not provide a conversion process from File-Based Loader to HCM
Data Loader.
4.
Oracle does provide the migration of File-Based Loader GUID values to the HCM Data Loader equivalent, which are referred to as sourcekeys.
5. Customers using Oracle Fusion Taleo Recruitment Out of the Box (OOTB) V1 Integration are not impacted.6.
If you are using Taleo Connect Client and File-Based Loader or a hybrid with OOTB to integrate with Fusion, you will need to perform an
evaluation and follow the steps to migrate to HCM Data Loader
HCMDATA LOADER COMPATIBILITY WITH FILE BASED LOADER
HCM Data Loader and File-Based Loader cannot be used at the same time for objects supported by both. Either of them should be picked for conver-
sion.The setting of the HCM Data Loader Scopeparameter on the Configure HCM Data Loader page determines whether HCM Data Loader or File-
Based Loader is used and controls the behavior of the loading tools. The default value of this parameter is Limitedfor existing customers. If youattempt to load data for a business object not supported in the Limited mode, your whole data set will fail.
Limited mode Only business objects not supported by HCM File-Based Loader can be loaded using HCM Data Loader. All objects that can
use File-Based Loader must use File-Based Loader. Any objects that are not available via File-Based Loader should use HCM Data Loader.
Full modeHCM Data Loader is used for bulk-loading data into all supported business objects. HCM File Based Loader and HCM Spread-sheet Data Loader are disabled.
Important Note:You can switch from Limited mode to Full mode, but you cannot switch from Full mode to Limited mode. This is a one-time
switchfrom File-Based Loader to HCM Data Loader.Once you migrate to HCM Data Loader, HCM Spreadsheet Data Loader is also disabled because it relies on the File-Based Loader engine to load
data to Oracle HCM Cloud. This restriction applies only to the spreadsheet loading that is launched from the Data Exchange work area. Other spread-sheet data loaders are not impacted by the uptake of HCM Data Loader.
-
7/24/2019 An Overview of Fusion Applications
40/243
IMPACT OF UPGRADE TO RELEASE 10
HCM Data Loader will be Generally Available in R10 (also in Release 9 Patch Bundle 7 and above ) but there is no immediate requirement tomigrate to HCM Data Loader.
HCM Data Loader and File-Based Loader cannot be used at the same time for objects supported by both.
On upgrade to Release 10 you will see the HCM Data Loader options available in the application but you should not use HCM Data Loader if youare an existing File-Based Loader customer until you have completed an evaluation of HCM Data Loader.
Important Note:
There are differences in file format and key structures.
Once the switch to HCM Data Loader has occurred, you will no longer have access to File-Based Loader or HCM Spreadsheet Data Loader.
If you have a requirement to load documents of record or areas of responsibility, then you can use HCM Data Loader in Limited mode with no im-
pact on File-Based Loader or HCM Spreadsheet Data Loader, since these objects are not currently supported by File-Based Loader
ENVIRONMENT MANAGEMENT CONSIDERATIONS
If you are live with File-Based Loader and testing HCM Data Loader in a nonproduction environment, then you should plan your environment re-
fresh (P2T) requests carefully.
When you request an environment refresh, the HCM Data Loader settings will be overwritten, and the environment will revert to the default Limited
mode.
You will need to go through the same steps as before to switch back to HCM Data Loader. That is, you must convert File-Based Loader GUIDs toHCM Data Loader source keys and switch HCM Data Loader Scope to Full.
During the HCM Data Loader migration validation and testing, important testing considerations must be included in your planning.HCM Data Loader in Full mode is not compatible with File-Based Loader; therefore, it i s not possible to have an environment with both HCM Data
Loader and File-Based Loader at the same time.
-
7/24/2019 An Overview of Fusion Applications
41/243
This will impact your ability to test File-Based Loader transactions in your nonproduction environment while you are in the process of validatingHCM Data Loader.
Important Note: You will need to ensure that the HCM Data Loader enabled environment is not required for any File-Based Loader testing prior tosetting the HCM Data Loader Scope to Full.
MIGRATION STEPS FOR MOVING FROM FILE BASED LOADER TO HCM DATA LOADER
It is not possible to move to HCM Data Loader for individual core objects on an incremental basis. It is a one-time migration and requires careful
planning and preparation to ensure a smooth transition.
CHOICE OF KEYS
One of the most important decisions when considering the upgrade from File-Based Loader to HCM Data Loader is whether to continue to use the
same key mechanism as is used in File-Based Loader (GUIDs) or whether to take advantage of the user key support that is available in HCM Data
Loader.
User keys allow objects to be identified in HCM Data Loader using their natural key; for example, Job Code, Person Number, and so on.
File-Based Loader GUIDs have an equivalent in HCM Data Loader known as source keys. These are values that are defined in the source system and
stored alongside the Oracle Fusion surrogate keys when objects are created in Oracle HCM Cloud. Source keys can be used to reference objects when
loading related data or to identify specific objects when performing updates or deletes.
Within HCM Data Loader, each object can use different types of keys, so a decision needs to be made on an object-by-object basis to determine
whether a user key or a source key will be used.
CONVERSION OF GUIDS
In order to facilitate the upgrade from File-Based Loader to HCM Data Loader, a process is provided to migrate the File-Based Loader GUIDs to
HCM Data Loader source system IDs. Regardless of whether user keys or source keys will be used, it is recommended that this process be run as the
first step
TEMPLATE GENERATION
Before reworking the export processes, you can download a template for each business object supported by HCM Data Loader. These templates take
into account any flex-field structures that are already in place. By using the templates, you can accurately outline the shape of the data that needs to
be generated by the reworked export processes.
REWORK OF EXPORT PROCESSES
-
7/24/2019 An Overview of Fusion Applications
42/243
-
7/24/2019 An Overview of Fusion Applications
43/243
OFFLINE VERIFICATION USING HDLDI
The offline Data File Validator Tool (HDLdi) and used in the extract process to ensure that the data files being prepared are valid in terms of the data
format. It also checks any business rules that apply to the data contained in the data file where other Oracle HCM Cloud data is not required as part ofthe validation.
HCMDATA LOADER PROCESS FLOW DIAGRAM
HDL(HCM DATA LOADER)VS FBL(FILE BASED LOADER)COMPARATIVE ANALYSIS (TOP 10POINTS)
HCMDATA LOADER (HDL) FILE BASED LOADER (FBL)
HAS NEW FEATURES CUSTOMERS ALREADY ACCUSTOMED TO USING FBL
SINGLE WORKER FILE MULTIPLE FILES TO LOAD WORKER DETAILS
ALLOWS BULK AND DELTA LOAD SPECIAL CONSIDERATIONS REQUIRED FOR DELTA LOAD
ERROR HANDLING MECHANISM IS EASY ERROR HANDLING TAKES LOT OF TIME AND EFFORT
-
7/24/2019 An Overview of Fusion Applications
44/243
ALLOWS DATE EFFECTIVE HISTORICAL DATA LOAD.NEED TO PASS ONLY
THE (N+1)TH RECORD
ALLOWS DATE EFFECTIVE HISTORY LOAD.IN CASE YOU NEED TO LOAD (N+1)TH RECORD
ALL RECORDS STARTING FROM 1TO NALSO NEEDS TO BE PASSED
ORACLE RECOMMENDS FOR ALL NEW IMPLEMENTATIONS ONLY RECOMMENDED FOR EXISTING CUSTOMERS
ENSURES EIT HER COMPLETE DETAILS GET LOADED ORNONE. NO PARTIAL
CONVERSION ALLOWED.ALLORNONE APPROACH
CUSTOMERS ALREADY ACCUSTOMED TO USING FBL.PARTIAL LOAD HAPPENS CAUSING
SYNC ISSUES.MAJOR SETBACK FOR ALL IMPLEMENTATIONS
USES SOURCE SYSTEM KEYS APPROACH.USER FRIENDLY PRIMARY KEYS FOLLOWS GUIDAPPROACH.PRIMARY KEYS ARE NOT USER FRIENDLY
HDL TEMPLATES (DATA FILE FORMAT)REQUIRED FOR CONVERSION CAN
BE DOWNLOADED FROM THE APPLICATION INSTANCE (COMMONLY RE-
FERRED TO AS POD)ITSELF.NO ADDITIONAL SR(SERVICE REQUESTS)
NEEDS TO BE RAISED
FBL TEMPLATES ARE MADE AVAILABLE ON REQUEST (VIA SR)
TODAY OR TOMORROW YOU HAVE TO ACCEPT USING HDL.YOU MAY DE-
LAY USING IT BUT CANNOT AVOIDIT.
FBL IS AGE OLD TECHNOLOGY NOW.YOU CAN USE IT FOR NOW BUT IT IS ON THE VERGE OF
EXTINCTION.
SAMPLE HDLFILES
Worker.dat
Worker.dat
-
7/24/2019 An Overview of Fusion Applications
45/243
How To Configure HCM Data Loader
This article explains in detail about the steps required to enable your system to use HCM Data Loader tool ( for HCM data Migration ) from Legacy
Applications to Fusion Applications.
It has been divided into various sections and the same are detailed below :
FUSION
APPLICATION LOGIN PAGE:
The below screenshot shows a Fusion Application Home page. Click on the Fusion Applications Link ( you will receive the same from your Project
Team Colleagues / IT Admin )
-
7/24/2019 An Overview of Fusion Applications
46/243
APPLICATION VERSION DETAILS
Verify the application version
Navigation-: Click on any link from the navigator (E.g.: Setup and Maintenance) -> A new page opens up. On the top right hand side of the page youwill find an arrow next to your login user name which populates below Settings and Actions list screenshots below :
-
7/24/2019 An Overview of Fusion Applications
47/243
Select About This Page. This will provide details of the Fusion application version (highlighted below)
-
7/24/2019 An Overview of Fusion Applications
48/243
USER ROLES:
Role required for using HCM Data Loader is Human Capital Management Integration SpecialistNavigation to check the User roles: Navigator-> My Account ->Current Roles
-
7/24/2019 An Overview of Fusion Applications
49/243
NAVIGATION:CONFIGURE HCMDATA LOADER
Login into Fusion applications-> Click on Navigator-> Setup and Maintenance -> All Tasks
In the search window, give name as Configure HCM Data Loader
-
7/24/2019 An Overview of Fusion Applications
50/243
-
7/24/2019 An Overview of Fusion Applications
51/243
-
7/24/2019 An Overview of Fusion Applications
52/243
-
7/24/2019 An Overview of Fusion Applications
53/243
-
7/24/2019 An Overview of Fusion Applications
54/243
-
7/24/2019 An Overview of Fusion Applications
55/243
WHERE flvt1.lookup_type ='ANC_ABS_PLAN_OTHER_REASONS'
AND flvt1.language = 'US') adj_reason
ON (apaed.adjustment_reason = adj_reason.lookup_code)LEFT OUTER JOIN( SELECT hauft.organization_id,
hauft.NAMEFROM HR_ORG_UNIT_CLASSIFICATIONS_F houcf,
HR_ALL_ORGANIZATION_UNITS_F haouf,HR_ORGANIZATION_UNITS_F_TL hauft
WHERE haouf.ORGANIZATION_ID = houcf.ORGANIZATION_IDAND haouf.ORGANIZATION_ID = hauft.ORGANIZATION_IDAND haouf.EFFECTIVE_START_DATE BETWEEN houcf.EFFECTIVE_START_DATE AND houcf.EFFECTIVE_END_DATEAND hauft.LANGUAGE = 'US'AND hauft.EFFECTIVE_START_DATE = haouf.EFFECTIVE_START_DATEAND hauft.EFFECTIVE_END_DATE = haouf.EFFECTIVE_END_DATEAND houcf.CLASSIFICATION_CODE = 'DEPARTMENT'AND TRUNC(SYSDATE) BETWEEN hauft.effective_start_date AND hauft.effective_end_date
) deptON (paam.organization_id = dept.organization_id)
LEFT OUTER JOIN(SELECT hauft.organization_id,
hauft.NAME,houcf.classification_code
FROM HR_ORG_UNIT_CLASSIFICATIONS_F houcf,HR_ALL_ORGANIZATION_UNITS_F haouf,HR_ORGANIZATION_UNITS_F_TL hauft
WHERE haouf.ORGANIZATION_ID = houcf.ORGANIZATION_IDAND haouf.ORGANIZATION_ID = hauft.ORGANIZATION_IDAND haouf.EFFECTIVE_START_DATE BETWEEN houcf.EFFECTIVE_START_DATE AND houcf.EFFECTIVE_END_DATEAND hauft.LANGUAGE = 'US'AND hauft.EFFECTIVE_START_DATE = haouf.EFFECTIVE_START_DATEAND hauft.EFFECTIVE_END_DATE = haouf.EFFECTIVE_END_DATEAND houcf.CLASSIFICATION_CODE = 'HCM_LEMP'AND TRUNC(SYSDATE) BETWEEN hauft.effective_start_date AND hauft.effective_end_date
) legal_employer
ON (paam.legal_entity_id = legal_employer.organization_id)LEFT OUTER JOIN(SELECT hauft.organization_id business_unit_id,
hauft.NAME,houcf.classification_code
FROM HR_ORG_UNIT_CLASSIFICATIONS_F houcf,HR_ALL_ORGANIZATION_UNITS_F haouf,HR_ORGANIZATION_UNITS_F_TL hauft
WHERE haouf.ORGANIZATION_ID = houcf.ORGANIZATION_IDAND haouf.ORGANIZATION_ID = hauft.ORGANIZATION_IDAND haouf.EFFECTIVE_START_DATE BETWEEN houcf.EFFECTIVE_START_DATE AND houcf.EFFECTIVE_END_DATEAND hauft.LANGUAGE = 'US'AND hauft.EFFECTIVE_START_DATE = haouf.EFFECTIVE_START_DATEAND hauft.EFFECTIVE_END_DATE = haouf.EFFECTIVE_END_DATEAND houcf.CLASSIFICATION_CODE = 'FUN_BUSINESS_UNIT'AND TRUNC(SYSDATE) BETWEEN hauft.effective_start_date AND hauft.effective_end_date
) business unit
-
7/24/2019 An Overview of Fusion Applications
56/243
-
7/24/2019 An Overview of Fusion Applications
57/243
Under Published Reporting -> Data Model
Create a New Data Set (of SQL Query type) as shown in Screenshot below:
Give a Name to Data Set (for this example say PersonAbsenceAccrualEntryDetails_ds):
-
7/24/2019 An Overview of Fusion Applications
58/243
You would need to take special care while selecting Data Source (Logic Below):
a) If you are Building Finance reports use : ApplicationDB_FSCM
b) If you are Building HCM reports use : ApplicationDB_HCM
c) If you are Building CRM Reports use : ApplicationDB_CRM
For this example we use ApplicationDB_HCM
Depending on the number of Parameters( Bind Variables) used a Popup window will appear as :
-
7/24/2019 An Overview of Fusion Applications
59/243
-
7/24/2019 An Overview of Fusion Applications
60/243
-
7/24/2019 An Overview of Fusion Applications
61/243
pPersonNumber String Text PersonNumber**
Create List of Values for Parameters.
LIST OFVALUES
LOV NAME TYPE DATA SOURCE SQLQUERY ASSOCIATED WITH PARAM-ETER
Legal Employer SQL Query ApplicationDB_HCM Refer Legal EmployerLOV SQL in LOV SQL
Section
pLegalEmployer
Business Unit SQL Query ApplicationDB_HCM Refer Business UnitLOV SQL in LOV SQL
Section
pBusinessUnit
-
7/24/2019 An Overview of Fusion Applications
62/243
-
7/24/2019 An Overview of Fusion Applications
63/243
-
7/24/2019 An Overview of Fusion Applications
64/243
CREATE REPORT
Click on Create Report
-
7/24/2019 An Overview of Fusion Applications
65/243
Click Next and Follow Train Stops :
-
7/24/2019 An Overview of Fusion Applications
66/243
-
7/24/2019 An Overview of Fusion Applications
67/243
Drag and Drop fields and the Final Report output will look like :
Creating Custom BIP Reports from Static Data
BUSINESSREQUIREMENT
While we all have been accustomed and bored with always creating Data Model using SQL Query we might have missed other options as in this
screen-shot:
-
7/24/2019 An Overview of Fusion Applications
68/243
STEPS
Sample Data is Saved in Local Desktop and uploaded. Once the same is done the screen will appear as
-
7/24/2019 An Overview of Fusion Applications
69/243
-
7/24/2019 An Overview of Fusion Applications
70/243
MIGRATION
This Report may be migrated into your specific environment. You would need the below three things :
a) SampleCSVData
SampleCSVData.csv
b)
StaticDataBIP ( Data Model)
c) StaticDataBIPReport
-
7/24/2019 An Overview of Fusion Applications
71/243
Chapter 3: OTBI Reports
Gives Brief Description of OTBI Reports
Describes how to create a OTBI Report from Static Data
Also explains creating OTBI Reports from SQL
-
7/24/2019 An Overview of Fusion Applications
72/243
Creating OTBI Reports from Direct Database Query
BUSINESS REQUIREMENT
While we must have been used to creating DRAG and DROP reports using OTBI we might have missed the option of
Create Direct Database Query . In this article lets try to explore the same.
CONTENT
Navigation:
Login to Fusion Applications -> Click on Reports and Analytics -> Click on BI Catalog ( Book Icon) and you reach on this page
Click on Create Direct Database Query
Step 2 :
Provide following details :
CONNECTION POOL: HCM_OLTP.Connection Pool
SQL:
-
7/24/2019 An Overview of Fusion Applications
73/243
-
7/24/2019 An Overview of Fusion Applications
74/243
-
7/24/2019 An Overview of Fusion Applications
75/243
MIGRATING THIS ANALYSIS
Click on Archive option as shown.
-
7/24/2019 An Overview of Fusion Applications
76/243
-
7/24/2019 An Overview of Fusion Applications
77/243
-
7/24/2019 An Overview of Fusion Applications
78/243
-
7/24/2019 An Overview of Fusion Applications
79/243
Unarchive
A Popup window appears as shown below
-
7/24/2019 An Overview of Fusion Applications
80/243
-
7/24/2019 An Overview of Fusion Applications
81/243
-
7/24/2019 An Overview of Fusion Applications
82/243
3) Now select any attributes from the Subject Area of Date Type for this example lets choose Start Date from Person Folder (Workforce ManagementPerson Real
Time). Choose Variable Data Type as Date
4) Click Ok.
5) Edit the Prompt Again and now Calendar appears as a User Input in Drop down list
6) Save the changes.
7) The Date Picker appears as desired.
-
7/24/2019 An Overview of Fusion Applications
83/243
-
7/24/2019 An Overview of Fusion Applications
84/243
Creating Custom ESS Job in Fusion Applications
BUSINESSREQUIREMENT
Oracle has already delivered a lot of BIP Reports in the Fusion Instance, however during a course of implementation it is a common requirement to
develop new ones.
CONTENT
There are few common steps involved they are :
b) Create a SQL Query which comprises of DB Tables ( that exist in Fusion Schema).
We have a SQL Query which is as below :
SELECT hdbo.bus_obj_file_discriminator EntityName,fr.key_source_owner SourceSystemOwner, fr.key_source_id SourceSystemId, l.msg_text Er-
rorMessage,bo.data_file_name,bo.imported_status,bo.validated_status,bo.skipped_status,bo.loaded_status,'Error' DataLoadStatus,'N' DataLoadFlag FROM fu-
sion.hrc_dl_message_lines l , fusion.hrc_dl_data_set_bus_objs bo , fusion.hrc_dl_data_sets ds , fusion.hrc_dl_physical_lines pl , fusion.hrc_dl_file_rows fr , fu-
sion.hrc_dl_file_lines fl , fusion.hrc_dl_business_objects hdbo WHERE l.message_source_table_name = 'HRC_DL_PHYSICAL_LINES' AND bo.data_set_bus_obj_id =
l.data_set_bus_obj_id AND ds.data_set_id = bo.data_set_id AND pl.physical_line_id = l.message_source_line_id AND fr.row_id = pl.row_id AND fl.line_id = fr.line_idAND hdbo.business_object_id = bo.business_object_id And ds.ucm_content_id = :p_ucm_content_id union SELECT hdbo.bus_obj_file_discriminator Enti-
tyName,fr.key_source_owner SourceSystemOwner, fr.key_source_id SourceSystemId, l.msg_text ErrorMessage,bo.data_file_name,bo.imported_status,bo.validated_sta-
tus,bo.skipped_status,bo.loaded_status,'Error' dataloadstatus,'N' dataloadflag FROM fusion.hrc_dl_message_lines l , fusion.hrc_dl_data_set_bus_objs bo , fu-
sion.hrc_dl_data_sets ds , fusion.hrc_dl_logical_lines ll , fusion.hrc_dl_file_rows fr , fusion.hrc_dl_file_lines fl , fusion.hrc_dl_business_objects hdbo WHERE l .mes-
sage_source_table_name = 'HRC_DL_LOGICAL_LINES' AND bo.data_set_bus_obj_id = l.data_set_bus_obj_id AND ds.data_set_id = bo.data_set_id AND ll.logi-
cal_line_id = l.message_source_line_id AND fr.logical_line_id = ll.logical_line_id AND fl.line_id = fr.line_id AND hdbo.business_object_id = bo.business_object_id
And ds.ucm_content_id = :p_ucm_content_id
SCREEN-SHOT :
-
7/24/2019 An Overview of Fusion Applications
85/243
CREATE AREPORT:
-
7/24/2019 An Overview of Fusion Applications
86/243
-
7/24/2019 An Overview of Fusion Applications
87/243
Give a Name to Data Set (for this example say PersonAbsenceAccrualEntryDetails_ds):
-
7/24/2019 An Overview of Fusion Applications
88/243
You would need to take special care while selecting Data Source (Logic Below):
d) If you are Building Finance reports use : ApplicationDB_FSCM
e) If you are Building HCM reports use : ApplicationDB_HCM
f) If you are Building CRM Reports use : ApplicationDB_CRM
For this example we use ApplicationDB_HCM
Depending on the number of Parameters( Bind Variables) used a Popup window will appear as :
-
7/24/2019 An Overview of Fusion Applications
89/243
Click OK. Give a Name to the Parameters as shown below
-
7/24/2019 An Overview of Fusion Applications
90/243
PARAMETER DETAILS:
PARAMETER NAME DATA TYPE DEFAULT VALUE PARAMETER TYPE ROW PLACEMENT DISPLAY LABEL
pLegalEmployer String Menu ( List of Val-ues Legal Employer)
LegalEmployer**
pBusinessUnit String Menu ( List of Val-ues Business Unit)
BusinessUnit**
pDepartment String Menu ( List of Val-
ues Department)
Department**
pAbsencePlanName String Menu ( List of Val-ues Absence Plan
Name)
AbsencePlan-Name**
pCalculationDate Date Text CalculationDate**
pPersonName String Menu ( List of Val-
ues Person Name)
PersonName**
pPersonNumber String Text PersonNumber**
-
7/24/2019 An Overview of Fusion Applications
91/243
Data Model is created. Now we need to check the data retrieved.
. Create List of Values for Parameters.
LIST OFVALUES
LOV NAME TYPE DATA SOURCE SQLQUERY ASSOCIATED WITH PARAM-ETER
Legal Employer SQL Query ApplicationDB_HCM Refer Legal EmployerLOV SQL in LOV SQL
Section
pLegalEmployer
-
7/24/2019 An Overview of Fusion Applications
92/243
Business Unit SQL Query ApplicationDB_HCM Refer Business UnitLOV SQL in LOV SQL
Section
pBusinessUnit
Department SQL Query ApplicationDB_HCM Refer Department LOV
SQL in LOV SQL Sec-tion
pDepartment
Absence Plan Name SQL Query pLegalEmployer Refer Absence PlanName LOV SQL inLOV SQL Section
pAbsencePlanName
Person Name SQL Query pLegalEmployer Refer Person Name LOV
SQL in LOV SQL Sec-tion
pPersonName
LOVSQLSECTION
This Section shows all the SQL which are used for LOV Creation.
LEGAL EMPLOYER LOVSQL
BUSINESS UNIT LOVSQL
DEPARTMENT LOVSQL
ABSENCE PLAN LOVSQL
-
7/24/2019 An Overview of Fusion Applications
93/243
PERSON NAME LOVSQL
VIEW DATA :
CLICK ON SAVE AS SAMPLE DATA:
-
7/24/2019 An Overview of Fusion Applications
94/243
-
7/24/2019 An Overview of Fusion Applications
95/243
Click Next and Follow Train Stops :
-
7/24/2019 An Overview of Fusion Applications
96/243
Create Table
-
7/24/2019 An Overview of Fusion Applications
97/243
Drag and Drop fields and the Final Report output will look like :
-
7/24/2019 An Overview of Fusion Applications
98/243
Chapter 5: Fusion Absence Management
Defines What is Meant by Absence Plan
Explains the same with a Worked Out Example
An Overview of Fusion Absence Management Absence Plan Definition and Use
-
7/24/2019 An Overview of Fusion Applications
99/243
INTRODUCTION
Before we start to understand How to create an Absence Plan first try to understand what an Absence Plan is and why is it required.
In real life Absence Plan holds a different meaning than that of the one meant in Fusion Applications.
In real life Absence Plan for an individual (or for that matter for a Working individual) relates more to a question which is generally asked by his Manager
What are your Absence Plans?
and he would generally respond stating I will be on leave on so and so dates.
But in context with Fusion Applications an Absence Plan (I feel the naming convention isnt correct it should have beencalled Accrual Plan but that again is incorrect as
Absence Plans are even those which are of qualification and No-Entitlement Type, details about the same in Absence Plan Types Section) could be imagined as a Bucket.
Yes, I mean a Bucket as we know.
Lets for time being say an Absence Plan is an Absence Bucket and I call it as a Bucket as it is supposed to hold:
a) Leave / Absence Balance
Anything and everything around the Entire Absence Plan surrounds around this single piece of information usually called Absence Balance
Different Items related with an Absence Plan and their association with Absence Balance follows:
Absence Plan
A name given to a set of rules / guidelines which define how the absence balance will be assigned and maintained
Legislation
Geography / Country where this Absence Balance is Maintained. For Example, if we are doing Absence Plan setup for India Legislation would be India, if we are doing
for USA it would be United States and so on....Plan Type
An attribute which defines how the Absence Balance would be calculated / paid.
For example:
If Absence / Leave Balance is paid to employees as a result of an event such as childbirth, illness or injury it is called Qualification Plan Type Absence Plan
Typical Example Being Hospitalization Leave.
If Absence / Leave Balance is paid to employees as a result of accumulation / accrual it is called Accrual Plan Type Absence Plan
Leaves like Annual Leave, Vacation Leave fall into this category
-
7/24/2019 An Overview of Fusion Applications
100/243
-
7/24/2019 An Overview of Fusion Applications
101/243
b) Incremental
The Absence Balance are accrued at regular intervals
Accrual Frequency
Frequency at which accrual happens. It is of two types Person Primary Frequency and Repeating Period.
If person gets his absence / leave balance at the start of payroll period, then the Accrual Frequency is of Person Primary FrequencyType
For Example:
Person Primary Frequency: Weekly
Means he gets paid every week (Employee has a Weekly Payroll Assigned / Attached to him) and same is true for his absence balance too i.e. absence balance is
received every week (in synchronization with his person primary payroll payment frequency).
Person Primary Frequency: Bi-Weekly
Means he gets paid once in row weeks (Employee has a Bi-Weekly Payroll Assigned / Attached to him) and same is true for his absence balance too i.e. absence
balance is received once in two weeks (in synchronization with his person primary payroll payment frequency).Person Primary Frequency: Monthly
Means he gets paid once a month (Employee has monthly payroll assigned / attached to him) and same is true for his absence balance too i.e. absence balance is
received once a month (in synchronization with his person primary payroll payment frequency).
Person Primary Frequency: Quarterly
Means he gets paid once in quarter (Employee has a Quarterly Payroll Assigned / Attached to him) and same is true for his absence balance too i.e. absence bal-
ance
is received once each quarter (in synchronization with his person primary payroll payment frequency).
If person gets his absence / leave balance at the start of each instance of a Specific Repeating Time Period, then Accrual Frequency is of Repeating Time Period
For Example:
Repeating Time Period: Every Quarter of a Calendar year
Means he will accrue this leave once every 3 months in the Calendar Year.
Repeating Time Period: Bi Monthly
Means he will accrue this leave 2 times in a month.
Repeating Time Period: Every Quarter of a Calendar year
Means he will accrue this leave once every 3 months in the Calendar Year.
Repeating Time Period: Monthly
-
7/24/2019 An Overview of Fusion Applications
102/243
-
7/24/2019 An Overview of Fusion Applications
103/243
-
7/24/2019 An Overview of Fusion Applications
104/243
-
7/24/2019 An Overview of Fusion Applications
105/243
-
7/24/2019 An Overview of Fusion Applications
106/243
-
7/24/2019 An Overview of Fusion Applications
107/243
5 AH Global
Absence
Plan Use
Rate For-
mula2
Global Ab-
sence Plan
Use Rate
For Custom Logic to fetch the rate code required to pay employee in case of leave disbursement / encashment
Sample Example Below.
Employee Type = Hourly Employee Type = Salaried
Rate Code = Hourly Rate Rate Code = Annual Salary Rate
-
7/24/2019 An Overview of Fusion Applications
108/243
AHGLOBAL ABSENCE PLAN DURATION FORMULA
AH Global Absence Plan Duration Formula
Formula Name AH Global Absence Plan Duration Formula
Formula Type Global Absence Plan Duration
Description If leave falls on a Sunday then the leave hours deducted from leave balance should be
0 for all other cases it should be 8.5 hours
FORMULA TEXT
/************************************************************************************
FORMULA NAME: AH Global Absence Plan Duration Formula
FORMULA TYPE: Global Absence Plan Duration
DESCRIPTION: This sample formula returns the duration based on effective date falls on Sunday.
Change History:
-
7/24/2019 An Overview of Fusion Applications
109/243
-
7/24/2019 An Overview of Fusion Applications
110/243
-
7/24/2019 An Overview of Fusion Applications
111/243
AH GLOBAL ABSENCE ACCRUAL FORMULA
AH Global Absence Accrual Formula
Formula Name AH Global Absence Accrual Formula
Formula Type Global Absence Accrual
Description This sample formula applies the Accrual, Ceiling, Carryover, Proration Factor, Vest-
ing Units, Vesting UOM, Carryover Proration and Ceiling Proration based on Length
of Service and Accrual Plan the person enrolled into
FORMULA TEXT
/*****************************************************************
FORMULA NAME: AH Global Absence Accrual Formula
FORMULA TYPE: Global Absence Accrual
DESCRIPTION: This sample formula applies the Accrual, Ceiling, CarryOver, Proration Factor, Vesting Units, Vesting UOM, CarryOver Proration and Ceiling Proration
based on Length of Service and Accrual Plan the person enrolled into.
Change History:
Name Date Comments
------------------------------------------------------------------------------------------------------------
XXXXXXX DD-MM-YYYY XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
------------------------------------------------------------------------------------------------------------
*****************************************************************/
/*=========== DATABASE ITEM DEFAULTS BEGIN =====================*/
DEFAULT for PER_ASG_REL_ORIGINAL_DATE_OF_HIRE is '4712/12/31 00:00:00' (date)
DEFAULT for ANC_ABS_PLN_NAME is 'A'
-
7/24/2019 An Overview of Fusion Applications
112/243
-
7/24/2019 An Overview of Fusion Applications
113/243
-
7/24/2019 An Overview of Fusion Applications
114/243
carryOverProration=0.25
ceilingProration=0.25
)
else if ((l_length_of_service =>3) and (l_length_of_service5)
then (
accrual =round(15/24,3)
ceiling =round(150/24,3)
carryover=round(75/24,3)
prorationFactor=0.25
vestingUnits=30
vestingUOM='C'
carryOverProration=0.25
ceilingProration=0.25
)
)
else if (ANC_ABS_PLN_PLAN_UOM ='W')
-
7/24/2019 An Overview of Fusion Applications
115/243
then(
if (l_length_of_service 3) and (l_length_of_service5)
then (
accrual =round(15/120,3)
ceiling =round(150/120,3)
-
7/24/2019 An Overview of Fusion Applications
116/243
carryover=round(75/120,3)
prorationFactor=0.25
vestingUnits=30
vestingUOM='C'
carryOverProration=0.25
ceilingProration=0.25
)))
if (ANC_ABS_PLN_NAME='Sickness')
then(
if(ANC_ABS_PLN_PLAN_UOM ='H')
then(
if(l_length_of_service3) and (l_length_of_service
-
7/24/2019 An Overview of Fusion Applications
117/243
prorationFactor=0.25
vestingUnits=30
vestingUOM='C'
carryOverProration=0.25
ceilingProration=0.25
)
else if (l_length_of_service =>5)
then (
accrual =14
ceiling = 160
carryover=80
prorationFactor=0.25
vestingUnits=30
vestingUOM='C'
carryOverProration=0.25
ceilingProration=0.25 ))
else if (ANC_ABS_PLN_PLAN_UOM ='D')
then(
if (l_length_of_service
-
7/24/2019 An Overview of Fusion Applications
118/243
-
7/24/2019 An Overview of Fusion Applications
119/243
if (l_length_of_service 3) and (l_length_of_service5)
then (
accrual =round(14/120,3)
ceiling =round(160/120,3)
carryover=round(80/120,3)
-
7/24/2019 An Overview of Fusion Applications
120/243
-
7/24/2019 An Overview of Fusion Applications
121/243
-
7/24/2019 An Overview of Fusion Applications
122/243
FORMULA NAME: AH Global Absence Vesting Period Formula
FORMULA TYPE: Global Absence Vesting Period
DESCRIPTION: This sample formula applies the vesting period based on employment category.
If the Employee belongs to a specific Legal Employer (Vision Corporation for this example)
then his Vesting Period (Number of Days after which he is allowed to use his accrued leaves) is 90 Calendar Days for any other Legal Employer it is 30 Days
Change History:
Name Date Comments
-----------------------------------------------------------------------------------------------------------------
XXXXXXX DD-MM-YYYY XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
----------------------------------------------------------------------------------------------------------------
********************************************************************/
/*==============DATABASE ITEM DEFAULTS BEGIN =====================*/
DEFAULT for PER_ASG_ORG_LEGAL_EMPLOYER_NAME is 'Vision'
/*==============DATABASE ITEM DEFAULTS ENDS======================*/
/*================== FORMULA SECTION BEGIN =======================*/
If (PER_ASG_ORG_LEGAL_EMPLOYER_NAME='Vision Corporation')
then (
vestingUOM = 'C'
vestingUnits=90
)
else(
vestingUOM = 'C'
vestingUnits=30)
/*=================== FORMULA SECTION END =======================*/
return vestingUOM,vestingUnits
SCREENSHOT
-
7/24/2019 An Overview of Fusion Applications
123/243
AHGLOBAL ABSENCE PLAN USE RATE SELECTION FORMULA 1
-
7/24/2019 An Overview of Fusion Applications
124/243
AH Global Absence Plan Use Rate Selection Formula 1
Formula Name AH Global Absence Plan Use Rate Selection Formula 1
Formula Type Global Absence Plan Use Rate
Description This sample formula returns the rate code. We have defined two different rate codes
namely Sickness Rate and Hourly Rate. If an individual chooses either an Absence
Type of Sick or Flu the RateCode is Sickness Rate else its Hourly Rate
FORMULA TEXT
/***********************************************************************
FORMULA NAME: AH Global Absence Plan Use Rate Selection Formula 1
FORMULA TYPE: Global Absence Plan Use Rate
DESCRIPTION: This sample formula returns the rate code.
We have defined two different rate codes namely Sickness Rate and Hourly Rate.
If an individual chooses either an Absence Type of Sick or Flu the RateCode is Sickness Rate else its Hourly Rate.
Change History:
Name Date Comments
---------------------------------------------------------------------------------------------------------------------
XXXXXXX DD-MM-YYYY XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
--------------------------------------------------------------------------------------------------------------------
***********************************************************************/
/*=========== DATABASE ITEM DEFAULTS BEGINS======================*/
DEFAULT for ANC_ABS_TYP_NAME is 'Sick'
DEFAULT for ANC_ABS_RSN_NAME is 'Cough'
/*=========== DATABASE ITEM DEFAULTS ENDS======================*/
/*================ FORMULA SECTION BEGIN =======================*/
-
7/24/2019 An Overview of Fusion Applications
125/243
-
7/24/2019 An Overview of Fusion Applications
126/243
AHGLOBAL ABSENCE PLAN USE RATE FORMULA 2
AH Global Absence Plan Use Rate Formula2
Formula Name AH Global Absence Plan Use Rate Formula2
Formula Type Global Absence Plan Use Rate
Decription This sample formula returns the Plan Use Rate. If an Individual is Paid on Hourly Ba-
sis his RateCode will be Hourly else it would be Annual Salary
FORMULA TEXT
/***********************************************************************
FORMULA NAME: AH Global Absence Plan Use Rate Formula2
FORMULA TYPE: Global Absence Plan Use Rate
DESCRIPTION: This sample formula returns the Plan Use Rate. If an Individual is Paid on Hourly Basis his RateCode will be Hourly else, it would be Annual Salary
Change History:
Name Date Comments
--------------------------------------------------------------------------------------------
XXXXXXX DD-MM-YYYY XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
-
7/24/2019 An Overview of Fusion Applications
127/243
--------------------------------------------------------------------------------------------
***********************************************************************/
/*=========== DATABASE ITEM DEFAULTS BEGIN =====================*/
DEFAULT for PER_ASG_HOURLY_SALARIED_CODE is 'H'
/*=========== DATABASE ITEM DEFAULTS ENDS======================*/
/*=========== FORMULA SECTION BEGIN======================*/
if (PER_ASG_HOURLY_SALARIED_CODE='H')
then (
rateCode='Hourly Rate'
)
else (
rateCode='Annual Salary Rate')
/*=========== FORMULA SECTION END======================*/
RETURN rateCode
SCREENSHOTS
-
7/24/2019 An Overview of Fusion Applications
128/243
SETUP STEPS
-
7/24/2019 An Overview of Fusion Applications
129/243
-
7/24/2019 An Overview of Fusion Applications
130/243
Navigation is as shown below:
Login to Fusion Applications -> Click on Navigator -> Click on Setup and Mai ntain enance-> In All Tasks Search for Manage%Absence%Plan
-
7/24/2019 An Overview of Fusion Applications
131/243
-
7/24/2019 An Overview of Fusion Applications
132/243
-
7/24/2019 An Overview of Fusion Applications
133/243
-
7/24/2019 An Overview of Fusion Applications
134/243
-
7/24/2019 An Overview of Fusion Applications
135/243
Populate Participation Tab:
This Tab Consists of 2 parts which are:
a) Enrollment Rules
b) Termination Rules
Populate the following details in Enrollment Rules Section as shown below:
Enrollment Rules
LABEL VALUE
Enrollment Start Rule As of Event
Waiting Period UOM Calendar Days
Duration 30
Populate the following details in Termination Rules Section as shown below:
Termination Rules
LABEL VALUE
Enrollment End Rule As of Event
On Employment Termination
LABEL VALUE
Positive Accrual Balances Checked
Negative Accrual Balance Checked
-
7/24/2019 An Overview of Fusion Applications
136/243
On Loss of Plan Eligibility
LABEL VALUE
Disburse Positive Balance Checked
Recover Negative Balance Checked
Use the above details and populate the Participation Tab and the screenshot would look like:
-
7/24/2019 An Overview of Fusion Applications
137/243
-
7/24/2019 An Overview of Fusion Applications
138/243
Populate Accruals Tab which consists of Accrual Attributes Section only.
Populate the following details in Accrual Attributes Section as shown below:
Accrual Attributes
LABEL VALUE
Accrual Definition Formula
Accrual Formula AH Global Absence Accrual Formula
Payment Percentage 100%
Accrual Method Incremental
Partial Accrual Period Formula
Accrual Vesting Rule Formula
Vesting Period Formula AH Global Absence Vesting Period Formula
Accrual Frequency Source Person Primary Frequency
-
7/24/2019 An Overview of Fusion Applications
139/243
-
7/24/2019 An Overview of Fusion Applications
140/243
Populate Entries and Balances Tab.This Tab Consists of 3 Sections which are:
a) Balance Updates
b) Rates
c) Payroll Integration
Populate the following details in Balance Updates Section as shown below:
Balance Updates
LABEL VALUE
Discretionary Disbursements of Accrual Balance Checked
Accrual Balance Transfers Across Plans Checked
Other Adjustments Checked
Other Adjustment Reasons Clerical Error , Compensatory
Populate the following details in Rates Section as shown below:
Rates
LABEL VALUE
Absence Payment Rate Rule Formula
-
7/24/2019 An Overview of Fusion Applications
141/243
-
7/24/2019 An Overview of Fusion Applications
142/243
If this check boxis not selected (Elementfield will not show a field value of Annual Leaverather it will be empty)
Once all the above setup is done Absence Plan Creation is complete.
-
7/24/2019 An Overview of Fusion Applications
143/243
An Overview of Fusion Absence Management Part 2 Absence Type Definition and Use
INTRODUCTION
This article is the second part of the series An Overview of Fusion Absence Management. The first part titled: An overview of Fusion Absence Management Part 1 Absence Plan Definition and Use can be found at Accenture KX Site too.
Before we start to understand How to create an Absence Type first try to understand what a Absence Type is and why is it required.
An absence type as the name suggests refers to different types of absences like Sick Leave, Annual Leave, Vacation Leave, Marriage Leave, Compassionate Leave, Mater-nity leave, Paternity Leave and you can keep on expanding so on and so forth.
Basically in a nutshell, all the various reasons / events / activities for which a Leave Application may be raised can be treated as Absence Type (context being Fusion
Absence Management).
So before we jump into a typical business requirement and dig deep into how to fulfill the same let-us try to familiarize ourselves with some of the most commonly used
terms which would be referred in the ongoing article:
Absence PatternThis could be defined as the broad level categorization of different leave types like General Leave, Illness, Injury special leave types.In context of Fusion Absence Management there are 3 different types of Patterns (available as of today) namely :
a) Childbirth or Placement: Refers to specific leave type Childbirth (Maternity) and Placement ( Specific Assignment)
b) Generic Absence : Covers the largest scope in terms of leave types. Includes Annual Leave, Vacation Leave, Compensatory Off, Marriage Leave, OptionalLeave, Compassionate Leave etc.
c) Illness or Injury : As the name suggests leave patterns which depends on an individuals physical condition. This patterns includes Sick Leave,Hospitalization leave to name a few.
-
7/24/2019 An Overview of Fusion Applications
144/243
LegislationGeography / Country where this Absence Type is Maintained. For Example if we are doing Absence Type setup for India Legislation would be India , if we are doing forUSA it would be United States and so on....
Absence Type UOM
Unit of Measure which states in which unit (either of Days / Calendar Days / Hours) will this Absence Type will get measured
BUSINESS REQUIREMENT
Now since we are aware of some of the most commonly used terms for an absence types we should try to create one absence type .Requirement is to create an Absence
Type of Pattern Generic Absence.
PERQUISITES:
You need to have an already created Absence Plan available to attach to the absence Type (we did same in Absence Article 1 so we are good) . Also we would assumethat we have an absence reason already created in the application to use.
SETUP STEPS
In this example to keep things simpler we would only discuss about the Mandatory Details required to create an Absence type (fields which are mandatory are generally
highlighted with an asterisk mark beside them), A complete detail of all fields could be covered in next article.
Navigation is as shown below:Login to Fusion Applications -> Click on Navigator -> Click on Setup and Mai ntenance-> In All T asks Search for Manage%Absence%Types
-
7/24/2019 An Overview of Fusion Applications
145/243
Click on Go to Task ButtonClick on Create Button and populate the following details:
LABEL VALUEEffective as of Date 9/18/14Legislation IndiaPattern Generic Absence
You may populate the following screen with above details
-
7/24/2019 An Overview of Fusion Applications
146/243
Each absence plan setup requires four Tabs to be filled namely (screen-shot reference).
a) TYPE ATTRIBUTES
Contains Details about Type Name, Description, UOM, Legislative Data Group, Status, Duration Rules , Absence Record Maintenance, fast formulas ConversionFormula , Validation Formula along with Eligibility Profile associated with a particular absence type
-
7/24/2019 An Overview of Fusion Applications
147/243
Populate the following values (displayed in tabular format below)
General Attributes
LABEL VALUEName XX AH Annual Absence Type INDescription XX AH Annual Absence Type INUOM Calendar Days
Legislative Data Group India
Status Active
Duration Rules
LABEL VALUEMinimum Duration Rule NoneMaximum Duration Rule NonePartial Day Rule Unlimited
-
7/24/2019 An Overview of Fusion Applications
148/243
b) PLANS AND REASONS
Plans and Reasons ( Absence Plans)
-
7/24/2019 An Overview of Fusion Applications
149/243
LABEL VALUEPlan XX AH Annual Absence Plan INStatus ActivePriority 10
Contains Details about Effective Start Date, Plan, Status Priority as shown in below screenshot :
Also select an Absence Reason as shown:
-
7/24/2019 An Overview of Fusion Applications
150/243
-
7/24/2019 An Overview of Fusion Applications
151/243
The page after filling details should look like:
-
7/24/2019 An Overview of Fusion Applications
152/243
c) DISPLAY FEATURES
This page comes with default values populated and for the sake of simplicity let-us keep them as is the page appears as shown below
d) ACTION ITEMS
-
7/24/2019 An Overview of Fusion Applications
153/243
Used to configure any specific actions to be triggered / executed / performed whenever this leave type is applied. Not applicable for current example hence ig-nored for now. We keep this page as blank as shown below;
Click on Save and Close Button
-
7/24/2019 An Overview of Fusion Applications
154/243
Once all the above setup is done Absence Type Creation is complete.
Chapter 6 - Fusion Fast Formulas
-
7/24/2019 An Overview of Fusion Applications
155/243
-
7/24/2019 An Overview of Fusion Applications
156/243
How-To Create a Global Absence Entry Validation Fast Formula in Fusion Applications
Customer has a requirement where-in they allow only individuals
a) Leave Duration should be wither Half / Full day.
b) This leave is only allowed up-to 3 childrens
c) You can only avail this leave if you have dependent/ adopted children
d) Leave needs to be applied within 1 year of childbirth
Details of the Custom **Error Message and their description below ( In tabular Format)
**All the above Error Messages are defined in 'Manage Messages' under Setup and Maintaineance
/******************************************************************************
FORMULA NAME: A2F_ANC_VALID_Paternity
FORMULA TYPE: Global Absence Entry ValidationDESCRIPTION: This formula returns the Paternity Leave Criteria. Only workers who have less than 3 dependent children are elig ible
Change History:
Name Date Comments
-----------------------------------------------
Ashley Hardy 07-Apr-2015 Initial Version
*******************************************************************************/
DEFAULT_DATA_VALUE FOR P ER_PER_CONTACT_PERSON_ID IS 0
DEFAULT_DATA_VALUE FOR P ER_PER_CONTACT_CONTACT_TYPE IS ' '
DEFAULT_DATA_VALUE FOR P ER_PER_CONTACT_DATE_OF_BIRTH IS '4712/12/31 00:00:00' (date)
DEFAULT_DATA_VALUE for ANC_PER_ABS_ENTRS_ABSENCE_ENTRY_ID_ARR is 0
DEFAULT FOR ANC ABS ENTRS ABSENCE TYPE ID i 0
-
7/24/2019 An Overview of Fusion Applications
157/243
DEFAULT FOR ANC_ABS_ENTRS_ABSENCE_TYPE_ID is 0
/*=========== DATABASE ITEM DEFAULTS END =====================*/
/*================ FORMULA SECTION BEGIN =======================*/
/*==============INPUTS SECTION BEGIN================*/
INPUTS ARE iv_start_date (date),
iv_end_date (date),
IV_TOTALDURATION
/*==============INPUTS SECTION BEGIN================*/
ln_pl_type_id = GET_CONTEXT(ABSENCE_TYPE_ID,0) /* pl stands for Paternity Leave */
ld_child_birth_date = TO_DATE('1951-01-01','yyyy-MM-dd')
ld_start_date = TO_DATE('1951-01-01','yyyy-MM-dd')
j = 1
l_new_duration = IV_TOTALDURATION
ln_child_count = 0
ln_rem = MOD(IV_TOTALDURATION,0.5)
IF (ln_rem 0)
THEN
(
VALID = 'N'
ERROR_MESSAGE = 'A2F_ANC_SG_ERR_DURCAL' /* 'Leave Duration should either be Half/Full Day.Please change absence start and end dates accordingly' */RETURN VALID,ERROR_MESSAGE
)
CHANGE_CONTEXTS(START_DATE=iv_start_date, END_DATE=iv_end_date)
(
i=PER_PER_CONTACT_PERSON_ID.FIRST(-1)
WHILE PER_PER_CONTACT_PERSON_ID.exists(i)
LOOP
(
if(PER_PER_CONTACT_CONTACT_TYPE[i] = 'C' or PER_PER_CONTACT_CONTACT_TYPE[i] = 'A')
then
(
ln_child_count = ln_child_count + 1
ld_child_birth_date = PER_PER_CONTACT_DATE_OF_BIRTH[i]
IF ( ld_child_birth_date < PER_PER_CONTACT_DATE_OF_BIRTH[i])THEN
ld_child_birth_date = PER_PER_CONTACT_DATE_OF_BIRTH[i]
)
i= i+1
)
if(ln_child_count => 3 ) /*ln_child_count > 3*/
THEN
(valid = 'N'
ERROR_MESSAGE = 'A2F_ANC_A2F_ERR_PATERNITY' /*'This leave is only allowed upto 3 childrens'*/
RETURN vali d,ERROR_MESSAGE
)
if (l hild t 0)
-
7/24/2019 An Overview of Fusion Applications
158/243
if (ln_child_count = 0)
THEN
(VALID = 'N'
ERROR_MESSAGE = 'A2F_ANC_A2F_ERR_PAT_0KIDS' /* 'You can only avail this leave if you have dependent/adopted children' */
RETURN VALID,ERROR_MESSAGE
)
else(
valid='Y'
)
)
CHANGE_CONTEXTS(START_DATE=ld_start_date, END_DATE=IV_START_DATE)
(
WHILE ANC_PER_ABS_ENTRS_ABSENCE_ENTRY_ID_ARR.exists(j)
LOOP
(
CHANGE_CONTEXTS (ABSENCE_ENTRY_ID = ANC_PER_ABS_ENTRS_ABSENCE_ENTRY_ID_ARR[j])
(
IF (ln_pl_type_id = ANC_ABS_ENTRS_ABSENCE_TYPE_ID)
THEN(
IF (DAYS_BETWEEN(IV_START_DATE,ld_child_birth_date) > 365 OR DAYS_BETWEEN(IV_START_DATE,ld_child_birth_date) < 0)
THEN
(VALID = 'N'
ERROR_MESSAGE = 'A2F_ANC_A2F_FLEX_FROM_CHILDBIRTH' /* This leave needs to be applied within 1 year of chilbirth */
RETURN VALID,ERROR_MESSAGE
)
)
)
j=j+1
)
)
/*================ FORMULA SECTION END =======================*/
return VALID,ERROR_MESSAGE
-
7/24/2019 An Overview of Fusion Applications
159/243
Click on Edit Button and then select Correct as shown :
-
7/24/2019 An Overview of Fusion Applications
160/243
How-To Create a Global Absence Vesting Period Fast Formula in Fusion Applications
BUSINESSREQUIREMENT
Global Absence Vesting Period Formula is used when want to ensure what type of vesting (how long will an employee accrue leave balance) but will
not be allowed to apply for a leave.For this specific example requirement is:
We have a DFF (Descriptive Flex Field) defined at the assignment screen which holds employee assignment type namely 'Assignee', 'OTP' , 'Resi-
dent', 'Resident -Home'.....
The Requirement is:
A) There will be no Vesting Period if
1) the current assignment is First assignment and DFF value is either 'Assignee' , 'OTP' or 'Resident'
OR
2) the current assignment is Global Temporary Assignment and DFF value is either 'Assignee' , 'OTP' or 'Resident'
B) There will be Vesting Period if
1) the current assignment is NOT First assignment and DFF value is neither of 'Assignee' , 'OTP' or 'Resident'
OR
2) the current assignment is NOT Global Temporary Assignment and DFF value is neither of 'Assignee' , 'OTP' or 'Resident'
-
7/24/2019 An Overview of Fusion Applications
161/243
-
7/24/2019 An Overview of Fusion Applications
162/243
-
7/24/2019 An Overview of Fusion Applications
163/243
Click on Edit Button and then select Correct as shown :
-
7/24/2019 An Overview of Fusion Applications
164/243
Chapter 7 - Fusion HCM Extracts
-
7/24/2019 An Overview of Fusion Applications
165/243
To make things simpler we would try to publish all three categories in three different articles which would be posted soon. The article names (pro-
-
7/24/2019 An Overview of Fusion Applications
166/243
To make things simpler we would try to publish all three categories in three different articles which would be posted soon. The article names (pro
posed) are:
A)How-to Migrate Custom HCM Extract
B) How-to Make a Copy of Existing Delivered HCM Extracts
C) How-to Create a Custom HCM Extract from scratch.
How-To Migrate Custom HCM Extract in Fusion Applications
Business Requirement
At times we have multiple instances and we intend to move one HCM Extract (created in Development) environment to another instance ( UAT ) or even in Production.
We can use the Export Import feature then.
Export
Login to Fusion Applications, Navigate to Data Exchange and then search for the custom worker extract you wish to export.
http://www.apps2fusion.com/at/133-ashish-harbhajanka/1133-how-to-migrate-custom-hcm-extracthttp://www.apps2fusion.com/at/133-ashish-harbhajanka/1133-how-to-migrate-custom-hcm-extracthttp://www.apps2fusion.com/at/133-ashish-harbhajanka/1133-how-to-migrate-custom-hcm-extracthttp://www.apps2fusion.com/at/133-ashish-harbhajanka/1133-how-to-migrate-custom-hcm-extract -
7/24/2019 An Overview of Fusion Applications
167/243
Click on the Export symbol and xml file gets downloaded as displayed:
IMPORT
Navigate to Data Exchange as displayed:
-
7/24/2019 An Overview of Fusion Applications
168/243
-
7/24/2019 An Overview of Fusion Applications
169/243
A new popup window opens which asks for the File Path as displayed:
Give a new name if you wish to
-
7/24/2019 An Overview of Fusion Applications
170/243
Once the import Process is complete you would be able to search for the Extract:
-
7/24/2019 An Overview of Fusion Applications
171/243
Data Extraction - HCM Extracts or Reporting Tools - Which one to use when and why
In Fusion Applications we have various methods of extracting data. The most popularly used ones being:
a) HCM Extracts
b) Fusion Reporting Tools (BIP, OTBI , OBIA also referred to as OTBI-E)
A very common question for any Technical Consultant is which one of the above mentioned mechanisms (be it either HCM Extracts / BIP / OTBI / OBIA) are used for
extraction.
But before going into the details let us try to understand what the above terms mean :
-
7/24/2019 An Overview of Fusion Applications
172/243
a) BIP
BIP stands for Business Intelligence Publisher
BIP Reports stands for Business Intelligence Publisher Reports
For technical consultant with Reports 6i or more advanced versions it is just a new name given in Fusion Applications.
These kind of reports comprises of :
i) Data Model
This is typically a name given to a Data Set which comprises of Data Set (which in turn is a name given to a Data Source which could be with of SQL
Query, LDAP Query, XML Query, Static Data. )
Also has provision of adding separate placeholder columns, formula columns and other features
ii) Layout
This is a page/graphical area which shows how the report would look like.
This can comprise of Table, Letters, Logos, Icons, Images and what not.
Can have repeating and Non-Repeating Segments, XML Tags, Dynamic Values, Summary Columns..
The layout can be any of the output formats like PDF, RTF, Excel, E-text, CSV..
b) OTBI
OTBI Stands for Oracle Transactional Business Intelligence
Typically referred to as Drag and Drop Reporting (similar to Discoverer Reports)
This kind of Reports are created from specific subject areas (basically specific folder structure made up of logical data attributes clubbed together and are associ-
ated with some specific areas of application like for Payroll we have Payroll Real Time, Workforce Management Real Time andso on
OTBI Agents are new features which works similar to like ( Oracle Alerts we had in EBS)
Also there are ways to combine 2 different subject areas using a common attribute (named as facts)
c) OBIA
OBIA stands for Oracle Business Intelligence Applications
Pre-seeded Analytics Reports
Details about Trends, Historical Analysis, Predictions
On-Premise Applications has these features enabled
Off late Oracle has planned to release it to Cloud Customers too renaming them as OTBI-E
-
7/24/2019 An Overview of Fusion Applications
173/243
d) HCM Extracts
This is the Oracle recommended way of data transfer from Fusion Applications to other 3rdparty systems.
While this tool comprises of:
i) Define
Comprises of Define Tab (here we name the Extract Names and the parameters)
ii) Design
This is the section where we define the Extract Definition (HCM Data Objects as well as the Extract Attributes)
iii) Delivery Options
Different ways of delivery ( File Naming, Output Type, Delivery Frequency , Output Format, Layout ..)
In essence while its not impossible to create data extract for integration from either of the above mentioned options but HCM Extracts is preferred because of
following reasons :
a) It is a mix and match of all above options
Design is OTBI + OBIA (you drag and drop extract attributes and they could be both real time attributes(OTBI) or historical extract attributes(OBIA))
Deliver is BIP ( you create layout, report, template )
Define is again BIP (allows you to have custom parameters)
b) This has DELTA extract features
So each new run can compare itself with previous run (depending on parameter value passed during define extract phase) and provides only the changed data
-
7/24/2019 An Overview of Fusion Applications
174/243
Chapter 8: Other Miscellaneous Topics
-
7/24/2019 An Overview of Fusion Applications
175/243
Fusion Applications User Role Detail Report
FUSION APPLICATIONSUSER ROLE DETAIL REPORT
BUSINESSREQUIREMENT:
It is a very common requirement in almost all implementation where in the Stakeholders are interested to know how many user accounts are there is
the system along with the corresponding roles attached to them. While oracle has delivered some seeded Reports which could be run from
Application Diagnostic Framework, screenshot below (Troubleshooting -> Run Diagnostic Tests)
ORACLE DELIVERED REPORTS
1)
User Roles Display
2) User and Role: Role Details 3) User and Role: User Details
NAVIGATION TO RUN DELIVERED REPORTS
Login to Application -> Run Diagnostic Tests
-
7/24/2019 An Overview of Fusion Applications
176/243
After Running Reports :
DELIVERED REPORT 1->USER ROLES DISPLAY
User Roles Display: (Displays the Roles attached to procurement user)
Input Value : Sachin.Satpute
-
7/24/2019 An Overview of Fusion Applications
177/243
Output Screenshot :
DELIVERED REPORT 2->USER AND ROLE :ROLE DETAILS
User and Role : Role Details
Takes Role Name as input and displays all users who have the role attached to their user account. ( Secured i.e if the individual who is running the
Report has access to a specific Data Set individuals belonging to that Data Set would only be displayed).
Input Value : Employee
-
7/24/2019 An Overview of Fusion Applications
178/243
Output Screenshot :
ELIVERED EPORT USER AND OLE SER ETAILS
-
7/24/2019 An Overview of Fusion Applications
179/243
DELIVERED REPORT 3->USER AND ROLE :USER DETAILS
User and Role: User Details
Takes User Name as input and displays all roles attached to the user. (Secured i.e. if the individual who is running the Report has access to a
User Account being passed as input data would be displayed else no.)
Input value : Sachin.Satpute
Output Screenshot :
When (pur_emp.is_user_role_active = 'Yes' AND pur_emp.is_user_role_terminated = 'No' ) Then 'Active' When (pur_emp.is_user_role_active =
'No' AND pur emp is user role terminated = 'No') Then 'NeitherActiveNorTerminated'
-
7/24/2019 An Overview of Fusion Applications
180/243
No AND pur_emp.is_user_role_terminated No ) Then NeitherActiveNorTerminated
When (pur_emp.is_user_role_active = 'Yes' AND pur_emp.is_user_role_terminated = 'Yes') Then 'ActiveAndTerminated'
When (pur_emp.is_user_role_active = 'No' AND pur_emp.is_user_role_terminated = 'Yes' ) Then
'InactiveAndNotTerminated' End as "UserRoleStatus", pur_emp.role_start_date
"UserRoleStartDate", pur_emp.role_end_date "UserRoleEndDate", prd_emp.ab-
stract_role "IsRoleAAbstractRole", prd_emp.job_role "IsRoleAJobRole",
prd_emp.data_role "IsRoleADataRole",
prd_emp.is_role_active "IsRoleActive",
Case
When (prd_emp.abstract_role = 'Y' AND prd_emp.job_role = 'N' AND prd_emp.data_role = 'N' ) Then 'Abstract Role'
When (prd_emp.abstract_role = 'N' AND prd_emp.job_role = 'Y' AND prd_emp.data_role = 'N' ) Then 'Job Role' When (prd_emp.abstract_role = 'N'
AND prd_emp.job_role = 'N' AND prd_emp.data_role = 'Y' ) Then 'Data Role'
When (prd_emp.abstract_role is NULL AND prd_emp.job_role is NULL AND prd_emp.data_role is NULL ) Then '-NA--'
End as "UserRoleType",
prd_emp.role_common_name "RoleCommonName", prd_emp.multitenancy_common_name "MultitenancyCommon-Name", prd_emp.role_distinguished_name "IsRoleDistinguishedName", prdt_emp.role_name "UserRoleName",
prdt_emp.RoleDescription
FROM per_all_people_f papf
JOIN
(
SELECT ppnf.full_name,
ppnf.person_id
FROM per_person_names_f ppnf
WHERE ppnf.name_type = 'GLOBAL'
AND TRUNC(SYSDATE) BETWEEN ppnf.effective_start_date AND ppnf.effective_end_date
) ppnf_emp ON (
ppnf_emp.person_id = papf.person_id
AND TRUNC(SYSDATE) BETWEEN papf.effective_start_date AND papf.effective_end_date
)
LEFT OUTER JOIN
(
top related