Skip to content
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.

Sign up for GitHub

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

Jump to bottom

HU "Herkunft" HU_Attribute is not propagated from LU to VHU #1194

Closed
metas-ts opened this issue Mar 24, 2017 · 1 comment
Closed

HU "Herkunft" HU_Attribute is not propagated from LU to VHU #1194

metas-ts opened this issue Mar 24, 2017 · 1 comment
Assignees
@metas-lc
Labels
type:bug

Comments

@metas-ts
Copy link
Member

Is this a bug or feature request?

Bug

What is the current behavior?

If you receive goods lying directly on a palette and change the "Herkunft" attribute, then that change is not propagated to the underlying VHU

Which are the steps to reproduce?

  • make a purchase order with a product, with a certain Herkunft attribute instance, but no TU
  • receive the product on a pallete (i.e. don't insert a TU now)
    • and ofc change the Herkunft in the HU edotor

Note: in this case, the HU is an aggregate one, i.e. there is just

  • LU (M_HU, "Pallet")
    • M_HU_Item with type= HA
      • VHU with the actual product

=> to verify the bug, find the VHU in the HU (non-POS) window, check its attributes verify that its Herkunft attribute still has the wrong value

What is the expected or desired behavior?

if you change an attribute like Herkunft in the HU editor, then that change should be propagated downwards
metas-ts added a commit that referenced this issue Mar 28, 2017
@metas-ts
Fix CU-on-LU scenarios: don't try include HA in the play
7f2184a 
* HUJoinBL: don't join a TU to a parent's HA item, because the HA item
is special (e.g. can represent just one type of TU), and one can't just
attach random stuff to it.
* TUProducerDestination: detect the CU-on-LU situation and avoid
creating an aggregate HU. This is now also verifies in
LUTUProducerDestinationLoadTest
* LUTUConfigurationEditorModel: if the current lutu-config already
contains some sort of virtualPI key, then don't add another one. It's
confusing to the user
* rest: minor changes

FRESH-1794 #1194 HU "Herkunft" HU_Attribute is not propagated from LU to
VHU
metas-ts added a commit that referenced this issue Mar 28, 2017
@metas-ts
Update ReleaseNotes.md
331e92c 
[#1194](#1203) HU "Herkunft" HU_Attribute is not propagated from LU to VHU
@metas-lc metas-lc self-assigned this Mar 30, 2017
@metas-lc
Copy link
Contributor

IT
https://github.com/metasfresh/metasfresh-documentation/blob/master/_tests_collection/Testcase_%231194.md
OK

@metas-mk metas-mk mentioned this issue Mar 31, 2017
Closed
metas-ts added a commit that referenced this issue Apr 2, 2017
@metas-ts
Fix CU-on-LU scenarios: don't try include HA in the play
d113c57 
* HUJoinBL: don't join a TU to a parent's HA item, because the HA item
is special (e.g. can represent just one type of TU), and one can't just
attach random stuff to it.
* TUProducerDestination: detect the CU-on-LU situation and avoid
creating an aggregate HU. This is now also verifies in
LUTUProducerDestinationLoadTest
* LUTUConfigurationEditorModel: if the current lutu-config already
contains some sort of virtualPI key, then don't add another one. It's
confusing to the user
* rest: minor changes

FRESH-1794 #1194 HU "Herkunft" HU_Attribute is not propagated from LU to
VHU
(cherry picked from commit 7f2184a)
metas-ts added a commit that referenced this issue Sep 24, 2017
@metas-ts
Update ReleaseNotes.md
2b120f9 
[#608](metasfresh/metasfresh-webui-api-legacy#608) CU
Quantity in Excel Export from HU Editor is wrong
[#2477](#2477)
Subscription Import Window Adjustments
[#588](metasfresh/metasfresh-webui-api-legacy#588)
Cloning Feature: Error when cloning BOM
[#2541](#2541) Allow
filtering by product group in window product
[#2538](#2538) Remove
legacy LDAP code
[#576](metasfresh/metasfresh-webui-api-legacy#576)
Implement batch entry for Sales/Purchase Invoice documents
[#2484](#2484) allow
using partner product numbers and name for entering order line
[#2502](#2502) Allow
multiple shipment schedules per orderline
[#2395](#2395) Drop
C_Flatrate_Conditions.IsNewTermCreatesOrder together with java code
[#2529](#2529) Import
System users
[#607](metasfresh/metasfresh-webui-api-legacy#607)
AD_Column.IsMandatory shall be overwritten by MandatoryLogic
[#2514](#2514) Support
importing multiline fields
[#603](metasfresh/metasfresh-webui-api-legacy#603)
Handle incorrect AD_Window_ID in URL
[#1167](metasfresh/metasfresh-webui-frontend-legacy#1167)
Edit Fields in Main Grid View
[#2146](#2146) Implement
Generic Multi Tags / labels for records
[#2501](#2501) Import
Requests
[#2510](#2510) Prevent
users from creating duplicate main prices
[#2344](#2344) Support
version 02 CAMT54 file
[#1197](metasfresh/metasfresh-webui-frontend-legacy#1197)
frontend: export view to excel
[#2482](#2482) Allow
disabling of model interceptors on the fly
[#1194](metasfresh/metasfresh-webui-frontend-legacy#1194)
Use API to fetch the locale
[#591](metasfresh/metasfresh-webui-api-legacy#591)
Filter by warehouse when selecting HUs to issue
[#593](metasfresh/metasfresh-webui-api-legacy#593)
Remove Clone action if not supported
[#2492](#2492) Process
C_Dunning_Candidate_Process fails
[#491](metasfresh/metasfresh-webui-api-legacy#491)
Wrong widget Type for Date-Range in Process Parameter

me-45
metas-ts added a commit that referenced this issue May 13, 2019
@metas-ts
update ReleaseNotes.md
1ae6cf7 
  * [#5101](#5101) Area search - Geocoding
  * [#5175](#5175) Add language parameter to SQL Function PP_Product_BOM_Recursive
  * [#5177](#5177) Checking BtM and PZN with Modulo 11
  * [#5183](#5183) Enable selective cache invalidation
  * [#78](metasfresh/metasfresh-e2e-legacy#78) Enable checking for user notifications
  * [#5172](#5172) Pricing Conditions Report Error
  * [#5182](#5182) forum-datenaustausch.ch XML externalId not sufficiently unique
  * [#5185](#5185) forum-datenaustausch.ch XML pre-existing documents are removed from XML on exporting
  * [#5186](#5186) Invoice candidate from order line candidate - pricelist precision not applied when computing PriceActual
  * [#1189](metasfresh/metasfresh-webui-api-legacy#1189) Results missing in batch entry dropdown
  * [#1194](metasfresh/metasfresh-webui-api-legacy#1194) Non-Mandatory BigDecimal fields inititalized with 0
  * [#79](metasfresh/metasfresh-e2e-legacy#79) Fix sales order test

metasfresh/me03#1680
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@metas-lc metas-lc

Labels
type:bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@metas-ts @metas-lc