Scribd Logo
Upload

Welcome to Scribd!

  • 72 views

    FS For Dunning Procedure in JSN

    Uploaded by

    Vikas M
    The document outlines the process for generating payment reminders or dunning notices for overdue customer invoices, including filtering invoices by payment status, populating output screens with invoice details, and providing options to print or email notices. It also describes capturing dunning history details in a separate table when notices are printed or emailed to view the dunning process over time for a customer.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    FS For Dunning Procedure in JSN

    Uploaded by

    Vikas M
    72 views3 pages
    The document outlines the process for generating payment reminders or dunning notices for overdue customer invoices, including filtering invoices by payment status, populating output screens with invoice details, and providing options to print or email notices. It also describes capturing dunning history details in a separate table when notices are printed or emailed to view the dunning process over time for a customer.

    Original Description:

    dunning

    Original Title

    FS for Dunning procedure in JSN

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document outlines the process for generating payment reminders or dunning notices for overdue customer invoices, including filtering invoices by payment status, populating output screens with invoice details, and providing options to print or email notices. It also describes capturing dunning history details in a separate table when notices are printed or emailed to view the dunning process over time for a customer.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    72 views3 pages

    FS For Dunning Procedure in JSN

    Uploaded by

    Vikas M
    The document outlines the process for generating payment reminders or dunning notices for overdue customer invoices, including filtering invoices by payment status, populating output screens with invoice details, and providing options to print or email notices. It also describes capturing dunning history details in a separate table when notices are printed or emailed to view the dunning process over time for a customer.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 3

    Selection Screen –

    Range
    Company Code
    (BUKRS) No
    Customer (KUNNR) Yes

    o Due items
    o Overdue items
    o Both

    Dunning History

    Go to table BSID, pass the below given fields-

    Selection
    BUKRS screen
    Selection
    KUNNR screen
    UMSKZ Equal to Blank

    S.No PO Pending Payment


    . Bill No. Date No. Amount terms Due date
    BSID- BSID-  VBKD- T052-ZTAG1 + BSID-
    1 VBELN BLDAT BSTKD BSID-DMBTR T052-TEXT1 DMBTR

    1. For payment terms, copy BSID-ZTERM and pass in table T052-ZTERM, copy T052-TEXT1 and
    T052-ZTAG1 and populate T052-TEXT1 in “Payment terms” field.
    2. Due date: Add T052-ZTAG1 to BSID-DMBTR and populate the calculated date in “Due date”
    field.
    3. Po number - Pass VEBLN in VBRP, extract AUBEL field and pass this field in table VBKD, extract
    field BSTKD , this field is PO No. 
    4. Also, capture field BSID-BELNR, BSID-KUNNR, BISD-GJAHR that we will be using in Dunning
    History.

    Scenario 1 – If the user has selected “Due items” on selection screen, only those line items needs to be
    filtered out where calculated Due date is equal to System date.

    Scenario 2 - If the user has selected “OverDue items”, only those line items needs to be filtered out
    where calculated Due date is less than the system date.
    Scenario 3 - – If the user has selected “Both”, no filter is required. All the documents we get in table
    BSID have to be populated in output screen. But separate mail body and attachment should go
    to the customer for Due and Overdue items.

    Same fields need to be replicated in Smartform.

    Once user gets the output screen, and convinced with the results, need to give an option to the user to
    either print or send an email to the customer.

    PRINT SEND EMAIL

    Bill Pending Payment


    S.No. No. Date PO No. Amount terms Due date
    BSID- BSID- T052-ZTAG1 + BSID-
    1 VBELN BLDAT  VBKD-BSTKD BSID-DMBTR T052-TEXT1 DMBTR

    When the user clicks print, a smartform with the same structure as shown above will be called in a print
    preview and further allowing user to print.

    When user selects “Send Email”, copy KUNNR and pass in table KNA1 and copy field KNA1-ADRNR and
    go to table ADR6 and pass KNA1-ADRNR in field ADR6-ADDRNUMBER and execute. Copy field
    ADR6-STMP_ADDR and send mail to that email id. In case, any mail id has been maintained in
    table ZDUNN_EMAIL, mail should also be triggered to that email id in CC.

    DUNNING HISTORY

    At the time, user prints the smartform or send the smartform via mail, program should capture the all
    the below given fields along with the dunning date (Print/Email date), BSID-BELNR, BISD-KUNNR,
    BSID-GJAHR save in a ztable that will be used to view the history of the dunning taken place for
    the customer.

    So, when the user selects Dunning history checkbox in selection screen and execute, all the line items
    saved in Ztable for that customer will be populated with all the fields mentioned above.

    You might also like