Advice Bitlog before making any changes in settings.

New combined view parameters and site settings.


Possibility to search/ filter options. View settings by module.  

Changes are saved automatically, marks the last changed.

Right-click to select restore setting.

Parameters

AdditionalItemSearchField

  • Select in list if you need an additional search field on item. 

AddressCodeControlActivated

  • Yes:

Activates control and validation of AddressCodes on the Delivery addresses. The maintenance of this function is done under Warehouses and per Picksite

  • No:

Address code validation is not activated

AddressCodeField

  • What field on the Delivery address that should be validated (only needed for maintenance)

AddressCodeView

  • Selects the view in database to fetch the description of field data.

AddressKeyFormat

  • Address-key that determines the consolidation of deliveries. The values are separated by # and you create the address key by pressing build.

AdjustDeliveryDateByDeliveryTime

  • Yes:

Uses the number of delivery days from Delivery Groups or Delivery Methods setting when calculating confirmed delivery date on order lines. The number of days that are set will be added to the confirmed delivery date calculation.

  • No:

System does not take in count the number of delivery dates into the delivery date calculation

AllowQuantityDecimals

  • Yes:

Quantity with decimals will be accepted in the system.

  • No:

  Function inactivated.

AsyncErpUpdate

  • Yes:

Async is activated. WMS will confirm and wait until its clear to confirm to ER, ERPContext must be complete to activate Async.

  • No:

 Function inactivated.

AuditLogActivated

  • Yes:

-

  • No:

 Function inactivated.

BusinessEvents (Credit Control) (only for ERP iScala)

  • Yes:

Activates ERP Business Events. This will raise events when changing credit limit in Credit Control Client and when confirming delivery in Workstation Client.

  • No:

Business events will never be raised.

CalculatePriceOnAllocationOrders (only for ERP iScala)

  • Yes:

The prices on INTR orders that uns positive and one negative order line will be calculated. For example: Line 1-5 includes stock items consisting of 1 QTY each and total cost of 100 euro and line 6 is a negative line that will be manufactured on the INTR order. The cost for this line will be the sum of line 1-5, in this example 100 euro

  • No:

Function inactivated.

CalculateUserPerformance

  • Disable:

Function disabled.

  • Hourly:

User performance is being calculated every hour.

  • Daily:

User performance is being calculated every day.

CampaignItemCounter

  • Numerical suffix (padded with zeros from the left).

CampaignItemPrefix

  • Textual prefix of every campaign item.

CheckOrderLinesUponAllocation (only for ERP Visma B)

  • Yes:

Checks orderlines when allocated.

  • No:

Function inactivated.

CODPaymentTerm (Credit Control) (only for ERP iScala)

  • Payment term in ERP used for COD payments. COD Payments are ignored from credit-checks and used to calculate specific COD charges on orders. The value for these orders will also be excluded from delivered not invoiced value.

CommonPickingActivated (only for ERP iScala)

  • Yes:

Activates integration to common picking tables and ERP Distribution will update the tables when printing and confirming deliveries in Workstation Client.

  • No:

Common picking tables will not be updated.

CompanyCode

  • Is the company ID that the parameters is setup.

ComplimentoryStockItems

  • 0 – Disabled:

This feature will be disabled

  • 1 – Deliver Together:

The orderline ending with 1 will be shipped together with the preceding line. For example, line 000011 will be shipped together with 000010.

CrateEventManager

  • Is the Used for Bitlog customization settings.

CreateAllocationOrders (only for ERP iScala)

  • Yes:

A sales order will be created in ERP that reflects the centralbooking in Bitlog WMS.

  • No:

Function inactivated.

CreditDueInDays (Credit Control) (only for ERP iScala)

  • The number of days in Credit Control tab “Due in X days”. Where X is this setting

CreditLimitFields (Credit Control) (only for ERP iScala)

  • Press “Build” to change the fields that should be taken into consideration when doing credit check on orders

CreditRiskCalculation (Credit Control) (only for ERP iScala)

  • Press “Build” to change the fields that should be taken into consideration when doing credit check on the tab “Credit Risk”

CreditRiskDueInDays (Credit Control) (only for ERP iScala)

  • The number of days used in Credit Risk calculation. Please note that parameter “CreditDueInDays” will still apply when customers is shown in Credit Control.

CreditSaveWithoutProposals (Credit Control) (only for ERP iScala)

  • Yes:

If you are not using Bitlog WMS Distribution Planning and want to credit stop all customers that have exceeded their credit limit

  • No:

Do not credit stop all customers that have exceeded their credit limit.

CreditStopOnOverdueInvoices (Credit Control) (only for ERP iScala)

  • Yes:

The function to credit stop overdue invoices is activated. The number of percentage of the customer’s credit limit to use is entered in the parameter “OverdueInvoiceTolerancePercentage”

  • No:

Function to credit stop on due invoices is inactivated

CreditTaskHistory (Credit Control) (only for ERP iScala)

  • This parameter sets how long Task history should be saved. The parameter is in If parameter is set to 0, task history will never be cleared.

CreditTaskMailAddress (Credit Control) (only for ERP iScala)

  • Sender e-mail address for Credit task mail.

CreditTaskMailSender (Credit Control) (only for ERP iScala)

  • Sender name for Credit task mail.

CreditTaskMailSubject (Credit Control) (only for ERP iScala)

  • Subject for Credit task mail.

CreditTaskMandatoryComments (Credit Control) (only for ERP iScala)

  • This parameter is linked to Credit Control and Tasks settings YES - NO

CreditTaskReminder (Credit Control)

  • This parameter is linked to Credit Control and Tasks settings YES – NO

CrossDockActivated

  • Yes:

CrossDock is available.

  • No:

Function inactivated.

CustomerDeliveryDaysField (only for ERP iScala)

  • Enter the last two digits from SL01 field that customerdelivery day is specified.

CustomerTypeForBookingOrders (only for ERP iScala)

  • 0 – Invoice:

InvoiceCustomer will be used to link the order to the booking.

  • 1 – Order:

OrderCustomer will be used to link the order to the booking.

  • 2 – Delivery:

DeliveryCustomer will be used to link the order to the booking.

DataProtection

  • Will mask or delete shipment or customer info, please enter months/ days using “build” button. Note! Deleting is irreversible!

DefaultCurrency

  • Enter default currency.

DefaultPrinter

  • Entered default printer in Documents is displayed.

DefaultReleaseCost

  • Default release cost used in Storefront if customer releases order put on wait.

DefaultZoneTitle

  • Used if no Zone title has been set.

DelayedPurchaseIgnoredAfterDays

  • Enter no of days when the delayed Purchases should be ignored.

DeleteUsedBookingOrders (only for ERP iScala)

  • Yes:

Used bookings will be deleted automatically.

  • No:

Function inactivated.

DeliveredNotInvoicedUpdateActivated

  • Yes:

If activated it will re-calculate delivered not invoices value (SL01058). Should only be activated if ERP problems exist.

  • No:

Function inactivated.

DeliveredNotInvoicedUpdateTime

  • What time the delivered not invoiced value should be calculated (Format HH:MM).

DeliveryDateLogActivated

  • Yes:

Distribution Planning will log all changes to the Delivery Date on the sales order lines, this can be accessed from Manager client on the Sales Order tab on line level menu.

  • No:

System will not log changes to delivery dates.

DeliveryMethodControlActivated

  • Yes:

Activated the Zip Code control functionality maintained under Warehouses and per picksite

  • No:

Zip Code validation inactivated.

DeliveryMethodControlUpdateOrder

  • Yes:

When the Delivery validation feature changes the delivery method on the order, when doing customer delivery, it will update the sales order with the new delivery method.

  • No:

Function inactivated.

DeliveryNoticeActivated

  • Yes:

Activates delivery notice by e-mail consisting of information regarding the delivery. The e-mail will be sent when the delivery is made in Workstation Client. Specific setting for Delivery Notice is set in File/Delivery Notice.

  • No:

Function inactivated.

DeliveryNoticeExternalAddresses

  • 0 – E-mailaddresses are retrieved from Bitlog WMSs address register.
  • 1 – E-mailaddresses are retrieved from Bitlog WMSs address register and from an external address register per ordercustomer.
  • 2 – E-mailaddresses are retrieved from Bitlog WMSs address register and from an external address register per sales order.

If the setting is 1 or 2, a view in the database for the delivery notice needs to be added.

DeliveryNoticeFolder

  • If you activate an XML delivery notice this is the folder that the files will be saved to. The file will be saved by Distribution Service on the server, please verify security setting for the folder for the user that run the Distribution Service. 

DeliveryTermImmediate

  • Determines what delivery term should be used as immediate. This will be used in Storefront when releasing a waiting delivery and in the system to override delivery release parameter (to ship the goods immediately whatever settings on the delivery term/customer/order)

DeliveryTermWait

  • What delivery term should be used as waiting term? This will be set on the order in Storefront if the customer choices to wait with his small shipments. This will enable consolidation of the delivery with his next order.

DocumentFolder

  • Set where documents should be saved

DisableCreditControl (only for ERP iScala)

  • Yes:

Will deactivate the credit check and inactivate the use of Credit Control.

  • No:

Credit check is activated and integration to Credit Control will be working. Please note: If the feature is activated the Credit Check will be active even if a license for Credit Control is missing. This is not recommended but is useful if you want to disable risk of delivering to customers with exceeded credit. The corresponding order-lines will be flagged as “creditstop”.

ERPContext

  • Select Build to enter information for your ERP Context.

FavourOrderDateOnProposals

  • Yes:

Proposals with oldest order date are favored before other proposals.

  • No:

Function inactivated.

FavourPickingFromStandardBin (only for ERP iScala)

  • Yes:

The system will allocate goods primary from the current item standard bin, this will be done regardless of FIFO. If goods is not available at the standard bin it will allocate according to FIFO.

  • No:

System will always allocate goods according to FIFO.

FavourTodaysProposals

  • Yes:

Today’s proposals are favored before other proposals.

  • No:

Function inactivated.

FlagProcessedSalesOrders (only for ERP iScala)

  • Yes:

Orders processed by Distribution Planning Service will be flagged with 1 in the field OR01128, often used to get information on which orders are processed by the service.

  • No

Will not flag processed orders.

FreightCalculationMethod

  • 0 – PerOrder:

Freight will be calculated per each order.

  • 1 – PerShipment:

Freight will be calculated per shipment.

FreightCostAccountNo (only for ERP NAV)

  • Enter the cost account for the freight.

HistoryBackupActivated

  • Yes (default):

Activates the History backup time.

  • No:

De-activates the history backup time. This is not recommended.

HistoryBackupDays

  • Enter number of days to move to history (default 1 day, the day before backup run)

HistoryBackupTime

  • What time should History backup run. Please note that it will move delivered proposals to the history older than the current date. If you want only the last days figures open In Client you should set a time after midnight and before normal warehouse-operations start. (format HH:MM)

IgnoreDelTimeCalculationOutsideLeadTime

  • Yes:

Distribution Service will ignore all delivery date calculation on order-lines with wished delivery date outside the current stock codes lead time. All order-lines with wished delivery-date outside lead-time will be confirmed to the same date as wished.

  • No:

Distribution Service will calculate delivery date calculation on all order-lines.

IncludeLeadTimeInAutoDistribution

  • Yes:

The system will include the leadtime set on the current stock-code in the calculation of availability quantity. Please see separate documentation for more information

  • No:

It will only use the number of days set on Delivery Groups and Delivery terms to reserve quantity when calculating available quantity.

IncludeUnconfirmedPurchaseOrders

  • Yes:

When calculating delivery dates, it will also take into consideration the un-confirmed purchase order lines

  • No:

It will only use confirmed purchase order lines when calculating delivery dates

IntangibleItems (these items will always be confirmed along with other items)

  • 0 – Ignore:

Items will be ignored in Pickinglist but confirmed along with the other items in the proposal.

  • 1 – Propose and Deliver:

Intangible items will be proposed for picking and delivered when confirming picking proposal automatically.

  • 2 – Propose Allow Changes:

Intangible items will be proposed for picking but when confirming proposal, it will be possible to adjust picked quantity.

InternalOrders

  • 0 – AssemblyOrders:

All INTR orders will only be proposed if there are positive lines (one or multiple) and only 1 negative line (the stock item that should be produced)

  • 1 – Ignore:

Negative lines will be ignored from the picking proposals and proposed for picking

  • 2 – Flexible:

If there are negative lines the order will be handled as assembly order. If not it will be proposed as a normal order.

INTRCostPriceCalculation

  • Yes:

Calculates new cost prices on the manufactured order-lines according to the lines used to manufacture the item. Please note: Only one negative order-line per production order can exist with this setting. Orders with more than one negative order-line will be completely ignored.

  • No:

Uses the cost-price entered on the negative order-line. Supports several negative order-lines on production orders.

ItemDeliveryTypeScalaField (only for ERP iScala)

  • Set what field should determine the type of delivery. This is used in delivery release settings to make different release values for different type of stock items. Data to enter on stock-code in ERP to activate is ‘1’

ItemDistributionTypeScalaField (only for ERP iScala)

  • Set what field should be used to determine the type of distribution should be used. If the stock-code has an ‘1’ in that field the item must be prioritized in manual distribution before Distribution Service will propose it for picking. Normally used for articles with severe shortage.

LastPerformanceStatisticsUpload

  • Shows when last upload was made.

LastVolumeUpload

  • Shows when last upload was made.

LogDestroyedProposals

  • Yes:

Deleted proposals logs are activated.

  • No:

Function inactivated.

Logs

  • SystemAdmin Logs, 0 = equals standard.

MailServer

  • Enter the address of the mail server. 

ManualFreightCosts

  • Yes:

Will de-activate the freight calculation and enable possibility to add manual freight cost when confirming proposal.

  • No:

Freight calculation is active.

MaxReloadListResultsCompact

  • Enter how many results you wish to be presented in Reload list in Wms.

MaxSearchResultsCompact

  • Enter how many results you wish to be presented in Wms mobile client.

MaxSearchResultsManager

  • Enter how many results you wish to be presented in Manager.

MaxSearchResultsWorkstation

  • Enter how many results in each DeliveryGroup to be presented in Workstation.

NextDeliveryNoteNo

  • Enter Delivery note number counter that should be used.

NextProposalNo

  • Enter Proposals No counter that should be used.

NextVolumeUpload (Bitlog Online)

  • Set time for volume upload.

OnlinePrintActivated

  • Yes:

Online printing is activated.

  • No:

Function inactivated.

OrderCounterForAllocationOrder (only for ERP iScala)

  • Add-on functionality not activated: What ordercounter should be used when creating orders in the function Booking orders.

OrderFieldFreightCosts (only for ERP iScala)

  • Select the field to update with the Freight cost.
  • Note! If the field is not selected the freight calculation will be disabled.

OrderFieldPackingCosts (only for ERP iScala)

  • Select the field to update with the COD cost.
  • Note! If the field is not selected the COD calculation will be disabled.

OrderStatusCreditStopped

Only used in combination when: OrderStatusUpdateOnCreditStop is set to “Yes”.

  • The order status that Credit Control should be change to when marked for credit stop.

OrderStatusesIgnored

  • If you want the system to ignore certain order statuses completely from all calculation you can enter them here. Multiple statuses can be set, separate with - ;

OrderStatusesStopped

  • Here you enter the order statuses used for stopped orders. Orders with this status will still get reserved quantity but not be proposed for delivery.

OrderStatusForAllocationOrder (only for ERP iScala)

  • What orderstatus to use for allocation orders in the function “Central Booking orders”.

OrderStatusFreightFree (only for ERP iScala)

  • If you want to enable setting of freight free from within ERP you can do this by setting a special-order status as freight free.

OrderStatusNormal (only for ERP iScala)

Only used in combination when: OrderStatusUpdateOnCreditStop is Yes.

  • The order status that Credit Control should change to when released for delivery in Credit Control Client.

OrderStatusUpdateOnCreditStop (Credit Control)

  • Yes:

This feature will enable the use of ERP Order Status changes when making credit stop on sales orders. To maximize the use you should combine the settings with ERP security features for allowing/disallowing users to change the order status away from Credit Blocked. You should also configure ERP order status so for example it is not possible to print picking list or confirm a delivery in ERP. This parameter interacts with these settings:

      • OrderStatusCreditStopped
      • OrderStatusNormal
  • No:

Function inactivated.

OverdueInvoiceTolerancePercentage (Credit Control)

  • Sets the number, in percentage, of overdue invoices of the customer’s credit limit that should trigger a credit-stop.

PackingCostsAccountNo (only for ERP NAV)

  • Enter the cost account for the packing.

PerpetualStockTakeActivated

  • Yes:

Stock take while picking (zero balance) activated.

  • No:

Function inactivated.

PickingEventManager

  • Used for Bitlog customization settings.

PickingListSortingManager

  • Used for Bitlog customization settings.

PickingStartedEventHandling

  • 0 – Synchronized
  • 1 – Background

PickingStartedEventManager

  • Used for Bitlog customization settings.

PickingStatisticsLevel

  • 0 – Proposal
  • 1 – ProposalItems

PreallocateProposalsOnPreview (only for ERP iScala)

  • Yes:

Preallocates proposals when previewing in Workstation Client. This will show the bin-number on the order lines not yet printed for picking. Will decrease performance.

  • No:

Disables bin-number view on not printed proposals in Workstation Client.

PrintDeliveryNotesFromClient

  • Yes:

Will use the client machine for printing the proposals. Necessary for some special printing logic. Prints to the printer set-up on the user in Bitlog WMS. If printer setting is missing or Printer prompt is disabled, printing will be done to the default printer in Windows.

  • No:

Will use the Distribution Server for printing the proposals

PrinterPrompt

  • Yes:

Activates a printer dialogue when printing proposals and confirming Delivery notes. (Requires PrintDeliveryNotesFromClient = Yes)

  • No:

De-activates a printer dialogue when printing proposals.

ProcessingOrdersActivated (only for ERP iScala)

  • Yes:

Activates processing orders. Customizations.

  • No:

Function inactivated.

ProductionOrderCustomer

  • Enter customer number that should be used for Production orders.

ProductionOrdersActivated

  • Yes:

Activates MPC functions within Distribution Planning

  • No:

De-activated MPC functions within Distribution Planning.

ProductLaunchActivated

  • Yes:

Reads ErpStockItem.ProductLaunchDate and updates confirmed delivery date to ProductLaunchDate and sets the status to “Delivery Blocked” if the ProductLaunchDate is not passed.

  • No (default):

  Normal logic

ProposalDestroyedEventManager

  • Used for Bitlog customization settings.

ProposalGroupingActivated

  • Yes:

Activates the use of Batch-lists (summary page with several delivery proposals grouped together). Note: This setting requires some additional work on the documents

  • No (default):

Normal logic without Batch-lists.

ProposalInterval

  • Settings, in minutes, how long delay should be used between Distribution Service runs on workdays

ProposalIntervalWeekend

  • Settings, in minutes, how long delay should be used between Distribution Service runs on Saturdays and Sundays (normally longer intervals).

ProposePrintedOrders

  • 0 – Propose:

Propose new order lines for picking for orders that are currently being picked.

Used in combination with “Replenishment Proposals“ settings for each Delivery methods.

  • 1 – Block:

New order lines for orders that are being picked will not be proposed.

  • 2 – BlockStockStatusWaiting:

PurchaseOrderDeliveryDays

  • Number of days that should be added to sales order that are reserved from the purchase order.

RecalculateStockOptions (only for ERP iScala)

  • Will recalculate SC03 accumulated values, please select values using “build” button.

Note! Should only be activated if experiencing problems with these values.

RecalculateStockTime (only for ERP iScala)

  • What time the recalculation of values in SC03 should be done (format HH:MM).

RedirectPickingActivated

  • Yes:

Activate the functionality for Redirect Picking

  • No:

Function inactivated.

ReleaseMaxDaysAnything

  • Default value if delivery release parameter is not set.

ReleaseMaxDaysComplete

  • Default value if delivery release parameter is not set.

ReleaseValue

  • Default value if delivery release parameter is not set.

ReturnOrderCounter

  • Used for sales order return, customization.

SalesOrderSorting

This parameter sets the order for how the warehouse stock should be reserved for SalesOrders. Distribution Planning will sort the available quantity according to the parameter and reserve requested quantity in that order. 

  • 0 – Required date, Order date, Order No:

With this setting Distribution Planning will sort first on required date of the order.

  • 1 – Order date, Required date, Order No:

This is the normal ERP delivery proposal logic.

SaveStockPlanning

  • Yes:

Default value that activates specific data storage used in Distribution Planning

  • No:

Should only be set when running Credit control only.

SerialNumbersActivated (outgoing goods)

  • Yes:

In Workstation Client the system will check the Serial Number flag set on the stock code in ERP. If Serial number is required for the product it will trigger a dialogue for serial number entry.

  • No:

Serial number will be deactivated without any regard of settings on the product in ERP

SerialNumbersAddsAsTextLines (only for ERP iScala)

  • Yes:

Serialnumbers will be shown as TextLines on orders in ERP.

  • No:

Serialnumbers will not be shown as TextLines on orders in ERP.

SerialNumbersLength

  • Here you enter the length for the serial number that is accepted by the Workstation Client. Multiple acceptable lengths can be added separated with ; sign (example: 5;6;7;8)

SerialNumbersPrefix

  • Prefix before the serial number to be put on the order text line. Normal logic is the prefix: S/N:

ServiceDataLoading

  • Alternative to load info from ERP, select “build”.

SMTPServer

  • Enter the SMTP server to use when sending Delivery Notice and error messages

StatisticTime

  • What time to calculate the statistics (format HH:MM)

StockEventManager

  • Used for Bitlog customization settings.

StockItemDescriptionSource

  • 0 – OrderLine
  • 1 – StockItemRegister

StockStatusWaiting

  • You can select a stock status here and those items will note be proposed for picking as long as other items on the same order can be picked.

StockTransactionReference

  • Select what customer code should be used when transactions created when confirming delivery

0 – CustomerCodeInvoice

1 – CustomerCodeOrder

2 – CustomerCodeDelivery

SuggestStorageManager

  • Used for Bitlog customization settings.

TransferOrdersActivated

  • Yes:

TransferOrders are activated.

  • No:

Function inactivated.

TrolleyRouteManager

  • Used for Bitlog customization or Bitlog standard picking route.

UpdateConfirmedDeliveryDate (only for ERP iScala)

  • Yes:

iScala order lines (and delivery planning) and the confirmed delivery date will be updated with delivery dates calculated by Distribution Service

  • No:

iScala orderlines (and delivery planning) will not be updated by Distribution Service.

UpdateConfirmedDeliveryDateToLatest

  • Yes:

If the orderline can be partially delivered the date will be set to the latest date that the whole order-line can be delivered

  • No:

The order-line will be set to the earliest available delivery date.

UploadPerformanceStatistics

  • Yes:

Upload performance statistics on user level, uploads to Bitlog Online. 

  • No:

Function inactivated.

UploadPickingStatistics

  • Yes:

Upload picking statistics, uploads to Bitlog Online.  

  • No:

Function inactivated.

UseCustomerDeliveryDays

  • Yes:

Uses the customer delivery days that are set in CustomerDeliveryDaysField.

  • No:

Function inactivated.

UsePartialLineDeliveryFlag (only for ERP iScala)

  • Yes:

Distribution Planning will read the ATP flag on the sales order if the line should be delivered complete (”Accept line split” = No)

  • No:

The setting for Partial Line delivery will not be taken into consideration.

UseScalaPickingList (only for ERP iScala)

  • Yes:

Will deactivate the use of Manager and Workstation Client. Recommended to be used when running Credit Control without Distribution Planning.

  • No:

Will not de-activate Workstation Client and Manager Client. This is the normal setting when running Distribution Planning.

UserDefinedFields

  • Used for Bitlog customization settings, please contact Bitlog.

UserPhotosActivated

  • Yes:

Enable profile pictures.

  • No:

Function inactivated.

UseUnconfirmedDeilveryDateOnUpdate

This parameter will interact with other parameters, please see separate documentation for more information.

  • Yes:

If unconfirmed delivery-date is calculated the system will set the date 2049-12-31 = unconfirmed.

  • No:

Will not use the unconfirmed delivery-date.

WarehouseRouteManager

  • Used for Bitlog customization settings.

WeekdayReleaseCustomerType

  • 0 – InvoiceCustomer:

The Invoice Customer fixed delivery days is used when to deliver.

  • 1 – OrderCustomer:

The order customers fixed delivery days is used when to deliver.

  • 2 – DeliveryCustomer:

The delivery customers fixed delivery days is used when to deliver.

WeightAndVolumeFromStockItem

  • Yes:

Weight and volumes comes from article directory.

  • No:

Function inactivated.  

VirtualStock (Credit Control)

NOTE: Only for Credit Management! Should not be used if you use Distribution Planning

  • Yes:

Should be used if you in Credit Check want to include all sales orders that’s in ERP without taking any consideration if the stock is available or not.

If enabled, Virtual Stock will Credit check all sales orders as they all have available stock for shipment.

This can be combined with the setting above – OrderStatusUpdateOnCreditStop.

  • No:

Function inactivated.  

YardManagement

  • Yes:

Activates WMS service to calculate Yard Management for purchase orders.

  • No:

Function inactivated.  

ZipCodeField

  • Select the field that should be used for Zip Code validation. If 0 is selected (undefined) the function will be deactivated.

ZipCodeLength

Select how many characters that the Zip Code consists of. The validation function will automatically ignore spaces in zip code. If you for example enters Zip Code like this: “123 45” it will still be 5 characters in length despite the space.



Site settings

AllowChangeQuantityOnBatch

o  Yes:

Quantity is possible to change when batch picking.

o  No:

Function in activated.

AllowOverDeliveryIn 

o  Yes:

Allows over delivery when receiving goods. 

o  No:

Over delivery is not permitted.

AllowOverDeliveryOut 

o  Yes:

Allows over delivery on specific orderlines. Over delivery will not be allowed if the amount to over-deliver is not available on the same bin-number.

o  No:

Over delivery of order lines is not permitted.

AllowToConfirmSingleItemBatchFromMobile

o  Yes: 

 Possible to confirm Single item batchpick in iPad or in workstation. 

o  No:

Only possible to confirm Single item batchpick from workstation.  

AssignPickingBoxPositions

o  Yes:

Assign PickingBoxes to positions on trolleys when batch picking. 

o  No:

Function inactivated.  

AutoCalculatePackingCosts

o  Yes:

Automatically calculates the Packing costs. Gets the values from settings in Expedition. 

o  No:

Function inactivated.  

AutoCalculateShippingWeight

o  Yes:

Automatically calculates the shipping’s weight. 

o  No:

Function inactivated.  

AutoSendMailForIncomingGoods

o  Yes:

Automatically sends e-mail for reported incoming goods. 

o  No:

Function inactivated.  

BlockBufferBatches (only for ERP iScala)

o  Yes:

Locks all batches to buffer from receive. 

o  No:

Function inactivated.  

BoxPicking

o  Yes:

Allow Box Picking

o  No:

Does not allow Box Picking

CalculateUserPerformance

o  Yes:

 Calculation on user performance is activated. 

o  No:

Function inactivated.  

CashOnDeliveryDangerCode

o  Enter code for COD danger code. 

CompactAddressFormat

o   Select which address fields you wish to be shown in mobile using “build

ConfirmTrolleyFromMobile

o  Yes: 

 Possible to confirm trolleys in iPad or in workstation. 

o  No:

Only possible to confirm trolleys from workstation.  

CrossDock

o  Yes:

Cross Dock per site is activated. 

o  No:

Function inactivated.  

CrossDockBinNo

o  Fixed BinNo for Cross Dock. 

CrossDockDeliveryGroup

o   Select in list that DeliveryGroup CrossDock orders should be in (preferable an own group).

CrossDockPrintDocument

o   0 – None:

No document will be printed. 

o   1 – DeliveryProposal:

Delivery Proposals will be printed

o   2 – DeliveryNote:

Delivery np will be printed. 

DeepReloadActivated

o  Yes:

 Reload for deepbuffer is activated.    

o  No:

Function inactivated.  

DefaultDeliveryGroup 

o   If no mapping has been done when grouping proposals into delivery groups this setting will be used as default.

DefaultInboundQuantity

o  Select a default value of inbound quantity. 0 = ordered qty, 1 = 1

DefaultStockMoveReason

o  Enter number of qty to include in cross-dock handling.

Deleted

o  Yes:

 Picking site is deleted.    

o  No:

Picking site, I still active. 

DeleteReceivedRecordsAfterRemovingFromCrate

o  Yes:

 Item and qty is removed to Incoming goods. 

o  No:

Item and qty is removed to Stock Received.   

DeliveryGroupAssignment

Set your own hierarchy to your delivery groups using build

DirectReceiveToCrate

o  Yes:

 Activates direct receive by crates.    

o  No:

Function inactivated.  

DiscrepancyHandlingActivated (Advanced licens required, not for ERP iScala)

o  Yes:

 Activates discrepancy handling during picking.    

o  No:

Function inactivated.  

DiscrepancyWarehouse

o  Select from list to what warehouse the discrepancy handling should be moved to. 

DynamicReloadLevelActivated

o  Yes:

 Dynamic reload is activated per site and updates depending on setting:  DynamicReloadLevelExecTime   

o  No:

Function inactivated.  

DynamicReloadLevelBufferHours

o   Enter how many hours you wish to calculate the reload level with. 

DynamicReloadLevelExecTime

o   Time of day to calculate the dynamic reload levels. 

DynamicReloadLevelLastTime

o   Last execution time (read only)

DynamicReloadLevelReloadHours

o   Enter how many hours you wish to calculate the reload with, with. 

Dynamic Reload Example:

Expected sales: 1000 per month                            Worktime per month: 60x4 weeks =240 hours

DynamicReloadLevelBufferHours: 4 hours             Consumption per hour: 1000/240 = 4,2

DynamicReloadLevelReloadHours: 6 hours           Reload level: 4x4,2 = 17

ManHoursPerWeek: 60                                         Reloads with: 6x4,2 = 25

EnableBinExtension

o  Yes:

If bin extension is used.  

o  No:

No extension is used for bins.   

ExcludeSingleProposalsFromBatch

o  Yes:

Excludes single packages to batch-pick.    

o  No:

Function inactivated.  

FixedBinLength

o  Yes:

Bins have fixed number length equals to MaxBinLength number. 

o  No:

Function inactivated and you can add bin name/ number between MinBinLength and MaxBinLength.   

FloorArea

o  Select Area from list to use as floor-area to reload to if allowing reloads when site setting ReloadFromBufferBeforePicking is activated. 

FreightStockCode

o  Enter fixed StockCode if freightcost should be on orderline. 

GroupBestBeforeDates

o  Yes:

Groups items with best-before dates on same bin

o  No:

Function inactivated.  

GroupStructureComponents

o  Yes:

Structure Items will be grouped in the proposal.

o  No:

Function inactivated.  

ImportCodeFromExternalWarehouse (only for ERP Visma B)

o  Used for bonded or non-bonded goods. 

ImportCodeStockDifference (only for ERP Visma B)

o  Used for bonded or non-bonded goods. 

IntengibleItems = 0 - Ignore

If setting = Ignore we should not present integibleItems items as a backorder line since this item will not be handled by WMS.

ManHoursPerWeek

o  Number of hours a normal week. 

ManualFreightCost

o  Yes:

Possible to add manual freight cost when confirming proposal.

o  No:

Function inactivated.  

ManualShipmentBoxes

o  Yes:

Activates the function of adding packages while picking. 

o  No:

Function inactivated.  

ManualStockReloadProposals

o  Yes:

Manual Reload Proposals are created in WMS Manager and must be Approved before handled in iPad. 

o  No:

Function inactivated. 

MaxBinLength

o  Enter value of maximum numbers for bin length. 

MaxBoxFactor

o  Enter value for maximum number of boxes in dynamic batch picking, 

MaxCrossDockDays 

o  Select how many days Wms should look forward in time to include sales orders. 

MaxCrossDockQuantity 

o  Enter number of qty to include in cross-dock handling.

MaxNumberOfReturnedSupplierPurchaseLines

o  Enter how many Purchase orderlines you wish to see in iPad. 

MaxPickingVolume

o  Enter maximum volume of total proposals to be included in dynamic batch picking. 

MaxPrePickingDays 

o  Select how many days Wms should look forward in time to include sales orders. 

MaxSingleItemProposalQuantity

o  Enter number of qty to include in single-batch picking.

MediaBankID (E-commerce Accelerator license required) 

o  Enter account information. 

MediaBankKey (E-commerce Accelerator license required) 

o  Enter account information. 

MinBinLength

o  Enter value of minimum numbers to enter when searching for bin. 

MinBoxFillVolumePercent

o  Enter value of min filled percent of box fill. 

OneDailyDeliveryPerCustomer

o  Yes:

 One delivery per day per customer Is activated.   

o  No: 

Function inactivated.  

OrganizeBatchPickingByArea

o  Yes:

 Batchpick organized by picking area (how batchpick is proposed). 

o  No: 

Function inactivated.  

PackingStockCode

o  Enter fixed StockCode if packingcost should be on orderline. 

PerpetualStockTake

o  Select Build to enter your settings. 

o   Enter your settings for Perpetual stock take. 

PickingAreaOffloadActivated

o  Yes:

 Automatic offload is activated. 

o  No: 

Function inactivated.  

PickingAreaOffloadExecTime

o  Time of day to automate the offloads, reloads. 

PickingAreaOffloadLastTime

o  Last execution time (read only)

PickingAreaSyncActivated

o  Yes:

Activates the synchronization of Areas from external system (ERP). 

o  No: 

Function inactivated.  

PickingAreaSyncExecTime

o  Time of day to synchronize picking areas. 

PickingAreaSyncLastTime

o  Last execution time (read only)

PickingBinForMultipleItems

o  Yes:

Allows multiple items to have the same picking bin. 

Enables possibility to receive items to other bins within the warehouse.

o  No:

Function inactivated.  

PickingFields 

o  Select fields to be visible in small device (iPod/ iPhone)

PickingWarehouse

o  Define picking warehouse. 

PickManualQty

o  Yes:

Enter picked quantity manually. 

o  No:

Function inactivated.  

PickStyle (old UI, new UI – on or off)

o  0 - Deafult:

Default font style. 

o  1 - LargeFont:

Large font style.

PrepareParcels 

o  Yes:

o  No:

Function inactivated

PrepareTrolleys

o  Yes:

 -

o  No:

Function inactivated

PrintDeliveryNotes

o  0 - Undefined:

If used, it needs to be configured as 1 or 2. 

o  1 - Server:

Deliverynotes are printed from server. 

o  2 - Client:

Deliverynotes are printed from local client.

PrintDeliveryProposals

o  0 - Undefined:

If used, it needs to be configured as 1 or 2.

o  1 - Server:

Deliverynotes are printed from server. 

o  2 - Client:

Deliverynotes are printed from local client.

ProductLabelLogActivated

o  Yes:

A log of how many productlabels are printed is activated. 

o  No:

Function inactivated 

ReceivalNoteRecipients

o  E-mail address to receiver of received goods. 

ReceiveStockStandardBinNo  

o  Enter standard bin number for Direct Receive.  

RegisterDimensionsIn

o  Yes:

Operator must enter item dimensions when stock receive items with dimensions.  

o  No:

Function inactivated.

ReleaseProposalsBlockedByDeepReload

o  Yes:

Proposals will be released for picking without item that is blocked for Deep reload.

o  No:

Function inactivated and proposals will be blocked. 

ReloadFromBufferBeforePicking

o  Yes:

Proposals will not be released for picking if reload must be performed before picking from pickingplace is possible. 

o  No:

Function inactivated

ScanEveryPickedItem

o  0 – Disabled.

o  1 – Trolley and Batch:

Every Item must be scanned for Trolley picking. 

o  2 – Trolley, Batch and Normal:

Every Item must be scanned for all picking. 

SetParkingLabelsForProposals

o  Yes:

Available to print parking-labels by each propsal in batch-pick.

o  No

Function inactivated

ShipmentBoxWeightFactor

o   Multiply with this factor when automatic calculating box weight. 

ShipmentGoals (Bitlog Online)

o  Select build – enter your goals. 

ShowOriginalItemDescriptionOnPickingList

o  Yes:

If Yes, the original item description will be shown on picking list. 

o  No:

If No, the order item description will be shown on picking list. 

ShowRestOrderLines

o  Yes:

Shows orderlines that is not available for delivery in the proposal. 

o  No:

Function inactivated. 

SinglePickPrintDocument

o  0 - None:

No documents will be printed. 

o  1 - DeliveryProposal:

DeliveryProposal will be printed when confirming single pick. 

o  2 - DeliveryNote:

DeliveryNote will be printed when confirming single pick.

SiteID

o  Enter Site ID.

SiteName

o  Name if the Site (default).  

SmallPickingVolume

o  Enter maximum volume of a proposal to be included in dynamic batch picking. 

StockMovementQuantityAdjustment

o  0 – Numeric TextBox 

o  1 – Ruler for Pieces. 

StockReload

o  Show setting made in Stock reload tab in Picking site settings. 

StockReloadAssembly

o  If Custom Assembly file is uploaded, it will be shown here. 

StockReloadReset

o  Yes:

Possibility to reset untaken StockReloads by Wms service. 

o  No:

Function inactivated.  

StockReloadResetLastTime

o  Time when reset was last executed. 

StockReloadResetTime

o  Default time for when reset should execute.

Multiple times can be set, separate with ; 

 StockTakeBalanceStyle

o  0 – Label and value:

Shows value in both current balance and counted quantity. 

o  1 – Label only:

Shows value in current balance and empty in counted quantity. 

o  2 – Hidden label and value:

Shows no value in current balance or in counted quantity. 

StockTakePickingPlaceIncludeZeroBalance

o  Yes:

Items with 0 balance will be shown when entering bin number or doing stock take if the items has been assigned to the actual picking bin. 

o  No:

Function inactivated.  

StockTakeRefText (only for ERP iScala)

o  Enter value as StockTake referens.

StockTakeRefType (only for ERP iScala)

o  0 – Text:

Use StockTakeRefText as stocktake referens. 

o  1 – TakeName:

The name of the inventory list is used as stocktake referens. 

o  2 – TakeType:

Take type is used as stocktake referens.   

SuggestPicking (Advanced licens required)

o  Yes:

Service will calculate the shortest picking-round depending on settings in SuggestPickingParameters.   

o  No:

Function inactivated.  

SuggestPickingParameters (Advanced licens required)

These settings must be set-up together with Bitlog consultants.  

SuggestSectionLevels 

o  Enter percent that should be allocated to the primary section

SuggestStorageType

o  Yes:

Service will calculate how the receive should be made.

o  No:

Function inactivated.  

TabletFlags

o  Settings for iPad. 

TimeZone

o  Select from list in what timezone WMS is running.

TransportParameters

o  Select build – enter your Transport settings. 

TransportSystem

o  Select in list in which Transport system is used.

TruckPickBinNo

o  Enter truck-bin no.

UniqueShipmentBoxIdCheck

o  Yes:

Controls current box-id is not beeing used in another picking. 

o  No:

Function inactivated.  

UseLoadCarrierForMovements

o  Yes:

Load carrier are used when doing reloading in Movement task. 

o  No:

Function inactivated.  

WarnAboutDangerousGoods

o  Yes:

Warning in iPad when picking dangerous goods.  

o  No:

Function inactivated.  

WorkingTimeEnd

o   Enter work start-time, used to calculate performance.   

WorkingTimeStart

o   Enter work end-time, used to calculate performance. 

WorkstationSummary

o  0 – JustInTime:

Calculates statistics every transaction.  

o  1 – ByService:

Calculates statistics every WMS service run.

YardManagement

o  Yes:

Yard Management is used in site. 

o  No:

Function inactivated.  

ZeroBalanceTake (Advanced licens required)

o  Settings for zero balance stock take.