Identifies how Warehouse Lot Numbers are auto generated for this Site when it is assigned as the 'To Site' (the receiving Site) on an inventory Transfer. This is only required and editable for Sites where the following conditions are both true:

• The Site's 'Warehouse Lot Tracked' property is set to either: "Yes - Allow multiple items in single lots" or "Yes - Limit Warehouse Lots to single items"
• The Site's 'Auto Generate Warehouse Lots on Transfer Receipts' property is set to Yes

If these conditions are true and the value is missing, the message "[SiteID] has the "Auto Generate Warehouse Lots on Transfer Receipts" option turned on but is missing a selection for "Auto Generate Warehouse Lots by"" will be displayed on Save.

When this feature is enabled for a Site assigned as the 'To Site' (the receiving Site) on an inventory Transfer, the system will automatically populate the Warehouse Lot values in the 'To Warehouse Lot' filed, on Save. The values will be populated as either:

• INTR:[SiteID]:[Reference Number] - for example INTR:BCS:12345
• [Item ID]-[Production Batch Date MM][Production Batch Date YY] - for example 10015-0519
• [Production Batch Date MM][Production Batch Date YY]-[Item ID] - for example 0519-10015

This lookup contains all the values in the WarehouseLotTemplateEN Enumeration Class.

 This should only be used for Sites that allow you to specify the Warehouse Lot numbers you want them to use. If the Warehouse Lot numbers are assigned by the Site, this should not be used.

Database Field: ERPx_MFSite.WarehouseLotTemplate

A Yes/No value to identify whether or not Warehouse Lot Numbers are auto assigned for this Site when it is assigned as the 'To Site' (the receiving Site) on an inventory Transfer. This is only visible for Sites where the 'Warehouse Lot Tracked' property is set to either: "Yes - Allow multiple items in single lots" or "Yes - Limit Warehouse Lots to single items".

When this feature is enabled for the 'To Site' (the receiving Site) on an inventory Transfer transaction, the system will automatically populate the warehouse lot values in the 'To Warehouse Lot', on Save based on the settings in the 'Auto Generate Warehouse Lots by' property. 

 This should only be used for Sites that allow you to specify the Warehouse Lot numbers you want them to use. If the Warehouse Lot numbers are assigned by the Site, this should not be used.

Database Field: ERPx_MFSite.AssignWarehouseLotsOnTransferReceipts

Used to assign the default 'In Transit' Site that will be used for Transfers that are imported/integrated from a 3rd party system. This default to blank, is not required, and is always editable. This property is only visible and editable if the following conditions are both true:

1. The Site is NOT an In Transit Site (it's 'In transit' property is set to "No")
2. The Site is visible to WMS (it's 'Visible to WMS' property is set to "Yes")

If there is a Site specified, imported Transfers sent from this Site will create 2-part transfers using the assigned 'In Transit' Site. If there is not a Site specified, imported Transfers sent FROM this Site will create 1-part transfers. 

Database Field: ERPx_MFSite.IntegratedTransferDefaultViaSiteSK

Identifies whether or not the Site is inactive. This is a single-select standard lookup that is required and is always editable. It defaults to "No" and is always editable.

Database Field: ERPx_MFSite.IsInactive

Specifies the next Production Batch number that will be auto assigned in the system. This is a text box that is required, defaults to "1000", and is always editable. It must be a positive whole number, else the message "Next Production Batch Number cannot be negative", "Next Production Batch Number cannot contain commas or decimals.", or "Next Production Batch Number must be a Number." will be displayed on Save. This field will auto increment by 1 for every new Production Batch that is auto created.

The 'Production Batch Prefix' is used in conjunction with the 'Next Production Batch #' to determine the auto assigned Production Batch ID. Production Batch IDs are created by stringing together the [Production Batch Prefix] + [Next Production Batch #].

Database Field: ERPx_MFSite.NextProductionBatchNumber

Used to set a prefix for Production Batches that are auto assigned in the system. If a prefix exists, it will be used prior to the site's 'Next Production Batch #' to auto create the Production Batch ID. This is a text box that defaults to '[Site ID] -', it must be <= 25 characters, it is not required, does not need to be unique, and is always editable.

The 'Production Batch Prefix' is used in conjunction with the 'Next Production Batch #' to determine the auto assigned Production Batch ID. Production Batch IDs are created by stringing together the [Production Batch Prefix] + [Next Production Batch #].

Database Field: ERPx_MFSite.ProductionBatchPrefix

Used to enter the Registration # for the Site (typically an FDA Registration #). This is a text box that defaults as blank, is not required, must be <= 50 characters, and is always editable.

Database Field: ERPx_MFSite.Registration

A lookup to identify the Vendor that is linked to the Site displayed as [Vendor Name] ([Vendor ID]). This is informational only and is typically only assigned to 3rd party sites (cold storages, re-packers, etc.). This defaults as blank, is not required, and is always editable.

The lookup contains a blank value, the current assigned value and the list of all 'Active' Vendors with a VendorTypeEN = 1 and is sorted alphabetically.

Database Field: ERPx_MFSite.VendorSK

A Yes/No lookup to identify whether or not the site is visible in the "Load Management" functional Area. This defaults to "No", is required, and is always editable.

• If "Yes', transactions shipping from the Site (that are also being shipped by a Carrier that is "Visible to Logistics") will be visible to the "Build Loads" process in Load Management.
• If "No', transactions shipping from the Site the Site will be visible/accessible in Load Management

 The list of Sites also exists in the Load Management functional area, allowing users to determine whether or not a Site is available to them for placement on Loads. Because of this, the Site record view Visible to Logistics field corresponds with the Logistics Sites list view Visible to Logistics checkbox. Therefore, if the Site's visibility to logistics is edited from either location, the site will be updated in both locations.

Database Field: ERPx_MFSite.IsVisibleToLogistics

A Yes/No lookup to identify whether or not the site is visible for use on Sales Orders, Price Adjustment, and Return transactions. This defaults to "No", is required, and is always editable.

• If "Yes', the Site will be included in the Site lookups on Sales Orders, Price Adjustment, and Return transactions.
• If "No', the Site will not be included in the Site lookups on Sales Orders, Price Adjustment, and Return transactions.

Database Field: ERPx_MFSite.IsVisibleToSales

A Yes/No lookup to identify whether or not transactions shipping for the site are visible to a 3rd party Warehouse Management system. This defaults to "No", is required, and is always editable.

• If "Yes', transactions shipping from the Site (for each Item that is also visible to WMS) will be visible/accessible to the Warehouse Management system.
• If "No', transactions shipping from the Site will not be visible/accessible to the Warehouse Management system.

 This setting is only applicable for NorthScope installations that are integrated with a Warehouse Management system. 

Database Field: ERPx_MFSite.IsVisibleToWMS

Displays the read-only name of the valid certifications to assign to the Site. Eligible certifications to assign to the site are those marked as Site Only or Item & Site in the Lot Certifications list view. To assign a certification to a site, simply check the certifications select box and save. All assigned certifications will filter to the top of the certifications list.