Search Results transactions_exist

Overview

PO_LINE_TYPES_SV is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. It serves as a server-side validation and inquiry utility for purchasing line types within the Oracle Purchasing module. Line types in Oracle Purchasing define the behavioral and accounting characteristics applied to a purchase order or requisition line, governing attributes such as whether the line is goods-based, service-based, outside processing related, or rate-based. The package encapsulates the business rules that determine the applicability and status of these line types across transactional and setup contexts.

The object is documented with an ETRM API classification of OTHER, indicating that it is not published as a formal public API but is nonetheless relied upon internally by Oracle Purchasing forms, concurrent processes, and dependent packages. Its status is VALID, confirming that the compiled body is present and usable in the 12.1.1 and 12.2.2 environments. The package body depends on several core Purchasing and Inventory tables, and it is itself referenced by six other database objects, underscoring its role as a shared utility within the purchasing codebase.

Key Procedures and Functions

The package exposes eleven documented procedures and functions. The following are explicitly identified in the metadata:

• NAMES — A procedure that retrieves or populates the collection of line type names available for a given context, supporting lookups and validation of valid line type designations.
• NAME — A function that returns the display name associated with a specific line type identifier, enabling forms and reports to render user-friendly line type labels.
• GET_LINE_TYPE_DEF — Retrieves the definition and attribute set of a specified line type, allowing callers to inspect the characteristics that drive downstream purchasing behavior.
• OUTSIDE_PROCESSING_ITEMS_EXIST — A function that determines whether any items associated with outside processing exist for the given line or transactional context.
• IS_OUTSIDE_PROCESSING_ITEM — A function that evaluates whether a particular item qualifies as an outside processing item, based on item and line type attributes.
• IS_OUTSIDE_PROCESSING — A function that determines whether a given line type or line is classified for outside processing processing.
• TRANSACTIONS_EXIST — A function that checks for the existence of purchasing transactions referencing a line type, used to prevent modification or deletion of line types that are already in use.

These routines collectively support validation, inquiry, and referential-integrity checks across the line type domain.

Tables Accessed

The package reads from and references the following documented tables, accessed through APPS synonyms:

• PO_LINE_TYPES and PO_LINE_TYPES_B — The base and translation tables that store line type definitions and their descriptive names, used to resolve definitions and display names.
• PO_LINES_ALL and PO_LINES_ARCHIVE_ALL — Purchase order lines and their archived counterparts, used to determine whether transactions exist against a line type.
• PO_REQUISITION_LINES_ALL — Requisition lines, consulted for the same existence and usage checks.
• MTL_SYSTEM_ITEMS — Inventory item master, used to evaluate item-level outside processing attributes.
• DUAL — The standard single-row utility table, used for scalar evaluations.

Additional dependencies include the PON_SOURCING_API_GRP group and the PO_MESSAGE_S message repository, indicating integration with sourcing logic and standardized error messaging.

Usage Notes

PO_LINE_TYPES_SV is typically invoked indirectly. Oracle Purchasing forms—such as the Purchase Orders and Requisitions windows—call these routines to populate line type list of values, validate user selections, and enforce outside processing rules. Concurrent programs that process or migrate purchasing data may call TRANSACTIONS_EXIST to guard against invalid modifications. Custom extensions and dependent Oracle packages referenced the body in six documented cases, making it a stable internal utility. Because the package is classified as OTHER rather than a formal API, direct custom invocation should be undertaken cautiously, and any dependence on its behavior should be validated against the specific 12.1.1 or 12.2.2 patch level in use.