Search Results get_formattedoutput




Overview

DPP_NOTIFICATION_PVT is a private PL/SQL package in the APPS schema that supports the notification and message-formatting infrastructure of Oracle E-Business Suite. The PVT suffix identifies the package as a private API, meaning it is intended for internal use by other Oracle-supplied components rather than as a public integration interface for customer extensions. Its metadata classifies it under the PVT API classification, and its declared status is VALID in the ETRM repository.

The package's principal business function is to construct formatted notification output and resolve the correct translated message text for notifications generated within the DPP (Oracle Demand Planning / supply chain planning) notification framework. It bridges stored notification content, language-specific message text, and the final formatted payload delivered to users or downstream processes. Because it depends on FND_API, it participates in the standard Oracle Application Object Library conventions for API error handling and return status.

Key Procedures and Functions

  • CREATE_FORMATTEDOUTPUT — Produces the formatted output payload for a notification. This routine assembles notification content into the structure required for delivery, working in conjunction with the stored notification data.
  • SELECT_MESSAGE_TEXT — Retrieves message text, resolving the appropriate language-specific content. It reads from FND_LANGUAGES to honor the session or notification language, ensuring the correct translated message is selected.
  • GET_FORMATTEDOUTPUT — Returns the already-formatted output to the calling program. This is the retrieval counterpart to CREATE_FORMATTEDOUTPUT, allowing callers such as DPP_BPEL_GETTRANSLATEDMESSAGE to obtain the formatted result.

The ETRM metadata documents three procedures/functions in total. The presence of both a creation routine and a retrieval routine indicates a two-stage design: output is first constructed and persisted, then retrieved by the consuming component. Parameter lists are not documented in the available metadata and should be confirmed by inspecting the package specification in the target instance.

Tables Accessed

  • DPP_NOTIFICATION_BLOBS — Stores notification content in binary large object form, including the raw or formatted notification payloads created and retrieved by this package.
  • FND_LANGUAGES — The Oracle Application Object Library table of installed languages. It is used to resolve the correct language context when selecting message text.
  • PLITBLM — An Oracle-supplied PL/SQL table type used internally for message and text handling.

Access to these objects is performed through APPS synonyms, consistent with standard EBS coding practice.

Usage Notes

DPP_NOTIFICATION_PVT is invoked indirectly. Its documented inbound dependency is DPP_BPEL_GETTRANSLATEDMESSAGE, a wrapper that exposes translated notification messages to BPEL-based orchestration flows. That package in turn is referenced by DPP_BPEL_GETTRANSLATEDMESSAGE procedures, confirming that the notification-formatting path is driven by planning and BPEL integration processing rather than by direct user invocation.

Because the package is classified as PVT, it should not be called from custom forms, concurrent programs, or bespoke code. Customizations that require notification message formatting or translation should use supported public APIs or the BPEL-facing wrapper. Any modification to this package risks affecting notification delivery across the DPP planning modules.