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

Multiple PP Order generation for a materialdispo line #3064

Open
metas-mk opened this Issue Nov 24, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@metas-mk
Member

metas-mk commented Nov 24, 2017

Is this a bug or feature request?

Feature Request

What is the current behavior?

Currently, it is possible to create multiple completed PP Order via materialdispo. The user does not see that a PP Order was created after the action was started. No notification nor shown in manufacturing detail tab.

Which are the steps to reproduce?

Open try and see.

What is the expected or desired behavior?

Only allow to start the action for PP Order creation as long as no PP Order exists for that line, What about having a processed flag for such cases in materialdispo line.

@metas-ts

This comment has been minimized.

Show comment
Hide comment
@metas-ts

metas-ts Nov 24, 2017

Member

Hi @metas-mk

What about having a processed flag for such cases in materialdispo line.

The table MD_Candidate has already a column MD_Candidate_Status.
I'm going to revise if it's set correctly. Can you display that column in the webui?

EDIT: the status is either something like "planned", or the actual DocStaus of the underlying document.
EDIT 2: i added the branch gh3064-app for this issue

Member

metas-ts commented Nov 24, 2017

Hi @metas-mk

What about having a processed flag for such cases in materialdispo line.

The table MD_Candidate has already a column MD_Candidate_Status.
I'm going to revise if it's set correctly. Can you display that column in the webui?

EDIT: the status is either something like "planned", or the actual DocStaus of the underlying document.
EDIT 2: i added the branch gh3064-app for this issue

metas-ts added a commit that referenced this issue Nov 24, 2017

add a check regarding the records' status (only allow process if it's…
… still "planned")

also start checking why the PP_Order was not shown in the production detail tab

Multiple PP Order generation for a materialdispo line #3064

metas-ts added a commit that referenced this issue Nov 24, 2017

extend the existing test a bit further
Multiple PP Order generation for a materialdispo line #3064

metas-ts added a commit that referenced this issue Nov 24, 2017

if ppORder or ddOrder is created via material-dispo-service, then..
return sugfficient info to find the respective records and incoporate the newly created document's ID and status

also rename and refactor stuff a bit

Multiple PP Order generation for a materialdispo line #3064
PP Order not shown in materialdispo although automatically generated #3065

metas-ts added a commit that referenced this issue Nov 27, 2017

minor refactorings/improvements of clarity
* also update the README.md files
* also rename and refactor stuff a bit

Multiple PP Order generation for a materialdispo line #3064
PP Order not shown in materialdispo although automatically generated #3065
@metas-dh

This comment has been minimized.

Show comment
Hide comment
@metas-dh

metas-dh Nov 27, 2017

Member

Results of IT1
tested in mf15 & customer db

  • status of PP_Order displayed in Materialdispo: for PP_Orders that are completed (manually created): OK
  • status of PP_Order displayed in Materialdispo: for PP_Orders that are still in draft (automatically created): not displayed, only after completion: NOK, shall be displayed also in status draft (see #3065)
Member

metas-dh commented Nov 27, 2017

Results of IT1
tested in mf15 & customer db

  • status of PP_Order displayed in Materialdispo: for PP_Orders that are completed (manually created): OK
  • status of PP_Order displayed in Materialdispo: for PP_Orders that are still in draft (automatically created): not displayed, only after completion: NOK, shall be displayed also in status draft (see #3065)

@metas-dh metas-dh self-assigned this Nov 27, 2017

@metas-ts metas-ts removed their assignment Dec 1, 2017

metas-ts added a commit that referenced this issue Dec 1, 2017

update releasenotes.md
[#2177](#2177) New Window
for Attribute Search in WebUI
[#3117](#3117) Disable
MStorage.add
[#1357](metasfresh/metasfresh-webui-frontend#1357)
Don't use the legacy view attributes API
[#1367](metasfresh/metasfresh-webui-frontend#1367)
view attributes shall be refreshed when the current selected row is
refreshed
[#3041](#3041) Forecast
Window copy Field content from header to lines when creation
[#3040](#3040) Implement
Clone/ Copy for Forecast Window WebUI
[#1360](metasfresh/metasfresh-webui-frontend#1360)
View field editor: override viewEditorRenderMode on row level
[#2868](#2868) Make
BOMValidate process to work correctly in webui
[#2956](#2956) drop
allowconsolidateinvoice from database
[#3073](#3073) Error:
Could not find or load main class ${argLine}
[#3072](#3072)
de_metas_purchasecandidate schema containing some diagnosis views
[#705](metasfresh/metasfresh-webui-api#705)
Backend Logic for new Date Filter Widget
[#3064](#3064) Multiple
PP Order generation for a materialdispo line
[#3088](#3088) Transform
in material receipt left destroyed HU behind
[#3086](#3086) HU planned
after Purchase Order, destroyed after material receipt
[#3089](#3089) Not able
to start report service with ReportServiceMain.launch
[#3042](#3042)
C_Bpartner: new Additional fields
[#3060](#3060)
TypedSqlQuery Bugs because aggregateList method ignores order
[#3054](#3054) purchase
candidates: document references

me-45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment