Search Results check_camp_dates_vs_child
Overview
APPS.AMS_CAMPAIGNRULES_PVT is a private PL/SQL package within the Oracle Marketing (AMS) module of Oracle E-Business Suite. It encapsulates the business rules that govern the creation, validation, and modification of marketing campaigns and campaign schedules. The package operates as a private API layer (PVT classification), meaning its procedures are intended for internal consumption by other AMS packages rather than as a public integration interface. Its principal role is to enforce data integrity and cross-entity consistency before campaign records are committed, particularly where hierarchical relationships exist between parent and child campaigns, business units, schedules, and templates.
The metadata identifies the package as VALID in the APPS schema, documented under ETRM 12.2.2 and applicable to 12.1.1 environments, with 36 documented procedures and functions. It sits at the heart of the campaign management dependency graph, calling AMS_CAMPAIGN_PVT and FND_API while being invoked by approval, scheduling, offer, and venue-rate packages.
Key Procedures and Functions
The documented procedures cluster into distinct business-rule families:
- Campaign modification and inheritance: HANDLE_CAMP_STATUS, HANDLE_CAMP_INHERIT_FLAG, CREATE_CAMP_ASSOCIATION, UPDATE_CAMP_SOURCE_CODE, and CHECK_CAMP_UPDATE manage status transitions, inheritance of attributes from parent campaigns, associations between campaign objects, and source-code maintenance.
- Validation of campaign attributes: CHECK_CAMP_TEMPLATE_FLAG, CHECK_CAMP_MEDIA_TYPE, CHECK_CAMP_FUND_SOURCE, CHECK_CAMP_CALENDAR, and CHECK_CAMP_VERSION verify template designation, media channel selection, funding source, calendar assignment, and version integrity.
- Hierarchical consistency: CHECK_CAMP_STATUS_VS_PARENT, CHECK_CAMP_DATES_VS_PARENT, CHECK_CAMP_DATES_VS_CHILD, CHECK_BU_VS_PARENT, and CHECK_BU_VS_CHILD enforce that a child campaign's status, date range, and business unit remain compatible with its parent.
- Schedule and source-code rules: CHECK_CAMP_DATES_VS_CSCH, HANDLE_CSCH_SOURCE_CODE, CHECK_CSCH_CAMP_ID, CHECK_CSCH_DELIV_ID, and CHECK_CSCH_OFFER_ID validate campaign schedule records against campaign, delivery, and offer identifiers.
Each routine is invoked as a precondition or post-condition step within larger campaign transactions; parameter signatures are not published and must be derived from the package specification.
Tables Accessed
Through APPS synonyms, the package reads and writes core marketing tables. AMS_CAMPAIGNS_ALL_B and AMS_CAMPAIGN_SCHEDULES_B hold the primary campaign and schedule records being validated. AMS_SOURCE_CODES supports source-code updates and schedule source-code handling. AMS_USER_STATUSES_B provides the status values against which CHECK_CAMP_STATUS and status-versus-parent rules are evaluated. AMS_MEDIA_CHANNELS underpins media-type validation. AMS_OBJECT_ASSOCIATIONS and AMS_OBJECT_ATTRIBUTES store relationships and attribute values for campaign objects. AMS_ACT_ACCESS, AMS_ACT_OFFERS, AMS_EVENT_HEADERS_ALL_B, AMS_EVENT_OFFERS_ALL_B, and OZF_ACT_BUDGETS support offer, event, and budget linkage checks. DUAL is used for single-row scalar evaluations.
Usage Notes
AMS_CAMPAIGNRULES_PVT is not intended for direct invocation by customers. It is called by AMS_CAMPAIGN_PVT, AMS_APPROVAL_PVT, AMS_CAMP_SCHEDULE_PVT, AMS_SCHEDULERULES_PVT, AMS_VENUE_RATES_PVT, OZF_OFFER_PVT, and OZF_COPY_OFFER_PVT, and it references AMS_CAMPAIGN_PVT and FND_API. Consequently, campaign creation and maintenance performed through the Oracle Marketing forms, the campaign scheduling concurrent programs, or offer-copy flows will indirectly trigger these rules. Custom extensions should use the public AMS_CAMPAIGN_PVT or OZF_OFFER_PVT APIs rather than calling this private package directly, since signatures and behaviour may change across patch levels. The package is a critical dependency for any diagnostic work involving campaign validation errors, inheritance problems, or parent-child date conflicts.