Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0018693Openbravo ERP09. Financial managementpublic2011-10-04 16:542014-12-22 11:16
Reporterxabiermerino 
Assigned Tojonalegriaesarte 
PriorityhighSeverityminorReproducibilityalways
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version3.0MP3 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0018693: You are not able to introduce different sequence in Journal Batch
DescriptionYou are not able to introduce different sequence in Journal Batch. If you create two doc types for different organizations with different sequences the application does not get the correct one.
Steps To Reproduce- Create two doc types for different organizations with different sequences
- Create a gl journal batch
- Realize that the application does not get the correct sequence
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to design defect 0024198 new dmiguelez Openbravo ERP Documentno in Expense Sheet not working well for different Organization sequences 
has duplicate design defect 0024210 new dmiguelez Openbravo ERP Wrong Documen No when changed organization in G/L Journal 
has duplicate defect 0056864 closed Triage Omni WMS Retail Modules Stock API. Difference between calls from SSMS or POS 
related to feature request 0028464 new Triage Omni OMS Openbravo ERP It would be fine to be able to define different document sequence by organization for Goods Movements 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-10-04 16:54xabiermerinoNew Issue
2011-10-04 16:54xabiermerinoAssigned To => jonalegriaesarte
2011-10-04 16:54xabiermerinoModules => Core
2014-12-18 18:22ngarciaRelationship addedhas duplicate 0024210
2014-12-18 18:30ngarciaRelationship addedrelated to 0024198
2014-12-22 11:16ngarciaIssue Monitored: ngarcia
2014-12-22 11:24ngarciaRelationship addedrelated to 0028464
2024-11-05 18:32mtaalRelationship addedhas duplicate 0056864

There are no notes attached to this issue.