-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transforming HU in Handling Unit Editor #181
Comments
I would suggest to create one action for each use case. |
As spoken. From a User perspective, I would propose to just have 1 action for these use cases - "transform". The user just wants to change the existing config and should not have to think in advance which action she/ he hast to choose to achieve nearly the same thing bit with slight differences. Talking about Material Receipt HU Editor here and only about the Use Cases needed there for Transformation. They can be valid for general Handling Unit Editor but are not focussing on those at the moment. Use Case 1 Use Case 2 Use Case 3 |
…nation.setIsHUPlanningReceiptOwnerPM
…HU_PI_Item_Product
…nient factory methods
…d fix when validating if ctx matches, use the same algorithm that it's used by "@CacheCtx"
…eCtx" (cherry picked from commit e10dfef) this fix was originally made in metasfresh/metasfresh-webui-api-legacy#181 ModelCacheService.isExpired fix FRESH-1531 #1036 Harmonize BL for ModelCacheService.IsExpired
highlights: * one place to create the class instance: ProcessInfo.DocumentFieldAsCalloutField * JavaProcess.currentInstance() * more refactoring required for webui
also reordered fields & methods FRESH-1504 metasfresh/metasfresh#181 Transforming HU in Handling Unit Editor
FRESH-1504 #181 Transforming HU in Handling Unit Editor
FRESH-1504 metasfresh/metasfresh-webui-api-legacy#181 Transforming HU in Handling Unit Editor
Also add a bit of javadoc and rearrange methods a bit FRESH-1504 #181 Transforming HU in Handling Unit Editor
FRESH-1504 metasfresh/metasfresh-webui-api-legacy#181 Transforming HU in Handling Unit Editor
FRESH-1504 #181 Transforming HU in Handling Unit Editor
FRESH-1504 metasfresh/metasfresh-webui-api-legacy#181 Transforming HU in Handling Unit Editor
FRESH-1504 #181 Transforming HU in Handling Unit Editor
FRESH-1504 #181 Transforming HU in Handling Unit Editor
FRESH-1504 #181 Transforming HU in Handling Unit Editor
FRESH-1504 metasfresh/metasfresh-webui-api-legacy#181 Transforming HU in Handling Unit Editor
also minor avadoc FRESH-1504 metasfresh/metasfresh-webui-api-legacy#181 Transforming HU in Handling Unit Editor
FRESH-1504 #181 Transforming HU in Handling Unit Editor
* unless existing-TU is aggregate, the CU is only "attached" to it * also fixed a number of deprecation warnings FRESH-1504 metasfresh/metasfresh-webui-api-legacy#181 Transforming HU in Handling Unit Editor FRESH-1682 metasfresh/metasfresh-webui-api-legacy#238 Attributes propagated on everything in TU
FRESH-1504 #181 Transforming HU in Handling Unit Editor
* also renamed facade methods, because it's really not splitting all the time metasfresh/metasfresh-webui-api-legacy#181 FRESH-1504 Transforming HU in Handling Unit Editor
#181 FRESH-1504 Transforming HU in Handling Unit Editor
FRESH-1504 metasfresh/metasfresh-webui-api-legacy#181 Transforming HU in Handling Unit Editor
* removed product and cuom params, because a CU has only one storage and product and uom can therefore be found in that single storage * move javadoc from webui to the actual methods that do the magic FRESH-1504 metasfresh/metasfresh-webui-api-legacy#181 Transforming HU in Handling Unit Editor
* removed product and cuom params, because a CU has only one storage and product and uom can therefore be found in that single storage * move javadoc from webui to the actual methods that do the magic FRESH-1504 #181 Transforming HU in Handling Unit Editor
FRESH-1504 #181 Transforming HU in Handling Unit Editor
FRESH-1504 metasfresh/metasfresh-webui-api-legacy#181 Transforming HU in Handling Unit Editor
unit tests are green, but need to add more FRESH-1504 metasfresh/metasfresh-webui-api-legacy#181 Transforming HU in Handling Unit Editor
FRESH-1504 metasfresh/metasfresh-webui-api-legacy#181 Transforming HU in Handling Unit Editor
Is this a bug or feature request?
Feature Request.
What is the current behavior?
No Functionality to Transform existing Handling Units into other Handling Unit/ Packing Instruction Combinations in handling Unit Editor.
Which are the steps to reproduce?
Open Handling Unit Editor via Material Receipt. The existing Handling Unit opened cannot be transformed into other combinations.
What is the expected or desired behavior?
The old functionalities of split and merge shall be combined in one action that can be called via Action menu and takes one selected HU and additional variable action values (existing HU, new HU, new Packing Instruction, Qty to transfer) as Parameter. The Action always reduces the source HU by the given qty and transfers to the target HU (new or existing) with the given qty.
Possible action parms:
a) own Packaging material? If no then it's from the vendor and will be included in the Material receipt.
b) Existing HU (List of HU combinations of needed Level TU, LU depending on source Level)
c) new Packaging Material (List of valid Packaging Material for the given target Level)
d) The quantity that shall be transferred from source to target.
The text was updated successfully, but these errors were encountered: