Date Difference in Report

Dear All,
How to calculate the number of days (Difference between start date and current date) in report. How to define the key figure for the same.
Thanks in advance.

Hi,
If you want to do the arethmatioc operations with the date then you will have to declare the date as key figure in the cube and add it there and then update it with the date from R/3.
You can use formula variable for this subtraction.
Create a formula in the bex analyzer and then in the down you will get option for the formula varibale.Just make a replacement path varibale on this time characteristic for which yuou want subtraction.
During creation use "key" in the display and "number" as the data type.
If number is not working them you can use "date" type.
Nothing alse needs to be done during the variable creation.
Once you have made the formula inlcude it in the columns of the report.
Thanks

Similar Messages

Calculation of % on Date Differences - BW Reporting

Hi Experts,
I have a typical scenario where in I need to calculate the % for the no of Days difference b/t 3 dates(Statistical Date, Delivery Date, GR Date).
As of now I just showed just the Difference b/t all the 3 dates in no of days. Now I need to acomplish the below task, Can any one plese suggest me how to proceed to resolve all the below conditions.
Need to provide the % of orders that fall into the following buckets for each of the above 3 Dates only in Reporting.
1. On time = +/- 5 days
2. Greater than 6-10 days late
3. 11-15 days late
4. Greater than 16 days late
5. 6-10 early
6. 11-15 days early
7. Greater than 16 days early
I need to do this at Query level only as I don't have authorization to create a new Calculated Key figures or Restricted KF.
Only I can do is play around with the New Selection or New Formula at Column area of designer, write some Macros or can access Exceptional reporting for above 3 DATE Char or Key Figure fields and do some math to accomplish.
Thanks,
Sam

Hi Nagesh,
     Thanks for your quick reply, I can say I tried with couple of options and couldn't
   suceed with the minimal access which I do have.
     Now I don't have much time to respond to user, If at all you do have and time
    and if you don't mine can you please look at the conditions and just give me the
    STEP1....STEPN for any one of the 3 diff types which you mentioned in your
    reply so that I can take it up from there.
Sample Days Difference in my spread sheet now:-
Stat-Del Date Diff Stat-GR Date Diff Del Date-GRDate Diff
-67             68                       -68
-112                160                       -160
-109                109                       -109
-109                109                       -109
0                1                                        -1
    Please take any one date and do write down the step1..stepN if you have time.
Sam

Query report with date difference.

Hi Expert,
I'm using below query to monitor unreleased checks. we have a policy that the holding period for unreleased check is 5 working days.
SELECT T2.[CardCode], T2.[CardName], T0.[TransId], T0.[DueDate], T1.[Credit], T1.[U_DisBank], T4.[Name], DateDiff(dd,T0.[DueDate],GetDate()) As 'OverDue Days' FROM OJDT T0 INNER JOIN JDT1 T1 ON T0.TransId = T1.TransId INNER JOIN OCRD T2 ON T1.ShortName = T2.CardCode INNER JOIN "@HOFFICE" T4 ON T1.U_Disbank = T4.Code WHERE T1.[Credit] !=0 AND T0.[DueDate] >=[%0] AND T0.[DueDate] <=[%1] AND T1.[balduedeb]+T1.[balduecred] !=0 ORDER BY T4.[Name]
However I would like to exclude weekends in computing date difference. Can you please help me modify my query code?
Thanks,
Arlmi2000

Hi,
A simple solution will be change DateDiff(dd,T0.DueDate,GetDate()) to DateDiff(dd,T0.DueDate,GetDate())*5/7+1
This can cover all the weekends. If you need to be exact that including public holiday, the coding will be longer.
Thanks,
Gordon

What is difference between report programming and dialog programming?

hi,
what is difference between report programming and dialog programming? plz provide some example code
bye

ABAP programming
Basically reports are used to read database and represent the results in lists.
Reports are collections of processing blocks that the system calls depending on events.
We can use reports to evaluate data from database tables.
Reports are stand alone programs and controlled by events.
A report itself never creates events
steps in report:
Processing the selection screen
Reading the database
Evaluating the data and creating lists
Outputting a list.
1st u write simple logics, after that u can enhance the code as step by step.
http://venus.imp.mx/hilario/Libros/TeachYrslfAbap4/index.htm
http://help.sap.com/saphelp_47x200/helpdata/en/d1/802cfc454211d189710000e8322d00/frameset.htm
http://www.sapdev.co.uk/reporting/reportinghome.htm
Dialog Programming
Structure of a Dialog Program
A dialog program consists of the following basic components:
Screens (dynpros)
Each dialog in an SAP system is controlled by dynpros. A dynpro (DYnamic PROgram) consists of a screen and its flow logic and controls exactly one dialog step. The flow logic determines which processing takes place before displaying the screen (PBO-Process Before Output) and after receiving the entries the user made on the screen (PAI-Process After Input).
The screen layout fixed in the Screen Painter determines the positions of input/output fields, text fields, and graphical elements such as radio buttons and checkboxes. In addition, the Menu Painter allows to store menus, icons, pushbuttons, and function keys in one or more GUI statuses. Dynpros and GUI statuses refer to the ABAP/4 program that control the sequence of the dynpros and GUI statuses at runtime.
ABAP/4 module pool
Each dynpro refers to exactly one ABAP/4 dialog program. Such a dialog program is also called a module pool, since it consists of interactive modules. The flow logic of a dynpro contains calls of modules from the corresponding module pool. Interactive modules called at the PBO event are used to prepare the screen template in accordance to the context, for example by setting field contents or by suppressing fields from the display that are not needed. Interactive modules called at the PAI event are used to check the user input and to trigger appropriate dialog steps, such as the update task.
All dynpros to be called from within one transaction refer to a common module pool. The dynpros of a module pool are numbered. By default, the system stores for each dynpro the dynpro to be displayed next. This dynpro sequence or chain can be linear as well as cyclic. From within a dynpro chain, you can even call another dynpro chain and, after processing it, return to the original chain.
Check this link for basics.
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
Check this link for Dialog Programming/Table Control
http://www.planetsap.com/Tips_and_Tricks.htm#dialog
Check this SAP Help for Dialog Program doc.
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
Check this SAP Help link for Subscreens.
http://help.sap.com/saphelp_nw70/helpdata/en/9f/dbabfe35c111d1829f0000e829fbfe/content.htm
Check this link for subscreen demo program.
http://abapcode.blogspot.com/2007/05/demo-program-to-create-subscreen-in.html
Also check this link too.
http://abapcode.blogspot.com/2007/06/dialog-programming-faq.html
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/frameset.htm
http://sap.mis.cmich.edu/sap-abap/abap09/sld004.htm
http://help.sap.com/saphelp_nw04/helpdata/en/52/670ba2439b11d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/52/670c17439b11d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/52/670c17439b11d1896f0000e8322d00/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9ccf35c111d1829f0000e829fbfe/frameset.htm
http://abapprogramming.blogspot.com/

[APEX 3] Requested source data of the report has been modified

Hello APEX-Friends,
I have a common problem but the situation is a bit different here. Many of you might know the "invalid set of rows requested the source data of the report has been modified" problem. Often it occurs on submit. That means, you have a report, you select rows, you do things, you submit the page and everything blews up.
This is because you enter some values into fields the report depends on and so you modify your report parameters and the source data changes.
But:
In my case I have a dynamically created report that blews up before any submits occur or values change.
My query is a union of two selects. Both query different views. Those views use a date field as parameter and some compare functions.
I read the field with a V-Function i wrapped arround the apex V Function - declared as deterministic. My date compare function is also declared deterministic (I doubt this makes any differences as it might be only important for the optimizer, but as long as I don't know exactly what APEX evaluates, I go for sure).
I ensured, that the date field is set by default with the current date (and that works, because my interactive report initially displays correct data from the current date).
So everything is deterministic and the query must return same results on subsequent calls, but APEX still throws this "source data has changed" error and I am to 99.99% sure, that this cannot be true.
And now the awesome thing about this:
If I change the value of the date field, an javascript performs a submit. The page is reloaded (without resetting pagination!) and everything works fine. I can leave the page, reenter, do things - everything works well.
But if I log into the application and directly move to the corrupted report and try to use the pagination without editing fields or submitting the page the error occurs.
Do you have any Idea what's happing there? I could try to workaround this by submitting the page the first time it's entered to trigger this "mystery submit" that gets everything working. But I would like to understand this issue and have a clean solution.
Thanks in advance,
Mike aka UniversE

Okay, I found a solution, but I do not understand it - it might be a design flaw in APEX.
I mentioned the date field that is used in the query. I also mentioned that it is set with the current date by default. I did not mention how.
There are some possibilities in APEX to do so.
1. Default-Setting in the element properties
2. Static assignment if no value is in session cache
3. Computation before header
I did the first and second.
BUT:
An interactive report seems to work as follows. A query is executed to get all rows of the report. Then a second query is executed to get the rows that shall be displayed. And the order is screwed up, I think.
1. The first report query to get all rows
2. The elements are loaded and set to default values
3. The second report query to get the display rows
And that's the reason why nothing worked. Scince I added a computation before header the date field is set before the report queries are executed and everything works all fine now.
But I think it's a design flaw. Either both queries shall be executed before Regions or afterwards but not split as field values might change when elements are loaded.
Greetings,
UniversE

Error while creating Data Form Definition report from Planning

Hi All,
Working on Planning 11.1.2 (x64)
I tried to generate a Data Form Definition report from Planning and found that I get an error if I select the option "Include member selection list". By going a bit deeper, I realised that it errors for some forms while works fine for others.
I have tried to find any differences in setting or selection between the forms but haven't been able to see anything that struck me as a reason for error.
Help please.
Thanks,
Abhishek

The Planning sysout log says:
[120910_091125126][oracle.apps.xdo.common.xml.XSLTWrapper][EXCEPTION] XSL error:
<Line 1, Column 1068>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 1068>: XML-20250: (Fatal Error) Missing entity 'ThisYear'.
<Line 1, Column 1075>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 1075>: XML-20250: (Fatal Error) Missing entity 'Year2'.
<Line 1, Column 1082>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 1082>: XML-20250: (Fatal Error) Missing entity 'Year3'.
<Line 1, Column 1089>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 1089>: XML-20250: (Fatal Error) Missing entity 'Year4'.
<Line 1, Column 1096>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 1096>: XML-20250: (Fatal Error) Missing entity 'Year5'.
<Line 1, Column 4586>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 4586>: XML-20250: (Fatal Error) Missing entity 'ThisYear'.
<Line 1, Column 4593>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 4593>: XML-20250: (Fatal Error) Missing entity 'Year2'.
<Line 1, Column 4600>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 4600>: XML-20250: (Fatal Error) Missing entity 'Year3'.
<Line 1, Column 4607>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 4607>: XML-20250: (Fatal Error) Missing entity 'Year4'.
<Line 1, Column 4614>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 4614>: XML-20250: (Fatal Error) Missing entity 'Year5'.
<Line 1, Column 12215>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 12215>: XML-20250: (Fatal Error) Missing entity 'ThisYear'.
<Line 1, Column 12222>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 12222>: XML-20250: (Fatal Error) Missing entity 'Year2'.
<Line 1, Column 12229>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 12229>: XML-20250: (Fatal Error) Missing entity 'Year3'.
<Line 1, Column 12236>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 12236>: XML-20250: (Fatal Error) Missing entity 'Year4'.
<Line 1, Column 12243>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 12243>: XML-20250: (Fatal Error) Missing entity 'Year5'.
<Line 1, Column 18528>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 18528>: XML-20250: (Fatal Error) Missing entity 'ThisYear'.
<Line 1, Column 18535>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 18535>: XML-20250: (Fatal Error) Missing entity 'Year2'.
<Line 1, Column 18542>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 18542>: XML-20250: (Fatal Error) Missing entity 'Year3'.
<Line 1, Column 18549>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 18549>: XML-20250: (Fatal Error) Missing entity 'Year4'.
<Line 1, Column 18556>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 18556>: XML-20250: (Fatal Error) Missing entity 'Year5'.
<Line 1, Column 39824>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 39824>: XML-20250: (Fatal Error) Missing entity 'Scenario'.
<Line 1, Column 39905>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 39905>: XML-20250: (Fatal Error) Missing entity 'PriorYear'.
<Line 1, Column 39985>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 39985>: XML-20250: (Fatal Error) Missing entity 'ThisYear'.
<Line 1, Column 39992>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 39992>: XML-20250: (Fatal Error) Missing entity 'Year2'.
<Line 1, Column 39999>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 39999>: XML-20250: (Fatal Error) Missing entity 'Year3'.
<Line 1, Column 40006>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 40006>: XML-20250: (Fatal Error) Missing entity 'Year4'.
<Line 1, Column 40013>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 40013>: XML-20250: (Fatal Error) Missing entity 'Year5'.
<Line 1, Column 41613>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 41613>: XML-20250: (Fatal Error) Missing entity 'CommentYearTarget'.
<Line 1, Column 41702>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 41702>: XML-20250: (Fatal Error) Missing entity 'CommentYearTarget'.
<Line 1, Column 41791>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 41791>: XML-20250: (Fatal Error) Missing entity 'CommentYearTarget'.
<Line 1, Column 41880>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 41880>: XML-20250: (Fatal Error) Missing entity 'CommentYearTarget'.
<Line 1, Column 41960>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 41960>: XML-20250: (Fatal Error) Missing entity 'ThisYear'.
<Line 1, Column 41967>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 41967>: XML-20250: (Fatal Error) Missing entity 'Year2'.
<Line 1, Column 41974>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 41974>: XML-20250: (Fatal Error) Missing entity 'Year3'.
<Line 1, Column 41981>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 41981>: XML-20250: (Fatal Error) Missing entity 'Year4'.
<Line 1, Column 41988>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 41988>: XML-20250: (Fatal Error) Missing entity 'Year5'.
<Line 1, Column 46124>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 46124>: XML-20250: (Fatal Error) Missing entity 'CostCentre'.
<Line 1, Column 47563>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 47563>: XML-20250: (Fatal Error) Missing entity 'Scenario'.
<Line 1, Column 47644>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 47644>: XML-20250: (Fatal Error) Missing entity 'PriorYear'.
<Line 1, Column 47724>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 47724>: XML-20250: (Fatal Error) Missing entity 'ThisYear'.
<Line 1, Column 47731>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 47731>: XML-20250: (Fatal Error) Missing entity 'Year2'.
<Line 1, Column 47738>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 47738>: XML-20250: (Fatal Error) Missing entity 'Year3'.
<Line 1, Column 47745>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 47745>: XML-20250: (Fatal Error) Missing entity 'Year4'.
<Line 1, Column 47752>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 47752>: XML-20250: (Fatal Error) Missing entity 'Year5'.
<Line 1, Column 49431>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 49431>: XML-20250: (Fatal Error) Missing entity 'Scenario'.
<Line 1, Column 49512>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 49512>: XML-20250: (Fatal Error) Missing entity 'PriorYear'.
<Line 1, Column 49592>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 49592>: XML-20250: (Fatal Error) Missing entity 'ThisYear'.
<Line 1, Column 49599>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 49599>: XML-20250: (Fatal Error) Missing entity 'Year2'.
<Line 1, Column 49606>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 49606>: XML-20250: (Fatal Error) Missing entity 'Year3'.
<Line 1, Column 49613>: XML-20100: (Fatal Error) Expected ';'.
<Line 1, Column 49613>: XML-20250: (Fatal Error) Missing entity 'Year4'.
Most of these are Substitution Variables. I dont know why it is showing a few lines for "Scenario" as well.
The Planning syserr log says
java.net.SocketException: socket write error: Connection reset by peer.
     at jrockit.net.SocketNativeIO.writeBytesPinned(Native Method)
     at jrockit.net.SocketNativeIO.socketWrite(SocketNativeIO.java:73)
     at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
     at weblogic.utils.io.ChunkedOutputStream.writeTo(ChunkedOutputStream.java:193)
     at weblogic.servlet.internal.ResponseHeaders.writeHeaders(ResponseHeaders.java:443)
     at weblogic.servlet.internal.ServletResponseImpl.writeHeaders(ServletResponseImpl.java:1291)
     at weblogic.servlet.internal.ServletOutputStreamImpl.sendHeaders(ServletOutputStreamImpl.java:260)
     at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:108)
     at weblogic.servlet.internal.ServletResponseImpl.sendRedirect(ServletResponseImpl.java:907)
     at HspValidatingHttpResponse.sendRedirect(Unknown Source)
     at jsp_servlet.__planninglogoff._jspService(__planninglogoff.java:1411)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:35)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at HspValidationFilter.doFilter(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
oracle.xml.parser.v2.XMLParseException: Expected ';'.
     at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:323)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:335)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:318)
     at oracle.apps.xdo.common.xml.XSLTClassic.transform(Unknown Source)
     at oracle.apps.xdo.common.xml.XSLTWrapper.transform(Unknown Source)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
     at oracle.apps.xdo.template.FOProcessor.createFO(Unknown Source)
     at oracle.apps.xdo.template.FOProcessor.generate(Unknown Source)
     at HspReportingServlet.Handle(Unknown Source)
     at HspHttpServlet.initialize(Unknown Source)
     at HspHttpServlet.doGet(Unknown Source)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at HspValidationFilter.doFilter(Unknown Source)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Would be great if you could interpret these log and let me know how I can resolve this.
Cheers

Difference between Reports in normal ABAP and Reports in CRM

Hi Experts,
I am new to CRM. Can someone tell me the Difference between Reports in normal ABAP and Reports in CRM.
It will be very useful if someone explains with example.
Some where in SDN i read in CRM we should not select statment. Then how to fetch data?
Please give me more basic concepts about CRM programming.
Thanks,
RAGU

Hi Ragu,
You can find much information at http://service.sap.com/crm-inst.
Go to Installation & Upgrade Guides -> SAP Business Suite Applications -> SAP CRM
Check the CRM version in which you are working and get the documents.
FMs are specific to the requirement. Like all Business Partner related FMs generally start with BUPA* or BAPI_BUPA*.
For CRM transaction data you can get info using FM CRM_ORDER_READ. To create a new transaction use CRM_ORDER_MAINTAIN and CRM_ORDER_SAVE.
More information can be fetched by surfing through the SDN threads and checking in SE37 t-code.
Hope this helps!
Regards,
Saumya

Using SQL queries via ODBC connection to obtain data for a report

Post Author: adhiann
CA Forum: General
Hi All,
I was trying to run a Crystal Reports report through Clearquest using an SQL query I designed in CQ to give me the data I need, however, from within ClearQuest, I cannot associate an SQL query on a report, so I went directly to Crystal Reports and am using the ODBC connection to the ClearQuest database to run the report. I selected the right tables and fields and am using the same formula that I used on ClearQuest's SQL query to get the data, however, the report doesn't return any data whereas I am getting at least 5 records from Clearquest for the same query.
Granted there's a difference in the way you create a SQL formula in Crystal, but I don't know if I'm doing it right as I've never had to use CR as a standalone product.
Is there a way I can directly plug my ClearQuest's SQL query into the CR and run it? I don't know why the results won't return any data for a query that has some results
Thanks in advance
nandita

Post Author: Roscoe1822
CA Forum: General
Did you try to add a command through the Database Expert? Also creating a Business View that contains your sql query might help as well.

Difference between Report painter and abap query .

can anyone please tell me the difference between the report painter and the ordinary alv,clasical reporting and also the difference between Report painter and abap query. How the output format will be in Report painter. If anyone has any documents please send it to
[email protected]
Thanks,
Joseph.

hi,
ABAP Query is an ABAP Workbench tool that enables users without knowledge of the ABAP programming language to define and execute their own reports.
In ABAP Query, you enter texts and select fields and options to determine the structure of the reports. Fields are selected from functional areas and can be assigned a sequence by numbering.
link for abap query --
https://forums.sdn.sap.com/click.jspa?searchID=221911&messageID=2790992
whereas the Report Painter enables you to report on data from various applications. It uses a graphical report structure that forms the basis for the report definition. When defining the report, you work with a structure that corresponds to the final structure of the report when the report data is output.
link for report painter --
https://forums.sdn.sap.com/click.jspa?searchID=221874&messageID=1818114
Regards,
pankaj singh
Message was edited by:
Pankaj Singh
Message was edited by:
Pankaj Singh

Get data from a Report Painter

Hello.
Does anyone know how to get data from a Report Painter?
Thanks in advance!

Hi
check the links
Report Writer functions can be accessed from within the Report Painter.
The difference lies in the GUI of the report painter.
For Report Painter
http://help.sap.com/saphelp_47x200/helpdata/en/66/bc7d2543c211d182b30000e829fbfe/content.htm
For Report Writer
http://help.sap.com/saphelp_47x200/helpdata/en/66/bc7dc143c211d182b30000e829fbfe/content.htm
Refer the following links :
http://www.virtuosollc.com/PDF/Get_Reporter.pdf
http://sap.ittoolbox.com/groups/technical-functional/sap-r3-other/accessing-tables-using-report-painterwriter-98766
http://help.sap.com/saphelp_47x200/helpdata/en/da/6ada3889432f48e10000000a114084/frameset.htm
http://help.sap.com/saphelp_bw31/helpdata/en/66/bc7d2543c211d182b30000e829fbfe/frameset.htm
Regards
Anji

Difference between Report screens vs Dynpros

Hi All:
Could someone please tell me what is the difference between report selection screens and dynpros?
Thanks.
Mithun

Hi
See the doc for Web Dynpros
Web Dynpro ABAP
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/db22242d-0701-0010-28a2-aeaa1fefd706
Hope that the following also helps you.
Web Dynpro for ABAP (WD4A, WDA) is the SAP standard UI technology for developing Web
applications in the ABAP environment. It consists of a runtime environment and a graphical
development environment with special Web Dynpro tools that are integrated in the ABAP
Workbench (SE80).
Web Dynpro offers the following advantages for application developers:
The use of declarative and graphical tools significantly reduces the implementation
effort
Web Dynpro supports a structured design process
Strict separation between layout and business data
Reuse and better maintainability by using components
The layout and navigation is easily changed using the Web Dynpro tools
Stateful applications are supported that is, if the page is changed and the required
data remains intact so that you can access it at any time throughout the entire
application context.
Note that stateless applications are not possible.
Automatic data transport using data binding
Automatic input check
Automatic operation of the Web Dynpro application using the keyboard
User interface accessibility is supported
Full integration in the reliable ABAP development environment
Web Dynpro Architecture
Definition
Web Dynpro is the SAP NetWeaver programming model for user interfaces (UIs).
The Web Dynpro model is based on the Model View Controller paradigm, and has the
following features that build on the classic dynpro model:
Clear separation of business logic and display logic
Uniform metamodel for all types of user interfaces
Execution on a number of client platforms.
Extensive platform independence of interfaces
Structure
Metamodel Concept
Web Dynpro provides support for developing Web representation of a business application.
You use specific tools to describe the properties of a Web Dynpro application in the form of
Web Dynpro metadata. The necessary source code is then generated automatically and
executed at runtime. In addition to the events offered by the framework, you can also define
your own events for a Web Dynpro application. However, the event handling must always be
programmed in separate source code areas which are executed automatically when the event
is triggered at runtime.
In Web Dynpro, each user interface is always made up of the same basic elements. These
elements of the metamodel can be statically declared using Web Dynpro tools.
It is also possible to implement elements of the metamodel at runtime and to change them or
reintegrate them at runtime. Using these implementations, you can make any changes or
enhancements to a user interface that has been created by declarative methods by
generating new interface structures at runtime.
This means that you can combine declarative processes and the implementation of source
code.
Graphical Development Tools
To support this declarative concept, both the SAP NetWeaver Developer Studio and the
ABAP Workbench contain a range of Web Dynpro tools. You can therefore generate a large
proportion of a Web Dynpro application using the tools provided, without having to create your
own source code. This applies to the following parts of the application:
Data flow between the front end and back end
Layout of the user interface
Properties of user interface elements
The Web Dynpro tools enable you to create source text areas manually within generated
source texts. These areas are not changed if the source code is regenerated.
Separation of Business and Application Logic
Using Web Dynpro enables a clear separation of business logic and display logic. A Web
Dynpro application runs on the front end and has local or remote access to the back end
system via a service. This means that the display logic is contained in the Web Dynpro
application, while the business logic and the persistence of the business objects run in the
back end system. The following options are currently available for connecting Web Dynpro
applications and the back-end system:
An interface generated using adaptive RFC, through which BAPIs of an SAP system
can be called
An interface for calling Web services
A self-generated interface
The source code required for connecting the Web Dynpro application can be generated
from a UML definition of the Web Dynpro interface. A UML definition can be imported
into the Web Dynpro tools as an XML file.
Conversion of the Model-View-Controller
Conversion of the Model-View-Controller Programming Model
Every Web Dynpro application is structured according to the Model View Controller
programming model:
? The model forms the interface to the back end system and thus enables the
Web Dynpro application access to data.
? The view is responsible for the representation of the data in the browser.
? The controller lies between the view and the model. The controller formats
the model data to be displayed in the view, processes the user entries made by the
user, and returns them to the model.
/people/thomas.jung/blog/2006/06/20/web-dynpro-abap-demonstration-videos
http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm
Reward if useful
regards
Anji

Date Difference Calculation in BW3.5

Hi
We are calculating date differences between 2 dates i.e. Delivery Date - System Date.For System date we used variable exit to derive the value.But when we create CKF on Delivery Date,we necessary have to keep date field in Drilldown(in rows).But reports needs to give Overview while including date field in rows removes the granularity.
Is thier any other way we can handle this situation.
Regards
Praveen

You have to put ur delivery date in Rows if u r doing the Formula variable with replacement path. There is no option.
Khaja

SAP COPA Delivery and billing date difference

Dear gurus,
I am new to COPA and going on a COPA project.
Here is one question that I have been searching answer for.
At the month end reconciliation of FI COPA data, there could be a situtaion where the SD delivery takes place this month but the billing for the same happens next month. under this circumstance,
1. how would a busness like to see the data?
2. Is there a way to reconcile the data where there is such date difference to get the correct report?
regards
Roy

Hi Roy
This is often a problem and causes FI/COPA to be out of synch....
However, please note that, this situation can also be a genuine one due to legal restrictions.. In some countries, you can not recognize revenue till customer gives you Proof of Delivery (POD)... In such cases, the PGI cost hits P&L in Month X and revenue hits P&L in Month X+1
To avoid this situation, you have 2 options....Both are tried and tested approaches
1. Use Exit RV60AFZB and write ABAP code saying that billing month cant be different than PGI month... This approach can be used if you are not bound by the legal restrictions I said above
2. Another approach is to use accrual keys in your SD pricing procedure.. (Ask your SD guy to do this)
a. At PGI: The accounting entry would be
Stock issued, but not Billed a/c ........... Dr (This is also a balance sheet account)
Stock /ac ............................................Cr (This is a Balance sheet acount)
b. During Billing, the entry would be
Customer .................................. Dr
Revenue ....................................Cr
COGS ..........................................Dr
Stock issued, but not Billed a/c.....Cr
This way, COGS and Revenue are both accounted in same month
BR,Ajay M

Difference between reports & modulepool programs

hi experts,
what is module pool programs?
Pls tell me the difference between reports & module pool programs?

hi..
TYPES 1
Type 1 programs have the important characteristic that they do not have to be controlled using user-defined screens. Instead, they are controlled by the runtime environment, which calls a series of processing blocks (and selection screens and lists where necessary) in a fixed sequence. User actions on screens can then trigger further processing blocks.
You can start a type 1 program and the corresponding processor in the runtime environment using the SUBMIT statement in another ABAP program. There are also various ways of starting a type1 program by entering its program name. This is why we refer to type 1 programs as executable programs.
When you run a type 1 program, a series of processors run in a particular order in the runtime environment. The process flow allows the user to enter selection parameters on a selection screen. The data is them selected from the database and processed. Finally, an output list is displayed. At no stage does the programmer have to define his or her own screens. The runtime environment also allows you to work with a logical database. A logical database is a special ABAP program which combines the contents of certain database tables. The flow of a type 1 program is oriented towards reporting, whose main tasks are to read data from the database, process it, and display the results. This is why executable programs (type 1) in the R/3 System are often referred to as reports, and why running an executable program is often called reporting.
Since it is not compulsory to define event blocks, you can yourself determine the events to which your ABAP program should react. Furthermore, you can call your own screens or processing blocks at any time, leaving the prescribed program flow. You can use this, for example, to present data in a table on a dialog screen instead of in a list. The simplest executable program (report) contains only one processing block (START-OF-SELECTION).
Executable programs do not require any user dialog. You can fill the selection screen using a variant and output data directly to the spool system instead of to a list. This makes executable programs (reports) the means of background processing in the R/3 System.
You can also assign a transaction code to an executable program. Users can then start it using the transaction code and not the program name. The reporting-oriented runtime environment is also called when you run a report using a transaction code. This kind of transaction is called a report transaction.
It is appropriate to use executable programs (reports) when the flow of your program corresponds either wholly or in part to the pre-defined flow of the runtime environment. Until Release 4.5A, the only way to use a logical database was to use an executable program. However, from Release 4.5A, it is also possible to call logical databases on their own.
Type M
The most important technical attribute of a type M program is that it can only be controlled using screen flow logic. You must start them using a transaction code, whcih is linked to the program and one of its screens (initial screen). Another feature of these programs is that you must define your own screens in the Screen Painter (although the intial screen can be a selection screen).
When you start a program using a transaction code, the runtime environment starts a processor that calls the initial screen. This then calls a dialog module in the corresponding ABAP program. The remainder of the program flow can take any form. For example, the dialog module can:
return control to the screen, after which, the processing passes to a subsequent screen. Each screen has a following screen, set either statically or dynamically.
call other sequences of screens, selection screens or lists, from which further processing blocks in the ABAP program are started.
call other processing blocks itself, either internally or externally.
call other application programs using CALL TRANSACTION (type M program) or SUBMIT (type 1 program).
ABAP programs with type M contain the dialog modules belonging to the various screens. They are therefore known as module pools. It is appropriate to use module pools when you write dialog-oriented programs using a large number of screens whose flow logic largely determines the program flow.
REGARDS,
VEERESH

Differences Between Report Painter and Report Writer

Hi,
Anyone knows the differences between report painter and report writer?
Thanks,
CW

Hello CW Teo,
Yes report writer can be used in logistics also. One of the way which I am aware of is described below.
Flexible analyses allow you to can tailor the way in which key figures are combined and aggregated. This means that it is possible to both provide administrators with detailed information and management with aggregated information.
Flexible analyses enable easy access to the Report Writer, a user-friendly tool with which you can create reports for various analyses. The Report Writer is integrated in other SAP applications, such as Extended General Ledger and Cost Center Accounting.
Evaluation structures form the interface to the Report Writer. Evaluation structures consist of characteristics and key figures and are easy to construct.An evaluation structure with the same name exists for each information structure in the standard system.Even the self-defined information structures created in Customizing can be evaluated via the flexible analyses.
Evaluations:You can create an evaluation on the basis of the evaluation structure.
To define an evaluation, all you need to do is select the characteristics and key figures you require (pick-up technique).One of the especially useful features here is that you have the option of tailoring the layout of your report to suit your particular requirements. You can also define extra key figures for the reports, which are derived from existing key figures by means of calculation formulas. You can thereby multiply the key figures or divide one key figure by another.
============================================================
In addition to the above you can also edit a report in logistics module with the help of a report writer. below mentioned is the process for it.
It is now possible to edit your report data using the Report Writer. You can also change the layout of the report. The most important functions of the layout design are summarized below.
Summation levels:In the report screen, you can use the menu sequence View ->Summation level to specify the number of summation used to calculate total values. All totals that do not lie within the specified interval will be hidden. A summation level corresponds to a hierarchical level (for example, material level). Summation level 1 is the lowest hierarchical level. Summation level 2 is the next level up, and so on. The individual values are on the summation level 0.
The summation levels can be specified both universally (for the entire report) or locally (for specific blocks of rows). In this case, the local settings overwrite global values.
Report views:If a report is displayed on the screen, the Report Writer will then set page breaks so that exactly one page fits into the current window. This view will be defined as the standard view. As the Report Writer always processes exactly one page, you can only use the page keys and page icons to page up and down; the scroll bars cannot be used.
The page view can be determined via Settings-> Page view. The page breaks in the page view correspond to those defined in the report layout.
Hide and show rows:The function Edit->Hide rows exclude certain preselected areas of your report from the display. You can undo this command with Edit ® Show rows.
Expanding and collapsing report rows:View-> Hierarchy->Collapse allows you to hide the report rows of the sub-trees that are located underneath. View->Hierarchy ->Expand allows you to undo this command level by level.
If you want to display all the report rows that were hidden by collapsing the hierarchy or restricting the summation levels, select, View->Hierarchy-> Expand all.
View->Collapse all allows you to reduced every row block to the highest summation level.
Texts and Annotations:You can create an annotation for your report.
Select: Extras->Annotation.
You branch into the text editor of the Report Writer.
Via the menu sequence Settings->Texts, you can create and format a title page, the last page, as well as headers and footers using word processing functions.
For example, you can store variables in the header for the author of the report, the date of the selection or the name of the person who last changed the report.
Layout parameters:Using the menu sequence Settings->Layout you can specify the page format, display form, rows and columns of the report according to your needs and you can determine the settings for the graphics function. You can make these layout settings with Report->Save settings.
Hope I had been able to help you to some extent. please assign points as reward.
Rgds
Manish

Date Difference in Report

Similar Messages

Maybe you are looking for