How to disable IBAN Validation When Createing Bank Account for an Employee

 How to disable IBAN Validation When Createing Bank Account for an Employee

Please check the value of the profile option, Disable Country Specific Bank Validations
This profile can be set (Manage Cash Management Profile Options) at the site, product, or user level. The profile is predefined with a default value of No at the site level.
The country-specific validations pertaining to the bank code, branch number, account number, check digit, and IBAN can be disabled by this profile option. If the profile is set to Yes these validations are not performed. The checks for unique banks, branches, accounts, and the mandatory requirement of bank account number are not affected by this profile.

Fusion Absence Management: Error While Saving Absence Plan with Multi year Carryover

 

Error While Saving Absence Plan with Multi year Carryover

Getting below error when we are running "Calculate Accruals and Balances" program for person number 1031582

oracle.jbo.AttrValException: JBO-27035: Attribute ParentRefId is required.

CAUSE:

File Name or Source
-------------------------
select * from fusion.FND_LOOKUP_VALUES_VL where LOOKUP_CODE like'ANC%'

Description
--------------
Checking if any lookup is blocking the functionality.

Relevance to the Issue
---------------------------
The lookup ANC_MULTIYEAR_COVR_DISABLED is enabled. This is causing the issue.

Solution:

Lookyp Type : ANC_PROC_CONFIGS

Lookup Code : ANC_MULTIYEAR_COVR_DISABLED

Disable the lookup ANC_MULTIYEAR_COVR_DISABLED.

Null value check in Fast formula in cloud

 

Null value check in Fast formula in cloud

if isnull(VALUE_SET_VALUE) = 'N' then

  (

  VALUE_SET_VALUE = 0

  )


However, it does the exact opposite of what its name suggests: it returns 'Y' if the value is not null, and it returns 'N' if the value is null.

SELECT..INTO returns too many rows occurred in table pay_status_processing_rules_f at location 512

 

When attempting to Run Quickpay,

the following error occurs.

ERROR

-----------------------

A system error SQL-02112: SELECT..INTO returns too many rows occurred in table pay_status_processing_rules_f at location 512. Contact your help desk.

The cause of the issue is invalid / incorrect data in fusion.pay_status_proc_rules_f

There are Duplicate rows of Status processing rules for the Element

Run the Below query to identify the element having duplicate status processing Rules

Query1 : select  distinct element_name,ldg.name,s1.STATUS_PROCESSING_RULE_ID,s1.element_type_id

from fusion.pay_status_proc_rules_f s1, fusion.pay_status_proc_rules_f

s2,fusion.pay_element_types_vl petf,fusion.per_legislative_data_groups_vl ldg

where s1.element_type_id=s2.element_type_id

and petf.element_type_id=s2.element_type_id

and ldg.legislative_data_group_id=s1.legislative_data_group_id

and s1.status_processing_rule_id<>s2.status_processing_rule_id

and s1.status_processing_rule_id>s2.status_processing_rule_id

order by ldg.name;

Check the Status Processing Rules for the Element.Check if there are Multiple Rows available.

If there are More than one Status Processing Rules Delete one of the Rules and retest the issue,

 

If you are unable to delete the Status processing rules from UI, you can go for the HDL approach to delete the same,

Query2 : select * from fusion.pay_status_proc_rules_f where ELEMENT_TYPE_ID = <Use the Element Type ID from First Query>

 

Sample data File

METADATA|StatusProcessingRule|ElementId|LegislativeDataGroupName|StatusProcessingRuleId

DELETE|StatusProcessingRule|300000545904797|AE Legislative Data Group|300000545905167

File Name : PayrollElementDefinition.dat

use the StatusProcessingRuleId from Query 2.

How to Define the Source System Owner for HDL in Oracle Fusion

 How to Define the Source System Owner for HDL in Oracle Fusion

In this post , We will be discuss about the HDL and one of the Important thing we do use in the HDL integration and that is called source system owner. 

Source system owner helps to identifies the imported record in oracle cloud that from which external system we have imported 

these records either through integration or manual import through HDL. Source System Owner in HDL helps to identify the imported 

data in oracle fusion. We do recognize the information in oracle cloud using source system owner. Here below in this post , 

i will try to define the steps to create  Source System Owner for HDL in Oracle Fusion. 

We can use User Keys/Source Keys when we load data for Business Objects. For using Source Keys, 

we first need to define the Source System Owner and then use the defined Source system owner in the HDL file.

Steps to create/define the Source System Owner for HDL in Oracle Fusion 

Step1:- In Fusion Applications > Click on Navigator > Setup and Maintenance

Search for task "Manage Common Lookups"

Step2:- Search for the Lookup Type of "HRC_SOURCE_SYSTEM_OWNER"

and Click on the '+' icon to create the new Source in this Lookup  to use in the HDL scripts.

Unable to enable ADFdi Add-in for Excel

 Unable to enable ADFdi Add-in for Excel

MS Excel open, but the spreadsheed does not work, that is, it does not try to connect.

Enable the addon using below steps

  1) Click Microsoft Office button - Excel options - Add-Ins
  2) In the Manage box, click Disabled Items, and then click Go.
  3) If the AdfDI addon is listed, select it and click Enable
  4) Again, navigate till Addons - In the Manage box, click COM Add-ins, and then click Go.
  5) In the COM Add-Ins dialog box, select the check box next to the AdfDI add-in - OK

Employee Element Entry Query - Fusion Payroll

 Employee Element Entry Query - Fusion Payroll

select

   papf.person_number empnumber,

   ppnf.full_name empname,

   petf.base_element_name salaryelement,

   pivf.base_name inputvalue,

   peevf.screen_entry_value entryvalue,

   to_char(peevf.effective_start_date, 'DD-MON-YYYY') elementstartdate,

   to_char(peevf.effective_end_date, 'DD-MON-YYYY') elementenddate 

from

   pay_element_entries_f peef,

   pay_element_entry_values_f peevf,

   pay_element_types_f petf,

   pay_input_values_f pivf,

   per_all_people_f papf,

   per_all_assignments_f paaf,

   per_person_names_f ppnf 

where

   1 = 1 

   and peef.element_entry_id = peevf.element_entry_id 

   and peef.element_type_id = petf.element_type_id 

   and peevf.element_entry_id = peef.element_entry_id 

   and pivf.input_value_id = peevf.input_value_id 

   and papf.person_id = peef.person_id 

   and papf.person_id = ppnf.person_id 

   and paaf.person_id = papf.person_id 

   and paaf.primary_flag = 'Y' 

   and paaf.assignment_type = 'E' 

   and ppnf.name_type = 'GLOBAL' 

   and pivf.element_type_id = petf.element_type_id 

   and trunc(sysdate) between trunc(papf.effective_start_date) and trunc(papf.effective_end_date) 

   and trunc(sysdate) between trunc(paaf.effective_start_date) and trunc(paaf.effective_end_date)  

   --and petf.base_element_name like ('Basic%') 

order by

   petf.base_element_name,

   papf.person_number asc