SimcenterKnowledge

Materials > Using custom materials > Simcenter Nastran user-defined material models

UMAT troubleshooting

If you inherit a FEM file, idealized part, or master model part that has materials with UMAT models, but you do not have access to the same underlying XML file the following occurs, depending on the presence and completeness of the UMAT models in the current session:

  • The software updates the UMAT model or reactivates UMAT model/properties.

  • The software displays a message and lets you update the UMAT model/properties.

The following tables list usage scenarios and related user options and software actions:

Open a part that has materials with UMAT models defined, and open the Material Library Manager, Manage Materials, or Assign Material dialog box

Problem Solution
The Information Window and Log File list a message that the software is Unable to map property to a property in the NX Model., when a UMAT model cannot be found in the current software session (that is, no XML file (.umatx extension file) in a startup directory. The software retains UMAT model/properties, but they are orphaned. Orphaned means that they are deactivated.You can delete the orphaned properties by using the Delete Orphaned User Material (UMAT) Model/Properties right-click command in the Manage Materials dialog box, or with an NX Open routine.
The UMAT model is found in the current session and no model differences exist. The software reactivates previously orphaned UMAT model/properties.If the stored model definition matches the session model definition (that is, all UMAT properties exist and none are new or modified), the part opens with no migration.
The UMAT model is found in the current session and model differences exist. The software reactivates previously orphaned UMAT model/properties.If the stored model definition does not match the session model definition, the part opens and the software updates the stored model definition based on the differences. The following UMAT model is found in the current session and model differences exist table outlines the differences, describes the actions taken by the software based on the differences, and includes possible user actions.

UMAT model is found in the current session and model differences exist

Problem Solution
The Information Window and Log File list a message that the software is Unable to map property to a property in the NX Model., when the stored UMAT model has some properties that are not defined in the session model. The software orphans the extra properties, and makes the orphaned properties inaccessible from the materials dialog boxes and any NX Open routines (except the routine to delete).You can delete the orphaned properties by using the Delete Orphaned User Material (UMAT) Model/Properties right-click command in the Manage Materials dialog box, or with an NX Open routine.
The software displays an Alerts message:This material contains orphaned user-defined material model (UMAT) properties., when you select a local material with an orphaned UMAT model and use the Inspect or Configure Library Material right-click commands in the Manage Materials dialog box. The software orphans the extra properties, and makes the orphaned properties inaccessible from the materials dialog boxes and any NX Open routines (except the routine to delete).You can delete the orphaned properties with the Delete Orphaned User Material (UMAT) Model/Properties right-click command in the Manage Materials dialog box, or with an NX Open routine.
The session UMAT model has some properties that are not found in the stored model. The software adds environment properties with default values.

Edit a material with orphaned UMAT models/properties

Problem Solution
The Information Window and Log File list a message that the software is Unable to map property to a property in the NX Model., when you open a part file, select a material with orphaned UMAT model/properties and edit the material, and the .umatx file misses a model.The software also displays an Alerts message indicating that orphaned UMAT model/properties exist.For example, your .umatx file lists the model choices None and a second one associated with a model type, but originally the local material was defined with a .umatx file that contained also a third model. The software sets the UMAT model to None if the current model selected is orphaned. Otherwise, the software specifies the current model. Also, the orphaned models associated with the model type are not available from the Model 1 or Model 2 lists.You can delete the orphaned models by using the Delete Orphaned User Material (UMAT) Model/Properties right-click command in the Manage Materials dialog box, or with an NX Open routine.
Quick links

Command reference

Pre/Post video examples

Bulk Entry Descriptions

Simcenter 3D tutorials

Browse Simcenter 3D help by product area

UMAT troubleshooting, Simcenter 3D 2021.1 Series

© 2020 Siemens

window.mainLanguage="en_US"

window.delivId=""

window.projectId=""

MathJax.Hub.Config({ TeX: { extensions: ["autoload-all.js"] }, tex2jax: { displayMath: [ ] }, "SVG": { scale: 125 } });

Source: https://docs.sw.siemens.com/en-US/doc/289054037/PL20200601120302950.advanced/xid1124833 · retrieved 2026-07-17