Results for “follow_up”

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

Overview

The APPS.AR_CUSTOMER_CALL_TOPICS_V view is a reporting and integration layer within the Oracle EBS Receivables (AR) module that consolidates collections call activity, customer details, transaction information, and follow-up data into a single queryable structure. It is defined over the AR_CUSTOMER_CALL_TOPICS table and several joined AR objects, providing a denormalized presentation of collections work items. In EBS 12.1.1 and 12.2.2, this view supports collections management reporting, dunning follow-up tracking, and custom integrations that need to surface call topics alongside their related transaction, payment schedule, and collector context without requiring the consumer to reconstruct the multi-table joins themselves.

Underlying Base Objects

The view is owned by APPS and is defined over the following documented base objects:

• AR_CUSTOMER_CALL_TOPICS (synonym) — the primary driving table holding each call topic record, including follow-up, promise, and forecast attributes.
• AR_PAYMENT_SCHEDULES (synonym, aliased APS) — supplies due dates, transaction numbers, currency, amount due remaining, and additional attributes.
• RA_CUSTOMER_TRX (RCT) and RA_CUSTOMER_TRX_LINES (RCTL) — provide invoice header and line detail such as transaction number, line number, description, and extended amount.
• RA_CUST_TRX_TYPES (B) — supplies the transaction type classification, with a DECODE defaulting to 'REC' when no transaction is present (cash receipt scenarios).
• AR_COLLECTORS (ACO) — provides the collector name via ACO.NAME.
• AR_LOOKUPS (via ARPT_SQL_FUNC_UTIL) — resolved meanings for reason codes and follow-up actions, and the customer call topic text (ANO.TEXT) is sourced from AR_NOTES (ANO).
• ARPT_SQL_FUNC_UTIL (package) — the get_lookup_meaning function is called to translate lookup codes for CUSTOMER_RESPONSE_REASON and FOLLOW_UP.

Key Columns

• CUSTOMER_CALL_TOPIC_ID, CUSTOMER_CALL_ID, CUSTOMER_ID — identify the call topic, parent call, and customer.
• FOLLOW_UP_DATE, FOLLOW_UP_ACTION (and its lookup meaning), FOLLOW_UP_COMPANY_REP_ID, COMPLETE_FLAG — the follow-up workflow fields central to the "follow_up" search term.
• PROMISE_DATE, PROMISE_AMOUNT, FORECAST_DATE, COLLECTION_FORECAST — collections forecasting and commitment tracking.
• CALL_OUTCOME, REASON_CODE, CALL_DATE — call disposition and timing.
• TRX_NUMBER, DUE_DATE, AMOUNT_DUE_REMAINING, INVOICE_CURRENCY_CODE, LINE_NUMBER, EXTENDED_AMOUNT — transaction and payment schedule detail.
• COLLECTOR_ID and ACO.NAME — collector identity; plus contact, site, and phone identifiers.

Common Use Cases and Queries

Typical scenarios include identifying open follow-up actions for a collector, aging outstanding promised amounts, and reconciling call topics to their overdue invoices. A representative query filtering on follow-up activity:

• SELECT customer_call_topic_id, customer_id, follow_up_date, follow_up_action, collector_id, trx_number, amount_due_remaining FROM apps.ar_customer_call_topics_v WHERE complete_flag = 'N' AND follow_up_date IS NOT NULL ORDER BY follow_up_date;

Additional use cases include joining to AR_CUSTOMERS for customer names, aggregating AMOUNT_DUE_REMAINING by collector for workload analysis, and embedding the view in Oracle Reports or OAF-based collections dashboards. Because it already resolves lookup meanings and transaction defaults, it reduces custom coding in downstream extracts and interfaces.