Results for “amount_attribute1”

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

Overview

RA_CUSTOMER_PROFILES_INT_ALL is the Oracle Receivables open interface table that stages customer profile information prior to validation and import into the production customer profile tables. Residing in the AR schema with 154 documented columns in release 12.2.2 (and equally valid against 12.1.1), it functions as the inbound landing zone for profile attributes such as credit checking, dunning, statements, interest charges, and credit limits. Records are loaded by the Receivables Customer Interface concurrent program, which validates each row, sets VALIDATED_FLAG, and transfers qualifying records into RA_CUSTOMER_PROFILES_ALL and its column-level detail tables. Rows rejected during import remain flagged with an error code for correction and resubmission. From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone, suggesting it is best treated as a staging or satellite-style structure rather than a true hub or link, since it carries no enforced parent relationships beyond a single interest schedule reference.

Key Information Stored

The table is keyed by an interface surrogate key generated on insert, with the operational identifier pair REQUEST_ID and ORIG_SYSTEM_CUSTOMER_REF linking each staging row back to the concurrent request and to the source customer record. Interface control columns include INTERFACE_STATUS, INSERT_UPDATE_FLAG, and VALIDATED_FLAG, which govern whether a row is inserted or updated and whether it has passed validation. Business attribute columns of primary importance include:

• CUSTOMER_PROFILE_CLASS_NAME — the profile class applied to the customer.
• CREDIT_CHECKING, CREDIT_HOLD, CREDIT_BALANCE_STATEMENTS — credit management controls.
• OVERALL_CREDIT_LIMIT and TRX_CREDIT_LIMIT — aggregate and transaction-level exposure ceilings.
• DUNNING_LETTERS and DUNNING_LETTER_SET_NAME — collections correspondence configuration.
• STATEMENTS and STATEMENT_CYCLE_NAME — statement generation behavior.
• INTEREST_CHARGES, INTEREST_RATE, INTEREST_PERIOD_DAYS — late charge configuration, with INTEREST_SCHEDULE_ID as the sole documented foreign key, referencing CE_INTEREST_SCHEDULES.
• CREDIT_RATING and RISK_CODE — risk classification attributes.
• ORG_ID — the operating unit owning the profile.
• ATTRIBUTE1–15, AMOUNT_ATTRIBUTE1–15, and GLOBAL_ATTRIBUTE1–20 — descriptive flexfield and globalization columns.

Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are present for change tracking.

Common Use Cases and Queries

Typical usage centers on pre-import validation, error remediation, and profile data migration. A common diagnostic query identifies rows that failed validation:

• SELECT request_id, orig_system_customer_ref, interface_status FROM ra_customer_profiles_int_all WHERE validated_flag = 'N';
• SELECT i.orig_system_customer_ref, i.credit_checking, i.overall_credit_limit FROM ra_customer_profiles_int_all i WHERE i.request_id = :req_id AND i.interface_status = 'NEW';

Reporting scenarios include auditing credit limits staged for a mass update, reconciling dunning and statement settings before a collections rollout, and verifying operating unit assignment through ORG_ID. During data conversion projects, this table is populated directly by SQL*Loader or external integration, then processed by the Customer Interface program. Post-import reconciliation compares staged rows against RA_CUSTOMER_PROFILES_ALL to confirm successful transfer.

Related Objects

The table integrates with the following significant objects:

• RA_CUSTOMER_PROFILES_ALL — the production target populated upon successful import.
• RA_CUST_PROFILE_AMTS_ALL and RA_CUST_PROFILE_CLASSES_ALL — column-level profile values and class definitions.
• CE_INTEREST_SCHEDULES — referenced through INTEREST_SCHEDULE_ID for late charge schedules.
• HZ_CUST_ACCOUNTS and HZ_CUST_ACCT_SITES_ALL — customer and site records identified by ORIG_SYSTEM_CUSTOMER_REF and ORIG_SYSTEM_ADDRESS_REF.
• FND_CONCURRENT_REQUESTS — ties REQUEST_ID to the Customer Interface run.
• The Customer Interface concurrent program and its validation APIs, which read this table and write status outcomes.