Search Results rosetta_g_miss_date_in_map

Overview

The APPS.AMS_TRIG_PVT_W package body is a generated PL/SQL wrapper (indicated by the _W suffix and the amswtrgb.pls source revision) that exposes the private business logic for Oracle Marketing Online triggers. Triggers in Oracle EBS are user-defined event handlers that fire when a marketing activity, campaign, or related object is created, updated, or deleted. This wrapper translates inbound JDBC-style parameter values into the sentinel conventions expected by the underlying private package AMS_TRIG_PVT.

The visible source confirms the package was last modified in July 2003 (115.13) and contains the standard Rosetta-generated "miss date" workaround. Lines 3–4 define two boundary dates: rosetta_g_mistake_date (01/01/+4713) and rosetta_g_miss_date (01/01/-4712). The function rosetta_g_miss_date_in_map at lines 7–11 detects the JDBC bug that transmits the Java Date.GMiss sentinel as a real date, and converts it back to fnd_api.g_miss_date. A parallel helper, rosetta_g_miss_num_map, maps g_miss_num to and from the numeric sentinel -1962.0724. These mappers correspond directly to the user's search term. The CREATE_TRIGGER signature at line 22 shows the generic p7_a parameter convention used by Rosetta wrappers, where DATE and NUMBER arguments default to these sentinel values.

Key Procedures and Functions

The ETRM metadata documents eight callable units in this wrapper:

• CREATE_TRIGGER — Creates a new marketing trigger record. It accepts the standard API version, initialization, commit, and validation parameters plus the trigger attribute arguments, returning the newly generated trigger identifier.
• UPDATE_TRIGGER — Modifies an existing trigger record identified by its trigger identifier.
• VALIDATE_TRIGGER — Performs validation of trigger data without persisting changes.
• CHECK_TRIG_ITEMS — Validates the item/attribute level content of a trigger.
• CHECK_TRIG_RECORD — Validates the trigger header record against business rules.
• CHECK_TRIG_REQ_ITEMS — Verifies that mandatory trigger items are present.
• INIT_TRIG_REC — Initializes the trigger record structure with default values prior to processing.
• COMPLETE_TRIG_REC — Finalizes or completes the trigger record, generally after all items have been populated.

All procedures return the standard x_return_status, x_msg_count, and x_msg_data out parameters, consistent with the Oracle Application Object Library API standard.

Tables Accessed

The provided ETRM extraction does not enumerate the APPS synonyms and underlying base tables referenced by this wrapper. Based on the Oracle Marketing data model, trigger definitions are held in the AMS_TRIGGERS and AMS_TRIGGER_ITEMS tables, and the wrapper delegates all physical reads and writes to those objects through the private AMS_TRIG_PVT package. Consumers performing impact analysis should confirm actual dependencies by querying USER_DEPENDENCIES for AMS_TRIG_PVT_W in the APPS schema.

Usage Notes

This wrapper is not intended for direct invocation by end users. It is called programmatically:

• By the Rosetta-generated Java/JDBC layer of Oracle Marketing Online, which is why the rosetta_g_miss_date_in_map and rosetta_g_miss_num_map functions exist.
• By Oracle Forms-based marketing setup screens that create and maintain triggers.
• By custom integration code that requires the standard fnd_api return status convention.

Because the file header dates from 2003 and is shared between 12.1.1 and 12.2.2, the API surface is stable across releases. The ETRM metadata records zero packages referencing this object, indicating it is a top-level entry point rather than an internal helper. Developers extending trigger functionality should call AMS_TRIG_PVT_W rather than the private package to preserve sentinel handling and the JDBC workaround.