ArcFM System Tables

The MM System Tables are created when an administrator (logged in as SDE) selects the ArcFM Solution System Tables button. Each of these tables must have the ARCFMSYSTEMTABLE model name assigned.

MM_CLASS_MODELNAMES

This table stores model names assigned to features and objects.

Field

Data Type

Description

ModelDatasetName

Text

Contains the name of the dataset to which the feature or object belongs.

ObjectClassName

Text

Contains the name of the feature or object class to which the feature belongs.

SubtypeUsed

Number

Reserved for future use.

Subtype

Number

Reserved for future use.

ModelName

Text

Contains model name assigned to the feature or object class.

MM_DOCUMENTS

This table stores user documents.

Field

Data Type

Description

DocumentName

Text

The user-defined name of the document. This is how it appears in the Documents dropdown menu.

Description

Text

Reserved for future use.

UserName

Text

The Login name of the user who created the document.

Document

OLE Object

Stores the document in binary format.

MM_EDITED_FEATURES

The Feeder Sync tool uses this table to track which features' feeder information is affected by edits. It uses this information to update the Feeder Manager 1.0 fields during sync.

Field

Data Type

Description

ClassID

Long Integer

Unique ID associated with the type feature that has had feeder information impacted by edits.

FeatureID

Long Integer

Unique ID associated with the feature who's feeder information has been impacted by edits.

Version

Text

The version of the edit session during which the feature was modified.

MM_FIELD_MODELNAMES

This table stores model names assigned to attributes.

Field

Data Type

Description

ObjectClassName

Text

Contains the name of the feature or object class to which the feature belongs.

FieldName

Text

Contains the name of the field to which the field model name is assigned.

ModelName

Text

Contains the field model name assigned to the attribute field.

MM_HIDDEN_PACKAGES

This table stores objects that are available system-wide, but don't appear in any of the system or user menus. For example, map books that are associated with designs. (Designer only).

Field

Data Type

Description

Name

Text

The name of the saved object (e.g., design map book). While the length of this value is determined by the length of the field, Schneider Electric strongly recommends this value be at least 32 characters.

Category

Number

Indicates the type of object. This table uses the mmPackageCategory enumeration.

Description

Text

A description of the design map book. This may be generated programmatically.

UserName

Text

Name of the design to which the map book is assigned.

ContentsProgID

Text

Contains the ProgID of the COM object that manages the package.

Contents

OLE Object

Stores the package in binary format.

MM_MOBILE_IMPORT_ORDER

This table stores the order in which features are imported into the enterprise database from the Mobile field database.

Field

Data Type

Description

Object_Class_Name

Text

This is the table name of the feature class (visible in the Packet Template database) to be imported (e.g., Transformer).

Object_Class_ID

Number

This is the identifier for the object class.

Subtype_ID

Number

This is the identifier for the subtype of the object class to be imported.

Import_Order

Number

This is the order in which you want the features to be imported. A feature layer with an import order of 1 is imported first.

MM_PACKAGES

This table stores map books and Structural Analysis scenarios. An object stored in this table is available only to the user who created it. Map book stored in this table may be accessed in Designer only by opening the associated design.

Field

Data Type

Description

Name

Text

The name of the saved object (e.g., map book or structural analysis scenario). While the length of this value is determined by the length of the field, Schneider Electric strongly recommends this value be at least 32 characters.

Category

Number

Indicates the type of object. This table uses the mmPackageCategory enumeration.

Description

Text

A description of the saved object. This may be generated programmatically.

UserName

Text

Login name of the user who saved the object.

ContentsProgID

Text

Contains the ProgID of the COM object that manages the package.

Contents

OLE Object

Stores the package in binary format.

MM_PAGE_TEMPLATES

This table stores user page templates.

Field

Data Type

Description

Name

Text

The user-defined name of the page template. This is how it appears in the Page Templates dropdown menu.

Description

Text

Reserved for future use.

UserName

Text

Login name of the user who created the page template.

Template

OLE Object

Stores the page template in binary format.

MM_PERSIST_INFO

This table stores binary information about user preferences and settings such as user favorites and options settings.

Field

Data Type

Description

TreeName

Text

The type of information stored.

Data

OLE Object

Stores the information in binary format.

UserName

Text

The login name of the user.

MM_QAQC

This table allows you ignore some Feeder Manager 2.0 QA/QC rules for designated features. This functionality and how to enable it is discussed in the Feeder Manager section on the Validation Rules page in the Configuration Guide.

Field

Data Type

Description

FeatureID

Long Integer

Unique ID associated with the piece of equipment that will ignore the specified QA/QC rule.

FeatureClassID

Long Integer

Unique ID associated with the type of equipment that will ignore the specificed QA/QC rule (e.g., an ID to indicate whether the equipment type is switch or transformer, etc.).

QaqcRule

Text

The rule that will be ignored by the feature (e.g., Electric MultiFeed Feature or Electric Loop Feature).

MM_SNAPPING

This table stores snapping information for feature classes.

Field

Data Type

Description

Feature_Class

Text

The feature class that may be snapped.

Subtype

Text

The subtype of the feature class that may be snapped.

Snap_to_feature_class

Text

The feature class to which the feature is snapped.

Snap_to_Subtype

Text

The subtype of the feature class to which the feature is snapped.

HitType

Number

Stores the snapping preferences such as Vertex, Edge, and/or End.

Tolerance

Number

The snapping tolerance as defined by the user.

Subtype_Code

Number

Stores a code that corresponds with a specific subtype for the feature.

MM_STORED_DISPLAYS

This table stores user stored displays.

Field

Data Type

Description

Name

Text

The user-defined name of the stored display. This is how it appears in the Stored Display dropdown menu. Modify the length of this field in the database if you wish to change the maximum length for user stored display names.

UserName

Text

The Login name of the user who saved the stored display.

Map

OLE Object

Stores the stored display in binary format.

MM_SYSTEM_DOCUMENTS

This table stores system documents.

Field

Data Type

Description

DocumentName

Text

The user-defined name of the document. This is how it appears in the Documents dropdown menu.

Description

Text

Reserved for future use.

UserName

Text

Stores a value of SYSTEM to indicate a system document.

Document

OLE Object

Stores the document in binary format.

MM_SYSTEM_PACKAGES

This table stores map books and Structural Analysis scenarios that are available to all users connected to the geodatabase.

Field

Data Type

Description

Name

Text

The name of the saved object (e.g., map book or structural analysis scenario). While the length of this value is determined by the length of the field, Schneider Electric strongly recommends this value be at least 32 characters.

Category

Number

Indicates the type of object. Uses the mmPackageCategory enumeration.

Description

Text

A description of the saved object. This may be generated programmatically.

UserName

Text

Stores a value of SYSTEM to indicate a system map book or scenario.

ContentsProgID

Text

Contains the ProgID of the COM object that manages the package.

Contents

OLE Object

Stores the package in binary format.

MM_SYSTEM_PAGE_TEMPLATES

This table stores system page templates.

Field

Data Type

Description

Name

Text

The user-defined name of the page template. This is how it appears in the Page Templates dropdown menu.

Description

Text

Reserved for future use.

UserName

Text

Stores a value of SYSTEM to indicate a system page template.

Template

OLE Object

Stores the page template in binary format.

MM_SYSTEM_PERSIST_INFO

This table stores binary information about the database including system favorites, CUs, graphic favorites, macros, autoupdaters, and database level model names.

Field

Data Type

Description

TreeName

Text

Type of information stored.

Data

OLE Object

Stores the information in binary format.

MM_SYSTEM_STORED_DISPLAYS

This table stores system stored displays.

Field

Data Type

Description

Name

Text

The user-defined name of the stored display. This is how it appears in the Stored Displays dropdown menu. Modify the length of this field in the database if you wish to change the maximum length for system stored display names.

UserName

Text

Stores a value of SYSTEM to indicate a system stored display.

Map

OLE Object

Stores the stored display in binary format.

QR code for this page

Was this helpful?