me_create_mbom

Creates or updates a manufacturing bill of materials (MBOM) from an engineering bill of materials (EBOM). The resulting MBOM structure can contain MBOM-specific levels that represent make items. Note The me_create_mbom utility does not support naming rule as user can specify any prefix/suffix. Use this utility only to create a new MBOM. If you need to update an MBOM, use an accountability check or an advanced accountability check. For more information, see Manufacturing Process Planning ─ Deployment and Administration. Syntax me_create_mbom -u=user-id -p={password | -pf=password-file} [-g=group ] {-ebomroot=item-id -key=multi-field-key-of-structure-root -revid=revision-selector -scname=structure-context-name|-scuid=structure-context-internal-ID -rev_rule=revision-rule -mbomroot=item-id -mkey=multi-field-key-of-structure-root| -mrevid=revision-selector -mscname=structure-context-name|-mscuid=structure-context-internal-ID -mrev_rule=revision-rule -scopeid=scope-ID|-scopeidincontext=scope-in-context-ID|-scopekey=scope-in-context-key -depth=level-from-root-structure -actiononrelease=1|2|3|4 -update -usemfk -log|-logrelation|-logobjectuid -loglevel=1|2|3 [-h] Arguments -u Specifies the user ID. This is a user with Teamcenter administration privileges. Note If Security Services single sign-on (SSO) is enabled for your server, the -u and -p arguments are authenticated externally through SSO rather than being authenticated against the Teamcenter database. If you do not supply these arguments, the utility attempts to join an existing SSO session. If no session is found, you are prompted to enter a user ID and password. -p Specifies the password. This argument is mutually exclusive with the -pf argument. -pf Specifies the password file. For more information about managing password files, see Manage password files. This argument is mutually exclusive with the -p argument. -g Specifies the group associated with the user. If used without a value, the user's default group is assumed. -ebomroot Specifies the item ID of the engineering bill of materials that is used as the basis for the new or updated manufacturing bill of materials. This value is mandatory unless an -scname, -scuid, or -key is specified. -key Specifies the key of the top line when multiple attributes are used to form the unique item ID. Use the following format: Copy [keyAttr1=keyVal1] [,keyAttr2=keyVal2]…[,keyAttrN=keyValN] To find the key of an object, use the get_key_string utility. This value is mandatory unless an -scname, -scuid, or -ebomroot is specified. For more information, see BMIDE for Data Model Design. If you use this argument, you must also specify a revision rule using the -revrule argument. -revrule Specifies the revision rule of the EBOM. This argument is mandatory if you specify the -ebomroot or -key arguments. -revid Specifies an additional revision id to be used with itemid to pick a specific revision for ebom root. -scname Specifies the name of the structure context representing the EBOM structure within a collaboration context object. You must specify this value if you do not specify a value for the -scuid, -ebomroot, or -key arguments. -scuid Specifies the internal ID of the structure context representing the EBOM structure within the collaboration context object. You must specify this value if you do not specify a value for the -scname, -ebomroot or -key arguments. -mbomroot Specifies the item ID of the manufacturing bill of materials that is to be created or updated. This value is mandatory unless an -mscname, -mscuid, or -mkey is specified. -mkey Specifies the key of the MBOM top line when multiple attributes are used to form the unique item ID. Use the following format: Copy [keyAttr1=keyVal1] [,keyAttr2=keyVal2]…[,keyAttrN=keyValN] To find the key of an object, use the get_key_string utility. This value is mandatory unless an -mscname, -scuid, or -mbomroot is specified. For more information, see BMIDE for Data Model Design. If you use this argument, you must also specify a revision rule using the -revrule argument. -mrevrule Specifies the revision rule of the MBOM. This argument is only required when you update an MBOM and is mandatory if you specify the -itemid or -key arguments. -mrevid Specifies an additional revision id to be used with itemid to pick a specific revision for the existing MBOM root. -mscname Specifies the name of the structure context representing the MBOM structure within a collaboration context object. You must specify this value if you do not specify a value for the -mbomroot or -mkey arguments. -mscuid Specifies the internal ID of the structure context representing the MBOM structure within the collaboration context object. You must specify this value if you do not specify a value for the -mbomroot or -mkey arguments. -scopeid Optionally specifies the item ID in the EBOM from which to begin the update. You do not have to update an entire MBOM each time you run this utility. You can choose to update only specific nodes. This argument cannot be used with -scopeidincontext. If no scope argument is specified, Teamcenter begins the traversal at the top line in the manufacturing BOM. -scopekey Optionally specifies the key ID in the EBOM from which to begin the update. You do not have to update an entire MBOM each time you run this utility. You can choose to update only specific nodes. This argument cannot be used with -scopeidincontext or -scopeid. If no scope argument is specified, Teamcenter begins the traversal at the top line in the manufacturing BOM. -scopeidincontext Optionaly specifies the IDIC of the line in the EBOM from which to begin the traversal. This argument is useful if you have multiple instances of the same subassemblies within an assembly. You can specify exactly which instance to update using the in-context ID. This argument cannot be used with -scopeid or -scopekey. If no scope argument is specified, Teamcenter begins the traversal at the top line in the manufacturing BOM. -depth Specifies the number of levels to traverse when creating or updating the MBOM. It may not be necessary to traverse to all leaf nodes in a structure. -actiononrelease When running an update, determines the action to take if, when trying to mirror a changed EBOM node, the corresponding node in the MBOM is released. 1 Skip the EBOM node and make no changes to the MBOM node. 2 Revise and modify the MBOM node in the next working revision to contain the changes. 3 Update the properties on released item where permissions permit. 4 Update properties on the MBOM and its children. Note There are many situations that may require one or more -actiononrelease options depending on your business process, how data is added to Teamcenter, and other considerations. For example, If your business process involves a design change in which you may either revise an EBOM node or create a new part, option 1 is relevant. If the business process is to always revise an EBOM node for a design change, option 2 is relevant. To migrate data, you should run the utility on the released parts using option 3 . The default value is 1. -update Updates an existing MBOM with changes in the corresponding EBOM. If you set this, you must specify the -mbomroot and -mrevrule, or the -mscname or -mscuid. -usemfk If specified, and the only object type present is defined in the MEMBOM_Mirror_TypePrefixSuffix preference, Teamcenter uses that type and ebom item_id for the MFK value. -log Writes additional failures and information to a log file. If specified, log file is written to disk and not attached to any object. You must specify an absolute path to the file. -loglevel Controls the level of logging. 1 (Default) Log errors only. 2 Log errors and warnings. 3 Log errors, warnings, and information. -logrelation If -log is not specified, uses the internal relation type name to attach the log file to the MBOM root item revision. Default value is IMAN_reference. -logobjectuid The uid of the persistent object to which the log file must be attached. If an invalid uid is supplied, the log is attached to the MBOM root item revision. -h Displays help for this utility. Environment As specified in Setting up a Teamcenter command-line environment. Files As specified in Log files produced by Teamcenter. Restrictions None.