Search Results convert_evnt_currency
Overview
AMS_EVHRULES_PVT is a private PL/SQL package in the APPS schema that encapsulates the business rules governing Oracle Marketing event headers and event offers. In Oracle EBS 12.1.1 and 12.2.2, the _PVT suffix classifies this package as an internal API layer: it is not intended to be called directly by external integrators, but instead provides the procedural engine consumed by the public-facing Marketing APIs and user interfaces. Its role is to validate, transform, and persist changes to event header records, enforce status transitions, evaluate funding source and calendar prerequisites, propagate source-code and currency values across related entities, and manage the lifecycle of rolled-up and executed events.
The package depends on AMS_EVENTHEADER_PVT, FND_API, JTF_FM_REQUEST_GRP, and STANDARD, confirming that it participates in the standard EBS API framework and the Marketing Foundation request-group infrastructure. It is itself referenced by AMS_APPROVAL_PVT, AMS_CAMPAIGNRULES_PVT, AMS_EVENTHEADER_PVT, AMS_EVENTOFFER_PVT, AMS_SCHEDULERULES_PVT, and recursively by itself, placing it at the center of the Marketing event rule architecture.
Key Procedures and Functions
The documented interface exposes 28 procedures and functions. They can be grouped by responsibility:
- Status and header maintenance: UPDATE_EVENT_HEADER_STATUS, UPDATE_EVENT_STATUS, HANDLE_EVH_STATUS, UPDATE_EVENT_SCHEDULE_STATUS, and UPDATE_OWNER modify the state and ownership attributes of event header, event, and schedule records.
- Validation routines: CHECK_EVH_UPDATE, CHECK_EVH_FUND_SOURCE, and CHECK_EVH_CALENDAR verify that an update is permitted and that required funding-source and calendar conditions are satisfied before a change proceeds.
- Source-code propagation: PUSH_SOURCE_CODE, UPDATE_EVH_SOURCE_CODE, UPDATE_EVO_SOURCE_CODE, and UPDATE_EONE_SOURCE_CODE transfer source-code values between event headers, event offers, and related entities.
- Lead processing: PROCESS_LEADS and INSERT_LEAD_REC create and manage lead records derived from event activity.
- Communication and currency: SEND_OUT_INFORMATION and CONVERT_EVNT_CURRENCY handle outbound information delivery and event currency conversion.
- Access and listing: ADD_UPDATE_ACCESS_RECORD and CREATE_LIST manage access-control rows and list creation.
- Event lifecycle: CANCEL_ROLLUPEVENT and CANCEL_EXEC_EVENT terminate rollup and executed events.
Tables Accessed
The package reads and writes a defined set of APPS-synonym tables. Event configuration data resides in AMS_EVENT_HEADERS_ALL_B, AMS_EVENT_OFFERS_ALL_B, AMS_EVENT_REGISTRATIONS, AMS_CAMPAIGN_SCHEDULES_B, and AMS_CAMPAIGNS_ALL_B. Source codes are maintained in AMS_SOURCE_CODES and access-control records in AMS_ACT_ACCESS. Budget validation draws on OZF_ACT_BUDGETS. Party and relationship data come from HZ_PARTIES, HZ_PARTY_SITES, and HZ_RELATIONSHIPS. Interface and staging activity uses AS_IMPORT_INTERFACE, AS_IMPORT_INTERFACE_S, and AS_SL_IMP_BATCH_S, while DUAL supports scalar evaluations.
Usage Notes
Because AMS_EVHRULES_PVT is a private package, it is invoked indirectly. Marketing forms and the public AMS event APIs route calls through AMS_EVENTHEADER_PVT and the other referencing packages rather than calling AMS_EVHRULES_PVT directly. It may also be exercised from concurrent programs and scheduler processes that advance event status, convert currency, or process leads. Custom code should call the public Marketing APIs instead of this package; direct invocation bypasses the intended encapsulation and risks incompatibility across patches. In 12.2.2 the package remains VALID, and its placement in the dependency chain confirms it is a stable internal component of the event rules layer.