Customer Ship To Setup - eCommerce field descriptions

Field descriptions are presented in alphabetical order within each section. Click a link to advance to that section.

Document Send Types

Acknowledgement Send To

Indicate whether you want the ship to document sent to the ship to or the customer.

If you send a document by email, the Acknowledgement Send To value dictates which email addresses can be used. If you change the Acknowledgement Send To value, the Acknowledgements field is cleared, and you must reset it.

You must specify Document Send Type values for each ship to record, even if the settings are the same on the customer record. If you do not specify these settings, printed documents are sent to the ship to location.

Acknowledgments (EDI 855)

Select an output format for sales order acknowledgments. If you do not send acknowledgments electronically, leave this field blank.

Select Fax to fax the document and print a copy of the document for your files.

Select EDI to send the document in the output format that is selected in the EDI Format field for Acknowledgements in SA Administrator Options-Documents-Sales Orders-Printing.

Select ION to send the document in a SyncSalesOrder BOD.

Select Email to email the document. When you select this option, the Select Email Address page opens. Select one or more email addresses, and then click Save. The addresses that are listed are from Customer Setup, Customer Ship To Setup, and the Contacts context application.

When the Sales Entry Processing Acknowledgments Report is run, the selected output format is generated only if Yes is selected for the corresponding Print to Where Appropriate? option. For example, if EDI or ION is selected, Yes must be selected for Print to EDI Where Appropriate?. If you print an acknowledgment on demand in Sales Order Entry, you must select Use Where Appropriate.

Advanced Shipping Notice (EDI 856)

Select an output format for advanced shipping notices. If you do not send notices electronically, leave this field blank.

Select EDI to send the document in the output format that is selected in the EDI Format field for Advanced Shipping Notices in SA Administrator Options-Documents-Sales Orders-Printing.

Select ION to send the document in a SyncAdvanceShipNotice BOD.

Invoice Sent To

Indicate whether you want the ship to document sent to the ship to or the customer.

If you send a document by email, the Invoice Send To value dictates which email addresses can be used. If you change the Invoice Send To value, the Invoices field is cleared, and you must reset it.

You must specify Document Send Types values for each ship to record, even if the settings are the same on the customer record. If you do not specify these settings, printed documents are sent to the ship to location.

Invoices (EDI 810)

Select an output format for sales order invoices. If you do not send invoices electronically, leave this field blank.

Select Fax to fax the document and print a copy of the document for your files.

Select EDI to send the document in the output format that is selected in the EDI Format field for Invoices in SA Administrator Options-Documents-Sales Orders-Printing.

Select ION to send the document in a SyncInvoice BOD.

Select XML to send the document in an XML file.

Select Email to email the document to the customer. When you select this option, the Select Email Address page opens. Select one or more email addresses, and then click Save. The addresses that are listed are from Customer Setup, Customer Ship To Setup, and the Contacts context application.

If you are integrated to Billtrust, select Do Not Distribute to prevent invoices from being sent to the customer or ship to. A customer or ship to might opt not to receive invoices if most of their business is counter sales, or they make payments based on statements.

When the Sales Entry Invoice Processing Report is run, the selected output format is generated only if Yes is selected for the corresponding Print to Where Appropriate? option. For example, if EDI or ION is selected, Yes must be selected for Print to EDI Where Appropriate?. If you print an invoice on demand in Sales Order Entry, you must select Use Where Appropriate.

Proposal Send To

Indicate whether you want the ship to document sent to the ship to or the customer.

If you send a document by email, the Proposal Send To value dictates which email addresses can be used. If you change the Proposal Send To value, the Proposals field is cleared, and you must reset it.

Proposals

Select an output format for proposals. If you do not send proposals electronically, leave this field blank.

Select Fax to fax the document and print a copy of the document for your files.

You must select Yes for the Print to Email-Fax Where Appropriate? report option when you fax or email the proposal.

Advanced Shipping Notice

Group Code

If you specified Group in the Send To field, use this field to specify where to send the Advanced Shipping Notices.

The group code is a ship to location that is validated against Customer Ship To Setup records. You can set up a ship to record that exists only to receive documents. For example, if your customer has two ship to records but wants all EDI 856 transmissions sent to another location, you can set up the third location as a ship to.

Grouping

This setting determines if the ship to or group that is specified in the Send To field receives an Advanced Shipping Notice for each order or one Advanced Shipping Notice for all orders.

Send To

Indicate if you want to send Advanced Shipping Notices to the customer, ship to location, or a group.

This table shows the results of different values in the Send To and Grouping fields:


Send To	Grouping	Result
Ship To	Order	One EDI 856 Advance Ship Notice is sent per order to the ship tp location.
Ship To	Sent to Ship To	Orders are grouped into one EDI 856 Advance Ship Notice for each ship to and sent to the ship to location.
Group	Order	One EDI 856 Advance Ship Notice is sent per order to the ship to specified in the Group Code field.
Group	Sent to Ship To	Orders are grouped into one EDI 856 Advance Ship Notice for each group code location, based on the Group Code field, and are sent to the group location.

eCommerce Settings

Acknowledgement Version: Used for order acknowledgments, EDI Document 843 - Response to a Request for a Quote to Customer. Specify the number of the ANSI X12 version you use with this trading partner.
Change Reason Code: This field is user-defined and correlates to the ANSI X 12 Element 371 Change Reason Code. See your ANSI X12 Standards manual for more information on the correct entry.
eCommerce Warehouse: The warehouse used in XML transactions. If this field is blank, the default warehouse from the Customer Setup-Ordering or Customer Ship To Setup-Ordering is used. A valid warehouse must exist to proceed with the transaction.
EDI User 1-3: These are user-defined fields. They are implemented if custom EDI modifications require their use.
Invoice Version: This field is used for order invoices, ANSI X12 Document 810 - Invoices to Customer. Specify the number of the ANSI X12 version you are using with this trading partner.
Order Status Code: This field is user defined and correlates to the ANSI X 12 Element 368 Shipment/Order Status Code. See your ANSI X12 Standards manual for more information on the correct entry.
Partner Code: Specify the code for the EDI Trading Partner. This value must always be set up at the customer level but can also be set up at the ship to level if the ship to records have individual Trading Partner codes.

Inbound Purchase Order Settings

Catalog Product: Select this option to check Product Catalog Setup records to determine a match for product numbers. Because a catalog product is created as a non-stock product, the nonstock product option must also be selected. If Catalog Product is not selected, inbound product numbers are not validated received against Product Catalog Setup records.
Just In Time Orders: If this option is selected and the order is a JIT order or the Allow Req/Promise Dates Entry on Lines for Non JIT Orders option in SA Administrator Options-Documents-Sales Order-Entry Settings is selected, the system checks for a promise date and a ship date at the line item level. If there are no dates, the dates are updated from the header values and can be overridden. The requested ship date cannot be later than the promise date.
Non-Stock Product: Select this option to enable nonstock products to be created. You must set up the tie information manually. If this option is not selected, nonstock products are not created for products that cannot be validated. Because catalog products are created as nonstock, this option must be selected if Catalog Product is selected. A header note lists all line items that could not be created and an exception is generated.
Price Override: Select this option to use the price received in the transaction. This generates an exception so you can validate the price. If this option is not selected, the system checks Customer Ship To Setup, then Customer Setup, and then business rules for validation.
Print Notes/Comments: Select this option to set the print status for order notes and line item comments to yes.
Terms Override: Select this option to use the terms code received in the transmission. If this option is not selected, the system checks Customer Ship To Setup, then Customer Setup, and then business rules for validation. If this option is selected and no term code information is sent, the order uses the Customer Setup or Customer Ship To Setup term code, and an exception is generated.

eCommerce

Exclude From SXAPI List: This option controls the export of each Customer Ship To Setup record in each of the three related SX.API calls: sxapiARGetShipToList, sxapiARGetShipToListV2, sxapiARGetShipToListV3. The standard REST SX API and FetchWhere web services for SX.API temp-tables include this field. Select this option to exclude the ship to record. The option value, yes or no, is stored in an internal Customer Ship To Setup database field, excsxapilstfl. This option is not available if not activated correctly.