Customer ageing report for fbl5n

hi all,
I want to develop an customer Ageing Report in abap  to calculate the net due date  which is similar to the Tcode fbl5n but the problem is functional consultant told me about this tcode  and there is no such information regarding the specified tables which are to be used. I had searched in SDN also but i did not got the desired information.
regards,
karthik
Edited by: k.vinu.karthik on Jul 23, 2010 7:21 AM

Use the development tools available to you - the transaction and a sample account is all you need.  Debug, ST05, SE30, etc....

Similar Messages

  • About customer aging report

    any body having customer aging report for FI pls send me..

    Hi Venkat,
    Check this Thread
    Re: Creating Aging Report and Counting report
    Please search the Forum, you will get lot of more information.
    Thanks
    CK

  • Problem in Logic for Customer Ageing Report

    Hi,
    I am developing a Customer Ageing Report in which i am facing a problem i.e. i am taking tables BSID,BSAD in which i ham taking the open items first and then i am using for all entries in it on the open items and i had debugged it and data picking is correct .
    But the MAJOR problem comes when the data is stored in the respective coloumns i.e. 0-30 ,31-60-61-90 etc.. Currently i am comparing the code with the Standard Report i.e.S_ALR_87012126 it is not coming accurate...
    Is there any way to solve this problem ....
    Edited by: nav009 on Jan 8, 2010 11:39 AM

    Hi,
    First you need to calculate the Due date of the Transaction with the help of FM 'NET_DUE_DATE_GET'.
    Once you get the Due date calculate the value wf_nod  as wf_nod = p_budat - wf_due_date where p_budat is the date on which you want to run the ageing report and wf_due_date  is due date of the transaction.
    once you get this wf_nod write the following logic :
          IF wf_nod < 0.
            wa_tab-ndue = wa_data-dmbtr.
          ELSE.
            IF wf_nod <= pnod1.
              wa_tab-amt1 = wa_data-dmbtr.
            ELSE.
              IF wf_nod > pnod1 AND wf_nod <= pnod2.
                wa_tab-amt2 = wa_data-dmbtr.
              ELSE.
                IF wf_nod > pnod2 AND wf_nod <= pnod3.
                  wa_tab-amt3 = wa_data-dmbtr.
                ELSE.
                  IF wf_nod > pnod3 AND wf_nod <= pnod4.
                    wa_tab-amt4 = wa_data-dmbtr.
                  ELSE.
                    IF wf_nod > pnod4 AND wf_nod <= pnod5.
                      wa_tab-amt5 = wa_data-dmbtr.
                    ELSE.
                      IF wf_nod > pnod5.
                        wa_tab-amt6 = wa_data-dmbtr.
                      ENDIF.
                    ENDIF.
                  ENDIF.
                ENDIF.
              ENDIF.
            ENDIF.
          ENDIF.
        ENDIF.
    Collect wa_tab into it_tab.
    where pnod1.......pnod5 are the aging period as 30,60,90,180,365 etc.
    by this you will get correct results.
    Please get back to me if you need some more help on this.
    Regards,
    Nikhil

  • Customer Aging Report - different defaults for different customers

    In SAPB1 2007, SP01 PL09, we want to be able to run a different Customer Receivables Report for only certain customers.
    That is, we want ONE Statement to print for most customers, but have a different statement print for a handful of other customers. Currently, the only way to do this is set one report as the default, bring up a handful of customers by a certain property, then reset the default, bring up the rest of the customers by excluding that property, then running the statements again.
    Alternatively, we can set the Customer Receivables Report default by User. But the customers we need for the alternative statement are not relegated to one user, so this doesn't work.
    Is there a better way to do this? Some way to assign a default statement to a particular group of customers, by Business Partner number alone?

    Hi,
    I'm using SBO 2005A PL 46, the BP currency is USD and the Local Curr is IDR.
    Thanks

  • Aging Report for AR

    Dear All,
    I have trouble about "Execute Aging Report for AR" (FDI0).
    The aging report from period 3 (march) till period 4 (may) is different from the amount in the Customer Line Item (FBL5N), whereas it should be has the same amount, isn't it?
    Please help me, what should I check first..? its urgent..
    Thanks & regards,
    Vanda

    hi,
    compare with report RFDOPR00
    and have a look on that discussion: AR Credit Concept of Aging
    regards
    Andreas

  • Customer aging report-needs the line items behind it

    We have created a Z report for customer aging report,is it feasible to get the drilldown against each aging bucket.I.e to call the FBL5n report to be displayed to see the line items behind each aging bucket.
    Regards
    Rekha

    If standard report does not suffice your requirement, then create your own.
    FOR vendor USE K in transaction code instead of D.
    Hello,
    The following example I have given is for customers.
    The only difference is in transaction codes. For customer you go to FDI1, for vendor you go to FKI1 (reports).
    For Customer you go to FDI4, for vendor you go to FKI4 for forms.
    Remaining all are the same.
    Hello,
    Go to transaction code FDI4
    Select Form Type RFFRRD20 Line item analysis
    Give your form name and description
    Structure (Two axis) - as defaulted
    Click on Create
    You will have lead column
    Delete the rows 2, 3 and 4
    Double click on column 1
    Enter the customer numbers from 1 to 999999
    First column double click (A)
    Slelect following values
    Due date analysis 1
    Days for net due date 0 to 30
    Give the short name, medium name and long text for the column.
    Repeat this step in next columns like 31 to 60, 61 to 90, 91 to 120 and 121 to 99999 days etc in other columns and select due date analysis 1. (B,C,D,E)
    Create one more column by way of formula. To create a new column you need to double click on blue line. Put formula add all five columns you have created above. (F = ABCDE)
    You prepare one more column with
    Due date analysis 2 (G)
    Now you prepare one more column add (F+G) = This will be total open items = over due and not due.
    Now go to FDI1 and prepare a report - assign the form created in FDI4 to the report.
    Characteristics you need to select are
    Account Type (Select Account Type as D for customers)
    Currency
    Customer
    Document Type
    Special G/L Ind
    Company Code
    Change the output types and options according to your requirement.
    Refer FDI2 and FDI3 for other standard reports created.
    Refer FDI5 and FDI6 for other standard forms created.
    Save your report and execute.
    From there you can put the cursor on customer number and from the menu goto -> line items then it will go for each line item wise..
    Regards,
    Nauma

  • Aging report for Open Invoice

    Hi All,
    I need to develop an Aging report for open invoice, there is no indication for open invoice or close invoice since we are using customise DS and DS from third party system. only one key flag we have is clearing date. so kindly let me know how to write the logic for this requirement.. can I use Customer exit for this? I have an Idea to do like
    first logic is
    *If Clearing date = blank than invoice is = open (by using of this logic we can get all open invoice).
    second logic
    total number of invoice = current date - document date.
    but I do not know how to implement this logic in BEx hnece kinnly advice me whether this logic can be work or suggest with different solution ples..
    Regards,

    hi,
    You can  check few default PO reports wid proper paramater in it
    or
    Can check table EKBE
    or
    Check PO history in the PO doc
    Or
    Check the ME80FN
    Regards
    Priyanka.P

  • Can using query create aging report for GL Account

    Hi all expert,
    I have a challenge scenario which customer request print out aging report for the following GL Account.
    This is not a business partner account. However, customer want display like aging report.
    30 days aging report for the following GL accounts by projects:-
         i)     WIP (Work In Progress) account
         ii)     Accrued Revenue account
         iii)     Accrued Cost account
    Examples:
                            Current Balance       30 day   60 day  90 day   120 day
    Account  WIP         10000               2000        3000      5000     0
    Any idea or example given? If yes, can you provide a query here?
    Regards,
    Eric Tan

    Hi Eric
    In standard SAP Business One this is difficult as the reports are 2 dimensional. To achieve this you will need to write multiple select statements into a temporary table and then select the final result from the temp table. Here is a sample for you to test:
    USE [*DATABASE_NAME*]
    GO
    /****** Object:  StoredProcedure [dbo].[REPORT_NAME]    Script Date: 04/24/2009 13:17:21 ******/
    SET ANSI_NULLS ON
    GO
    SET QUOTED_IDENTIFIER ON
    GO
    CREATE proc [dbo].[*REPORT_NAME*]
    as
    set nocount on
    begin
    DECLARE @Day_no varchar(2)
    DECLARE @Month_no varchar(2)
    DECLARE @Year_no varchar(4)
    DECLARE @Start_Date Datetime
    SET @Day_no = DAY(GetDate())
    SET @Month_no = MONTH(GetDate())
    SET @Year_no = YEAR(GetDate())
    SET @Start_Date = @Year_No + '/' + @Month_no + '/' + @Day_no --  + '/' + @Year_No
    IF OBJECT_ID(N'tempdb..#CRDAGEING', N'U') IS NOT NULL
    drop table #CRDAGEING
    SELECT T0.[CardCode] AS [CardCode], T0.[CardName] AS [CardName], -T0.[Balance] AS [Balance], CAST(0 AS MONEY) AS [Current], CAST(0 AS MONEY) AS [1Week], CAST(0 AS MONEY) AS [2Weeks], CAST(0 AS MONEY) AS [3Weeks], CAST(0 AS MONEY) AS [4Weeks], CAST(0 AS MONEY) AS [5Weeks], CAST(0 AS MONEY) AS [6Weeks], CAST(0 AS MONEY) AS [Over6Weeks], CAST(0 AS MONEY) AS [Avg3Months], CAST (0 AS MONEY) AS [Onhand] INTO #CRDAGEING FROM OCRD T0 WHERE T0.[CardType] = 'S' -- and T0.[CardCode] <> '' --and T0.[DocDate] >= @FromDate AND T0.[DocDate] <= @ToDate
    INSERT dbo.#CRDAGEING SELECT T1.[ShortName], NULL, 0, -SUM(T1.[BalDueDeb] - T1.[BalDueCred]), 0, 0, 0, 0, 0, 0, 0, 0, 0 FROM JDT1 T1, OCRD T2 WHERE T2.[CardType] = 'S' and T2.[CardCode] = T1.[ShortName] and T1.[DueDate] <= @Start_Date GROUP BY T1.[ShortName]
    INSERT dbo.#CRDAGEING SELECT T1.[ShortName], NULL, 0, 0, -SUM(T1.[BalDueDeb] - T1.[BalDueCred]), 0, 0, 0, 0, 0, 0, 0, 0 FROM JDT1 T1, OCRD T2 WHERE T2.[CardType] = 'S' and T2.[CardCode] = T1.[ShortName] and T1.[DueDate] >= DATEADD(DAY,1,@Start_Date) and T1.[DueDate] <= DATEADD(DAY,8,@Start_Date) GROUP BY T1.[ShortName]
    INSERT dbo.#CRDAGEING SELECT T1.[ShortName], NULL, 0, 0, 0, -SUM(T1.[BalDueDeb] - T1.[BalDueCred]), 0, 0, 0, 0, 0, 0, 0 FROM JDT1 T1, OCRD T2 WHERE T2.[CardType] = 'S' and T2.[CardCode] = T1.[ShortName] and T1.[DueDate] > DATEADD(DAY,8,@Start_Date) and T1.[DueDate] <= DATEADD(DAY,15,@Start_Date) GROUP BY T1.[ShortName]
    INSERT dbo.#CRDAGEING SELECT T1.[ShortName], NULL, 0, 0, 0, 0, -SUM(T1.[BalDueDeb] - T1.[BalDueCred]), 0, 0, 0, 0, 0, 0 FROM JDT1 T1, OCRD T2 WHERE T2.[CardType] = 'S' and T2.[CardCode] = T1.[ShortName] and T1.[DueDate] > DATEADD(DAY,15,@Start_Date) and T1.[DueDate] <= DATEADD(DAY,22,@Start_Date) GROUP BY T1.[ShortName]
    INSERT dbo.#CRDAGEING SELECT T1.[ShortName], NULL, 0, 0, 0, 0, 0, -SUM(T1.[BalDueDeb] - T1.[BalDueCred]), 0, 0, 0, 0, 0 FROM JDT1 T1, OCRD T2 WHERE T2.[CardType] = 'S' and T2.[CardCode] = T1.[ShortName] and T1.[DueDate] > DATEADD(DAY,22,@Start_Date) and T1.[DueDate] <= DATEADD(DAY,29,@Start_Date) GROUP BY T1.[ShortName]
    INSERT dbo.#CRDAGEING SELECT T1.[ShortName], NULL, 0, 0, 0, 0, 0, 0, -SUM(T1.[BalDueDeb] - T1.[BalDueCred]), 0, 0, 0, 0 FROM JDT1 T1, OCRD T2 WHERE T2.[CardType] = 'S' and T2.[CardCode] = T1.[ShortName] and T1.[DueDate] > DATEADD(DAY,29,@Start_Date) and T1.[DueDate] <= DATEADD(DAY,36,@Start_Date) GROUP BY T1.[ShortName]
    INSERT dbo.#CRDAGEING SELECT T1.[ShortName], NULL, 0, 0, 0, 0, 0, 0, 0, -SUM(T1.[BalDueDeb] - T1.[BalDueCred]), 0, 0, 0 FROM JDT1 T1, OCRD T2 WHERE T2.[CardType] = 'S' and T2.[CardCode] = T1.[ShortName] and T1.[DueDate] > DATEADD(DAY,36,@Start_Date) and T1.[DueDate] <= DATEADD(DAY,43,@Start_Date) GROUP BY T1.[ShortName]
    INSERT dbo.#CRDAGEING SELECT T1.[ShortName], NULL, 0, 0, 0, 0, 0, 0, 0, 0, -SUM(T1.[BalDueDeb] - T1.[BalDueCred]), 0, 0 FROM JDT1 T1, OCRD T2 WHERE T2.[CardType] = 'S' and T2.[CardCode] = T1.[ShortName] and T1.[DueDate] > DATEADD(DAY,43,@Start_Date)  GROUP BY T1.[ShortName]
    SELECT SR.[CardCode], MAX(SR.[CardName]), SUM(SR.[Balance]) AS [BalanceOwing], SUM(SR.[Current]) AS [Current], SUM(SR.[1Week]) AS [1Week], SUM(SR.[2Weeks]) AS [2Weeks], SUM(SR.[3Weeks]) AS [3Weeks], SUM(SR.[4Weeks]) AS [4Weeks], SUM(SR.[5Weeks]) AS [5Weeks], SUM(SR.[6Weeks]) AS [6Weeks], SUM(SR.[Over6Weeks]) AS [Over6Weeks] FROM dbo.#CRDAGEING SR GROUP BY SR.[CardCode] ORDER BY SR.[CardCode]
    END
    Go to Microsoft SQL Studio manager and select your company database. Then expand the list and select Programmability > Stored Procedures. Right click on Stored Procedures and select New Stored Procedure. Copy the above code over the code in the edit window and change the database name as well as report name. Then select Execute to create the stored procedure. If you make changes, remember to change the word CREATE to ALTER (with other words CREATE for the first execute, and ALTER thereafter). Then in SAP Business One create a new query and leave everything blank. Click on execute and select the pencil to change to edit mode. Remove the words SELECT and type in EXEC REPORT_NAME (change the REPORT_NAME to the name you used in SQL). Then execute again and the results will be displayed in SAP Business One.
    Let me know if you get stuck. Remember the above is an example and will need to be changed to use your tables and fields as required. The basic idea is to move across by one column with each select statement. So for example the first select statement does the CURRENT column, the second one the 30DAYS column, and so on.
    Kind regards
    Peter Juby

  • Aging Report for Multicurrency Customers

    Dear all,
    We have some customers whose BP Currency have been set to 'all currency' and they have transactions in both our local and foreign currencies.
    The customer aging report displays the balances only recalculated at the aging date's exchange rate. How can we have the customer aging report to display document currency transactions?
    Kind Regards,
    Asif

    Hi Asif,
    all transactions for a BP that is defined to use 'Multicurrency' (MC) is held in local currency (LC), the display of the amounts in another currency is simply that, a display according to the exchange rate for that posting date. Therfore, only the LC is relevant for the ageing report. You may, however, choose to display the ageing report in any given currency that you have defined.
    All the best,
    Kerstin

  • Aging Report for consolidating Business Partners

    I have a customer that is using consolidation functionality for its vendors. The BP parent it is set as multicurrency, the childrenu2019s for this parent are set with a different currency (USD, CAD, RMB etc).  My question is how I can obtain a proper aging report for this consolidated BP (by BP children currency) as for now all the transactions are automatically converted in local currency even when Iu2019m selecting the BP currency to display.
    Thank you,
    Alex Corbu

    Hi Alex
    The best would be a query on JDT1 table linked to OINV for example. The problem as you mentioned is that although the document is against the sub account, it is automatically posted against the head account for balance and payment purposes. In the journal file it only keeps the Head account and not the sub accounts. In OINV (and other marketing documents) you can use the FatherCard field to identify the Head account and the CardCode the sub account. These will of course be linked by the Document number from OINV and the Ref1 from JDT1.
    The above is assuming you need the information exactly the same as the ageing, as the ageing is by default pulled from the Journal tables. You could simplify this by using just the OINV table. Remember that the balance is made up of Invoices less Credit Notes, so in this instance it would be OINV minus ORIN entries.
    Hope the above all makes sense, if not just ask.
    Kind regards
    Peter Juby

  • SGD Exchange Rate Difference JE appears in Customer Aging Report

    Dear Experts,
    SAP Version: 8.81
    Local Currency: SGD
    We perform Exchange Rate Difference for a USD BP to calculate the unrealized gain/loss during month-end, JE created successfully.
    Next, we go to Customer Aging Report and select this USD BP.
    When i choose to view the Aging Report in Local Currency, the USD Invoice will appear in SGD + Exchange Rate Difference JE in SGD, the total balance can appear in SGD with no problem.
    When i choose to view the Aging Report in BP Currency, the USD Invoice will appear in USD + Exchange Rate Difference JE in SGD, i can't see the total balance as it is appeared as xxxxx.
    Above is the behaviour in 881.
    Last time in SAP 2005, when i choose to view the Aging Report in BP Currency, the Exchange Rate Difference JE in SGD will not appear, therefore i can see the total balance in USD.
    What is your opinion about the behavior in 881? Will you consider it as design or issue?
    Thanks.
    Regards,
    Lay Chin

    Dear all,
    This problem is no longer there when upgrade to 881 Patch 08.
    Regards,
    Lay Chin

  • Asking Exchange rate at the time of Customer aging report

    Dear All,
    I am facing one problem, when I am asking customer aging report the system is asking to enter exchange rate.but at the time of vendor aging is working fine does not asking any exchange rate,this problem happens only one specific  user, not for other users.
    In other users it is working fine.Do we need to do any configuration for that user for working this customer aging report.
    Please give solution as soon as possible
    Thanks advance.
    Regards
    Komanduri.

    We faced the same problem today.
    Finally, we found out the user accidentally selected the currency which we didn't set the exchange rate in the aging report.
    After the aging report is generated, we can change the currency in the upper left corner.
    If we didn't set the rate of that currency, it will keep asking.
    Even if we close the aging report and open again, it  will still ask for that currency before it could generate the report
    When we set the rate of that currency, it will not ask exchange rate again

  • Customer Aging Report Query (without invoices offset by incoming payment)

    Hi All Experts,
    May I know is there any field from JDT1 mention which invoices is already offset by the Incoming payment or AR Credit note? Because I do not want those invoices that already offset by incoming payment appear at the Customer Aging Report. Meaning, the data appear in the Customer Aging Report is only show those invoices that yet to pay by the customer. Kindly give some advise on it. Thanks a lot.
    Thanks and regards,
    Angie Ng

    Hi David,
    Thanks for your suggestion. I have try it, but all of my JDT1.IntrnMatch is in 0 value. Meaning in my situation it is none of any reconcilliation making. But from my SBO window, i manage to see that actually this incoming payment is pay for which invoices. Problem is it is difficult for me to do the possiblity logic that might be happen in my Customer Aging Report Query. Please give some advise that how to show only those invoices yet to pay? The current query will show all the data no matter the invoices or credit memo has been offset.
    select OCRD.cardcode 'Supplier Code',OCRD.cardname 'Name',sysdeb  'Debit GBP',syscred 'Credit GBP',
    case JDT1.transtype
    when '13' then 'INV'
    when '14' then 'AR CN'
    when '24' then 'INCOMING'
    else 'Other'
    end 'Type',
    Ref1,
    fccurrency 'BP Currency',
    CONVERT(VARCHAR(10), refdate, 103)'Posting Date' ,
    CONVERT(VARCHAR(10), duedate, 103) 'Due Date',
    CONVERT(VARCHAR(10), taxdate, 103) 'Doc Date' ,
    CASE
    when (DATEDIFF(dd,refdate,current_timestamp))+1 < 31
    then
    case
    when syscred <> 0 then syscred * - 1
    else sysdeb
    end
    end "0-30 days",
    case when ((datediff(dd,refdate,current_timestamp))+1 > 30
    and (datediff(dd,refdate,current_timestamp))+1< 61)
    then
    case
    when syscred <> 0 then syscred * - 1
    else sysdeb
    end
    end "31 to 60 days",
    case when ((datediff(dd,refdate,current_timestamp))+1 > 60
    and (datediff(dd,refdate,current_timestamp))+1< 91)
    then
    case
    when syscred <> 0 then syscred * - 1
    else sysdeb
    end
    end "61 to 90 days",
    CASE
    when (DATEDIFF(dd,refdate,current_timestamp))+1 > 90
    then
    case
    when syscred= 0 then sysdeb
    when sysdeb= 0 then syscred * - 1
    end
    end "90 + days"
    from JDT1,OCRD where JDT1.shortname = OCRD.cardcode and cardtype = 'c' and intrnmatch = '0'
    ORDER BY OCRD.CARDCODE, taxdate

  • Customer Aging Report

    Hi all,
    Our client requires aging report
    for a customer in the following format
    Customer Code,Name,0-30 Days,31-60 days,61-90 days,
    91-120 days,121-150 days,151-180 days,180 + above days,Row Total (all days).
    Condition:  By Aging date
    Thanks
    Jeyakanthan

    Hi Jeyakanthan,
    SAP Business One displays the relevant open receivables in four columns for the time interval for customer aging report.
    The fourth column includes open receivables for the days/months/periods prior to the first three columns. For more information please refer to the explanation for 'Time Intervals' field in Online help.
    Based on the testing in 2007 version, it is improved that there is one more column added there, which means if you set 'Time Intervals' as month, you may get five columns in aging report, the first four columns are for 4 months and the last column shows open receivables for the months prior to the first four columns.
    Regards,
    Van Xue
    SAP Business One Forums Team

  • Customer Aging Report. Pl help me in this issue.

    Problem in Customer Aging Report.
    1. No concrete solution given to take project wise, bill wise. 2. Opening dues break up - project wise. Bill wise. 3. Aging days not able to select the required interval. Only standard intervals are available. 4. How to find the exact payment payable/ receivable for an vendor/customer.

    Hi Arun...........
    You can get the invoice wise aging. Once you run aging report you have to only double click on the sequence no grid.
    Hope this will solve the issue........
    Regards,
    Rahul

Maybe you are looking for