Search Results okc_xprt_rule_pub

Overview

OKC_XPRT_RULE_PUB is a public PL/SQL API package owned by the APPS schema in Oracle E-Business Suite, classified as a "PUB" (public) interface within Oracle's eTRM (Enterprise Contract and Transaction Management / Contracts) module. Its business purpose is to provide a supported, version-stable entry point for creating, maintaining, and removing export/import rule definitions — the configuration records that govern how contract terms, pricing, and compliance conditions are exported, imported, or validated across contract templates and transaction documents. The "_PUB" suffix indicates Oracle's intended layering: external callers (forms, concurrent programs, and custom extensions) invoke this public wrapper rather than the underlying private implementation. In the documented dependency chain, OKC_XPRT_RULE_PUB depends on FND_API (the Oracle Application Object Library API utility layer), OKC_API (the core Contracts application API), OKC_XPRT_RULE_PVT (the private implementation package that contains the actual business logic and DML), and the SYS.STANDARD package. This architecture is typical of Oracle's public/private API convention, where OKC_XPRT_RULE_PUB performs parameter validation, initializes the FND_API global context, and delegates processing to OKC_XPRT_RULE_PVT. The package status is VALID in both Oracle EBS 12.1.1 and 12.2.2, applying to the APPS schema in each release.

Key Procedures and Functions

The documented public interface exposes three procedures:

• CREATE_RULE — Establishes a new export/import rule record. It accepts the rule definition attributes, performs standard FND_API validation (mandatory columns, lookup values, and referential checks), and inserts the new rule through OKC_XPRT_RULE_PVT. Callers receive the standard API return status and message stack.
• UPDATE_RULE — Modifies an existing rule record. This procedure applies changes to previously created rule definitions, using the same FND_API error-handling conventions and delegating the update logic to the private package.
• DELETE_RULE_CHILD_ENTITIES — Removes the dependent (child) records associated with a rule, supporting cleanup or cascading deletion. This is invoked when a parent rule is being removed or reorganized and its subordinate configuration rows must be purged to preserve data integrity.

The metadata does not document parameter signatures, so no argument lists are asserted here; developers should reference the package specification in the EBS instance for exact parameters.

Tables Accessed

The provided ETRM metadata does not enumerate physical tables accessed via APPS synonyms; all DML is abstracted behind OKC_XPRT_RULE_PVT. Based on contract-module conventions, the package operates on the OKC export/import rule and related child-entity tables (the OKC_XPRT_RULE base table and its dependent detail tables) that store rule headers, conditions, and their associated child rows. Custom code should not query or modify these tables directly but should treat them as an implementation detail surfaced only through this public API.

Usage Notes

OKC_XPRT_RULE_PUB is intended for programmatic and declarative invocation: contract configuration forms, concurrent programs that bulk-load or migrate rule definitions, and custom PL/SQL extensions that follow Oracle's public API guidelines. Callers should invoke these procedures rather than OKC_XPRT_RULE_PVT, because Oracle supports only the public layer across upgrades — the private implementation may change between 12.1.1 and 12.2.2 without notice. Standard practice includes checking the returned status, reading the FND_API message stack on failure, and committing or rolling back within the caller's transaction. No other application packages reference this package, so it functions as a leaf-level public service consumed by external clients rather than by other Oracle APIs.