Search Results update_process_setup

Overview

OZF_PROCESS_SETUP_PVT is a private PL/SQL package in the Oracle E-Business Suite APPS schema that supports the Order Capture and Trade Management (formerly ETRM) foundation. It encapsulates the business logic used to create, maintain, and validate the process setup records that drive automated trade management processing. Process setup records define the individual processes, such as accrual, claim, or settlement processing steps, that the application can execute, along with their enablement and automation flags. The package belongs to the PVT API classification, meaning it is an internal implementation package rather than a public, supported API. As such, it is not intended to be called directly by external or customer-written code; it is instead consumed by other packages in the same product family. The header comments confirm the package was originally created on 09-OCT-2003 and last updated in the 120.2 revision dated 2008/07/03. It also defines a package-level record type, process_setup_rec_type, and a global constant G_DEFAULT_NUM_REC_FETCH set to 30, which controls the default number of records fetched per call for bulk retrieval operations.

Key Procedures and Functions

The documented API exposes six procedures and functions:

• CREATE_PROCESS_SETUP — Inserts a new process setup record into the underlying table, populating the standard WHO columns, the process code, the enablement flag, the automatic flag, and any descriptive flexfield attributes.
• UPDATE_PROCESS_SETUP — Modifies the attributes of an existing process setup record identified by its primary key.
• UPDATE_PROCESS_SETUP_TBL — Performs update processing across a set or table of process setup rows, supporting bulk maintenance rather than single-row changes.
• CHECK_UNIQ_PROCESS_SETUP — Enforces uniqueness of the process setup definition, typically by validating that a combination of process code and related profile or org context does not already exist.
• VALIDATE_PROCESS_SETUP_REC — Validates a single in-memory process setup record structure prior to persistence, ensuring mandatory and referential integrity constraints are satisfied.
• VALIDATE_PROCESS_SETUP — Performs validation of a process setup by identifier, querying the database to confirm the record exists and is in a valid state.

Tables Accessed

The package operates against the following objects through APPS synonyms:

• OZF_PROCESS_SETUP_ALL — The primary transactional table holding process setup definitions; read and written by the create and update routines.
• OZF_PROCESS_SETUP_ALL_S — The corresponding sequence used to generate primary key values for new process setup records.
• OZF_SYS_PARAMETERS — Read to retrieve system-level configuration or default values that influence process setup behavior.
• DUAL — Used for singleton queries such as sequence value retrieval or simple existence checks.
• PLITBLM — The standard PL/SQL index-by table used for bulk processing and array handling.

In addition to these, the record structure references SUPP_TRADE_PROFILE_ID and ORG_ID, indicating that process setup is scoped by operating unit and supplier trade profile, supporting multi-org and supplier-specific configuration.

Usage Notes

Because OZF_PROCESS_SETUP_PVT is a PVT-classified package, it should not be invoked directly from custom code, forms personalizations, or concurrent programs. It is referenced by two other packages within the Trade Management schema, which act as the supported entry points for maintaining process setup data. Administrators and implementers configure process setup through the standard Order Capture/Trade Management setup windows; those form-level actions ultimately call the public wrapper packages that delegate to the routines in this private package. Understanding this package is primarily useful for debugging, extending, or diagnosing how trade management processes such as automatic accrual or claim generation are enabled and automated, since the ENABLED_FLAG and AUTOMATIC_FLAG columns it manages directly govern whether those processes run and whether they execute automatically.