VMF Engine & Configurator: Hierarchies & Unions FAQ Xvantage for Associates

Summary:

A VMF Configuration file may contain fields tied to a Vendor, Product Category, Vendor Program, VPN, or a combination. This FAQ article offers a summary of the Hierarchies and Unions within the VMF Engine & Configurator.

Table of Contents:

1. How does the VMF Engine determine which vendor‑mandatory fields appear on an order?

2. What are the two options in hierarchies and unions?

3. How do product categories (Option 1) work in a VMF Configuration?

4. How do Vendor Programs and VPNs (Option 2) work in a VMF Configuration?

How does the VMF Engine determine which vendor‑mandatory fields appear on an order?

Answer: A VMF Configuration file can include vendor‑required fields tied to a Vendor, Product Category, Vendor Program, VPN (Vendor Part Number), or a combination of these. The vendor‑level configuration acts as the parent or baseline, and all other configuration levels are linked to it, creating a hierarchy. When a reseller places an order, the VMF Engine finds all applicable VMF fields for the product and combines them into a single Vendor Required Information (VRI) screen—this process is called a union. The required fields are then completed using auto‑fill where available, or by a user manually entering values before the order can proceed.

What are the two options in hierarchies and unions?

Answer: (Option 1) Product Categories and (Option 2) Vendor Programs and VPNs.

How do product categories (Option 1) work in a VMF Configuration?

Answer: Product category–based VMF configurations allow vendor‑required fields to be assigned at different levels of a product hierarchy to ensure the right data is collected. Product categories are structured into three hierarchical levels, where Level 2 is a subset of Level 1, and Level 3 is a subset of Level 2.

For example, an associate may select Product Category – L1: Services/Warranties, L2: Warranties, and L3: Warranties to narrow the scope. VMF fields can then be added at any level in the hierarchy using the Header or Line Field options. When an order is placed, the VMF Engine evaluates the category hierarchy and includes the applicable fields on the VRI screen, ensuring all required information is captured based on the selected product category.

How do Vendor Programs and VPNs (Option 2) work in a VMF Configuration?

Answer: VMF configurations can be created at the Vendor Program and Vendor Part Number (VPN) levels to capture vendor‑required data for specific offerings. Associates select a Vendor Program (for example, SENTINELONE), then choose the applicable Product VPN (such as DR90‑10K1‑CP‑12). VMF fields can be added at any level—vendor program or VPN—using the Header or Line Field options. When an order is placed, the VMF Engine evaluates these configurations and includes the relevant fields on the VRI screen, ensuring accurate data capture for program‑ or product‑specific requirements.