Unique identifier for the sales transaction record.

System-generated global identifier used to reference the transaction across Vault instances.

System-generated link to directly access the sales transaction record within the Vault application.

Name or title of the sales transaction, typically representing the transaction event or purpose.

Current status of the sales transaction, such as Draft, Approved, or Completed.

User who initially created the sales transaction record.

Date and time when the sales transaction was first created.

User who last modified the sales transaction record.

Date and time of the most recent update to the sales transaction record.

Custom metric B100 associated with the transaction, potentially used for financial or performance tracking.

Custom metric B101 tied to the transaction, which can represent a pricing, quantity, or adjustment value.

Custom numeric field B102 for capturing transaction-specific data, such as discount rates or unit costs.

Numeric field B103, used for custom calculations or business metrics related to the transaction.

User-defined field B104, commonly used to track monetary values or internal scoring.

Numeric field B105, potentially used to represent tax, markup, or volume-related values.

Field B106 stores custom quantitative data tied to the sales transaction process.

Custom metric B107, typically configured for analytics or operational tracking.

User-defined numeric value B108 related to transaction performance or classification.

Custom field B109 used to store additional computed or imported financial data.

Legacy or system-specific metric B10, can represent a subtotal or line-level amount.

Custom data point B110, configured for a business rule or workflow logic.

User-configurable metric B111, used for validation or reporting calculations.

Numerical value B112 designed for transaction-specific analytics or summarization.

Custom field B113 storing numeric details related to transaction categorization.

Metric B114, likely used for tracking amounts, rates, or quantities in a transaction.

Numeric field B115 supporting business-specific reporting or segmentation.

Calculated or user-entered value B116 representing transaction metadata or detail.

Field B117 reserved for custom extensions to the transaction model.

Final numeric metric B118 used in sales transaction analytics, validation, or documentation.

Represents the transaction amount or quantity for item or metric code B119, typically used in performance or sales reporting.

Contains the numerical value associated with item or indicator B11, which can represent a specific sales volume or metric.

Stores the value for sales metric B120, potentially used for regional or category-specific reporting.

Numeric field capturing data related to B121, possibly tied to transactional performance or product-specific statistics.

Reflects data for sales indicator B122, which can denote a particular sales phase or customer segment metric.

Holds the calculated value for B123, typically representing detailed breakdowns in transaction-level data.

Includes metric data under code B124, often used for analytical tracking of sales performance.

Captures the recorded value for B125, likely representing sales effectiveness or call outcome metrics.

This is used to store the double-precision value for B126, possibly linked to a time-based or region-specific transaction count.

Contains numerical data for B127, which can be related to incentive tracking, goals, or performance KPIs.

Stores sales-related information under code B128, often used in advanced analytics or trend analysis.

Numeric field representing the value of B129, potentially tied to compliance tracking or activity-based scoring.

Reflects transaction data or metric value under B12, possibly summarizing totals or sales rep performance.

Represents a calculated or input value for B130, frequently used in sales dashboards or reporting models.

Represents metric B131, a numerical field likely used to capture a sales-specific quantitative attribute such as product units, order volume, or regional allocation data.

Contains the B132 metric value, which can reflect a financial figure, performance indicator, or transactional count relevant to sales activities.

Stores the B133 value, potentially representing a derived or calculated measure within a sales reporting context such as average units sold or commission amount.

Captures the B134 metric, typically associated with secondary sales data points like adjusted totals or returns.

Tracks B135, a numeric value possibly linked to discount rates, product availability scoring, or quota fulfillment.

Represents B136, which can relate to the conversion rate or sales penetration for a particular product or segment.

Holds the B137 value, often tied to business intelligence KPIs such as regional performance indexes or campaign-level metrics.

Numeric field B138, which can denote revenue contribution or a target achievement percentage in the context of sales.

Captures B139, a metric that could be used for measuring productivity, engagement level, or cross-sell ratios.

Represents the B13 numeric indicator, a foundational metric used across sales reports or dashboards for aggregating performance.

Stores the B140 field, likely related to revenue targets, sales incentives, or market share tracking.

Contains B141, a sales data metric often used to calculate trend analysis or year-over-year growth.

Captures B142 values that might reflect tiered pricing impact, demand variance, or product ranking scores.

Represents the B143 numeric indicator, potentially associated with internal benchmarking or compliance metrics.

Tracks B144 values that can be utilized for operational forecasting or incentive payout modeling.

Holds the B145 metric, typically tied to performance thresholds, deal closure ratios, or sales velocity.

Stores B146, which can represent a cumulative or weighted value used in executive reporting or sales analysis models.

Represents the total number of product samples distributed during the transaction, as recorded in field b147__v.

Indicates the total monetary value of all samples distributed, helping track high-value transactions via b148__v.

Captures the total volume or units sold in this transaction, aligned with field b149__v for inventory movement tracking.

Reflects a custom metric such as a transaction discount or adjustment factor, tied to field b14__v.

Denotes the number of Healthcare Professional (HCP) engagements linked to this sales event, stored in b150__v.

Records the number of promotional materials shared during the sales call, as captured in b151__v.

Measures the duration of the sales call or interaction in minutes, tracked using b152__v.

Represents a performance score or effectiveness rating of the transaction, calculated and stored in b153__v.

Indicates the percentage of the sales target achieved in this transaction, logged in b154__v.

Stores the bonus eligibility or earned incentive value for the sales rep related to this transaction, in b155__v.

Reflects a compliance score or audit metric for the sales interaction, recorded in field b156__v.

Captures the number of product variants discussed or presented during the transaction, noted in b157__v.

Represents the customer satisfaction score, usually gathered post-transaction, and stored in b158__v.

Denotes the count of follow-up actions scheduled or completed as part of this transaction, from field b159__v.

Captures a transaction-specific metric such as co-promotion indicator or marketing tag value, using b15__v.

Logs the number of samples returned, exchanged, or adjusted post-transaction, recorded in b160__v.

Metric B161: Captures the total monetary value of promotional samples distributed during the transaction period, used for compliance and tracking.

Metric B162: Represents the calculated average spend per territory associated with this transaction entry, typically used in sales performance evaluations.

Metric B163: Indicates the total volume of product units transferred in this transaction, reflecting operational throughput.

Metric B164: Tracks the return quantity of distributed items for reconciliation and loss prevention purposes.

Metric B165: Denotes adjusted gross revenue after discounts have been applied to the original transaction value.

Metric B166: Captures total tax applied to the transaction, including both sales and regulatory taxes where applicable.

Metric B167: Represents the amount attributed to shipping and handling fees included in the transaction.

Metric B168: Reflects the number of interactions recorded with healthcare providers in connection to this transaction.

Metric B169: Summarizes the number of samples requested in follow-up to this transaction by the receiving party.

Metric B16: Historical field retained for compatibility with legacy reporting systems, can represent deprecated or transitional values.

Metric B170: Reflects the cumulative value of bonuses or incentives issued to field reps based on this transaction's metrics.

Metric B171: Tracks calculated cost-per-call derived from field activity linked to the transaction.

Metric B172: Indicates the number of products with low inventory thresholds triggered during this transaction.

Metric B173: Denotes compliance score assigned to the transaction based on regulatory guidelines or internal policy.

Metric B174: Captures transaction-level flags for audit review, quality assurance, or data verification processes.

Metric B175: Stores calculated forecast accuracy by comparing expected vs. actual sales performance in this transaction.

Metric B176: Represents internal risk rating or alert level assigned based on transaction irregularities or anomalies.

Custom field B177 capturing a numeric sales-related metric specific to transaction audits or performance tracking.

Custom field B178 used to store calculated values related to pricing, discounts, or financial adjustments during a sales transaction.

Custom metric B179 that can reflect inventory counts, batch-level totals, or regulatory compliance data in sales workflows.

Field B17 typically stores a numeric value such as a transaction score, risk factor, or forecast indicator.

Custom field B180 potentially representing volume-based sales data, quantity multipliers, or promotional impact figures.

Numeric field B181 tracking partner-related revenue shares, sales commissions, or allocation metrics.

Field B182 used to record detailed numeric inputs such as expected delivery counts, sample allocation, or sales thresholds.

Custom field B183 capturing structured financial metrics, such as invoice discrepancies or tax computations tied to a transaction.

Field B184 used in transaction analytics to quantify customer-level segmentation or campaign responsiveness.

Numeric field B185 storing reporting-specific values like year-over-year sales change, margin variances, or product-level benchmarks.

Custom metric B186 used for internal tracking of SLA adherence, delivery turnaround time, or fulfillment rates.

Field B187 likely designed to store sales scorecards, transaction-based evaluations, or compliance checkpoints.

Field B188 represents numeric inputs linked to budget allocations, sales planning, or incentive payout estimations.

Custom field B189 tracking operational performance metrics such as distribution accuracy, region-based performance, or logistics delays.

Field B18 typically holds a transaction-level numeric identifier, such as a sales stage progress index or milestone achievement score.

Custom numeric field B190 designed for advanced reporting calculations, potentially involving weighted averages or predictive scoring models.

Represents the numeric value associated with transaction attribute B191, which can correspond to a specific sales metric or internal identifier used in revenue tracking.

Numeric field capturing the value for B192, potentially indicating a secondary measurement related to the sales transaction such as a bonus, tax, or adjustment.

Stores a quantitative detail for field B193, likely representing a transaction-specific calculation such as margin, rate, or allocation.

Denotes the value of field B194, which can be used to represent a special condition, conversion factor, or auxiliary amount in the context of a sales event.

Holds the numerical data for B195, potentially a derived figure such as prorated cost, distributed revenue, or tier-based value.

Reflects the value associated with B196, which might correspond to an internal system flag, quota metric, or adjusted transaction score.

Captures the transaction-specific amount for B197, possibly indicating regional variance, cost override, or incentive payout.

Numeric representation of B198, which can be a result of business logic related to rebates, net sales, or promotion deductions.

Stores the double-precision number for B199, used potentially for performance indicators, ROI calculations, or transactional benchmarks.

Represents a key numeric value from field B19, often linked to legacy codes or standardized values used across historical transaction records.

Core transaction amount or indicator labeled as B1, possibly representing the primary sales figure or unit price in the transaction dataset.

Captures the calculated or input value for B200, often used for extended transaction attributes such as total discount or customer ranking score.

Stores the value of B201, which can represent estimated impact, strategic forecast data, or pipeline-derived contribution.

Numeric field for B202, likely associated with transaction metadata such as sales channel weight, allocation ratio, or uplift factor.

Holds the double value for B203, potentially tied to regulatory reporting, audit scoring, or CRM-influenced transaction weight.

Represents the value stored in B204, which could be relevant for compliance factors, exception tracking, or procedural adjustments.

Numeric data field for B205, which can reflect a concluding metric in the sales transaction pipeline, such as final evaluated value or quality assurance adjustment.

Represents a numeric metric associated with transactional performance, possibly a sales efficiency or conversion ratio indicator.

Quantitative value capturing a specific financial detail within the sales transaction, potentially related to rebates or discounts applied.

Holds a decimal-based value likely corresponding to tax adjustments or a calculated financial offset applied to the sale.

Stores a numerical code or measure used to segment transaction categories, such as region or product type.

Captures the unit cost or price per item sold in a given sales transaction.

Represents the total quantity of units sold for the item within the transaction record.

Reflects the gross transaction amount prior to discounts, taxes, or adjustments.

Indicates the discount applied to the transaction, recorded as a numeric value.

Represents tax or VAT calculated for the transaction line item.

Final amount after applying discounts and taxes, serving as the net transaction value.

Tracks the commission or incentive value earned for this transaction line.

Contains the budget allocation value from the marketing or sales budget attributed to this transaction.

Numeric field used for auditing purposes, potentially tracking internal validation scores or system checks.

Stores the transaction sequence or priority index, helping define order or processing logic.

Represents a custom financial calculation applied to the transaction, such as margin or profitability ratio.

Captures an adjustment or correction applied post-transaction, used for financial reconciliation.

Captured numeric value representing sales-related attribute B32, typically associated with customer-specific transaction metrics.

Numeric value for B33, which can correspond to calculated revenue figures or performance thresholds tied to a sales operation.

Represents a transaction-specific metric B34, often used in the context of sales event logging or reporting analysis.

Quantitative field used to track value B35, which could relate to inventory movement, sales volume, or pricing adjustments.

This is used to store financial or operational figures labeled as B36, such as sales discounts, surcharges, or allocation ratios.

Reflects a transaction factor B37, commonly used for internal reporting on customer engagements or product performance.

This column tracks metric B38, typically linked to promotional effectiveness, sales representative output, or regional performance.

Stores numeric value B39, which could indicate invoice totals, rebate amounts, or internal adjustment coefficients.

Represents base metric B3, frequently used in legacy transaction tracking or as a foundational sales data component.

Contains figure B40 related to secondary financial indicators like commissions, bonuses, or channel-specific allocations.

A value representing attribute B41, often associated with client groupings, specialty campaign results, or offer tracking.

Sales transaction field B42, possibly referencing currency conversions, unit sales in bundles, or performance indexing.

This is used for tracking operational metric B43, which can pertain to delivery compliance, logistics KPIs, or distribution effort.

Stores measurement B44, likely related to territory-based performance analysis or vertical market segmentation outcomes.

Numeric representation of B45, which can support audit trail evaluations, escalation flags, or workflow scoring.

Captures quantitative detail B46, possibly associated with VAT, tax implications, or pricing tier differentiation.

Represents transaction variable B47, generally used for special case sales activities, such as incentive qualification or exception handling.

Custom numeric field B48, often used to capture a transaction-specific metric such as discount rate or secondary commission amount.

Custom numeric field B49, which can represent an override value, rebate percentage, or similar sales adjustment metric.

Custom numeric field B4, typically configured to store region-specific sales figures or a derived calculation based on quantity and unit price.

Custom numeric field B50, often used to store a calculated field such as promotional value, bonus allocation, or pricing variance.

Custom numeric field B51, potentially representing a secondary sales performance indicator or territory-based sales quota.

Custom numeric field B52, likely capturing transactional costs such as shipping fees, handling charges, or packaging expenses.

Custom numeric field B53, used to track supplementary sales data such as adjusted net value or customer-level adjustments.

Custom numeric field B54, intended to hold alternate revenue figures such as exchange rate-adjusted revenue or tax-adjusted amounts.

Custom numeric field B55, capturing metrics linked to customer engagement levels or incentive-based volume tiers.

Custom numeric field B56, which can be used to hold data for time-sensitive sales elements like flash discount totals or campaign spend.

Custom numeric field B57, used for tracking metrics tied to digital sales channels, such as app-based transactions or website-specific revenue.

Custom numeric field B58, which could reflect legacy import values, conversion-adjusted amounts, or integration-transferred data.

Custom numeric field B59, generally used for customized reporting, capturing data like forecast overrides or market simulation outcomes.

Custom numeric field B5, commonly used in sales performance reports, potentially representing a fixed monthly quota or benchmark value.

Custom numeric field B60, used for high-level rollup data such as quarterly aggregate sales or pipeline-weighted projections.

Custom numeric field B61, capturing transaction-level statistics such as sales effectiveness ratios or conversion efficiency scores.

Custom numeric field B62, frequently configured to log adjustment factors, refund percentages, or tolerance thresholds.

Custom numeric field B63, used to represent grouped transaction data such as cluster-level totals or territory aggregates.

Custom numeric field B64, often applied to quality control or audit checks, capturing calculated discrepancies or flags.

Custom numeric field B65, potentially used to hold compliance scores, customer satisfaction metrics, or audit result indicators.

Represents the total discount amount applied to the transaction before tax calculations.

Indicates the final invoice value after applying all discounts and taxes.

Captures the unit cost of the product or service sold in the transaction.

Reflects the total quantity of items returned or reversed in this transaction.

Internal metric B6 used for pricing adjustment calculations based on territory or customer tier.

Represents the applied tax percentage or rate used in the transaction.

Captures the net payable amount post all adjustments including discounts and taxes.

Denotes the shipment cost incurred for fulfilling this particular transaction.

Holds the promotional discount percentage if the sale was part of a campaign.

Tracks the revenue contribution from this transaction toward monthly sales goals.

Represents an internal risk score or confidence factor associated with this transaction.

Indicates the average deal size in which this transaction falls, based on historical ranges.

Captures the transaction margin percentage based on cost vs. invoice value.

Stores adjustment values due to late payments, refunds, or invoice corrections.

This is used to represent the weighted revenue impact for sales compensation calculations.

Internal metric B7 tracking customer engagement level during the sales cycle.

Captures the sales channel ID through which the transaction was executed, such as direct, partner, or digital.

Indicates the calculated customer lifetime value contribution derived from this sale.

Represents the discount percentage applied to the transaction, often used for promotional pricing analysis.

Captures the final net price after all discounts, rebates, and adjustments have been applied.

Indicates the wholesale acquisition cost (WAC) at the time of the transaction, used for market comparisons.

Specifies the cost of goods sold (COGS) for the item in this transaction, contributing to profitability metrics.

Shows the markup amount added to the base cost to derive the list price for the transaction item.

Reflects the reimbursement amount expected from third-party payers or insurance entities for this sale.

Denotes the government price ceiling relevant to the item, ensuring compliance with regulatory price limits.

Tracks the total taxes applied to this transaction, including local, state, and federal taxes.

Stores a custom business-specific metric, such as internal performance scoring or incentive triggers.

Measures the quantity sold in standard units, providing input for forecasting and sales performance tracking.

Indicates the number of free or bonus units included in the transaction, commonly used in sampling programs.

Represents the sales territory multiplier, used for crediting sales teams based on regional contributions.

Contains the calculated gross margin for the transaction, derived from price and COGS differentials.

Holds the standard price before any customer-specific or market-based adjustments are applied.

Captures the actual invoice amount paid by the customer, post-discounts and returns.

Stores the internal revenue code or classification tied to this transaction for accounting purposes.

Reflects the percentage of transaction cost attributed to logistics and distribution overhead.

Indicates the volume-based rebate or credit earned as part of a larger purchasing agreement.

Captures the deferred revenue portion from this transaction, relevant for multi-period revenue recognition.

Internal numeric identifier used for reference or system-specific computations within the sales transaction dataset.

Geographical segmentation code, commonly used in pharmaceutical sales to define territories for sales reporting and analysis.

Identifier for a subordinate or related entity, such as a sub-account or dependent product, linked to the parent record.

Indicates the source or type of channel through which the sales data was collected, such as retail, mail order, or specialty pharmacy.

Secondary unique identifier for the transaction or record, often used in legacy systems or integration processes.

Specifies the healthcare market or therapeutic area in which the transaction took place, used for segmentation and analytics.

Unique identifier assigned to the insurance payer or benefit provider responsible for reimbursing the transaction.

Name or identifier of the specific insurance or benefit plan associated with the payer, used to distinguish between multiple plans under the same payer.

Categorization of the product involved in the transaction, grouping similar medications or treatments for reporting purposes.

The descriptive name of the sales territory associated with the transaction, used for sales force alignment and performance tracking.

Specifies the classification or nature of the transaction, such as new, refill, adjustment, or sample.

Postal ZIP code indicating the geographic location related to the transaction, typically of the prescribing provider or dispensing pharmacy.

Vault-specific owner ID referencing the user or process that owns or submitted the transaction record.

Identifier carried over from a previous Customer Relationship Management (CRM) system, used to map historical data to the current Vault record.