Skip to main content

Validate

A
Written by Alex Salb
Updated over a year ago

The Validate tab on the output page gives detailed information on whether any problems have been detected with a user’s input data.

The page consists of three fields:

  • The scenario field showing the name of the scenario that has been validated.

  • The “last updated” field showing when the scenario validation was run.

  • The download field allowing the user to export the validation details into an Excel workbook.

Clicking the icon to the left a scenario reveals the details of the validation results for that scenario. Here are the fields that it depicts:

  • The scenario field giving the name of the scenario.

  • The table name giving the name of the table where the error has been found.

  • The keys field explaining the error.

  • The field giving a summary description of the error.

  • The message type field indicating the number the error corresponds to.

  • The severity field giving a measure of the severity of the error.

  • The message field giving the actual SQL statement causing the error.

  • The data field for any additional information.

To download a validation report into an Excel spreadsheet, simply click the download icon to the right of the scenario and the file will automatically download into the downloads folder.

The last feature of the validation tab is the expand all toggle which allows the user to expand all given scenarios to see the details for each one at once.

Here are the following error codes (numbers) that you might run into with their corresponding meaning:

  1. Referential Integrity

    1. Checks if keys in all main tables exist in key tables.

    2. i.e. all products and sites in SIteProducts table have corresponding records in Sites table and Products table

  2. Duplicate Key(s)

    1. Checks for records with the same keys i.e. the same product exists twice in the products table

  3. CustomerDemand has no lanes

    1. Checks all customers with demand have associated customer lane in CustomerLanes table

  4. Invalid constraint variable. Must be FLOW or COUNT or PROPORTION

    1. Checks UserConstraints.Variable field does no have a typo or invalid entry.

  5. Invalid SolverInclude value. Must be YES or NO

    1. Checks SolverInclude field does no have a typo or invalid entry in all tables

  6. Product is not produced with a BOM

    1. Checks for products in model that do not have an associated Output and BOM record in BOMs table.

  7. User constraints with missing constraint components

    1. Checks for constraints in UserConstraints that have no associated records in UserConstraintComponents.

  8. Proportion constraints not equal to 1

    1. Checks for if constraint is marked as Proportion, does the Weight of its Components add up to 1

Did this answer your question?