Search Results create_process_setup

Overview

OZF_PROCESS_SETUP_PVT is a private (PVT) PL/SQL package owned by APPS within the Oracle E-Business Suite Trade Management (formerly Oracle Trade Management / ETRM) module. It encapsulates the business logic required to maintain process setup records, which govern the configuration of automated process flows tied to supplier trade profiles. Process setups determine which processes are enabled or disabled, whether they execute automatically, and how they relate to a given supplemental trade profile, via the OZF_PROCESS_SETUP_ALL entity. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking schema rather than the definer. Its source header (ozfvpses.pls, version 120.2, dated 2008) indicates the package has been stable since the 11i/R12 lineage and remains unchanged in the 12.1.1 and 12.2.2 releases except for underlying table and synonym support. As a private API, it is not part of the public integration surface; it is intended to be called from within the Trade Management application layer, typically from concurrent programs, other PL/SQL packages (it is referenced by two other packages), or the forms-based UI layer that manages trade profile and process configuration.

Key Procedures and Functions

The package exposes six documented subprograms, all designed around CRUD and validation logic for process setup records:

• CREATE_PROCESS_SETUP — Inserts a new process setup record using the process_setup_rec_type record structure, populating the surrogate key, descriptive attributes, and standard WHO columns.
• UPDATE_PROCESS_SETUP — Modifies an existing process setup record identified by its primary key, applying changed attributes such as ENABLED_FLAG or AUTOMATIC_FLAG.
• UPDATE_PROCESS_SETUP_TBL — Performs a bulk (table-based) update of process setup records, typically iterating over a PL/SQL table of records for set-based maintenance.
• CHECK_UNIQ_PROCESS_SETUP — Verifies uniqueness constraints on the process setup key attributes (for example PROCESS_CODE combined with SUPP_TRADE_PROFILE_ID or ORG_ID) prior to insert or update.
• VALIDATE_PROCESS_SETUP_REC — Validates an in-memory process_setup_rec_type record structure, checking required fields and referential integrity before persistence.
• VALIDATE_PROCESS_SETUP — Validates an existing persisted process setup record, confirming it satisfies business rules for the supplied identifiers.

The package also declares a record type, process_setup_rec_type, mirroring the columns of OZF_PROCESS_SETUP_ALL, and a module constant G_DEFAULT_NUM_REC_FETCH set to 30, controlling fetch batch size.

Tables Accessed

• OZF_PROCESS_SETUP_ALL — The primary transactional table holding process setup definitions, including PROCESS_SETUP_ID, SUPP_TRADE_PROFILE_ID, PROCESS_CODE, ENABLED_FLAG, and AUTOMATIC_FLAG.
• OZF_PROCESS_SETUP_ALL_S — The sequence used to generate the PROCESS_SETUP_ID surrogate key during inserts.
• OZF_SYS_PARAMETERS — System parameter store consulted for configuration defaults and validation thresholds.
• DUAL — Used for single-row lookups and PL/SQL-embedded SQL validation checks.
• PLITBLM — The standard Oracle Applications PL/SQL table type, used to pass sets of records into bulk operations such as UPDATE_PROCESS_SETUP_TBL.

Usage Notes

Because OZF_PROCESS_SETUP_PVT is a PVT package, it is not documented for direct customer extension and should be treated as an internal implementation detail. In practice it is invoked by the Trade Management application's process configuration flows — for example, when an administrator enables or disables an automated trade process against a supplier trade profile through the forms UI, or when a seeded concurrent program refreshes process setup defaults. Customizations that need to manipulate process setups should prefer the public API surface (such as OZF_PROCESS_SETUP_PUB, if available) where one exists, since private packages are subject to change without notice between 12.1.1 and 12.2.2. When calling it directly for diagnostics, supply a properly populated process_setup_rec_type, invoke VALIDATE_PROCESS_SETUP_REC before CREATE_PROCESS_SETUP or UPDATE_PROCESS_SETUP, and handle the standard Oracle Applications WHO columns and object version number to avoid lost-update conditions.