Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0026756 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Modules] Service Contract Management | critical | have not tried | 2014-06-02 06:44 | 2014-06-05 06:48 | |||
| Reporter | sjkumar | View Status | public | |||||
| Assigned To | vmromanos | |||||||
| Priority | normal | Resolution | invalid | Fixed in Version | ||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | SCM revision | |||||||
| Regression date | ||||||||
| Regression introduced by commit | ||||||||
| Regression level | ||||||||
| Review Assigned To | vmromanos | |||||||
| Regression introduced in release | ||||||||
| Summary | 0026756: Billing schedule gets spilit up incase of creating 1 billing schedule | |||||||
| Description | 1) created a subscription:10000343 2)1st parent subscription was from 01-JUN-2014 TO 31-MAY-2015 and it created the billing schedule from 01-jun-2014 to 31-may-2015 ---> it looks correct 3)2nd parent subscription line was 6 months later - 01-DEC-2014 TO 31-NOV-2015 This created 2 billing schedule line - 01-dec-2014 to 31-may-2015 01-JUN-2015 to 31-NOV-2015 This is not correct. It should have created 1 billing schedule from 01-DEC-2014 to 31-nov-2015 instead of splitting it into 2 invoices (6 months each). screenshot attached | |||||||
| Steps To Reproduce | 1) created a subscription:10000343 2)1st parent subscription was from 01-JUN-2014 TO 31-MAY-2015 and it created the billing schedule from 01-jun-2014 to 31-may-2015 ---> it looks correct 3)2nd parent subscription line was 6 months later - 01-DEC-2014 TO 31-NOV-2015 This created 2 billing schedule line - 01-dec-2014 to 31-may-2015 01-JUN-2015 to 31-NOV-2015 This is not correct. It should have created 1 billing schedule from 01-DEC-2014 to 31-nov-2015 instead of splitting it into 2 invoices (6 months each). screenshot attached | |||||||
| Tags | No tags attached. | |||||||
| Attached Files |  splitting.doc [^] (101,376 bytes) 2014-06-02 06:44 | |||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
|
(0067674) vmromanos (manager) 2014-06-02 16:09 |
Issue rejected. It is exactly the same scenario as 0026727 that I rejected some days ago. Please read my note in 0026727 to understand why the system must behave this way |
|
(0067768) sjkumar (reporter) 2014-06-05 06:47 |
OB team recommnded to use the “One Time” check box. But this does not always work especially if the invoicing schedule is not Pay In Full (e.g. Quarterly or monthly). |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2014-06-02 06:44 | sjkumar | New Issue | |
| 2014-06-02 06:44 | sjkumar | Assigned To | => vmromanos |
| 2014-06-02 06:44 | sjkumar | File Added: splitting.doc | |
| 2014-06-02 16:04 | vmromanos | Relationship added | has duplicate 0026727 |
| 2014-06-02 16:09 | vmromanos | Review Assigned To | => vmromanos |
| 2014-06-02 16:09 | vmromanos | Note Added: 0067674 | |
| 2014-06-02 16:09 | vmromanos | Status | new => closed |
| 2014-06-02 16:09 | vmromanos | Resolution | open => invalid |
| 2014-06-05 06:47 | sjkumar | Note Added: 0067768 | |
| 2014-06-05 06:48 | sjkumar | Issue Monitored: sjkumar | |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |