View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Add page
Show collection (0 pages)
Collections help

Search

CreditMngtDunning/Use Cases

FBF02400 Dunning Process

Table of Contents

[Hide]


Contents

Modification Log

Date Author Chapter Changes
2009-03-06 Bochmann FBF02400ff Use Cases created

Related Project-File ArgoUML

Example:

Project file:

Version tracking by link:

Test Cases for all Use Cases

Test Case 1 Create Receivables-List

Description of Mask Fields


Field Name Description Value
Fiscal Year Min. 1-digit number for fiscal year (is changed automatically to a 4-digit format)
Authority 2-digit number for the authority (office)
Receivable Type Marking for Receivable Class

(if the entry field is empty, all due data sets will be shown)

  • F= Receivable
  • V= Execution
Dunning Key 2-digit number for dunning key. The dunning key is a dunning level which will later be considered by the dunning process. This dunning key is to be numbered freely.

Test Case 2

Expand Dunning Data

Description of Mask Fields

Field Name Description Value
Fiscal Year Min. 1-digit number for fiscal year (is changed automatically to a 4-digit format)
Authority 2-digit number for authority
Chapter 5-digit number for chapter number
Title 5-digit number for title number. It is to be considered that the system differentiates between revenue and expense titles
Journal No. 6-digit identification of a journal
Payment Partner Given Names Payment partner’s given names
Payment Partner Gender
Payment Partner State Name of state in which the payment partner is registered
Dunning Text Marking
Note

Generate Dunning file Description of Mask Fields

Field Name Description Value
Fiscal Year Min. 1-digit number for fiscal year (is changed automatically to a 4-digit format)
Authority 2-digit number for authority
Dunning Key Determining the dunning level which is later considered by the dunning process
Cash Display 12-digit cash display number * E : spontaneous or relation to debit position (receivable)
  • S : with relation to 0.0 debit position
  • B : All

Test Case 4

Delete Dunning Case Description of Mask Fields

Field Name Description Value
Fiscal Year Min. 1-digit number for fiscal year (is changed automatically to a 4-digit format)
Journal No. 6-digit identification of a journal
Receivable No. Receivable number

Test Case 5 Dunning Log

Display

This feature is to output dunning logs on the screen. Via the numerous fields searching limitations can be entered via the dunning data sets.

Description of Mask Fields

Field Name Description Value
Hj Min. 1-digit number for fiscal year (is changed automatically to a 4-digit format)
Dst 2-digit number for authority number
Kap 5-digit number for chapter number
Tit 5-digit number for title number. It is to be considered that the system differentiates between revenue and expense titles
Ut 2- to 3-digit identification of subtitle
Fb Department-/project-number
Ins Institution number
Obj 15-digit number for object account
Dr
(V/F)-Receivable Type Marking for receivable class * F = Receivable
  • V = Execution
Receivable Number Receivable number
Receivable date Due-date of receivable in format DD.MM.YYYY
Dunning identification Determining if this account with open debit positions should be dunned or not * J : Account open for dunning process
  • N: Account not open
Responsible Official
Receivable Time
Amount Amount of receivable
Dunning fees Total amount of dunning fees [in Euro], which will be charged with this dunning due to the dunning key
Wbezk
Journal
Book No.
HÜL-No./UNo. Number of fiscal year monitoring list and their sub-document number. Check if fiscal year monitoring list number has already been booked from cash. Concerning unknown fiscal year monitoring list number, in both fields “0” needs to be entered
Booking Identification Booking identification
Method of payment 2-digit field for payment method conclusions
Accounting 2-digit number for accounting entity. This is to be numbered freely and will not be checked for consistency.
Due-Date Due-Date in format DD.MM.YYYY
MBS-Dat.
KBS-Date
Payment Partner No. Number of payment partner
Payment Partner Name Name of payment partner
Payment Partner Given Names Payment partner’s given names
Payment Partner Street Payment partner’s address
Payment Partner City City payment partner lives in
Payment Partner Post Code Post code of city payment partner lives in
Payment Partner Bank Account No. Payment partner’s bank account number
Payment Partner Bank Code Bank Code for payment partner’s bank
Purpose of Use Purpose of Use
Customer No. Customer number
Order No. Order number
Invoice No. Invoice number
Invoice Date Date of invoice in format DD.MM.YYYY
Account Form Distinct number of an account form, which will be issued by account generation

Report Mask


Description of Mask Fields

Field Name Description Value
Receivable Date Due-Date of a receivable in format DD.MM.YYYY

Requirements

FBF02100 dunning .png

Use Cases

FBF02400 Due Receivables (Use Case) 01

Status

Author: Anja-Katharina Bochmann

Date: 06.03.09

Intention:

Due receivable will be processed in batches.

Category: Primary (core business process)

Involved people (Those in this use case involved people and any case relating their involvement)

Pre-condition Post-condition Standard procedure Alternative procedures Triggering event

Each receivable need to be booked with a dunning key. Via this dunning key it will be assigned to what time the dunning process has to be initiated.

Results

Description (Use case diagram, activity diagram): Data model

Data security (optional)

Materials (optional)


FBF02410 Calculate Fees (Use Case) 02

Status

Author: Anja-Katharina Bochmann

Date: 06.03.09

Intention:

Due receivables will be processed in batches.

Category: Primary (core business process)

Involved people (Those in this use case involved people and any case relating their involvement)

Pre-condition

A receivable needs to be dunned.

Post-condition

The calculated fees need to be booked separately as receivable

Standard procedure Alternative procedures Triggering event Results

Fees have been calculated

Description (Use case diagram, activity diagram):

The calculation of fees depends on the particular dunning key. The algorithm will be added later.

Data model

Data security (optional)

Materials (optional)


FBF02420 Book Fees (Use Case) 03

Status

Author: Anja-Katharina Bochmann

Date: 06.03.09

Intention:

The dunning fees will be booked separately as receivable.

Category: Primary (core business process)

Involved people (Those in this use case involved people and any case relating their involvement)

Pre-condition

The dunning fees have been calculated.

Post-condition Standard procedure Alternative procedures Triggering event Results

Receivables booked

Description (Use case diagram, activity diagram):

The dunning fees will be booked on a separate account

Data model

Data security (optional)

Materials (optional)

FBF02430 Increase Dunning Key (Use Case) 04

Status

Author: Anja-Katharina Bochmann

Date: 06.03.09

Intention:

The dunning key needs to be changed to the next dunning run.

Category: Primary (core business process)

Involved people (Those in this use case involved people and any case relating their involvement)

Pre-condition Post-Condition

Standard Procedure

Alternative Procedures

Triggering Event

Results Description (Use case diagram, activity diagram):

In the dunning key master data administration each dunning key has a following key (exception 99 = Execution). This dunning key will be now allocated to the receivable to respect it automatically for the next dunning run. Additionally the due-date has to be calculated which also results from the dunning key. In this connection Sundays and public holidays will be respected.

Data model

Data security (optional)

Materials (optional)


FBF02440 Write Dunning (Use Case) 05

Status

Author: Anja-Katharina Bochmann

Date: 06.03.09

Intention:

Dunning letters need to be created.

Category: Primary (core business process)

Involved people (Those in this use case involved people and any case relating their involvement)

Pre-condition Post-Condition

Standard Procedure

Alternative Procedures

Triggering Event

Results

A file with dunning data is created which can be loaded to a serial letter.

Description (Use case diagram, activity diagram):

Dunning data will be written to a file which can be loaded to a serial letter.

Data model

Data security (optional)

Materials (optional)


FBF02450 Write Log (Use Case) 06

Status

Author: Anja-Katharina Bochmann

Date: 06.03.09

Intention:

All dunned receivables are logged.

Category: Primary (core business process)

Involved people (Those in this use case involved people and any case relating their involvement)

Pre-condition Post-Condition

Standard Procedure

Alternative Procedures Triggering Event

Results Description (Use case diagram, activity diagram):

All dunned receivables are to be logged.

Data model

Data security (optional)

Materials (optional)

Concepts (optional)

Concepts result during the preliminary considerations about the use case/group of use cases formulation. Concepts contain e.g. table descriptions, suggestions for the data model, suggestions for possible handling of a problem, evaluation of alternative suggestions and so on.

Drafts (optional)

Retrieved from "http://wiki.openbravo.com/wiki/CreditMngtDunning/Use_Cases"

This page has been accessed 156 times. This page was last modified on 26 March 2018, at 11:48. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.