Search Results check_creation_sign

Overview

ARP_NON_DB_PKG is a non-database PL/SQL package owned by the APPS schema in Oracle E-Business Suite Releases 12.1.1 and 12.2.2. As its name indicates, the package performs business-rule validation and calculation logic without directly persisting data; it contains no DML against application tables and is classified as an OTHER API in the ETRM repository. The package resides in the Oracle Receivables (AR) module and supports the validation layer used during payment and receipt application processing. Its central responsibility is to evaluate the conditions under which a payment or receipt may be applied to a transaction, including natural application constraints, overapplication rules, and sign conventions. The package is referenced by six other packages within the Oracle Receivables schema, which indicates that it functions as a shared validation utility rather than a standalone user-facing component. The most recent version stamp in the source header dates to 2003, reflecting the maturity and long-term stability of this logic across successive EBS releases.

Key Procedures and Functions

The documented metadata lists two public procedures, both of which carry overloaded signatures defined in the package specification:

• CHECK_NATURAL_APPLICATION — The primary validation routine. It evaluates whether a proposed application logic set satisfies the natural application rules. The procedure accepts parameters describing the creation sign, the overapplication allowance flag, the natural-application-only flag, the sign of the payment schedule, and a flag controlling overapplication checks when the amount is zero. It also receives the payment amount, discount taken, remaining amount due, and original amount due. Two overloaded forms exist: one accepts an event parameter for diagnostic context, while the other additionally returns a message name through an OUT NOCOPY parameter, allowing callers to retrieve a descriptive validation message. A p_lockbox_record Boolean flag allows lockbox-originated records to be handled under distinct rules.
• CHECK_CREATION_SIGN — A supporting validation routine that verifies the sign convention applied to a transaction at creation time. It accepts the creation sign, the monetary amount to be evaluated, and an optional event identifier. As with the preceding procedure, an overloaded variant returns a message name through an OUT NOCOPY parameter so the caller can surface a specific error or warning to the user.

Tables Accessed

The ETRM metadata records no table references for ARP_NON_DB_PKG. This is consistent with its designation as a non-database package: all validation inputs are supplied as parameters by the calling program unit, and the package performs no direct SQL operations against Receivables base tables or APPS synonyms. Data retrieval and persistence remain the responsibility of the invoking packages, which supply amounts, flags, and sign information as bind arguments.

Usage Notes

ARP_NON_DB_PKG is invoked internally by other Oracle Receivables packages rather than directly by end users. Because it exposes no database state of its own, callers use it as a deterministic rule engine: given a set of application parameters, the procedures return a pass/fail determination or a message name identifying the violated rule. The overload returning a message name is intended for callers that need to present a translated error to the user interface, while the simpler overload supports internal short-circuit validation where only a boolean outcome is required. The event parameter permits diagnostic tracing of which validation stage triggered a result, and the lockbox flag accommodates the specialized application rules applied to automatic lockbox receipt processing. Customizations that emulate or extend standard Receivables application logic should call these procedures rather than replicating the rules, ensuring consistency with standard overapplication and natural-application behavior across 12.1.1 and 12.2.2 environments.