Search Results get_invoice_to_customer_id




Overview
Explore in AI Chat

Overview

OE_DEFAULT_AGREEMENT is an Oracle Order Management (OM) package body in the APPS schema that supports the defaulting framework for pricing and agreements within Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its principal business purpose is to supply default values for the agreement attributes that Order Management uses when constructing a pricing agreement context during order entry and pricing. The package implements a set of getter functions whose names mirror the agreement record structure defined in OE_PRICING_CONT_PUB.Agreement_Rec_Type, allowing the pricing engine to populate an agreement record through a consistent defaulting interface rather than hard-coding values in calling code. In the delivered seed data, several of these getters intentionally return NULL, which signals to the calling defaulting logic that no system default exists for that attribute and that the attribute should be resolved through alternative defaulting sources such as customer profile options, price lists, or user entry. The header comment ($Header: OEXDAGRB.pls 120.3 2005/12/14) indicates the file has been largely stable since the mid-2000s, with only targeted corrections applied, notably the change associated with Bug 1524336 that altered end-date defaulting behavior.

Key Procedures and Functions

The documented package metadata lists a single exposed entry, ATTRIBUTES, while the package body source additionally reveals a family of getter functions. The documented API surface should be treated as authoritative for integration purposes:

  • ATTRIBUTES — The documented procedure/function associated with this package. It represents the exposed entry point through which callers obtain agreement defaulting information. Do not assume a parameter list; invocation details are governed by the package specification, which is not reproduced here.
  • Get_Agreement — Returns a newly generated agreement identifier by selecting the next value from the OE_AGREEMENTS_S sequence. This is the only getter in the package that produces a real value rather than NULL.
  • Get_End_Date_Active — Returns the default end date for an active agreement. Per the bug fix noted in the source, this returns NULL rather than SYSDATE plus 24 months.
  • Remaining getters (Get_Accounting_Rule, Get_Agreement_Contact, Get_Agreement_Num, Get_Agreement_Type, Get_Customer, Get_Freight_Terms, Get_Invoice_Contact) — Each returns NULL, deliberately deferring the corresponding agreement attribute to other defaulting sources.

Note that the user search term get_invoice_to_customer_id does not correspond to a documented function in this package body; the closest documented member is Get_Invoice_Contact, which returns NULL. Callers seeking invoice-to-customer defaulting should verify the correct owning package in the pricing defaulting hierarchy.

Tables Accessed

The documented tables referenced through APPS synonyms are:

  • OE_AGREEMENTS_S — The sequence used to generate agreement identifiers. Get_Agreement selects OE_AGREEMENTS_S.NEXTVAL FROM DUAL to produce a unique agreement ID for a new agreement record.
  • DUAL — The standard single-row pseudo-table used solely as the source for the sequence NEXTVAL selection.

No base tables are read or written directly by this package; persistent agreement data is managed by the pricing and agreements APIs rather than by this defaulting helper.

Usage Notes

OE_DEFAULT_AGREEMENT is invoked indirectly by the Order Management pricing and defaulting framework, typically when an agreement record must be instantiated or populated during order entry, order import, or pricing API calls. It is referenced by one other package, which supplies the agreement record context. Because the getters are largely NULL-returning by design, the package behaves as a placeholder defaulting layer: it centralizes the interface and the agreement ID generation while allowing customer-specific or profile-driven values to override. Custom code should not call the spec-less internal getters directly unless the package specification exposes them; the documented entry point is ATTRIBUTES. Diagnostic output is emitted through OE_DEBUG_PUB, and unexpected errors are surfaced via OE_MSG_PUB and FND_API.G_EXC_UNEXPECTED_ERROR, so callers must handle standard EBS API exception propagation.