Results for “check_relation_exists”

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

Overview

OE_CUSTOMER_INFO_PVT is an Oracle E-Business Suite (EBS) private PL/SQL package maintained under the APPS schema. It is classified as a PVT (private) API, meaning it is not intended for direct invocation by external or customer code; instead it is called internally by other Oracle Order Management packages. Its principal business function is to retrieve, validate, and create customer-related information for the Order Management (OE) modules. The package mediates between Order Management transaction processing and the Oracle Trading Community Architecture (TCA) / Receivables customer model (HZ_ and AR_ tables), resolving or constructing party, account, address, site, contact, and relationship records that an order header or line requires.

Within ETRM 12.2.2 the package is recorded as VALID and exposes 34 documented procedures and functions. Its dependency profile confirms this role: it references OE_ORDER_PUB and STANDARD, and is referenced by OE_CUSTOMER_INFO_PVT, OE_HEADER_UTIL, and OE_LINE_UTIL. The reference to OE_HEADER_UTIL is significant for readers who search for that object, since OE_HEADER_UTIL is a primary internal consumer of OE_CUSTOMER_INFO_PVT.

Key Procedures and Functions

The documented procedures group into four functional clusters. Names are given as documented; parameter lists are intentionally not reproduced.

• Retrieval: GET_CUSTOMER_INFO_IDS obtains the identifiers associated with customer information, and VALUE_TO_ID_ADDRESS and VALUE_TO_ID_CONTACT convert descriptive address and contact values into their corresponding TCA identifiers.
• Account and party creation: CREATE_ACCOUNT, CREATE_PARTY_SITE, CREATE_CUST_ACCOUNT_SITE, and CREATE_ACCT_SITE_USES build the customer account hierarchy, party site, account site, and site-use records respectively.
• Address, contact, and relationship creation: CREATE_ADDRESSES, CREATE_CONTACT, and CREATE_RELATIONSHIPS persist address, contact, and relationship data. Associated CHECK_PARTY_SITE_EXISTS, CHECK_CUST_SITE_EXISTS, and CHECK_RELATION_EXISTS verify prior existence before creation.
• Validation and duplication checks: CHECK_CUSTOMER_FIELDS, VALIDATE_CUSTOMER_FIELDS, CHECK_DUPLICATE_CUSTOMER, CHECK_ADDRESS_FIELDS, VALIDATE_ADDRESS_FIELDS, CHECK_DUPLICATE_ADDRESS, and CHECK_CONTACT_FIELDS enforce mandatory-value and duplicate-detection rules before data is committed.

Tables Accessed

The package reads and writes the following tables through APPS synonyms, which are central to customer master and TCA processing:

• HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS — party, party site, and location records comprising the underlying address and entity model.
• HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_RELATE — customer account, account site, site use, role, and account relationship data.
• HZ_ORG_CONTACTS, HZ_RELATIONSHIPS — organization contact and relationship records.
• AR_SYSTEM_PARAMETERS_ALL — Receivables system options, typically consulted for customer/address validation defaults.
• DUAL and PLITBLM — utility references for scalar evaluation and PL/SQL table handling.

Usage Notes

OE_CUSTOMER_INFO_PVT is an internal package and should not normally be called directly. It is most commonly invoked from OE_HEADER_UTIL and OE_LINE_UTIL during order entry and order import processing, when Order Management must resolve an existing customer or create customer, address, contact, and relationship records on the fly. Because the package name itself appears as its own referencing package, recursive or overloaded internal calls also occur.

For extension or debugging work, Oracle's supported public interfaces (for example OE_ORDER_PUB and the TCA public APIs) should be used rather than this private package. Custom code that requires equivalent behavior should call HZ_CUST_ACCOUNT_V2PUB or related TCA public APIs. Readers arriving via the search term "oe_header_util" should note that OE_HEADER_UTIL is a documented dependent of OE_CUSTOMER_INFO_PVT, and that behavior observed in OE_HEADER_UTIL frequently originates in this package's validation and creation logic.