Table of Contents
Mehr zu diesem Produkt auf sievers-group.com

Automations

Automatic Stock Transfer Posting

Transfers can be posted automatically in SIEVERS WMS. This can be useful, for example, if inventory has to be regularly sorted out to another location because it is broken, for example. The Automatic Stock Transfer Posting also works for outside storage inventory.

In the SIEVERS WMS setup, set up the numbering Automatic Item Transfer Jnl. Template Name and Automatic Item Transfer Jnl. Batch Name.

Also make sure that you have filled in the Inventory Posting Setup for the Location Code.

Then open the storage place card for the storage place from which you want to make an automatic transfer. Here you will find the fields

  • Transfer Location Code
  • Transfer Storage Place Code.

Here you enter the destination location and place for the transfers. Ideally, this is a place or location that all employees know as a drop-off point for sorting out, for example. If the storage location is a SIEVERS WMS-managed storage location, you must also enter a storage place. If this is not the case, the storage place field remains empty. The location entered here must be different from the location of the storage place to which the current storage place card belongs. The reason for this is to ensure a clean separation of inventories so that broken items are not sold by mistake.

If an item transfer or an internal transport is now posted from a storage place to the transfer location or place, the system automatically creates a transfer posting in the corresponding item transfer journal.

Warehouse Shipment Automation

This automation is used to automatically create warehouse shipments or assign source documents to existing warehouse shipments according to certain rules. The Whse. Ship. Automation page is used as the configuration table. Here you can not only set the rules in question, but also access the log and start processing the automation.

Ideally, you have set up the warehouse shipment automation as a job queue entry. If the processing is to be executed automatically via job queue, please use the CodeUnit 71310347 for the AppSource onPrem and SaaS versions and 77347 for PTE.

The setup rows of the Whse. Ship. Automation are executed in the order in which they are sorted. The following setup columns are available on the page:

When a warehouse shipment is created via the automation, the purity flags from the setup line are transferred to the warehouse shipment header. These flags then prevent source documents of other customers, vendors, orders, or shipping addresses from being added to this warehouse shipment, regardless of whether this happens manually or via the automation.

  • Sorting: The automation rows are processed in this order when the automation is started
  • Deactivated: When this field is checked, the automation row is not applied
  • Location Code: Specifies that this automation is only applied to orders at this warehouse location
  • Description: Describes the automation row
  • Priority: Defines a priority for all warehouse shipments created with this setup line. If you do not enter anything here or enter a 0, the priority will be formed regularly according to weekday + priority value and shipping agent + priority value.
  • Source Type Filter: Defines the type of source document to which this automation line is applied.
  • Customer Clean: Specifies that all subsequent orders must have the same customers as the first order. This is how single-customer warehouse shipments are formed.
  • Customer No. Filter: Specifies that this automation line only applies to a specific customer. If nothing is entered here, the line is applied to all customers.
  • Vendor Clean: Specifies that all subsequent orders must have the same vendors as the first order. This is how single-vendor warehouse shipments vendors are formed.
  • Venor No. Filter: Specifies that this automation line only applies to a specific vendor. If nothing is entered here, the line is applied to all vendor.
  • Order Specific WS: Specifies that a separate warehouse shipment must be created for each order.
  • By Shipping Address: Specifies that all source documents in the warehouse shipment must have the same shipping address.
  • Shipping Agent Code Filter: Specifies that all warehouse shipments created have this shipping agent. Please note that the shipping agent also serves as a filter when adding new orders to warehouse shipments
  • Lead Time: Specifies how many working days before the delivery date a warehouse shipment can be created. If a 10 is entered here, a warehouse shipment can be created 10 days before the loading date. See also Warehouse Shipment Dates.
  • Deadline: Specifies the number of days before the first loading date of the warehouse shipment that no more orders are assigned. This can be useful if it takes one or more days from the creation of the warehouse shipment until loading is possible. If no base calendar is entered, calendar days apply.
  • Grace Period Shipment Date: Tolerance period around the first loading date in which various orders can be grouped into a warehouse shipment. For more information, see Warehouse Shipment Dates.
  • Loading Day: Specifies the loading day for each warehouse shipment created with this setup line. The system tries to find a date in the current week before the shipment date. If this is not possible, the next possible date in the following week is set as the loading date.
  • Update Loading Date: If you have not specified a loading day in the previous field, use this radio button to activate the automatic update of the loading date based on the earliest loading date from the source documents.

Outbound Stock Post Automation

This automatically creates Outbound Stock Post documents for orders X days before the warehouse shipment loading date. The automation is executed by a job queue or the button Start Processing on the Outbound Stock Post Automation page. This is where you can set up lines that are passed through when the automation is executed. The table has the following fields:

  • Sorting: The automation lines are procCessed in this order when the automation is started
  • Deactivated: If this field activated, the automation line is not applied
  • Location Code: Determines that this automation will only be applied to orders in this location
  • Description: Describes the automation line
  • Source Document: Defines the source document type this automation line will be applied on. Right now there are only warehouse shipments possible
  • Shipping Agent Code Filter: Determines that this automation will only be applied to orders of this shipping agent
  • Lead Time: Determines the time in working days how far before the delivery date a Outbound Stock Post may be created. If a 10 is entered here, a Outbound Stock Post may be created 10 days before the loading date. The working days are based on the calendar from the location.
  • Reservation Order: Determines the order in which the documents are sorted to create the Outbound Stock Posts
  • Variable for Auto. Creation Filter: Here you can determine a variable as filter for the automatic Outbound Stock Post. You can find the corresponding counterpart of the field in the warehouse shipment planning. The optional field is called Variable for Aut. creation of stock doc..
  • Delete Protocol after days: Specifies after how many days the protocol should be deleted. Can be disabled with 0

After the execution is started via the button or a job, all source documents with warehouse shipments that match the filter criteria are searched for. The filter criteria include

  • Order type
  • Shipping agent
  • Variable for Aut. Creation of Stock Doc.

After that, a check is made to see if the lead time of, for example, three days before the loading date has been reached.
If this is the case, Outbound Stock Post documents and shipping orders are now created on the basis of the source documents and sorted by delivery date and priority of the order. If the system finds that a stock document is empty, it is automatically deleted.

Hinweis

The runtimes of the Outbound Stock Post automation can differ greatly. Sometimes the processing is quickly finished and sometimes it takes a long time. This is often because many new stock documents have to be created and these are already processed during the next run. In addition, a cache is filled during processing, which can be retrieved again as needed during later runs. This can also speed up processing.

Automatic Picking Team Determination

In both manual and automatic goods issue processing, a picking team must be found and assigned during the process. Sometimes this does not work right away, for example, because team master data is not set up correctly. This may not be noticed immediately, especially in automated processes. To avoid this, you can set up a job queue entry with the code unit SNCL Pick Team Determ Mgt. This automatically searches for picking documents without a picking team and attempts to assign a team to them. The code unit has the following IDs:

  • SaaS/OnPrem: 70294248
  • PTE: 77248
Hinweis

If you have any questions about this, please contact your SIEVERS partner.

Automatic Picking Documents

With this automation, created picking documents can be released automatically. This reduces the manual effort involved in processing warehouse shipments. The automation mainly runs via three setups:

The release lead time indicates how many days before the loading date the picking document is automatically released. The release lead time in the order types always has the highest priority. If the current work date falls within the release lead time, the appropriate picking documents for the corresponding team are released via job queue entries. The automatic release can also be executed manually via the Picking -> Automatic Release action on the team.

In the teams themselves, you can also start the automatic release manually via the action menu. Automatically released picking documents are logged.

Picking Release Automation Protocol

This page displays a log of the automatically released picking documents. If an error occurs, it will be written in the Error Message field. An error does not necessarily mean that the release run is cancelled completely. For example, if a blocked inventory is found during the release, it will only be mentioned in the error message and skipped.

  • Entry No.
  • Location Code
  • Source No.
  • Source Subtype
  • Source Type
  • Warehouse Shipment No.
  • Outbound Stock Post No.
  • Picking Document No.
  • Picking Team
  • Order Type
  • Shipping Agent Code
  • Successful
  • Error exist
  • Error Message

Assembly-to-Order (ATO) Automations

In the assembly-to-order (ATO) process, SIEVERS WMS runs several automations that enable packed and shipped assembled items without manual intervention:

  • Automatic SSCC creation: As soon as all attributes on the load carrier are complete (depth, width, height, and weight) and the status 7 - Packed is reached, an SSCC is automatically created. If dimensions or weight are missing, no automatic SSCC is created.
  • Packaging lines and packaging process: The related packaging lines are automatically created and the packaging process is fully supplied.
  • Warehouse shipment planning update: The warehouse shipment planning is automatically updated after processing.
  • Automatic label printing: Via the setup field Auto. Print LC on Assembly in the Assembly tab of the SIEVERS WMS Setup, a label for PTU and/or SSCC can be printed automatically after successful processing.
  • Reservation entry linkage: When posting an inbound warehouse entry, the newly created inventory is automatically linked to the corresponding reservation entry. This ensures the reserved stock remains uniquely assigned to the sales order so that subsequent WMS processes (e.g. warehouse shipment, stock posting) can be executed correctly and without manual intervention.
  • Posting compatibility at WMS locations: The fixed BC standard link between the assembly order and the sales order (table "ATO Link") is internally and temporarily removed at WMS-managed locations before posting to enable the inbound warehouse entry, and automatically restored afterwards if remaining quantities exist. For warehouse and shipping staff, this process is fully transparent: WMS processes for assembly-to-order items now run without errors and without requiring any manual intervention.

If errors occur during processing, the entire transaction is rolled back and the link between the assembly order and the sales order is fully preserved.