Two lists that get conflated

What each list is for

The approved manufacturer list attaches to an internal part and names the manufacturer parts engineering has qualified for it, each with an approval state: preferred, alternate, qualified, under evaluation, rejected. TE Connectivity's connector is on the AML; the fact that four distributors sell it is not an AML question.

The approved vendor list attaches to a manufacturer part or a commodity and names who you may buy it from, with the commercial terms attached. Changing distributor is a sourcing decision. Changing manufacturer is an engineering decision that may require a qualification.

That is the distinction, and it is the whole page. They are conflated constantly because both look like a supplier field on a part, and the conflation has consequences that only surface years later.

The mechanism: four object types, not one

A manufacturer makes things. A supplier sells things. A manufacturer part is a specific product with an MPN. A supplier part is that product as sold by a particular vendor, with their part number and their terms. Four types, because they are four things.

The separation is not bureaucratic. It is what allows the question “which of our parts are affected by this manufacturer's end-of-life notice” to be answerable at all — the notice names an MPN, the MPN sits on a manufacturer part, the manufacturer part sits on the AML of one or more internal parts, and those roll up to products through resolved structures.

Collapse manufacturer and supplier into one field and that chain breaks at the first link. The notice names a manufacturer you may have recorded as a distributor, or recorded three ways across three parts, and the join stops working.

Approval state lives on the AML entry, not on the part. A part with three approved manufacturer parts where one is preferred, one is a qualified alternate and one is under evaluation is a normal and useful state that a single field cannot express.

The failure it prevents

A manufacturer discontinues a connector and issues a notice naming their MPN. The company's PLM has a supplier field on each part, populated over years by different people — sometimes with the manufacturer, sometimes with the distributor, sometimes with whoever quoted last.

The notice matches nothing reliably. Somebody searches the description instead, finds forty possible parts, and spends a day narrowing it to four. Two of those four were false matches and one real one was missed, because its supplier field named a distributor rather than the manufacturer.

That missed part ships for another five months. Nobody was careless — the data was recorded honestly by people using the field they were given. The field was wrong, and a field that conflates two questions cannot be filled in correctly no matter who is filling it.

How it meets the rest of the product

Component data feeds match on manufacturer part number against AML entries, which is why the AML is the join that makes lifecycle risk work at all. A part with no AML entry is invisible to every feed, and the unmatched list is the concrete argument for maintaining it.

Reuse detection uses a shared AML manufacturer part as its strongest signal: two internal numbers approving the same MPN are almost certainly the same thing, whatever their descriptions say.

Compliance declarations attach to manufacturer parts rather than to internal ones, because the manufacturer is who declares composition. A rollup that attached declarations to internal parts would need a fresh declaration every time engineering created a duplicate number.

Change management treats an AML change as a change: adding an approved alternate goes through the process with an impact set, because it affects what may be built and by whom.

How it meets your ERP

The AVL largely masters in your ERP, because it is a purchasing fact — terms, pricing, the vendor part number a buyer transacts against, the history of what was actually bought. Manufacturing PLM reads supplier records back and renders them read-only.

The AML masters here, because it is an engineering qualification. Which manufacturer parts are approved for an internal part, and in what state, is a decision engineering makes and records through change control.

That split is the default row in the system-of-record matrix and it holds across all six connectors. What Manufacturing PLM publishes outward is the manufacturer part and its approval state where the target models them; what it never does is write a vendor's commercial terms, which are not engineering's to hold.

Where the boundary is

Manufacturing PLM does not rank suppliers commercially, negotiate, or hold pricing. A qualification state is an engineering judgement about whether a part performs; who is cheapest this quarter is a different question owned by people with a budget.

It also does not maintain manufacturer records for you. Manufacturers and their parts arrive through the component data feeds or through import, and a manufacturer nobody has recorded is one no feed can match against — which is the ordinary limit of every join on this page.