The Ship-To address is the physical address where customer shipments are sent. The purpose of this page is to select a customer address and enter/select default fields for a sales order and sales quote transactions. From this record view, users may choose to navigate to the Select Items Record View, allocate from inventory lots using the Find Lots Record View, or go directly to the Sales Order Record View.
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 grid layout. Customer Addresses attributes are not included in the help documentation.
Software Version: 2021.xx.xx and newer
Page Header
| Toolbar Icons | Description |
|---|---|
| Go To Catalog | |
| Go To Find Lots | |
| Go To Order |  Opens the Sales Transaction Record View for the current transaction. |
| Help |  Opens the online WIKI help page for the current page. |
| Fields | Description |
| Carrier | Identifies the default Carrier associated with the transaction. This is a single-select standard lookup that is sometimes required. This field is required when the sales preference 'Do Sales Order Require a Carrier' is set to "Yes". If required and missing, the message "Sales Order Preferences require a Default Carrier" will be displayed on Save. It defaults as blank and is always editable. Carriers represent entities that transport goods from one location to another. They can be actual freight companies (i.e. UPS or Fed Ex) and/or they can represent a delivery method (i.e. Our Truck, Customer Pickup, Transfer in Storage, or UPS-Air). They are used on Inventory transfers and sales order shipments. This lookup contains a list of all active Carriers. Database Field: ERPx_SOCarrier.CarrierName |
Deliver On | Error rendering macro 'excerpt-include' : No link could be created for 'Deliver On Date - Default'. 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 always editable. 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 to be defaulted for all shipments on the transaction. This is a single-select standard lookup that is sometimes required. It is required when the 'Require Freight Terms' preference for the associated transaction class is set to "Yes". It defaults from the 'Freight Terms' property on the 'Properties' tab of the Customer Addresses Record View. This field is always editable. If missing, the message "Freight Terms are required for orders in the Transaction Class of [Transaction Class]" will be displayed on Save. Freight Terms are used to describe the contract terms between the shipper and receiver or product. They can be assigned to Inventory Transfer and Sales Order Shipments. These can print on transaction documents but do not drive an other functionality. This lookup contains a list of all active Freight Terms. Database Fields: ERPx_SOFreightTerms.Description |
Order Date | Identifies the date of the transaction. This is a date picked that is required. 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 | Identifies the Purchase Order number (PO number) entered for the transaction or transaction line item. 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. A Purchase Order (aka PO) is a document issued by a buyer committing to pay the seller for specific products or services to be delivered in the future. The advantage to the buyer is the ability to place an order without immediate payment. From the seller’s perspective, it reduces credit risk, since the buyer is obligated to pay once the products or services have been delivered. Each PO has a unique number associated with it that helps both buyer and seller track delivery and payment. Database Field: ERPx_SOOrderHeader.PurchaseOrder |
| Ship By | Displays the default date the order (or Shipment) is, or was, expected to be shipped, formatted from the users 'Date Format' preference. 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 always editable. 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 | Error rendering macro 'excerpt-include' : No link could be created for 'Site'. This is a single-select standard lookup that is required. Need the error message here! It defaults as blank and is always editable.Sites represent Plants, Warehouses, Distribution Centers, or virtual objects that are used to store and/or maintain perpetual inventory balances. 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 | Identifies the unique Transaction ID for each 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 a Transaction Number using the 'Document Prefix' and 'Next Document Number' properties. If the transaction number is manually entered, then it must be unique. Else the message "Transaction Number may not be duplicated." will be displayed on Save. Sales transaction numbers may be system assigned IDs to differentiate unique transactions. Transaction ID's are unique by the unique combination of 'Document Prefix' + 'Next Document Number'. Database Field: ERPx_SOOrderHeader.OrderID |
| Transaction Class | The unique identifier of the 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 to the selected transaction when the New button was clicked from the Sales Transactions LV or the Sales Items LV. It is always editable. Transaction Classes are used to differentiate transactions within a Transaction Type. For example, Transaction Classes of Fresh and Frozen can be setup for the Transaction Type of 'Sales Order'. Transaction Classes are used in all functional areas throughout the application. This lookup contains a list of all active Transaction Classeswhere the 'Transaction Type' property is set to "Order" or "Quote". Database Field: ERPx_SOOrderType.DocumentID |
Page Details
Ship To Tab
| Toolbar Icons | Description |
|---|---|
| Column Filter Show/Hide |  Toggles between displaying and hiding a filter row in the grid under the column headers. The filter row will be displayed by default if the Quick Column Filter is also implemented in the page. When enabled, this will allow users to type in text to filter by a specific column. |
| Excel |  Exports the contents of the grid to an Excel file that will automatically download. The contents that export are those that are visible to the user. Therefore, if the user has filtered the view, or excluded columns, only the contents in the grid will be exported. |
| Group By Show/Hide |  Toggles between displaying and hiding a row in the grid above the column headers to enable grouping by one or more column(s). Once displayed, users may drag and drop column headers to group by a specific column. Once the grid is grouped by a column(s), a subtotal footer row will display in the grouping for columns that have a page footer total. |
| Help | Opens the online WIKI help page for the current page. |
| Quick Filter | Error rendering macro 'excerpt-include' : No link could be created for 'Quick Filter'. |
| Saved Column Layouts |  Displays the column layout lookup and related icons. This tool allows users to select a previously saved layout, create a new layout, save changes to a layout, forget/delete a layout and/or assign a saved layout as the default for the page. Once changes are made to the layout, such as columns are added or removed, the user can click the Save Layout icon and save the changes to the column layout. The visibility of the Filter Row is also saved with a saved layout. The new layout can also be set as the default. This is useful for creating specific views to separate master files or transaction types (i.e. Invoice specific vs. Credit Memo specific). Default layouts can be removed by clicking the 'Set as Default' button again when the current default layout is selected. Please note that existing saved grid layouts will display the Filter Row as hidden by default. |
| Fields | Description |
| Address | Displays the first line in the Address where the order will be shipped to. This is a non-editable text box that is not required. It defaults from the 'Address 1' field on the 'Properties' tab of the Customer Addresses Record View. This field is editable from the Customer Addresses Record View and the Customer Record View. Address Line 1 typically contains the primary address information such as the street address. Database Field: ERPx_ARCustomerAddress.AddressLine1 |
| Address ID | Identifies the ID of the Address for the associated Account. This is a non-editable text box that is required. It defaults from the 'Address ID' field on the 'Properties' tab of the Customer Addresses Record View. This field is editable from the Customer Addresses Record View and the Customer Record View. Customer Address IDs are used as a short description and unique identifier for Customer Address records. They can be changed at any time to any alphanumeric value. For Customers with only one Address, the default value of PRIMARY can be used. Address IDs of BILLING and SHIPPING are often used for Customers with separate addresses for each. For customers with many Ship-to addresses a City or Street name can be used. Note: Address Types of "Both" and Shipping" will be included on this page; Address Types of "Inactive" and "Billing" will not be included on this page. Database Field: ERPx_ARCustomerAddress.AddressID |
| Address Name | Identifies the ID of the Address for the associated Account. This is is a non-editable text box that is required. It defaults from the 'Address Name' field on the 'Properties' tab of the Customer Addresses Record View. This field is editable from the Customer Addresses Record View and the Customer Record View. Database Field: ERPx_ARCustomerAddress.AddressName |
| Attention To | Identifies the value from the 'Attention To' field. This field is only available for systems that get the Customer Address from a host system. This is a non-editable text box that is not required. It defaults from the 'Ship Attention To' field on the Edit Ship To Address dialog box. This field is always editable Ship To address hyperlink on the Sales Order Record View. Will there be another place to access this field? Else this field will also be blank since the Sales Order RV is only displayed after this page. Database Field: ERPx_ARCustomerAddress.AttentionTo |
| City | Displays the destination City where the order will be shipped to. This is a non-editable text box that is not required. It defaults from the 'City' field on the 'Properties' tab of the Customer Addresses Record View. This field is editable from the Customer Addresses Record View and the Customer Record View. The City identifies the value of 'City' in an address record. Database Field: ERPx_ARCustomerAddress.City |
| Customer | Error rendering macro 'excerpt-include' : No link could be created for 'Customer ID - Transaction'. This is a non-editable text box that is required. It defaults from the 'Customer ID' field on the 'Properties' tab of the Customer Addresses Record View. This field is editable from the Customer Addresses Record View and the Customer Record View.Customer IDs are used as a short description and the unique identifier for Customers. They can be changed at any time to any alphanumeric value. If you do not have an existing strategy for Customer IDs the 3-3-2 method would be recommended. Database Fields: ERPx_ARCustomer.CustomerID, ERPx_ARCustomerAddress.CustomerSK |
| Customer Name | Error rendering macro 'excerpt-include' : No link could be created for 'Customer Name - Transaction'. This is a non-editable text box that is required. It defaults from the 'Customer Name' field on the 'Properties' tab of the Customer Addresses Record View. This field is editable from the Customer Addresses Record View and the Customer Record View.Customer Names are used as a long description for Customer records. Database Fields: ERPx_ARCustomer.CustomerName, ERPx_ARCustomerAddress.CustomerSK |
| State | Displays the destination State where the order will be shipped to. This is a non-editable text box that is not required. It defaults from the 'State' field on the 'Properties' tab of the Customer Addresses Record View. This field is editable from the Customer Addresses Record View and the Customer Record View. The State identifies the value of 'State' in an address record. Database Field: ERPx_ARCustomerAddress.State |
| Zip | Displays the destination Zip Code where the order will be shipped to. This is a non-editable text box that is not required. It defaults from the 'Zip' field on the 'Properties' tab of the Customer Addresses Record View. This field is editable from the Customer Addresses Record View and the Customer Record View. The Zip identifies the value of 'Zip' (Zip Code) in an address record. Database Field: ERPx_ARCustomerAddress.Zip |