Results for “check_csch_deliv_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AMS_CampaignRules_PVT is a private PL/SQL package body in the Oracle Marketing (AMS) module of Oracle E-Business Suite, shipped under the APPS schema. Its header comment references the source file amsvcbrb.pls (version 120.6), confirming it is one of the marketing campaign validation and maintenance libraries. The package encapsulates the business rules that govern the lifecycle of marketing campaigns, campaign programs, and campaign schedules: activation, holding, cancellation, completion, archiving, and the checking of campaign attributes against parent, child, template, budget, and calendar constraints. Because it is classified as a PVT (private) API, it is not intended for direct invocation by external integrators; it is called internally by public AMS APIs, concurrent programs, and the Campaign Workbench forms. It is referenced by seven other packages, which indicates its role as a shared rule engine rather than an entry-point API. The list of documented procedures (36 in total) is dominated by read-only validation routines, supplemented by a smaller set of status-transition and archival procedures.

Key Procedures and Functions

The documented procedures fall into three functional groups.

• Lifecycle transition procedures — Archive_Schedules and Archive_Campaigns, Activate_Campaigns, Hold_Campaigns, Cancel_Schedule, Cancel_Program, Complete_Schedule, and Complete_Program perform bulk or single-object state changes on campaign programs, campaigns, and schedules. Check_Close_Campaign and Handle_Camp_Status resolve the user-selected status into the corresponding internal system status code, consulting AMS_USER_STATUSES_B and the campaign's current system status.
• Campaign validation procedures — Check_Camp_Update, Check_Camp_Template_FLag, Check_Camp_Media_Type, Check_Camp_Fund_Source, Check_Camp_Calendar, Check_Camp_Version, Check_Camp_Status_Vs_Parent, Check_Camp_Dates_Vs_Parent, and Check_Camp_Dates_Vs_Child enforce consistency of campaign attributes, date ranges, template flags, budget sources, and versioning against the campaign hierarchy. Check_BU_Vs_Parent and Check_BU_Vs_Child perform equivalent validation for the operating unit against parent and child campaigns.
• Schedule and association procedures — Check_Camp_Dates_Vs_CSCH, Check_CSCH_Camp_ID, Check_CSCH_Deliv_ID, Check_CSCH_Offer_ID, and Handle_CSCH_Source_Code validate campaign-schedule attributes, foreign keys, and source-code inheritance. Handle_Camp_Inherit_Flag, Create_Camp_Association, Update_Camp_Source_Code, and Update_Related_Source_Code manage campaign-to-object associations and the related source code fields used for campaign attribution and tracking.

Tables Accessed

The package reads and writes the core marketing and order-capture tables through APPS synonyms.

• AMS_CAMPAIGNS_ALL_B, AMS_CAMPAIGN_SCHEDULES_B, AMS_USER_STATUSES_B — the primary campaign, schedule, and status definition tables, used for status resolution and validation.
• AMS_EVENT_HEADERS_ALL_B and AMS_EVENT_OFFERS_ALL_B — event and offer definitions against which campaign-schedule offer and delivery IDs are validated.
• AMS_ACT_ACCESS, AMS_ACT_OFFERS, OZF_ACT_BUDGETS — activity access, offers, and budget records used by Check_Camp_Fund_Source and association validation.
• AMS_MEDIA_CHANNELS, AMS_OBJECT_ASSOCIATIONS, AMS_OBJECT_ATTRIBUTES, AMS_SOURCE_CODES — media channel, association, attribute, and source-code reference data used by Handle_Camp_Media_Type, Create_Camp_Association, and the source-code update procedures.
• DUAL — used for trivial SELECT and cursor-driven status lookups.

Usage Notes

AMS_CampaignRules_PVT is invoked indirectly. The Campaign Workbench forms call public AMS APIs, which in turn delegate attribute and status validation to this package before an insert, update, or status change is committed. Concurrent programs that perform bulk activation, holding, archival, or completion of campaigns and schedules call the transition procedures on a set-based basis. The validation procedures are also invoked from custom code that must enforce the same hierarchy, date, template, and source-code rules as the seeded application. Because the package is classified PVT, direct calls from customer extensions are not supported and signatures may change between releases; integrators should use the corresponding public AMS APIs wherever possible.