Table and Field Names
The Data Engine supports all FMEA, FRACAS, and FTA tables in the System file. It also supports tables in Data Definition files, List Library files, and FRACAS Lookup Table files. Many API functions require a table name and one or more field names.
• Anywhere a table name is required, you supply either the singular name or plural name assigned to the table in the Project properties.
• Anywhere a field name is required, you supply the prompt assigned to the field in the Project’s Data Definition file.
Most users find the previous guidelines sufficient for using the Data Engine. However, a few fields, such as those for PTC Windchill identifiers, do not have prompts. If you want to read, modify, or export data from such fields, you can supply internal database field names.
Some users have Projects with different table and field names. If you need to remove Project-specific dependencies, you can supply internal database names for both tables and fields. For your convenience, internal database names for supported tables follow in alphabetic order. The N in a subtable name represents the number of the subtable in the Project properties.
• Configurations
• ControlPlanSubtableN
• DVPSubtableN
• FaultTree
• FMEATable
• FMEATableSubtableN
• FMEATree
• FMEATreeSubtableN
• FMEAWorksheet
• FMEAControlPlans
• FMEADVP
• Incidents
• IncidentsSubtableN
• ListChoices
• ListDefinitions
• LookupKey
• MaintenanceLogs
• OperatingTimes
• Problems
• ProblemsSubtableN
• SystemTree
• SystemTreeSubtableN