openwms / org.openwms.wms.receiving.lib Goto Github PK

View Code? Open in Web Editor NEW

2.0 2.0 2.0 30.09 MB

WMS Receicing Service to handle announcements or expected receipts

Home Page: https://openwms.github.io/org.openwms.wms.receiving.lib/

License: Apache License 2.0

Java 100.00%

asn receipts receiving wms microservices openwms spring-boot spring-cloud

org.openwms.wms.receiving.lib's Introduction

Purpose

The purpose of the Receiving service is to handle goods receipts. It offers an API to create incoming orders, so called Receiving Orders (expected receipts). This kind of receipts are announced before the actual goods are received. Blind receipts are supported as well. Those don't require any announcements and allow to capture goods that are not expected to receive.

Resources

Find further Documentation on Microservice Website

Build

The service can be built and started locally without any other services.

Build the code:

$ ./mvnw package

org.openwms.wms.receiving.lib's People

Contributors

Stargazers

Watchers

Forkers

hitrovzs

org.openwms.wms.receiving.lib's Issues

Do not only take the SKU into account but also the Label of the Product and the UomRelation

Remove the strict usage of Piece.ZERO

Upgrade to Dozer 6.5.x

ReceivingOrder numbers shall allow to configure a prefix

Verify that all RO details and ROP details are returned via API

Introduce UOM JSR-385 library to support various units

In capturing a PU must created asynchronously

where is 'wms-inventory'

I can't find 'wms-inventory' service source code, where can find??

Get rid of Dozer and use MapStruct

Migrate to SpringBoot 2.6.x and Java 17

Upgrade to Java 21

Decouple Feign specific PackagingUnitApi

The PackagingUnitApi is part of a SPI package, what means it can be implemented and access remote (or local) services to achieve the required functionality. In case of thePackagingUnitApi interface specification that is a Feign client, means it is directly coupled to a remote service with name wms-inventory. This shall be avoided for two reasons:

The service may not run in a distributed environment
Even in a distributed environment, the service may not be available

origins from #22

The ReceivingOrderPosition shall have a details field to store arbitrary values

Add feature to manage suppliers: Supplier setup

Use the foreignPKey as pKey if given

Allow single ReceivingOrderPositions to be updated

Demo data not correctly loaded with DISTRIBUTED and DEMO profile

ReceivingOrderPosition shall offer arbitrary details

The quantityExpected shall be initialized

Enable identity management

Add foreignPid and label to Product

Offer an API for Blind Receipts

Migrate to SpringBoot 2.7.0

Overbooking shall be configurable per Product not service wide

Backend shall create and assign an orderId if not provided

Migrate to SpringBoot 2.3.7

Allow to set the order state to PROCESSED manually

Useful for manual operations where the operator checks incoming goods and accepts the whole delivery

Decouple Feign specific TransportUnitApi

The TransportUnitApi is part of a SPI package, what means it can be implemented and access remote (or local) services to achieve the required functionality. In case of the TransportUnitApi interface specification that is a Feign client, means it is directly coupled to a remote service with name wms-inventory. This shall be avoided for two reasons:

The service may not run in a distributed environment
Even in a distributed environment, the service may not be available
origins from #22