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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0039627
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Modules] Distribution Ordersmajoralways2018-11-14 13:162018-11-20 10:15
ReporterLeyreView Statuspublic 
Assigned ToAtulOpenbravo 
PriorityhighResolutionfixedFixed in Version
StatusclosedFix in branchFixed in SCM revisionef9d72bb2754
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Regression date
Regression introduced by commit
Regression level
Review Assigned ToSandrahuguet
Regression introduced in release
Summary

0039627: Error with print templates in "Distribution Order" Window

DescriptionWhen you try to print a Distribution Order Issue, with an Organization parent of the Organization defined in the selected Document Type for the Distribution Order Issue, the template defined for this Document Type is not used. The default template is used.

This does not happen if the Organization of the Distribution Order Issue is the same or child of the Organization defined in the selected Document Type for the Distribution Order Issue.
Steps To Reproduce1. In "Document Type" window, define a Document Type for the "F&B España - Región Norte" Organization.

2. On the "Report Templates" tab, define a template.

*** You can modify a fixed text of the default template, to differentiate both:
/org/openbravo/distributionorder/erpReports/OBDO_DistOrder.jrxml
 
3. In "Distribution Order Issue" window, generate a Distribution Order Issue for the same Organization ("F&B España - Región Norte").

4. Book the Distribution Order Issue.

5. Print and verify that the template used, is the one defined for the Document Type.

6.Generate a Distribution Order Issue for a superior Organization, such as "F&B España, S.A".

7. Book the Distribution Order Issue.

8. Print and verify that the template used is not the one defined for the Document Type.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0107984)
AtulOpenbravo (developer)
2018-11-19 15:17

Test Plan

- Install Distribution Order module and dependent module if any.
- Using enterprise module management, create reference data for
Distribution Order module in organization "F&B Espana, S.A"
- Navigate to Distribution Order issue window & create one record
in "F&B Espana, S.A" organization,
  Document Type = Distribution Order Issue
  Warehouse Issue = España Región Norte,
  Warehouse Receipt = España Región Sur
- In Lines, create one record with
  Product: Cerveza Ale 0,5L
  Quantity: 10
- Book Order and Print record.
- Realize that report is generated with name as OBDO_DistOrder.pdf
- This is correct and is the one set as DEFAULT_OUTPUT_NAME in Print_DistOrder class.
- Navigate to document type window with reference of record: Distribution Order Issue
- In Report Template tab, create one record with
  Name: Distribution Order Print (Parent)
  Template Location:@basedesign@/org/openbravo/distributionorder/erpReports
  Template File Name: OBDO_DistOrder.jrxml
  Report File Name: ParentOrgDOPrint
- Navigate back to record created in Distribution Order Issue window previously & print record.
- Realize that report is generated with name as ParentOrgDOPrint.pdf
- Navigate to document type window create a record with
  Organization: F&B España - Región Norte
  Name: Distribution Order Issue (Child Org)
  G/L Category: DO Issue
  Print Text: Distribution Order Issue (Child Org)
  Document Category: Distribution Order Issue
  Sales Transaction: Yes
  Table: OBDO_DistOrder
  Sequence Document = Yes
  Document Sequence: Create a new one and assign it here
- In Report Template tab, create one record with
  Name: Distribution Order Print (Child)
  Template Location:@basedesign@/org/openbravo/distributionorder/erpReports
  Template File Name: OBDO_DistOrder.jrxml
  Report File Name: ChildOrgDOPrint
- Navigate back to record created in Distribution Order Issue window previously & print record.
- Realize that report is generated with name as ParentOrgDOPrint.pdf
- Create two Distribution Order Issue records with organization F&B España - Región Norte.
- Realize that available document types in the list are "Distribution Order Issue" & "Distribution Order Issue (Child Org).
- Create one with document type: "Distribution Order Issue" & one with "Distribution Order Issue (Child Org) with similar data created in step 3.
- Print record with document type "Distribution Order Issue".
- Realize that report is generated with name as ParentOrgDOPrint.pdf
- Print record with document type "Distribution Order Issue (Child Org)".
- Realize that report is generated with name as ChildOrgDOPrint.pdf
- Create a Distribution Order Issue record in organization "F&B Espana, S.A"
- Realize that available document types in the list is only "Distribution Order Issue".
(0108001)
hgbot (developer)
2018-11-20 09:49

Repository: erp/mods/org.openbravo.distributionorder
Changeset: ef9d72bb27545fb6e50107e2e8fe964e116b59a7
Author: Atul Gaware <atul.gaware <at> openbravo.com>
Date: Mon Nov 19 19:50:51 2018 +0530
URL: http://code.openbravo.com/erp/mods/org.openbravo.distributionorder/rev/ef9d72bb27545fb6e50107e2e8fe964e116b59a7 [^]

Fixes Issue 39627: Error with print templates in "Distribution Order"
Window

Added and clause in validation for document type in Distribution Order
Issue so that only document defined in transaction org and its
parents can be used.

---
M src-db/database/sourcedata/AD_VAL_RULE.xml
---
(0108003)
hgbot (developer)
2018-11-20 10:14

Repository: retail/backports/AWO/3.0RR18Q3/org.openbravo.distributionorder
Changeset: cf24743b753d4393b6940ff2d3c992f40de7bee6
Author: Sandra Huguet <sandra.huguet <at> openbravo.com>
Date: Tue Nov 20 09:53:33 2018 +0100
URL: http://code.openbravo.com/retail/backports/AWO/3.0RR18Q3/org.openbravo.distributionorder/rev/cf24743b753d4393b6940ff2d3c992f40de7bee6 [^]

related to issue 39627 backport 18Q3. Error with print templates in DO

Added and clause in validation for document type in Distribution Order
Issue so that only document defined in transaction org and its
parents can be used.

---
M src-db/database/sourcedata/AD_VAL_RULE.xml
---
(0108004)
Sandrahuguet (developer)
2018-11-20 10:15

Code review + testing OK

- Issue History
Date Modified Username Field Change
2018-11-14 13:16 Leyre New Issue
2018-11-14 13:16 Leyre Assigned To => Triage Finance
2018-11-14 13:16 Leyre Resolution time => 1543964400
2018-11-14 16:42 Sandrahuguet Assigned To Triage Finance => AtulOpenbravo
2018-11-15 08:32 AtulOpenbravo Status new => scheduled
2018-11-19 15:17 AtulOpenbravo Note Added: 0107984
2018-11-20 09:49 hgbot Checkin
2018-11-20 09:49 hgbot Note Added: 0108001
2018-11-20 09:49 hgbot Status scheduled => resolved
2018-11-20 09:49 hgbot Resolution open => fixed
2018-11-20 09:49 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/mods/org.openbravo.distributionorder/rev/ef9d72bb27545fb6e50107e2e8fe964e116b59a7 [^]
2018-11-20 10:14 hgbot Checkin
2018-11-20 10:14 hgbot Note Added: 0108003
2018-11-20 10:15 Sandrahuguet Review Assigned To => Sandrahuguet
2018-11-20 10:15 Sandrahuguet Note Added: 0108004
2018-11-20 10:15 Sandrahuguet Status resolved => closed


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker