rdv_run_audit_report

Generates audit reports that report the information related to mismatches that exist between VAS CAD structure and usage data that is imported into Teamcenter. Audit reports allow you to check that design solutions exist for each option combination (NVE) required on the architecture elements. This feature assumes you use both part and design solutions; if you use only part solutions, do not use this report. Note You create audit reports for design solutions in Structure Manager. Use Platform Designer to create audit reports for part solutions. To create an audit report for design solutions, Teamcenter first performs a consistency check, verifying that for each design solution in the selected installation assembly, there is a part solution that matches the NVE on the design solution. It also checks that the variant condition on the design solution is consistent with the variant condition on the part solution. If the NVE changes on the architecture or part solution, the variant condition on the design solution may be out-of-date and require refreshing. Alternatively, the design solution itself may be changed to meet the new NVE requirement. Designers perform this type of audit on the installation assembly for which they are responsible. You cannot perform this audit on a level higher than the installation assembly. You can still use the audit report if no part solutions exist yet, because the NVEs on the architecture are checked. You can create an audit report for a particular configuration by setting the variant and revision rules audit algorithm details. The audit checks the following: If the NVE is not referenced by any solution. If the NVE is referenced by one or more solutions with a matching architecture element ID, but the variant condition is out-of-date (assuming there are no split NVEs). If the usage quantity is not a positive integer. If the solutions are referencing an NVE, but the architecture element ID references a split NVE. If the NVE is referenced by one or more solutions, but none of them have an architecture element ID that matches that of the NVE. The audit report delivers a list of architecture breakdowns in rows, with colored indicators specifying whether the line is an exact, partial, or mismatch with respect to an NVE, part number (typically the part solution ID), and usage quantity. The audit algorithms use data stored in occurrence notes on the design solution. It is therefore necessary to replace a design in the product using the Replace Design in Product wizard before the audit can be run to populate the appropriate occurrence notes. These occurrence notes are: Usage_Product Usage_PartNumber Usage_Quantity Configure these occurrence notes by setting the RDV_copied_occurrence_notes preference. Syntax rdv_run_audit_report [-u=user-id {-p=password | -pf=password-file} -g=group] [-product_id=item-id-of-top-level-product | -product_key=key-id-of-top-level-product] -product_rev_id=revision-id -v_rule=saved-variant-rule -rev_rule=revision-rule-name [-input_file=input-file-path | -keys_input_file=keys-input-file-path] -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. -product_id Specifies the item ID of the top-level product. -product_key Specifies the key of the top-level product. This argument can be used to identify an item instead of the -product_id argument. To find the key of an object, use the get_key_string utility. For more information, see Introduction to multifield keys in BMIDE for Data Model Design. -product_rev_id Specifies the item ID of the top-level product revision. -v_rule Specifies the saved variant rule. -rev_rule Specifies a named revision rule. Defaults to the site default, frequently the latest working revision. -input_file Specifies the path to the file used for input when you use the -product_id argument. -keys_input_file Specifies the path to the file used for input when you use the -product_key argument. -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. Related Topics Structure Management on Rich Client ─ Usage