Administering EBOM and MBOM

Creating an MBOM using the me_create_mbom utility

The me_create_mbom utility creates an MBOM based on a specific EBOM, but replaces make parts or phantom levels in the EBOM with manufacturing-specific parts and directly copies over buy parts.

Except in specific cases (see preferences below), do not use this utility to update the MBOM. To update an MBOM, use an accountability check or an advanced accountability check.

You can create a manufacturing bill of materials (MBOM) from an engineering bill of materials (EBOM) automatically using the me_create_mbom utility. This utility creates a new MBOM root node, and then either:

Copies over engineering parts that are designated as Buy or Phantom.
Replaces the parts designated as Make with new manufacturing parts containing the same in-context ID (IDIC) as the engineering part for future comparison.

Example

me_create_mbom -u=kj -p=kj -g=Engineering -key="item_id=000159,object_type=Item" -revrule="Latest Working" -mrevrule="Latest Working" -log=D:\workdir\create3.csv -usemfk

Caution

Log off any interactive session that uses the same structures as the structures you update with the utility before you use the utility to avoid failures due to locking of objects in that user session.

The utility is affected by the values of these preferences:

MEMBOM_Mirror_MakeRules This preference specifies a BOM Line property, such as bl_item_object_type, and property value pair that serve as input for the decision as to whether to create a manufacturing-specific part. There are two ways to view defined BOM Line property names:

In the BMIDE, you can check the properties defined for the object BOM Line.

In Structure Manager, if you right-click on the column title line and choose Insert Column(s)…, you get a list of the defined BOM Line properties.

Note 
 This preference accepts only a string value.
 If you require a boolean or other attribute, you should write your own Business Modeler Framework extension to control a make or buy decision.

Preference syntax KEY:,VALUE:,ACTION:

is the property on which the value criterion will apply (e.g. "GCS CP").

is the value used by the criterion.

is the action to undertake on the BOM node. Valid values are PartLink (links a Design node to Part node) and PartAssign (links and assigns a Design node Under a Part node). Note ACTION is only meant for Design/Part like structures. If more than one value for a given property can determine the action, the operator OR ('|') can be used as follows: "CopyKEY:<BOMLinePropertyInternalName>,VALUE:<PropertyValue1>,ACTION:<ActionValue1>|VALUE:<PropertyValue2>,ACTION:< ActionValue2>If there is no preference value, the item is shared between Engineering BOM (EBOM) and Manufacturing BOM (MBOM) structures.

A common criteria may be, for example, whether you make or buy a part. Any parts designated as Make or Phantom (for organizational purposes) in the EBOM are replaced by manufacturing-specific parts in the MBOM. In this case, the value of this preference may look like this: CopyKEY:Usage_MakeOrPurchase,VALUE:Make|VALUE:Phantom You can use a custom property in this preference. If you do not assign any value, the utility carries over the parts from the EBOM directly. Note You should write your own Business Modeler Framework extension to control a make or buy decision.

MEMBOM_Mirror_TypePrefixSuffix This preference specifies the target item type, naming prefix, and naming suffix used when creating MBOM items via the me_create_mbom utility. If you use custom manufacturing business object types, you can add this type to the value of this preference. Default Values: Item:Item:M_: Part:Part:M_: The preference supports two value formats:

Colon format: srcType:targetType:prefix:suffix Source-type aware mapping that allows different target types and naming rules per EBOM source type.

Comma format (legacy): targetType,prefix,suffix A single catch-all mapping applied to all source types.

The default value of -usemfk is false. If true, and only the object type is present in MEMBOM_Mirror_TypePrefixSuffix, use that type and the ebom item id for MFK value. If you set the command line option -usemfk to true and specify only the item type, you can enter multifield keys. If your company uses naming rules for new items, you must ensure that the prefix that you assign in this preference corresponds to the naming rules for the manufacturing item. Alternatively, you can remove all naming rules for manufacturing items. A conflict with item naming rules leads to this error message:

MEMBOM_Mirror_ReplaceMakeOnChange This preference specifies the behavior when, after creation of an MBOM, you change a make/buy property value from Make to Buy. At update, by default, Teamcenter simply appends the buy part to the existing structure without removing the make part already in the MBOM. If you set this preference to TRUE, at update, Teamcenter replaces the make part in the MBOM with the buy part from the EBOM, avoiding duplication of parts.
MEMBOM_Mirror_RemoveLineWithIDIC This preference is applicable to updating an MBOM with the utility. It specifies that if the in-context ID (IDIC) of a line in the MBOM is not found in the EBOM, or if a line in the MBOM has no IDIC, it is not removed at update if it is already stamped with an IDIC.
MEMBOM_Mirror_IDICOnChildren This preference determines whether the IDIC is retained on a make part in the MBOM when updating it using the utility after changing a make part to a buy part in the EBOM. When updating, if the MEMBOM_Mirror_ReplaceMakeOnChange preference is set to FALSE, both the original make part and the buy part exist in the MBOM after updating. This causes the accountability check to display multiple matches. Removing the IDIC on the make part ensures that there is only one match in an accountability check. If the MEMBOM_Mirror_ReplaceMakeOnChange preference is set to TRUE, the make line is replaced with the buy line from the EBOM so this preference is irrelevant.
MEMBOM_Mirror_IgnoreRules This preference uses the keyword ACTION to skip an EBOM node or to traverse below an EBOM node while ignoring that EBOM node. The children of the traversed EBOM node become the children of the corresponding MBOM parent.
MEMBOM_Mirror_AlignProperties This preference controls which properties and attachments are copied from the EBOM to the MBOM by enabling the alignment of properties on Make items and revisions. The Make nodes are of different types than the original EBOM nodes.

The following examples of running the utility demonstrate its use and the differences in output caused by changing the utility arguments. The initial values of the preferences are as follows.

CopyMEMBOM_MakeRules=KEY:Usage_Product,VALUE:Make|VALUE:Phantom
CopyMEMBOM_RemoveLineWithIDIC=FALSE
CopyMEMBOM_TypePrefixSuffix=Company,,

Note No prefix is used in this course due to the naming rule conflict.

Creating an MBOM

For the following EBOM:

Run the utility:

Copy

me_create_mbom -u=user-name -p=password -g=group -ebomroot=000202 -revrule="Latest Working" -mrevrule="Latest Working"

Produces the following MBOM:

Note the following:

The top-level node is replaced with a manufacturing-specific part.
The make and phantom parts are replaced with new manufacturing-specific parts.
The buy parts of the EBOM are directly copied over to the MBOM.
An IDIC is generated for all parts except for those below a buy part.
The in-context ID (IDIC) of the new parts is the same as the original part in the EBOM. This is true if the IDIC is already present in the EBOM part.
When you right-click the top node of the EBOM or MBOM and choose Link/Associate→Link Structures, you can see that the utility has linked the two structures.

Creating the MBOM to a specific level

For the following EBOM:

Run the utility:

Copy

me_create_mbom -u=user-name -p=password -g=group -ebomroot=000202 -revrule="Latest Working" -mrevrule="Latest Working" -depth=2

Produces the following MBOM:

Note that the new MBOM contains only two levels of structure. The remaining levels in the EBOM are ignored.

Updating the MBOM from a specific line

You now update the MBOM above, but only for the M_000225 line and down, requiring the following utility command:

Copy

me_create_mbom -u=your-user-name -p=your-password -g=your-group -ebomroot=000202 -scopeid=000225 -revrule="Latest Working" -mbomroot=M_000202 -mrevrule="Latest Working"

The utility creates the following MBOM:

Changing Make to Buy and Buy to Make in the EBOM

For the following EBOM and MBOM:

You change the Make value to Buy for the drive gears and change the Buy value to Make for the rcvr remote control in the EBOM and run the utility as follows:

Copy

me_create_mbom -u=user-name -p=password -g=group -ebomroot=000202 -scopeid=000225 -revrule="Latest Working" -mbomroot=M_000202 -mrevrule="Latest Working" -update

The results are as follows:

When the rcvr remote control part is changed from a Buy to a Make, the utility replaces the buy part in the MBOM during update. Buy to make behavior is not affected by preference settings. For the make to buy change (the drive gears), the behavior depends on two preferences:

The MEMBOM_Mirror_ReplaceMakeOnChange preference is set to FALSE. The make part is not removed from the MBOM. The buy part is added to the structure. The IDIC values on the make part are determined by the MEMBOM_Mirror_IDICOnChildren preference.

If MEMBOM_Mirror_IDICOnChildren is set to FALSE (or does not exist), the IDIC on the make part in the MBOM is retained. Performing an accountability check between the EBOM and MBOM results in multiple matches as the MBOM contains both a make and a buy part with the same IDIC.

If MEMBOM_Mirror_IDICOnChildren is set to TRUE, the IDIC on the make part in the MBOM is deleted and an accountability check displays the make part as missing in source. Caution You must exercise caution when removing an IDIC on any part. This can cause problems in other areas, for example, if the part is consumed in an process structure, you lose the link to that line.

The MEMBOM_Mirror_ReplaceMakeOnChange preference is set to TRUE. The buy part (drive gears) replaces the make part. The result of the MBOM after update is as follows:

In summary, the behavior of the preferences is as follows:

MEMBOM_Mirror_ReplaceMakeOnChange	FALSE	The buy part is added to MBOM and the previous make part is kept in the structure but its IDIC is removed.
MEMBOM_Mirror_IDICOnChildren	TRUE

MEMBOM_Mirror_ReplaceMakeOnChange	FALSE	The buy part is added to MBOM and the previous make part is kept in the structure but its IDIC is not removed.
MEMBOM_Mirror_IDICOnChildren	FALSE

MEMBOM_Mirror_ReplaceMakeOnChange	TRUE	The buy part is added to MBOM and the previous make part is removed in the structure, irrespective of the value of MEMBOM_Mirror_IDICOnChildren.
MEMBOM_Mirror_IDICOnChildren	TRUE/FALSE

Updating a released node in the MBOM

In the following EBOM and MBOM, M_000229/A;1–M_rear_drive_asm is released and then the make/buy property on its child, 000230/A;2–rear_axle, is changed from Buy to Make.

You revise the MBOM part so you have write access and run the update utility.

You run the utility with the -actiononrelease argument set to 2.

Copy

me_create_mbom -u=your-user-name -p=your-password -g=your-group -ebomroot=000202 -scopeid=000225 -revrule="Latest Working" -mbomroot=M_000202 -mrevrule="Latest Working" -actiononrelease=2 -update

The results are as follows:

The utility revises the part and replaces the old revision with the new one.

Changing properties in the EBOM

To detect property changes in the EBOM, run an accountability check between the EBOM and MBOM. You can propagate any property differences using the accountability check mechanism.

Attachments

Attachments are always synchronized as the attachment is created as a reference on the new make part. Any changes to the attachments on the EBOM side are automatically reflected in the MBOM. If you add a new attachment to the EBOM, you must run the update to see it in the MBOM part.