Results for “line_credits”

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

Overview

AS_DOSSIER_SALESREPS_V is a reporting view in the Oracle E-Business Suite Sales Foundation (AS) module. Its documented description is "Order history sales representatives view," indicating that it exposes sales credit information tied to order headers and associated sales representatives. The view is part of the sales dossier family of database objects used by Oracle Sales Foundation and related order-management reporting components, where a "dossier" represents an aggregated, historical profile of an order's sales-credit distribution across credited salespersons.

This view does not store data itself; it derives its content by aggregating results from another view, AS_DOSSIER_REPS_UNIONALL_V, which consolidates sales-credit rows across credit types. AS_DOSSIER_SALESREPS_V therefore serves as a summarized layer purpose-built for query and reporting rather than for transactional processing. Its role in Oracle EBS reporting and integration is to provide a denormalized, per-order roll-up of header-level and line-level sales credits grouped by sales representative and credit type, which downstream reports, dossier screens, or custom integrations can consume without re-implementing the aggregation logic.

Note that the ETRM metadata records this object as "Not implemented in this database," meaning it may be absent or dormant in certain installations and would only exist where the associated Sales Foundation dossier feature set has been deployed.

Underlying Base Objects

The documented view text defines AS_DOSSIER_SALESREPS_V entirely over another view rather than directly over base tables. The single referenced source is AS_DOSSIER_REPS_UNIONALL_V (aliased as DUR), a UNION ALL view that combines sales-credit records from multiple credit-type sources into a consistent structure. Because the ETRM metadata lists no directly referenced base tables, the underlying physical tables are reached only indirectly through AS_DOSSIER_REPS_UNIONALL_V.

The defining SQL is:

• SELECT DUR.HEADER_ID, SUM(DUR.HEADER_CREDITS), SUM(DUR.LINE_CREDITS), DUR.CREDIT_TYPE, DUR.SALESREP_ID, DUR.SALESREP
• FROM AS_DOSSIER_REPS_UNIONALL_V DUR
• GROUP BY DUR.HEADER_ID, DUR.SALESREP_ID, DUR.SALESREP, DUR.CREDIT_TYPE

This structure confirms that the view aggregates credits to the grain of order header, sales representative, and credit type, collapsing multiple detail rows from the union-all source into one summarized row per combination. Understanding this relationship matters because any filter applied to the view is effectively a filter on the aggregated output of AS_DOSSIER_REPS_UNIONALL_V, and performance depends on how efficiently that underlying union-all view resolves.

Key Columns

The view exposes six columns, each documented in the ETRM metadata:

• HEADER_ID — Identifier of the order header to which the sales-credit record belongs. It is the primary grouping key and links the aggregated rep data back to the order.
• HEADER_CREDITS — Summed header-level credit amount for the given header, sales representative, and credit type. The aggregate is produced by SUM(DUR.HEADER_CREDITS).
• LINE_CREDITS — Summed line-level credit amount for the same grouping. Produced by SUM(DUR.LINE_CREDITS).
• CREDIT_TYPE — Classification of the credit (for example, the sales-credit category or recipient type), which distinguishes otherwise similar aggregated rows.
• SALESREP_ID — Unique identifier of the sales representative credited on the order.
• SALESREP — Descriptive name or label of the sales representative, carried alongside SALESREP_ID for readable reporting output.

Common Use Cases and Queries

The principal use case is order-history sales-credit reporting: determining which sales representatives were credited on an order and how much header and line credit each received. A typical query retrieves the credit breakdown for a specific order:

• SELECT header_id, salesrep_id, salesrep, credit_type, header_credits, line_credits FROM as_dossier_salesreps_v WHERE header_id = :p_header_id ORDER BY salesrep;

For representative-level performance analysis, aggregate totals across all orders are obtained by grouping on the sales representative:

• SELECT salesrep, credit_type, SUM(header_credits) total_header_credits, SUM(line_credits) total_line_credits FROM as_dossier_salesreps_v GROUP BY salesrep, credit_type ORDER BY total_line_credits DESC;

Integration scenarios include feeding sales-compensation extracts, dossier summary windows, or custom order-credit dashboards where a per-order, per-rep roll-up is required. Because the view performs grouping internally, consumers avoid duplicating aggregation logic, though they should confirm availability of the object in their environment, as the metadata marks it as not implemented in the referenced database.