Search Results create_metadata

Overview

HR_ADE_ADI_DATA_SETUP is an Oracle Application Object Library package owned by APPS that provides the metadata provisioning layer for Oracle Web Applications Desktop Integrator (Web ADI) within the HR (Human Resources) product family. Web ADI allows users to download, edit, and upload Oracle E-Business Suite data through desktop spreadsheets, and every such integration requires a registered "integrator" definition: a set of metadata rows describing the source query, the target interface columns, and the API used to validate or apply uploaded rows. HR_ADE_ADI_DATA_SETUP is the utility package that creates and maintains those definitions programmatically, rather than requiring a developer to populate the underlying Web ADI tables manually.

The package carries AUTHID CURRENT_USER, meaning its unqualified references resolve against the invoking schema's object namespace. In practice it is executed from an APPS session or from a custom schema that holds the necessary synonyms and privileges. Its header revision (peadeset.pkh 115.3, dated 2003) indicates a long-stable interface that has been carried forward essentially unchanged into EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

• CREATE_METADATA — The package's primary entry point and the object users typically search for. It creates the metadata required for a Web ADI integrator. The parameter p_metadata_type designates the integration kind — DOWNLOAD, UPDATE, or CREATE — and, per the source comments, download-type integrations do not require API details to be supplied. Additional parameters identify the owning application, the integrator user name, and optionally the view, form, API package and procedure, interface user, interface parameter, API type, and API return type that describe how uploaded spreadsheet rows are processed.
• CREATE_STANDALONE_QUERY — Registers a standalone SQL query as a Web ADI data source, independent of a form or view. Parameters identify the application, the integrator user name, the SQL text, and up to three optional query parameters, each with a name, type, and prompt. This supports ad hoc download-only layouts built directly from SQL.
• MAINTAIN_STANDALONE_QUERY — Maintains an existing standalone query definition, allowing the registered SQL text or its parameter definitions to be revised without recreating the integrator.

Tables Accessed

• BNE_INTERFACE_COLS_B — The Web ADI base table holding interface column definitions; rows are inserted or updated here to describe the columns of the integrator being created.
• HR_ADI_OBJECT_CODE_S — A HR-specific sequence used to generate unique object codes for the ADI definitions created by the package.
• ALL_TAB_COLUMNS — Queried to introspect column names and datatypes, most likely to derive metadata automatically when a view or table name is supplied instead of an explicit column list.
• FND_ORACLE_USERID — Used to resolve or validate the Oracle user identity associated with the interface or integrator definition.
• USER_SYNONYMS — Consulted to resolve the object names available to the invoking schema under AUTHID CURRENT_USER semantics.
• DUAL — Used for single-row expression evaluation and sequence access.

Usage Notes

HR_ADE_ADI_DATA_SETUP is a developer and administrator utility rather than an end-user API. It is normally invoked from a one-off PL/SQL script executed as APPS during the setup or migration of a Web ADI integrator, or during the construction of a custom HR desktop integration. It may also be called from a custom concurrent program that regenerates integrator metadata as part of a deployment. It is not referenced by any other documented package, so it sits at the leaf of the dependency tree and can be invoked without concern for downstream callers. Because the package writes directly to Web ADI metadata structures, changes take effect for new integrator sessions and should be validated in a non-production environment before promotion.