Results for “advance_required”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_ADVANCE_CLIENT_EXT is a public Oracle Projects client extension package owned by the APPS schema. It provides a single extensibility hook that Oracle Projects calls during transaction processing to determine whether an advance payment is required for a given customer. In Oracle EBS 12.1.1 and 12.2.2, client extensions of this type allow implementers to override seeded application logic without modifying Oracle-owned source. The package is declared with AUTHID CURRENT_USER, so it executes with the privileges of the invoking user rather than the definer. Its header carries the version marker $Header: PAAGADCS.pls 120.1 2006/11/21 05:35:33 rkchoudh noship $, indicating a long-stable interface carried forward into the 12.x releases. The documented behavior is to return a valid value for the advance required flag; when a valid value is returned, Oracle Projects uses that value instead of the application default. This makes the package the supported mechanism for customer-specific advance payment rules — for example, requiring advances only for certain customers or categories of work.

Key Procedures and Functions

The package exposes one documented procedure, ADVANCE_REQUIRED. It is the sole entry point in this extension package and is classified in the metadata as a client extension under business entity PA_PROJECT. Its stated purpose is to specify the advance required flag for the transaction being processed. The documented parameters are p_customer_id (the customer identifier supplied as input), x_advance_flag (the advance required flag returned to the caller), x_error_message (error message text), and x_status (status indicator, where zero denotes success and a non-zero value denotes an error). All out parameters are NOCOPY, consistent with Oracle Projects client extension conventions. The accompanying metadata annotation, advance_required_check, states that the extension determines whether the advance required functionality is allowed for an agreement. Implementers supply the body logic in a custom package or overriding implementation; Oracle Projects invokes the extension at the appropriate point in transaction processing and honors the returned flag when it is valid.

Tables Accessed

The ETRM metadata for this package does not list any tables referenced through APPS synonyms, and the package header contains no SQL. This is consistent with the design of client extension stubs, which are intended to be implemented by customers and are therefore not bound to a fixed data model. Source annotations reference the business entity PA_PROJECT and the documentation set 120pjapi.pdf (Oracle Projects API's, Client Extensions, and Open Interfaces Reference), but no physical tables are documented as read or written by the seeded package itself. Any table access occurs only in customer-provided implementations of ADVANCE_REQUIRED, and such access is outside the scope of the delivered metadata.

Usage Notes

This extension is invoked by Oracle Projects at the point where the advance required flag must be resolved for a transaction, replacing the default value with the value returned by the procedure. Because the package is referenced by two other packages in the APPS schema, it participates in standard Oracle Projects transaction flows rather than being called directly by end users. Customizations should be implemented with attention to the contract documented in the header: return a valid value for x_advance_flag to override the default, populate x_error_message when validation fails, and set x_status to zero on success or a non-zero value on error. The extension is classified as public scope, active lifecycle, and S (supported) compatibility, confirming it is a supported extension point in 12.1.1 and 12.2.2. It should be treated as an interface to be implemented, not as an application API invoked directly from forms or concurrent programs.