This menu option is available from Base, Web, POS, and EPayments stores.
Sales settings provide a basic framework for how your system will work based on integration rules and business needs as they relate to JD Edwards Sales Order Management. The two tabs available are Basic and Advanced. Please remember to click Save to preserve any changes you make to Sales Settings.
For POS stores the address number is used for cash and carry sales orders for which no consumer/customer number is entered.
For Web stores, the address number is used to get pricing for an anonymous web user. Additionally, this address number is used in orders placed following the “Continue without registering” check-out process.
In any case if a customer is not selected for the order the tax area and reason for the default Customer defined here will be used.
|Cash and carry orders P4210 version||
Designates the version of the Sales Order application (P4210) that will be used in the Solution for cash and carry orders/order lines. Please note that certain P4210 Processing Options such as Document Type must match for all P4210 versions used for POS.
|Shippable orders P4210 version||Designates the version of the Sales Order application (P4210) that will be used in the Solution for order/lines to be shipped. Please note that certain P4210 Processing Options such as Document Type must match for all P4210 versions used for POS.
|Discount Line Type||The line type that is assigned to the sales order line generated when an order level discount is entered for an order. Order level discounts include percentage or fixed amount discounts entered during order entry.|
|Discount Product Number||The product number to be used when manual discount is added via POS. If this setting is left blank or is 0 then no product will be written.
|Supply and Demand P4021 Version||
When a product is on backorder the system will calculate the Backorder Availability Date and display it on the Product Content and More Info page for Web Stores. For POS the Backorder Availability Date will display on the Product Detail page. If this setting is left blank then the BO Availability date will not be calculated.
This calculation will always be performed using quantity 1 and will be recalculated anytime the UOM is changed.
|Marketing Code Behavior||
Designates the marketing code functionality desired during order entry. Possible values are:
Hide - don't display marketing code field
Display Not Required - marketing code field as optional
Display Required - marketing code field is required
|Marketing Code Default Value||The default marketing code automatically applied to the order. If left blank, no default value will be displayed. If you specify a default marketing code you can override it in the order as needed.
|Sales Order Document Restrictions||Sales order types to display in Order Status / Shopping History.|
|Sales Order Display cancelled lines||When displaying details of a sales order canceled sales order lines can be displayed or hidden from web user.|
|Status Limit for Open Orders||Used in order search to represent the JD Edwards last status (LTTR) for open orders. Orders with line items less than or equal to this status will be displayed in order search when open order search selection is executed by web user.|
|Apply Advanced Basket Repricing||
Indicates whether the Sales Order Re-pricing functionality is Active or Disabled. Possible values are “Yes” and “No”. Applies only to EnterpriseOne releases 8.10 and above.
Please note that if both the Management Console and P4210 are setup to apply advanced basket repricing the results could be unfavorable. Therefore, if basket repricing is desired set this option to Yes and leave the P4210 basket repricing off. However, you must still set the R42750 version in the P4210 processing options so that Ecommerce knows which version to run for the repricing.
|Display Base Price and Savings||Base price and savings are calculated using JD Edwards functions and returned to the product content and cart Ecommerce for display.|
|Synchronize Pricing UOM with Transaction UOM||
Standard JDE uses the pricing UOM to display the unit price and the transaction UOM to display the extended price. This setting allows you to decide if you want to synchronize the pricing UOM with the transaction UOM. For example on the item master you might have an item setup with EA as the transaction UOM, but CA as the pricing UOM. When this option is turned on the pricing UOM for the order will be updated and synchronized with the transaction UOM selected. If the UOM is not synchronized Product Content will display the price with the pricing UOM displayed next to it. If the user changes the UOM then the price will be recalculated. In addition, checkout, place quote, and modify order processes (and the associated email confirmations) will also display the pricing UOM next to the price.
Yes - Synchronize the pricing and transaction UOM
No - Do not synchronize the pricing and transaction UOM
|Price Break Behavior||Determines if price break information will be displayed in Product Content and in More Info (first five quantity breaks will display).|
|Price Break Required Quantity||If price break behavior display is set to “Show” enter the maximum quantity across all pricing adjustments within JD Edwards that if provided will return a price break. For example, if product price break discounts are provided at quantity of 5, 10 and 15, enter 15 as the price break quantity.|
|Enable Taxed Prices||JDE functionality for taxed pricing must be enabled or this option will not be enabled. When JDE taxed pricing is on tax is calculated using a JDE business function. Options are:
|Tax explanation code for Vertex||For Vertex users only - A user defined code (00/EX) that controls how a tax is assessed and distributed to the general ledger revenue and expense accounts|
|Calculate Tax in History Search||
Determines if tax is calculated in historical searches. For Customers working with Tax included it is recommended to configure the setting On. Please note performance may be impacted when this setting is on to allow for calculations (for example during the export to Excel from Shopping History).
This setting applies for the Search and the Detail views as follows:
For Customers working with Tax included it is recommended to configure the setting On.
|Insert New Products at Top of Cart||
Products inserted into shopping cart can be inserted at top of list of at end of list. Possible values are:
No Insert at end of list
Yes Insert at top of list
|Accumulate Product Quantities on Same Line Upon Insertion||
Products inserted into shopping cart can be accumulated on same line if same product or can be inserted on separate lines. Possible values are:
No Accumulate on separate lines
Yes Accumulate on sale line
|Bypass Inventory Commitment in Shopping Cart||
Determines if inventory commitments will take place when products (excluding kits) are placed into the shopping cart or not. Regardless of this setting inventory will commit when the order is placed. Possible values are:
No - Do not bypass commitments means inventory will be committed when placed in the cart
Yes - Bypass commitments in the shopping cart means inventory will not be committed when the product is in the cart, but it will continue to be committed when the order is placed
Please note this setting will override P4210 version setting to bypass commitments.
|Allow Foreign Transactions||
Determines if orders can be recorded in a currency other than the base currency of the company. Possible Options are:
|CRS call back hold code||Hold code utilized when placing an On Account Sales Order for Customer Service Representative (CSR) Call Back.|
|AvaTax Hold Code for Tax Revision||Hold code utilized when the tax cannot be calculated for an order.|
|Order Header Commission Information||Defines which commission code will be used.|
|Configured Products Allowed Segmented Values||
Defines how configured product segment values will be retrieved to display them in the Customization view in Product Content widget.
Calculated using SmarterCommerce logic - Segment values will be retrieved without executing JDE Business functions and validating cross segment rules using custom logic. Using this option will improve performance.
Calculated using JDE - Segment values will be retrieved executing JDE Business functions.
|Minimum Line Status Required to Enable Insert Lines (Modify Order)||At least one line on the order must have a next status less than the value configured here to be able to insert lines on the order.|
|Decimal Places to Display Weights||Determines how many decimal places are displayed for item weights.|
|Decimal Places to Display Totals||Determines how many decimal places are displayed for totals.|
|Decimal Places to Display Prices||Determines how many decimal places are displayed for the unit price.|