Results for “credit_percent”

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

Overview

The AS_SALES_CREDITS_LOG table is a transactional audit table within the Oracle E-Business Suite Sales Foundation (AS) module. It resides in the OSM schema and holds the sales credit change history — a chronological record of modifications made to sales credit assignments on leads and lead lines. Because sales credits determine revenue attribution and quota fulfillment for sales representatives, preserving a full historical trail of credit percentage and credit amount changes is essential for compensation audits, dispute resolution, and compliance reporting.

The table is classified as VALID in the ETRM metadata for both 12.1.1 and 12.2.2. Mined from its foreign key structure, the heuristic Data Vault classification is standalone, meaning it functions independently rather than as a pure hub, link, or satellite. As a modeling suggestion, it is best understood as a satellite-style history table: it carries a surrogate primary key (LOG_ID) and records attribute changes against referenced business entities, but it does not itself drive the core sales credit relationship.

Key Information Stored

The documented physical schema defines 20 columns. The most significant, organized by role, are:

• LOG_ID — surrogate primary key, enforced by AS_SALES_CREDITS_LOG_PK and uniquely indexed by AS_SALES_CREDITS_LOG_U1. This is the sole documented business-key candidate.
• LOG_MODE — indicates the nature of the logged operation (for example insert, update, or delete), allowing reconstruction of the change sequence.
• SALES_CREDIT_ID — identifies the underlying sales credit record to which the logged change applies.
• LEAD_ID — foreign key to AS_LEADS_ALL, the lead header associated with the credit.
• LEAD_LINE_ID — foreign key to AS_LEAD_LINES_ALL, the specific lead line affected.
• SALESFORCE_ID — foreign key to AS_SALESFORCE, the sales organization team.
• SALESGROUP_ID — the sales group within the salesforce credited for the transaction.
• CREDIT_TYPE_ID — foreign key to IGS_FI_CR_TYPES_ALL, defining whether the credit is revenue or non-revenue.
• CREDIT_PERCENT and CREDIT_AMOUNT — the credited share of the opportunity, expressed as a percentage and a monetary value respectively.
• OPP_BEST_FORECAST_AMOUNT, OPP_FORECAST_AMOUNT, and OPP_WORST_FORECAST_AMOUNT — the forecast-band amounts tied to the opportunity at the time of logging.
• Creation, update, and audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER provide the standard EBS WHO columns and optimistic locking support.
• ENDDAY_LOG_FLAG — flags records captured via end-of-day processing.

Common Use Cases and Queries

Typical reporting scenarios include auditing credit reassignments, tracking forecast revisions against a lead, and reconciling credit history for compensation cycles. A representative join reconstructs the credit trail for a lead:

• Query the full change history for a lead: SELECT log_id, log_mode, credit_percent, credit_amount, last_update_date FROM as_sales_credits_log WHERE lead_id = :lead_id ORDER BY last_update_date;
• Compare credits across forecast bands by joining on SALESFORCE_ID to AS_SALESFORCE.
• Filter by ENDDAY_LOG_FLAG = 'Y' to isolate records generated by scheduled end-of-day jobs versus interactive updates.
• Group by LOG_MODE to measure volume of insert versus update versus delete operations over a period.
• Reconcile OPP_FORECAST_AMOUNT history to diagnose forecast variance.

Related Objects

The table participates in the following documented relationships, driven by foreign keys:

• AS_LEADS_ALL — joined via LEAD_ID; the parent lead header.
• AS_LEAD_LINES_ALL — joined via LEAD_LINE_ID; the affected lead line.
• AS_SALESFORCE — joined via SALESFORCE_ID; the credited sales team.
• IGS_FI_CR_TYPES_ALL — joined via CREDIT_TYPE_ID; the credit type definition.

While the metadata marks this as a standalone data object, functionally it is consumed alongside the base sales credit tables in the AS module, and its history supports the sales compensation and forecasting processes that depend on accurate credit attribution.