HTP.P Build-In Package

Using HTP.P for Dynamic HTML Generation in Oracle APEX

When building Oracle APEX applications, developers often rely on built-in components like Interactive Reports and Forms. However, there are scenarios where these standard components cannot achieve the exact visual layout or dynamic behavior required. In these cases, the HTP.P procedure from the PL/SQL Web Toolkit becomes an essential tool for generating custom HTML directly from the database (Oracle, 2024).

---

What is HTP.P?

The HTP (HyperText Processor) package is a built-in Oracle PL/SQL library that allows developers to generate HTML tags from within PL/SQL code (Oracle, 2026). The P procedure—short for "Print"—is the most commonly used subprogram within this package. It accepts a string argument and writes it directly to the HTTP output buffer, which is then rendered by the user's browser (Oracle, 2026).

In Oracle APEX, this functionality is exposed through the PL/SQL Dynamic Content region type. Unlike standard reports that expect a SQL query, this region type expects a PL/SQL block that "prints" HTML using HTP.P (Oracle, 2024).

-- Basic Syntax
htp.p('<h1>Hello World</h1>');

---

Why Use HTP.P in APEX?

While APEX provides many declarative components, HTP.P offers several distinct advantages:

• Complete Control: You can generate any HTML structure, including custom CSS grids, dashboards, and interactive widgets that APEX templates cannot easily replicate (Oracle, 2024).
• Dynamic Content: You can loop through database records and generate HTML for each row, allowing for highly customized data presentation.
• Integration with PL/SQL Logic: You can combine complex business logic (IF/ELSE statements, cursor loops) with HTML generation in a single code block.

---

Practical Application: Dashboard Cards in the Change Management System

In my Capstone Project, I used HTP.P to build a dynamic dashboard that displays real-time statistics for the Change Management System. The dashboard needed to show the number of users in each role (Requesters, Reviewers, Approvers, Developers, Deploy Admins) and the number of requests processed at each stage.

The following code demonstrates how HTP.P was used to generate a "card" for the Requester role:

-- Open the card container
htp.p('<div style="flex: 1; background: #f8fafc; border-left: 4px solid #3b82f6; padding: 20px; border-radius: 8px;">');

-- Print the card title
htp.p('<h3 style="color: #64748b;">REQUESTERS</h3>');

-- Print the dynamic data (fetched from a SYS_REFCURSOR)
htp.p('<h2 style="color: #1e293b;">' || v_total_requesters || ' Users</h2>');
htp.p('<p style="color: #3b82f6;">' || v_total_initiated || ' Initiated</p>');

-- Close the card container
htp.p('</div>');

By repeating this pattern for each role, I was able to create a visually appealing dashboard with six distinct cards, all generated dynamically from data stored in the CHANGE_HISTORY and CHANGE_REQUESTS tables. The HTP.P procedure allowed me to combine database logic with presentation logic in a way that standard APEX components could not achieve.

---

Best Practices

When using HTP.P in APEX, consider the following guidelines:

• Keep Logic Separate: While it is tempting to mix complex PL/SQL logic with HTML generation, it is better to fetch data first, then generate HTML in a separate section (Oracle, 2024).
• Use CSS Frameworks: Since HTP.P only generates raw HTML, you must manually include CSS styles or link to external stylesheets (like Bootstrap or Tailwind) to achieve a modern look.
• Escape User Input: When displaying user-generated content, always use APEX_ESCAPE.HTML or HTP.ESCAPE_SC to prevent Cross-Site Scripting (XSS) attacks (Oracle, 2026).

---

Conclusion

HTP.P is a powerful tool for Oracle APEX developers who need to go beyond the limitations of declarative components. By leveraging the PL/SQL Web Toolkit, you can generate fully customized, data-driven HTML pages directly from the database. In the Change Management System project, this approach enabled the creation of a professional dashboard that would have been difficult to replicate using standard APEX regions alone.

---

References

Oracle. (2024). App builder user's guide: Rendering HTML using custom PL/SQL (24.1). Oracle Help Center. https://docs.oracle.com/en/database/oracle/apex/24.1/htmdb/rendering-html-using-custom-plsql.html

Oracle. (2026). PL/SQL packages and types reference: HTP (26). Oracle Help Center. https://docs.oracle.com/en/database/oracle/oracle-database/26/arpls/HTP.html