Search Results insert_export_schedules




Overview
Explore in AI Chat

Overview

AMS_ADI_OBJECTS_EXPORT_PVT is a private PL/SQL package body in the APPS schema that supports the Oracle Marketing (AMS) module's object export and migration facility. The "ADI" prefix designates the Application Data Installer / object movement infrastructure used within Oracle E-Business Suite, and the "_PVT" suffix marks the package as an internal implementation unit intended to be invoked through the accompanying public wrapper or concurrent program rather than called directly by customer code. Its role is to populate and maintain the staging records that describe which application objects (such as marketing objects, campaigns, or metadata definitions) are to be exported out of the EBS environment for transport to another instance or for backup purposes.

The package is classified as a PVT API, meaning it encapsulates the persistence logic behind the export scheduling interface. It is a leaf-level dependency in the Oracle EBS dependency graph: the ETRM metadata confirms that AMS_ADI_OBJECTS_EXPORT_PVT is not referenced by any other database object, so it is invoked only from the interface layer, not from other PL/SQL packages.

Key Procedures and Functions

The documented package exposes one program unit:

  • INSERT_EXPORT_SCHEDULES — Inserts the export schedule rows that drive the object export process. This procedure is responsible for recording, in the export list table, the set of objects selected for export along with their scheduling attributes. It represents the write-path of the package: the marketing administrator or concurrent program supplies the object selection context, and INSERT_EXPORT_SCHEDULES persists the corresponding schedule entries so that the export engine can later process them.

The procedure is not documented as returning a value, and no parameter list is published in the ETRM metadata; it should therefore be treated as an internal routine whose signature is not part of a supported public contract.

Tables Accessed

All table access is made through APPS synonyms and the following objects are documented:

  • AMS_ADI_OBJECTS_EXPORT_LIST — The primary export list header/line table. INSERT_EXPORT_SCHEDULES writes the schedule records here, establishing which objects are queued for export.
  • AMS_ADI_OBJECTS_EXPORT_LIST_S — The sequence-backed or "_S" companion table for the export list. This is the object most closely associated with the user's search term, ams_adi_objects_export_list_s, and is used by the package to derive identifiers for new export list rows.
  • DUAL — Used for scalar evaluation and single-row PL/SQL constructs.
  • PLITBLM — A standard Oracle-supplied PL/SQL table type (index-by table of VARCHAR2) used for in-memory collections within the package body.

The package also depends on FND_API and FND_GLOBAL, confirming that it uses the standard EBS API error-handling stack (fnd_api.g_exc_error, fnd_msg_pub) and obtains session context such as user ID, responsibility ID, and login ID through FND_GLOBAL. The JTF_NUMBER_TABLE type is referenced, indicating that numeric arrays are passed or manipulated internally.

Usage Notes

Because AMS_ADI_OBJECTS_EXPORT_PVT is a private package with zero inbound dependencies, it is not intended for direct invocation from customer forms, reports, or custom PL/SQL. It is invoked by the Oracle Marketing export infrastructure — typically through a concurrent program or an internal public wrapper — when an administrator defines an export schedule for a set of application objects. Within the call, INSERT_EXPORT_SCHEDULES performs the staging insert and relies on FND_API exception handling to signal success or failure back to the calling layer.

In releases 12.1.1 and 12.2.2 the package remains VALID in the APPS schema. Customizations should never modify this body; instead, integrators should use the supported public interface or the concurrent program that fronts it. Any tuning or troubleshooting of export schedule failures should focus on the AMS_ADI_OBJECTS_EXPORT_LIST and ..._LIST_S tables, since those are the persistence points the procedure writes to.