Search Results ams_scheduler_b_pkg
Overview
AMS_SCHEDULER_B_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Marketing (AMS) application family and operates as a low-level database access layer for the AMS_SCHEDULER entity. The object is classified under the generic API category OTHER, meaning it is not published as a formal public API but instead functions as an internal persistence package that supports the marketing scheduling infrastructure.
The package encapsulates the standard CRUD operations required to maintain rows in the AMS_SCHEDULER table. By isolating insert, update, delete, and locking logic in a single package, Oracle Marketing ensures consistent handling of scheduler records across the forms, concurrent programs, and PL/SQL routines that manipulate campaign and marketing activity schedules. Its status is VALID in the documented environments, confirming that it is a supported, compiled component of the EBS data dictionary.
Key Procedures and Functions
The ETRM metadata documents four procedures within AMS_SCHEDULER_B_PKG. Each corresponds to a conventional row-level persistence operation:
- INSERT_ROW — Creates a new row in the AMS_SCHEDULER table, populating the entity with the values supplied by the calling program.
- UPDATE_ROW — Modifies an existing AMS_SCHEDULER row, applying changed attribute values to the record identified by the caller.
- DELETE_ROW — Removes the specified AMS_SCHEDULER row from the table.
- LOCK_ROW — Acquires a row-level lock on the target scheduler record, typically used to prevent concurrent modification during an update or delete sequence.
No parameter lists are published in the supplied metadata, and none are inferred here. The procedures follow the naming conventions typical of Oracle Forms-generated and hand-coded EBS base packages, where the "_B_PKG" suffix denotes the base table handler package for a given entity.
Tables Accessed
The package references a single documented table, AMS_SCHEDULER, accessed through an APPS synonym. This table stores the scheduling definitions that drive Oracle Marketing campaign and activity execution. INSERT_ROW, UPDATE_ROW, and DELETE_ROW write to or remove records from AMS_SCHEDULER, while LOCK_ROW performs a select-for-update style lock against it. No additional application tables are documented in the ETRM dependency listing, which reflects the package's narrow, single-entity design.
Usage Notes
AMS_SCHEDULER_B_PKG is not intended for direct invocation by end users or external integrations. It is referenced by at least one other package, AMS_SCHEDULER_PVT, which serves as the private API layer wrapping the base table operations with business logic. AMS_SCHEDULER_PVT is the more appropriate entry point for custom code that needs to manipulate scheduler data, since it applies validation and business rules before delegating to the base package.
In standard EBS operation, the package is typically invoked indirectly through Oracle Forms-based marketing setup and scheduling windows, and through concurrent programs that process marketing schedules. The presence of LOCK_ROW indicates the package participates in multi-user form transactions where row-level concurrency control is required. Developers extending Oracle Marketing should call AMS_SCHEDULER_PVT rather than the base package, and should avoid direct DML against AMS_SCHEDULER to ensure that package-level integrity checks and audit expectations are preserved.
-
PACKAGE: APPS.AMS_SCHEDULER_B_PKG
12.2.2
owner:APPS, object_type:PACKAGE, object_name:AMS_SCHEDULER_B_PKG, status:VALID,
-
PACKAGE: APPS.AMS_SCHEDULER_B_PKG
12.2.2
-
PACKAGE BODY: APPS.AMS_SCHEDULER_B_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:AMS_SCHEDULER_B_PKG, status:VALID,
-
PACKAGE: APPS.AMS_SCHEDULER_B_PKG
12.1.1
owner:APPS, object_type:PACKAGE, object_name:AMS_SCHEDULER_B_PKG, status:VALID,
-
PACKAGE: APPS.AMS_SCHEDULER_B_PKG
12.1.1
-
PACKAGE BODY: APPS.AMS_SCHEDULER_B_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:AMS_SCHEDULER_B_PKG, status:VALID,
-
PACKAGE BODY: APPS.AMS_SCHEDULER_B_PKG
12.1.1
-
PACKAGE BODY: APPS.AMS_SCHEDULER_B_PKG
12.2.2
-
SYNONYM: APPS.AMS_SCHEDULER
12.1.1
owner:APPS, object_type:SYNONYM, object_name:AMS_SCHEDULER, status:VALID,
-
SYNONYM: APPS.AMS_SCHEDULER
12.2.2
owner:APPS, object_type:SYNONYM, object_name:AMS_SCHEDULER, status:VALID,
-
PACKAGE BODY: APPS.AMS_SCHEDULER_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:AMS_SCHEDULER_PVT, status:VALID,
-
PACKAGE BODY: APPS.AMS_SCHEDULER_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:AMS_SCHEDULER_PVT, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
APPS.AMS_SCHEDULER_PVT dependencies on AMS_SCHEDULER_B_PKG
12.1.1
-
APPS.AMS_SCHEDULER_B_PKG dependencies on AMS_SCHEDULER_B_PKG
12.2.2
-
PACKAGE: APPS.AMS_UTILITY_PVT
12.2.2
owner:APPS, object_type:PACKAGE, object_name:AMS_UTILITY_PVT, status:VALID,
-
APPS.AMS_SCHEDULER_PVT dependencies on AMS_SCHEDULER_B_PKG
12.2.2
-
APPS.AMS_SCHEDULER_B_PKG dependencies on AMS_SCHEDULER_B_PKG
12.1.1
-
PACKAGE: APPS.AMS_UTILITY_PVT
12.1.1
owner:APPS, object_type:PACKAGE, object_name:AMS_UTILITY_PVT, status:VALID,
-
APPS.AMS_SCHEDULER_B_PKG dependencies on AMS_SCHEDULER
12.2.2
-
APPS.AMS_SCHEDULER_B_PKG dependencies on AMS_SCHEDULER
12.1.1
-
PACKAGE: APPS.APP_EXCEPTION
12.2.2
owner:APPS, object_type:PACKAGE, object_name:APP_EXCEPTION, status:VALID,
-
PACKAGE: APPS.APP_EXCEPTION
12.1.1
owner:APPS, object_type:PACKAGE, object_name:APP_EXCEPTION, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
PACKAGE: APPS.FND_MESSAGE
12.2.2
owner:APPS, object_type:PACKAGE, object_name:FND_MESSAGE, status:VALID,
-
PACKAGE: APPS.FND_MESSAGE
12.1.1
owner:APPS, object_type:PACKAGE, object_name:FND_MESSAGE, status:VALID,
-
PACKAGE: APPS.FND_API
12.2.2
owner:APPS, object_type:PACKAGE, object_name:FND_API, status:VALID,
-
PACKAGE: APPS.FND_API
12.1.1
owner:APPS, object_type:PACKAGE, object_name:FND_API, status:VALID,
-
PACKAGE: SYS.STANDARD
12.1.1
owner:SYS, object_type:PACKAGE, object_name:STANDARD, status:VALID,