Search Results get_bill_to_use_id

Overview

APPS.AR_AME_CM_ATTRIBUTES_API is an Oracle E-Business Suite PL/SQL package that belongs to the Oracle Receivables (AR) module and supports the integration between Receivables credit management and Oracle Approvals Management Engine (AME). The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the calling schema rather than the definer. Its central business role is to expose the set of transaction-level and customer-level attributes that AME requires when evaluating an approval or credit management rule for an Accounts Receivable transaction.

The package binds itself to two constants that anchor it within the EBS workflow and application registries: c_application_id is fixed to 222 (the Receivables application identifier), and c_item_type is set to 'ARAMECM', the workflow item type used by Receivables Credit Management. These constants confirm the package operates specifically in the AME-driven credit management context rather than general transaction entry. The item type is significant because AME retrieves the item type and item key from the transaction being evaluated and then invokes the relevant attribute functions to resolve values for rule evaluation. The header comment date (2003) reflects the package's long-standing presence in the codebase, and the noship designation indicates it is not a standalone ship unit but a supporting component.

Key Procedures and Functions

The package exposes 28 documented functions, all of which accept a transaction identifier as input (typically p_transaction_id) and return a single scalar value. They fall into logical groupings:

• Transaction identity and linkage: GET_CUSTOMER_TRX_ID, GET_CUSTOMER_ID, GET_BILL_TO_USE_ID, GET_ORIG_TRX_NUMBER, and GET_BATCH_SOURCE_NAME resolve the underlying transaction and its batch origin.
• Customer and bill-to data: GET_BILL_TO_CUSTOMER_NAME, GET_BILL_TO_CUSTOMER_NUMBER, and GET_CUSTOMER_NAME return the customer's descriptive identifiers for display and rule evaluation.
• Collector information: GET_COLLECTOR_ID, GET_COLLECTOR_EMPLOYEE_ID, GET_COLLECTOR_NAME, and GET_COLLECTOR_USER_NAME provide the collector assigned to the transaction across both ID and name representations.
• Approval and routing: GET_APPROVAL_PATH, GET_APPROVER_ID, GET_APPROVER_USER_NAME, GET_NON_DEFAULT_PERSON_ID, and GET_REQUESTOR_PERSON_ID identify the participants and path involved in the approval process.
• Financial and classification attributes: GET_TRANSACTION_AMOUNT, GET_CURRENCY_CODE, GET_REASON_CODE, and the transaction type name function (retrieved via the get_transaction_type_name query) supply the monetary and categorical values used in rule evaluation.

Because AME evaluates rules by interrogating named attributes, each function effectively registers a rule-addressable attribute. The calling framework invokes the appropriate function based on the attribute name configured in the AME rule, and the returned value is then compared against rule conditions.

Tables Accessed

The package reads from a defined set of tables through APPS synonyms:

• FND_APPLICATION — supplies the application ID used in the c_application_id constant.
• WF_ITEM_ATTRIBUTES and WF_ITEM_ATTRIBUTE_VALUES — workflow attribute definitions and values that map AME attributes to their resolved data.
• RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_LINES — the Receivables transaction and line records underpinning amount, currency, and original transaction number.
• RA_CUST_TRX_TYPES — transaction type definitions, used to resolve the transaction type name.
• RA_CM_REQUESTS — credit management request records linking transactions to their approval state.
• AR_COLLECTORS — collector employee assignments.
• HZ_CUST_ACCOUNTS, HZ_PARTIES, and HZ_CUSTOMER_PROFILES — Trading Community Architecture customer, party, and profile data used for bill-to and customer name resolution.

Usage Notes

This package is not intended for direct invocation by end users or standalone custom programs. It is invoked indirectly by AME when evaluating credit management rules for Receivables transactions. When a transaction is submitted to credit management, AME reads the item type (ARAMECM) and item key, then calls the relevant attribute functions to populate the transaction attributes against which approval rules are evaluated. Consequently, customizations that require an additional approval attribute must extend both the AME attribute configuration and, where appropriate, this package's function set. The package is referenced by zero other packages in the documented metadata, confirming its role as a leaf-level provider of attributes rather than a reusable service layer. Developers extending credit management approvals should treat the documented function signatures as the only supported contract and avoid altering the return semantics, since AME rule definitions depend on stable, consistent values.