Drill down reports (Reports 3.0)

I am trying to create a series of drill down reports using
Reports 3.0. To do this I have created buttons in each report
which pass parameters to the next report using the
srw.run_report package. I have a problem with the lowest level
report where no errors are reported but the report is generated
as a blank page. When run in isolation, i.e. filling in the
paramters manually, the report works perfectly well. Does anyone
have any ideas? Also, when passing more than one parameter, do
you just have to use the concatenation operator (

nicola (guest) wrote:
: I am trying to create a series of drill down reports using
: Reports 3.0. To do this I have created buttons in each report
: which pass parameters to the next report using the
: srw.run_report package. I have a problem with the lowest level
: report where no errors are reported but the report is generated
: as a blank page. When run in isolation, i.e. filling in the
: paramters manually, the report works perfectly well. Does
anyone
: have any ideas? Also, when passing more than one parameter, do
: you just have to use the concatenation operator (

Similar Messages

Drill down in report based on two queries

Hi,
I have a problem with drilling down in report which is based on two queries.
Queries are based on different universes.
Both queries contains almost the same dimensions but different measures.
In my report is a calculated measure based on measures from both queries.
In both universes are the same hierachies.
When I drill down in report for the first time I have to chose hierarchy but then data are filtered to the choosen value only from one query , data from second query are not filtered and the values of calculated measure are incorrect
How can I solve this issue without adding dimensions belonging to the hierarchies to queries.
Please help.
Regards.
MG

Hi MG,
First of all, what do you mean by "Both queries contains almost the same dimensions but different measures"
"Almost" is not a good word in the IT world, especially when trying to merge/join tables. You need to be exact.
That sounds like a possible reason for the problem.
I am also not sure about your question:
"How can I solve this issue without adding dimensions belonging to the hierarchies to queries."
You may have to add those dimensions to the queries. Why would you not want to?
Thanks

Unable to Drill Down for Report Designer

hellooo...I created a report using a query in Report Designer. My query is having a structure in the row and I'm using this query for the report in Report Designer. After I created this report in Report Designer, I assign this report in Web Application Designer and create a navigation pane to link this report for the drill down function. But I have problem on drill down this report in the web template when i click on this navigation pane for the free char i defined. Eg: when i drill down for the char in the free char under the navigation pane item, I cannot perform the drill down horizontally but can perform drill down vertically. After perform drill down, I don't see the values from that char being displayed in the reports. Just wondering report in report designer cannot have any drill down function? or is my query problem due to the structure i defined? thanks alotttt...

The report designer needs a fixed Column definition ( structures)
In case of drill across this requirement is not fullfilled.
This is not changable and is due to design, sorry.
so you can only drill down.
best regards,
Kai

Error in Drilled down ALV Report.

Hi all
i am creating a single level drilled down report , in that in the first screen i am displaying the header detials , in the second level i am displaying the item detial of the particular line..
While processing the second level i am getting a dump like
A PERFORM was used to call the routine "USER_COMMAND" of the program
"SAPLSLVC_FULLSCREEN".
This routine contains exactly 1 formal parameters, but the current
call contains 2 actual parameters.
parameters.
here is my code :
FORM USER_COMMAND USING R_UCOMM LIKE SY-UCOMM.
CASE R_UCOMM.
WHEN '&IC1'.
PERFORM BUILD_CATALOG_EKPO.
PERFORM EVENT_EKPO.
PERFORM POPULATE_EVENT_EKPO.
PERFORM DATA_EKPO.
PERFORM BUILD_LIST.
PERFORM DISPLAY_EKPO.
ENDCASE.
ENDFORM.
*&      Form BUILD_CATALOG_EKPO
      text
--> p1        text
<-- p2        text
FORM BUILD_CATALOG_EKPO .
WA_FIELDCAT-TABNAME = 'ITAB_EKPO'.
WA_FIELDCAT-FIELDNAME = 'EBELN'.
WA_FIELDCAT-SELTEXT_M = 'PO NO.'.
APPEND WA_FIELDCAT TO I_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-TABNAME = 'ITAB_EKPO'.
WA_FIELDCAT-FIELDNAME = 'EBELP'.
WA_FIELDCAT-SELTEXT_M = 'Item No.'.
APPEND WA_FIELDCAT TO I_FIELDCAT.
CLEAR WA_FIELDCAT.
    WA_FIELDCAT-TABNAME = 'ITAB_EKPO'.
WA_FIELDCAT-FIELDNAME = 'MATNR'.
WA_FIELDCAT-SELTEXT_M = 'Material NO.'.
APPEND WA_FIELDCAT TO I_FIELDCAT.
CLEAR WA_FIELDCAT.
    WA_FIELDCAT-TABNAME = 'ITAB_EKPO'.
WA_FIELDCAT-FIELDNAME = 'WERKS'.
WA_FIELDCAT-SELTEXT_M = 'PLANT.'.
APPEND WA_FIELDCAT TO I_FIELDCAT.
CLEAR WA_FIELDCAT.
    WA_FIELDCAT-TABNAME = 'ITAB_EKPO'.
WA_FIELDCAT-FIELDNAME = 'LGORT'.
WA_FIELDCAT-SELTEXT_M = 'Storage Loc.'.
APPEND WA_FIELDCAT TO I_FIELDCAT.
CLEAR WA_FIELDCAT.
    WA_FIELDCAT-TABNAME = 'ITAB_EKPO'.
WA_FIELDCAT-FIELDNAME = 'MENGE'.
WA_FIELDCAT-SELTEXT_M = 'Quantity.'.
APPEND WA_FIELDCAT TO I_FIELDCAT.
CLEAR WA_FIELDCAT.
    WA_FIELDCAT-TABNAME = 'ITAB_EKPO'.
WA_FIELDCAT-FIELDNAME = 'MEINS'.
WA_FIELDCAT-SELTEXT_M = 'UNIT.'.
APPEND WA_FIELDCAT TO I_FIELDCAT.
CLEAR WA_FIELDCAT.
ENDFORM.                    " BUILD_CATALOG_EKPO
*&      Form EVENT_EKPO
      text
--> p1        text
<-- p2        text
FORM EVENT_EKPO .
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
I_LIST_TYPE           = 0
IMPORTING
   ET_EVENTS             = V_EVENTS
EXCEPTIONS
LIST_TYPE_WRONG       = 1
OTHERS                = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " EVENT_EKPO
*&      Form POPULATE_EVENT_EKPO
      text
--> p1        text
<-- p2        text
FORM POPULATE_EVENT_EKPO .
READ TABLE V_EVENTS INTO WA_EVENT WITH KEY NAME = 'TOP_OF_PAGE'.
IF SY-SUBRC EQ 0.
WA_EVENT-FORM = 'TOP_OF_PAGE'.
MODIFY V_EVENTS FROM WA_EVENT TRANSPORTING FORM WHERE NAME = WA_EVENT-FORM.
ENDIF.
ENDFORM.                    " POPULATE_EVENT_EKPO
FORM F_TOP_OF_PAGE.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      IT_LIST_COMMENTARY       = IT_LISTHEADER
   i_logo                   =
   I_END_OF_LIST_GRID       =
ENDFORM.
*&      Form DATA_EKPO
      text
--> p1        text
<-- p2        text
FORM DATA_EKPO .
DATA:RS_SELFIELD TYPE SLIS_SELFIELD.
READ TABLE ITAB_EKKO INTO WA_EKKO INDEX RS_SELFIELD-TABINDEX.
SELECT EBELN EBELP MATNR WERKS LGORT MENGE MEINS
FROM EKPO
INTO CORRESPONDING FIELDS OF TABLE ITAB_EKPO
WHERE EBELN = WA_EKKO-EBELN.
DATA :ID_ITEM_COLOR.
LOOP AT ITAB_EKPO INTO WA_EKPO.
ID_ITEM_COLOR = ID_ITEM_COLOR + 1.
IF ID_ITEM_COLOR = 8.
   ID_ITEM_COLOR = 1.
ENDIF.
CONCATENATE 'C' ID_ITEM_COLOR '10' INTO WA_EKPO-LINE_COLOR_ITEM.
MODIFY ITAB_EKPO FROM WA_EKPO TRANSPORTING LINE_COLOR_ITEM.
ENDLOOP.
ENDFORM.                    " DATA_EKPO
*&      Form DISPLAY_EKPO
      text
--> p1        text
<-- p2        text
FORM DISPLAY_EKPO .
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_INTERFACE_CHECK                 = ' '
I_BYPASSING_BUFFER                = ' '
I_BUFFER_ACTIVE                   = ' '
   I_CALLBACK_PROGRAM                 = V_REPID
I_CALLBACK_PF_STATUS_SET          = ' '
I_CALLBACK_USER_COMMAND           = 'USER_COMMAND '
I_CALLBACK_TOP_OF_PAGE            = 'TOP_OF_PAGE'
I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
I_CALLBACK_HTML_END_OF_LIST       = ' '
I_STRUCTURE_NAME                  =
I_BACKGROUND_ID                   = ' '
   I_GRID_TITLE                      = I_TITLE_EKPO
I_GRID_SETTINGS                   =
IS_LAYOUT                         =
   IT_FIELDCAT                       = I_FIELDCAT[]
IT_EXCLUDING                      =
IT_SPECIAL_GROUPS                 =
IT_SORT                           =
IT_FILTER                         =
IS_SEL_HIDE                       =
I_DEFAULT                         = 'X'
I_SAVE                            = ' '
IS_VARIANT                        =
   IT_EVENTS                         = V_EVENTS
IT_EVENT_EXIT                     =
IS_PRINT                          =
IS_REPREP_ID                      =
I_SCREEN_START_COLUMN             = 0
I_SCREEN_START_LINE               = 0
I_SCREEN_END_COLUMN               = 0
I_SCREEN_END_LINE                 = 0
IT_ALV_GRAPHICS                   =
IT_HYPERLINK                      =
IT_ADD_FIELDCAT                   =
IT_EXCEPT_QINFO                   =
I_HTML_HEIGHT_TOP                 =
I_HTML_HEIGHT_END                 =
IMPORTING
E_EXIT_CAUSED_BY_CALLER           =
ES_EXIT_CAUSED_BY_USER            =
TABLES
    T_OUTTAB                          = ITAB_EKPO
EXCEPTIONS
PROGRAM_ERROR                     = 1
OTHERS                            = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " DISPLAY_EKPO
*&      Form BUILD_LIST
      text
--> p1        text
<-- p2        text
FORM BUILD_LIST .
gd_layout-no_input          = 'X'.
gd_layout-colwidth_optimize = 'X'.
gd_layout-totals_text       = 'Totals'(201).
Set layout field for row attributes(i.e. color)
gd_layout-info_fieldname =      ' LINE_COLOR_ITEM'.
ENDFORM.                    " BUILD_LIST
Arun Joseph

The form USER_COMMAND should have 2 changing/actual parameters which is standard.
Ex:
FORM user_command USING r_ucomm LIKE sy-ucomm
rs_selfield TYPE slis_selfield.
ENDFORM.

Error: "Numeric value entered was too low " -drill down discoverer report

Hi ,
We have created a Discoverer drill down report (drill down to another worksheet). We have two worksheets one for the master and and the other for the detail.The parameters are passed to detail sheet (The link information is set using the Manage links option in the Discoverer plus) from the master. This whole thing works fine in dev instance.
We imported the business area . Deleted the existing file and the opened the new .dis file from local computer and then saved it to db.
Now the master report runs fine and when we click on the drill down link for the detail we get the following error
An error occured while handling the event.See the application log for more details.
- The numerical value entered was too low."
However the link works fine in plus and desktop in the same instance.
Kindly help.
Thanks,
Shobana

I hope you're not using Internet Explorer v7.
It has a specific problem with Disco Viewer, is not certified to work with it, and the error is drilling in Viewer.
The Oracle bug (metalink) is: 5608740
This bug prevents the listing of drill items under the drill icon.
Russ

Drill down in reports

Hi,
when I want to work with drill downs is this only possible with using hierarchies for the neccessary characteristics?
I'm working with SAP BW 3.5 and 7.
Thanks in advance.
Edited by: saplaz on Jun 23, 2010 11:11 PM

The report shows for example:
Risk class 1 customerX 500 Dollar
                    customerY 300 Dollar
                    customerZ 200 Dollar
                    Sum 1000
after drill down
Risk class 1.1 customerX 500 Dollar
Sum 500
Risk class 1.2 customerY 300 Dollar
Sum 300
Risk class 1.3 customerZ 200 Dollar
Sum 200
The thing is that I only want to see one row with the risk class like that:
Risk class 1 1000 Dollar
after the drill down the other rows should appear
Rc 1.1 customerX 500 Dollar
Rc 1.2 customerY 300 Dollar
Rc 1.3 customerZ 200 Dollar
Any ideas how this could be done?

Layout problem for Drill down ALV Report

Hello Everyone,
                       I have developed a ALV drill down report using the method G_GRID->SET_TABLE_FOR_FIRST_DISPLAY. The problem is what ever layout i save for the primary list 'Screen 100' is effecting my secondary list 'Screen 200'. User need to save both Screen 100 and Screen 200 layouts independently without affecting each other.
I am calling screen 100 as below,
Call metthod g_grid_100->set_table_for_first_display
Exporting
   i_Save                                     = 'A'
   is_layout                                 = ls_layout
   is_Variant                                =   ls_Variant
Changing
   it_outtab                                  = ct_poitems
   it_fieldcatalog                           = lt_fieldcat
Exceptions
   Invalid_parameter_combimation   = 1
   Program_error                            = 2
   too_many_lines                         = 3
   others                                       = 4.
Could any body suggest me a way to do this..
Thanks in advance.
Regards,
Shyam.

Hi,
Use multiple Layout structure (each alv have its own structure) .
Note the use of disvariant-log_group .
DATA: gs_disvariant_1 TYPE disvariant ,
           gs_disvariant_2 TYPE disvariant .
* Layout-Logical groups
CONSTANTS: gc_log_group_1 TYPE disvariant-log_group VALUE 'ALV1' ,
                        gc_log_group_2 TYPE disvariant-log_group VALUE 'ALV2' .
INITIALIZATION.
PERFORM at_initialization .
FORM at_initialization .
DATA: vari TYPE disvariant-variant .
PERFORM alv_variant_get_default USING gc_log_group_1 CHANGING gs_disvariant_1 vari .
PERFORM alv_variant_get_default USING gc_log_group_2 CHANGING gs_disvariant_2 vari .
ENDFORM.
FORM alv_variant_get_default
USING
    log_group TYPE disvariant-log_group
CHANGING
    disvariant TYPE disvariant
    variant    TYPE slis_vari .
DATA: ls_disvariant TYPE disvariant.
ls_disvariant-report = sy-repid .
ls_disvariant-log_group = log_group .
disvariant = ls_disvariant.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
    EXPORTING
      i_save     = 'A'
    CHANGING
      cs_variant = ls_disvariant
    EXCEPTIONS
      not_found = 2.
IF sy-subrc = 0.
    disvariant = ls_disvariant.
    variant    = ls_disvariant-variant .
ENDIF.
ENDFORM.                    "alv_variant_get_default
Later....
   CALL METHOD gui_alv_grid_1->set_table_for_first_display
      EXPORTING
        is_layout       = wa_layout
        is_print        = wa_print
        i_save          = 'A'
        is_variant      = gs_disvariant_1
      CHANGING
        it_sort         = it_sort
        it_fieldcatalog = it_fieldcatalog
        it_outtab       = it_alv_grid_1.
CALL METHOD gui_alv_grid_2->set_table_for_first_display
      EXPORTING
        is_layout       = wa_layout
        is_print        = wa_print
        i_save          = 'A'
        is_variant      = gs_disvariant_2
      CHANGING
        it_sort         = it_sort
        it_fieldcatalog = it_fieldcatalog
        it_outtab       = it_alv_grid_2.
Regards.

Drill down in report

I am looking to add some drill down functionality in one of my reports. Does anyone have an references (books, tutorials, or otherwise) that could provide an example. I'm running Reports 9i. TIA.

Hi,
One example you could look at is "Parameter form JSP".
http://otn.oracle.com/products/reports/htdocs/getstart/examples/index.html
In the example, you can search for customet name (eg, s%), then from the customer list you select one in order to view all its orders.
If you want to use the paper layout and output to HTML / HTMLCSS, in that case you can use the Hyperlinks property to create drill-down. You can look at "Building Reports" manual section 2.2.6 for information on Hyperlinks. Create a master report with hyperlinks, and in each hyperlink you can pass the full report command for the detail report with the relevant master infromation, eg, the customer_id or the department_id.
http://otn.oracle.com/documentation/reports.html
Navneet.

Drill Down in Report Designer

Hi to all,
I have create query in query designer with drill down, but when i format my query in Report Designer and execute it, it is not showing drill down.
can i show drilll down in Report Designer when executed.
If yes, How to do that.
I shall be thankfull to you for this.
Reagrds
Pavneet Rana

Hello,
Because BEx Reports are optimized for presentation and printing, the drill down cannot be changed (you can set filter values only). If you want to navigate within the data on the Web, use the BEx Web Analyzer or create a Web Application using a Web item analysis.
A dynamic section is based on a data provider thet contains a key figure in the columns and one more characteristics in the drill down od the rows.
Regards,
Edited by: Subbu_Amar on Oct 27, 2010 8:35 AM

Drill Down Error / Report Builder Limitations

I have been having alot of problems recently with the new
version of 7.0.2. A few things that i have noticed is that i can't
do drill downs anymore. I don't think it's a coding issue since it
was working in the previous 2 releases of Report Builder(7.0,
7.0.1).
Another problem is that I have reports that return around
1,000 pages. Now, I know there is a limitation on Flash Paper/Flash
Player, whoever i was wondering if there is a work around or
something i can do to get this reports to finish. Right now I get
the error roughly stating "A script has cause this flash movie to
become unstable and if you continue it might make the computer
unresponsive". Currently the only work around that i have is to
offer the same report in PDF format, however 90% of our customers
want to run it in flash paper, and my boss wonts it to work using
flash paper aswell.
Any sugguestions that you might have or anything please email
me. If you have any questions please email me aswell.
Thank you,
Daniel

Yeah, still having this issue... Can't get the links working
in Flash Paper. A temp fix is to have the report in PDF instead of
Flash.

Drill down on report s_alr_87012999

Hi,
I'm having trouble tracing a drilldown problem on order reports such as S_ALR_87012999. When drilling down on plan line items an error message saying "No plan line items were selected" appears, yet there is a total against the account code, suggesting there is data there. An authorization check doesn't return any problems. Am I missing anything else?
thanks

Ian,
Are you using ST01 for the auth trace?
Reading the error message, it did not sound like an authorization error message to me. One way you can rule out whether this is an authorization problem or not, assign the test uid with SAP_ALL , and run the report to see if the error still persists. So you don't waste time on non-security error.
Hope this help.
Regards,
Lye

Drill down on reports

Hi guys,
Sorry posted this in the wrong forum first.
Need help. On the vanilla chart on the Service Request home page. If you click on one of the segments, it drill's down to a list of the SR's within that segment.
However when i create such as pie chart, the pie-chart cannot be drilled down. I read some stuff about actions link and setting a custom data type with 2 different html options but nothing is working.
Also as Mike had suggested previously, i tried setting the drill property in the interaction tab.
But no joy any advice?
Thanks
Minesh

Min,
The interaction you are attempting to replicate is a Navigate interaction rather than a Drill. You will need to create a target report with the detail columns you want. One of these columns needs to be the same column you are clicking on in the first report. Set a filter on this column to Is Prompted.
Now go back to your first report and on Step 1 of the Build and View Analysis screen format the column you want to drill on with a column interaction of Navigate and browse and identify the target report.
Go to Step 2 and do the same for the Chart. Edit the chart and set the Navigate interaction to the target report.
Both reports need to be in the shared space, but do not need to be in the same folder. User must have access to both reports in order to use the navigate drill down.
If you have questions about how this should be set up, Open the Pre-built Analysis named Open Service Request Analysis in the Pre-built Analysis/Service Analysis folder. This is the report that is on the Service Homepage. The target report is named Service List and is in the Pre-built Analysis/Quick List Reports folder.
Hope this helps.
Mike

SSRS - multiple toggle in single row item to drill down sub report

I need to open a sub report using drill down concept. Is there any possible to give toggle for multiple columns in single row.
http://social.msdn.microsoft.com/Forums/getfile/528971
The sub report have two parameters to show data. If I click first link the subreport to be drill down with parameters 1 and 5. If I click second link the
same sub report to be drill through with different parametrs as 2 and 6.
Any idea to do this?

Thanks for your reply.
I do it this in different way.
See the below sample image url. I created the main report having four details with toggle to drill down the sub report. If I click the Detail1 the
subreport1 will expand drill down then I click Detail2 the subreport2 to be expand.
But still the subreport1 is visible I want to collapse Subreort1 once click toggle second and vice versa.
Please give your suggetions.
http://social.msdn.microsoft.com/Forums/getfile/529184

Drill Down ALV Report

One of my columns in ALV Report has PO# Number. If I double click that I should go to ME22N and edit that particular ALV . How to do this

hi..
check this.....
TYPE-POOLS : SLIS.
DATA: GS_LAYOUT TYPE SLIS_LAYOUT_ALV,
      G_EXIT_CAUSED_BY_CALLER,
      GS_EXIT_CAUSED_BY_USER TYPE SLIS_EXIT_BY_USER,
      G_REPID LIKE SY-REPID.
DATA : GS_VARIANT LIKE DISVARIANT,
       G_SAVE.
DATA : GT_EVENTS TYPE SLIS_T_EVENT,
       GT_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER,
       G_STATUS_SET TYPE SLIS_FORMNAME VALUE 'PF_STATUS_SET',
       G_TOP_OF_PAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE',
       G_TOP_OF_LIST TYPE SLIS_FORMNAME VALUE 'TOP_OF_LIST',
       G_END_OF_LIST TYPE SLIS_FORMNAME VALUE 'END_OF_LIST'.
DATA: W_EVENTS TYPE SLIS_ALV_EVENT.
DATA: T_EVENTS TYPE SLIS_T_EVENT.
after calucation i m storing my output in Jtab
PERFORM CREATE_FIELD_CATALOG CHANGING FC_DC.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
       I_BACKGROUND_ID    = 'ALV_BACKGROUND'
       I_BUFFER_ACTIVE    = 'X'
       I_CALLBACK_PROGRAM = G_REPID
       IS_LAYOUT          = GS_LAYOUT
       I_SAVE             = G_SAVE
       IS_VARIANT         = GS_VARIANT
       IT_EVENTS          = GT_EVENTS[]
       IT_FIELDCAT        = FC_DC
IMPORTING
       E_EXIT_CAUSED_BY_CALLER = G_EXIT_CAUSED_BY_CALLER
       ES_EXIT_CAUSED_BY_USER = GS_EXIT_CAUSED_BY_USER
TABLES
       T_OUTTAB = JTAB
EXCEPTIONS
       PROGRAM_ERROR = 1
       OTHERS        = 2.
FORM CREATE_FIELD_CATALOG CHANGING FC_DC TYPE SLIS_T_FIELDCAT_ALV.
DATA LS_CAT TYPE SLIS_T_FIELDCAT_ALV WITH HEADER LINE.
LS_CAT-FIELDNAME = 'VBELN'.
   LS_CAT-TABNAME = 'JTAB'.
   LS_CAT-SELTEXT_M = 'Delivery No'.
   LS_CAT-KEY = 'X'.
   APPEND LS_CAT TO FC_DC.
   CLEAR LS_CAT.
W_EVENTS-NAME = 'USER_COMMAND'.
W_EVENTS-FORM = 'SUB3'.
APPEND W_EVENTS TO gt_EVENTS.
ENDFORM.
FORM SUB3 USING UCOMM LIKE SY-UCOMM FIELDS1 TYPE SLIS_SELFIELD.
READ TABLE JTAB INTO KTAB INDEX FIELDS1-TABINDEX.
SET PARAMETER ID 'VL' FIELD KTAB-VBELN.
CALL TRANSACTION 'VL03N' AND SKIP FIRST SCREEN.
CLEAR KTAB-VBELN.
ENDFORM.
i m doing this for VL03N Transaction......& passed the parameter for delivery no,
same u hv to call me22n & pass the parameter
for PO parameter id is "BES".
Regards,
Arpit.
Edited by: Arpit Shah on Dec 18, 2007 10:24 AM

Need help with Drill down Matrix Report

Hi,
I need to create a matrix report with a tree functionality with two line heading.
Can some body tell me how can I generate this report?
REGION1 REGION2 REGION3
COL1 COL2 TOTAL COL1 COL2 TOTAL COL1 COL2 TOTAL
===========================================================
CAT1+
Sub_CAT1
Sub_CAT2
CAT2+
Sub_SCAT3
Sub_SCAT4
Where CAT1 , CAT2 needs to be collapsible rows. SCAT1..SCAT4 are sub categories under main categories.
REGION1.... REGION3 are top level headings. And COL1,COL2 are sub headings under top level headings.
Thanks,
Shrikant

As I said when I believe you posted up a similar question under a different user name...., (yes, it's that easy to tell )
Asking questions here about a version of Logic that was apparently, not legally purchased using the Mac App Store.. is not wise.... no matter what your reasoning for not being able to afford it...
Buy LPX, install it properly and then see if you have the same issues.....

Show Date Variable of report in drill down of report

Hi
I am using BI7.0 query designer and i am trying to build in the output of the date used in a variable as output in a drilldown in the report.This date is a keydate i use for making snapshots with APD's.
Example:
Keydate variable value: 01.07.2009
output in report:
Company Code   Date         Amount
    1000           01.07.2009       10
    2000           01.07.2009       20
    3000           01.07.2009       15
I have seen this before once in Bex 3.x designer, i had to use formula variables with replacement path i remember. Unfortunately i don't see how i should do this in the new query designer.
Can somebody help me out?
Thanks in advance!
best regards,
F. Geldof

y cant u use 0CALDAY and then create variable for it
use same 0CALDAY in query design in rows below ur characteristic COMPANY CODE

Drill down reports (Reports 3.0)

Similar Messages

Maybe you are looking for