Search Results send_effective_date_notif

Overview

DPP_BUSINESSEVENTS_PVT is a private PL/SQL package in the APPS schema that belongs to the Oracle E-Business Suite Advanced Pricing and Trade Management (DPP) module family. Its principal business function is to generate Oracle Workflow business events and notifications associated with transaction processing in the trade management and customer claims domain. The package emits events when transaction records reach significant lifecycle milestones, when effective dates change, when transactions are cancelled, and when batch or process-level activity requires notification to downstream subscribers.

The package is classified as PVT, meaning it is a private implementation package not intended for direct customer invocation. It is referenced by three other packages, which call its event-raising procedures as internal helpers. The public package specification exposes strongly typed record and table structures that callers use to pass transaction context. Notably, the specification defines dpp_txn_hdr_rec_type, a record type carrying Transaction_Header_ID, Transaction_number, Process_code, claim_id, claim_type_flag, and claim_creation_source, and dpp_txn_line_tbl_type, defined as TABLE OF NUMBER INDEX BY BINARY_INTEGER. The latter is the object most frequently searched by developers, and it serves as the line-level identifier collection passed alongside the header record. Because it is an associative array of NUMBER indexed by BINARY_INTEGER, it is populated in PL/SQL memory and cannot be used in SQL statements or bound to database columns directly.

Key Procedures and Functions

Five documented procedures are exposed by this package:

• RAISE_BUSINESS_EVENT — The core routine. It accepts the transaction header record and the transaction line identifier table, then raises the appropriate Oracle Workflow business event for the transaction. It follows the standard EBS API convention with API version, initialization of message list, commit flag, validation level, and the standard return status, message count, and message data OUT parameters. All other procedures in the package are specialized variants of this central logic.
• RAISE_EFFECTIVE_DATE_EVENT — Raises a business event when effective date information for a transaction changes, allowing subscribers to react to date-driven pricing or eligibility modifications.
• SEND_EFFECTIVE_DATE_NOTIF — Sends a workflow notification, rather than a pure business event, in response to effective date activity. This path uses the workflow notification infrastructure directly.
• SEND_CANCEL_NOTIFICATIONS — Dispatches cancellation notifications for transactions that have been cancelled, ensuring stakeholders are informed through the workflow notification system.
• RAISE_BUSINESS_EVT_FOR_PROCESS — Raises business events at the process level, supporting batch or set-based processing scenarios rather than a single transaction.

Tables Accessed

The package reads and writes the following documented tables and objects:

• DPP_TRANSACTION_HEADERS_ALL and DPP_TRANSACTION_LINES_ALL — The primary transactional tables that supply header and line context for events.
• DPP_TRANSACTION_LINES_GT — A global temporary table used to stage line identifiers during processing.
• DPP_CUSTOMER_CLAIMS_ALL and DPP_EXECUTION_DETAILS — Claims and execution detail data referenced when claim-related attributes such as claim_id and claim_type_flag must be resolved.
• DPP_EXECUTION_DETAIL_ID_SEQ — Sequence used to generate execution detail identifiers.
• OZF_SUPP_TRD_PRFLS_ALL and OZF_SYS_PARAMETERS — Supplier trade profile and system parameter data that govern event routing and notification behavior.
• FND_USER — Resolves recipient identity for notifications.
• WF_PARAMETER_LIST_T — Workflow parameter list structure used to build event payloads.
• Utility and XML objects including DBMS_UTILITY, DBMS_XMLQUERY, XMLTYPE, PLITBLM, and DUAL support payload construction and diagnostic routines.

Usage Notes

DPP_BUSINESSEVENTS_PVT is not called directly by end users. It is invoked internally by the three referencing packages, typically during transaction creation, update, cancellation, and effective date maintenance flows within the Advanced Pricing and Trade Management modules. Because the API follows the standard EBS PL/SQL API contract, callers must supply p_api_version and inspect x_return_status for FND_API.G_RET_STS_SUCCESS before proceeding, and must call FND_MSG_PUB to retrieve messages when x_msg_count exceeds one. The dpp_txn_line_tbl_type parameter must be populated as a PL/SQL associative array before invocation; because it is INDEX BY BINARY_INTEGER it cannot be sourced from a SQL query and must be built in a loop or through bulk collection into an intermediate structure. Custom code should never call this PVT package directly, since its signature and internal behavior are subject to change without notice between 12.1.1 and 12.2.2; supported integration should target the corresponding public APIs or the workflow business event subscription layer instead.