# Manage Products Vault makes managing large groups of products efficient. You can configure a _Product_ record with product, registration, and substance details for each product on which your organization monitors and reports. Optionally, to group products with the same substance, you can create _Product Families_ for an _Organization_. _Product Families_ can include _Datasheets_, which are applied to all _Products_ in the family without a specified _Datasheet_. You must set up your _Product_ library to add _Study Products_ and _Combination Products_. Your company _Product_ library is a key component in many features, which includes the following: * **E2B Import**: During an E2B import, Vault attempts to match products in the E2B file to products configured in the _Product_ library. * **ICSR Report Generation**: When Vault generates ICSRs (including E2B, FDA 3500A, and CIOMS I reports) certain fields are mapped from the _Product_ library. These fields are identified in their descriptions below. * **Aggregate Reports**: Products added to an aggregate report Reporting Family are used to filter _Cases_ to include in report tabulations. * **Reporting Rules**: Vault looks at local _Product Registrations_ for _Case Products_ to generate _Submissions_ according to reporting rules in your Vault. * **Watchlists**: You can set up _Watchlists_ to monitor _Cases_ with certain _Products_. _Case Products_ must be suspect or interacting to trigger watchlists. * **Automatic Expectedness and Listedness**: Set up _Products_ and _Product Datasheets_ for Vault to determine whether an adverse event is expected or unexpected. ## Prerequisites To use this feature, your Admin must configure the following: * To manage [_Substances_][9] on _Products_, enable Substances. * To use [unknown formulation _Products_][10], enable Unknown Formulation Product Selection. * To assign [_Default Alias_][19] values, enable Product Coding: Additional Matching Fields for Product Aliases. * To use [Inactivate Products and Product Registrations][18]: * Inactivate Products and Studies * Product Browser for Faster Case Product Selection * Inactivate Product & Study Registrations ## Create Products {#create-products} Add a _Product_ for each company product for which you will process _Cases_ in Vault. When you add a _Case Product_ linked to a record in the company _Product_ library, Vault maps values from the _Product_ to the _Case Product_. To support organizing and maintaining your _Product_ library, products can be grouped into _Product Families_. All _Products_ within a _Product Family_ must have the same _Substance_ and be linked to the same _Organization_. If products become inactive, you can [deprecate][7] the records. ### Add a Product Family {#add-a-product-family} To add a _Product Family_: 1. Navigate to **Business Admin > Objects > Product Families**. 2. On the _Product Families_ page, select **Create**. 3. On the _Create Product Family_ page, complete the applicable [fields][11]. 4. Select **Save**. Upon saving a _Product Family_, a [_Products_ section][12] appears. Vault populates this section with any _Products_ that are linked to the _Product Family_. You can select **Add** to add existing _Products_ or to create new _Products_ to include in the _Product Family_. Depending on your Admin's configuration, Vault may create an [unknown formulation _Product_][10] on the _Product Family_. #### Product Family Fields {#product-family-fields} The following fields may be available:

Field	Description
Name	Enter a name for the Product Family.
Organization	Select the Organization to which the Product Family belongs.
Product Family Abbreviation	Enter an abbreviation for the Product Family.
API Name	Enter a unique API Name for the Product Family. The Product Family reporting rule parameter uses this value to determine if a Case Product belongs to this Product Family.
Family Datasheet	Add a Datasheet that applies to all Products within the Product Family that do not have a specified datasheet. If the Product Family's Datasheet changes, Vault applies those updates to those Products.
Therapeutic Area	Select the Therapeutic Area for the Product Family.
EMA Substance Group	When importing literature references from an EMA MLM RIS file, Vault populates the substance code used by the EMA MLM service.

### Add a Product {#add-a-product} To add a _Product_: 1. Navigate to **Business Admin > Objects > Products**. 2. On the _Products_ page, select **Create**. 3. In the _Create Product_ window, select the type, then select **Continue**. * If the _Product_ has multiple _Product Type_ registrations to meet agency requirements, select **Product**. If not, select from the other options. When you select a product type registered in the FDA's jurisdiction, the product type determines how Vault generates submissions to the FDA. 4. On the _Create Product_ page, complete the applicable [fields][13]. 5. Select **Save**. #### Unknown Formulation Products {#unknown-formulation-products} If your Admin has configured unknown formulation _Products_, Vault provides a standard method of handling cases with limited product information with the following: * Vault creates an unknown formulation _Product_ on [newly created _Product Families_][14] * You can select the [_Unknown Formulation_ checkbox][15] on a _Product_ to indicate that it has an unknown formulation * Vault maps all updated [_Substances_][9] on any _Product_ in the _Product Family_ to the unknown formulation _Product_ * When coding _Products_, you can filter your search results to only unknown formulation _Products_ * The _Inbox Item to Case Compare_ page considers all _Products_ in the _Product Family_ as potential matches

Note: For unknown formulation Products to work as expected, you must organize your Products within Product Families.

#### Product Fields {#product-fields} The following fields may be available:

Field	Description
Organization	Select the organization to which the Product belongs. When adding a Case Product, the Case must be associated with this organization to allow users to select this product.
Product Name	Enter the primary name of the product. Vault references the product using the name that you enter in this field. When a Case Product references this Product, Vault uses this field to generate the Case Product Name.
Product Family	Select the Product Family to which the Product belongs. Vault populates the Product Families section of the Product with this value.
Abbreviation	Enter the abbreviated name for the product. This field is for reference only.
Generic Name	Enter the generic name for the product. For Device-type products, Vault exports this value when generating FDA E2B(R2), FDA VAERS E2B(R3), and FDA MedWatch 3500A report formats. For any Case Product with an eligible Drug Role, Vault exports this value to CIOMS I forms.
Vaccine Type	If the product is a vaccine, select the vaccine type. When a Vaccine-type Case Product references this Product, Vault maps this field to the Case Product.
International Birthdate	Enter the date when a regulatory authority first granted marketing authorization for the product. Vault uses this value in report generation for FDA MedWatch 3500A formats.
Expiration Date	Enter the expiration date for the product. Partial dates are supported and the minimum precision required is the year. Vault maps this field to the Case Product. For Device-type products, this field is used in report generation for FDA E2B(R2) (B.4.k.2.4.FDA.1).
Manufacturer	Select the organization that manufactures the product, if it is different from the one selected in the Organization field. For device-type Products, when this field contains an organization value, that organization is used in report generation for FDA E2B(R2), FDA VAERS E2B(R3), and FDA MedWatch 3500A report formats.
Core Datasheet	Select the core Datasheet for the Product Family. Vault uses Datasheets to detect expectedness for an adverse event and the suspect or interacting Case Products.
Product Use Type	Select the Product Use Type. When users are searching for Products in the Product Browser on Inbox Items and Cases, Vault returns only Products for which this field is Company Use or blank.
Non-Company Product	If selected, Vault will consider Marketing→Investigational and Marketing→Marketing (Cross-Agency) cross reporting scenarios for the Product.
API Name	Enter a unique identifier that can be used with the Safety "Product" rule parameter to define a specific Product for a reporting rule.
Market Segment	Select a market segment from the picklist.
Device Nomenclature Code	Enter the numeric code corresponding to the device. During report generation, Vault maps this value to EU MIR and MHRA MIR forms.
Basic UDI-DI	Enter the Basic UDI-DI key. During report generation, if the Basic UDI-DI on the Case Product is blank, Vault maps this value to EU MIR and MHRA MIR forms.
FEI Number	Enter the unique FDA Establishment Identifier (FEI) assigned to the FDA-regulated facility. Vault exports this to the September 2025 version of the FDA MedWatch 3500A form.
Brand Name	Enter the brand name.
Description of Device	Enter a description of the device.
Unknown Formulation	Select the checkbox to indicate an unknown formulation. A Product Family can contain only one unknown formulation Product.

## Add Product Registration Details {#add-product-registration-details} Add _Product Registrations_ for each country in which the product is registered. Vault looks at the _Product Registration Countries_ for _Case Products_ to generate _Submissions_ according to reporting rules in your Vault. When you select the _Product Registration_ on a _Case Product_, upon saving the record, Vault maps fields from the _Product Registration_ to the _Case Product_. If product registrations become inactive, you can [deprecate][8] the records. ### Add a Product Registration {#add-a-product-registration} Add product registration details for each country in which the product is registered. 1. Navigate to **Business Admin > Objects > Products > [Product]**. 2. Under _Registrations_, select **Create**. 3. Complete the _Create Product Registration_ page. 4. Select **Save**. #### Product Registration Fields {#product-registration-fields}

Field	Description
Organization	Vault populates this field with a reference link to the Organization on the parent Product record. If the Registration Holder/Applicant field is blank, Vault maps this field to the Registration Holder field on Case Products.
Product	Vault populates this field with a reference link to the Product parent record.
Registration Name	Enter a name for the Product Registration. Vault references the registration using the name that you enter in this field.
Product Type	Vault populates this field with the product type of the Product parent record.
FDA Product Type	Select a product type. Vault exports the value to the August 2024 and September 2025 versions of the FDA MedWatch 3500A form.
Combination Type	If the product is a combination product, select the combination type. Vault maps this field to the Case Product and is used in report generation for the FDA VAERS E2B(R3) format.
Registration Number	Enter the product authorization or application number for the country where the product is marketed. For U.S. Registrations, ensure that the value you enter in this field adheres to the FDA E2B format requirements for element B.4.k.4.1 (Authorisation / Application Number). Vault maps this field to the Case Product and is used in report generation for E2B, FDA MedWatch 3500A, and PADER formats.
Registration Date	Enter the date when the product was registered. This field is for reference only.
Registration Type	Select the registration type. This field is used in report generation for FDA MedWatch 3500A and PADER formats. This field is needed to correctly match Transmission Profile Scope records for any Organization with multiple Transmission Profiles for the same destination Agency.
Country	Select the country where the product is registered and authorized. Vault maps this field to the Registration Country field on a Case Product and is used in report generation for E2B formats.
Route of Administration	Select the route of administration TermID code. This field is for reference only.
Compounding Type	For compounded products, select the compounding type. Vault maps this value to Case Products and references it in report generation for E2B and FDA MedWatch 3500A formats.
Agency	Based on the Country selected on the Product Registration, Vault populates this field with the Agency assigned jurisdiction over that country. If configured, reporting rules generate Submissions to this Agency when a Case Product references this Product Registration.
Transmission Profile	Select a Transmission Profile for Vault to use when generating Submissions for this registration. We recommend populating this field when you have a Transmission Profile corresponding to this reporting destination and report type.
Local Datasheet	Select the Local Datasheet for this product registration. A Local Datasheet is specific to a country or region, listing expected adverse events that apply to that product registration. Datasheets are used to detect expectedness for an adverse event and the suspect or interacting Case Products.
Registration Holder/Applicant	Vault maps this value to the Registration Holder/Applicant field on Case Products. If this field is blank, Vault maps the Organization value.
MAH	This field may also be named Reporting Organization depending on your Admin's configuration. If you have a Marketing Authorization Holder (MAH) that manages your ICSR reporting obligations for this registration, select the Organization. Selecting an Organization in this field creates an MAH Distribution List, and thereby a reporting obligation, for this registration. Note: Removing the last remaining MAH/Reporting Organization from an MAH Distribution List will also delete the MAH Distribution list. Warning: Use caution when setting this field. Reporting Obligations are for Distributions only and override agency submission rules. Do not select an Agency such as the FDA or EMA.
Registered As	Select the product type for this registration. Vault maps this value to the Registered As field on Case Products. When generating E2B Transmissions for this registration, Vault maps this field, then uses that value to determine whether Device-type Combination Product Constituents are exported. See Exclude Device Constituents from E2B Exports for more information. When generating an FDA 3500A form for a non-Combination Company Product, this field determines which section of the form is populated, as follows: If the Registered As field is set to Device or OTC Device, populate the Suspect Medical Device sections. If the Registered As field is not set to Device or OTC Device, populate the Suspect Product(s) section. If the Company Product has multiple FDA registrations (one device, and one non-device, for example), populate the Suspect Product(s) section. If the Company Product has no FDA registration, populate the Suspect Product(s) section. For information on how the product type for a registration is used when evaluating reporting rules, see the Product Registration Type rule parameter. This field does not appear on layouts by default, but can be added to Transmission layouts by your Admin. Depending on your Admin's configuration, this field may be called Transmission Product Type.
Default Registration	Designates the registration as the most current or commonly used registration for the selected country. If the registration is the most commonly used for the selected country, select the checkbox. During data entry, in the Case Product Registration field, this registration is prioritized in the picklist, though all active Product Registrations remain available for use.
Strength	Enter the strength of the product. In the first field, enter a numeric value. In the second field, select a unit of measurement from the picklist or enter a custom unit.
MPID	Enter the UMC Medicinal Product Identifier (MPID) for the product. Note: You can specify only one type of product identifier. Do not specify an MPID if you have entered an IDMP MPID or PhPID. Vault maps this field to the Case Product and is used in report generation for E2B(R3) and CIOMS I formats.
IDMP MPID	Enter the Identification of Medical Products (IDMP) MPID for the product. Note: You can specify only one type of product identifier. Do not specify an IDMP MPID if you have entered an MPID or PhPID.
PhPID	Enter the Pharmaceutical Product Identifier (PhPID). Note: You can specify only one type of product identifier. Do not specify a PhPID if you have entered an MPID or IDMP MPID. Vault maps this field to the Case Product and is used in report generation for E2B(R3) and CIOMS I formats.
National Drug Code	Enter the US National Drug Code (NDC) or unique identifier for the product. This field is used in report generation for FDA MedWatch 3500A formats.
Product Code	Enter the device Product Code. Vault maps this field to Device-type Case products, and it is used in report generation for FDA E2B(R2), FDA VAERS E2B(R3), and FDA MedWatch 3500A report formats.
Local Product Code	Enter the region-specific Medicinal Product Identification (MPID) code. This field is used for Localized Cases.
Trade Name	Enter the trade name of the product registration. Vault maps this field to Device-type Case products, and it is used in report generation for FDA E2B(R2) (B.4.k.20.FDA.1).
Applicable legislation unknown	Select Yes or No to identify whether applicable legislation for the device is unknown. During report generation, Vault maps this value to EU MIR forms.
MDD/AIMDD Risk Class	Select the risk class of the medical device. During report generation, Vault maps this value to EU MIR and MHRA MIR forms.
IVDD Risk Class	Select the risk class of the medical device. During report generation, Vault maps this value to EU MIR and MHRA MIR forms.
MDR Class	Select the MDR class of the medical device. During report generation, Vault maps this value to EU MIR and MHRA MIR forms.
MDR Type	Select the MDR type of the medical device. During report generation, Vault maps this value to EU MIR and MHRA MIR forms.
IVDR Class	Select the IVDR class of the medical device. During report generation, Vault maps this value to EU MIR and MHRA MIR forms.
IVDR Type	Select the IVDR type of the medical device. During report generation, Vault maps this value to EU MIR and MHRA MIR forms.
Notified Body ID	Enter the identification number for the bodies that granted the CE mark for the device. During report generation, Vault maps this value to EU MIR and MHRA MIR forms.
Notified Body Certificate Number	Enter the certificate number of the bodies entered in the Notified Body ID field. During report generation, Vault maps this value to EU MIR and MHRA MIR forms.
Device Market Date Type	Select the device market date type. During report generation, Vault maps this value to EU MIR and MHRA MIR forms.
Device Market Date	Use the calendar to select the device market date corresponding to the device market date type or enter the date manually. During report generation, Vault maps this value to EU MIR and MHRA MIR forms.
EU Market After Application Date	Select Yes or No to indicate whether the device continued to be placed on the EU market after the MDR/IVDR date of application. During report generation, if the EU market after application date on the Case Product is blank, Vault maps this value to EU MIR form field 2.e.
Deleted in RIM?	For records generated by the Safety-RIM Connection, this field indicates whether the source record has been deleted in the RIM Vault. Safety preserves the record in case other object records reference it.
Expiration Date	Indicates the date the registration expires if no renewal is submitted. Vault populates this field based on data received from the Safety-RIM Connection.
Marketing Start Date	Indicates the date on which the product became available in this market. Vault populates this field based on data received from the Safety-RIM Connection.
Marketing End Date	Indicates the date on which the product is no longer available in this market. Vault populates this field based on data received from the Safety-RIM Connection.
Marketing Status	Indicates the marketing status for the registration and presentation in this market. Vault populates this field based on data received from the Safety-RIM Connection.
Product Alias	Indicates the reference number for the product alias. Vault populates this field based on data received from the Safety-RIM Connection.
Product Family	Indicates the Product Family of this registration. Vault populates this field based on data received from the Safety-RIM Connection.
Product Variant	Indicates the registered presentation or product variant. Vault populates this field based on data received from the Safety-RIM Connection.
Registration End Date	Indicates the date on which the registration ends. Vault populates this field based on data received from the Safety-RIM Connection.
Registration Status	Indicates the date on which the registration moved to its current status. Vault populates this field based on data received from the Safety-RIM Connection.
RIM Lifecycle Status	Indicates the lifecycle state of the source record in the RIM Vault. Vault populates this field based on data received from the Safety-RIM Connection.
RIM Registration Type	Indicates the type of registration. Vault populates this field based on data received from the Safety-RIM Connection.
RIM Status	Indicates whether the source record in the RIM Vault is Active or Inactive. Vault populates this field based on data received from the Safety-RIM Connection.
Additional Monitoring	Select whether additional product monitoring is required by the health authority in this market. This field supports Annex H documents in PSMF reports.
Application Lead Market	Indicates the primary market of the related application to which this registration applies. Vault populates this field based on data received from the Safety-RIM Connection. This field supports Annex H documents in PSMF reports.
Application Number	Indicates the application number associated with the registration. Vault populates this field based on data received from the Safety-RIM Connection. This field supports Annex H documents in PSMF reports.
Non-Standard Aggregate Periodicity	Select whether the product has a non-standard aggregate report submission cycle in this market. This field supports Annex H documents in PSMF reports.
Procedure Number	Indicates the procedure number issued by the health authority. Vault populates this field based on data received from the Safety-RIM Connection. This field supports Annex H documents in PSMF reports.
Procedure Type	Indicates the procedure type under which the related application will be reviewed in the European Union (EU). Vault populates this field based on data received from the Safety-RIM Connection. This field supports Annex H documents in PSMF reports.

#### PMDA Fields Use the PMDA fields to set up regional information when adding Japan Product Registrations. ### Product-Manufacturer Site {#p-m-site} Use the _Product-Manufacturer Site_ section to link _Manufacturer Sites_ with _Product Registrations_ for the United States. You can create a _Product-Manufacturer Site_ record for each _Product Registration_ to track adverse events by site. When a user adds a _Case Product_ for the _Product Registration_, Vault populates the _Manufacturer Site_ field. Vault exports this value to FDA eMDR and FDA MedWatch 3500A reports. ## Add Substances {#substance-records} Configure substance information to map information to _Cases_ for E2B export as follows: * **E2B(R3)**: Section G.k.2.3.r Substance / Specified Substance Identifier and Strength * **E2B(R2)**: Data element B.4.k.2.2 Substance / Specified Substance Name When a _Case_ contains a _Case Product_ linked to a company _Product_ with preconfigured _Substances_, Vault maps each _Substance_ to create _Case Product Substances_. PSUR aggregate reports can leverage _Substances_ to filter _Cases_ to include in the report tabulations. Other aggregate reports do not leverage _Substances_.

Note: We recommend that you link a Substance at the Product level instead of adding a Substance to a Study Product. You should only add a Substance at the Study Product level when you need the Strength fields to appear. If a Study Product Substance exists, it will supersede any Product Substances on the Case.

### Add a Substance to a Product {#add-substance-to-product} To add a _Substance_ to a _Product_: 1. Expand the **Substances** section, then select **Add**. 2. From the _Search: Substance_ window, use either of the following methods to add a _Substance_: * To select existing _Substances_ from the library: 1. Optional: Use the search bar or filters to refine your search. 2. Select the applicable _Substances_. 3. Select **OK**. * To create a new _Substance_: 1. Select **Create**. 2. On the _Create Substance_ page, complete the applicable [fields][16]. 3. Select **Save**. 3. Select **OK**.

Note: You can also add a Substance to a Product from Business Admin > Objects > Substances. Create or select a Substance, and then expand the Products section and select Add.

Whenever you add or remove a _Substance_ from a _Product_ within a _Product Family_, Vault maps all updated _Substances_ across all _Products_ to the [unknown formulation _Product_][10] on the _Product Family_. You can run the [_Sync Substances_][17] action to update all _Product Substances_ associated with a _Product Family_. #### Product Substance Fields {#product-substance-fields} The following fields may be available:

Field	Description
Substance Name	Enter the name of the substance. Vault references the substance using the name that you enter in this field. Vault maps this field to the Case Product Substance and is used in report generation for E2B(R2) and E2B(R3) formats. This field supports up to 128 characters. If your Admin has configured your Vault for 250-character Substance Names, this field may be unavailable and have a different field name.
Substance Name	Enter the name of the substance. Vault references the substance using the name that you enter in this field. Vault maps this field to the Case Product Substance and is used in report generation for E2B(R2) and E2B(R3) formats. This field supports up to 250 characters. Your Admin must enable this field in your Vault.
Organization	Select the organization or use the binoculars icon to search for the organization associated with the substance.
Substance ID	Enter the unique identifier for the substance. This field is for reference only.
Term ID	Enter the substance TermID. Vault maps this field to the Case Product Substance and is used in report generation for E2B(R3) formats.
Term ID Version	Enter the version date or number for the TermID. Vault maps this field to the Case Product Substance and is used in report generation for E2B(R3) formats.
Description	Enter a description for the substance. This field is for reference only.

### Sync Product Substances {#sync} You can run the _Sync Substances_ action to update all _Substances_ for all _Products_ in a _Product Family_. You can run the action on individual _Product Family_ records and on multiple records in bulk. To run as a bulk object record action: 1. Navigate to **Products > Product Families**. 2. Optional: Apply filters to narrow down the list of _Product Families_ you want to synchronize with substance details. 3. From the **All Actions** menu, select the option to perform a bulk action on all records. 4. On the _Refine Selection_ page, review the list of selected records and clear the checkboxes of any _Product Families_ for which you do not want to update. 5. Select **Next**. 6. On the _Choose Action (Step 2)_ page, select **Record Actions** in the _Manage Records_ section. 7. Click **Next**. 8. On the _Choose Record Action (Step 3)_ page, select **Sync Substances (bulk)**. 9. Select **Next**. 10. On the _Confirmation_ page, review the summary of changes and select **Finish**. When the action completes, you'll receive an email and a Vault notification letting you know if the action was successful or if there were any errors. ## Create Product and Substance Aliases {#alias} During E2B or JSON import, Vault attempts to match the _Case Product_ with the relevant _Product_ in your library. You can set up _Product_ matching using _Product_ and _Substance Aliases_. If Vault cannot find a match for the _Case Product_ using non-Study matching, it will attempt to use aliases you set up in the library. ### Add a Product Alias {#product-alias} To add a _Product Alias_: 1. Navigate to **Business Admin > Objects > Product Aliases**. 2. Select **Create**. 3. Complete the following information: * **Alias**: Enter the alias name. * **Product**: Select the _Product_ the alias is associated with. * **Default Alias**: To make this _Product Alias_ a default, select **Yes**. 4. Select **Save**. Now, Vault can match any _Case Product_ with this alias to the associated _Product_ in your library. Vault adds the _Generic_ and _Localized_ names from the _Product_ record as aliases. #### About Product Alias Matching The _Product Alias_ matching logic uses the _Organization_ field and the following _Product_ fields on _Inbox Items_ for additional matching: * _Country Obtained_ * _Dose Form_ * _Patient ROA_ * _Dosage_ * _Dose Strength and Unit_

Note: If the imported product contains more than one Dosage record, Vault uses the existing logic for Product matching. Instead of using these additional Product fields, Vault will use only the Product Alias name.

If the imported product still matches with more than one library _Product Alias_, Vault checks if either of them is set as the [_Default Alias_][6] and selects this library _Product Alias_ for auto-coding. Vault also looks for the _Default Alias_ if no _Inbox Item Product_ fields match between the imported product and the library _Product Alias_. If there is no _Default Alias_, Vault does not code the product. If multiple _Default Aliases_ are configured, Vault uses the one with the latest modified date. ### Add a Substance Alias Consider adding _Substance Aliases_ for _Cases_ where users mistakenly enter a _Substance Name_ as the _Product_. To add a _Substance Alias_: 1. Navigate to **Business Admin > Objects > Substance Aliases**. 2. Select **Create**. 3. Complete the following information: * **Substance**: Select the **+** the alias is associated with. * **Alias**: Enter the alias name. 4. Select **Save**. Now, Vault can match any _Case Product_ with this _Substance_ alias to the associated _Substance_ and, subsequently, to the associated _Product_. Vault adds the _Localized Substance Name_ as an alias. ### Bulk Import Product and Substance Aliases Using Vault Loader You can use Vault Loader to load _Product_ and _Substance Aliases_ in bulk from a _Company Product_ in the library. You must repeat the instructions below to upload two different CSV input files for _Product Aliases_ and _Substance Aliases_. To bulk import _Product_ and _Substance_ aliases: 1. [Prepare the CSV input file][2] 2. [Load aliases into Your Vault][3] #### Prepare the CSV Input File {#prepare-the-csv-input-files} You can prepare CSV input files for [_Product_][4] and [_Substance_][5] aliases. ##### Prepare the Import File for Product Aliases {#product-aliases} 1. Use Vault Loader to extract the _Product Aliases_ fields. Keep only the _Field Names_, which will serve as the column headers for the import file. 2. Use Vault Loader to extract the following _Product_ (`product__v`) fields: * _Product Name_ (`name__v`) * _Organization_ (`organization__v`) * _Generic Name_ (`generic_name__v`) 3. Copy the extracted fields into the import file under the respective column. The following table displays the field mapping between the extracted file and the import file columns:

FIELD LABEL	EXTRACTED FIELD NAME	IMPORT FIELD NAME
Product Name	`name__v`	`product__v`
Organization	`organization__v`	`organization__v`
Generic Name	`generic_name__v`	`alias__v`

4. Use Vault Loader to extract the following _Localized Product_ (`localized_product__v`) fields. * _Name_ (`name__v`) * _Product_ (`product__v`) * _Organization_ (`organization__v`) 5. Copy the extracted fields into the import file under the respective column. The following table displays the field mapping between the extracted file and the import file columns:
6. In the import file, perform the following steps: * Capitalize the fields under the _Alias_ (`alias__v`) column. * Go through the aliases and remove any duplicates. ##### Prepare the Import File for Substance Aliases 1. Use Vault Loader to extract the _Substance Aliases_ fields. Keep only the _Field Names_, which will serve as the column headers for the import file. 2. Use Vault Loader to extract the following _Substance_ (`substance__v`) fields: * _Substance Name_ (`name__v`) * _Organization_ (`organization__v`) 3. Copy the extracted fields into the import file under the respective column. The following table displays the field mapping between the extracted file and the import file columns:

FIELD LABEL	EXTRACTED FIELD NAME	IMPORT FIELD NAME
Name	`name__v`	`alias__v`
Product	`product__v`	`product__v`
Organization	`organization__v`	`organization__v`

FIELD LABEL	EXTRACTED FIELD NAME	IMPORT FIELD NAME
Substance Name	`name__v`	`substance__v`
Organization	`organization__v`	`organization__v`

4. Use Vault Loader to extract the following Localized _Substance_ (`localized_substance__v`) fields. * _Name_ (`name__v`) * _Substance_ (`substance__v`) * _Organization_ (`organization__v`) 5. Copy the extracted fields into the import file under the respective column. The following table displays the field mapping between the extracted file and the import file columns:

FIELD LABEL	EXTRACTED FIELD NAME	IMPORT FIELD NAME
Name	`name__v`	`alias__v`
Substance	`substance__v`	`substance__v`
Organization	`organization__v`	`organization__v`

6. In the import file, perform the following steps: * Capitalize the fields under the _Alias_ (`alias__v`) column. * Go through the aliases and remove any duplicates. #### Load Aliases into Your Vault Use Vault Loader to upload object records to your Vault. When loading records: * In the **Action Type** dropdown menu, select **Upsert**. * In the **Key Field** dropdown menu, select **Alias**.

Note: When uploading Products to your Vault, if the Generic Name for a Product exists on another Product, Vault creates a new Product with populated Product Name and Generic Name fields, but does not create a Product Alias.

## Create Inactive Ingredients Add an _Inactive Ingredient_ for each _Inactive Ingredient_ for which you will process _Cases_. ### Add Inactive Ingredients 1. Navigate to **Business Admin > Objects > Inactive Ingredients**. 2. On the _Inactive Ingredients_ page, select **Create** 3. Complete the following fields: * **Name**: Enter a name for the record. * **Organization**: Select the _Organization_ to which the ingredient belongs. * **Inactive Ingredient Name**: Enter a name for the ingredient. 4. Select **Save**. ### Add Inactive Ingredient Registrations Add _Inactive Ingredient Registrations_ for each country the _Inactive Ingredient_ is registered in. Vault links _Inactive Ingredient Registrations_ to _Product Registrations_ and _Inactive Ingredients_. 1. Navigate to the _Inactive Ingredient_ or _Product Registration_. * Find _Inactive Ingredient_ records on the **Business Admin > Objects > Inactive Ingredients** page. * Find _Product Registration_ records on the **Business Admin > Objects > Product** page, under _Product Registrations_. 2. Under _Inactive Ingredient Registrations_, select **Create**. 3. Complete the following fields: * **Name**: Enter a name for the record. * **Organization**: This is populated with the _Organization_ name from the parent record. * **Inactive Ingredient**: Select the **Inactive Ingredient**. If you access this page through the _Inactive Ingredient_ record, this field is prepopulated. * **Product Registration**: Select the associated **Product Registration**. If you access this page through the _Product Registration_ record, this field is prepopulated. 4. Select **Save**. ## Inactivate Products and Product Registrations {#inactive} You can set _Product_ and _Product Registration_ records to the _Deprecated_ state so that the Safety Rule Engine no longer considers them when determining the reportability of a _Case_. Depending on your configuration, when you deprecate a _Product_, Vault sets all of the related _Product Registration_ records to the _Deprecated_ state as well. For existing _Inbox Items_ and _Cases_ that include the _Product_, a _Deprecated_ tag appears next to the applicable product field. _Products_ and _Product Registrations_ in the _Deprecated_ state remain available for follow-up scenarios. To manage _Products_ and _Product Registrations_, navigate to **Business Admin > Objects > Products**. ### Deprecate Products To deprecate a _Product_: 1. Navigate to the applicable _Product_. 2. Select **State** and select **Deprecated** from the picklist. 3. In the _Change Object Status_ dialog, select **Yes**. To reactivate the record, update the **State** field to **Active**. ### Deprecate a Product Registration To deprecate a _Product Registration_: 1. Navigate to the associated _Product_ record. 2. Expand the **Registrations** section and select the **Product Registration**. 3. Select **State** and select **Deprecated** from the picklist. 4. In the _Change Object Status_ dialog, select **Yes**. To reactivate the record, update the **State** field to **Active**. [1]: #substance-records [2]: #prepare-the-csv-input-file [3]: #load-aliases-into-your-vault [4]: #product-aliases [5]: #substance-aliases [6]: #default-alias-field [7]: #deprecate-a-product [8]: #pr-inactive [9]: #add-substance-to-product [10]: #unknown-formulation-products [11]: #product-family-fields [12]: #add-a-product [13]: #product-fields [14]: #create-unknown-formulation-products [15]: #unknown-formulation-field [16]: #product-substance-fields [17]: #sync [18]: #inactive [19]: #product-alias