availability_to_availability_rule_utility

Creates equivalent availability rules for present availability objects in the system. Beginning in Teamcenter 10.1.7, Product Configurator on Rich Client ─ Usage does not consider constraints based on Family Availability and Option Value Availability objects. To ensure consistent constraint evaluation results, you must generate Availability Rule objects that correspond to the Family Availability and Option Value Availability objects created in earlier Teamcenter versions. Beginning in Teamcenter 10.1.7, Family Availability and Option Value Availability objects can no longer be created in Product Configurator on Rich Client ─ Usage. After the Teamcenter 10.1.7 upgrade, site administrators execute the availability_to_availability_rule_utility utility to generate the corresponding Family Availability rule objects. You must run this utility if: You are migrating to Teamcenter 10.1.7, and Family Availability and Option Value Availability objects exist in the Teamcenter version you are migrating from. The availability_to_availability_rule_utility utility does not release the newly created Availability Rule objects, even if existing Option Value Availability or Family Availability objects are released. If required, you need to release newly created availability objects manually, after running this utility. The history of availability objects is not migrated. The availability_to_availability_rule_utility utility execution may take a significant time, depending on the number of existing availability constraints defined in the system. If you have a large number of availability constraints, consider running the utility during off-peak hours. Syntax availability_to_availability_rule_utility [-u=user-id {-p=password -g=group-batch_size] 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 user and password 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. -g Specifies the group associated with the user. If used without a value, the user's default group is assumed. -batch_size Specifies how many rules are processed in bulk. By default, the size is set to 100. This utility retains the original effectivity as set on the availability constraints prior to migration. Effectivity on availability constraints are applied to newly created availability rules. Example You have a Color family with Red, Green, and Black values. Below are existing availability constraints in Teamcenter 10.1.6. Family availability constraint Color → VXI Color family is made available to model VXI Value availability constraint Red → VXI Red value made available to model VXI Value availability constraint Green → VXI Green value made available to model VXI) with Date Effectivity (2012-09-01 to 2016-09-01) After you run the availability_to_availability_rule_utility migration utility, after the Teamcenter 10.1.7 upgrade, two new availability rules are created as follows: Availability rule Red → VXI Applicability → VXI and Subject → Red Availability rule Green → VXI Applicability → VXI and Subject → Green with Date Effectivity (2012-09-01 to 2016-09-01)