Difference between revisions of "New Dunning Functionality"

From ADempiere ERP Wiki
Jump to navigationJump to search
 
Line 27: Line 27:
*Volunteers for analyzing: [[User:Kthiemann|Kthiemann]]
*Volunteers for analyzing: [[User:Kthiemann|Kthiemann]]
*Result of analysis:
*Result of analysis:
**Should be included in next release
**The new dunning funcitionality is fully compatible with the existing old dunning. It reuses existing tables/functionality like C_Dunning and C_DunningLevel. The main problem with the existing dunning functionality is that it doesn't use the standard ADempiere document pattern. After the creation of a dunning run you can print the dunning run entries but you don't have them as documents in the system. The new dunning functionality replaces the dunning run window with a process to find dunning canditates (overdue invoices). The user can edit this canditates, for example by giving a dunning grace and create dunning documents in a second step. This is independant from the old existing dunning run functionality so you can choose to stick with the old dunning or use the new functionality instead. The created dunning documents can be printed/emailed as a batch or individualy. In a longer perspective we should think about disabeling the old dunning, in a first step (next) release we can have both dunning mechanisms in parallel.
**[[Process_Gear_in_Window|Process gear in window]] is needed for the new dunning
**End user documentation is still missing (work in progress)
===User roles & profiles===
===User roles & profiles===
===Business process definition===
===Business process definition===

Latest revision as of 09:42, 17 June 2013

Status[edit]

In Production use

Contributors[edit]

Overview[edit]

Possibility to define Pluggable Dunning Sources and create Dunning Candidates. Works with existing Dunning Grace Functionality. Dunning candidates can be processed to Dunning Documents. New Windows:

  • Dunning candidates
  • Dunning Documents

New Process:

  • Create Dunning candidates
  • Create Dunning documents
  • Mass Writeoff/ Dismissal

Purpose[edit]

References[edit]

Design Considerations[edit]

Assumptions[edit]

Dependencies[edit]

Constraints[edit]

Glossary[edit]

Functional Requirements[edit]

Functional team[edit]

  • Volunteers for analyzing: Kthiemann
  • Result of analysis:
    • Should be included in next release
    • The new dunning funcitionality is fully compatible with the existing old dunning. It reuses existing tables/functionality like C_Dunning and C_DunningLevel. The main problem with the existing dunning functionality is that it doesn't use the standard ADempiere document pattern. After the creation of a dunning run you can print the dunning run entries but you don't have them as documents in the system. The new dunning functionality replaces the dunning run window with a process to find dunning canditates (overdue invoices). The user can edit this canditates, for example by giving a dunning grace and create dunning documents in a second step. This is independant from the old existing dunning run functionality so you can choose to stick with the old dunning or use the new functionality instead. The created dunning documents can be printed/emailed as a batch or individualy. In a longer perspective we should think about disabeling the old dunning, in a first step (next) release we can have both dunning mechanisms in parallel.
    • Process gear in window is needed for the new dunning
    • End user documentation is still missing (work in progress)


User roles & profiles[edit]

Business process definition[edit]

User stories[edit]

Functional requirements based on business processes[edit]

User Interface Mockups[edit]

Acceptance criteria[edit]

QA and test cases[edit]

Development infrastructure[edit]

Technical Requirements[edit]

Technical team[edit]

  • Volunteers for analyzing:
  • Result of analysis:

Data Requirements[edit]

Non-Functional Requirements[edit]

Open Discussion Items[edit]

Closed Discussion Items[edit]