Results for “set_debug_on”

35 results




Overview
Explore in AI Chat

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

Overview

OE_CREATE_ACCOUNT_INFO is an Oracle E-Business Suite Accounts Receivable / Order Management utility package owned by APPS and classified under ETRM as OTHER. Its principal business function is to resolve incoming customer and account information — the party, account, contact, and site data collectively referred to as "account info" — and to create the corresponding Trading Community Architecture (TCA) entities automatically when they do not already exist. The package underpins the Automatic Account Creation (AAC) flow invoked during order entry and telesales/teleservice scenarios, where an agent or an order capture process supplies a customer name and address and the system must decide whether to match an existing account or build a new one.

The header definition (OEXCACTS.pls 120.2) exposes a control record, Control_Rec_Type, that governs this behaviour. It carries switches such as p_allow_account_creation (values ALL, SITE_AND_CONTACT, NONE, CHECK or NULL), p_multiple_account_is_error, p_multiple_contact_is_error, p_commit, p_init_msg_list, p_created_by_module, and the Contact Center integration flags p_fetch_primary_party_sites, p_continue_processing_on_error, p_do_value_to_id, and p_return_if_only_party. These parameters allow the same API to serve order entry, telesales, and teleservice integrations with different matching and creation rules.

Key Procedures and Functions

The ETRM inventory documents fifteen callable units:

  • CREATE_ACCOUNT_LAYER — orchestrates creation of the account-level TCA entities when the matching routines fail to identify an existing account.
  • CHECK_AND_CREATE_ACCOUNT — validates whether a customer account exists and creates one if permitted by the control flags.
  • CHECK_AND_CREATE_CONTACT — performs the equivalent check-and-create cycle for contacts associated with the party or account.
  • CHECK_AND_CREATE_SITES — resolves site (address) information and creates party site, account site, and site use records as required.
  • SET_DEBUG_ON — enables diagnostic tracing for troubleshooting the resolution and creation path.
  • IF_MULTIPLE_ACCOUNTS — evaluates the multiple-match condition and applies the p_multiple_account_is_error behaviour.
  • VALUE_TO_ID — converts descriptive attribute values into their corresponding TCA identifiers, subject to p_do_value_to_id.
  • FIND_SOLD_TO_ID — locates the sold-to customer identifier for the supplied account information.
  • FIND_CONTACT_ID — locates the contact identifier matching the supplied contact information.
  • FIND_SITE_ID — locates the site identifier matching the supplied address information.
  • GET_PARTY_ID — retrieves the party identifier underlying the customer or prospect.
  • GET_PARTY_CONTACT_ID — retrieves the party-level contact identifier.
  • GET_PARTY_SITE_ID — retrieves the party site identifier.
  • SOLD_TO_ORG — returns sold-to organisation information used by downstream order capture.
  • CUST_EXISTS — a boolean-style existence check indicating whether the customer already exists in TCA.

Tables Accessed

All tables are referenced through APPS synonyms into the HZ schema. HZ_PARTIES is the anchor entity, holding the party record created or matched first. HZ_PARTY_SITES and HZ_PARTY_SITE_USES store party-level addresses and their purposes. HZ_CUST_ACCOUNTS holds the customer account, with HZ_CUST_ACCOUNT_ROLES recording role assignments and HZ_CUST_ACCT_RELATE capturing account relationships. Address assignments flow through HZ_CUST_ACCT_SITES / HZ_CUST_ACCT_SITES_ALL and HZ_CUST_SITE_USES / HZ_CUST_SITE_USES_ALL. HZ_LOCATIONS stores the raw address geography, HZ_ORG_CONTACTS stores contact details, and HZ_RELATIONSHIPS links parties. PLITBLM is a PL/SQL table used for bulk/in-memory processing within the package.

Usage Notes

OE_CREATE_ACCOUNT_INFO is not a public API intended for arbitrary external calls. It is invoked internally by the Order Management account-generation flow — typically from order entry forms and from the telesales/teleservice integrations that pass Contact Center-specific control flags. ETRM records that it is referenced by one other package, which supplies the calling context and the control record values.

When extending or debugging the AAC behaviour, developers should set SET_DEBUG_ON to trace the match-and-create sequence and respect the control record defaults; notably p_allow_account_creation defaults to CHECK and p_do_value_to_id defaults to TRUE, so callers such as Telesales that must avoid value-to-id processing must override these explicitly. Direct custom invocation should be treated cautiously because the package writes across the full TCA hierarchy in a single logical unit governed by p_commit.