Refresh Business objects is a process which is used to create the HDL template for a business object with the latest supported attributes.
When to run ‘Refresh Business Objects’ process:
It is advised to run this process:
After every upgrade
After any new DFF/EFF attributes are configured for any HDL supported business objects.
How to run‘Refresh Business Objects’ process:
To run ‘Refresh Business Objects’ process, navigate to My Client Groups -> Data Exchange -> View Business Objects
On the View Business Objects UI, you will see 2 buttons:
a. Refresh Object – This is used when you want to refresh only one object at a time. This is usually run when any new DFF attributes are setup for a particular object. Once you click on ‘Refresh Object’, you will see the below screen:
Click on Submit button to submit the process.
You can then click on ‘View Process Results’ button to check the progress:
Once the process completes, you can see the last refreshed date:
b. Refresh All Objects – This is used when you want to refresh all the business objects. This is usually run post release upgrade.
Post P2T refresh, it is mandatory to mask the actual email Ids of the users in cloned test environment. This is required to avoid any unwanted emails getting triggered to the end users.
Use the below SQL to extract the data in HDL format:
select 'MERGE' "METADATA",
'PersonEmail' "PersonEmail",
pea.email_address_id "EmailAddressId",
pea.person_id "PersonId",
to_char(pea.date_from,'RRRR/MM/DD') "DateFrom",
to_char(pea.date_to,'RRRR/MM/DD') "DateTo",
pea.email_type "EmailType",
-->pea.email_address "1EmailAddress",
replace(replace(pea.email_address,'@','@invalid'),'.co','.xco') "EmailAddress", --> Change the format as per your requirement
(select email_hrc.source_system_id
from hrc_integration_key_map email_hrc
WHERE pea.email_Address_id = email_hrc.surrogate_id) "SourceSystemId",
(select email_hrc.source_system_owner
from hrc_integration_key_map email_hrc
WHERE pea.email_Address_id = email_hrc.surrogate_id) "SourceSystemOwner"
from per_email_addresses pea
where 1=1
and upper(email_address) like '%XXCOMPANY%' --> Change the format as per your requirement
Query with Person Number:
select 'MERGE' "METADATA",
'PersonEmail' "PersonEmail",
pea.email_address_id "EmailAddressId",
pea.person_id "PersonId",
papf.person_number "PersonNumber",
to_char(pea.date_from,'RRRR/MM/DD') "DateFrom",
to_char(pea.date_to,'RRRR/MM/DD') "DateTo",
pea.email_type "EmailType",
-->pea.email_address "1EmailAddress",
replace(replace(pea.email_address,'@','@invalid'),'.co','.xco') "EmailAddress", --> Change the format as per your requirement
(select email_hrc.source_system_id
from hrc_integration_key_map email_hrc
WHERE pea.email_Address_id = email_hrc.surrogate_id) "SourceSystemId",
(select email_hrc.source_system_owner
from hrc_integration_key_map email_hrc
WHERE pea.email_Address_id = email_hrc.surrogate_id) "SourceSystemOwner"
from per_email_addresses pea, per_all_people_f papf
where 1=1
and pea.person_id = papf.person_id
and trunc(sysdate) between papf.effective_start_date and papf.effective_end_date
and upper(email_address) like '%XXCOMPANY%' --> Change the format as per your requirement
Once the data is generated, create the HDL file and load the Worker.dat.
Post data load steps:
Run “Send Personal Data for Multiple Users to LDAP” process. This process will sync up the latest email address from worker email to user.
Login to Security Console and verify for couple of users from UI or you can verify from backend.
Disable the notifications (optional) – Navigate to Security Console -> User Categories -> Notification Preferences -> Uncheck the Enable Notifications:
4. Or you can redirect all the notification to single email address. Search for ‘Manage Approval Groups’ task in ‘Setup and Maintenance”:
Clicking on above task will take you to the BPM Worklist page.
Click on “Administration” button and search for Test Notification Email Address and provide the value where you want to redirect all your notifications:
If you want to completely purge the email data then use below post:
Sometimes it is required to delete the uploaded phones data from Fusion HCM. Below query can be used to create a BIP report which in turn can be used to generate HDL file to delete phones data.
The query can be modified to delete phones data for contacts as well as for other person types.
Supported Version :- 20D
Query:
SELECT 'METADATA|PersonPhone|PhoneId|PhoneType|PersonId|DateFrom|SourceSystemId|SourceSystemOwner' D_ROW
FROM DUAL
union
SELECT 'DELETE|PersonPhone|'||
pp.phone_id||'|'||
pp.phone_type||'|'||
pp.person_id||'|'||
to_char(pp.date_from,'RRRR/MM/DD')||'|'||
hikm.source_system_id||'|'||
hikm.source_system_owner
from per_phones pp,
hrc_integration_key_map hikm
where pp.phone_id= hikm.surrogate_id
and exists (select 1 from per_periods_of_service where person_id=pp.person_id)
