The whole truth about the integration

Beas-WMS Synergy

Beas offer a significant value proved on different industries across last 20 years and the same happens with Produmex WMS in its domain but an endless potential is only realized when they work together.

In the last 3 years we have achieved market sectors and company sizes that both solutions couldn’t achieve separately and that’s why our company plans involve strengthening this alliance.

What it is and what is not (and what it will never be)

Clarity, honesty and transparency have been always pillars in our relationship with partners, it will not be different in this matter, and certainly not regarding this article.

Both solutions (Beas and WMS) were born separately, with a different data structure and different concepts about some common ideas, so certainly Beas and WMS do not have an end-to-end integration and there are topics that will never be included on the scope.
Laying on the same fact, as they were conceived as two standalone solutions, they have overlapping solutions for the same common processes.

The two previous statements contain certain pitfalls that an unsuspecting implementer could fall into. Therefore, I suggest that those who see themselves reflected in this statement read the following article: Beas-WMS: Five Keys to unlock the right Mindset of the Beas-WMS implementation (zendesk.com)

CONDITIONED FUNCTIONALITIES

To establish common ground between both solutions, we have defined a shared framework where Beas and WMS coexist, which involves some compromises, this list details two different casuistries:

• Out of the Scope: Native WMS features which are not compatible with Beas production processes. And vice versa, Beas native functionalities which are not compatible with WMS logistics processes.
• Functionalities integrated but their visibility is contingent upon the use of the right solution and configuration. 
  Understanding this approach not only clarifies project boundaries but also ensures that users have a clear pathway to accessing all relevant functionalities effectively.
  The conditional functionalities discussed in the article are inherent to the standard Beas-WMS integration; however, both solutions are highly customizable, providing ample alternatives to tailor the integration conditions to the client's specific operational needs, take a look of them at the "alternative solutions" last section.

Out of the scope (2024)             

Transactions listed below will end up in error:

• WMS Has PMX Serial Number setting. PMX Serial numbers are stored and processed independently of SBO (and Beas) therefore there is a lack of information when processing transactions with PMX Serial numbers.
  
• WMS Second Inventory UoM. Information configured on WMS, Beas currently don’t read this data.

• WMS Catch Weight. Beas production flows do not query for the weight of a produced item.

• WMS Production flow and SAP Production flow. Assuming the reason for the integration is to take advantage of the Beas production capabilities, which overlap SBO production ones, make no sense to support them.
• WMS Item lockings: stock allocation function, minimum reserved stock for customers and Lock waves by users. Item locking is the only WMS locking type which Beas do not support.
  
• Beas external Operations. Bellow Operations are currently not supported on WMS Terminal:
  - Deliver provisions to the external supplier.
  - Once subcontracted product is finished, receipt the goods back on the main warehouse.
  

However, this is included on the roadmap on both products WMS supporting Beas External Operations stock moves (notion.site)

• Beas Allocation, based on the same principle as the previous point, where logistics transactions for Beas external operations are managed under the WMS Terminal umbrella, logistics transactions within Beas are excluded from the scope, as all warehouse movements are intended to be processed through the WMS terminal.
• WMS Ose elements (printers, docks, movable locations…) Exception: Production Lines, WMS Zones at Beas Issue, WMS Bins at production reception and production issue.
  Beas has its own logistics data structure where there are no organizational elements objects such as they exist on WMS, as a consequence most of them do not exist in production.
  The exceptions are WMS Production lines which can be found on the Work Order Positions and Beas resources, the possibility to consume the components in production processes which are hosted only in certain WMS bins or WMS Zones and of course the possibility to receive on a specific bin the result of our production operations.
  
• Only Production transactions are supported in Beas, the inventory transactions are supported via WMS.
  • Incoming goods
  • goods issues
  • goods receipt
  • Stock transfer
  • Inventory Counting
  • Beas Batch split not supported.
  • Beas Batch transfer not supported.
  • Terminal apps related to stock transactions, not supported.
    WMS is compatible with the standard SBO documents as GRPO, Issues, receipts, stock transfers (do not compatible with batch transfer, batch split and Beas terminal apps) and has its own inventory counting methods so it is still possible to work with them via SBO Desktop or WMS Terminal.

Integrated but conditioned

In the next step we will review transactions which can be completed but where certain data is not accessible from the not native software.

• Traceability Report: Full traceability guaranteed on the integration on different data sources:

-WMS Traceability report shows movements, WMS Quality Status modifications, stock status, batch attributes and inventory transactions.

-Beas tracing report contains components/materials/assemblies used in production of the parent or finished/semifinished goods using certain batch/Serial Number on the parent level.

• WMS Quality Status. Except: reception from production and property “can’t be used in production”

WMS Quality Status is not registered on Beas transactions, however the “Default Quality Status for Production” defined in WMS Item master data will be used when processing production receives in Beas.

If the default quality status of the WMS master data is not set, the global parameter bellow will be used:

Other useful exception is that only the stock which has activated the WMS property “can be used in production” can be issued in production.

• WMS Reasons are only requested from WMS Terminal and when locations suggestions are configured Location Suggestions [] (produmex.name).
• Beas Version Control. Exception: WMS reception flow.
  WMS Terminal asks for the received Version of the product (if Version control is configured on Beas master data), at any other process WMS do not consider Version control on logistics operations.
  

• WMS Master SSCC: Beas currently supports SSCC’s but the data structure is not ready to store Master SSCC’s at production.
  

  However Master SSCC’s can be used as in the standard before or after production.

• WMS Batch associated data accessibility Beas. Except: Production reception.
  
  

  -There is a customization available to receipt finished products and store its WMS batch attribute Beas-WMS: Receive from production an item with WMS Batch Attributes – Boyum Help Center (boyum-it.com)

  -Another customization allows to capture the BBD on Beas production receipts (terminal or desktop) and stores them on WMS PMX_ITRI so they are available for outbound processes.

  In any other case Beas ignores the batch associated data (second batch, batch attributes, or Supplier Pallet Number). Keep tunned to our Boyum Help Center (boyum-it.com) if you wishing to learn more about this business case.

• Best Before Dates
  When this field is checked in WMS master data, it is mandatory to provide a Best before date in any stock transaction. Beas supports this field calculating a date based on the SAP Batches and Serial shelf life. For a non-Batch/Serial item the date is calculated based on WMS Shelf-life Delivery available in the Sales tab.
• Restrictions on Picking for production to pick production order line components with certain characteristics: batch attributes. Exception: valid BBD for BoM components.

Beas allows to define the logic under the system will validate if a component of the BoM has a valid BBD. 3.1. Bill of Materials [] (produmex.name)

On the other side pick list proposals and pick lists on Beas-WMS integration are created via services from Beas Worder documents and not the standard SBO Production Order therefore the selection of batches/batch attributes to pick for production can’t be set.

Selecting specific batches for production orders can be done via Beas reservation screen.

Alternative Solutions

There are solutions provided for all the conditional functionalities listed above, and we have developed ad hoc exceptions for cases where, despite being outside the initial scope, we believe they add significant value to the integration. However, if there are still business requirements that fall outside the standard product, both Beas and WMS offer robust tools for customizing specific needs. Stay tuned to our Boyum community, where we will publish customizations applied in other projects, and take a look at the following alternatives, as they might offer the adjustments you are looking for in your process:

• WMS Hookscripts are empty pieces of code called, or executed, from various points in Produmex, they allow users to perform customs actions (which may involve Beas data) after a certain SBO/WMS event happens.
• WMS .Cs Scripts can be called from Beas scripts to perform WMS Actions
• WMS Notification Listener is a service running each minute which allows you to modify SBO  standard or WMS documents once they are adjusted. Notification Listener Tool [] (produmex.name) This option will be enhanced after the release of the Create a task trigger on WMS Notification Listener (notion.site) of the WMS Roadmap 2024.
• Beas Service Layer can create own objects to perform any kind of Beas/SBO/WMS actions as the standard UE_PRODUMEX object for picklist creation.
• Web API allows to send web requests for performing WMS actions from Beas screens (included on Roadmap 2024) WMS Web API: Expose WMS methods to be consumed (notion.site)
• Use extra criteria (Beas Version or manufacturing date) as criteria to allocate stock in WMS pick list proposals (included on Roadmap 2024) Create a Function to Allocate Stock on Pick List Proposals (notion.site)

• Beas Web Apps can be customized based on the standard adding extra logics which could involve WMS data. https://help.beascloud.com/beas202406/index.html?web_apps_version_2_1.htm

  
  

Benefits from the article

• Enhanced Problem Mitigation: Increased information availability helps in anticipating and mitigating future issues more effectively.
• Strengthened Brand Trust and Sales Opportunities: Empowering partners with knowledge and real-world solutions boosts trust in our brand and enhances selling opportunities.
• Efficient Implementation: Understanding the scope and conditioned functionalities supports simultaneous implementation or blueprinting, reducing implementation time and errors.
  

  
  Stay tuned during the last semester of 2024, cause purchasing Beas and WMS licenses simultaneously may offer NEW benefits in both cost and implementation. Discover them by following Boyum IT official channels together with new E-learning content, onboarding programs for partners adopting our solutions, customization training for partners and game changing features in upcoming versions…