Search Results get_counter




Overview
Explore in AI Chat

Overview

OE_MASS_CHANGE_PVT is a private PL/SQL package in the APPS schema that implements the core processing engine for mass change operations against Oracle Order Management sales orders. Mass change in Oracle EBS Order Management allows users to apply attribute updates — for example, changing a payment term, warehouse, or requested ship date — across many order lines simultaneously rather than editing each line individually. The package belongs to the PVT (private) API classification, meaning it is intended for internal consumption by other Oracle EBS modules, such as the Order Organizer and the mass change scheduling infrastructure, rather than as a public extension point for customer code.

The object is documented as VALID in ETRM for both 12.1.1 and 12.2.2, and it references the standard EBS API framework package FND_API, which provides the shared error-handling, message-stack, and savepoint conventions used throughout the application. It also depends on OE_GLOBALS for global Order Management constants and context values.

Key Procedures and Functions

The package exposes eleven documented procedures and functions, organized around record-by-record processing and transaction control:

  • PROCESS_ORDER_SCALAR — Applies mass change processing at the order header level, operating on a single order record supplied as scalar values.
  • PROCESS_LINE_SCALAR — Applies mass change processing to an individual order line, using scalar inputs rather than a record structure.
  • LINES_REMAINING — Determines whether additional order lines remain to be processed in the current mass change run, supporting iterative driver logic.
  • SAVE_MESSAGES — Persists accumulated API messages, allowing errors and warnings generated during processing to be retained for later retrieval.
  • INSERT_MESSAGE — Records an individual message into the message stack used by the mass change process.
  • MC_ROLLBACK — Rolls back the current mass change transaction, typically invoked when validation or processing fails.
  • SET_COUNTER and GET_COUNTER — Set and retrieve an internal counter used to track processing progress across a mass change run.
  • SET_ERROR_COUNT and GET_ERROR_COUNT — Maintain and expose the number of errors encountered, enabling callers to decide whether to continue or abort.
  • GET_SEL_REC_TBL — Returns the selected record table, giving callers access to the set of records selected for mass change.

Tables Accessed

The package operates against two documented tables exposed through APPS synonyms:

  • OE_ORDER_LINES_ALL — The base table for sales order lines. Mass change processing reads the selected lines and writes updated attribute values back to this table, making it the primary target of the change operation.
  • PLITBLM — The standard EBS PL/SQL message table used by the API message framework. Message rows inserted by INSERT_MESSAGE and SAVE_MESSAGES are stored here so that they can be retrieved and displayed by the calling application.

Usage Notes

OE_MASS_CHANGE_PVT is not a public API and is not intended for direct invocation by customer extensions. It is referenced by six other packages, including OE_CONFIG_SCHEDULE_PVT, OE_DELAYED_REQUESTS_PVT, OE_ORDER_ADJ_PVT, OE_ORDER_PRICE_PVT, OE_SCHEDULE_UTIL, and OE_OE_FORM_HEADER, as well as by itself recursively. This dependency pattern indicates that the Order Management forms and the scheduled mass change concurrent processing framework call the package to apply changes, with OE_CONFIG_SCHEDULE_PVT and OE_DELAYED_REQUESTS_PVT handling deferred or background execution. Its use of FND_API confirms adherence to the standard EBS API error-handling model, so messages accumulated during a run are surfaced through the standard message stack. Because the package manages its own counters and rollback behavior, callers should treat a mass change run as a single logical transaction governed by MC_ROLLBACK and the error counters.