Ageing Buckets for whole query

Dear All,
I have to make a BEx query on meter characteristics. No keyfigures
The whole information should shown against buckets (current date - disconnection date of meter)
0-30 days     Customer     Meter No     Meter Type     Zone
31-60 days   Customer     Meter no.     Meter Type     Zone.
I tried making selections with disconnection date (0calday value range variable 0dat-30to 0dat-0    and   0dat-60 to 0dat-31). I included a dummy keyfigure (disconnection amount) in selection
But data isn't coming according to conditions. Any suggestions please.
Regards,
Cleo

Cleo,can you please clarify what exactly you need to show in those bucket range.
I understand you have disconnection date in your provider and for current date you can use sap standard formula variable i.e 0F_ADAY.
Now to get the difference between the two,if disconnection date is of type char.then you need to convert the same into kf for getting the difference with the help of replacement path.
Note:It is mandatory to keep that date in rows which you use as reference char.in formula variable otherwise it will not work.
Please check the above points.
Regards,
AL

Similar Messages

Aging buckets in a query

Hi gurus,
I am creating an A/R aging queries to age open items in 30days buckets( 0-30days, 31-60days,61-90 days and 91days+).My logic for each buckets is below ..
eg -- 31-60days bucket (Key fig)- Item status- Open
                                                 Posting date - <= posting date(Variable)
                                                 Net due date - btw -31 to -60 days, using offsets
                                                                       on the key due date variable
                              (2nd Key fig)- Posting date- <= Posting date(variable)
                                                  Net due date - btw -31 to -60 days, using offsets
                                                                       on the key due date variable
                                                  Clearing date-- > Clearing date
Then for the 31-60 days bucket, I now add both key figures together.
The logic is working fine but I just found out that there are a few plants that the buckets are not aging the data correctly like it is in R/3 because some of the customers make partial payment and in R/3 they are moved from an aging bucket to a current one after the partial payment has been made,but BW is looking at the original invoice posting date and not recognising the date that the partial payment was made.
How do I make BW to recognise the partial payment date when a partial payment has been made for the aging instead of the original posting date?
I hope this was not too confusing.
Thanks

Hi Kartikey,
Thanks for the response. I am not calculating the subtotals at the in the query definition and the sub totals are based on the info object 0customer's setting in the query designer to suppress the result rows. In RSRT also I am unable to get the sub totals.
If I remove the calculations (aging buckets) and display direct key figure in the columns, I am able to get the sub totals.
Is there any specific reason why the sub totals can not be calculated if the columns are calculated key figures/new formula.
Can any one let me know how to fix the sub totals.
Thanks

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

Customize AP Trial Balance XML Data Definition for adding Aging Buckets

Hi
I have to customize AP Trial Balance Report XML Data Definition Template for adding Aging Buckets & Supplier details in R12 , Could you let me know how i can modify XML file?
Thanks
Pravin

Hi,
My requirement is different from the one which is in below link.
I need to add Aging Buckets & Supplier details to AP Trial Balance report (R12) , here i need to modify the XML Data definition template.
Please help me, very urgent.
Thanks
Pravin

Xml parsing error while selecting whole result set for sql query

Hi All,
I am having xml parsing error while selecting whole query result set. The data is coming fine for default result set of 50 rows.
My exception is below.
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00234: namespace prefix "xsi" is not declared
Error at line 1
ORA-06512: at "SYS.XMLTYPE", line 254
ORA-06512: at line 1
*31011. 00000 - "XML parsing failed"*
**Cause: XML parser returned an error while trying to parse the document.*
**Action: Check if the document to be parsed is valid.*
My sql query is below that is giving results for default result set of 50 rows.
select extract(xmlType(clob_xml_colm_name), '//v2:node1//childnode/text()','xmlns:v2="namespace_url"').getStringVal() from table_name
My sql developer version is below.
Java(TM) Platform     1.7.0_04
Oracle IDE     3.1.07.42
Versioning Support     3.1.07.42
My database version is below.
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit
Please could any one help me urgently as the sql query is supposed to be correct as it is returning query results, but the problem happening when i try to select whole result set.
Thanks and regards,

What does the XML look like? It appears that some of the supposed XML stored as a CLOB is not really valid XML. Find the row in the table that is causing your issue and review the "XML" in it.

Create aging bucket in BEx - based on date variable

Hi everyone,
I have a report for which we need to create account receivable aging bucket to classify arrears (1>29 / 30>59 / etcu2026).
Our solution overall architecture is the following :
Source System (SAP) > BW back end...Multiprovider > Super BEx Query > Universe > Webi Report
BW 7.0
BO XI 3.2 SP3.0
In this report, each bucket is defined by the difference between:
-     the Net Due Date (which is the due date of payment of the invoice)
-     and the Current Date (date for which the report is run u2013 can be the date of the day or a date in the past)
We can develop this either in BEx or in Webi, but to avoid potential performance issues in Webi, we take the try to develop this in BEx.
As you can easily imagine, this BEx query will be used for many reportsu2026so not only for this specific report.
What weu2019ve done so far:
1-     We created a variable to prompt the user with the date he wants to run the report for
           - ZTEST is an optional variable, single value, User input, based on characteristic 0CALDAY
2-     We developed RKF in BEx
-     Key Figure restricted by Amount
-     Net Due Date restricted by the variable ZTEST using the between function and an offset (to determine the range)
=> When we save the query we are getting a warning message saying u201CVariable ZTEST for characteristic Net Due Date has been converted to a required entryu201D
Why? (you probably knowu2026) Because my RKF is using a variable with an offsetu2026which automatically turn on my variable as mandatory and no more as optional.
Consequences:
-     In BEx: My variable, which is required to be optional (because we donu2019t have to have this field as mandatory for each and every report running on top of this query) is now mandatory.
-     In Webi: If I use the variable (funnel in webi), my report is working fineu2026but if I donu2019t use it in the webi report, I get an error message saying u201Cvalue required for ZTESTu201D
o     Funnel is configured as optional in the universe designer (so the issue is not coming from here)
=> 2 consequencesu2026same issue
Question: What can we do to keep our bucket logic running in BEx and avoid this variable to become mandatory?
Solutions (potential)
-     Create a custom exit routine to work around this issue u2013 how?
-     Create CKF/Custom exit to create our bucket (using ZTEST as an entry value to determine the range) and then use the created range in our RKF to restrict the amount u2013 how? Not so easyu2026
-     Build the logic in Webi
-     Any other suggestions?
Here we are, any advice would be really appreciated
Thank you guys
Regards
Henri

Hi peeps,
We finally find a solution for this problem! So I can share it with you.
The overall solution is pretty easy to understand.
1st step is to prompt with the user with a 0DATE variable. The date selected becomes a date input for the next step.
The variables is defined as a range [01/01/1900;variable_value)...in order to retrieve the right data set.
2nd step is to use this date to create our aging bucket, dates range.
To do so, we created 4 user exit variables (for each aging bucket).
3rd step is to use these ranges in RKF.
This way you get aging bucket dynamically defined by the user input pretty cool!
Regards
H

Vendor ageing report for down payment bucketwise

Hi
I have paid many downpayment to various vendors. Now i want the ageing report for the same (i.e. bucket wise i.e. 0-30 days, 31-60 days and so on).
This i am getting for vendor invoices in TCode: S_ALR_87012085 (Vendor payment history with OI sorted list).
Please let me know if the bucketwise report is possible for the downpayment too.

Hi,
Vendor ageing for down payments as well as invoice i use to see from T.code FBL1N by creating layouts.
Choose Arreas after net due date from layout and for that column you can apply a rule that from 0 to Lessthan or equal to 30.
Like that you can create the layouts. In FBL1N you can give this layout (down) so information come in that format.
The one disadvantage is that you have to select manually the layouts and you can see only one ageing information at a time.
Regards,
Sankar

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

Inventory ageing report for batches

Hi Experts,
I am looking for a ageing report for batches. MC46 and MC50 is not displaying the batches which is my main requirement. I learnt that its not available in standard SAP. I am planning to develop a Zreport which is a copy/reference of MC46 and MC50.
If you ever come across this situation before, which approach you followed? I appreciate if you throw some thoughts on builiding a query or Zreport or any logics.
Regards,
R.S

Hi Shiva,
Thanks for the information. We are not using SLED for the batches and BMBC is just a **** pit where you can use it as work list when you try to change mass batches. I dont know how BMBC helps in fetching a report for ageing.
Regards,
R.S

How can the dunning letter shows O/S amt and corresponding aging bucket?

Hi,
I am going to implement the dunning letter setup in R12. Our user request to have the dunnng letter layout which should show all regular dunning details but also the aging info of the outstanding invoices, i.e. which aging bucket the outstanding amount will be shown. Anybody have idea and help? Thanks a lot.
Edmond

Thank you Nagarajan. I have a dunning letter created in Crystal Reports for our client. It is fairly limited in scope, it just has the customer name and address, invoice numbers and dates, amounts due and the text they wanted in it.
I can import it into B1 9.0 and set it as the default for Dunning Letter #1 and it runs, but unlike other formats where there is a DocEntry and/or ObjectID and a ?DocKey@ or ?ObjectId@ parameter, how do I limit the report to just one customer? Typical document layouts run for the document that's on the screen. In the dunning process, the report runs once for every customer when the Dunning Letter Method is set to "One Letter per BP". I have to limit the report to one customer at a time. Right now, each dunning letter based on the Crystal report is identical and it contains all the data for every customer.
So, does anyone have any ideas for what selection criteria needs to be included in the Crystal report to have it select just one customer from the dunning wizard tables? Thanks.
Michael
Edit: I created a ?WizardID@ parameter and a ?CardCode@ parameter to limit the report to a single dunning wizard event and a single customer. While it works fine in Crystal itself, it doesn't work in B1 at all. I had thought that by limiting the report in this way, it would only create dunning letters for a single customer.

AR - Aging Bucket report Customisation

I have a requirement from end users to be able to run an aged debt report for any date range in the past e.g. From 01-Jan-2008 to 01-Jan-2013.
Aging Bucket report only has, "As of date" field in the parameters.
Is it possible to add additional parameters to this report?

Hi.
I don't believe such parameter can be included in the Aging reports. According to the user manual, the design of the report is to:
Receivables includes all open items whose GL date is before or the same as the date you enter, and whose GL date closed is after the date you enter. The default is the current date.
Besides, such parameter would cause debts to be excluded from the balance.
Octavio

Age Analysis for a GL account?

Hie All
Good day, I have a client who has a unique requirement. They have a general ledger account which shows all Downpayments made. The client requires this account to produce an age analysis for each line item. Is this possible if so how can I achieve that?
Thanks

Hi
Thanks for the response but I might need your assistance on how to write the query, as you said it doesn't sound simple.
Just as a background the account in question is a balance sheet account (asset) linked to business Partner records on the accounting tab Down payments clearing account. When a down payment invoice is raised a DR is created on the down payments clearing account. This is the amount they require to age.

Cusomter aging bucket

Hello,
we are trying to print customer aging bucket on monthly statement by print program RFKORD10. in customer due date list, i entered the break down days as 30, 60, 90 and etc. But when i run RFKORD10, the structure RF140 is not updated with the breakdown amount I am looking for. Is there any specific step I have to go through to have the RF140 updated correctly? or how I can make the aging bucket works by the standard print program?
thanks,

there is no specific setting for this aging program.
its just a standard program by SAP.
for more information, just click on the 'i' icon in the program execution screen.
Regards
Anantha

Calculated Age and Age Ranges in a Query

Hello,
We are using 3.5 Query Designer.
I am trying to create age ranges in a query. The InfoProvider at this point (I've gone very simple) is InfoObject, 0PERSON.
I've created a calculated key figure (CKF) called age which I have used a formula to define. The age is calculating correctly. Age has 'Calculate Result As...' = Summation. And in the 'Enhance', 'Time of Calculation' is set to Before aggregation. Number of decimal places set to 0. Now I've created a CKF, AGE_GE_40 which has as its formula 'COUNT(('Age' >= 40)). I've created an additional CKF, AGE_LE_39 which has a formula 'COUNT(('Age'<=39))'. Both of these have the 'Summation' set in the calculation section. The query contains 0GENDER, 0PERSON with AGE_GE_40 and AGE_LE_39 and Number of records as the key figures in the columns. When executed initially, all of the result rows are correct. The problem is when I remove 0PERSON, the result rows only give me 1 per gender. This seems like an easy thing to do, why is it not working?
Thanks for any help,
Diane Merrill

Diane,
For each row in the query data, there is only one age value calculated, which is the aggregration of all records which fulfills the row's characteristic value combination. Thus, when there is Gender & Person columns in the query, each row calculates an age value for the Gender/Person combination, which is essentially the same as for each person, because each person has one gender value. However, when you remove person from the columns, there will be only two values for gender, and the age is calculated as the sum of ages for all records with the same gender value. To reveal more on this, you can add the Age key figure into the query columns, and run the query with only the gender (i.e. without person). Once you see the age value for each row, it should be clear to you.
Please reward points if this is helpful.
Wayne

How to cumulate key figure for whole fiscal year with one time variable?

Hello everybody!
I have a problem creating a query that allows to get cumulated key figure for <b>whole fiscal year</b> (FY), when I actualy type <b>only last period</b> for the FY.
The query itself is very simple:
- I have "Organization" characteristic in "Rows" section
- I have one key figure "Number of invoices" in "Columns"
- I have "Fiscal year variant" 0FISCVARNT defined in "Filter" that has 12 periods within Fiscal year
and then
- in section "Free Characteristics" I have "Fiscal year/period" 0FISCPER.
I want to be able to provide ONE single value when run query, which is last period of a FY (like 012/2003), but then in report see cummulated number of invoices for WHOLE fiscal year.
Will appreciate any help!
Vitaliy

Please see the white paper entitled "How to... Derive a Variable value from another variable 2.x (pdf)".
Regards,
Troy

Ageing Buckets for whole query

Similar Messages

Maybe you are looking for