概要
Internal Part Number Search ties your internal numbering schema to the manufacturer part numbers in Z2's database, so engineers and buyers work in the part numbers they recognize instead of translating MPNs by hand. You upload an IPN-to-MPN map by CSV or API, and from that point every search, BOM upload, lifecycle forecast, and compliance check resolves to the matching MPN behind the scenes. Lookup runs both ways, from an internal number to its MPN or from an MPN back to your internal number, so a part stays traceable across your ERP, your BOMs, and the Z2 record.
Load your internal-part-number-to-MPN map with a CSV upload or a direct API push, so the schema your ERP and your BOMs already use becomes searchable in Z2 without manual re-keying. A single internal number can map to multiple approved manufacturer parts, which keeps your approved vendor list intact rather than collapsing alternates into one entry. As parts are added or re-sourced, you re-upload or push the changes so the mapping tracks your live numbering instead of drifting out of date.
Once a part is mapped, Z2's full toolset accepts your internal numbers: search, BOM scoring, lifecycle forecasting, compliance screening, and supplier-risk checks all resolve to the right MPN behind the scenes. An engineer pastes a BOM in your internal schema and gets obsolescence, end-of-life, and country-of-origin signals back against the same numbers, with no spreadsheet step to translate IPNs into MPNs first. The data stays anchored to the canonical manufacturer part, so an internal number inherits every score and alert attached to its MPN.
Lookup runs in both directions, so you can find the MPN behind an internal number or trace an MPN back to the internal number that carries it, which keeps a part identifiable whether you start from your ERP or from a manufacturer change notice. Mappings are maintained per account with role-based access controls, so your numbering schema stays private to your team and only the right people can edit it. That two-way link means a discontinuation notice on an MPN surfaces against your internal number too, so the right part gets flagged in the language your buyers act on.
Internal Part Number Search is one capability inside Part Risk Manager, Z2's component risk platform. The IPN-to-MPN map sits on the same data layer that drives lifecycle forecasting, compliance, and supplier risk, so an internal number you search inherits every score and alert attached to its manufacturer part. Because the mapping is shared across the product, the obsolescence event or compliance flag that lands on an MPN reaches your team in the internal numbers they already use.
機能
Internal Part Number SearchはZ2DataのPart Risk Managerに搭載された機能の一つであり、the industry's largest component intelligence platform. Search and score 1B+ parts across obsolescence, compliance, sourcing, and supplier risk, all in one view.
よくあるご質問
Upload your internal-part-number-to-MPN map as a CSV or push it through the API. Once loaded, Z2 resolves your internal numbers to their manufacturer parts across every function.
Yes. An internal number can map to several approved manufacturer parts, which preserves your approved vendor list instead of forcing each internal number onto a single MPN.
Mappings are maintained per account with role-based access controls, so your numbering schema stays private to your team and only authorized users can change it.
