• Recipe Validation
  • Use the File/Validate command to initiate a validation of the current recipe.
  • The validation process consists of the following elements.
    • Verify that the process model database information used in the recipe exists.
  • This includes process classes, phases, parameters, and tags.
    • Verify that the material database information used in the recipe exists.
    • Verify that the minimum, maximum, and default batch sizes defined in the recipe header are appropriate. (Minimum <= Default <= Maximum).
    • Verify that all of the formula parameters defined in the recipe procedure are linked to the appropriate information.
    • Verify that all transition logic, including loop logic, is valid.

Note: The validation process only verifies user configured information. Because of the flexibility provided in constructing recipe procedures, it is impossible to verify a recipe design. This verification is the responsibility of the user.

• • The validation does not check the document path specified for a document that is to be viewed as part of a phase's execution.
  • The validation process does not verify the existence of reports on the Information Server. This verification is the responsibility of the user.

• Recipe Approvals
• Use the File/Approvals command to approve any recipe in the database for production or for testing.
• Approvals are required before the Approved for Production check box can be set. A recipe cannot be scheduled as part of a batch unless the Approved for Production or Approved for Test check box has been enabled.
• The levels of approval required are configured in the Security Editor. If security is not enabled, the Approved for Production or Approved for Test check box must be manually enabled each time the recipe is saved.
• There are five levels of recipe approval permitted. The first level corresponds to the author.
• The remaining levels of approval are numbered two through five and can be assigned based on your requirements.

Note: In order to prevent the same person from approving recipes at different levels, each level of approval should be assigned a different security level.

• You approve the recipe by selecting the appropriate level command button on the Approvals and entering information required by the security request windows.
• Levels may be approved in any order, but the Approved for Production or Approved for Test check box cannot be enabled until all of the required levels have been satisfied.
• The Approved for Production or Approved for Test check box can be enabled or disabled at any time for recipes in which all levels of approval have been satisfied.