Tuesday, September 1, 2020

How To Create New User and add Roles In Oracle FUSION Cloud

๐Ÿ” How to Create User and Assign Roles in Oracle Fusion HCM Security Console

Oracle Fusion HCM provides a centralized way to manage user access through the Security Console. In this guide, we’ll walk through the step-by-step process of creating a user and assigning roles including BI Consumer Role, which is essential for OTBI access.


✅ Step-by-Step Instructions

  1. Go to your Oracle Fusion Application Login Page.
  2. Login using Admin credentials.
  3. From the homepage, click on the Navigator icon.
Oracle Navigator
  1. Navigate to Tools > Security Console.
Security Console
  1. Click on Users > Add User Account.
Add User
  1. Enter User Details like Name, Email, Start Date.
  2. Click on + Add Role and search for:
    • BI Consumer Role (for OTBI access)
Assign BI Role
OTBI Role Screenshot

๐Ÿ“ Final Step: Click on Save and Close to finalize user creation and role assignment.


๐ŸŽฏ Tips

  • Always verify if the role is inherited from a Job Role.
  • For OTBI, BI Consumer is the minimum role needed.
  • Use Security Console for periodic user audits.

๐Ÿ“š Related Articles

✅ Stay tuned for more Oracle Fusion tutorials!

Sunday, September 1, 2019

Sample format to include all in parameter list

๐Ÿ“Œ Sample Format to Include All IN Parameters in PL/SQL Procedures

When designing PL/SQL procedures in Oracle, you often encounter scenarios where multiple inputs are needed. Organizing all IN parameters in a consistent and scalable format not only enhances readability but also improves maintainability. This guide provides a clean and reusable sample format for writing PL/SQL procedures with multiple IN parameters.

PLSQL IN Parameters Format

Example format for handling IN parameters in PL/SQL

๐Ÿงพ Sample Procedure Format with All IN Parameters

CREATE OR REPLACE PROCEDURE insert_employee_info (
    p_emp_id       IN NUMBER,
    p_first_name   IN VARCHAR2,
    p_last_name    IN VARCHAR2,
    p_email        IN VARCHAR2,
    p_salary       IN NUMBER,
    p_hire_date    IN DATE,
    p_department   IN VARCHAR2
)
IS
BEGIN
    INSERT INTO employees (
        emp_id, first_name, last_name, email,
        salary, hire_date, department
    )
    VALUES (
        p_emp_id, p_first_name, p_last_name, p_email,
        p_salary, p_hire_date, p_department
    );

    DBMS_OUTPUT.PUT_LINE('Employee record inserted successfully.');
EXCEPTION
    WHEN OTHERS THEN
        DBMS_OUTPUT.PUT_LINE('Error: ' || SQLERRM);
END insert_employee_info;

๐Ÿง  Why Use This Format?

  • Clarity: Clean separation between parameter names and logic.
  • Scalability: Easy to extend when more parameters are added.
  • Standardization: Follows Oracle best practices for readable procedures.
  • Debug-Friendly: Includes DBMS_OUTPUT for status and exception handling.

๐Ÿ’ป How to Execute the Procedure

EXEC insert_employee_info (
    101, 'John', 'Doe', 'john.doe@example.com',
    55000, SYSDATE, 'HR'
);
๐Ÿ’ก Tip: Use meaningful prefixes like p_ for parameters to differentiate them from column names or variables.

❗ Common Mistakes to Avoid

  • Omitting `IN` keyword (required in explicit mode).
  • Using undeclared variables or mismatched data types.
  • Missing exception block for error handling.
  • Using same name for parameter and table column (leads to confusion).

๐Ÿ“š Related Resources

๐Ÿ“Œ Conclusion

Following a structured and readable format for your IN parameters can make your PL/SQL code easier to maintain and debug. As your applications grow in complexity, these best practices become even more important.

Happy coding with PL/SQL!

Handling long-running BI Publisher (BIP) reports with huge data in Oracle Integration Cloud

 Handling long-running BI Publisher (BIP) reports with huge data in Oracle Integration Cloud (OIC) is a very common real-time challenge. He...

Popular Posts