Basic Settings for Dispatch Policy

The field indicates whether a separate delivery number is created for each order.

Select the check box if a separate delivery number should be created for each order.

If you do not select the check box, an existing delivery number can be accumulated if it involves:

• Same direction (inbound or outbound)
• Same dispatch policy
• Same order category (CO, DO, RO, MO, and such)
• Same consignee (customer/address ID for CO)
• Distribution orders have the same receiving warehouse
• Same estimated dispatch date & time
• Same terms of delivery
• Same transportation method
• Same delivery note reference (CO through delivery schedule).

The field indicates whether the delivery number is automatically released for allocation after it is created.

Select the check box if the delivery number should be automatically released for allocation after it is created.

The allocation method determines how allocation is done. Settings are done in 'Item. Connect Warehouse' (MMS002).

The field indicates whether the delivery is released to create picking lists.

Select the check box if the delivery should be released to create picking lists.

This does not set whether the picking list is printed. The parameter 100 in 'Dispatch Policy. Open' (MWS010) determines whether the picking list is printed.

The field indicates the number of days before the planned picking date that picking lists are created.

The date is calculated when the delivery status is 01 (Released for auto-allocation, but nothing allocated).

The field indicates the number of hours before the planned picking date that picking lists are created.

The date and time are calculated when the delivery status is 01 (Released for auto-allocation, but nothing allocated).

The field indicates whether a credit check is done when picking lists are created for customer orders.

Select the check box if a credit check should be done when picking lists are created for customer orders.

If several customer orders are planned for the same delivery number, all the COs must clear the check.

Calculate estimated picking time

The field indicates whether estimated picking times should be calculated and saved when a picking list is created.

The calculation is based on the picking time table in 'Item. Connect Picking Time' (MMS405).

The field indicates whether picking resource planning is used.

Select the check box if picking resource planning is used.

If picking resource planning is used, picking lists are assigned status 30 when created. The picking resource planner can then change these to status 40 in 'Picking List. Plan Pickers' (MWS415).

If picking resource planning is not used, picking lists are assigned status 40 when created and so are ready to pick and report immediately.

The field indicates whether picking lists are printed automatically when they are created.

Select the check box if picking lists should be printed automatically when they are created.

Printing of picking lists also could be manually triggered by using option 6 on 'Picking List. Report' (MWS420).

The field indicates how picking lists are split, as well as the printer used to print picking lists.

The picking list is always printed on the printer set for the stock zone unless there are multiple stock zones.

Alternatives:

1. No split by zone or warehouse equipment. The printer with the highest priority is selected.
2. The picking list is split by stock zone, but not by warehouse equipment. The picking list is split and printed on the printer for each zone respectively.
3. The picking list is split by stock zone and warehouse equipment. The warehouse equipment used is as defined per item/warehouse in 'Item. Connect Warehouse' (MMS002) or location in 'Stock Location. Open' (MMS010). The picking list is printed on the printer for each zone respectively.
4. The picking list is split by warehouse equipment. The warehouse equipment used is as defined per item/warehouse (MMS002) or location (MMS010). The picking list is printed on the printer with the highest priority.

Select the check box to indicate that the picking capacity should be split.

If this option is selected, the picking release activity attempts to split one picking list into several ones based on the capacity constraints defined in 'Picking List Capacity. Open' (MWS175).

The field indicates the document variant used when a picking list is printed.

These standard variants are valid.

Alternatives:

• Blank = Lines
• 01 = Lines and unallocated lines are printed at the end of the list when only one order number is attached to the delivery. If several orders are attached to the delivery, then this alternative works as the Blank alternative above.
• 10 = Labels
• 20 = Matrix.

The field indicates the sorting sequence used when picking lists are created and printed.

Alternatives:

• 1 = By location or transportation flow code, depending on the field in 'Stock Zone. Open' (MMS040)
• 2 = By item priority (fragility level) from the item file
• 3 = By item number
• 4 = By order and order line.

This field is not used in M3.

Weights & volumes are always printed on the picking lists, and adjustments must be done using M3 Output Management.

This field is not used in M3.

Alias numbers are always printed on picking lists and adjustments must be made using M3 Output Management.

The field indicates the planned time for manual shipment consolidation (except for alternative 8, see Note) and can be used for the selection and grouping of delivery numbers in 'Delivery. Open Toolbox' (MWS410).

Alternatives:

• 0 = Shipment consolidation is optional and can be performed at any time
• 1 = Before a picking list is created
• 2 = After a picking list is created
• 3 = After packing is completed
• 4 = After goods are moved to docking location
• 5 = After final report of the picking list
• 8 = Automatic connection failed - handle as alternative 1
• 9 = Shipment consolidation is not used.

The field indicates whether picking lists can be partially reported during pick line reporting on 'Picking List. Report Lines' (MWS422) and, if so, in which packed status.

Alternatives:

• 0 = Not applicable. Full reporting only
• 1 = Partial reporting (unpacked)
• 2 = Partial reporting (unpacked) when entered from (MWS422)
• 3 = Pick deviation by planning date and time
• 4 = Pick deviation by planning date and time when entered from (MWS422)
• 5 = Pick deviation by order priority, planning date and time
• 6 = Pick deviation by order priority, planning date and time when entered from (MWS422).

Partial reporting allows different lines from a picking list to be reported at different times.

Pick deviation reporting occurs when a packed picking list line is reported with a deviating quantity and/or deviating balance ID. Deallocation and reallocation occurs when the picked balance ID is allocated by other demands or other picking lists. The deallocation continues until the allocatable inventory covers the reported quantity of the current picking list line.

Options 2, 4, and 6 allow the user to bypass the F19 key on (MWS422/E).

The field indicates the level on which pick reporting is done.

Alternatives:

• 1 = Picking line level. The picking lines are presented and reported for each allocated picking line.
• 2 = Package-based level. The presentation and reporting function is performed for each package detail line. This alternative assumes that pack reporting is done prior to pick reporting.

The field indicates whether overissue is permitted during picking reporting.

Alternatives:

• 0 = No
• 1 = Yes
• 2 = Yes + additional allocation at movement.

When the parameter is set to 2, additional allocation is enabled at the movement stages during pick reporting. The process is available when all the existing allocation lines on the picking list are located at the pack or docking location.

All existing allocation lines must have the same pick status, either 50 (all at the pack location) or 60 (all at the docking location).

The issue method must equate to the current location (50 for ‘Move to Pack Location’ or 60 for ‘Move to Docking Location’). The 'To location' for the movement being reported must be identical to the pack or docking location for the existing allocations.

The field indicates whether the completion flag field is activated during picking list reporting.

Select the check box to activate the completion flag during picking list reporting.

The field indicates whether financial transactions are created from stock transactions.

Select the check box if financial transactions are created from stock transactions.

The field indicates whether limits for completion flagging are checked against the table when reporting picking lists.

Select the check box to check against the table when reporting picking lists.

If you select the check box, one or more lines can be automatically flagged as complete if remaining quantities are within the limits set in the table, see 'Item. Connect Order Line Compl Limit' (MMS425).

The field indicates whether distribution order receipts use the status proposal on the stock location when new balance identities are created.

The field indicates whether receipt reporting at the receiving warehouse is done automatically when issuing stock at the delivering warehouse. Note that this applies only to distribution orders.

Alternatives:

• 0 = No, manual receipt reporting
• 1 = Yes, automatic receipt reporting.
• 2 = Yes, automatic receipt reporting at receiving warehouse based on an estimated receiving date (transaction date and time of the inbound delivery). This date is calculated as being the departure date and time of the outbound delivery + the transportation time defined in the distribution relation master 'Distribution Relation. Open' (DPS001).

The field determines how inbound deliveries are created.

Alternatives:

• 0 = An inbound delivery is created when the outbound delivery for the distribution order is dispatched. For purchase orders, the inbound deliveries is created immediately when purchase order lines are released.
• 1 = Inbound deliveries are created using autostart job (MWS975). Inbound deliveries can at the earliest be created after the user has exited the order entry.

The field indicates whether variances created during manual receipt of distribution orders, are displayed in 'Stock Transaction. Display History' (MWS070).

Variances are logged in the stock transaction history file with transaction type 53.

Select the check box if variances should be displayed in (MWS070), even if 'Dsp all transaction' is off on (MWS070/P).

The field indicates whether variances created during manual receipt reporting of DOs are logged in the stock transaction history file with transaction type 53.

Select the check box if variances should be logged in the stock transaction history file with transaction type 53.

The field indicates whether packing processing is used and how.

Alternatives:

• 0 = Packing not used
• 1 = Manual simple packing
• 2 = Manual advanced packing
• 3 = Automatic advanced packing when picking list moved to packing location
• 4 = Automatic advanced packing when picking list is created.

Simple packing involves entering packages and weights only in 'Delivery. Connect Packages' (MWS423).

Advanced packing is when all picking lines are packed in one or several packages, with defaults according to the table in 'Item. Connect Packaging' (MMS053).

For alternative 3, the automatic advanced packing is done in 'Picking List. Report' (MWS420) when the dispatch order is assigned status 50.

Select the check box to enable cartonization.

To enable cartonization, an advanced packing reporting method must be selected, that is, alternative 2, 3, or 4 must be selected in field 240.

You can enable or disable cartonization manually on the delivery as long as the packaging status is lower than 30 in 'Delivery. Open Toolbox' (MWS410).

The field indicates whether different items can be packed in the same package for automatic advanced packing.

Default settings for packaging are defined in 'Item. Connect Packaging' (MMS053).

Alternatives:

• 0 = No
• 1 = Yes
• 2 = Yes, if they have the same commodity code. This alternative is valid for installations using bill of lading documents.

Cartonization is not affected by this parameter. Different item numbers are then always packed together unless the system is set up to start a new package when the item number changes. Such setup is made in 'Cartonization Selection Table. Open' (MWS185).

Select the check box to enable the packing of picking list lines that are soft allocated.

When the check box is selected, both hard allocated and soft allocated picking list lines are packed in automatic packing and can be packed during manual packing.

When the check box is not selected, only hard allocated picking list lines are packed in automatic packing and can be packed during manual packing.

The field indicates whether automatic package numbering is used continuously per delivery number.

Alternatives:

• 0 = Continuous package numbering is used. Numbers are retrieved from number series (type 08, series A in 'Number Series. Open' (CRS165)).
• 1 = Sequential package numbering is used. Numbering is restarted from 1 for every new delivery.
• 2 = Formatting rules in 'Package Number. Create Formatting ID' (MMS044) are used to retrieve package numbers. Each packaging in 'Packaging. Open' (MMS050) can have its own formatting rule, through the connected packaging type in 'Packaging Type. Open' (DRS080).

The field indicates whether packaging actions should be executed automatically as soon as a delivery is fully packed.

Alternatives:

• 0 = No, packaging actions are performed manually by option 39 in 'Delivery. Open Toolbox' (MWS410)
• 1 = Yes, packaging actions are performed automatically when fully packed
• 2 = Yes, packing actions are performed automatically when the delivery is confirmed as shipped.

The packaging actions are controlled by package type in 'Packaging Type. Open' (DRS080) and can consist of:

Adding a charge to the CO - Updating 'Packaging. Open Ledger' (MWS080).

The field indicates whether transactions are created in the stock transaction history file when an order line is moved between picking locations, packing locations, and docking locations.

Alternatives:

• 0 = No
• 1 = Yes, one transaction (from location)
• 2 = Yes, two transactions (from and to location).

This only applies to items that update the history file. See the Stock history field on 'Item. Connect Warehouse' (MMS002/G).

The field indicates whether an allocation check must be done before picking lists within a warehouse can be created for a delivery.

Alternatives:

• 0 = No
• 1 = Yes, all order lines with the same joint delivery code and warehouse must be fully allocated before picking lists can be created.
• 2 = Yes, all order lines within the same warehouse must be fully allocated before picking lists can be created.

The field indicates when a delivery number is closed. When a delivery number is closed, no more order lines and picking lists can be added, and remaining quantities not released for picking is transferred to another delivery.

Alternatives:

• 0 = Close when all delivery lines are delivered
• 1 = Close when all picking lists are delivered
• 2 = Close when the first picking list is created.

The field indicates if the delivery regrouping process is activated.

Select the check box to enable a controlled delivery regrouping process. All delivery lines and deliveries are created as preliminary at order entry with one order per delivery. Later process steps perform the delivery consolidation and transform these preliminary deliveries into firm.

If the check box is left blank, the delivery consolidation is performed as an integrated part of the order line entry. All delivery lines and deliveries are created as firm at order line entry and no delivery regrouping is performed.

For delivery regrouping to take place, this setting must be selected in 'Dispatch Policy. Open' (MWS010). If delivery regrouping is also selected for the consignee in 'Customer. Open' (CRS610) or 'Warehouse. Open' (MMS005), then the delivery regrouping process is automatically initiated.

Delivery regrouping can be manually changed in 'Customer Order. Open' (OIS100) and in 'Req/Distr Order. Open' (MMS100) at order entry. It can be displayed in 'Delivery. Open Toolbox' (MWS410) and via the view in 'Delivery. Open Line Toolbox' (MWS411).

The field indicates whether the next delivery, or the backorder delivery (BO-delivery), should be released for allocation.

Alternatives:

• 0 = Not released for allocation
• 1 = Released for allocation
• 2 = Not released for allocation, but also reset the original delivery to Not released if the field 'Closing point' = 1 in (MWS010), see parameter 300.

The field indicates whether the next delivery, or the backorder delivery (BO delivery), should be released for picking.

Alternatives:

• 0 = Not released for picking
• 1 = Released for picking
• 2 = Not released for picking, but also reset the original delivery to 0 = Not released for picking if the field 'Closing point' = 1 in (MWS010), parameter 300.

The field indicates under what conditions new deliveries are to be automatically connected to a shipment.

Alternatives:

• 0 = No automatic connection
• 1 = Automatic connection to next open shipment if transport capacity is sufficient
• 2 = Automatic connection to next open shipment. If transport capacity not is sufficient, no connection is made. If no open shipment exists, one is created automatically.
• 3 = Automatic connection to next open shipment regardless of transport capacity
• 4 = Automatic connection to next open shipment regardless of transport capacity. If no open shipment exists, one is created automatically.
• 5 = Automatic connection to next open shipment. If transport capacity not is sufficient, or no open shipment exists, a new shipment is created for the next possible departure time.
• 6 = Automatic connection to next open shipment regardless of transport capacity. If no open shipment exists, a new shipment is created for the next possible departure time.
• 7 = Automatic connection to next open shipment. If transport capacity not is sufficient, or no open shipment exists, a new shipment is created for the same departure time and with the best possible route/departure.
• 8 = Automatic connection to next open shipment regardless of transport capacity. If no open shipment exists, a new shipment is created for the same departure time and with the best possible route/departure.

Automatic connection only applies to route types with scheduled route departures (that is, route type 4-6), and to those that allow automatic connection to shipment (see 'Route. Open' (DRS005/F)).

Deliveries are only connected to shipments with matching place of loading, route/route departure, and departure date/time. Closed shipments, shipments that are past deadline, or shipments that are manually prevented from being used for automatic connection (see 'Shipment. Open Toolbox' (DRS100/E)) are not considered.

The field indicates if and when delivery documents are automatically selected for a delivery.

Alternatives:

• 0 = No documents automatically connected
• 1 = Yes, when the delivery is created
• 2 = Yes, when packing for the delivery starts
• 3 = Yes, when packing for the delivery ends
• 4 = Yes, when the delivery number is blocked for use during order line entry.

In all cases, you can still manually select or remove delivery documents in 'Delivery. Connect Delivery Documents' (MWS260).

The field indicates whether the delivery receipt confirmation should be used and how for a delivery. This confirmation enables tracking of deliveries and packages after they have been issued from the warehouse. Delivery receipt confirmation can be done by delivery number or the highest level of a SSCC number.

Alternatives:

• 0 = Delivery receipt confirmation not used
• 1 = Simplified delivery receipt confirmation used. Delivery receipt confirmation done on delivery head level
• 2 = Detailed delivery receipt confirmation used. Delivery receipt confirmation done on delivery line level and can be confirmed on different dates
• 3 = Same as 2, but mandatory to perform detailed receipt confirmation.

Alternative 3 is not selectable. It is only set if delivery is sent from an EU country to an EU country and the check box of parameter 'Tax Delivery Confirmation' (TDLC) in 'Country. Open' (CRS045) is activated.

The field indicates whether fixed document texts per customer in'Document Text. Open' (OIS035) is printed on picking lists and delivery notes for outbound deliveries.

Select the check box to print fixed document texts per customer.

This parameter is only relevant for documents initiated by customer orders.

The field indicates whether fixed item texts in (OIS035) is printed on picking lists and delivery notes for outbound deliveries.

Select the check box to print fixed item texts.

The field indicates whether fixed document texts in (OIS035) is printed on picking lists and delivery notes for outbound deliveries.

Select the check box to print fixed document texts.

This parameter is only valid when document 120 (picking list), or document 900 (delivery note) is stored in (OIS035).

The field indicates the number of days after the last delivery date that a delivery line is automatically held. This means that auto-allocation is prevented, and release for picking and reporting is only possible after releasing a hold flag on the delivery line 'Req/Distr Order. Open Lines' (MWS301/E).

This only applies to customer orders since only customer orders have a last delivery date.

A value of 999 in this field indicates that this function is disabled; that is, auto-allocation is performed regardless of the last delivery date on the customer order, and no hold is placed on the lines during release for pick and report.

The field indicates a program that is called when the delivery status is greater than 50 (issued from stock) and the packing status is greater than or equal to 30 (fully packed).

The intention is to enable you to design a program to add customer order charges based on the delivery totals and packing details. In addition, the program is to be called at the point in the dispatch flow where all required information is available.

The field indicates the status of a picking list that is automatically assigned when extended cross-docking is in use. This field is only valid for CO and outbound DO (the sending warehouse).

Alternatives:

• 00 = Not activated
• 40 = Ready for reporting
• 50 = All lines reported as moved to packing location
• 60 = All lines reported as moved to docking location
• 90 = All lines issued.

The field indicates how advanced cross-docking is to be performed. This field is only valid for inbound DO (receiving warehouse).

Alternatives:

• 0 = Not activated
• 1 = Line by line
• 2 = By delivery
• 3 = By package.

When method 1 is used, each line that is cross-docked is checked to see if advanced cross-dock should apply. It is not possible to copy packaging with this method of advanced cross-docking. When method 2 is used, the whole outbound delivery must be cross-docked from the same inbound delivery. The advanced cross-docking is not performed until the last delivery line is cross-docked.

When method 2 is used, the entire inbound delivery must be cross-docked to the same outbound delivery to be qualified for extended cross-docking. The extended cross-docking is performed when the last delivery line of the inbound delivery is cross-docked.

When method 3 is used, the entire inbound delivery package must be cross-docked to the same outbound delivery to be qualified for extended cross-docking. The extended cross-docking is performed when the last package line of the inbound delivery package is cross-docked.

Select the check box to copy packaging details from the inbound delivery to the outbound delivery when advanced cross-docking is performed. This field is only valid for CO and outbound DO (the sending warehouse).

This field only applies if the extended cross-docking check type (setting 430) is 2 (By delivery) or 3 (By package).

The field indicates if the ship-via address is retrieved automatically and how it is retrieved. The ship-via address is the address the goods are transported through before they arrive at the final address.

Alternatives:

• 0 = No ship-via address is retrieved automatically when the delivery is created. The ship-via address is maintained manually from (MWS410/F).
• 1 = The address is retrieved automatically from the consignee. Either the customer delivery address in 'Customer. Connect Addresses' (OIS002) or the customer in 'Customer. Open' (CRS610) is used to propose the ship-via address. Applies only to order category 3 (customer order).
• 2 = The address is retrieved automatically from the route. The place of unloading that is connected to the delivery 'Delivery. Open Toolbox' (MWS410) and route 'Route. Connect Unloading Places' (DRS021) is used to default the ship-via address.
• 3 = The address is retrieved automatically from the generic object control. The ship-via address in 'Available Object Ctrl Parameters. Open' (CMS016), 'Generic Object Control Table. Open' (CMS017) and 'Ship-via Address. Define' (MWS190) is used to propose the ship-via address.

Select the check box to enable pre-selection of freight accessorials when deliveries and delivery lines are created.

This setting must be enabled both on the dispatch policy and in (Settings - TPL Standard values) to enable retrieval of pre-selection of freight accessorials on the delivery and delivery line level.

To activate retrieval of the freight accessorial pre-selection on the shipment level, only the setting in (Settings - TPL Standard values) must be enabled.

The field indicates at which step in the dispatch flow that freight cost control is activated.

Alternatives:

• 0 = No control.
• 1 = Yes, a control is performed at release for allocation.
• 2 = Yes, a control is performed at release for picking
• 3 = Yes, a control is performed at issuing.

Alternative 1 activates a control at release for allocation, at release for picking and at issuing.

Alternative 2 activates a control at release for picking and at issuing.

Alternative 3 activates a control only at issuing.

If the freight cost setup has changed between the steps, this avoids any incorrect invoices being sent to customers and payments to forwarding agents and internal accounting.

If stopped at release for allocation, the delivery status is set to 00–'Not released for allocation'. If stopped at release for picking, the delivery status is set to 03–'CO stop'. For both scenarios, a stop code is stated on the delivery.

This parameter only defines the point in time when controls is performed, and not what to control. To set what to control, see 'Freight cost control' in the delivery terms.

The field indicates how the transportation service is retrieved. The transportation service is the specific service that the forwarder provides.

Alternatives:

• 0 = No transportation service is retrieved automatically when the delivery is created. The transportation service is maintained manually from'Delivery. Open Toolbox' (MWS410/F).
• 1 = The transportation service is retrieved automatically first from the route departure in 'Route. Connect Departures' (DRS006) and then from the route in 'Route. Open' (DRS005).

• 2 = The transportation service is retrieved automatically from the selection program 'Customer/Warehouse. Connect Tran Service' (DRS030) per customer (only for reference order category 3) or per delivering warehouse

• 3 = First according to value 1 (route departure then route), and then if no match is found according to value 2 (from selection program).
• 4 = First according to value 2 (from selection program), and then if no match is found according to value 1 (route departure then route).

Select the check box to start simple packing when the picking list is issued.

If you select this option, program 'Delivery. Connect Packages' (MWS423) is displayed with sorting order 3 when the picking list is issued.

You can only use this option if the packing reporting method is set to manual simple packing.

Select the check box to use a reporting version.

If you select the check box, one reporting version number is stored on the picking list headers and the packages created each time one or more picking lists are issued simultaneously. This enables you to display and print address labels for packages for each reporting version as a subset of the packages connected to the delivery.

You can only select this check box if the packing reporting method is manual simple packing.

The field indicates if a package is automatically created when simple packing is automatically started during picking list issue.

Alternatives:

• 0 = No package is created. At least one package must be created manually in 'Delivery. Connect Packages' (MWS423).
• 1 = One package is automatically created.

If the value is set to 1, then the 'Standard package to use' must be entered.

The field indicates if and when soft allocation is automatically transferred to hard allocation.

During certain events, soft allocated lines can automatically be transferred to hard allocation. When these events take place, the standard allocation rules select the balance identity and perform hard allocation if possible.

Alternatives:

• 00 = There is no automatic transfer from soft allocation to hard allocation.
• 10 = Transfer from soft allocation to hard allocation is done immediately when the allocation is done. This means that hard allocation is done immediately at allocation.
• 20 = Transfer from soft allocation to hard allocation when the picking list is generated.
• 30 = Transfer from soft allocation to hard allocation when the picking list is printed or downloaded to the M3 Warehouse Interface.

Note that the transfer from soft allocation to hard allocation can also be triggered manually by using option 38 in 'Allocation. Prepare Picking Release' (MWS413) or 'Picking List. Report' (MWS420).

The field indicates the ID of the number series used to generate chronological delivery note numbers when a delivery note is printed for a delivery with the current dispatch policy. The number is also printed per invoice line when invoicing the customer order.

The first time a delivery note is printed for a delivery, the functional program MMS480 (Print delivery note) generates a chronological delivery note number and stores it in the delivery header in the deliveries table, MHDISH, together with the date and time of creation in the time zone of the delivering warehouse.

If a delivery note has been printed with a chronological delivery note number for a delivery and this delivery note is later deleted, the chronological delivery note number saved in the delivery header is used when a new delivery note is created for the delivery, so that there are no gaps in the number series.

The optional number series must belong to number series type 'DT' (Chronological delivery note number) in 'Number Series. Open' (CRS165).

When the parameter 'Nbr ser per div' is activated in 'Settings - Deliveries' (CRS721) you only get a chronological delivery note number for the specific division. If there is no setup of a chronological delivery note number for the division, no chronological delivery note number is created for the delivery note.

The field indicates a user-defined reason code 'Transaction Reason. Open' (CRS103). The description for the reason code is printed on the delivery note.

To be able to enter a reason code for the dispatch policy, the chronological delivery note number series ID must be entered.

The field indicates the first user-defined field to use during delivery creation.

This field is used to consolidate or split delivery numbers as the user prefers. If the field is filled in, it is used as extra criteria together with system-defined values when deliveries are created.

The main purpose is to be used for delivery regrouping to further split a preliminary delivery into firm deliveries.

Other specific processes that require specific values in delivery consolidation field 1 or 2:

Prepayment – Value: OBTEPY

Internal Sales – Value: OAICTR

Pick-up delivery – Value: &PUDL

The field indicates the second user-defined field to use during delivery creation.

This field is used to consolidate or split delivery numbers as the user prefers. If the field is filled in, it is used as extra criteria together with system-defined values when deliveries are created.

The main purpose is to be used for delivery regrouping to further split a preliminary delivery into firm deliveries.

Other specific processes that require specific values in delivery consolidation field 1 or 2:

Prepayment – Value: OBTEPY

Internal Sales – Value: OAICTR

Pick-up delivery – Value: &PUDL

Select the check box to activate the transfer of a fully allocated package in stock to a package for a specific delivery.

When this check box is selected, the system tries to transfer a hard-allocated package in stock to a package for a specific delivery in the following cases:

When the packing reporting method is 4 and the picking list is printed.

When the packing reporting method is 2, 3 or 4 and option 22 (Autopack) is used on 'Picking List. Report' (MWS420/B).

Select the check box to enable package-based receipt.

If this check box is selected, you can perform receipt when working with packages in stock and still keep the package structure and content from the supplying order. The external package information is then transferred to become in-house package information.

Package-based receipt is done for each shipment, delivery, or package number for a distribution order. Receipt can be performed from 'Goods Receipt DO/RO. Report' (MWS440) or from API MHS850MI.

Package-based receipt is done for each delivery note number and package number for a purchase order. Receipt can be performed from 'Supplier Delivery Note. Open' (PPS360) or from API PPS360MI.

Select the check box to create a stock count task in 'Physical Inventory. Perform' (MMS300) when sending a pick message in 'Order Init Stock Msg. Manage' (MHS850) or using API MHS850MI. The stock count task is created if the on-hand balance is equal to zero when pick reporting is done.

The following MI transactions are included in the create physical inventory process:

AddCOPick Report CO

AddMOPick Report MO

AddDOPick Report DO

AddROPiCK Report RO

AddReplPick Report replenishment order (TTYP 92)

AddPickviaRepNo Report via reporting number

AddPickviaPack Report full package (can contain more than one item)

AddPickviaPacStk Report soft allocated package

This check box must be selected both for the location (MMS010) and for the dispatch policy (I).

The field indicates if and how the delivery value check should be triggered. A triggered delivery value check performs an evaluation if the payer of the delivery is solvent, to let the delivery be issue reported. The result of the delivery value check is shown via the issue reporting status of the delivery. The issue reporting status is validated at issue reporting to only allow deliveries that have passed the delivery value check or have been manually approved for issue reporting. Deliveries without a performed delivery value check or a failed delivery value check is prevented from being issue reported.

Alternatives:

• 0 = Not used
• 1 = Only manually
• 2 = Manually and automatically when goods are on dock location for the first time.

The delivery value check functionality is only valid for deliveries with reference order category 3 (customer order).

The field indicates how the delivery value is calculated.

Alternatives:

• 0 = Not used
• 1 = Value calculated per line as sales price - line discounts, multiplied with transaction quantity.

The delivery value check functionality is only valid for deliveries of reference order category 3 (customer order).

The field indicates if a pick-up delivery should be created and which address information that should be used as the end destination for the pick-up delivery. Note that pick-up deliveries for transportation orders are used for transportation planning purposes regarding the empty vehicle leaving the warehouse. A pick-up delivery only incorporates the planning of the first part of the transportation from the M3 BE warehouse to either the departure address or the delivery address entered on the transportation order.

Alternatives:

• 0 = No creation of pick-up delivery
• 1 = Yes, use departure address information as end destination for pick-up delivery
• 2 = Yes, use delivery address information as end destination for pick-up delivery.

Select the check box to enable propagation of delivery changes to order lines.

When propagation is activated and a change is made to a delivery, all order lines connected to the delivery are updated with the same values as the ones set on the delivery.

Propagation is limited to customer orders. Only departure date, departure time, and final delivery terms are propagated. Propagation is only performed while a delivery is open (the delivery status is below 50).

The change of departure date and time on the connected order lines updates the planned date and time as well as the confirmed delivery date and time.

A change of departure date or time on a shipment is always propagated to the deliveries connected to it. This is not dependent on the propagation parameter, but when the propagation parameter is activated on the dispatch policies on the connected deliveries, the changed departure date or time on the shipment is propagated all the way to all the order lines connected to the deliveries.

If the final delivery terms on a delivery are changed and if that leads to the delivery terms on all of the order lines of an order are updated through propagation, the delivery terms on the order header are also updated with the same value.

The field indicates whether it is permitted to receive more than what is registered to be sent on a distribution order (DO) line.

Alternatives:

• 0 = No, you cannot receive more items than what is registered to be sent on the DO line or to receive a different item.
• 1 = Yes, you can receive more than what is registered to be sent on the DO line. The quantity difference must be within the tolerance defined in parameter 610. Observe that if the tolerance percentage is 0, no limitation applies. You cannot receive other items than the ones registered in the DO.
• 2 = Yes, you can receive more than what is registered to be sent on the DO line, if that quantity is within the tolerance defined in parameter 610. You can also receive items that were not in the DO.

The field indicates the percentage variance tolerated for the distribution over receipt and is considered if the parameter 600 (‘Allow distribution over receipt’) in (MWS010) is set to 1 or 2.

Two decimal places are used.

This percentage is used for checking if the value is reasonable when registering the distribution order receipt.

If the value of the quantity received is higher than the entered percentage of the dispatched quantity, the receipt is not allowed.

The field indicates if approval from legal authorities is necessary for delivery. If activated, the delivery note is not printable before approval has been received.

Alternatives:

• 0 = Not used
• 1 = Mandatory approval - digital only
• 2 = Mandatory approval, digital or manual.

Alternative 0 means that no approval is required.

Alternative 1 means that digital approval from a legal government portal should be received. This alternative is suitable for a BOD-integrated solution when the progress of the approval is managed by the integration to Localization Services Platform (LSP).

Alternative 2 means that approval from a legal government portal must be received before the delivery note can be printed. The approval can be received digitally or be performed manually.

The field indicates the ID of the number series used to generate a freight document alias ID when the non-sales transit document is created.

A new freight document alias ID is retrieved every time a new non-sales transit document is created per delivery. The number series ID must belong to number series type DC (Non-sales transit document number).

The field indicates which variant of the non-sales transit document that should be used for a delivery with the specific dispatch policy.

Alternative 0 means that some detailed values but no rates are retrieved when printing the non-sales transit document.

Alternative 1 means that information on the non-sales transit document is retrieved from the delivery that origins from a distribution order.

Alternative 2 means that information on the non-sales transit document is retrieved from the delivery that is created for the requisition order that manage goods transported back to the supplier.

Alternative 3 means that information on the non-sales transit document is retrieved from the delivery that is created for the requisition order that manage goods transported to the supplier for subcontracting operations.

Alternative 4 means that information on the non-sales transit document is retrieved from the delivery that is created for the replenishment order that manage goods to be moved to supplier location in the maintenance repair process.