Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0008264 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Openbravo ERP] 07. Sales management | minor | have not tried | 2009-03-24 14:20 | 2009-05-06 00:00 | |||
Reporter | pmagnin | View Status | public | |||||
Assigned To | jayakumar | |||||||
Priority | low | Resolution | no change required | Fixed in Version | ||||
Status | closed | Fix in branch | pi | Fixed in SCM revision | ||||
Projection | none | ETA | none | Target Version | 2.40 | |||
OS | Any | Database | Any | Java version | ||||
OS Version | Database version | Ant version | ||||||
Product Version | 2.40MP1 | SCM revision | ||||||
Review Assigned To | ||||||||
Web browser | ||||||||
Modules | Core | |||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0008264: Issue when Auto Numbering option inactivated | |||||||
Description | You can not do a “Create Shipments from Orders” and a “Create Invoices from Orders” after having inactivated the Auto numbering. Please see screenshots in attachment. | |||||||
Tags | No tags attached. | |||||||
Attached Files | AutonumberingIssue_Nuevo.pdf [^] (200,477 bytes) 2009-03-30 20:00 | |||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0016044) jayakumar (reporter) 2009-05-05 12:25 |
We can do "Good shipment", “Create Shipments from Orders” and a “Create Invoices from Orders” after having inactivated the Auto numbering. We don't have any constraint for process whether we choose auto numbering or not in our system. If you choose auto numbering, it will take sequence from specific meta data/sequence name. Otherwise it will take from general pool for particular document type. For instance: The general sequence pool for above scenario is DocumentNo_M_InOut. If you switch it off auto numbering, it will take document number from "DocumentNo_M_InOut" sequence. Otherwise it will take it from specific sequence pool. It is "MM Shipment" in our case above. You may get next sequence id on both the cases. Case 1- Auto Numbering off at good shipment: SELECT * FROM Ad_Sequence where name='DocumentNo_M_InOut' and ad_client_id = '1000001' Case 2- Auto Numbering on at good shipment: SELECT * FROM Ad_Sequence where name = 'MM Shipment' and ad_client_id = '1000001' This rule of thumb is same across our ERP. I am closing this, since the given defect is invalid. |
Issue History | |||
Date Modified | Username | Field | Change |
2009-03-24 14:20 | pmagnin | New Issue | |
2009-03-24 14:20 | pmagnin | Assigned To | => rafaroda |
2009-03-24 14:20 | pmagnin | File Added: AutonumberingIssue.pdf | |
2009-03-24 14:20 | pmagnin | Regression testing | => No |
2009-03-30 19:39 | PascalMagnin | File Added: AutonumberingIssue_New.pdf | |
2009-03-30 19:40 | psarobe | File Deleted: AutonumberingIssue.pdf | |
2009-03-30 19:51 | psarobe | Severity | major => minor |
2009-03-30 20:00 | PascalMagnin | File Added: AutonumberingIssue_Nuevo.pdf | |
2009-03-30 20:02 | psarobe | File Deleted: AutonumberingIssue_New.pdf | |
2009-04-15 22:14 | psarobe | Priority | normal => low |
2009-04-15 22:15 | psarobe | Status | new => scheduled |
2009-04-15 22:15 | psarobe | fix_in_branch | => pi |
2009-05-04 10:44 | AinhoaPagola | Assigned To | rafaroda => sathiyan |
2009-05-04 14:30 | sathiyan | Assigned To | sathiyan => jayakumar |
2009-05-05 12:25 | jayakumar | Status | scheduled => closed |
2009-05-05 12:25 | jayakumar | Note Added: 0016044 | |
2009-05-05 12:25 | jayakumar | Resolution | open => no change required |
2009-05-06 00:00 | anonymous | sf_bug_id | 0 => 2787545 |
Copyright © 2000 - 2009 MantisBT Group |