Select Ship-To Record View

Select Ship-To Record View

The purpose of this page is to populate some basic transaction header information and to select the correct Ship-To address. Selecting the Ship-To also assigns the Customer. When this page opens, it displays all the all the active ship to address. From here, users can click on the Find Items, Find Lots, or Go to Order icons.

 This record view also contains columns for each Attribute that is set up for the 'Customer Addresses' attribute type. Because these are user defined, they are not included in the default view but can be added a saved column layout. Customer Addresses attributes are not included in the help documentation.

Software Version: 2022.03.18 and newer

[ 1 Page Header  ] [ 2 Page Details ] [ 2.1 Ship To Tab ] [ 2.1.1 Related Topics ] [ 2.1.1.1 Page Definitions ] [ 2.1.1.2 Technical Details ]

Page Header 

Toolbar Icons

Description

Toolbar Icons

Description

Find Items

Find Items with Balance

Find Lots

Go to Order

Fields

Description

Carrier

This is a single-select standard lookup that is sometimes required. This field is required when the selected transaction class 'Is Carrier Required' property is set to "Yes". If required and no Carrier defaults are assigned, the message "Carrier is required and there is no transaction class or customer address default set." will be displayed on Save. This defaults as "(Use Default)" and is always editable.

If the Carrier is not manually assigned (left as "(Use Default)"), it will be auto-assigned from a default if possible, if not the Carrier will be blank. The defaults are assigned in the following sequence:

  1. From the 'Sales Order Carrier' assigned to the Customer Address

  2. From the 'Default Carrier' assigned to the Sales Order Transaction Class

  3. No default exists and the Carrier will be blank 

This lookup contains a list of all active Carriers.

Database Field: ERPx_SOCarrier.CarrierName

Deliver On

 This is a date picker that is sometimes required. It is required when the selected transaction class 'Require a Deliver On Date' property is set to "Yes". It defaults as blank and is editable if the 'Single Date Management' property on the Order Transaction Class Record View is set to "No". If required and not entered, the message "Deliver On Date is required for orders in the transaction class." will be displayed on Save. If entered it must be on or after the Order Date, else the message "Deliver On Date must be on or after Order Date." will be displayed on Save.

Database Field: ERPx_SOOrderHeader.ScheduledDeliveryDate

Freight Terms

Identifies the Freight Terms that will default for all shipments on the transaction. This is a single-select standard lookup that is sometimes required. It is required when the selected transaction class 'Require Freight Terms' property is set to "Yes". If required and no Freight Term defaults are assigned, the message "Freight Terms are required and there is no transaction class or customer address default set." will be displayed on Save. This defaults as "(Use Default)" and is always editable.

If the Freight Term is not manually assigned (left as "(Use Default)"), it will be auto-assigned from a default if possible, if not the Freight Terms will be blank. The defaults are assigned in the following sequence:

  1. From the 'Freight Terms' assigned to the Customer Address

  2. From the 'Default Freight Terms' assigned to the Sales Order Transaction Class

  3. No default exists and the Freight Terms will be blank 

This lookup contains a list of all active Freight Terms.

Database Fields: ERPx_SOFreightTerms.Description

Order Date

This is a date picker that is required. It is formatted in the user's 'Date Format' preference. It defaults as the current date and is always editable. If missing, the message "Order Date is required." will be displayed on Save. The Order Date must be on or before the Ship By Date and the Deliver On Date, else the messages "Ship by Date must not be earlier than Order Date." and "Deliver On Date must be on or after Order Date." will be displayed on Save.

Database Field: ERPx_SOOrderHeader.OrderDate

Purch. Order

This is a text box that is not required. It defaults as blank and is always editable. If entered, this field must be <=35 characters and validation will occur to determine whether the same Purchase Order number has been used for the same customer on any non-Void sales transaction (Order, Quote, Price Adjustment or Return). If so, the message "Warning: This Purchase Order has been used on at least one non-Void sales transaction for this Customer." will be displayed when the user clicks the Find Items, Find Lots or Go to Order buttons.

Database Field: ERPx_SOOrderHeader.PurchaseOrder

Ship By

This is a date picked that is sometimes required. It is required when the selected transaction class 'Require a Ship By Date' property is set to "Yes". It defaults as blank and is editable if the 'Single Date Management' property on the Order Transaction Class Record View is set to "No". If required and not entered, the message "Ship by Date is required for orders in the transaction class." will be displayed on Save. If entered it must be on or after the Order Date, else the message "Ship by Date must not be earlier than Order Date." will be displayed on Save.

Database Field: ERPx_SOOrderHeader.ScheduledShipDate

Ship From Site

This is a single-select standard lookup that is required. If missing and no defaults are set, the message "Ship From Site is required and there is no transaction class or customer address default set." will be displayed on Save. This defaults as "(Use Default)" and is always editable.

If the Ship From Site is not manually assigned (left as "(Use Default)"), it will be auto-assigned from a default if possible, if not the Ship From Site will be blank. The defaults are assigned in the following sequence:

  1. From the 'Sales Order Site' assigned to the Customer Address

  2. From the 'Default Ship From Site' assigned to the Sales Order Transaction Class

This lookup contains a list of all active Sites where the 'Visible to Sales' property is set to "Yes".

Database Fields: ERPx_MFSite.SiteName, ERPx_SOOrderHeader.SiteSK

Transaction 

This is a text box that is required. It defaults with "(Use Next Trans. #)" and is always editable. If missing, the system will auto assign based on how the Transaction Class is configuredTransaction IDs are set as follows for each Transaction Type:

  • Quotes: From the Order's Transaction Class or from the Quote's Transaction Class. 

  • Orders: From the Transaction Class

  • Price AdjustmentsFrom the Source Order, Price Adjustment Transaction Class or the Source Invoice

  • ReturnsFrom the Return Transaction Class or the Source Invoice

When generating a Transaction ID from a Transaction Class it is made up as the 'Document Prefix' + 'Next Document Number'. If the transaction number is manually entered,  it must be unique. Else the message "The Transaction ID you are trying to add has already been used. Please check your transaction class setup to make sure the next document number available has not already been used." will be displayed on Save.

Database Field: ERPx_SOOrderHeader.OrderID

Transaction Class

This is a single-select standard lookup that is required. If missing, the message "Transaction Class is required." will be displayed on Save. It defaults from the value selected when the New button was clicked from the Sales Transactions List View or the Sales Items List View. It is always editable.

This lookup contains a list of all active Transaction Classes where the 'Transaction Type' property is set to "Order" or "Quote".

Database Field: ERPx_SOOrderType.DocumentID