Search Results edit_rule

Overview

The APPS.PON_BIZRULE_PKG package body is a PL/SQL business rule maintenance utility that forms part of the Oracle Sourcing (PON) application module within Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to manage the relationship between sourcing business rules and the document types defined in the system. Specifically, it maintains the intersection between a business rule and the set of sourcing document types to which that rule applies, persisting each association in the PON_AUC_DOCTYPE_RULES table.

The package is classified in the ETRM metadata as an "OTHER" API, indicating it is an internal support program rather than a formally published, externally supported interface. The embedded source header ($Header: PONBIZRB.pls 120.0 2005/06/01) confirms it is a long-standing component of the Sourcing foundation layer and has remained stable across the 12.1.x and 12.2.x release lines.

Rather than storing business rule attributes directly, the package is concerned with the scope of a rule: the list of auction and sourcing document types against which a rule is evaluated, displayed, or enforced. This makes it a supporting package for the Sourcing administrative configuration rather than a transactional processing component.

Key Procedures and Functions

The package exposes three procedures, all of which take a business rule identifier as their sole documented input.

• ADD_RULE — Establishes a baseline set of document type rule rows for a newly created business rule. It iterates over all document types defined in PON_AUC_DOCTYPES and inserts one default row into PON_AUC_DOCTYPE_RULES for each, initializing display, required, restricted-values, and validity flags to 'N' and leaving the fixed and default value columns null. This gives every document type latent coverage under the new rule until an administrator refines the settings.
• EDIT_RULE — Reconciles the rule-to-document-type mapping for an existing rule. It selects only those document types that do not yet have a corresponding row for the given rule (using a NOT EXISTS correlated subquery) and inserts default rows for them. This handles document types added to the system after the rule was originally created, ensuring newly introduced document types are not silently excluded from the rule.
• DELETE_RULE — Removes all PON_AUC_DOCTYPE_RULES rows associated with the specified business rule identifier, performing a full cleanup of the rule's document type associations, typically in conjunction with deletion of the parent business rule.

The ETRM metadata documents no functions and no additional parameters beyond the rule identifier.

Tables Accessed

• PON_AUC_DOCTYPES — The master list of Sourcing/Auction document types. It is read-only from this package's perspective and supplies the driving cursor for ADD_RULE and EDIT_RULE, defining the full universe of document types that must be represented for each rule.
• PON_AUC_DOCTYPE_RULES — The association (detail) table holding one row per business rule and document type combination, including flags for display, required, restricted values, and validity, plus fixed and default value columns. The package inserts into this table in ADD_RULE and EDIT_RULE and deletes from it in DELETE_RULE. Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) are populated with the value 1 and the database SYSDATE.

Usage Notes

PON_BIZRULE_PKG is an internal package: ETRM records zero other packages referencing it, and it is not classified as a public API. It is most likely invoked by the Sourcing business rule setup forms or by administrative setup code that creates, modifies, or removes business rules on behalf of an application administrator rather than an end user.

Because the procedures only accept a rule identifier and rely on SYSDATE and a hard-coded creator value of 1, they are designed for server-side setup flows rather than interactive multilanguage or multi-organization contexts. The insert statements do not initialize the concurrent program request context, so they should not be treated as a substitute for properly audited API calls.

Customizations in 12.1.1 and 12.2.2 should avoid calling this package directly where a supported business rule API exists, since the flag semantics and default population logic are managed entirely within the Sourcing framework. When troubleshooting missing document type coverage for a rule, EDIT_RULE is the procedure that repairs gaps by re-inserting absent combinations. Because it operates on the whole PON_AUC_DOCTYPES set, it should be applied deliberately to avoid unintentionally extending a rule's scope to document types that were intentionally excluded.