How Materials Compliance Management Matches Imported Parts and Material Declarations with Existing Objects

Part Matching

For an enterprise part, the only matching criteria that used are Name and Rev of the part. For plant-specific parts, the Name, Rev, and host-company location name are used. For an MEP, the matching is based on the Manufacturer, Name, and optionally the Manufacturer Location Name (formerly known as fabrication plant).

If a match is found for a part in Materials Compliance Management, then the importer needs to determine whether to use the existing part in Materials Compliance Management "as-is" or to update it with what is in the import file. This decision is based on whether the part in Materials Compliance Management and the part in the import file are considered "reported".

For enterprise and plant-specific parts:

The part is determined as reported or unreported by using a compliance definition. The importer is configured as to which compliance definition to query for in Materials Compliance Management. The EU RoHS compliance definition is used as the default. If the "make" compliance of the part is "Unreported", then the part will be considered unreported. For all other values the part will be considered reported.
The part in the import file will be determined as reported or unreported by examination of the data associated with the part. The part will be reported if it references a child enterprise part or a material.

Once the importer determines the reported state of the Materials Compliance Management part and the import file part, it takes the appropriate action on imports as described in the following table:


Import File Part	MCC Part	Action
Unreported	Reported	Use MCC Part.
Reported	Unreported	Replace MCC part with Import File part.
Unreported	Unreported	Use duplicate-definition-mode parameter to determine whether to use the existing MCC part or replace it with the Import File part.
Reported	Reported	Use duplicate-definition-mode parameter to determine whether to use the existing MCC part or replace it with the Import File part.

For MEPs: the part in Materials Compliance Management is also determined as reported or unreported by using a compliance definition. The importer will be configured as to which compliance definition to query for in Materials Compliance Management. The EU RoHS compliance definition is used as the default. If the "selected" compliance of the part is "Unreported", then the part is considered unreported. For all other values the part is considered reported.

The part in the import file is determined as reported or unreported by examination of the data associated with the part. The part is reported if one of the following is true:

It references a child sub-tier part or a material
It contains IPC RoHS override data.

Once the importer has determined the reported state of the Materials Compliance Management part and the import file part, it takes the appropriate action on imports as described in the following table:


Import File MEP	MCC MEP	Action
Unreported	Reported	Use the Materials Compliance Management Part.
Reported	Unreported	Create or replace a reported part under a matching material declaration for the MEP.
Unreported	Unreported	Use duplicate-definition-mode parameter to determine whether to use the existing Materials Compliance Management part or replace it with the import file part.
Reported	Reported	Create or replace a reported part under a matching material declaration for the MEP.

Material Declarations

When a reported MEP is imported into Materials Compliance Management it must be imported as a reported part under a material declaration. The importer must determine whether an appropriate material declaration already exists for the MEP and, if not, create one.

A match to an existing material declaration is based on the following:

A material declaration must exist under the matching MEP.
If enterprise part information (Name and Revision) is provided in the import file for the reported MEP, then the material declaration must also be connected to the enterprise part that the MEP was requested for. If no enterprise part information is provided in the import file, then the material declaration must not be connected to any enterprise part.
The material declaration must be in a state of Requested, Submitted, or Received.

If a match is found, the reported part is created underneath this material declaration and the material declaration is promoted to the Received state. The reported part completely replaces any previous reported part in the material declaration.

If no match is found, the importer must create a material declaration under the MEP, connect it to the enteprise part (if enterprise part information is provided), and promote it to the Received state.