Pre-ship validation configuration

  1. At the Enterprise level, select Configuration > Validation Rules > Outbound to open the Conditional Validation screen.
  2. To create a new record, click New to access the Conditional Validation detail view.
    Note: An application-generated Validation Key number is automatically created. However, you can change this number to a unique non-sequential value. For example, add a letter or name. If the number is changed to a sequential number that has not yet been used by the application, it can later cause duplication errors, resulting in application termination.
  3. To edit a current record, use the Search and Lookup features to access a specific Conditional Validation type.
    Note: The only edits allowed to the default pre-ship validation routine are to enable or disable the validations.
  4. When adding a new record, enter the appropriate information in the following fields for each validation type.
    Validation Key
    Validation identifier, which you can override if necessary. Select from Ship Group Validation and Shelf Life Comparison. Write-protected.
    Note: You can edit the initial definition, up until the record is saved.
    Enabled
    Indicator that determines whether the Validation Routine header is checked by the application. If set to No, this record is not validated by the application.
    • If the check box is selected, the routine header is enabled.
    • If the routine is not enabled, any detail sequences associated with the header are not checked by the application, regardless of their enabled status.
    • The default value for post-allocation and post-shipment validation is disabled. The default value for Post-pick validation is enabled.
    Owner
    Owner of the item to be validated. Required.
    Note: Owner must be configured in the application.
    Customer
    Party to whom the item is delivered. Required.
    Note: 
    • Only entry of a valid customer is allowed.
    • Customer must be configured on the Owner screen.
    Item
    Item to be validated. Required.
    Note: The Customer, Owner, and Item fields are not required fields for the default record. However, these fields are required when adding a new record.
    Type
    Validation type for the record. Click the drop-down list and select Pre-ship Validation. Required.

    Default value: Post-pick validation

    Minimum Shelf Life
    Minimum number of days that the customer allows between the current date and either the expiration date or the manufacturing date for the item being shipped. This number is compared with the calculated number to determine if the validation passes or fails.
    Note: 
    • Accepts entries only when the validation header Type is Post-pick or Pre-shipment Validation.
    • Cannot be edited when the Validation Header Type is Post-allocation.
    Default
    Response that determines who created the record. Displays Y for default records created by the application and N for any records you created. It is pre-populated. Write-protected.
    Detail List View
    Sequence
    Sequence of the validation routines that the application should follow. Write-protected.
    Validation Routine
    Validation routine that the application should follow. Select one of the following:
    • Shelf Life Comparison
    • Check Lot
    • Check Location
    • Check Item
    • Check ID
    • Check New LOT, LOC, ID

      See the Validation Routine table for these definitions.

    When you use the Check Lot routine, be sure to modify the prompts.ini file to require that the lot be entered on RF.
    Note: 
    • Selections in the drop-down list depend on the Validation type defined at the header.
    • You cannot enter routine names from other validation types. Only those routines associated with the Validation Type in the header are allowed.

    Default value: Check Location

    Enabled
    Indicator that determines whether the Validation Routine is checked by the application. Only enabled routines are considered by the application when processing validations.
    Note: Define each sequence as being enabled or not, regardless of the Enabled option setting at the header.
    An explanation of the validation routines follow.
    Validation Routine Definition
    Ship Group Validation When this function is enabled, the application ensures that all items for matching Ship Groups have been allocated. If the application finds that items with a matching Ship Group were not allocated, it generates an error message and does not allow the order to ship. The error message displays when shipping is attempted from the Shipment Order, Wave, or through Mass Ship of either orders or pick details. If this function is disabled, this check is not performed.

    Ship Groups are defined at the Shipment Order Detail Level. There are three Ship Groups: 01, 02, and 03.

    The Ship Together option at the Shipment Order header takes precedence over the Ship Group Validation. If the Ship Together option is set at the Shipment Order header, all lines must be allocated for the order to ship. The default value for the Ship Together option is No.

    Valid entries for this field are Y=Yes or N=No

    Shelf Life Comparison When enabled, the application works through the following process to validate Shelf Life Comparison:
    • Identifies the Shelf Life Code Type for the item on the Item screen (Manufacturing or Expiration Date).
    • Compares either the Manufacturing or Expiration date to the current date to calculate the shelf life.
    • If the Shelf Life Code is the Expiration Date:
      • The calculated shelf life is compared to the Minimum Shelf Life defined on the Conditional Validation screen (if this is an override record).
      • If the override record’s Minimum Shelf Life is set to 0 (zero), the application uses the value on the item record.
      • If this is the default record, the application always uses the Outbound Shelf Life on the Item screen.
      • When the calculated shelf life is less than the Minimum Shelf Life, the validation fails. When the calculated shelf life is greater than the Minimum Shelf Life, the validation passes.
    • If the Shelf Life Code is the Manufacturing Date:
      • The calculated shelf life is compared to the Minimum Shelf Life defined on the Conditional Validation screen if this is an override record.
      • If the override record’s Minimum Shelf Life is set to 0 (zero), the application uses the value on the item record.
      • If this is the default record, the application always uses the Outbound Shelf Life on the Item screen.
      • When the calculated shelf life is less than the Minimum Shelf Life, the validation passes. When the calculated shelf life is greater than the Minimum Shelf Life, the validation fails.
  5. Click Save.