Search Results validate_ptaoe

Overview

APPS.PSP_POA_BUS is the business-layer PL/SQL package body that governs the maintenance of organization account records within the Oracle E-Business Suite Payables and Payments product family. The package encapsulates the core business logic and validation rules applied to rows in the PSP_ORGANIZATION_ACCOUNTS entity, providing a controlled, reusable interface for inserting, updating, and deleting organization account definitions while enforcing security-group and legislation context derived from the associated business group. It is classified in the ETRM repository as an "OTHER" API rather than a fully published public interface, and it forms part of the internal foundation used by higher-level PSP modules. The header indicates a no-ship source status with a creation/amendment lineage dating to 2006, reflecting its role as stable, mature infrastructure in both 12.1.1 and 12.2.2 releases. The package also exposes a utility routine for resolving the legislation code associated with an organization account, and a security-group resolution routine that establishes the operating context for all subsequent DML operations.

Key Procedures and Functions

The package exposes five documented procedures and functions that together implement its business logic:

• SET_SECURITY_GROUP_ID — Resolves and caches the security group identifier and legislation code for a given organization account by joining the performance business-group view to PSP_ORGANIZATION_ACCOUNTS. It validates that the mandatory organization account identifier is supplied before performing the lookup.
• RETURN_LEGISLATION_CODE — Returns the legislation code previously determined for the organization account context. It relies on the private global variables maintained by the package, which are documented as being used exclusively by this function.
• INSERT_VALIDATE — Validates the data attributes supplied when creating a new organization account record, applying the mandatory-argument and business-rule checks required before the row is persisted.
• UPDATE_VALIDATE — Validates attribute changes applied to an existing organization account record, ensuring referential and business integrity before the update is committed.
• DELETE_VALIDATE — Validates that an organization account record may be safely removed, applying the deletion constraints enforced by the business layer.

The validate routines intentionally separate validation from the physical DML, allowing calling modules to enforce rules consistently and to raise standardized HR-style API errors through the shared HR_API and HR_UTILITY infrastructure.

Tables Accessed

The documented table references, resolved through APPS synonyms, are:

• PSP_ORGANIZATION_ACCOUNTS — The primary entity managed by this package; insert, update, and delete validation all address attributes of this table, and the security-group cursor joins to it on ORGANIZATION_ACCOUNT_ID.
• PER_BUSINESS_GROUPS (referenced as PER_BUSINESS_GROUPS_PERF) — Used to obtain the SECURITY_GROUP_ID and LEGISLATION_CODE associated with the account's business group, establishing the multi-tenant security context.
• HR_ALL_ORGANIZATION_UNITS — Provides the organization unit definitions that underlie organization account ownership and legislation derivation.
• PA_ALL_ORGANIZATIONS — Supplies the organization hierarchy and classification data used when validating organization account associations.

Usage Notes

PSP_POA_BUS is an internal business-layer package and is not intended for direct invocation by end users. It is typically called from Oracle Forms-based maintenance screens, from other PSP packages, and from custom extensions that must create or modify organization accounts. The ETRM metadata records that the package is referenced by three other packages, confirming its role as a shared dependency. Because it is classified as "OTHER," implementers integrating custom code should call it only where the calling interface requires the same validation semantics as the standard Payables organization account maintenance flow. Direct DML against PSP_ORGANIZATION_ACCOUNTS should be avoided, as it bypasses the security-group and legislation enforcement embodied in SET_SECURITY_GROUP_ID and the validate routines. In 12.2.2 environments the package operates unchanged in concept from 12.1.1, remaining under the APPS schema with no ship-home designation.