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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0051334
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo Localizations] Localization Italymajoralways2023-01-11 16:012023-03-30 17:55
ReporterucarrionView Statuspublic 
Assigned Tofermin_gascon 
PriorityurgentResolutionfixedFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Merge Request Status
Regression date
Regression introduced by commit
Regression level
Support ticket
OBNetwork customerNo
Regression introduced in release
Summary

0051334: Direct invoice document number incorrectly generated

DescriptionFollowing the last exchanges, whenever I issue a direct invoice, I expect to get an invoice number based on the the c_invoice.document_no


Currently it is not working like this.
Steps To Reproduce-Login an envionment using the RTPrinter.
-Go out from the demo mode on the RTPrinter.
-Do a sales invoice (press the Issue Invoice button).
-Complete the sales process.
-Check the printout and compare the invoice number with the one expected.
Proposed SolutionThe number informed in the invoice MUST match the c_invoice.document_no
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]

-  Notes
(0145515)
psanjuan (viewer)
2023-01-17 16:52

 This behavior can not be implemented as OB Core is not able to generate a Document Nº based on a given algotithm.
What the RT.Printer does is to sent to the RT-Printer the Document Nº of the invoice that is created by taking into account the corresponding series (configured in the terminal) / sequence number.

To be reviewed with Norauto Project team.

IMHO this is not a bug.
(0145731)
ucarrion (viewer)
2023-01-23 11:00

 FROM (in the BO)
UCA23TT00000001
TO (in the paper RTP)
UCA23TT1
(0145787)
jetxarri (viewer)
2023-01-24 09:15
edited on: 2023-01-30 09:58

 Fixed in commits
https://gitlab.com/openbravo/customers/NOR/org.openbravo.retail.rtprinter/-/merge_requests/26/diffs?commit_id=77218b8917d201536bc64b96e5e45563cb033686 [^]
https://gitlab.com/openbravo/customers/NOR/org.openbravo.retail.rtprinter/-/merge_requests/26/diffs?commit_id=378218bece36a6fe22178abac9da8044cf344ed2 [^]
https://gitlab.com/openbravo/customers/NOR/org.openbravo.retail.rtprinter/-/commit/6c8f025a6a57ffa189ebda8e62e1dc0c576d22cc [^]

As part of MR
https://gitlab.com/openbravo/customers/NOR/org.openbravo.retail.rtprinter/-/merge_requests/26/commits [^]
(0146121)
psanjuan (viewer)
2023-02-01 14:46

 The main problem is that at the end the customer does not see the same "number" in the printed document than in the Backoffice, so we need to find the way to show the same number.
(0146490)
psanjuan (viewer)
2023-02-13 17:22
edited on: 2023-02-14 12:38

 Proposal suggested:
to put the Document Series in a dedicated field and in the next line
to put the Document Sequence "N. Fatura" up to 99999, if more numbers then we will use the field Prefix (10 characters)

Example:
series fattura : vbs1itikdaf/
n fattura: 00000000000012
(0147644)
ucarrion (viewer)
2023-03-17 09:06

 Reopening the issue as it is still KO.
(0147838)
psanjuan (viewer)
2023-03-22 13:31
edited on: 2023-03-22 13:40

 NEW PROPOSED SOLUTION (as the one provided so far can not be implemented properly due to RT-printer constraints).

We will let the RT-Printer to manage Direct Invoice numbering
OB Invoice number (including prefix + sequence number) will be included in the Direct Invoice as a comment through a specific command.

This OB Invoice number will be included in the "Customer" section before the ticket start, with details:

FATTURA N. XXXXXXXXX/XXXXXXXXXX
(0148124)
fermin_gascon (viewer)
2023-03-30 17:55

 https://gitlab.com/openbravo/customers/NOR/com.openbravo.norauto.printtemplates/-/merge_requests/384 [^]
https://gitlab.com/openbravo/customers/NOR/org.openbravo.retail.rtprinter/-/merge_requests/35 [^]

- Issue History
Date Modified Username Field Change
2023-01-11 16:01 ucarrion New Issue
2023-01-11 16:01 ucarrion Assigned To => psanjuan
2023-01-11 16:01 ucarrion OBNetwork customer => No
2023-01-17 16:52 psanjuan Note Added: 0145515
2023-01-17 16:52 psanjuan Status new => feedback
2023-01-18 13:15 ucarrion Description Updated View Revisions
2023-01-18 13:15 ucarrion Proposed Solution updated
2023-01-20 09:32 ucarrion Status feedback => new
2023-01-23 11:00 ucarrion Note Added: 0145731
2023-01-23 11:02 psanjuan Description Updated View Revisions
2023-01-23 11:04 psanjuan Assigned To psanjuan => Triage Platform Conn
2023-01-23 11:06 psanjuan Assigned To Triage Platform Conn => jetxarri
2023-01-24 09:15 jetxarri Note Added: 0145787
2023-01-30 09:58 jetxarri Note Edited: 0145787 View Revisions
2023-01-31 14:56 ucarrion Assigned To jetxarri => fermin_gascon
2023-02-01 14:46 psanjuan Note Added: 0146121
2023-02-13 17:22 psanjuan Note Added: 0146490
2023-02-13 17:31 psanjuan Note Edited: 0146490 View Revisions
2023-02-14 12:37 psanjuan Note Edited: 0146490 View Revisions
2023-02-14 12:38 psanjuan Note Edited: 0146490 View Revisions
2023-03-16 17:00 fermin_gascon Status new => acknowledged
2023-03-16 17:00 fermin_gascon Status acknowledged => scheduled
2023-03-16 17:00 fermin_gascon Status scheduled => resolved
2023-03-16 17:00 fermin_gascon Resolution open => fixed
2023-03-17 09:06 ucarrion Note Added: 0147644
2023-03-17 09:06 ucarrion Status resolved => new
2023-03-17 09:06 ucarrion Resolution fixed => open
2023-03-22 13:31 psanjuan Note Added: 0147838
2023-03-22 13:37 psanjuan Note Edited: 0147838 View Revisions
2023-03-22 13:38 psanjuan Note Edited: 0147838 View Revisions
2023-03-22 13:40 psanjuan Note Edited: 0147838 View Revisions
2023-03-30 17:55 fermin_gascon Note Added: 0148124
2023-03-30 17:55 fermin_gascon Status new => scheduled
2023-03-30 17:55 fermin_gascon Status scheduled => resolved
2023-03-30 17:55 fermin_gascon Resolution open => fixed
2023-03-30 17:55 fermin_gascon Status resolved => closed

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker