Staging Error Messages (Master Data Services)

When the staging process is complete, all processed records in the staging tables have a value in the ErrorCode column. These values are listed in the following tables.

NoteNote

You can also view warning and error messages in Master Data Manager on the Staging Batch Errors page.

Error

Description

ERR210000

The record was imported successfully.

ERR210012

A new non-mandatory explicit hierarchy relationship was created successfully.

ERR210013

A new collection member was created successfully.

ERR210014

The member was assigned as a child of MDMUNUSED successfully.

Error

Description

ERR210007

The assignment already exists. No changes were made.

ERR210030

The AttributeValue will not be assigned.

ERR210050

A hierarchy is not required when you are importing members into collections.

Error

Description

ERR210001

The same MemberCode exists multiple times in the staging table. The first member with the MemberCode is created successfully but the members with this error code are not.

ERR210003

The AttributeValue references a member that does not exist or is inactive. If you are updating a domain-based attribute, use a code rather than a name for AttributeValue.

ERR210004

The AttributeValue references a member that does not exist or is inactive.

ERR210006

The MemberCode is inactive.

ERR210008

The TargetCode is inactive.

ERR210009

The MemberCode does not exist.

ERR210010

The TargetCode does not exist.

ERR210011

When TargetType_ID is 1, the TargetCode cannot be a leaf member. It must be a collection or consolidated member.

ERR210015

For the non-mandatory hierarchy, the MemberCode exists multiple times in the staging table.

ERR210016

The relationship could not be created because it would cause a circular reference.

ERR210017

The UserName is not valid.

ERR210018

The ModelName is missing or not valid.

ERR210019

You must be a model administrator.

ERR210020

The EntityName is missing or is not valid.

ERR210021

The MemberType_ID is not valid. Use 1 for leaf, 2 for consolidated (parent), or 3 for collection.

ERR210022

You cannot update system attributes.

ERR210023

You cannot update file attributes.

ERR210024

The AttributeValue is too long.

ERR210025

The AttributeValue must be a number.

ERR210026

The AttributeValue must be a date.

ERR210027

The AttributeValue must be an integer.

ERR210028

The AttributeName is missing or is not valid.

ERR210029

The AttributeValue is missing.

ERR210031

When you change the MDMMemberStatus attribute, the AttributeValue must be either "Active" or "De-Activated." For more information, see How to: Reactivate a Member or Collection by Using tblStgMemberAttribute (Master Data Services).

ERR210032

The HierarchyName is required if MemberType_ID is 2. You must designate which explicit hierarchy the member belongs to.

ERR210033

The entity is not enabled for collections.

ERR210034

The MemberCode is a reserved word and is not valid.

ERR210035

Because a code generation business rule does not exist, the MemberCode is required.

ERR210036

Because a code generation business rule exists, the MemberCode is not required.

ERR210037

The MemberType_ID is not valid. Use 1 for leaf, 2 for consolidated (parent), or 3 for collection.

ERR210038

The HierarchyName is required when the MemberType_ID is 4. When you are updating relationships in an explicit hierarchy, you must include the hierarchy name.

ERR210039

The MemberType_ID must be 4 (hierarchy relationship) or 5 (collection relationship).

ERR210040

MemberCode is required.

ERR210041

ROOT is not a valid MemberCode.

ERR210042

MDMUNUSED is not a valid MemberCode.

ERR210043

The TargetType_ID must be 1 (parent) or 2 (sibling).

ERR210044

The TargetCode does not exist.

ERR210045

MDMUNUSED is a reserved word and is not valid.

ERR210046

The member cannot be a sibling of Root.

ERR210047

The member cannot be a sibling of Unused.

ERR210048

MemberCode and TargetCode cannot be the same.

ERR210049

The TargetType_ID must be 1 (parent) when staging collection relationships.

ERR210051

The ObjectID cannot be updated because it is a system attribute.

ERR210052

The MemberCode cannot be deactivated because it is used as a domain-based attribute value.

ERR210053

The relationship could not be created because it would cause a circular reference.

ERR210054

An unknown error occurred when staging attribute values.

ERR210055

An unknown error occurred when staging attribute members.

ERR300001

The file attribute cannot be saved.

ERR300002

The member code is not valid.

ERR300003

The member code already exists.

Community Additions

ADD
Show: