Search Results get_cursor_from_clause

Overview

HR_DM_GEN_TDS is a generator package within the Oracle E-Business Suite Human Resources Data Migration (HR_DM) subsystem. Its name, "Gen TDS," denotes "generate Table Data Structures," and it belongs to the family of HR Data Migration utilities that support the extraction, transformation, and loading of legacy or external HR data into Oracle HRMS tables. The package operates as a metadata-driven code generator rather than as a transactional or business-rule API. It reads descriptive information about target HRMS tables — held in the HR_DM repository tables — and programmatically constructs a companion PL/SQL package (referred to as a "TDS package") plus the associated procedures required to populate or extract data for each registered table.

The package is classified as OTHER in the ETRM 12.2.2 inventory, reflecting that it is a developer-facing migration utility and not part of the supported public API surface. It is owned by APPS and is referenced by two other packages, indicating that it sits within a chain of generation steps driven by the HR Data Migration framework rather than being invoked standalone by end users.

Key Procedures and Functions

The documented interface exposes two procedures:

• CREATE_TDS_PACAKGE — Generates the TDS package and its related procedures for a given table. Input to the procedure describes the table via a record type (covering attributes such as whether the table is datetracked, whether it holds global data, and whether it uses a surrogate primary key), together with collections that enumerate the table's columns, the column-and-datatype parameter lists, and the columns that carry foreign keys to AOL tables (for example USER_ID columns). The procedure uses these inputs to build the parameter list and body of the generated TDS procedures, including any procedure needed to resolve an AOL developer key from a given ID value. (The internal spelling "PACAKGE" is retained as documented.)
• GET_CURSOR_FROM_CLAUSE — Returns the list of tables required to build the download "FROM" clause used by the generated extraction logic. This supports assembly of the correct join set so that the generated TDS package can query the source tables with all required relationships intact.

No public parameter lists beyond those shown in the package specification excerpt are documented; parameter behaviour is described at the purpose level only.

Tables Accessed

The package works primarily against the HR Data Migration repository tables that hold the metadata it consumes and the registrations it produces:

• HR_DM_TABLES — the register of HRMS tables eligible for data migration, supplying the table-level facts the generator requires.
• HR_DM_MIGRATIONS — migration business definitions that scope which tables and processes are involved in a given migration.
• HR_DM_HIERARCHIES — hierarchy metadata used to determine parent/child relationships between registered tables, feeding the FROM-clause construction performed by GET_CURSOR_FROM_CLAUSE.
• DBMS_SQL — Oracle's dynamic SQL package, invoked to parse, execute, and generate the dynamic DDL/DML statements that define the TDS package and its procedures.
• PLITBLM — the PL/SQL table (index-by table) built-in package, used for the collection handling that underpins the table-of-columns inputs.

Usage Notes

HR_DM_GEN_TDS is not invoked through standard HRMS forms or concurrent programs by end users. It is typically called from within the HR Data Migration setup and generation flow, where an administrator registers a table into the HR_DM repository (via HR_DM_TABLES and related entities) and the framework then invokes CREATE_TDS_PACAKGE to emit the corresponding TDS package. That generated package subsequently performs the actual row extraction for the registered table.

Because the interface accepts internal record and collection types from HR_DM_GEN_MAIN and HR_DM_LIBRARY, direct invocation from custom code is fragile and version-sensitive. Customisations should call the HR_DM framework entry points rather than HR_DM_GEN_TDS directly. The package is best understood as plumbing: it produces code, and it must be re-run whenever a registered table's column set, datetracking attributes, or AOL foreign-key columns change, so that the generated TDS package remains consistent with the underlying schema.