Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0040354Retail ModulesWeb POSpublic2019-03-11 23:062019-05-08 10:12
Reportergsuarez 
Assigned Toranjith_qualiantech_com 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in VersionRR19Q3 
Merge Request Status
Review Assigned Toguilleaer
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0040354: Attibute set value entered in a order are not the same when a Verified Return transaction is created
DescriptionIn a new receipt, When a product is selected having an instantiable attribute, a popup appear to input the attribute set value.
The entered attribute set value in a new receipt, has a format like a Atributo1_Atributo_2_SerialNro, but when a Verified Return transaction want to be created the attribute set must be SerialNro_Atributo1_Atributo2.
Then, there is an error in Errors While Importing POS data window, because the value received is not valid.
Steps To ReproduceIn livebuilds retail_mp_3.0RR18Q3.5 or retail_mp_3.0RR18Q4.2


1. Go to Preference and search the Property = "Web POS Enable support for product attributes" and change the Value = Y.
2. Create attributes, Atribute1 and Atribute2 from the Attribute window.
3. Create the "Attribute set" with the previous Attributes, from the attribute set window.
4. Set to any product the "Attribute set" previously created. Example: GPS Mini
5. In the POS, create new Receipt for the product configured with attribute C_2_587, for example. (Atributo1_Atributo_2_SerialNro)
6. Check the order in the backend
7. Go to Verified Returns and find the previous order.
8. Try to enter the attribute set in the same format like when the new receipt was created (Atributo1_Atributo_2_SerialNro)
9. Since in the previous step, C_2_587 (Atributo1_Atributo_2_SerialNro)could not be entered , try (SerialNro_Atributo1_Atributo_2) 587_C_2
10. Check the "Errors While importing POS Data" window
11. If attSetInstanceDesc is change in the json, from attSetInstanceDesc":"587_C_2” to attSetInstanceDesc":"C_2_587” the receipt will be imported.
11. Repeat de step 5, but creating the new receip with atribute format 587_C_2. Then we will have an error in "Errors While importing POS Data" window.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to design defect 0040807 new Retail [Support for attributes] Web POS is not managing correctly serialNo and LotNo when specific control is defined 
Attached Files? Steps issue 11032019 8415.odt (1,875,201) 2019-03-11 23:06
https://issues.openbravo.com/file_download.php?file_id=12735&type=bug
Issue History
Date ModifiedUsernameFieldChange
2019-03-11 23:06gsuarezNew Issue
2019-03-11 23:06gsuarezAssigned To => adrianromero
2019-03-11 23:06gsuarezFile Added: Steps issue 11032019 8415.odt
2019-03-11 23:06gsuarezResolution time => 1554156000
2019-03-14 05:41gsuarezDescription Updatedbug_revision_view_page.php?rev_id=18459#r18459
2019-03-14 05:41gsuarezSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=18461#r18461
2019-04-09 03:39matias-bernalIssue Monitored: matias-bernal
2019-04-09 03:48matias-bernalNote Added: 0111033
2019-04-09 10:27adrianromeroAssigned Toadrianromero => Retail
2019-04-11 15:02matias-bernalResolution time1554156000 => 1554087600
2019-04-11 15:02matias-bernalPrioritynormal => high
2019-04-29 11:44gorka_gilProjectJava Client POS => Retail Modules
2019-04-29 11:45gorka_gilResolution time1554087600 => 1554069600
2019-04-29 11:45gorka_gilTriggers an Emergency Pack => No
2019-04-29 11:45gorka_gilCategory02 - ERP-POS Integration => Web POS
2019-04-29 13:02marvintmResolution time1554069600 => 1557871200
2019-04-29 14:57ranjith_qualiantech_comAssigned ToRetail => ranjith_qualiantech_com
2019-04-30 11:57ranjith_qualiantech_comStatusnew => scheduled
2019-05-03 12:34hgbotCheckin
2019-05-03 12:34hgbotNote Added: 0111475
2019-05-03 12:34hgbotStatusscheduled => resolved
2019-05-03 12:34hgbotResolutionopen => fixed
2019-05-03 12:34hgbotFixed in SCM revision => http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/393e289261cdb5c5d927c7cccafcbd0f24a9070a [^]
2019-05-07 08:45ranjith_qualiantech_comNote Added: 0111523
2019-05-07 08:45ranjith_qualiantech_comStatusresolved => new
2019-05-07 08:45ranjith_qualiantech_comResolutionfixed => open
2019-05-07 18:00guilleaerNote Added: 0111548
2019-05-08 07:13ranjith_qualiantech_comStatusnew => scheduled
2019-05-08 07:19ranjith_qualiantech_comNote Added: 0111554
2019-05-08 07:19ranjith_qualiantech_comStatusscheduled => resolved
2019-05-08 07:19ranjith_qualiantech_comResolutionopen => fixed
2019-05-08 10:12guilleaerNote Added: 0111556
2019-05-08 10:12guilleaerReview Assigned To => guilleaer
2019-05-08 10:12guilleaerStatusresolved => closed
2019-05-08 10:12guilleaerFixed in Version => RR19Q3
2019-05-08 10:12guilleaerRelationship addedrelated to 0040807

Notes
(0111033)
matias-bernal   
2019-04-09 03:48   
When you create an attribute from good shipment or purchase order, the serial number adds a '#' in front of number. if you add serial number control into attibute set then '#' is not added.

Steps to reproduce:

1. Create new atributes (Attribute1 and Attribute2).
2. Create a new Attribute set without serial number control and add them the previous attributes.
3. Set to any product the Attribute set proviously created.
4. Create a Good Shipment, add a new line using the product configured in the previous step.
5. The attribute set created will have '#' in front of number.
6. Change the attribute set created in the step 3 adding serial number control.
7. Create another Good Shipment using the same configuration in step 4.
8. The attribute set created will do not have '#'.
(0111475)
hgbot   
2019-05-03 12:34   
Repository: erp/pmods/org.openbravo.retail.posterminal
Changeset: 393e289261cdb5c5d927c7cccafcbd0f24a9070a
Author: Ranjith S R <ranjith <at> qualiantech.com>
Date: Fri May 03 16:03:15 2019 +0530
URL: http://code.openbravo.com/erp/pmods/org.openbravo.retail.posterminal/rev/393e289261cdb5c5d927c7cccafcbd0f24a9070a [^]

Fixed issue 40354 : Attibute set value should be formed based on attributes order

* Attibute set value should be formed in the order of custom attributes, lot, serialno and guaranteedate
  Above value is formed based on erp m_getjsondesciption plsql function

---
M web/org.openbravo.retail.posterminal/js/utils/attributeUtils.js
---
(0111523)
ranjith_qualiantech_com   
2019-05-07 08:45   
Note https://issues.openbravo.com/view.php?id=40354#c111033 [^] not yet fixed
(0111548)
guilleaer   
2019-05-07 18:00   
Regarding the note added by Matias

I understand what he is telling and all the things that he explains are true.

What is the problem?

could you give more details
(0111554)
ranjith_qualiantech_com   
2019-05-08 07:19   
New issue will be created for note https://issues.openbravo.com/view.php?id=40354#c111033 [^]
(0111556)
guilleaer   
2019-05-08 10:12   
New issue created related with the note https://issues.openbravo.com/view.php?id=40354#c111033 [^]

New Issue: https://issues.openbravo.com/view.php?id=40807 [^]