Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0046528Openbravo ERP07. Sales managementpublic2021-05-06 03:092021-06-07 12:16
Reporterlbressan 
Assigned Tomarvintm 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tomarvintm
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0046528: The "Can be delivered" check of the sales order line is not marked
DescriptionThe product is set as "Do not delivered" when the Sales Order is generated from the backoffice selecting a POS Terminal in the header.
The marked "Can Be deliver" field should be saved, when the line with quantity> 0 is updated.
Steps To ReproduceEnter https://livebuilds.openbravo.com/retail_pi_pgsql/security/Login [^] in The White Valley Group client.
1.Enter Sales Order. Generate the header selecting a POS Terminal.
2.Create a line and select the product.
3.Exit the line WITHOUT indicating quantity. Quantity 0

**** The record is saved leaving the "Can be delivered" check without selection

4.Edit the registry indicating the value in quantity. Keep.

**** The record is updated but the "Can be delivered" check remains without selection
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
duplicate of defect 0046243 closed rqueralta The "Can be delivered" check of the sales order line is not marked 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2021-05-06 03:09lbressanNew Issue
2021-05-06 03:09lbressanAssigned To => rqueralta
2021-05-06 03:09lbressanModules => Core
2021-05-06 03:09lbressanResolution time => 1621980000
2021-05-06 03:09lbressanTriggers an Emergency Pack => No
2021-05-06 03:09lbressanIssue generated from0046243
2021-05-06 04:00lbressanRelationship addedrelated to 0046243
2021-05-31 12:24marvintmReview Assigned To => marvintm
2021-05-31 12:24marvintmRelationship replacedduplicate of 0046243
2021-05-31 12:24marvintmStatusnew => closed
2021-05-31 12:24marvintmResolutionopen => duplicate
2021-06-01 08:00lbressanAssigned Torqueralta => marvintm
2021-06-01 08:00lbressanNote Added: 0128846
2021-06-01 08:00lbressanStatusclosed => new
2021-06-01 08:00lbressanResolutionduplicate => open
2021-06-01 08:02lbressanNote Edited: 0128846bug_revision_view_page.php?bugnote_id=0128846#r22643
2021-06-01 11:53marvintmNote Added: 0128853
2021-06-01 11:53marvintmStatusnew => closed
2021-06-01 11:53marvintmResolutionopen => no change required
2021-06-02 00:58lbressanStatusclosed => new
2021-06-02 00:58lbressanResolutionno change required => open
2021-06-07 12:16marvintmNote Added: 0129134
2021-06-07 12:16marvintmStatusnew => closed
2021-06-07 12:16marvintmResolutionopen => no change required

Notes
(0128846)
lbressan   
2021-06-01 08:00   
(edited on: 2021-06-01 08:02)
This ticket is not duplicated, although it is related to ticket 46243, but with a variation in step 1: "Generate the header selecting a POS Terminal". This problem (with this variation) is still reproducible in pi livebuild. Please review urgently.
(0128853)
marvintm   
2021-06-01 11:53   
After internal review and discussion, we have seen that this issue is not valid.

The criteria we are currently following is:
- If the order comes from the POS (as identified by the fact that it is associated with a terminal) then this check should be set by the order creation
- If it doesn't come from the POS, then we automatically set it depending on whether there are ordered units or not.

The way we have to distinguish if the order is coming from the POS or not is the terminal, that is why it works like this when the terminal is manually set.
(0129134)
marvintm   
2021-06-07 12:16   
I left a comment explaining our view of the situation. We also explained this view with Egoitz before I closed the issue.