About Importing Data

Materials Compliance Management provides specialized converters that recognize specific formats and automatically convert them into the XML import format.

Converters support the following formats:

Format	Data Loaded
ELV (IMDS)	Material Classifications Substance Applications Substances Materials Organizations Internal Modules: Enterprise Part BOMs Internal Simple Component External Modules: Reported Part BOM Forwarded modules are not supported.
RoHs	IPC 1752A IPC 1752B IPC 1754 Classes E, F, and G Reported Part BOMs
RoHs and ELV	BOM Text (also known as the Legacy BOM format): Organizations, Substances, Materials, Enterprise Part BOMs, and AML Compliance Connect: Reported Part BOMs JGPSSI: Reported Part BOMs
JAMP AIS	Reported Part BOMs
JAMA JAPIA	Reported Part BOMs

The import process first converts the import file to XML format, then loads the data into Materials Compliance Management.

Configuration data are typically imported during setup or by an Owner or Compliance Administrator. IMDS configuration data can be imported automatically by clicking Load IMDS Data from the top bar (See Loading IMDS Data).

Certain business objects such as organizations and substances are typically imported into Materials Compliance Management by an Owner or Compliance Administrator. Organizations and substances can be imported directly or as a reference list. When imported as a reference list, the import file is stored in the database and used to dynamically create organizations or substances when they are referenced by an imported object, such as a part or a material. Organizations and parts are not created in the database until they are referenced.

The remaining business objects, such as parts and materials, are imported by an Author or Compliance Engineer, often on a daily basis.

The GADSLandJIGSubstances.xml contains definitions of GADSL and JIG substances and can be imported.

The file is located in this directory:

<VERSION>\studio\Apps\RoHSDataManagementOption\V6R2008-2.0\RoHSDataManagementOption

Importing this file does not create new substances; it modifies the existing substances to associate the respective substance classifications. When the GADSLandJIGSubstances.xml file is imported as a reference file, all existing substances are matched by CAS number (or name if CAS is not present). For each match found, the matched substance's aliases and classifications are updated. Any alias and classification connections of the matched substance that exist prior to import are NOT removed. If a match is not found, the substance is not added.

To add substances to Materials Compliance Management, you must import Compliance Connect, IPC, or the GADSLandJIGSubstances.xml file. The GADSLandJIGSubstances.xml file can be converted to a substance list file to import the substances by replacing the root element name bom:SubstancesReference to bom:SubstancesList.

Materials Compliance Management can import data exported from the chemSHERPA Article Tool or Chemical Tool. The chemSHERPA Article Tool allows suppliers to enter information about products. These products are mapped to parts in Materials Compliance Management.

chemSHERPA uses XML files to import and export composition details (components, materials, and substances) and compliance declarations (thresholds exceeded, exemptions). When more than one part is involved, the XML files are bundled into a zip file. The chemSHERPA Article Tool uses the .shai extension and the chemSHERPA Chemical Tool use the .shci file extension. The zip file can contain up to 100 XML files. If there are more than 100 parts, multiple zip files are used.

When exporting from the chemSHERPA Article tool, the supplier can choose to export composition information, compliance information, or both types of information. By default, Materials Compliance Management will import files of any of these exports. However, your Business Administrator can disable either the composition only or compliance only types of imports. When importing both, your Business Administrator can disable it, or allow importing of only compliance or only composition data.

When importing compliance declarations, Materials Compliance Management connects the part to one or more declared thresholds based on the compliance information. For more information, see Declared Thresholds.

The chemSHERPA Chemical Tool exports composition information only, not compliance declarations. The Product exported from the tool is imported to Materials Compliance Management as a material associated with that supplier. If you want to automatically create MEPs for these materials, you can select the Auto-Make-Parts check box when configuring the import. In this case, the app creates a part with the same name as the material title. For more information, see Configuring Import Options. The app only creates the MEP if one does not already exist. The app also connects the MEP to a material declaration (if one exits for the MEP) or creates a new material declaration and reported part. The reported material is assigned a weight of 1 gram, and the part is defined as each part with no reference weight. To approve such a material, you approve the material declaration associated with the MEP of the material. These materials have no associated exemption information. You might need to edit the materials before using them in parts.

After importing compliance declarations, the related material declarations are promoted to Received, and you can run reports to review the compliance and composition data.

The import attaches these items as Reference Documents for the material declarations:

• The XML import file (extracted from the zip file)
• The log file for the specific XML file (extracted from the full log file)
• The full log file
• The full zip file

Materials Compliance Management can be configured to hide private data. If so, the Authorizer, Issuer, and Requester lists are grayed out when you try to prepopulate a BOM from either the chemSHERPA Article or Chemical Tool.

Materials Compliance Management supports the chemSHERPA 2.02 version to import the data. This version is supported to include the SCIP data.

The SCIP data is included at both the part and threshold levels. The SCIP data is mapped at part level with the part new attributes for SCIP. The SCIP data is mapped at threshold levels with the declared threshold attributes.

A new attribute named SCIP Primary Article Identifier is added to Materials Compliance Management to store SCIP Primary Article Identifier. This attribute is added to enterprise part, plant-specific part, reported part, MEP, and subtier part to store the information at part level. It is also added to Declared Threshold to store information at threshold level.

The SCIP data is added in the Comment attribute at each level. The following are changes for each area:

Product

This is the top-level part and it is mapped to the MEP for Materials Compliance Management. The SCIP data at part level is stored in the Comment attribute of <Product> XML element. The value of this attribute is updated as mentioned below. The items 1–8 are from the previous version. The items 9–15 are for the SCIP data for the chemSHERPA v2.02 version. All the items are separated using the character @.

1. Compliance Input Status
2. Compliance Finalized Date
3. Composition Input Status
4. Composition Finalized Date
5. Xml Import Status
6. Revision Date
7. Manufacturer Name
8. Comment of Product
9. SCIPComplete(Compliance)
10. SCIPComplete(Composition)
11. Primary Article Identifier

    This is mapped to a new attribute SCIP Primary Article Identifier on part.

12. Article Name

    This is mapped to the part attribute SCIP Article Name.

13. Article Category

    This is mapped to part attribute SCIP Article Category Identity. MCC will validate and error if the identity is invalid.

14. Production in European Union

    This is mapped to part attribute Production in European Union.

15. Safe Use Instruction

    This is mapped to the part attribute Safe Use Instructions.

    If the string from the data is “No need to provide safe use information beyond the identification of the Candidate List substance”, then Materials Compliance Management is specify the ‘Safe Use Instruction are not required’ check box option.

Composition

• Product Part:

  The part is mapped with the Materials Compliance Management subtier part at this level.

  The SCIP data at this level is stored in the Comment attribute of <ProductPart> XML element. All the items are separated using the character @.

  1. Primary Article Identifier

     This is mapped to a new attribute SCIP Primary Article Identifier on part.

  2. Article Name

     This is mapped to part attribute SCIP Article Name.

  3. Article Category

     This is mapped to part attribute SCIP Article Category Identity. MCC will validate and error if the identity is invalid.

  4. Production in European Union

     This is mapped to part attribute Production in European Union.

  5. Safe Use Instruction

     This is mapped to part attribute Safe Use Instructions.

     If the string from the data is “No need to provide safe use information beyond the identification of the Candidate List substance”, then Materials Compliance Management is set the ‘Safe Use Instruction are not needed’ check box option.

• The SCIP data at part level is stored in the Comment attribute of <Material> XML element. The value of this attribute is updated as mentioned below. The items 1–4 are from the previous version. The item 5 is for the SCIP data for the chemSHERPA v2.02 version. All the items are separated using the character @.
  1. chemSHERPA Material Category
  2. Not Use
  3. Standard
  4. Comment
  5. SCIP Material Category

     This is mapped to the material classification code. Compliance Type is ECHA (which is used from the properties file parameter setup for ECHA material classification).

Compliance

Compliance data is imported as the declared thresholds. The attribute Comment for <DsDsg> XML element is updated to add the SCIP data. The items 1–5 are from the previous version of chemSHERPA. The items 6-11 are for SCIP data from the chemSHERPA v2.02 version. All the items are separated using the character @.

1. Comment
2. not use (was Quantity of content on 1.07)
3. not use(was Unit on 1.07)
4. Usage
5. Portion used
6. Primary Article Identifier

   This is mapped to a new attribute SCIP Primary Article Identifier on the declared threshold.

7. Article Name

   This is mapped to the declared threshold attribute SCIP Article Name.

8. Article Category

   This is mapped to the declared threshold attribute SCIP Article Category Identity.

9. Production in European Union

   This is mapped to declared threshold attribute Production in European Union.

10. Safe Use Instruction

    This is mapped to the declared threshold attribute Safe Use Instructions.

11. Material Category

    There are no or more than one material categories.

    Each category is mapped to material classification code for Materials Compliance Management.

    Compliance Type is ECHA (used from the properties file parameter setup for the ECHA material classification).

IPC 1752B standard allows reporting of multiple classes in a single declaration for an MEP. For complex part, a single declaration can have a mixture of classes D, C, and A.

Mixed Declarations

Materials Compliance Management is updated to read MEP data structure and gather all the child components, which are reported in either class A, C, or D.

Materials Compliance Management verifies that all the child components declared in the parent structure exist in a declaration. The error is displayed if a child component is missing from the declaration.

Each time Materials Compliance Management get a part declaration:

• If it is a child or leaf component of an existing parent part in the same module, the app processes and add to the parent part structure.
• If it is a component without an existing parent part in the same module, the app processes and add to the list of top-level parts.

Multiple MEPs
<IPC-1752B> SubSectional = Class D Product 111 Product 222 Product 333 </IPC-1752B> <IPC-1752B> SubSectional = Class C Product 222 </IPC-1752B> <IPC-1752B> SubSectional = Class A Product 333 </IPC-1752B> <IPC-1752B> SubSectional = Class C Product 444 </IPC-1752B>
In this case, there is a class D declaration for the BOM 111. The two subtiers under 111 are declared as Class A (222) or Class C (333). There is a separate class C declaration for 444. Since this is not a component of BOM 111, the 444 is a top-level MEP declaration.

Also, attributes such as child part itemNumber, itemName, unitType, and isArticle can be consistent with the parent declaration of the same part. Otherwise the error is displayed.

As described below, the app also displays the error, if either O-ring leaf part is missing from a declaration, or O-ring declaration has inconsistent attribute values with the parent declaration.

MEP Thermostat (class D) O-ring (class C)

As described below, after the successful import, in you can able to see class data for leaf part from whichever class that was reported. For example, after import and except for MD, you can see that MEP Thermostat has class D data with subtier O-ring. O-ring has class C data.

MEP Combustion Engine (class D) O-ring Thermostat O-ring (class C)

SCIP Data Mapping:

Materials Compliance Management reads the SCIP related data that are available at any level in BOM structure where IsArticle is marked as true. The following are details of mapping for each item:

• Other Item
  • SCIP has the capability for providing “Other Identifiers” for the article parts. This is mapped to the new Other Article Identifier type.
    • Other item identity - Other Article Identifier attribute Identifier Value
    • Other item authority - Other Article Identifier attribute Identifier Type.
    • Properties file parameter is setup to contain mapping between Other Item authorities to the Other Article Identifier attribute Identifier Type. For more information, see Configuring Other Identity Authority.
    • Authority ECHA is mapped to range value ECHA Article ID for Identifier Type.
• Safe Use Instructions
  • This is mapped to the new Safe Use Instructions attribute on part. Materials Compliance Management reads and stores the list identity, list authority, item identity, and description attributes value.
  • Similar to chemSHERPA 2.02 support, there is a string from this import format to indicate no need for the Safe Use Instructions.
  • The properties file parameter to store all versions of No Need for Safe Use Instruction. For more information, see Configuring Safe Use Instructions.
• Article Category
  • This is mapped to the new SCIP Article Category attribute on part. Materials Compliance Management reads and stores the article category identity. For display, Materials Compliance Management searches the description of the article category from the ECHA list loaded using the identity value. The app validates and the error message is displayed if identity is invalid.
• IsArticle
  • Materials Compliance Management reads and stores IsArticle value for part on corresponding attribute.
• isFSD
  • This is an attribute for <HomogeneousMaterialList> XML element. It is used to indicate Full Substance Declaration. This flag is not imported.

Declared Threshold Changes for SCIP

IPC 1752B includes the ECHA material classifications at threshold level. This is stored on Declared Threshold similar to chemSHERPA 2.02.

Material Category

• IPC 1752B standard includes the list of material categories at material and substance category levels. Each material category is mapped to a material classification in MCC. Also, these material classification is from the material classifications list from ECHA.
• Material Category identity is mapped to the material classification code. And material category description is mapped to material classification description.
• For class D, material can now have ECHA material classification. MCC will only read a single ECHA material classification. Additional material category list is not read at this time.
• For class C, each substance category (a threshold) can have one or more material categories. Similar to chemSHERPA 2.02, this is stored in the Classification relationship between Declared Threshold relationship and Material Classification. For more details, see the following examples,

  Material Category per Material class D

  Material Category per Material class D