Search Results cust_acct_relationship




Overview

ASO_CHECK_TCA_PVT is a private PL/SQL package in the APPS schema belonging to the Oracle Order Capture / Oracle Quoting application family (ASO module). Its central purpose is to validate and reconcile Oracle Trading Community Architecture (TCA) customer data referenced on a quote before that quote is processed, priced, or converted to an order. The "PVT" suffix identifies the package as a private API: it is not intended to be called directly by customers, but rather as an internal service consumed by other ASO packages.

During quote entry, a user may select an existing customer account, a ship-to or bill-to site, a contact, or a party relationship. Because TCA data can change independently of the quote, stale or invalid references can exist by the time the quote is submitted or converted. ASO_CHECK_TCA_PVT provides the mechanism that re-validates these references against the current TCA model and repopulates the quote's customer-account attributes when discrepancies are found. Status is documented as VALID, confirming the package is a supported, compiled component of the ASO stack in EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

  • CHECK_TCA — The primary entry point of the package. Orchestrates validation of the customer data associated with a quote and determines whether the TCA references held on the quote remain valid.
  • CHECK_HEADER_ACCOUNT_INFO — Validates the customer account and site information recorded at the quote header level.
  • CHECK_LINE_ACCOUNT_INFO — Performs the equivalent validation for customer/site information captured at the quote line level, where lines may carry different ship-to or bill-to references.
  • CUSTOMER_ACCOUNT — Retrieves and validates a customer account from the TCA model (HZ_CUST_ACCOUNTS).
  • CUSTOMER_ACCOUNT_SITE — Retrieves and validates an account site (HZ_CUST_ACCT_SITES) against the account.
  • CUST_ACCT_RELATIONSHIP — Validates relationships between customer accounts (HZ_CUST_ACCT_RELATE) used in quoting scenarios such as bill-to/ship-to relationships.
  • CUST_ACCT_CONTACT_ADDR — Checks the contact and address data attached to a customer account or site.
  • ASSIGN_CUSTOMER_ACCOUNTS — Assigns or re-assigns customer account values back onto the quote structures after validation.
  • POPULATE_ACCT_PARTY — Populates party-related attributes (HZ_PARTIES) derived during the validation cycle.
  • CHECK_CUSTOMER_ACCOUNTS — A wrapper-level check that evaluates the set of customer accounts associated with the quote and returns the aggregate validation result.

Tables Accessed

The package reads the ASO quote tables — ASO_QUOTE_HEADERS_ALL, ASO_QUOTE_LINES_ALL, and ASO_SHIPMENTS — to obtain the customer references currently stored on the quote. It validates these against the TCA model, including HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_CUST_ACCT_RELATE, HZ_PARTIES, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, and HZ_RELATIONSHIPS. PLITBLM is a PL/SQL internal table type used for bulk processing rather than a persistent table. The TCA tables are read to confirm that the account, site, and party references on the quote still exist and are usable; ASO tables are read, and in the assignment routines potentially updated, to synchronize the quote with validated values.

Usage Notes

ASO_CHECK_TCA_PVT is invoked indirectly. It is referenced by ASO_CHECK_TCA_PVT itself, ASO_CORE_CONTRACTS_INT, ASO_MAP_QUOTE_ORDER_INT, ASO_QUOTE_HEADERS_PVT, ASO_QUOTE_LINES_PVT, and ASO_SUBMIT_QUOTE_PVT. Practically, this means the checks run during quote submission and during the quote-to-order mapping and contract integration flows, ensuring TCA references are consistent before data leaves the quoting module. It depends on ASO_QUOTE_PUB and FND_API, indicating use of the standard EBS API error-handling and message conventions (returning FND_API.G_RET_STS_SUCCESS or G_RET_STS_ERROR). Because it is a private package, customizations should call the public ASO_QUOTE_PUB or ASO_SUBMIT_QUOTE_PVT APIs rather than ASO_CHECK_TCA_PVT directly; direct calls risk breakage across patches and are unsupported.