Get Even More Visitors To Your Blog, Upgrade To A Business Listing >>

FI ECC 6 Certification Part-3

Tags: dunning
  1. Dunning
  2. Dunning Run
    1. System check account for items that is overdue
    2. Check whether dunning notice to be sent
    3. Dunning level to be assigned
    4. Dunning proposal can be edited / deleted
    5. Dunning Notices printed
    6. Dunning data updated in:
      1. Document
      2. Customer / Vendor master record

  3. 4 steps of dunning process
    1. Maintain parameters
    2. Proposal Run
    3. Edit dunning proposal
    4. Print dunning notices

  1. Customer without dunning procedure in Master Record cannot be dunned


  3. Dunning Program Configuration
  4. Maintain Dunning Procedure
    1. Controls how dunning is done
    2. Every customer / vendor that needs to be dunned needs to have a dunning procedure
    3. Dunning procedure can process both standard & special GL transactions


  5. For each dunning procedure define
    1. Dunning procedure key
    2. Dunning Procedure description
    3. Interval in days at which accounts have to be dunned. System check dunning date is after the number of days specified here from the last dunning run date
    4. Minimum days in arrears for which an item in an account must be overdue for dunning notices to be created for the account
    5. Grace period per line item: Grace period >= minimum days in arrear for an item to be dunned
    6. Number of dunning levels: The highest dunning level possible in this procedure
    7. Grace Period: Not considered for calculating dunning level. Thus an item whose days in arrears <= Grace period is not due for dunning notice
    8. Interest Indicator : If selected interest is calculated for this account

  6. Dunning Levels
    1. Days in Arrear: Item dunning Level = (Item due date + Days in arrear)
    2. Calculate Interest : Can specify whether interest is to be calculated for each dunning level
    3. Print Parameters :
      1. Always Dun: If selected a dunning notice is sent even if no changes have been made to the dunning proposal since last Dun
      2. A Dun proposal changes: At least one item in the account reaches next level or/and a new item is added.
    4. Print All Items: All open items printed in the dunning notice. Dunning notice has dunning level of the item with highest dunning level

  7. Dunning Charges
    1. Dunning charges defined for each dunning level
    2. Dunning charges can be fixed amount or % of dunned amount

  8. Minimum Amount:
    1. Minimum amount of an overdue item necessary for dunning notice at this dunning level
    2. Minimum Amount for Interest : Minimum amount of interest necessary for dunning at the dunning level

  9. Dunning Texts:
    1. SAP Forms / scripts to be used for dunning at each dunning level


  1. Parameters for Dunning run
  2. Run Date: Any Date

  3. Identification: Any 6 digit to identify the dunning run
  4. Parameters:
    1. Dunning Date: Issue date for dunning note. Basis for calculating days in arrears
    2. Document Posted Up to: Items posted up to this date are included in the proposal
    3. Company code
    4. Vendor / Customer
    5. Additional Log: Activate if more details required

  5. The Dunning Run
  1. Dunning Run has 3 steps
    1. Account Selection: Program selects customer / vendor accounts as per parameters
    2. Dun Line Items: Program selects line item for dunning, i.e. overdue line items

  1. Account Selection Criteria
    1. Dunning procedure entered in customer / vendor master record
    2. (Date of last dunning run entered in customer / vendor master record by the system + Dunning interval ) > dunning date in the dunning procedure

  1. Due Line Items
    1. Customer Invoices: Due on date for net payment. Due date is date after missing all cash discount periods
    2. Credit memos: If a credit memo refers to an invoice then invoice due date applies to the credit memo

  2. Clearing with credit memos & vendor line items
    1. Customers net due debit items cleared with net due credit items ( credit memos)
    2. Where customer = vendor. Customer net due credit item cleared against vendor net due debit item. Same dunning procedure assigned to both the customer & vendor.

  3. Dunning Dates:
    1. Due Date: Date by which Item must be paid
    2. Item Overdue: After deducting grace period from days in arrears

  4. Dunning block in Item / a/c's
    1. If a dunning block exist in customer / vendor master records system add these accounts to blocked account list
    2. Similarly for items

  5. Each dunning procedure can have:
    1. Up to 9 levels
    2. Each line item assigned it's dunning level according to its days in arrear in Dunning procedure
    3. No dunning procedure can be skipped

  6. Payment Reminder : Dunning Procedure with one dunning level

  7. Dunning Keys:
    1. Can assign dunning keys to the line item to restrict maximum dunning level for the line item ( FB03 – Customer line item – Change)

  8. Minimum days in arrears:
    1. Customer / Vendor account can only be dunned if at least one line item has reached the minimum days in arrears
  9. Dunning run updates master record with dunning level


  1. Exercises : Dunning
  2. Reason why overdue items may not be dunned
    1. Customer / Vendor account not in dunning parameters
    2. Item w/I grace period
    3. Item / account blocked for dunning
    4. Overdue amount < Minimum amount in dunning procedure
    5. Net due item can be cleared with due on credit side
    6. None of the item in the account exceed minimum days in arrears
    7. (Dunning data has not changed since last dunning run + Always DUN not selected)

  3. Dunning run does not update dunning data in line item account. Dunning data is updated when dunning notices are printed

  4. Dunning proposal can be edited as many times as required. Dunning database not changed. Dunning database is changed when DUN notice is printed

  1. Automatic Payment Program
APP Config: FBZP

  1. FBZP: All company codes
    1. Sending Company code : Company code whose invoices are paid
    2. Paying company code: Company code responsible for outgoing payments. Normally same but can be different
    3. Vendor / Customer special GL transaction: Specify which special GL transaction can be paid / considered during APP run. E.g.: A (Down Payment), F (DP request), G (Guarantee)

  2. FBZP : Paying Company code: For each company code define:
    1. Minimum amount for incoming and outgoing payments
    2. Forms used for payment advice & EDI
    3. BOE Specification : You should flag the field if you wish to use bills of exchange, bill of exchange payment requests in the paying company code

  3. FBZP: Payment Method per Country: For each country define:
    1. Payment method to be used (I, W, C...)
    2. Vendor / Customer master record requirements (Bank details, Vendor address..)
    3. Payment & Clearing document type
    4. Payment Medium ( Classic payment medium / PMWB)
    5. Permitted currencies:
      1. Currencies specified: Payment restricted in these currencies
      2. Currency not specified: Payment in any currency

  4. Payment Method in Company code
    1. A line item whose payment method differ from one specified here are excluded
    2. Specify minim um and maximum amount of payment that can be made for this payment method and company code
    3. Foreign business partner: If selected payment can be made to customer / vendor outside paying company code country
    4. Foreign Currency Allowed: If selected payment can be made in FC.
    5. Form for the payment medium : Form to be used by payment medium program entered in Payment method in Country
    6. Payment Advice Control: Whether a payment advice to be permitted or not permitted

  1. Bank Determination
    1. Ranking Order: HB rank in which APP picks them up for payment
    2. Bank Accounts: Entry for paying company code. GL account to which posting made by this HB. If currency field is blank any currency can be used
    3. Available Amounts: Maximum amount available for outgoing payments
    4. Expenses / Charges: If applicable deducted from incoming payment and added to the outgoing payment

  2. House Bank: HB Config FI12

  1. Reasons for Exception List
    1. Invoice blocked / Vendor blocked for payments
    2. Bank details / Address missing in vendor / customer master record
    3. Payment method not defined in the customer / vendor master records
    4. Debit balance (Not due)
    5. Payment amount < minimum permitted payment amount in FBZP
    6. Invalid House bank

This post first appeared on OM SAP, please read the originial post: here

Share the post

FI ECC 6 Certification Part-3


Subscribe to Om Sap

Get updates delivered right to your inbox!

Thank you for your subscription