Formulations in NuGenesis LMS won't transfer to the Stability module if the product and specification have already been transferred - WKB47167

SYMPTOMS

• A Product and Specification have been defined in NuGenesis LMS, approved, and successfully transferred to the NuGenesis Stability module
• A formulation is added to the Product
• The formulation has the same name as the Specification
• The formulation is not transferred to the Stability module

ENVIRONMENT

• NuGenesis 8 LMS

CAUSE

A defect within the NuGenesis Stability module

FIX or WORKAROUND

1. If possible, delete the formulation and rebuild it with a name distinct from the Specification name.
2. If the formulation must not be renamed, enable the "Formulation_Name_Unique" option within the Stability module:
   1. Log in to the NuGenesis Stability module with the Slim user account.
   2. Start the Stability client by running it directly from the installation folder:
      • Drive:\Program Files (x86)\Waters\NuGenesisLMS\slim.exe
   3. In the Stability client, click the Tools menu > Execute SQL.
   4. Type the following text into the input box and click OK:
      • {call proc_config('Formulation_Name_Unique','1')}
   5. Edit the formulation in LMS in order to trigger the transfer to the Stability module.
3. Add the formulations to the product definition in NuGenesis LMS prior to approving the specification.

ADDITIONAL INFORMATION

This issue has been registered by H&A Scientific Inc. as a defect within the SLIM software. The defect has the designation KBN 790.

The root cause is that the Stability module incorrectly checks for pre-existing objects when it processes the formulation transfer from LMS.  For most types of data within Stability (products, specifications, clients, etc.), the system checks for objects of the same type that have the same name as the new object; for formulations, the system does not restrict this check to pre-existing formulations. Thus, a specification with the same name as the new formulation would be seen as a duplicate, and the new formulation would not be added to the Stability database.

The "Formulation_Name_Unique" option alters system behavior. When it is active, the check for pre-existing objects is restricted to just formulations, and it also requires that formulations be uniquely named through the entire database.  When this option is inactive, formulation names can be reused in different products, but this is not allowed when the system option is active.

It can be deactivated by running this command in the Stability client:

• {call proc_config('Formulation_Name_Unique','0')}