rdv_import_usage

Imports usages from an XML file to Teamcenter usage representations. The utility applies all model NVEs available during the pre-usage stage to the top-level architecture node. The model NVEs are not applied to the children of the top-level architecture node (the architecture breakdown elements). However, the stored model NVEs on the top-level architecture element are available for manual application to any children in the architecture breakdown. When working in the Replace Design in Product wizard in Design Context or Structure Manager, the user can select the model NVEs from the top-level architecture breakdown, rather than from the preselected architecture breakdown element (ABE). Unlike in earlier versions of Teamcenter, model NVEs are not associated with the ABEs under the top-level architecture breakdown. Rather, model NVEs are stored as absolute occurrence data on the top-level architecture node. The utility creates the necessary absolute occurrence data at the top-level during the pre-usage import step. Platform Designer allows the user to view model and manual NVEs associated with the top-level. You can use the Add command to add associated manual NVEs from the variant expression block at the top level to the absolute occurrence data. Optionally, you can configure the utility to retry if it fails to complete a usage load for any reason on the first attempt. Failure to complete the load impacts downstream processes, as users cannot align their CAD solutions to the most recent PLM system changes. The utility retries obtaining a lock on the objects needing modification, typically, the product revision or top-level architecture node. Once a lock is obtained, the utility completes usage load operations. The optional ability for the utility to obtain the necessary locks is set with the RDV_enable_product_lock preference. Caution Data loss may occur if the utility removes the lock while a user is actively editing data associated with the top-level product. In the event of a failure while importing LOUs, it reports error codes and descriptions in the system log. These reports can be interpreted by users or scripts to take the necessary corrective action. Note The format of the NVEs created by this utility changed with effect from Teamcenter 2007.1 MP6. Newer versions of the utility automatically include options and values so that you can use those options for the manual creation of NVEs and saved variant rules (SVRs) in Platform Designer. While running the utility, Teamcenter checks to see if the item ID of the product item is present in the PSM_global_option_item_ids preference. If so, it automatically creates the variability on the top level architecture breakdown. The import utility then applies variability for every option-value on the architecture breakdown (VAB). During execution of the rdv_import_usage utility, Teamcenter does not enforce hierarchical variability on the architecture breakdown (VAB). If you used an earlier version of this utility to create NVEs, you should run the gmo_migrate_usage_nves utility to migrate them to the new format. If you created NVEs in Teamcenter 2007.1 MP6 or later, it is not necessary to migrate them. Examples of the old and new formats follow: Old NVE format New NVE format D1_2008-UP_8619_2WC69_P D1_8619_2WC69_000Year_2008-UPProductionUsage D1_2007-07_8619_2WR69_P D1_8619_2WR69_000Year_2007-07ProductionUsage D1_2007-07_8619_2WP69_P D1_8619_2WP69_000Year_2007-07ProductionUsage A sequence number is appended to the authorized NVE so that true availability changes in model codes across years may be recorded in the NVE content. In the previous examples, the sequence number is 000. Syntax rdv_import_usage [-u=user-id {-p=password | -pf=password-file} -g=group] -input_file=name-of-xml-file -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. -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. -input_file Specifies the XML input file from which the utility imports usages. -h Displays help for this utility. Environment As specified in Setting up a Teamcenter command-line environment. The TC_retry_time preference determines the time interval at which the utility tries to obtain a lock on objects to import, if it is not initially successful. You can set this preference as an environment variable so that the default value can be overridden by scripts during usage loading. The TC_max_number_of_retries preference determines how many attempts the utility makes to obtain a lock on objects to import, if it is not initially successful. You can set this preference as an environment variable so that the default value can be overridden by scripts during usage loading. Restrictions None. Files As specified in Log files produced by Teamcenter. Examples To import usages, enter the following command on a single line: Copy rdv_import_usage -u=user-name -p=password -g=group -input_file=pdis101.x The utility uses the RDV_IMPORT_USAGE_TM transfer mode to convert the XML file to PLM XML format, via a style sheet. Related Topics Teamcenter Automotive Edition