§0 — How to read the confidence tags
Every term is tagged so you don’t over-trust a definition:
[confirmed]— the term came straight from an interview (Lonny, Alex Zhu, or Greg)[standard]— a standard SAP/logistics/Salesforce term I’m mapping onto our context[inferred]— an NVIDIA-custom code where I’m inferring meaning from naming convention, not from an explicit definition in the vault
The five shakiest — ZMRR, ZMFG, ZMRA, ZRMA, WHI — are NVIDIA-internal codes where I’m inferring from SAP’s Z-namespace convention and surrounding process. Confirm those with Alex/Greg before quoting them.
§1 — Systems of record
- SFDC — Salesforce.com.
[confirmed]NVIDIA’s customer-facing order-management and case-management system. Where an RMA case is opened, warranty entitlement and serial # are validated, and the standard-vs-Advance-Replacement disposition is recorded. Effectively NVIDIA’s CRM sitting in the slot SAP SD would otherwise fill. - control tower software
[confirmed]— An orchestration/visibility layer above the transactional systems, giving end-to-end tracking of a unit as it moves customer → warehouse → CM → back to spares. NVIDIA’s core visibility gap on the customer and CM legs is what a control tower is meant to close. - ODP data lake
[confirmed, name partial]— NVIDIA’s backend data store / data lake (“ODP” is their internal name). The intended single source of truth the planning and control-tower layers would read from, versus today’s emails and spreadsheets. - SSO / SSO portal
[standard]— Single Sign-On. The authentication front door to NVIDIA’s internal portals (the ZMRR portal, SFDC, etc.) — one federated login across the toolset.
§2 — SAP landscape (ECC, modules, Z-transactions)
NVIDIA is mid-migration on SAP and paying SAP $2M+ to automate the planning layer. Custom NVIDIA transactions are prefixed Z (SAP’s reserved namespace for customer-defined transaction codes), so the Z-codes below are NVIDIA-built, not stock SAP.
- ECC
[standard]— SAP ERP Central Component, the classic on-prem SAP ERP (predecessor to S/4HANA). NVIDIA’s ERP back end for material planning/finance. - EWM
[confirmed]— Extended Warehouse Management. SAP’s warehouse module (goods receipt, put-away, storage, dispositioning). Rolling out now; also being pushed into 3PL partners. - TM
[confirmed]— Transportation Management. SAP’s module for planning/executing freight and carrier moves (the Expeditors 3PL legs, inbound and outbound). - TMS
[confirmed]— Transportation Management System — the generic-category name for the same capability, used interchangeably with “TM” in our notes (“WMS + TMS rolling out now”). - ECC + TM/EWM
[confirmed]— Shorthand for the target SAP stack: the ECC ERP core with Transportation and Extended Warehouse Management bolted on to run the physical reverse-logistics flow. - SCM
[standard]— Supply Chain Management (both the discipline and SAP’s SCM product family — planning, EWM, TM historically live here). - SFC — Shop Floor Control
[standard]— The manufacturing-execution layer that tracks a unit through the repair/build steps on the CM’s shop floor (work orders, WIP status, operation-level completion). Adjacent to “Clear to Build.” - A-RMA / ZRMA
[confirmed / inferred]— A-RMA = Advance RMA / Advance Replacement (ARMA): NVIDIA ships a good replacement before the defective unit returns, so the customer’s data center keeps running[confirmed]. ZRMA is the SAP Z-transaction that executes the RMA in the ERP[inferred]. - ZMFG / ZMRA
[inferred]— NVIDIA-custom SAP transactions. ZMFG ≈ the manufacturing/repair-build transaction. ZMRA ≈ a manufacturing/return-authorization variant. Z-namespace custom codes; exact scope not pinned in the vault — confirm. - ZMRR portal process
[inferred]— An NVIDIA-custom, portal-driven workflow (Z-transaction fronted by a web portal, reached via SSO), most plausibly the material-return/receipt routing that governs how a returned unit is logged and dispositioned. The “ZMRR” expansion is not confirmed — flag for verification.
§3 — Process, document, and identifier terms
- RMA — Return Merchandise Authorization
[confirmed]— The industry term and the whole workflow: customer requests to send a failed unit back; NVIDIA authorizes, replaces, repairs, and returns the repaired unit to the spares pool. <1% of RMAs are ever rejected — the approval gauntlet is latency, not a filter. - SLA — Service Level Agreement
[standard]— The contractual performance promise (e.g., replacement ship-by time). Here it’s the clock behind Advance Replacement — can ops commit to the ship date? Ties to Available-to-Commit. - DC — Distribution Center
[confirmed]— The warehouse node where a customer shipment is received and dispositioned (“customer shipment intake, receipt at distribution center”). Run by the 3PL (Expeditors, which replaced Omni). The receiving DC is where the ASN should land. - QA approval / QA gate
[confirmed]— The quality gate in the three-gate pre-shipment sequence (case management → quality → finance). Part of the ~1–2-week gauntlet that rejects <1% of RMAs — adds latency, doesn’t filter eligibility. Unknown failure codes route to the failure-analysis lab. - non-conformance
[standard]— A unit or part that fails to meet spec/quality on inspection — the QA finding that routes something out of the normal flow (to FA lab, rework, or scrap). Rare here given the <1% rejection rate. - shipment vs reshipment
[standard]— Shipment = the initial outbound move (the replacement going to the customer). Reshipment = a subsequent move of the same or corrected unit (re-send after a return, mis-ship, or the repaired unit going back into circulation). Matters for who pays freight and how it’s coded in TM. - IB shipments
[standard]— Inbound shipments: the return legs coming into NVIDIA/the DC (the defective unit, or CM-to-warehouse moves), as opposed to outbound replacements. The inbound leg is where ASN/EDI visibility is weakest today. - EDI — Electronic Data Interchange
[confirmed]— Standardized machine-to-machine document exchange between NVIDIA and its warehouse/carriers. NVIDIA is turning on automated ASN via EDI (outbound ASN to the warehouse + a receipt-acknowledgment EDI back) to replace “emails and papers — really bad” (Alex, 2026-05-27). - ASN / PRE-ASN solution
[confirmed]— ASN = Advance Shipping Notice: an electronic “here’s what’s arriving, when, with these serials” message sent ahead of a physical shipment so the receiving DC can expect and reconcile it. Today it isn’t flowing properly. A PRE-ASN solution generates/pushes that notice before dispatch, pre-populating the receiving side so intake isn’t a surprise. - WHI Ticket
[inferred]— A warehouse/inbound ticket — the work item raised at the DC to receive and disposition an arriving unit. The “WHI” expansion isn’t confirmed in the vault; treat as the warehouse-side receiving/inspection ticket and confirm. - component serial number hierarchy
[confirmed]— The parent-child structure of serials: a system/board (top-level serialized asset, e.g., an HGX/GPU tray) contains component-level serialized parts (GPUs, HBM stacks, switches) beneath it. Tracking which child serials sit inside which parent is what lets NVIDIA validate entitlement and trace a failure — exactly what breaks when telemetry is wiped and consignment counts run on “suspect sheets.” - asset management in SFDC / data rationalization
[confirmed]— Keeping the installed-base / asset records in Salesforce accurate (which serial is where, under what warranty, owned by whom) and reconciling conflicting versions of that truth across systems (“data rationalization”). Same root pain as cycle counting one level up — you can’t commit or route confidently on untrustworthy asset data, and NVIDIA has “no reliable directory of who to talk to on the customer side.”
§4 — The four planning terms (cross-reference)
These sit one level above the acronyms and have their own brief — see the four-terms primer:
- cycle counting → keeps inventory data honest
- material management → plan/track/cost the materials (the one term used by name in interviews)
- Clear to Build (CTB) → parts availability per unit
- Available to Commit (ATC) → what NVIDIA can promise a customer, and when
Sources: Lonny Orona 2026-05-12; Alex Zhu 2026-05-27; Greg + Lonny 2026-06-17; Greg en-route call 2026-06-26; RMA process map; four-terms primer.