Defining Related Objects When Importing Parts

When parts are imported from an XML file, you can configure if the app should create or connect additional objects when a part is created by importing an XML file.

See Also
Configuring Properties
  1. Create or open the text file to contain customized properties. For more information, see Editing Properties Using MQL.
  2. To indicate whether suppliers should be created if the supplier referenced in the reported part import does not exist, follow these steps:
    1. Add or edit this line in the file used to import properties into a page object: 

      emxMaterialComplianceCentral.importer.addReferencedSupplier=true

      The importer uses the supplier name and code provided with the reported part to find a match to an existing supplier. For IMDS imports of external module files, the IMDS Company ID is used to match a Materials Compliance Management Supplier. If this fails to find a match then the IMDS Company ID is used to look up the supplier name and code in the ccall.dat file. The importer then uses this name and code to find a match to an existing supplier.

      Note: This property only applies if the addReferencedMEP property is set to true and a MEP is created because it does not already exist.

    2. Set the value for this property depending on your business requirements:

      • true A supplier is created if no match is found.
      • false An error occurs if no match is found.

  3. To indicate whether supplier locations should be created if the supplier location referenced in the reported part import does not exist, follow these steps:
    1. Add or edit this line in the file used to import properties into a page object: 

      emxMaterialComplianceCentral.importer.addReferencedManufacturerLocation=true
      Note: This property only applies if the addReferencedMEP property is set to true and a MEP is created because it does not already exist.

    2. Set the value for this property depending on your business requirements:

      • true A supplier location is created if one does not exist
      • false An error occurs if the supplier location does not exist in the database.

  4. To indicate whether supplier contacts should be created when importing IMDS external modules, follow these steps:
    1. Add or edit this line in the file used to import properties into a page object: 

      emxMaterialComplianceCentral.importer.addReferencedSuppContact=false

    2. Set the value for this property depending on your business requirements:

      • true If the supplier is created as part of the module import, all of its contacts, as defined in the IMDS CCALL.dat file, are added to the supplier. If the supplier already exists, only the contact associated with the module is added to the supplier.
      • false No IMDS contacts are added to the supplier.

  5. To indicate whether existing supplier contacts should be updated when importing IMDS external modules, follow these steps:
    1. Add or edit this line in the file used to import properties into a page object: 

      emxMaterialComplianceCentral.importer.updateReferencedSuppContact=false

    2. Set the value for this property depending on your business requirements:

      • true If the supplier contact already exists, the contact is updated with new data from the IMDS import.
      • false No IMDS contacts are updated for the supplier.

  6. To indicate whether a customer should be created if referenced in a Customer Part Number of an enterprise part when the customer does not exist, follow these steps:
    1. Add or edit this line in the file used to import properties into a page object: 

      emxMaterialComplianceCentral.importer.addReferencedCustomer=true

    2. Set the value for this property depending on your business requirements:

      • true If the customer does not exist, it is created so that it can be referenced.
      • false If the customer does not exist, an error is generated.

      For example, if a part has a customer part number defined for the customer Big Car Co, the importer determines if a customer named Big Car Co exists in Materials Compliance Management.

  7. To indicate whether to create an MEP if it does not exist when importing a Reported Part, follow these steps:
    1. Add or edit this line in the file used to import properties into a page object: 

      emxMaterialComplianceCentral.importer.addReferencedMEP=false

    2. Set the value for this property depending on your business requirements:

      • true If the MEP does not exist, it is created so that it can be referenced.
      • false If the MEP does not exist, an error is generated in the import log.

  8. To indicate whether to create an Enterprise Part if it does not exist when importing a Reported Part, follow these steps:
    1. Add or edit this line in the file used to import properties into a page object: 

      emxMaterialComplianceCentral.importer.addReferencedCEP=false

    2. Set the value for this property depending on your business requirements:

      • true If the Enterprise Part does not exist, it is created and the MEP is connected to it as an equivalent.
      • false If the Enterprise Part does not exist, an error is generated in the import log.

      This property only applies if the addReferencedMEP property is true and an MEP is created.

  9. For a reported part, to indicate whether to connect a matched or created MEP to a matched or created enterprise part as an equivalent if it is not already an equivalent, follow these steps:
    1. Add or edit this line in the file used to import properties into a page object: 

      emxMaterialComplianceCentral.importer.connectMEPAsEquivalent=false

    2. Set the value for this property depending on your business requirements:

      • true If not already connected as an equivalent, the MEP is connected to the Enterprise Part as an equivalent.
      • false If not already connected as an equivalent, an error is generated in the import log.

  10. To indicate whether enterprise parts are imported as enterprise parts or plant specific parts with a default plant, follow these steps:
    1. Add or edit this line in the file used to import properties into a page object: 

      emxMaterialComplianceCentral.importer.defaultPlant=

    2. Set the value for this property to the name of an active host company location.

      Normally an enterprise part is imported as an enterprise part. This means that the enterprise part is either matched to an existing Enterprise Part or a new Enterprise Part is created. If you specify a Default Plant, then the enterprise part is first matched or created. A plant-specific part for the Enterprise Part is then matched or created using the default plant. These plant-specific parts are then connected to each other to define the BOM. The net result is that the BOMs that are created are plant-specific part BOMs rather than Enterprise Part BOMs.

  11. To indicate whether equivalents are added to enterprise parts when imported, follow these steps:
    1. Add or edit this line in the file used to import properties into a page object: 

      emxMaterialComplianceCentral.importer.addEquivsToEP=true

    2. Set the value for this property to the name of an active host company location.

      • true If not already connected as an equivalent, the MEP is connected to the EP as an equivalent.
      • false If not already connected as an equivalent, an error is generated in the import log.

  12. When finished updating the text file with all properties you want to modify, including the ones shown here, use the text file to modify the emxMaterialsComplianceCentral.properties page object. For more information, see Editing Properties Using MQL.