Search Results line_tbl_type

Overview

The APPS.OKE_FORM_DD250_EXT package body is the standard Oracle E-Business Suite extension hook associated with the Oracle Order Capture / Order Management shipping document framework. In EBS 12.1.1 and 12.2.2, shipping documents such as packing slips, bills of lading, and commercial invoices are generated through the DD250-series report and form templates. Each shipping document template exposes a corresponding extension package whose interface methods are invoked at defined points during document generation, allowing customers to substitute or augment standard behavior without modifying seeded Oracle code.

This package serves as the customization insertion point for the DD250 shipping document. It allows implementers to override the default shipment prefix value printed on the document and to manipulate the header and line record structures before the document is rendered. In its delivered form, the package is a shell: every method returns either a NULL value or an unmodified copy of the input, which preserves the seeded behavior exactly. Business-specific logic is expected to be added in the corresponding custom schema or directly within this package body during implementation.

Key Procedures and Functions

• Override_Shipment_Prefix — A function that accepts shipment context identifiers and returns a VARCHAR2 value representing an override for the shipment prefix text that appears on the printed DD250 document. In the seeded body it returns NULL, signaling to the calling report or template that no override applies and that the standard prefix should be used. Implementers populate this function to derive a custom prefix from shipment attributes such as header, delivery, inventory organization, or ship-from location.
• Override_Form_Data — A procedure invoked immediately before the DD250 form data is finalized for rendering. It receives the key header and delivery identifiers along with input header and line record structures, and returns the output header and line record structures. In the seeded body, the output assignments copy the inputs unchanged, effectively performing a no-op. This procedure is the standard location for applying record-level transformations, such as masking values, adding derived attributes, or reordering line content prior to print.

Tables Accessed

No tables are referenced within the delivered package body. All data required for the override logic is passed in as scalar identifiers or as PL/SQL record structures defined in the parent package OKE_FORM_DD250. Because the extension body operates purely on in-memory parameters, it introduces no direct SQL dependencies and no additional read or write locks on Order Management or Shipping Execution base tables. Implementers who add query logic to these methods should be aware that additional database round trips occur inside the document generation cycle.

Usage Notes

The package is not called directly by end users or concurrent programs. Instead, the DD250 report or form invokes the extension methods during printing when the corresponding calling interface is enabled. The P_Line_Tbl parameter, referenced in the search term line_tbl_type, is an instance of OKE_FORM_DD250.Line_Tbl_Type, the nested table collection type that carries the document line records into the override procedure. The type is owned by the parent package and must be used consistently when customizing these signatures.

Customizations should avoid changing the published procedure and function signatures, because the calling report binds to the exact parameter list documented here. Changes to the signatures can cause the shipping document generation to fail at runtime. The extension package is referenced by one other documented package, reflecting its position as a dependent extension point of the DD250 form framework. Typical implementation steps involve copying the seeded logic, adding business rules, and validating output during a controlled shipping print run before promotion to production.