Search Results set_message_attr




Overview
Explore in AI Chat

Overview

QA_SS_IMPORT_WF is the workflow integration package for the Supplier Scheduling (SS) import process in Oracle Quality. It provides the PL/SQL entry points that Oracle Workflow uses to drive the buyer notification and supplier-scheduling import business flow, and it exposes a set of lookup helper functions that resolve descriptive names and identifiers for use in notification message attributes. The package is owned by APPS and is compiled with AUTHID CURRENT_USER, meaning all unqualified object references execute under the privileges of the calling session. The $Header line (qltsswfb.pls 120.0.12010000.1, dated 2008/07/25) indicates the file has been stable since the 12.1 code line and is carried forward unchanged into 12.2.2.

The object the user searched for, GET_BUYER_NAME, is one of several name-resolution functions in the package. It returns a display name for a buyer given a surrogate identifier, and is typically used when building the subscription content of a buyer notification item.

Key Procedures and Functions

  • UNBLOCK — releases a blocked workflow item identified by item type and item key.
  • CHECK_COMPLETION — a standard workflow function-mode callback that evaluates whether an activity has completed and returns a result.
  • DISPATCH_NOTIFICATION — workflow callback that sends the notification associated with the current activity.
  • SET_MESSAGE_ATTR — populates the message attributes of a workflow notification for a given identifier.
  • START_BUYER_NOTIFICATION — initiates the buyer notification workflow, accepting optional buyer, source, plan, item, and PO header identifiers so the process can be scoped to a specific document or a broader activity.
  • SEND — workflow callback that transmits the notification or message.
  • CREATE_BUYER_PROCESS — returns a numeric handle for a buyer process instance, parameterised by type.
  • GET_ITEMTYPE_PROFILE — returns the item type profile value controlling which workflow definition applies.
  • GET_BUYER_NAME — returns the buyer name for a supplied identifier.
  • GET_USER_NAME — returns the FND user name for a user identifier.
  • GET_PLAN_NAME — returns the name of a Quality plan.
  • GET_ORG_ID, GET_ORG_CODE, GET_ORG_NAME — resolve organization identifier, code, and description respectively.
  • GET_ITEM — returns the item description or concatenated item value for an inventory item.
  • SET_SUPPLIER_INFO — writes supplier-related attributes onto the workflow item identified by item key and item type.
  • GET_PO_NUMBER — returns the purchase order number for a PO header identifier.

Tables Accessed

  • FND_USER — source for user names used by GET_USER_NAME and related notification attributes.
  • HR_ALL_ORGANIZATION_UNITS — source for organization code and name resolution.
  • MTL_PARAMETERS — provides the inventory organization context needed to resolve items and organizations.
  • MTL_SYSTEM_ITEMS_KFV — key flexfield view used by GET_ITEM to return the concatenated item description.
  • QA_PLANS — source of Quality plan names for GET_PLAN_NAME.
  • QA_RESULTS_INTERFACE — the interface table holding supplier-scheduling results being imported through the workflow.
  • QA_SS_NOTIFY_WORKFLOW_S — the package's own sequence, used to generate workflow item keys for new notification processes.
  • DUAL — used for single-row computations and function-mode evaluations.

Usage Notes

QA_SS_IMPORT_WF is not a general-purpose API and is not intended to be called directly from forms or ad hoc SQL. Its procedures CHECK_COMPLETION, DISPATCH_NOTIFICATION, and SEND follow the Oracle Workflow standard callback signature (item type, item key, activity id, function mode, result) and are registered as the function activities of the supplier-scheduling buyer notification workflow. START_BUYER_NOTIFICATION is the programmatic entry point used when a buyer notification needs to be launched from the import process itself.

The remaining functions exist to support notification content generation: rather than embedding SQL in the workflow message body, the workflow definition calls these helpers to translate identifiers into human-readable values such as buyer name, user name, plan name, organization, item, and PO number. The package is referenced by two other packages, confirming it is a shared utility layer for the Supplier Scheduling module rather than an isolated component. In both 12.1.1 and 12.2.2 the interface is identical; the 12.2 upgrade does not alter this object, so customisations that wrap or call these functions remain valid across the upgrade.