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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0021364
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Modules] Dunning Lettersmajoralways2012-08-16 11:002012-08-20 22:17
ReporterngarciaView Statuspublic 
Assigned Tomtaal 
PriorityurgentResolutionduplicateFixed in Version1.0.5
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version1.0.5
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Regression date
Regression introduced by commit
Regression level
Review Assigned Tomtaal
Regression introduced in release
Summary

0021364: The Start Dunning Work Flow background process is not working properly

DescriptionThe Start Dunning Work Flow background process is not working properly. It does not create any record in the Payment In Plan - Dunning Log tab for late payments.
Steps To ReproduceAs group admin role:
   Go to the Enterprise Module Management window and add the reference data of the module
   Go to the Business Partner window and add the Dunning Policy included in the reference data in the Dunning Policy field of the Customer tab for Alimentos y Supermercados, S.A.
   Create a new Sales Invoice for that BP changing its Invoice Date in order to obtain a payment for at least 11 days ago
   Go to the Process Request window and create a new record:
      Organization: *
      Process: Start Dunning Work Flow
      Timing: Run Immediately
   Click the Schedule Process button
   Go to the Payment In Plan window, select the already created payment
   Notice that there are no records in the Dunning Policy tab
   If there is a payment with tomorrow as Due Date, the process creates two records on it:
      Dunning work flow has started
      Payment not late, exiting dunning work flow

TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
duplicate of defect 00213951.0.5 closedmtaal Dunning letter parameter LateTimeInDays is not used/available in process execution 

-  Notes
(0051379)
mtaal (manager)
2012-08-20 14:15

This is by design, only payments which are 'so-many' days late are considered. This set through the LateTimeInDays parameter in the 'Report and Process' record for starting the dunning work flow. The default value for this parameter is 5.

This assumes that the process request is scheduled in 5 days intervals or less.

Can you try this?

Note that I have solved some other issues in the dunning module. I will publish a new version in a few days from now.
(0051407)
mtaal (manager)
2012-08-20 22:17

The latetimeindays is now done through a preference. I have noted this case (that a payment is not dunning-workflowed) in the documentation also:
http://wiki.openbravo.com/wiki/Projects:Dunning/User_Documentation#Dunning_policy.2C_dunning_status_and_dunning_business_process [^]

See the link in the first bullet in the middle of the section.

- Issue History
Date Modified Username Field Change
2012-08-16 11:00 ngarcia New Issue
2012-08-16 11:00 ngarcia Assigned To => mtaal
2012-08-16 11:00 ngarcia Issue Monitored: networkb
2012-08-20 14:15 mtaal Note Added: 0051379
2012-08-20 14:15 mtaal Status new => feedback
2012-08-20 22:17 mtaal Closed by => mtaal
2012-08-20 22:17 mtaal Relationship added duplicate of 0021395
2012-08-20 22:17 mtaal Note Added: 0051407
2012-08-20 22:17 mtaal Status feedback => closed
2012-08-20 22:17 mtaal Resolution open => duplicate
2012-08-20 22:17 mtaal Fixed in Version => 1.0.5


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker