VPxVIN Variable Profit by VIN
Data classification: GM_Confidential
Domain: Finance Data Engineering — Vehicle Profitability by VIN
Catalog schema: finance_prod.gold_vehicle_profit_gbl
Certification status: VERIFIED
Data product ID: 121243 — VPxVIN / Vehicle Profitability by VIN
Overview
VPxVIN (Variable Profit by Vehicle Identification Number) is GM's enterprise platform for vehicle-level profitability analytics. It combines VIN-level vehicle events, product attributes, dealer and geography context, sales channel classification, and financial measures so Finance and Sales & Marketing teams can understand how profitability changes by product, region, channel, dealer, option content, and time period.
VPxVIN is the common business foundation for answering questions such as:
- Which products, models, trims, and options are most profitable?
- How do incentives affect variable profit, net revenue, and sales allowance performance?
- How do dealers, geographies, and sales channels compare on profitability and inventory behavior?
- Which option packages drive penetration, revenue, contribution margin, or inventory turnover?
- How do retail, fleet, commercial, rental, government, cash, APR, lease, employee, and non-employee channels perform?
The platform supports day-to-day analysis for VSSM Finance, SSM Finance, Sales & Marketing, Product Marketing, Controllership, Demand/Fleet, and Finance Data Engineering. It is active in the United States, Canada, Mexico, AMEO, and Korea, with approximately 474 business users as of Q2 2025. Argentina and Brazil are listed as inactive in current business reference material.
Key benefits
VPxVIN gives GM a consistent profitability view at the VIN grain. That matters because the financial story of a vehicle is not just the wholesale invoice: it includes product configuration, delivery events, channel assignment, incentives, sales allowances, material cost, standard cost, variable manufacturing expense, and geography-specific access rules.
For business users, VPxVIN turns those inputs into repeatable profitability analysis. For data engineers, it provides the certified gold-layer foundation that powers semantic models, Power BI experiences, Cognos reporting, Databricks analytics, Finance360 experiences, and downstream finance applications.
The most common business themes are:
| Theme | Typical questions |
|---|---|
| Product profitability | What is variable profit by division, brand, model, trim, body style, model year, or option content? |
| Product mix and option contenting | Which options are most frequently ordered, and how do they affect revenue, incentives, contribution cost, and variable profit? |
| Incentive management | How effective are incentive programs by product and geography, and where are incentive-spend outliers? |
| Dealer and inventory performance | How does P&L compare across dealers, and how do inventory KPIs correlate with incentive spend and profitability? |
| Sales channel management | How do retail, fleet, lease, APR, commercial, rental, government, and employee channels compare on profitability and deliveries? |
| Finance reporting | Which VINs, products, or channels explain movement in gross revenue, net sales, sales allowances, variable cost, and variable profit? |
Who uses it
| Team / persona | How they use VPxVIN |
|---|---|
| VSSM Finance / SSM Finance | Day-to-day vehicle profitability analysis, P&L performance, incentive effectiveness, and sales channel profitability |
| Sales & Marketing | Product, option, geography, dealer, and channel performance analysis |
| Product Marketing | Option take-rate, option contenting, configuration profitability, and pricing-event support |
| Demand / Fleet | Fleet channel profitability, fleet customer segmentation, and delivery performance |
| Controllership | Revenue recognition support, finance tie-outs, and cube/reporting consumption |
Core business scope
VPxVIN organizes VIN-level analytics around five major subject areas:
| Subject | What it captures |
|---|---|
| Vehicle and configuration | Model year, brand, marketing division, merch model, body style, trim/PEG, architecture, generation, color, vehicle type, segment, tonnage, drive type, cab type, RPOs, and SEOs |
| Vehicle events | Order, production, invoice, dealer delivery, customer delivery, final delivery, and event timing used in profitability eligibility |
| Channel and delivery type | Retail, fleet, employee, non-employee, cash, APR, lease, commercial, rental, government, and related sales-channel classifications |
| Geography | Marketing region, section, zone, area, dealer, country, city, state, ZIP, NSC, and selling organization context |
| Financials | Gross revenue, net sales and revenue, sales allowances, material cost, standard cost, variable manufacturing expense, variable cost, MSRP, and variable profit |
Product attributes come from GVIT (Global Vehicle Identity Table), which aligns product attributes with GM3PD and is governed by MDG / DRM. GVIT supplies the product hierarchy used across VPxVIN reporting, including brand, body style, marketing division, architecture, generation, and VIN model year.
Source systems by business subject
VPxVIN combines regional transaction systems, global product identity, dealer geography, standard cost, incentives, material cost, and event data.
| Subject area | Key sources |
|---|---|
| Product attributes | GVIT, with supporting legacy/regional inputs such as VIC where applicable |
| Dealer geography | GMDID, with GIANT or C005 in selected regions |
| Sales order | Venus, GVSOM/BARS, DOMS for Korea, VIC/C001 in inactive regions |
| Revenue | VBARS, OTD-S, GIANT for Korea, C005/SAP regional sources where applicable |
| Incentives | VBARS, VISTEX, UMF, OTD-S, GIANT/SAP regional sources where applicable |
| Material and standard cost | S4GL, UMF, GPPS / eGPPS, and related standard-cost processes |
| Events | VID, DOMS/Venus/GIANT for Korea, and regional legacy systems |
| Sales channel | VBARS, VID, OTD-S, GIANT, and regional channel assignment sources |
Argentina and Brazil appear in historical source mappings, but UMF data for those markets has not been maintained for several years and they are not treated as active VPxVIN deployments.
Business measures and eligibility
VPxVIN profitability centers on a repeatable P&L structure:
Gross Revenue = Model Net + Option Net + Destination Freight Charges
+ Other Invoice Additions + Other Revenues
+ Tax Benefit/Loss + Loss on PEP
- Exclusion to Model Net
Net Sales and Revenue = Gross Revenue - Sales Allowances
Variable Profit = Net Sales and Revenue
- Material Cost
- Standard Cost
- Variable Manufacturing Expense
VP Before Incentives = Variable Profit - Sales Allowances
A VIN is eligible for VP calculations only when all five conditions are met:
- Model Net is greater than zero.
- Direct Material or Purchased Vehicle Cost is available.
- At least one required standard-cost component is available, such as Freight, Policy & Warranty, or Variable Manufacturing Expense.
- A valid end-customer delivery date is present.
- A valid sales channel is assigned.
The VP_ELIG_FLG eligibility flag captures these criteria and should be used in profitability analysis.
Reporting and analytics interfaces
VPxVIN is exposed through multiple interfaces so users can work at the right level of detail.
| Interface | View of the data | Primary use cases |
|---|---|---|
| Finance360 | Finance search, dashboard cards, and guided application access | Business discovery, dashboard visibility, and Finance application entry point |
| Power BI semantic models | Summary views for self-service BI | Trend analysis, dashboard creation, executive and team reporting |
| Excel semantic model access | Pivot-style summary analysis | Finance analyst exploration and recurring business analysis |
| Cognos standard reports | VIN-level and summary reports | Packaged reporting, anomaly investigation, and downloadable extracts |
| Cognos Workspace Advanced | VIN-level and summary ad-hoc views | Custom analysis for experienced report users |
| Databricks / Genie | Conversational and SQL-based analytics | Engineering exploration, advanced analysis, and validated data-product access |
Common VPxVIN dashboard and reporting experiences include VP Performance, Incentive Analysis, Option Mix / Option Analysis, Fleet Analysis, EightBox reporting, VIN Profitability Detail, VIN Lookup, and Fleet Profitability.
Dashboards and semantic models generally refresh daily by 2 PM Eastern. Semantic model snapshots refresh Sundays by 2 PM Eastern. Cognos standard reports and WSA ad-hoc reporting packages refresh daily.
Finance360 relationship
Finance360 is part of the current VPxVIN operating surface. It is not a replacement for VPxVIN; it is an application layer that helps users discover finance insights, access dashboards, and interact with Finance Data Engineering capabilities.
For VPxVIN, Finance360 is relevant in four ways:
- It provides a visible business entry point for finance search, dashboard access, and guided analytics.
- It surfaces VPxVIN-related experiences such as YTD delivery volume and Finance Agent interactions.
- It supports the broader modernization of Finance analytics onto Data Mesh and Databricks-backed platforms.
- It is connected to ongoing work around VPxVIN user-maintained file intake and operational workflows.
Downstream consumers
VPxVIN feeds a broad finance and analytics ecosystem. Known downstream consumers include:
| Consumer | How VPxVIN contributes |
|---|---|
| GDAAS-GSSM | Sales and marketing analytics consumption |
| CPURAM | Profitability and revenue analytics consumption |
| RVM | Residual value / remarketing-related analytics consumption |
| IOT | Vehicle and connected analytics consumption |
| DRMO | Dealer, retail, and market operations analytics consumption |
| Event 360 | Vehicle event and delivery analytics consumption |
| Controllership Cube | Finance reporting and controllership consumption |
| OrCA | Finance analytics consumption |
| Envolve | Commercial fleet and product profitability context |
| DSE | Legacy / historical analytics dependency and migration context |
Security and access model
VPxVIN uses tiered security so finance and non-finance users can work from the same data foundation with the right level of detail.
| Security level | Intended audience | Financial visibility | Detail level |
|---|---|---|---|
| Level 1 — Unrestricted Super User | VSSM Finance power users | Complete profit account hierarchy | VIN-level detail, custom ad-hoc report saving |
| Level 2 — Unrestricted | VSSM Finance | Complete profit account hierarchy | VIN-level detail |
| Level 3 — Limited | VSSM users | Summary metrics such as VP, VP before incentives, gross revenue, sales allowances, net sales, variable cost, and MSRP | Aggregate detail |
| Level 4 — Controlled Sales Allowance | VSSM users with limited finance need | Sales allowances and MSRP-focused visibility | Aggregate detail |
Access is also constrained by selling organization, GM selling entity, and NSC region. Users only see data populated for the regions and entities they are approved to view. Security approval is granted by the appropriate country or regional VSSM finance approver.
Getting access
Report access starts from the Finance360 access page.
- Open
https://gmone.gm.com/programs/finance/global/en/gm/home/finance360-get-access.html. - For What Do You Need Access To?, select VPxVIN.
- Select the report of interest.
- Follow the displayed steps to continue to the required myGMAccess request.
- Provide a business justification that explains the VPxVIN analysis or reporting work being performed.
- After approval, validate access through the relevant reporting interface.
For direct query access, use the VPxVIN data product in Immuta: https://app.immutacloud.com/marketplace/data-product/b2aa932f-3694-470c-a18c-42efbddd928f/details.
For current business, Finance IT, and Finance Data Engineering support contacts, use the VPxVIN Wiki, Finance360 portal material, current operating pages, and VPxVIN Teams channel. Regional VSSM finance approvers support access approval questions for their markets.
Where the data lives
The certified gold serving layer is:
finance_prod.gold_vehicle_profit_gbl
New users should usually start with vp_analytics_f, which is the analytics-ready VIN-level fact. It is designed for profitability analysis where product, dealer, geography, channel, event, and financial measures are already brought together.
For most business analysis, use VPxVIN semantic models, Power BI dashboards, Finance360 experiences, or vp_analytics_f before moving into lower-level transaction tables.
Popular tables and views
These are the most useful objects to recognize when getting started. They are listed for orientation, not as a complete schema guide.
| Object | What it is used for |
|---|---|
vp_analytics_f | Best starting point for VIN-level profitability analytics; combines financials, product, channel, dealer, and geography context |
veh_profit_f | Atomic P&L fact used for detailed profit account analysis and engineering investigations |
vehicle_revenue_f | Revenue fact used to understand wholesale invoice revenue and amount-type detail |
vehicle_cost_f | Cost fact used to investigate vehicle material cost, standard cost, and cost components that feed profitability analysis |
incntv_pymt_f | Incentive payment fact used for incentive spend and program effectiveness analysis |
veh_whlsl_inv_event_m | Wholesale invoice event master used to understand invoice timing and event context |
veh_cust_deliv_evnt_m | Customer delivery event master used for delivery and eligibility context |
veh_sales_chnl | Sales channel classification used to compare retail, fleet, employee, lease, APR, commercial, rental, and government behavior |
nsc_h | National Sales Company hierarchy used for regional and security-aware analysis |
sales_chnl_h | Sales channel hierarchy used for summary channel reporting |
profit_acct_h | Profit account hierarchy used to interpret gross revenue, cost, sales allowance, and variable profit rollups |
fleet_cust_d | Fleet customer dimension used for fleet account analysis |
vp_8_box | EightBox segmentation used in summary profitability and sales-channel reporting |
Practical guidance for engineers
- Start with
vp_analytics_ffor most analytical work. - Use the
VP_ELIG_FLGflag when calculating or filtering variable profit. - VIN values are masked by default; request the appropriate plain-text access only when the business use case requires raw VINs.
- Financial amount columns commonly appear in USD, functional currency, and NSC/local currency variants.
- Use lower-level tables such as
veh_profit_f,vehicle_revenue_f,vehicle_cost_f, andincntv_pymt_fwhen investigating source logic, reconciliation, or pipeline behavior.
Product hierarchy reference
The Super Six are the six GVIT attributes that define the standard product hierarchy used across core planning and forecasting platforms:
- Marketing Division
- Global Brand / Local Brand / Segment
- Body Style
- Global Trim
- Architecture / Generation
- VIN Model Year
Common option and product identifiers include:
| Code | Meaning |
|---|---|
| RPO | Regular Production Option — standard factory option code |
| SEO | Special Equipment Option — non-standard or dealer-added option |
| UMD | Uniform Model Designator — engineering-release identifier for a vehicle configuration |
Getting started path
Work through these steps to become productive with VPxVIN:
- Read the business overview, core subject areas, eligibility rules, and reporting-interface sections in this document.
- Review VPxVIN 101 and the VPxVIN Reference deck from the VPxVIN Wiki.
- Confirm access through myGMAccess and the relevant reporting interface.
- Explore Finance360, the VPxVIN dashboard experiences, and available semantic models before writing custom SQL.
- Use
vp_analytics_ffor a first Databricks exploration of VIN-level profitability. - Review the product hierarchy and option-code concepts so technical columns map back to business vocabulary.
- Move into lower-level tables only when investigating reconciliation, pipeline behavior, source-system logic, or detailed profit-account questions.
Reference links
| Resource | URL |
|---|---|
| Finance360 | https://finance360.gm.com |
| Finance 360 VPxVIN portal | gmone.gm.com/programs/finance/global/en/gm/home/vpxvin.html |
| VPxVIN Wiki / VPxVIN 101 | https://generalmotors.sharepoint.com/sites/vpxvinwiki |
| VPxVIN One-Pager | https://gm-sdv.atlassian.net/wiki/spaces/IT/pages/644514420 |
| VPxVIN Genie space | go/vinny |
| Atlan catalog entry | finance_prod.gold_vehicle_profit_gbl |
| VPxVIN GitHub repo | GeneralMotors-IT/VPxVIN_121243_FIN_PaaS_VPxVIN |
| Databricks workspace (prod) | adb-2487737680686229.9.azuredatabricks.net |
| myGMAccess | myaccess.gm.com |
| VPxVIN Teams channel | Search VPxVIN in Teams |