_{WARNING: Records cannot be recovered once they are deleted!}

 The bolded view is the default view, which will determine the view will automatically display in when opened. 

Identifies how Warehouse Lot Numbers are auto-generated for applicable transfer line items. This is not visible for new Sites and is only required and editable for Sites where the following conditions are both true:

• The 'Warehouse Lot Tracked' property is set to either: "Yes - Allow multiple items in single lots" or "Yes - Limit Warehouse Lots to single items"
• The '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 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. 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

Linked Database Field: ERPx_MFSite.WarehouseLotTemplate

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

Identifies whether or not the Warehouse Lot Numbers are auto-generated for applicable transfer line items. 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". This value is required if the Site is warehouse lot tracked and there is a value in the "Auto Generate Warehouse Lots By" property. 

If these conditions are true and the value is missing, the message "Unable to set "Auto Generate Warehouse Lots By" if "Auto Generate Warehouse Lots on Transfer Receipts" is not enabled on Save.

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. 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

Linked Database Field: ERPx_MFSite.AssignWarehouseLotsOnTransferReceipts

This lookup contains options for either "Yes" or "No". 

The 'City' that is setup on the Address Tab. This is part of the address for the Site. It is not required, is always editable from the Record View, and must be <= 35 characters.

Linked Database Field: ERPx_MFSite.City

The 'Country' that is setup on the Address Tab. This is part of the address for the Site. It is not required, is always editable from the Record View, and must be <= 50 characters.

Linked Database Field: ERPx_MFSite.Country

Identifies the "In Transit Site" that will be auto assigned to imported Transfer transactions where the current site is listed as the 'To Site' (the receiving Site). As a result, a one part transfer transaction will import as a two part transfer. This is typically assigned when:

• The source system that is exporting the data to NorthScope does not have functionality to support two-part transfers
• Companies want to ensure the correct In Transit Site is used when there may be more than one to choose from.

It is not required and always editable but is only visible, and applicable for non In-Transit Sites (Sites with the 'In Transit' property set to "No").

Two-part Transfers provide a way to deduct on-hand inventory from the 'From Site' (the sending site) before receiving it into the 'To Site' (the receiving Site). This is useful when transfers cannot be physically shipped and received at the same time, or when companies need to manage variances between what was actually shipped and actually received. This is accomplished by creating two separate, but linked, transfer transactions: 1) a one-part transfer that, when posted, moves on-hand balances from the 'From Site' (the sending site) to the 'Ship Via' (the in-transit site) and then creates a linked, un-posted transfer receipt transaction to move on-hand balances from the 'Ship Via' (the in-transit site) to the 'To Site' (the receiving Site). This allows the sending Site to deduct what they actually sent, the receiving Site to receive what they actually received, and any discrepancies to be reflected in the in transit Site.

Linked Database Field: ERPx_MFSite.IntegratedTransferDefaultViaSiteSK

The 'Email' that is setup on the Address Tab.  This is part of the address for the Site. It is not required, is always editable from the Record View, and must be <= 50 characters.

Linked Database Field: ERPx_MFSite.Email

The 'Fax' that is setup on the Address Tab. This is part of the address for the Site. It is not required, is always editable from the Record View, and must be <= 25 characters.

Linked Database Field: ERPx_MFSite.Fax

A Yes/No lookup to identify whether the Site is an "In Transit" Site or not. The value defaults to "No" but can be changed at anytime. 

A value of "Yes" means that the Site is an "In Transit". In Transit Sites are visible in the In Transit and Ship Via Site look ups and canot be set to 'Visible to Sales'. A value of "No" means that the Site is not and In Transit Site.

Linked Database Field: ERPx_MFSite.IsInTransit

A Yes/No field used to identify if the record is Inactive. If set to 'Yes' then the record is "Inactive" and will not be included in look-ups for transactions or other master files. If set to 'No' then the record is "Active" and can be freely used. 

Linked Database Field: ERPx_MFSite.IsInactive

Identifies the next Production Batch ID that will be used, by an integrated WMS or bar code data collection system, if they are configured to auto generate Production Batches. This defaults to 10000 for new Sites, is not required, is always editable, and must be an integer value. This is only used for imported transactions and does not impact manual data entry.  

Linked Database Field: ERPx_MFSite.NextProductionBatchNumber

The 'Phone' that is setup on the Address Tab. This is part of the address for the Site. It is not required, is always editable from the Record View, and must be <= 25 characters.

Linked Database Field: ERPx_MFSite.Phone1

Identifies a prefix that will be appended to the 'Next Production Batch #, by an integrated WMS or bar code data collection system, if they are configured to auto generate Production Batches. Because the 'Next Production Batch #' is an integer value, there is a possibility more than one Site could use the same number. Using a 'Production Batch Prefix' ensures Production Batch #'s remain unique across multiple production facilities. This does not impact manual data entry. This defaults as '[Site ID]-' for new Sites, is always editable, and must be <= 25 characters.  This is only used for imported transactions and does not impact manual data entry.  

Linked Database Field: ERPx_MFSite.ProductionBatchPrefix

Identifies the Plant's registration number. This is typically an FDA assigned number for US facilities. This defaults to blank for new records, is not required, and can be edited any time, and must be <= 50 characters. This is only used for reports. 

Linked Database Field: ERPx_MFSite.Registration

A hyperlink that shows the value of the 'Site ID' property on the Site record. Clicking on the link opens the record view for the selected Site. 

This defaults to blank for new records and is required. If not assigned, the message "Site ID is required." will be displayed on Save. This value must be unique. If not, the message "Duplicate Site IDs are not allowed." will be displayed on Save. This field is always editable from the record view and must be <= 20 characters. 

The Site ID is used as a short description and unique identifier of the Site.

Linked Database Field: ERPx_MFSite.SiteID

The 'Site Name' property on the Site record. This defaults to blank for new records and is required but duplicate values are allowed. If not assigned, the message "Site Name is required." will be displayed on Save. This field is always editable from the record view and must be <= 35 characters. 

The Site Name is used as a long description/name of the Site.

Linked Database Field: ERPx_MFSite.SiteName

The 'State' that is setup on the Address Tab. This is part of the address for the Site. It is not required, is always editable from the Record View, and must be <= 30 characters.

Linked Database Field: ERPx_MFSite.State

The 'Vendor name' of the AP Vendor that the Site is associated with. This defaults to blank for new records and is not required. Associating an AP Vendor with a Site is only for informational purposes.

Linked Database Field: ERPx_MFSite.VendorSK

This lookup contains a blank value, the current assigned value, and a list of all the 'Active' Vendor Accounts with an Account Type of Vendor.

A Yes/No lookup to identify whether or not the management of Sales Order shipment data is done within Load Management or from the individual Sales transaction. The value defaults to "No" but can be changed at anytime. 

If set to Yes: Shipment data for sales transactions that are set to ship from BOTH a Site and Carrier that are visible to logistics, is managed in Load Management and not on the individual Sales transaction. The data is visible on the Sales transaction but not editable.

A value of "No" means that all shipment data for sales transactions set to ship from this Site, is managed from the Sales transaction.

Linked Database Field: ERPx_MFSite.IsVisibleToLogistics

A Yes/No lookup to identify whether or not product can be sold from this Site. Some Sites may be used exclusively for production or storage. These Sites would not be visible to Sales. The value defaults to "No" but can be changed at anytime. 

A value of "Yes" means that the Site will be visible in look-ups for Sales transactions.

A value of "No" means that the Site will not be visible in look-ups for Sales transactions.

Linked Database Field: ERPx_MFSite.IsVisibleToSales

A Yes/No lookup to identify whether or not the Site is managed by a WMS or bar code data collection system. The value defaults to  "No" but can be changed at anytime. 

A value of "Yes" means that orders set to ship from these Sites will be visible to the bar code system.

A value of "No" means that orders set to ship from these Sites will not be visible to the bar code system.

Linked Database Field: ERPx_MFSite.IsVisibleToWMS

Identifies which option is selected in the 'Warehouse Lot Tracked' property on the Site record. The available options include:

• No: The Site does not track Warehouse Lots. To enforce this, the Warehouse Lot fields for inventory transactions for these sites are disabled.
• Yes - Allow multiple items in single lots: The Site requires Warehouse Lots on all Inventory tracked product and does not restrict them to individual item ID's. 
• Yes - Limit Warehouse Lots to single items: The Site requires Warehouse Lots on all Inventory tracked product but prevents Warehouse Lot Numbers from being applied to more than one Item ID without additional user intervention. Users can override this on a case by case basis by opening the Warehouse Lot master file and adding the new Item(s) to the Lot

This defaults to No for new records but can be edited at any time.  You should not change from either of the Yes options to No if there are open lot balances for the site.

Linked Database Field: ERPx_MFSite.IsSiteWarehouseLotTracked

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

The 'Zip' that is setup on the Address Tab. This is part of the address for the Site. It is not required, is always editable from the Record View, and must be <= 15 characters.

Linked Database Field: ERPx_MFSite.Zip