Options
- Send statement – displays trader in Produce statements
- Complete deliveries – all orders added for this trader default to Complete deliveries only.
- Allow invoice –
- Cancel all invoices – sets the trader and its branches to have all invoices cancelled. On sales orders, the cancelled quantity will match the ordered quantity for each line.
- Allow delivery –
- Invoice on delivery – each delivery note raised will also raise an invoice
- Invoice complete only – only orders completely delivered will be invoiced
- Give loyalty points – trader can accrue loyalty points
- Require line reference – customer reference must be entered on every order line
- Require order number – customer reference must be entered on to every order
Note: Selects the option When ordering > Require a PO reference to be entered on EvolutionX for users.
- Require header department – a department must be selected on each order (unless the trader has no departments)
Note: EvolutionX does not have the concept of order headers, so this setting is ignored by EvolutionX Export.
- Require line department – each order line entered requires a department (unless the trader has no departments)
Note: Selects the option When ordering > Require a cost centre to be selected on EvolutionX for users.
- Customer requires confirmation – prompted to print an order confirmation after taking an order
- Require analysis –
- Do not substitute items –
- Notify new calls – a call log entry is added for the user managing this account to notify an order has been placed
- Hide all transactions – no transactions will be visible in the daybook (unless a user has permissions)
- Select all contacts – contacts on this account are shared between all branches
- Select all departments – departments on this account are shared between all branches
- Force auto confirm deliveries – force deliveries to be completed for this account
-
Mask – masks let you define what is included in the Reference box for all orders for a customer.
For EvolutionX orders, mandatory masks are configured by selecting Require order number in Horizon. This selects the EvolutionX option User > When ordering > Require a PO reference to be entered when exporting data.
For HorizonWeb orders, Require order reference before checkout should be selected.
In Horizon, selecting Require order number and setting a Mask means that Reference must be completed according to the mask set before the order can be confirmed.
Note: Selecting Require order number will affect sales orders that already have Reference set so that it does not meet the new mask requirements.
- It will show as blank, even though the existing reference is still there in the database.
- You will not forced to enter a Reference if you edit the order and Confirm it.
- You can still edit the Reference so that it meets the new mask definition.
Masks cascade to delivery branches, so if Mask is left empty for a delivery branch, the mask set for the customer is used.
Type the character your customer wants its users to include. These are standard characters. You can also type the following special characters which represent a set of possible characters.- 9 – numeric (optional)
- 0 – numeric (required)
- a – alphanumeric (optional)
- A – alphanumeric (required)
- l – alphabetic (optional)
- L – alphabetic (required)
- C or c – any character (optional)
- For this list of characters, if you want to include that character (not the set described) you must precede it with a backslash. This is called escaping a character.
Note: When defining masks to define HorizonWeb references, it is recommended that you avoid using the characters ! < > \ # : / ; and _.
- You want references for a customer to start with PaO and then a number. In the Mask box, type P\aO0.
- P is a standard character.
- a is a special character so it must be escaped with a backslash
- O is a standard character
- 0 means that a number must follow the letters. Note that this doesn't have a preceding backslash because you want any number to be allowed, not force the user to include 0.
- Your customer needs each reference to start 90aA. The mask should be entered as \9\0\a\A because they are all special characters and must be escaped.
Examples
Note: A trader mask is limited to 20 characters including the escape characters.
Note: Masks are exported to EvolutionX as RegEx expressions at the Account level.
- Use main trader
- Contracts – When selected, contracts for the main trader apply to the trader's branches. When cleared, you can offer different prices for each branch, by creating sales contracts for different customer branches.
- Catalogues –
- Disable hidden switch – product hidden switches will not be applied for this customer
- Prevent swap to lead – catalogue code entered will be kept
- Auto update entry reps – any change to rep is set on all transactions for this account
- Prevent auto allocation – when selected, the Auto Allocate button is hidden
- View security –
- Modify security –
- View transactions –
Special Settings
Statements can be typed into the Special Settings box to affect entries added for the trader. Each statement should be typed on a separate line. If delivery branches exist for a customer, then each branch must have the special setting set.
Horizon
| Statement | Functionality |
|---|---|
| cxml_SUPPNOTE=Department | A node called <Extrinsic name="SUPPNOTE"/> can be included in cXML order imports from cXML Punch-outs. When received, cost centres (at header & line level) populate Department on the sales order header and the line(s). |
| hidedeptperline=true | Hides the Department for each line on order entry |
| hiderefperline=true | Hides the Reference for each line on order entry |
| holdadhocorder=true | Orders received via a cXML punch-out to Horizon with an ad hoc address will be placed on hold. |
cXML Punch-outs, Invoices and Credits
| Statement | Functionality |
|---|---|
| cXMLBasic=true | The elements in the cXML invoice file do not include the enhancements added to 4.71 onwards. This includes no support for credit memos. |
| CoupaCode=code | When creating cXML invoices or credits to send to a customer using Coupa procurement, set CoupaCode=code where code is your customer's reference code for you, used as the addressID in Contact roles. For instance, your customer orders using a procurement system that accepts cXML invoices and credit notes. They tell you what customer reference they have for you. That reference is included in ..<InvoicePartner> <Contact role="remitTo" addressID="[CoupaCode]"> |
| billTo=code | When creating cXML invoices or credits, set billTo=code where code is the agreed customer reference included in ..<InvoicePartner>
<Contact role="billTo" addressID="code"> . billTo is only included when cXMLbasic is false or not set. For cXML punch-outs to HorizonWeb, the BillTo addressID in the request is matched to the invoice address with the same billTo code in Special Settings. |
| shipTo=code |
When creating cXML invoices or credits, set shipTo=code where code is the agreed customer reference for the branch the originating order was shipped to. A shipTo element is included within the InvoiceDetailShipping element. This element is only added when a CoupaCode is set. If shipTo is set on a delivery branch, it overrides that set on the main trader. |
| soldTo=code | When creating cXML invoices or credits, set soldTo=code where code is the agreed customer reference included in ..<InvoicePartner> <Contact role="soldTo" addressID="code"> . If not set, the customer's delivery branch code is used. |
| excludeShipping=true | When creating cXML invoices or credits, within <InvoiceDetailSummary>, the elements <ShippingTax> and <ShippingAmount> are omitted. Must not have cXMLBasic=true set. |
| CoupaExtrinsic=true |
When creating cXML credit notes, extrinsic elements are included as specified for Coupa integrations. The elements included are: <Extrinsic name="CustomFields"><IdReference identifier="original_invoice_date" domain="CustomField"> <Description xml:lang="en">[invoice taxpoint]</Description> </IdReference> </Extrinsic> <Extrinsic name="CustomFields"> <IdReference identifier="original_invoice" domain="CustomField"> <Description xml:lang="en">[invoice reference]</Description> </IdReference> </Extrinsic> <Extrinsic name="CreditReason">Credit for invoice</Extrinsic> Must not have cXMLBasic=true set. |
| cXMLPositiveCreditTotals=true | When creating cXML credits, cXML Credit Memo summary totals are changed from negative values to positive values. The details line values remain negative. |
HorizonWeb
| Statement | Functionality |
|---|---|
| contractLayout=1 | Forces a redirect to ranges for orderpads. |
| createpunchoutuser=true | A contact is always created when receiving a cXML punch-out to Horizon. Overrides HorizonWeb option Allow a punch-out set-up request to create a contact when cleared. |
| hidedeptperline=true | Hides the Department for each line on order entry |
| hideHWOrderNotes=true | Hides order notes at checkout in HorizonWeb |
| invaddresstraderbasis=true | If Allow users to select an invoice address at checkout is set to On trader basis, then this customer can pick an invoice address at checkout |
| OPADMaxQty=1 | Sets the maximum quantity for an order line that can be ordered from an order-pad. The restricted quantity is set with the quantity on the order-pad line. |
| returnontraderbasis=true | If Enable online returns is set to On trader basis, the customer will be allowed to return goods. |
| H2HUniqueRefCheckDays=n | Setting is for dealers using ERP to Horizon Ordering, importing orders via posts to HorizonWeb process_opxml. Using the specified number of days (n), sales orders over the designated period are checked for duplicate references (0 denotes checking only today). Should a reference match previous orders, the sales order will not be imported into Horizon. |
See Also
