Scribd Logo
Upload

Welcome to Scribd!

  • 39 views

    Customer Ageing Report FSD

    Uploaded by

    K KUMAR JENA
    This functional specification document outlines the logic for generating an accounts receivable aging report. It describes 20 steps for retrieving customer, invoice, and payment data from SAP tables based on input parameters like company code and customer number. For each invoice, the document type, due date, aging buckets, amounts, and opening balance will be determined and grouped in the report output.

    Copyright:

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

    Customer Ageing Report FSD

    Uploaded by

    K KUMAR JENA
    39 views3 pages
    This functional specification document outlines the logic for generating an accounts receivable aging report. It describes 20 steps for retrieving customer, invoice, and payment data from SAP tables based on input parameters like company code and customer number. For each invoice, the document type, due date, aging buckets, amounts, and opening balance will be determined and grouped in the report output.

    Original Description:

    ok

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This functional specification document outlines the logic for generating an accounts receivable aging report. It describes 20 steps for retrieving customer, invoice, and payment data from SAP tables based on input parameters like company code and customer number. For each invoice, the document type, due date, aging buckets, amounts, and opening balance will be determined and grouped in the report output.

    Copyright:

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

    Customer Ageing Report FSD

    Uploaded by

    K KUMAR JENA
    This functional specification document outlines the logic for generating an accounts receivable aging report. It describes 20 steps for retrieving customer, invoice, and payment data from SAP tables based on input parameters like company code and customer number. For each invoice, the document type, due date, aging buckets, amounts, and opening balance will be determined and grouped in the report output.

    Copyright:

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

    FUNCTIONAL SPECIFICATION DOCUMENT

    Input Screen & Parameter


    Company Code: Mandatory Single Inputs
    Customer No: Optional with Multiple inputs (from to)
    Reporting Date: Optional If Blank then consider System Date
    Logic:
    1. Customer No
    Pass Customer No (KUNNR) and Company Code (BUUKRS) in Table KNB1
    If available, the inputs Customers No (KUNNR) then fetch as Customer No in Report

    Note- Blanck input consider as All Customers

    2. Customer Name
    Pass Customer No (KUNNR) in Table KNA1
    And Fetch Customer Name (NAME1) as Customer Name in Report

    3. Invoice No
    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Invoice No (BELNR) with respect to Customer (KUNNR)

    4. Invoice Date
    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Invoice Date (BLDAT)

    5. Posting Date
    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Invoice Date (BUDAT)

    6. Due Date
    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Base Line Date (ZFBDT)+ Days (ZBD1T)

    7. Currency
    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Transaction Currency (WAERS)

    8. Document Type
    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Document Type (BLART)

    DZ- Collection
    SA- TDS Posting Ask to Client
    AB-Clearing Document (Currency also) ask to client.
    DA- Customer Interest Posting Ask to client.
    DC-Advance
    OB- Open Item migration
    DG-FI Credit Memo
    RV- Invoice / Credit Memo
    ZP- Payment Refund
    DR- FI Invoice
    DN-Debit Note
    9. Not Yet Due
    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Base Line Date (ZFBDT)+ Days (ZBD1T) = due date
    if due date is greater than to Reporting Date (Future Date) then the Value line will come in not
    yet due column with respect to invoice no and all above

    Note- Other than document type DZ/ZP/DC/OB

    10. Today Due


    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Base Line Date (ZFBDT)+ Days (ZBD1T) = due date
    if due date is equal to Reporting Date (Same Date) then the Value line will come in today due
    column with respect to invoice no and all above

    Note- Other than document type DZ/ZP /DC/OB

    11. Overdue
    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Base Line Date (ZFBDT)+ Days (ZBD1T) = due date
    if due date is Lesser than to Reporting Date (Past Date) then the Value line will come in not
    Overdue column with respect to invoice no and all above

    Note- Other than document type DZ/ZP /DC/OB

    12. On Account Collection


    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Amount (WRBTR), Special GL Indicator (UMSKZ) = empty if Document type
    (BLART)=DZ/DC) if Dr / Cr Indicator = S get + sign, Dr / Cr Indicator = H get - sign

    13. Down Payment Collection


    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Amount (WRBTR), Special GL Indicator (UMSKZ) = not empty if Document type
    (BLART)=DZ/DC if Dr / Cr Indicator = S get + sign, Dr / Cr Indicator = H get – sign

    14. Overdue Days


    Due date (fetch as per the above logic)– System Date = Overdue days

    15. Overdue By 0-30 Days


    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Amount (WRBTR) if Document type (BLART)=RV/DR, if Dr / Cr Indicator = S get +
    sign, Dr / Cr Indicator = H get – sign
    And if Due date (fetch as per the above logic)– System Date = Overdue days is greater than /
    equal to 0 and less than 31 Days
    16. Overdue By 31-60 Days
    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Amount (WRBTR) if Document type (BLART)=RV/DR, if Dr / Cr Indicator = S get +
    sign, Dr / Cr Indicator = H get – sign
    And if Due date (fetch as per the above logic)– System Date = Overdue days is greater than
    29 and less than 61 Days

    17. Overdue By 61-90 Days


    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Amount (WRBTR) if Document type (BLART)=RV/DR, if Dr / Cr Indicator = S get +
    sign, Dr / Cr Indicator = H get – sign
    And if Due date (fetch as per the above logic)– System Date = Overdue days is greater than
    59 and less than 91 Days

    18. Overdue By 91-180 Days


    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Amount (WRBTR) if Document type (BLART)=RV/DR, if Dr / Cr Indicator = S get +
    sign, Dr / Cr Indicator = H get – sign
    And if Due date (fetch as per the above logic)– System Date = Overdue days is greater than
    89 and less than 181 Days

    19. Overdue By 181 Days onwards


    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Amount (WRBTR) if Document type (BLART)=RV/DR, if Dr / Cr Indicator = S get +
    sign, Dr / Cr Indicator = H get – sign
    And if Due date (fetch as per the above logic)– System Date = Overdue days is greater than
    180 and onwards

    20. Opening Balance


    Pass Customer No (KUNNR) and Company Code (BUKRS) in Table BSID
    Fetch Amount (WRBTR) if Document type (BLART)=OB, if Dr / Cr Indicator = S get + sign,
    Dr / Cr Indicator = H get – sign

    You might also like