Search Results get_org_contact_rec_type

Overview

APPS.CSC_RESPONSE_CENTER_PKG_V2 is a public PL/SQL package declared with AUTHID CURRENT_USER, belonging to the Oracle Customer Care (CSC) Response Center module within Oracle E-Business Suite. Its header carries the source control signature $Header: CSCV2RCS.pls 120.0 2005/07/17 23:57:04 vshastry noship $, confirming that the package was built against the Oracle Trading Community Architecture (TCA) Version 2 public APIs introduced with Release 11.5.10 and preserved through releases 12.1.1 and 12.2.2.

The principal business function of this package is to act as a centralized factory of strongly typed record structures used by the Response Center (TeleService / Interaction Center) application logic. Rather than defining its own record types, the package returns the record type definitions published by the various HZ_*_V2PUB packages, allowing callers to declare local variables that match exactly the parameter structures required by the TCA public APIs for parties, customer accounts, contact points, and relationships. In this sense the package is an abstraction layer or "type registry" that shields Response Center code from hard-coded references to individual TCA API specifications and keeps those references consistent across the application.

Key Procedures and Functions

The documented interface comprises 31 functions, all returning either a scalar or a TCA record type. They fall into three functional groups.

• Missing-value sentinels: G_MISS_NUM, G_MISS_CHAR, and G_MISS_DATE return the standard numeric, character, and date placeholders used throughout Oracle Forms and PL/SQL code to represent an unset or null value, mirroring the FND_API.G_MISS_* convention.
• Party and customer structures: GET_PERSON_REC_TYPE, GET_ORG_REC_TYPE, GET_PARTY_REC_TYPE, and GET_ORG_CONTACT_REC_TYPE supply person, organization, party, and organization-contact record types from HZ_PARTY_V2PUB and HZ_PARTY_CONTACT_V2PUB. GET_ACCOUNT_REC_TYPE, GET_CUST_PROFILE_REC_TYPE, GET_CUST_ACCT_ROLES_REC_TYPE, and GET_CUST_ACCT_RELATE_REC_TYPE return the HZ_CUST_ACCOUNT_V2PUB and HZ_CUSTOMER_PROFILE_V2PUB structures describing customer accounts, profiles, account roles, and account relationships.
• Address, contact point, and site structures: GET_ACCT_SITE_REC_TYPE, GET_ACCT_SITE_USES_REC_TYPE, GET_PARTY_SITE_REC_TYPE, and GET_PARTY_SITE_USE_REC_TYPE return the customer account site and party site definitions used to build and update addresses. GET_PHONE_REC_TYPE, GET_EMAIL_REC_TYPE, GET_WEB_REC_TYPE, GET_EDI_REC_TYPE, GET_TELEX_REC_TYPE, GET_CONTACT_POINTS_REC_TYPE, and GET_CONT_POINTS_PREF_REC_TYPE supply the individual contact point variants and the aggregate contact point and contact preference structures.

The address_rec_type construct for which the object was searched corresponds directly to these site and contact-point record type accessors, which callers use when passing postal address data to the TCA address and site APIs.

Tables Accessed

The package specification is a pure declaration unit: it defines only function signatures and therefore performs no direct SQL. Because every accessor returns a type defined in an HZ_*_V2PUB package, the underlying tables are accessed indirectly when the caller invokes the corresponding TCA public API. Those APIs operate against the TCA schema, principally HZ_PARTIES, HZ_PARTY_SITES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_CONTACT_POINTS, HZ_CONTACT_PREFERENCES, HZ_CUST_ACCT_RELATE_ALL, and HZ_RELATIONSHIPS, all referenced through APPS synonyms. Within the ETRM metadata the explicit table reference list is empty, which is consistent with this design.

Usage Notes

CSC_RESPONSE_CENTER_PKG_V2 is invoked principally by the Response Center forms and by the supporting server-side PL/SQL that surrounds them, including the wrapper packages built for the version 2 TCA APIs. A developer writing a customization against the Response Center typically calls a GET_*_REC_TYPE function to declare a local variable of the correct shape, populates it with values collected from the form, and passes it to the matching HZ_*_V2PUB procedure. The ETRM metadata records a single reverse dependency, indicating that one other package within the APPS schema references this specification.

Because the package header is dated 2005 and remains classified as noship with an API classification of OTHER, it should be treated as an internal application programming interface rather than a formally supported public API. The interface is stable between 12.1.1 and 12.2.2, so code written against it continues to compile across both releases, but customizations should continue to rely on the underlying HZ_*_V2PUB APIs for long-term supportability.