Search Results get_osp_info




Overview
Explore in AI Chat

Overview

The APPS.POS_OSP_JOB package is a small, purpose-built PL/SQL utility within Oracle E-Business Suite that supports Outside Processing (OSP) transactions tied to Work in Process (WIP) jobs. Outside Processing refers to operations in a manufacturing routing that are performed by an external supplier rather than in-house. In the Oracle EBS flow, a WIP job generates a purchase requisition and subsequently a purchase order to the outside processor, and the resulting receiver, distribution, and WIP accounting records must remain consistent. This package exists to bridge the Purchasing and Work in Process data models by resolving the relationships between a purchasing line location, its distributions, and the associated WIP entity, line, and sequence.

The package is declared as AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking user rather than the package owner. This design allows the seeded definitions to be invoked from both standard application flows and customer-written extensions without granting elevated privileges to APPS. The header identifier (POSASNWS.pls, version 115.0) indicates the package originated as part of the Purchasing application’s outside-processing feature set and has been carried forward across the 12.1.1 and 12.2.2 releases largely unchanged.

Key Procedures and Functions

The package exposes a set of seven documented functions, most of which are thin lookup routines that accept a purchasing identifier and return a single related value.

  • R_COUNT — Returns a count derived from a purchase line location, typically used to determine whether related OSP records exist before further processing.
  • GET_OSP_INFO — Returns descriptive OSP information associated with a purchase line location.
  • GET_PO_DISTRIBUTION_ID — Resolves the purchasing distribution identifier for a given purchase line location.
  • GET_WIP_ENTITY_ID — Returns the WIP entity identifier (the job or repetitive schedule) linked to the purchase line location. This is the function most often sought when mapping purchasing lines back to their originating WIP job.
  • GET_WIP_LINE_ID — Returns the WIP line identifier associated with the job.
  • GET_WIP_SEQ_NUM — Returns the WIP operation sequence number involved in the outside processing step.
  • GET_WIP_INFO — Given a distribution identifier, returns descriptive WIP information, providing the reverse lookup from distribution to job context.

Tables Accessed

The package reads from three core tables through APPS synonyms:

  • PO_DISTRIBUTIONS_ALL — The purchasing distributions table, which holds the accounting and charge information for each purchase order line and shipment. It provides the linkage between the purchasing side and the WIP job via the distribution identifier.
  • WIP_ENTITIES — The primary WIP job/schedule table, supplying the WIP entity identifier and related job attributes used by the OSP linkage.
  • WIP_LINES — The WIP operation lines table, supplying line and operation sequence details for the job’s routing.

Usage Notes

Because these functions are lightweight scalar lookups, they are typically called from forms, concurrent programs handling OSP receipt and job closure, and custom code that must reconcile purchasing and manufacturing records. Two other packages in the ETRM inventory reference POS_OSP_JOB, confirming it acts as a shared dependency rather than a top-level entry point. The most common invocation, corresponding to the search term get_wip_entity_id, occurs when a developer or report needs to determine which WIP job is associated with a particular purchase line location, for example when tracing an outside-processing receipt back to its manufacturing order. As with all APPS-seeded packages, direct calls should be treated with care across upgrades, and the read-only lookup nature of these functions means they should not be relied upon to modify transactional state.