Customer Aging Report by Highest Due Sorted List
Hi
Can any one tell me is there any report where i get Customer Aging Details like S_ALR_87012178 - Customer Open Item Analysis by Balance of Overdue Items. and sorted by highest Due balance Accounts first rather than by Account No.
Thanks
Sivaram
You can get this in evaluations F.30, however I think the report you mention can be sorted by the highest outstanding amount.
You cannot however in the report you mentioned sort it by say highest amount over 30 days which you can in evalutions.
Use the search option in the forum about how to create evaluations, I have posted some stuff on it before.
Similar Messages
-
SAP Query (SQ01) Customer ageing report
Dear All,
My Customer want Customer ageing report only for" Due amount" open document in Sq01.Customer ageing report based on Document date+Payment term.
thanking you,
Rupang shahHi
We also required the same. Since no standard report available, we have developed ABAP report for the same.
regards
Ravi -
Dear All,
I checked in SCN and did not find answer for my query so posting here.
This is with reference to customer ageing report,
we are developing z report for customer ageing since we could not get customer specific report either through standard transaction or FDI4/FDI0 level.
So, we are developing Z report for customer ageing.
My doubt is, case where Customer is also a vendor
in BSID table we can get customer open item balances. which means due and not due balances. This is clear.
but how to bring Net off balances (customer open items - vendor open items) into ageing report like (0-30, 31-60, 61-90, 91-120 & >120).
Kindly share the ideas to get net off balances into ageing.
also let me know how would I confirm that my zreport showing the correct values.
Thanks in advance.
Regards,
GaneshIn simple terminology ageing analysis is
Listing of amounts due to the business (by debtors) by splitting them into different categories based on how old the debts are.
In SAP you could view the Ageing reports of Debtors in the easy access. The path being
Financial Accounting-aAccounts Receivable-Information System-Reports for Accounts ReceivableAccounting-Customer Balances
Thanks & Regards
phaneendra -
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 NgHi 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 -
Hi Friends,
As per my knowledge,Customer Aging Report consider only those documents(ar invoice,ar downpayment,incoming payment-payment on a/c,ar credit memo) which are open and showing balance due and standalone JE against Customer.
As I cross checked,I found those standalone JE where Customer and round off account are considered as debit,credit are not considered by 'Customer Aging report'.
So,I just want to know what are all the logic based on which SAP B1 standard report 'Customer Aging ' (without reconciled transaction ) consider the documents????Which SAP B1 Version and Patch is under use at your end ?
There were issues in SAP B1 regarding reconcilliations in versions prior to 2007 series.
Samir Gandhi -
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 AMUse the development tools available to you - the transaction and a sample account is all you need. Debug, ST05, SE30, etc....
-
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 AMHi,
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 -
Regarding Customer ageing report logic in R/3.
Dear
Experts
i have requirement to develop customer ageing report logic for input 30,60,90,180,360
i don' t have any idea hw can i take these values in input& hw can i caluclate the values
i searched in sdn, i did n't get any suitable answer..
Regards
SpandanaHello,
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.
Regards,
Ravi -
Customer aging report - receipts also displayed
hi all,
Customer aging report is showing all outstandings &
also receipts from customer,
we want only customer outstanding in intervals of days ?
JeyakanthanHi Jeyakanthan,
I take it you are using a version prior to 2007.
When you run your ageing report by journal entries, B1 will show you the full amount as due for all partially paid invoices & also, in another row, the actual partial payment. This is due to the 2 different reconciliation engines. You need to manually reconcile the invoices with the partial payments, then they will no longer appear in the ageing by journal entry.
To determine which payments belong to which invoice, you could run the report by marketing documents. There B1 will show you the remaining outstanding amounts only, from which you can deduct the payment(s) & thence reconcile the correct documents.
As a rule, SAP recommends to only run the ageing reports by journal entry.
If you are looking for more info on reconciliation, please have a look at the IRU landing page:
http://service.sap.com/~sapidb/011000358700000380562007E
All the best,
Kerstin -
180 days - customer aging report
Hi Experts,
I'm required to revise the Customer Receivable Aging Report from Business Partners > Business Partner Reports > Aging > Customer Receivable Aging. the Standard report shows only up to 120+ days. We require 180+ days. Could you help me with the work around on this.Hi Sachin,
Could you please send your SQL (and maybe also Crystal Report) for SAP B1 "Customer Aging Report" to me too?
I am trying to write the SQL which will mimic the SAP B1 standard report, and then add a few more fields because Management wants these.I need to do a lot of Excel gymnastics each time I produce an ageing. I am looking for an SQL Query that will give the same total as the standard report. It must also list all outstanding invoices individually and their amounts, as well as all other unreconciled items.
Send me what you have (SQL). I'll try to modify it to suit my requirements. As I'm newbee, it is much easier for me to start from some existing code.
Thanks a lot
LEONLAI -
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
RekhaIf 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 -
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 ChinDear 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 -
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
JeyakanthanHi 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
-
How do I remove my credit card from an apple id account that I'm locked out of?
I had set up two step verification and through every fault of my own, i lost, misplaced, hid, and or burned the recovery key while at the same time forgetting which of the 10,000 passwords i commonly use. No i can not guess the Pass word and no ther
-
Can't create Connection to Oracle Database
Hi i'm trying to create a simple connection to my oracle database and my projects compiles, but at the "createConnection" statement an SQLException is thrown. Well first of all my stats: Windows XP 32 bit Visual Studio 2005 (VC++ 8) Oracle Database 1
-
Hardware sizing recommendations for B2B Server
My customer Welch Foods Inc. is on 11i Oracle eBusiness Suite and is planning to uptake the latest 1Sync integration features in the PIM product. For out-of-box AS2 connectivity with 1Sync - they are planning to use Oracle B2B Integration Server 10.1
-
Is it possible to make a screenshot like in windows
^?
-
Infotype 17getting updated automatically
I dont understand what is causing infotype 17 (travel privilege) to get updated automatically. Users are claiming that after entering trip request using "trip" when they go to enter traval claims (pr05) the system is throwing this error message "erro