Search Results create_cust_acct_relationship

Overview

ASO_PARTY_INT is an internal integration package in the Oracle E-Business Suite Order Management (ASO) schema, owned by APPS. It functions as a wrapper layer that consolidates party, customer account, contact, and account relationship maintenance operations performed against the Oracle Trading Community Architecture (TCA) data model. The package abstracts the underlying TCA Version 2 public APIs (HZ_PARTY_V2PUB, HZ_CUST_ACCOUNT_V2PUB, and related packages) so that Order Management and its dependent modules can create and update trading community entities through a single, stable interface.

The header comment identifies the package as having been migrated from the earlier TCA Version 1 APIs to the Version 2 public API set. This migration affected CREATE_CUSTOMER_ACCOUNT, CREATE_ACCT_SITE, CREATE_ACCT_SITE_USE, CREATE_CONTACT, CREATE_CONTACT_ROLE, CREATE_ORG_CONTACT_ORD, CREATE_PARTY_SITE_USE, CREATE_CUST_ACCT_RELATIONSHIP, and UPDATE_PARTY. Procedures judged obsolete after the migration—including the original CREATE_ORG_CONTACT, contact point, contact restriction, and party site update routines—were removed. The current file header version is 120.8, last modified in September 2010, which is consistent with the code line shipped in both EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes fifteen documented procedures. They fall into four functional groups:

• Party operations: CREATE_PARTY and CREATE_PARTY_SITE create a party record and its associated party site, while UPDATE_PARTY maintains existing party data. These procedures delegate to the HZ_PARTY_V2PUB API structures, as evidenced by the use of HZ_PARTY_V2PUB.Party_Rec_Type and G_MISS_PARTY_REC in the source.
• Customer account operations: VALIDATE_CUSTACCOUNT performs validation of account data; CREATE_CUSTOMER_ACCOUNT creates the customer account header; CREATE_ACCT_SITE and CREATE_ACCT_SITE_USES create account sites and their site uses; GET_ACCT_SITE_USES retrieves existing site use information.
• Contact operations: CREATE_CONTACT creates contact records, CREATE_ORG_CONTACT_ORD creates organization contact associations specific to order processing, and CREATE_CONTACT_ROLE assigns roles to contacts.
• Relationship operations: CREATE_CUST_ACCT_RELATIONSHIP and UPDATE_CUST_ACCT_RELATIONSHIP establish and maintain the hierarchical or reciprocal relationships between customer accounts, which is the specific operation referenced by the search term "create_cust_acct_relationship."

The package is referenced by seven other packages, indicating that it is a shared internal utility rather than a standalone public API.

Tables Accessed

The package reads and writes TCA base and interface tables through APPS synonyms. HZ_PARTIES and HZ_RELATIONSHIPS store party and party-to-party relationship data. HZ_PARTY_SITES, HZ_PARTY_SITE_USES, HZ_LOCATIONS, and HZ_ORG_CONTACTS hold party site, site use, location, and organization contact records. Customer account data resides in HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, and HZ_CUST_ACCT_RELATE_ALL, the last of which is the table underlying customer account relationships. HZ_ROLE_RESPONSIBILITY supports role assignment. ASO_ACCOUNT_NUMBER_S supplies account numbering for the Order Management schema. AR_SYSTEM_PARAMETERS provides Receivables system option values, and AMS_SOURCE_CODES supplies source code references used during record creation.

Usage Notes

ASO_PARTY_INT is an internal package and is not intended for direct invocation by external integrations; Oracle's supported public interface for TCA remains the HZ_*_PUB and HZ_*_V2PUB API family. Within EBS, the package is invoked by other ASO packages (seven documented dependents) and by Order Management forms and concurrent programs that must ensure a customer account exists with the required sites, contacts, and relationships before order entry proceeds. Custom code that calls this package directly assumes the risk of an unsupported interface, since procedure signatures and internal API calls may change between patch levels. When extending or troubleshooting customer account relationship creation, the CREATE_CUST_ACCT_RELATIONSHIP and UPDATE_CUST_ACCT_RELATIONSHIP procedures are the relevant entry points, with all exception handling and message propagation expected through the standard x_return_status, x_msg_count, and x_msg_data out parameters.