Search Results get_agreement_id

Overview

APPS.PA_EVENT_CORE is the internal validation and business-rule layer of the Oracle Projects event processing architecture in Oracle E-Business Suite 12.1.1 and 12.2.2. It sits beneath the public API package PA_EVENT_PUB and its private counterpart, and is responsible for applying the domain rules that govern whether an event—the billing or revenue-generating unit of work recorded against a project—may be created, updated, or processed. The package is classified under the generic "OTHER" API category in ETRM, reflecting that it is not a published integration interface but a supporting component invoked by the higher-level event APIs.

The source header shows a build from the 12.1.1 code line (PAEVAPCB.pls 120.5.12010000.2), and the same package body continues to be shipped in 12.2.2. The dominant characteristic of PA_EVENT_CORE is its collection of boolean-style CHECK functions, each returning a flag value (typically 'Y' or 'N') that indicates whether a supplied attribute satisfies the Projects event model. When an exception occurs, the package appends its own name and the failing procedure to the PA_EVENT_PUB.PACKAGE_NAME and PA_EVENT_PUB.procedure_name globals before re-raising util_excp, so that the public layer can report the exact validation path that failed.

Key Procedures and Functions

The package exposes eighteen documented procedures and functions, almost all of them validators:

• CHECK_VALID_PROJECT — Confirms that a project number resolves to a valid contract project that is not a template, is not in purge status, and is not a provider-owned project; it returns the resolved project ID as an OUT parameter.
• CHECK_FUNDING — Determines whether funding is defined at task level while the event is being inserted at project level, returning 'N' in that inconsistent case and 'Y' otherwise.
• CHECK_VALID_TASK — Validates that a task belongs to the project and is eligible for event entry.
• CHECK_VALID_EVENT_NUM — Verifies the existence and uniqueness of the event number.
• CHECK_VALID_EVENT_TYPE — Confirms the event type is valid and active for the project.
• CHECK_VALID_EVENT_ORG — Validates the event organization against the project's owning organization.
• CHECK_VALID_CURR — Checks that the entered currency is a valid, enabled currency.
• CHECK_VALID_FUND_RATE_TYPE, CHECK_VALID_PROJ_RATE_TYPE, CHECK_VALID_PFC_RATE_TYPE — Validate the funding, project, and project funding currency rate types respectively.
• CHECK_VALID_BILL_AMT and CHECK_VALID_REV_AMT — Validate billable and revenue amounts against project and event rules.
• CHECK_EVENT_PROCESSED — Determines whether an event has already been processed and is therefore not amendable.
• CHECK_VALID_INV_ORG — Validates the invoice organization for the event's agreement and project.
• CHECK_WRITE_OFF_AMT — Validates write-off amounts within permitted tolerances.
• CHECK_VALID_INV_ITEM — Confirms the invoice item is valid for the billing context.
• CHECK_VALID_AGREEMENT — Validates that the agreement referenced by the event is active and applicable to the customer.
• CHECK_VALID_EVENT_DATE — Ensures the event date falls within the permitted project or agreement date range.

The get_agreement_id search term aligns with CHECK_VALID_AGREEMENT, which is the routine that resolves and confirms the agreement identifier associated with an event, reading from PA_AGREEMENTS_ALL and HZ_CUST_ACCOUNTS.

Tables Accessed

Validation logic draws on established Projects and Receivables base tables through APPS synonyms. PA_PROJECTS and PA_PROJECTS_ALL supply project attributes including project type class, template flag, and status. PA_EVENTS and PA_EVENT_TYPES hold the event and event-type definitions being validated. PA_SUMMARY_PROJECT_FUNDINGS supports the funding-level checks in CHECK_FUNDING. PA_AGREEMENTS_ALL and HZ_CUST_ACCOUNTS back the agreement and customer validation path relevant to agreement ID resolution. FND_CURRENCIES supports CHECK_VALID_CURR, PA_DRAFT_INVOICES_ALL and PA_DRAFT_INVOICE_ITEMS are used by the processed-event and invoice-item checks, PA_IMPLEMENTATIONS provides implementation-level settings, and DUAL is used for scalar lookups.

Usage Notes

PA_EVENT_CORE is not intended for direct invocation. It is called by PA_EVENT_PUB and PA_EVENT_PRIVATE, which are in turn referenced by the Projects event entry forms, the event import and processing concurrent programs, and by custom extensions that rely on the published event APIs. ETRM records that the package is referenced by two other packages, confirming its position as an internal dependency rather than a standalone integration point. Custom code that requires agreement-ID or event-validation logic should call the public PA_EVENT_PUB APIs, allowing PA_EVENT_CORE to perform its checks and to populate the package and procedure name globals used for error diagnostics.