Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0022256
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Retail Modules] Web POSminorhave not tried2012-11-09 15:212014-12-17 12:51
ReportermarvintmView Statuspublic 
Assigned Toadrianromero 
PrioritynormalResolutionno change requiredFixed in VersionRR14Q2
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0022256: Web POS doesn't support more than one location or contact per business partner

DescriptionCurrently, Web POS doesn't support more than one location or contact per business partner.

The table used to store business partners locally is also used to store the contact and location, so implicitly the design is assuming that only one location and contact will exist for each one.

However, in Openbravo is perfectly acceptable to have more than one location or contact per business partner. So it needs to be decided whether this also needs to be supported in the POS, and how this will be done.
Steps To ReproduceVerify that the C_Bpartner table is designed around the idea that each business partner will store only one location and contact. Also check the logic in the POS application, which is essentially assuming the same.
TagsNo tags attached.
Attached Filespng file icon Selection_022.png [^] (105,652 bytes) 2014-12-17 12:50

- Relationships Relation Graph ] Dependency Graph ]
related to feature request 0022230 closedadrianromero Handle multiple addresses 

-  Notes
(0061146)
dmitry_mezentsev (developer)
2013-09-13 19:02

Hi Adrian,

Could you update this ticket as it is done please.
(0072628)
mtaal (manager)
2014-12-17 12:51

required functionality is supported, see screenshot

- Issue History
Date Modified Username Field Change
2012-11-09 15:21 marvintm New Issue
2012-11-09 15:21 marvintm Assigned To => adrianromero
2012-11-14 18:31 adrianromero Status new => scheduled
2012-11-14 18:31 adrianromero fix_in_branch => pi
2012-11-14 18:32 adrianromero Assigned To adrianromero => guilleaer
2012-12-05 20:09 adrianromero Fixed in Version => RMP18
2012-12-05 20:09 adrianromero fix_in_branch pi =>
2012-12-20 13:40 adrianromero Severity major => minor
2013-07-28 11:22 thirumalaik Relationship added related to 0022230
2013-08-07 11:50 guilleaer Assigned To guilleaer => adrianromero
2013-09-13 19:02 dmitry_mezentsev Note Added: 0061146
2014-12-17 12:50 mtaal File Added: Selection_022.png
2014-12-17 12:51 mtaal Note Added: 0072628
2014-12-17 12:51 mtaal Status scheduled => closed
2014-12-17 12:51 mtaal Resolution open => no change required
2014-12-17 12:51 mtaal Fixed in Version RMP18 => RR14Q2


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker