Oracle Cloud HCM

    Bank Account User Rules Update


 

In Cash Management, Bank account rule represents the properties of a bank account attribute for a specific country and a page.

The rule identifies the display and required properties as well as the label of an attribute.

Page indicates the usage or the flow that consumes the bank account rules in the application.

The pages of our interest are ‘ORA’ and ‘SupplierRegistration’.

ORA page rules are seeded according to bank account standards followed across countries.

These rules cannot be changed and are used by default on pages if their page specific rules are not defined.

SupplierRegistration rules deviate from ORA rules and are seeded specific for the next generation supplier registration page to simplify the bank account entry page for anonymous users registering suppliers. You can update these rules or also create new ones under this page if a rule doesn't already exist for the attribute you want to change.

To change properties of an attribute, first find if there exists a seeded rule for that attribute for either of the SupplierRegistration or ORA pages. If there exists a SupplierRegistration rule, update the rule directly. If a rule for SupplierRegistration page doesn't exist but ORA rule exists (or no rule exists), then create a new rule for the SupplierRegistration page.

If both SupplierRegistration and ORA rules exist for an attribute, the SupplierRegistration rule is considered and if there are no rules defined, the attribute is considered to be always displayed.

If the ORA rule for an attribute has the required property as ‘true’, you cannot change the attribute to not required or hidden even for SupplierRegistration page.

The next-generation self-service supplier registration flow supports country specific dynamic bank accounts page. The dynamic behavior of the bank accounts page is driven through country specific rules that are configurable using the bankAccountUserRules REST resource.

 Out of the box, country specific rules are provided to support an easier uptake, and simplified bank accounts page to improve the user experience.

If you still have requirements to change these rules, you can use the bankAccountUserRules REST resource directly, or through the Oracle Visual Builder Add-in for Excel.

 

The fields displayed on the user interface are governed by the rules defined in the table CE_CTRY_SPECIFIC_UI_RULES.

 

We've a REST service to update these rules.

Sample:

Below is the Oracle provided bank account rules for Brazil.

Brazil

Country Code: BR

Attribute Name

Display Indicator

Label Code

Required: Yes or No

ACCOUNT_NUMBER

Y

Y

IBAN

Y

N

ACCOUNT_TYPE

Y

N

CHECK_DIGIT

Y

N

ACCOUNT_NAME

Y

N

ACCOUNT_NAME_ALT

Y

N

SEC_ACCT_REF

Y

COMPANY_CODE

N

BANK_NAME

Y

Y

BANK_CODE

Y

Y

BRANCH_NAME

Y

N

BRANCH_NUMBER

Y

Y

BIC

Y

N

 

If we need to make the attribute Bank Account Name as Mandatory, below RESET API can be run for the same.

 

https://<could-url>/fscmRestApi/resources/11.13.18.05/bankAccountUserRules

 

/fscmRestApi/resources/11.13.18.05/bankAccountUserRules

{

            "CountryCode": "GI",

    "BankAccountFieldName": "ACCOUNT_NAME",

    "DisplayFlag": true,

    "RequiredFlag": true,

    "PageName": "FUSE"

}

Comments

Post a Comment

Popular posts from this blog

Oracle Cloud HCM Open Ended Absences Update

  Oracle Cloud HCM Open Ended Absences       In Oracle Cloud HCM, when there exist open ended absences like Maternity and Sickness and Employee is terminated, it is seen that there is no end date updated to these open absences as of Termination Date. This leads to ambiguity in reporting and payroll To address this issue, worked on an automation process which will pick such records and put an end date same as the termination date.   Design Steps   1.       Build a BIP report to list the Open ended absences for Terminated employees 2.      Write the Bursting definition to feed the BIP report output to Extract 3.      Desing the ETF template to build the HDL Template for End dating Open Absence 4.      Design a HCM Extract that will take the output fed from BIP Report and Auto Loads as   HDL process 5.   ...
Read more

Oracle HCM Absence Orphan Records

Image
Sometimes We come across a less known Error while submitting an Absence in Oracle Cloud HCM with an Error Code ANC-3405194 Likely caused when  Update of Accrual plan is done after an accrual process has already run till a date in future. OR  Entering accrual via HDL in a previous plan period and missing to run calculate accrual. This is Resolved when we Delete the Orphaned records found by Below Query Query to identify the Orphan Absence Records in the System SELECT  per_accrual_entry_dtl_id,         ppl.person_number       ,         ass.assignment_number   ,         plans_tl.NAME           ,         TYPE                    ,         procd_date FROM    fusion.anc_per_acrl_entry_dtls acrl_dtls ,         fusion.per_all_people_f ppl  ...
Read more
Image
           Deploying an AI agent on Redwood Page                                    1.     N avigate to the AI Agent Studio from the Tools Menu             2.    Select any available delivered AI agent and Copy it to be used by    your business.                         3.     Run it to see all the Profiles and Config are good.         4.     Publish the AI Agent              5.       Navigate to My Client Groups -> Guided Journeys      6.       Create New Journey      7.       Create Draf...
Read more