Results for “delete_all_contacts”

10 results




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

Overview

APPS.PA_CUSTOMERS_CONTACTS_PVT is a private (PVT) PL/SQL package body within the Oracle Projects (PA) module of Oracle E-Business Suite, current across releases 12.1.1 and 12.2.2. It encapsulates the business logic required to maintain the association between projects and the customers and contacts that participate in them. Specifically, it provides the implementation layer for creating, updating, and deleting project-customer relationships and customer contacts, along with the validation routines that enforce data integrity before those relationships are persisted.

This package is classified as private, meaning it is not intended to be called directly by external applications. Instead, it functions as the internal engine behind a corresponding public API package, which exposes the same operations to forms, concurrent programs, and custom integrations. The private designation reflects Oracle's standard layered-API design, where the public package handles interface concerns while the private package contains the substantive transactional and validation logic. The header comment in the source identifies it as part of the PARPCCVB.pls file, with a version lineage dating to 2007, indicating long-standing stability of the interface.

Key Procedures and Functions

The package exposes nine documented procedures and functions organized around three functional areas:

  • CREATE_PROJECT_CUSTOMER — Establishes a new customer-to-project relationship, including billing and shipping attributes and invoice currency and exchange rate handling. The documented signature carries parameters for project and customer identifiers, a project relationship code, a customer bill split, bill-to and ship-to customer and address identifiers, invoice currency and rate information, and standard API return-status messaging parameters.
  • UPDATE_PROJECT_CUSTOMER — Modifies an existing project-customer relationship, allowing changes to the customer attributes recorded against the project.
  • DELETE_PROJECT_CUSTOMER — Removes a project-customer relationship.
  • CREATE_CUSTOMER_CONTACT — Creates a contact associated with a project customer.
  • UPDATE_CUSTOMER_CONTACT — Updates the details of an existing customer contact.
  • DELETE_CUSTOMER_CONTACT — Removes a single customer contact.
  • DELETE_ALL_CONTACTS — Removes all contacts tied to a given project-customer context in a single operation.
  • VALIDATE_CUSTOMER — Performs validation of customer data prior to persistence.
  • VALIDATE_CONTACT — Performs validation of contact data prior to persistence.

Tables Accessed

The package reads from and writes to four documented tables through APPS synonyms:

  • PA_PROJECT_CUSTOMERS — The primary store for project-customer relationships, including bill split and billing/shipping attributes.
  • PA_PROJECT_CONTACTS — The store for customer contacts associated with project-customer records.
  • PA_PROJECT_PARTIES — Records the parties participating in a project, supporting the relationship model used by the customer APIs.
  • HZ_RELATIONSHIPS — The Trading Community Architecture (TCA) table that holds relationship definitions between entities, used to link customers and contacts to project parties consistently with the broader EBS party model.

Usage Notes

Because PA_CUSTOMERS_CONTACTS_PVT is a private package, it is not invoked directly by end users or by customer-developed code. It is referenced by one other package within the APPS schema — the public-facing counterpart that delegates to these routines. Typical invocation paths include the Oracle Projects project-customer and contact maintenance forms, related concurrent programs that bulk-load or update project customer data, and any public API that layers validation and message handling on top of these private procedures.

The documented parameter defaults follow the standard EBS API pattern: p_commit defaults to FND_API.G_FALSE and p_validate_only defaults to FND_API.G_TRUE, so a caller can validate without committing. The return-status trio — x_return_status, x_msg_count, and x_msg_data — signals success, warning, or error conditions and carries diagnostic messages. Custom implementations requiring this functionality should call the public package rather than the private body, ensuring compatibility across 12.1.1 and 12.2.2.