How to define Work Structure
Manual-Usage: The manual should be used along with the Fusion HCM application in order to familiarize themselves with the navigation and functionality. 1. Login to Oracle Fusion-HCM: This section covers…
Read MoreManual-Usage: The manual should be used along with the Fusion HCM application in order to familiarize themselves with the navigation and functionality. 1. Login to Oracle Fusion-HCM: This section covers…
Read More1.- Log in with our credentials 2.- Clic on the “Purchase” module and select “Purchase order” 3.- Go to the task bar and choose the “Create order”…
Read MoreIntroduction: This blog has the SQL query that can be used to pull the data for the AR Customer Collector Portfolio Report Cause of the issue: Business wants to see the Customer Collector Portfolio Details How do we solve: Create a BI report in fusion using below SQL query to extract the details. SELECT customer_name, account_number, portfolio, portfolio_description, business_unit, account_profile_class_effective_end_date, account_profile_class, account_profile_collector FROM ( SELECT hp.party_name customer_name, hca.account_number account_number, hca.attribute10 portfolio, ( CASE WHEN hca.attribute10 = ‘Default – Portfolio’ THEN ‘Portfolio Default for Unclassified Customer Accounts’ WHEN hca.attribute10 != ‘Default – Portfolio’ THEN hca.attribute10 END ) portfolio_description, hou.name business_unit,…
Read MoreIntroduction: This blog has the SQL query that can be used to pull the data for the AR Customer Dunning Strategy Status Report Cause of the issue: Business wants to see the AR Customer Dunning Strategy Status Report How do we solve: Create a BI report in fusion using below SQL query to extract the details. With cust as ( select hp.party_id, hp.party_number cust_number, hp.party_name cust_name, hca.cust_account_id, hca.account_number CUST_ACCOUNT_NUMBER from hz_parties hp, hz_cust_accounts hca where hp.party_id = hca.party_id ) , cltr as ( select acl.collector_id, acl.employee_id, acl.name collector, pmail.email_address collector_email from ar_collectors acl, per_email_addresses_v pmail where acl.employee_id = pmail.person_id ) , stg_temp as ( select WORK_ITEM_TEMP_ID, name task, DESCRIPTION from IEX_STRY_TEMP_WORK_ITEMS_VL group by WORK_ITEM_TEMP_ID, name, DESCRIPTION )…
Read MoreBusiness requested a new TDS rate for the supplier to apply at invoice level. Steps: Load new recovery tax rate. Navigator: Setup and Maintenance à Financials à Manage tax codes …
Read Moredeclare l_ctx dbms_xmlquery.ctxHandle; l_clob clob; begin l_ctx := dbms_xmlquery.newContext(‘select * from <TABLE_NAME>’); dbms_lob.createtemporary(:g_clob,true,dbms_lob.session); :g_clob := dbms_xmlquery.getXml(l_ctx); end;
Read MoreBusiness requested a new VAT to apply the tax at the invoice level. Steps: Go to Set up and Maintenance > Financials > Transaction Tax > Manage Tax Rates and…
Read MoreIntroduction: The purpose of this document is to demonstrate how we pass multiple set of parameters in REST API through Postman. Cause of the issue: Whenever we test any REST…
Read MoreIntroduction: Apache Tomcat Upgrading from Tomcat 8 to Tomcat 9 is a critical step for taking advantage of the latest features, improved performance, and enhanced security. This blog provides a structured approach for a successful upgrade. Why we need to do: Tomcat 9 introduces support for Servlet 4.0, HTTP/2, and other modern web technologies. Many applications require these features to maintain compatibility and performance. Moreover, Tomcat 8 has reached its end-of-life phase, leaving systems exposed to unpatched vulnerabilities. Challenges and Issues Faced During Upgradation: Configuration Incompatibilities: Configuration files such as server.xml, web.xml, and context.xml may require adjustments to align with Tomcat 9 standards. Application Dependencies: Applications running on Tomcat 8 may rely on deprecated libraries or APIs that are removed in Tomcat 9. Custom Scripts and Integrations: Custom startup scripts, monitoring tools, or integrations might need modifications for compatibility. Steps to Upgrade Tomcat from Version 8 to Version 9: Backup Your Current Setup: l Backup all configuration files: server.xml, web.xml, context.xml. l Backup application WAR files and logs. l Snapshot the current environment to ensure rollback options. Download and Install Tomcat 9: l Download the Tomcat 9 binary from the official Apache Tomcat website. l Extract the archive to a new directory (do not overwrite the existing Tomcat 8 directory). Migrate Configuration Files: l Compare the server.xml, web.xml, and context.xml from Tomcat 8 with the default Tomcat 9 configurations. l Update configurations to align with Tomcat 9 schema. Remove any deprecated elements. Migrate Applications: l Deploy your application WAR files to the webapps directory in the Tomcat 9 installation. l Test applications for compatibility, focusing on deprecated APIs and libraries. Update Custom Scripts: l Modify any startup scripts or custom integrations to reference the new Tomcat 9 directories and binaries. Test the Upgrade: l Start Tomcat 9 using the startup.sh or startup.bat script. l Monitor logs in the logs directory for errors. l Test all deployed applications to ensure they function as expected. Rollback Plan: l If issues are encountered, stop Tomcat 9 and revert to the backup of Tomcat 8.…
Read MoreIntroduction: This blog has the SQL query that can be used to pull the data for the oracle cloud users having what roles & for which BU it is assigned…
Read More