- Create or open the text file to contain customized properties. For more information, see Editing Properties Using MQL.
-
To determine whether the importer should create IMDS substances marked as deleted from the sball.dat file, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxMaterialComplianceCentral.importer.imds.addDeletedSubstances=true
-
Set the value for this property depending on your business requirements:
true (default) Deleted substances are created when referenced by a material.false Deleted substances are not created and the import aborts with an error.
-
To determine whether the importer should create IMDS substances marked as hidden from the sball.dat file, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxMaterialComplianceCentral.importer.imds.addHiddenSubstances=true
-
Set the value for this property depending on your business requirements:
true (default) Hidden substances are created when referenced by a material.false Hidden substances are not created and the import aborts with an error.
-
To determine if modules marked as hidden in the IMDS module file are imported, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxMaterialComplianceCentral.importer.imds.addHiddenModules=true
-
Set the value for this property depending on your business requirements:
true (default) Hidden modules are imported.false Hidden modules are skipped.
-
To handle a confidential substance, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxMaterialComplianceCentral.importer.imds.confidentialSubstanceId=9999
When a confidential substance is encountered in an IMDS material import, this parameter identifies the IMDS Node ID of the substance to reference in its place.
-
Set the value for this property depending on your business requirements. The default values is substance node ID 9999, which is the "Misc., not to declare" substance.
-
To handle an ELV material classification, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxMaterialComplianceCentral.importer.imds.defaultMaterialClassificationCode=7.3
When ELV is installed, an ELV material classification, that is also the IMDS material classification, must be associated with each material. IMDS contains materials with a classification code of 0 indicating that the material classification is undefined in IMDS. In this case, this parameter maps this classification to a valid ELV (IMDS) material classification.
-
Set the value for this property to the code of the material classification. The default is 7.3, corresponding to the ELV (IMDS) material classification of "Other compounds (for example, friction linings)."
-
To handle an ELV material classification when RoHS is installed, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxMaterialComplianceCentral.importer.imds.defaultMaterialClassificationCodeForRoHS=8.1
When ELV is installed, an ELV material classification, that is also the IMDS material classification, must be associated with each material. If RoHS is also installed and a RoHS Compliance Connect file is imported, no material classification is specified for materials. In this case, this parameter identifies the default material classification to use.
-
Set the value for this property to the code of the material classification. The default is 8.1, corresponding to the ELV (IMDS) material classification of "Electronics (for example, pc boards, displays)."
-
To define the default configuration setting for importing internal modules, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxMaterialComplianceCentral.importer.imds.InternalModules=Import - Update Only
-
Set the value for this property depending on your business requirements:
Value | Description |
---|
Skip | Internal modules will not be imported. | Import - Update Only | Existing parts and materials in internal modules will be imported. When the import cannot find a matching part or material, an entry is made in a log. | Import - Update and Add | Existing parts and materials in internal modules will be imported. When the import cannot find a matching part or material, the import will create the part or material. |
-
To define the default configuration setting for importing external modules, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxMaterialComplianceCentral.importer.imds.ExternalModules=Import
-
Set the value for this property depending on your business requirements:
Value | Description |
---|
Skip | External modules will not be imported. Choose this option when importing internal modules. | Import | Existing parts and materials in external modules will be imported. |
-
To determine how material modules in IMDS module files are handled, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxMaterialComplianceCentral.importer.imds.materialsMode
Materials are generally created as components of part modules. However, it is possible for a supplier to create a top level material module and send it to you.
-
Set the value for this property depending on your business requirements:
Ignore If a material module is found in an import file, the material module is skipped.
-
To control how the importer matches to enterprise parts when importing IMDS modules, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxMaterialComplianceCentral.importer.imds.epMatchingMode
-
Set the value for this property depending on your business requirements:
Latest (default) Matches the last Revision of an Enterprise Part with the same name.Latest-Released Matches the last Revision of a "Released" Enterprise Part with the same name.Don't-Match Does not try to match the Enterprise Part.
-
To control how internal material modules are imported from IMDS, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxMaterialComplianceCentral.importer.imds.IMDSInternalModuleImport.AutoCreateApproveInternalMaterial=true
-
Set the value for this property depending on your business requirements:
true (default) If no match to an existing material is found, creates and promotes the material to "Approved" Internal Materials.false Does not create Internal Materials.
-
To remove deleted applications, follow these steps:
-
Add or edit this line in the file used to import properties into a page object:
emxMaterialComplianceCentral.importer.imds.removeDeletedApplications=false
When the IMDS applications file is imported, Compliance Applications are created in Materials Compliance Management so that they can be referenced by substances in materials. The IMDS applications file (SAAll.dat) contains applications marked as deleted in IMDS. Old modules in IMDS may reference these deleted applications. This property determines whether these deleted applications are imported into Materials Compliance Management.
-
Set the value for this property depending on your business requirements:
true Deleted applications are skipped.false (default) Deleted applications are imported so that older module imported into Materials Compliance Management can reference them.
- 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.
|