Results for “default_attributes”

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

Overview

AR_AI_INTEG_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM (E-Business Suite Technical Reference Manual) as an "OTHER" API. Its name follows the naming convention used for Receivables (AR) integration objects, with the "AI" segment commonly denoting Automatic Invoice or AutoInvoice-oriented processing. In EBS 12.1.1 and 12.2.2 the package operates as a supporting integration layer that resolves defaulting logic and contextual values required during invoice and customer-related processing. The dependency metadata confirms it compiles against SYS.STANDARD and is both referenced by and dependent on the APPS schema, with a downstream consumer identified as AR_EBI_INVOICE_PUB — the public wrapper frequently used by Oracle's EBI (Enterprise Business Integration) flows and by external integration points.

Key Procedures and Functions

The ETRM documentation for release 12.2.2 lists a single documented program unit within this package:

• DEFAULT_ATTRIBUTES — The sole documented procedure. Its name indicates a responsibility for populating or deriving default attribute values used by the calling integration process. In practice, procedures with this naming pattern apply defaulting rules sourced from system parameters, customer profiles, and receivable terms, returning or storing those values so that downstream invoice creation logic operates with fully resolved attributes. The metadata does not expose the formal parameter list, so no argument signature should be assumed; the procedure should be treated as an internal defaulting routine invoked by the package's integration caller.

No additional public functions or procedures are documented. The presence of a package body confirms that private helper logic exists beyond the documented interface.

Tables Accessed

The package references the following tables through APPS synonyms, as recorded in the ETRM metadata. Each is consistent with a defaulting and integration role:

• AR_SYSTEM_PARAMETERS_ALL — Receivables system options, supplying operating-unit-level defaults.
• GL_LEDGERS — General Ledger ledger definitions, used to resolve accounting context.
• HZ_CUSTOMER_PROFILES — TCA customer profile values, driving customer-specific defaulting behavior.
• HZ_CUST_ACCT_SITES_ALL — Customer account sites, for site-level address and attribute resolution.
• HZ_CUST_SITE_USES_ALL — Site use assignments, determining bill-to and ship-to purpose context.
• RA_TERMS — Payment terms, providing term-related defaults for the transaction.

Collectively these reads indicate that DEFAULT_ATTRIBUTES assembles default values from Receivables setup, Trading Community Architecture customer data, and ledger configuration before an invoice or integration payload is finalized. No write operations are evidenced by the reference data provided.

Usage Notes

AR_AI_INTEG_PKG is not an end-user-facing component. It is not documented as being attached to a specific Oracle Forms block or concurrent program. Its principal documented consumer is AR_EBI_INVOICE_PUB, which suggests invocation from integration service flows, Web Service or EBI callouts, and possibly from AutoInvoice interface processing that requires attribute defaulting ahead of import validation. Custom development should call it only where the corresponding Oracle EBI path requires the same defaulting semantics; direct substitution for standard AutoInvoice defaulting rules is not advised. Because the package is marked VALID and carries a package body, developers extending it should preserve the existing DEFAULT_ATTRIBUTES behavior and continue to rely on the APPS synonyms for the TCA and Receivables tables listed above. In 12.2.2, the same object metadata applies, and the dependency on SYS.STANDARD indicates only Oracle-supplied base types rather than external third-party dependencies.