Bex Report week wise

Hi All,
Can anyone help me to generate my report like this please in bex 7
.........................................      1st Week          2nd Week        3rd Week         Total Consumption Parts wise
Model of Bike XX            Parts consumed A         2                       1                          1                    4
.                           Parts consumed B         1                       2                          3                    6
.                           Parts consumed C         5                       3                          1                    9
Model of Bike YY             Parts consumed A          6                      3                          2                   11
.                           Parts consumed B          2                      2                          1                   5
.                           Parts consumed C          1                      2                          1                   4
Total Consumtion of Parts Week wise                    17                     13                          9
Please help me to design a query and advice changes that I have to make with my Infoobject
Thanks

Hi,
Steps:
1. Add 0CALWEEK in your cube or DSO whatever be the info-provider is.
2. map date field(for which you want to calculate the week) from data source to this 0CALWEEK.
3. choose transformation type as routine.
4. in routine write a logic of calculating week based on date.
5. different companies have different definitions for week, some companies states week from sunday - saturday, some has monday - suday. bsed on this week calculationneeds to be done.
6. make sure how about your definition of calweek and write routine acordingly.
7. But thing is for sure in almost all companies that they have 52 weeks in a year.
8. upload the data.
9. use this calweek in your report above consumptin quntity keyfigure i.e. in columns.
Regards,
akshay

Similar Messages

BI report required week wise

Hi ALL,
I am very new to BI and have got an issue at hand.
we have a vendor ageing report that is distributed month wise i.e 0-30, 31-60 and so on..is there a way by which i can change the months to weeks and get the report..
Regards
Arvind Kumar

Hi,
How it is distributed month wise, assuming at transormation level...you can either enhance rule written for this distribution or load this data to new infoprovider and there distribute week wise.
Hope it helps...
Regards,
Ashish

Report - Day wise /Week wise

Hi Experts,
I have 2 reports for which the data is fetched from 1 DSO.
I have CREATED DATE and DESPATCHED DATE in that.
I want to view both the reports Day Wise / Week Wise.
In the DSO i have mapped the Created Date to the CalDay and CalWeek/Year. Which will be used in the report 1
And I want to do the same mapping for the Despatched Date too. In order see the Day/Week trend in the report 2.
Since there is only one CalDay and CalWeek/Year objects available in the DSO im not able to bring the trend for despatched date.
Can anyone give solution to fx this issue please.
Thanks
Edited by: MO AHMED on Jan 7, 2010 4:30 PM

There are different solutions to this topic. The easiest is described by Roy:
Create two InfoObjects DESP_DAY and DESP_WK, copy them from 0CALDAY and 0CALWEEK and populate them from DESPATCHED_DATE in the transformation. I think you might need a routine for DESP_WK, simply use the function module DATE_GET_WEEK there.
If this doesn't work for you, e.g. if the DSO is used in a Multi Provider you might add an additional InfoObject DATE_TYPE to the DSO key. This is CHAR 1 and filled with either C for created date or D for dispatched date. Then you use two different field groups in the transformation to create two lines, one where 0CALDAY and 0CALWEEK are filled from CREATED_DATE with DATE_TYPE C and one where they are filled from DESPATCHED_DATE with date type D.
Best regards
Dirk

Week wise report

Hello all,
I would like to create new report for weekly wise details.But I do not know how to generate valid query for which report .
The requirement like this, the user will dynamically give two dates like 'from date' and 'to date'   and every week will started with 'Saturday' and ending with 'Friday'
Example:
From Date: 1/1/2013
To Date:31/12/2013
Days
week
1/1/2013
week01
1/2/2013
week01
1/3/2013
week01
1/4/2013
week01
1/5/2013
week02
1/6/2013
week02
1/7/2013
week02
1/8/2013
week02
1/9/2013
week02
1/10/2013
week02
1/11/2013
week02
1/12/2013
week03
1/13/2013
week03
1/14/2013
week03
1/15/2013
week03
1/16/2013
week03
1/17/2013
week03
1/18/2013
week03
1/19/2013
week04
1/20/2013
week04
1/21/2013
week04
1/22/2013
week04
1/23/2013
week04
1/24/2013
week04
1/25/2013
week04
1/26/2013
week05
1/27/2013
week05
1/28/2013
week05
1/29/2013
week05
1/30/2013
week05
1/31/2013
week05
2/1/2013
week05
2/2/2013
week06
2/3/2013
week06
2/4/2013
week06
2/5/2013
week06
2/6/2013
week06
2/7/2013
week06
2/8/2013
week06
2/9/2013
week07
2/10/2013
week07
2/11/2013
week07
2/12/2013
week07
2/13/2013
week07
2/14/2013
week07
2/15/2013
week07
2/16/2013
week08
2/17/2013
week08
2/18/2013
week08
2/19/2013
week08
2/20/2013
week08
2/21/2013
week08
2/22/2013
week08
2/23/2013
week09
2/24/2013
week09
2/25/2013
week09
2/26/2013
week09
2/27/2013
week09
2/28/2013
week09
3/1/2013
week09
3/2/2013
week10
3/3/2013
week10
3/4/2013
week10
3/5/2013
week10
continue
continue
The new week always start with Saturday and End with friday,
Kindly help me.....i am totally confused with this query

WITH input_dates AS
(SELECT to_date( '01-Jan-2013','dd-Mon-YYYY') stdt ,
    to_date( '01-Mar-2013','dd-Mon-YYYY') eddt
FROM dual
date_gen AS
(SELECT ( stdt + level -1) dt ,
    DECODE ( TO_CHAR(stdt,'D') , 7 , 0,1 ) ad
FROM input_dates
    CONNECT BY level <= (eddt - stdt)
SELECT TO_CHAR(dt , 'DD-Mon-YYYY') Dat,
TO_CHAR(dt,'Day') DAY,
'Week '
||(SUM (DECODE (TO_CHAR(dt,'D'),7,1,0)) over (order by dt) + ad ) wk_no
FROM date_gen
DAT
DAY
WK_NO
01-Jan-2013
Tuesday
Week 1
02-Jan-2013
Wednesday
Week 1
03-Jan-2013
Thursday
Week 1
04-Jan-2013
Friday
Week 1
05-Jan-2013
Saturday
Week 2
06-Jan-2013
Sunday
Week 2
07-Jan-2013
Monday
Week 2
08-Jan-2013
Tuesday
Week 2
09-Jan-2013
Wednesday
Week 2
10-Jan-2013
Thursday
Week 2
11-Jan-2013
Friday
Week 2
12-Jan-2013
Saturday
Week 3
13-Jan-2013
Sunday
Week 3
14-Jan-2013
Monday
Week 3
15-Jan-2013
Tuesday
Week 3
16-Jan-2013
Wednesday
Week 3
17-Jan-2013
Thursday
Week 3
18-Jan-2013
Friday
Week 3
19-Jan-2013
Saturday
Week 4
20-Jan-2013
Sunday
Week 4
21-Jan-2013
Monday
Week 4
22-Jan-2013
Tuesday
Week 4
23-Jan-2013
Wednesday
Week 4
24-Jan-2013
Thursday
Week 4
25-Jan-2013
Friday
Week 4
26-Jan-2013
Saturday
Week 5
27-Jan-2013
Sunday
Week 5
28-Jan-2013
Monday
Week 5
29-Jan-2013
Tuesday
Week 5
30-Jan-2013
Wednesday
Week 5
31-Jan-2013
Thursday
Week 5
01-Feb-2013
Friday
Week 5
02-Feb-2013
Saturday
Week 6
03-Feb-2013
Sunday
Week 6
04-Feb-2013
Monday
Week 6
05-Feb-2013
Tuesday
Week 6
06-Feb-2013
Wednesday
Week 6
07-Feb-2013
Thursday
Week 6
08-Feb-2013
Friday
Week 6
09-Feb-2013
Saturday
Week 7
10-Feb-2013
Sunday
Week 7
11-Feb-2013
Monday
Week 7
12-Feb-2013
Tuesday
Week 7
13-Feb-2013
Wednesday
Week 7
14-Feb-2013
Thursday
Week 7
15-Feb-2013
Friday
Week 7
16-Feb-2013
Saturday
Week 8
17-Feb-2013
Sunday
Week 8
18-Feb-2013
Monday
Week 8
19-Feb-2013
Tuesday
Week 8
20-Feb-2013
Wednesday
Week 8
21-Feb-2013
Thursday
Week 8
22-Feb-2013

Bex Report Performance

Dear Friends,
I would like to know is the complex authorizations can also cause the Bex report performance.
One of my scenerio is like there are two users A & B
A is having relevant authorizations for reporting, Drill down etc which are required.
B is having SAP All authorization.
When the same report has been executed by both users on the same system.
the data retrieved by user B(SAP_ALL authorization) is quite faster than User A.
Its like ther diffference of about 10 minutes.
There are some exsclude selections in report.
So my conclusion is like the complex authorizations do also hampers the query performance.
Please confirm & share your views.
Thanks & Best Regards,
Vivek Tripathi
+91-9372313000

Hi Vivek
     Can you help us understand what was the exact problem and how you resolved it / solution at Extraction / Modeling / Reporting end.
     I have a quite similiar issue with my report i have Header + Item report on Infoset
u2022     Header report takes seconds and item report takes minutes
u2022     The same report executed with exact parameter has inconsistent performance results meaning one time it takes 1 minutes next time same report same user and same authorization takes 5 minutes.
    Any help on this would be really greatfull. Suspecting is not an issue with the report at all , as no changes happened between the pre and post check.
_Additional Information : _
We Create Secondary -Bitmap index every week end i do not see that is one of the route cause.
Except that we have our regular daily loads that are running for master data loads and transaction data loads in series.
   Thanks in Advance.
Much Regards
Jagadish Thirumalachetty.
Edited by: Jagadish Thirumalachetty on Jul 14, 2010 1:35 PM

BEx report issue on setting offset value

Friends,
I have got a Bex reporting requirement as follows.
Given a Calendar week I have to show data for 5 Key figures for the next 3 calendar weeks. For ex: if I enter 05/2006 I have to show data for 05/2006, 06/2006 and 07/2006.
I thoght of using the Off Set parameter for all the Key figures, and for testing I did for 2nd set of Key figures with off set (1)..but these key figures are not showing any data.. Is it I am missing anything here ??
Please comment if you have any better thoght of doing this..
Thanks
Mavi

Hi,
The format of period you gave refers to month i believe. If it is right, check the offsets once again. If the user enters fiscal year period, it should be converted in to week period using an customer exit variable(if you don,t have 0CALWEEK) and set offsets.
Check this link, you may get some idea from that.
Re: Aging Report

Using Report-to-Report Interface (RRI) in BEx Report Designer?

Dear experts,
I would like to know if it is possible to use Report-to-Report Interface in BEx Report Designer?
From what I read from this article
[(Creating Formatted reports using BEx Report Designer)|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00ae5173-6112-2d10-d78f-e7779d269f25?quicklink=index&overridelayout=true], the RRI capability of query is not supported in BEx report. So is it true? And are there any workarounds to enable/emulate RRI capability in BEx Report?
Thanks in advance.
Regards,
Joon

Hi Joon,
It is possible to make RRI in BEX Report Designer by using Transaction Code - RSBBS .
Here you need to give the Target Query and Source Query names and than you can easily connect two reports or two levels of same report.
For further step wise description please check the below SDN document :
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/607e63d5-b56f-2c10-718f-8e33a08baa89?quicklink=index&overridelayout=true
I hope this document helps to sort out the queries.
Regards,
Akanksha

Layout in selection screen of Bex report

Hi Gurus,
I have a report which is needed by many users.
Now each user has a different way to use the report
like SE wise,material wise,payer wise , each with selected key figures.
Now i have one solution that to create a seperate view for each user, but i dont want to maintain number of views.
Again i have to schedule the same report for email to diferent users through Enterprise Portal where Views are not supported
so can i have any other way to meet this requirement
Can we have layout selection in bex report selection screen ( as we have in R/3 reports) ?
( i m using BI 7.0 and EP 6.0)

Hi Sonal,
If you are using EP end, then that can be achieved at there but for the same as u already said that you have to create either views of the query or you have to create seprate query's itself and at the EP end you can define which query you want at Different selection. But at BI end there is as such no option to do so, i mean at query level .
Thanks
dipika

Accounts Receivable Report: Customer Wise Ageing Analysis report -FI module

Hi Gurus,
             Can anyone help me in providing standard report(source code) or already done sample report(source code) for Accounts Receivable Report: Customer Wise Ageing AnalysisThis is in FI Module. Though it is FI Module we need to fetch details related to Sales Module, and the days should be <0     30     60     90     120     180     365     >365
It is urgent I need to deliver this report by this week end.
Please help me . Waiting for your reply.
Points Rewarded for help rendered and I would personally send a good gift if you can help me
Yours Truly,
Rajiv Christopher.
Edited by: Rajiv Christopher on Apr 2, 2008 11:33 AM

Hi,
i am attaching aging report.
see if this is useful to you.
REPORT ZFUS0102 MESSAGE-ID OA
                LINE-SIZE 270.
Title:      GR/IR AGING REPORT
Date:       January 2001
TABLES: DISVARIANT, EKPO.
TYPE-POOLS: SLIS.
Tables
TABLES:
BSIS,
EKKO.
working table
DATA: BEGIN OF RTAB OCCURS 0,
         HKONT   LIKE BSIS-HKONT,
         ZUONR   LIKE BSIS-ZUONR,
         BUDAT   LIKE BSIS-BUDAT,
         SHKZG   LIKE BSIS-SHKZG,
         DMBTR   LIKE BSIS-DMBTR,
         PRCTR   LIKE BSIS-PRCTR,
      END OF RTAB.
DATA: BEGIN OF WTAB OCCURS 0,
         ZUONR(2) TYPE N,
         PRCTR   LIKE BSIS-PRCTR,
         DAYS(4) TYPE P,
         DMBTR   LIKE BSIS-DMBTR,
      END OF WTAB.
DATA: BEGIN OF PTAB OCCURS 0,
         ZUONR(2),
         PRCTR   LIKE BSIS-PRCTR,
         AMT30   LIKE BSIS-WRBTR,
         AMT60   LIKE BSIS-WRBTR,
         AMTPL   LIKE BSIS-WRBTR,
         TOTAL   LIKE BSIS-WRBTR,
      END OF PTAB.
PARAMETERS: COMPANY LIKE BSIS-BUKRS OBLIGATORY,
             ACCT    LIKE BSIS-HKONT OBLIGATORY,
             DATE    LIKE SY-DATUM OBLIGATORY.
SELECT-OPTIONS: S_EKORG FOR EKKO-EKORG.
PARAMETERS: P_VARI LIKE DISVARIANT-REPORT.
DATA: WS-AMT30 LIKE BSIS-WRBTR.
DATA: WS-AMT60 LIKE BSIS-WRBTR.
DATA: WS-AMTPL LIKE BSIS-WRBTR.
DATA: TITLE(21) VALUE 'GR/IR Aging Report'.
DATA: LIN TYPE I.
DATA: GX_VARIANT LIKE DISVARIANT,
      G_VARIANT LIKE DISVARIANT.
DATA: LAYOUT   TYPE SLIS_LAYOUT_ALV,
       L_F      TYPE SLIS_T_FIELDCAT_ALV   WITH HEADER LINE,
       GROUP    TYPE SLIS_T_SP_GROUP_ALV   WITH HEADER LINE,
       COLOR    TYPE SLIS_T_SPECIALCOL_ALV WITH HEADER LINE.
DATA: LT_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER,
       LS_LINE TYPE SLIS_LISTHEADER,
       T_EVENTS   TYPE SLIS_T_EVENT.
CONSTANTS: FORMNAME_TOP_OF_PAGE TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE'.
INITIALIZATION.
PERFORM EVENTTAB_AUFBAUEN USING T_EVENTS[].
PERFORM VARIANT_INIT.
Get default variant
GX_VARIANT = G_VARIANT.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
       EXPORTING
            I_SAVE     = 'A'
       CHANGING
            CS_VARIANT = GX_VARIANT
       EXCEPTIONS
            NOT_FOUND = 2.
IF SY-SUBRC = 0.
    P_VARI = GX_VARIANT-VARIANT.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_VARI.
PERFORM VARIANT_INPUTHELP_F14.
START-OF-SELECTION.
LS_LINE-TYP = 'S'.
WRITE SY-DATUM TO LS_LINE-INFO DD/MM/YY.
WRITE SY-UZEIT TO LS_LINE-INFO+10.
WRITE SY-UNAME TO LS_LINE-INFO+20.
WRITE TITLE    TO LS_LINE-INFO+30.
APPEND LS_LINE TO LT_TOP_OF_PAGE.
PERFORM FIELDS.
IF NOT P_VARI IS INITIAL.
    PERFORM PAI_OF_SELECTION_SCREEN.
ELSE.
    CALL FUNCTION 'REUSE_ALV_VARIANT_SELECT'
         EXPORTING
              I_DIALOG            = ' '
              I_USER_SPECIFIC     = 'A'
              I_DEFAULT           = ' '
        I_TABNAME_HEADER    =
        I_TABNAME_ITEM      =
              IT_DEFAULT_FIELDCAT = L_F[]
              I_LAYOUT            = LAYOUT
         IMPORTING
        E_EXIT              =
              ET_FIELDCAT         = L_F[]
        ET_SORT             =
        ET_FILTER           =
         CHANGING
              CS_VARIANT          = DISVARIANT
         EXCEPTIONS
              WRONG_INPUT         = 1
              FC_NOT_COMPLETE     = 2
              NOT_FOUND           = 3
              PROGRAM_ERROR       = 4
              OTHERS              = 5.
ENDIF.
Decide which tables to access.
PERFORM MAIN_SELECT.
MOVE TITLE TO LAYOUT-WINDOW_TITLEBAR.
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
       EXPORTING
            I_CALLBACK_PROGRAM      = 'ZFUS0102'
            I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
            IS_LAYOUT               = LAYOUT
            IT_FIELDCAT             = L_F[]
            IT_SPECIAL_GROUPS       = GROUP[]
            I_SAVE                  = 'A'
            IS_VARIANT              = G_VARIANT
            IT_EVENTS               = T_EVENTS
       TABLES
            T_OUTTAB                = PTAB
       EXCEPTIONS
            PROGRAM_ERROR           = 1
            OTHERS                  = 2.
      FORM FIELDS                                                   *
FORM FIELDS.
L_F-FIELDNAME     = 'ZUONR'.
L_F-OUTPUTLEN     = 6.
L_F-SELTEXT_L     = 'SERIES'.
L_F-REPTEXT_DDIC = 'SERIES'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME     = 'PRCTR'.
L_F-OUTPUTLEN     = 10.
L_F-SELTEXT_L     = 'PROFIT CTR.'.
L_F-REPTEXT_DDIC = 'PROFIT CTR.'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME     = 'AMT30'.
L_F-SELTEXT_L     = '30 DAYS'.
L_F-REPTEXT_DDIC = '30 DAYS'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
L_F-REF_TABNAME   = 'BSIS'.
L_F-REF_FIELDNAME = 'WRBTR'.
L_F-DO_SUM        = 'X'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME     = 'AMT60'.
L_F-SELTEXT_L     = '60 DAYS'.
L_F-REPTEXT_DDIC = '60 DAYS'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
L_F-REF_TABNAME   = 'BSIS'.
L_F-REF_FIELDNAME = 'WRBTR'.
L_F-DO_SUM        = 'X'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME     = 'AMTPL'.
L_F-SELTEXT_L     = '60+ DAYS'.
L_F-REPTEXT_DDIC = '60+ DAYS'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
L_F-REF_TABNAME   = 'BSIS'.
L_F-REF_FIELDNAME = 'WRBTR'.
L_F-DO_SUM        = 'X'.
APPEND L_F. CLEAR L_F.
L_F-FIELDNAME     = 'TOTAL'.
L_F-SELTEXT_L     = 'TOTAL'.
L_F-REPTEXT_DDIC = 'TOTAL'.
L_F-REF_TABNAME   = 'PTAB'.
L_F-SP_GROUP      = 'A'.
L_F-REF_TABNAME   = 'BSIS'.
L_F-REF_FIELDNAME = 'WRBTR'.
L_F-DO_SUM        = 'X'.
APPEND L_F. CLEAR L_F.
ENDFORM.
      FORM MAIN_SELECT                                              *
FORM MAIN_SELECT.
SELECT HKONT ZUONR BUDAT SHKZG DMBTR PRCTR
       INTO TABLE RTAB
       FROM BSIS
       WHERE BUKRS = COMPANY
       AND   HKONT = ACCT.
IF SY-SUBRC = 0.
    SORT RTAB.
    PERFORM PROCESS_RTAB.
    PERFORM PROCESS_WTAB.
ENDIF.
ENDFORM.                    " MAIN SELECT
      FORM VARIANT_INPUTHELP_F14                                    *
FORM VARIANT_INPUTHELP_F14.
DATA: G_EXIT(1) TYPE C.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
       EXPORTING
            IS_VARIANT          = G_VARIANT
            I_SAVE              = 'A' " g_save
          it_default_fieldcat =
       IMPORTING
            E_EXIT              = G_EXIT
            ES_VARIANT          = GX_VARIANT
       EXCEPTIONS
            NOT_FOUND = 2.
IF SY-SUBRC = 2.
    MESSAGE ID SY-MSGID TYPE 'S'      NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
    IF G_EXIT = SPACE.
      P_VARI = GX_VARIANT-VARIANT.
    ENDIF.
ENDIF.
ENDFORM.
      FORM USER_COMMAND                                             *
--> UCOMM                                                         *
--> SELFIELD                                                      *
FORM USER_COMMAND USING UCOMM LIKE SY-UCOMM SELFIELD TYPE
SLIS_SELFIELD.
IF UCOMM EQ '&IC1'.
    IF SELFIELD-TABINDEX <= 0.
      MESSAGE S108.
      EXIT.
    ENDIF.
IF SELFIELD-SEL_TAB_FIELD CS 'LIFNR'.
    SET PARAMETER ID 'LIF' FIELD SELFIELD-VALUE.
    CALL TRANSACTION 'XK02'.
ELSE.
    IF SELFIELD-SEL_TAB_FIELD CS 'VEND'.
      SET PARAMETER ID 'LIF' FIELD SELFIELD-VALUE.
      CALL TRANSACTION 'FBL1'.
    ENDIF.
ENDIF.
    CLEAR SY-UCOMM. CLEAR UCOMM.
ENDIF.
ENDFORM.
      FORM TOP_OF_PAGE                                              *
FORM TOP_OF_PAGE.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
       EXPORTING
            IT_LIST_COMMENTARY = LT_TOP_OF_PAGE.
ENDFORM.
      FORM EVENTTAB_AUFBAUEN                                        *
--> P_T_EVENTS                                                    *
FORM EVENTTAB_AUFBAUEN USING P_T_EVENTS TYPE SLIS_T_EVENT.
DATA: LS_EVENT TYPE SLIS_ALV_EVENT.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
       EXPORTING
            I_LIST_TYPE = 0
       IMPORTING
            ET_EVENTS   = P_T_EVENTS.
READ TABLE P_T_EVENTS WITH KEY NAME = SLIS_EV_TOP_OF_PAGE
                                                 INTO LS_EVENT.
IF SY-SUBRC = 0.
    MOVE FORMNAME_TOP_OF_PAGE TO LS_EVENT-FORM.
    APPEND LS_EVENT TO P_T_EVENTS.
ENDIF.
ENDFORM.                               " EVENTTAB_AUFBAUEN
      FORM PAI_OF_SELECTION_SCREEN                                  *
FORM PAI_OF_SELECTION_SCREEN.
IF NOT P_VARI IS INITIAL.
    MOVE G_VARIANT TO GX_VARIANT.
    MOVE P_VARI TO GX_VARIANT-VARIANT.
    CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
         EXPORTING
              I_SAVE     = 'A' " g_save
         CHANGING
              CS_VARIANT = GX_VARIANT.
    G_VARIANT = GX_VARIANT.
ELSE.
    PERFORM VARIANT_INIT.
ENDIF.
ENDFORM.                               " PAI_OF_SELECTION_SCREEN
      FORM VARIANT_INIT                                             *
FORM VARIANT_INIT.
CLEAR G_VARIANT.
G_VARIANT-REPORT = 'ZFUS0102'.
ENDFORM.                               " VARIANT_INIT
*&      Form PROCESS_RTAB
      text
--> p1        text
<-- p2        text
FORM PROCESS_RTAB.
DATA TLNS TYPE I.
DESCRIBE TABLE S_EKORG LINES TLNS.
LOOP AT RTAB.
    IF TLNS GT 0.
      SELECT SINGLE EKORG FROM EKKO INTO EKKO-EKORG
        WHERE EBELN = RTAB-ZUONR(10).
      CHECK EKKO-EKORG IN S_EKORG.
    ENDIF.
    IF NOT RTAB-BUDAT > DATE.
      MOVE RTAB-ZUONR(2) TO WTAB-ZUONR.
      COMPUTE WTAB-DAYS = DATE - RTAB-BUDAT.
      IF RTAB-SHKZG = 'H'.
        WTAB-DMBTR = RTAB-DMBTR * -1.
      ELSE.
        WTAB-DMBTR = RTAB-DMBTR * 1.
      ENDIF.
      MOVE RTAB-PRCTR TO WTAB-PRCTR.
      APPEND WTAB.
    ENDIF.
ENDLOOP.
FREE RTAB.
ENDFORM.                    " PROCESS_RTAB
*&      Form PROCESS_WTAB
      text
--> p1        text
<-- p2        text
FORM PROCESS_WTAB.
SORT WTAB BY ZUONR PRCTR DAYS.
LOOP AT WTAB.
    PTAB-ZUONR = WTAB-ZUONR.
    PTAB-PRCTR = WTAB-PRCTR.
    AT END OF DAYS.
      SUM.
      IF WTAB-DAYS > 60.
        WS-AMTPL = WS-AMTPL + WTAB-DMBTR.
      ELSE.
        IF WTAB-DAYS > 30.
          WS-AMT60 = WS-AMT60 + WTAB-DMBTR.
        ELSE.
          WS-AMT30 = WS-AMT30 + WTAB-DMBTR.
        ENDIF.
      ENDIF.
    ENDAT.
    AT END OF PRCTR.
      PTAB-AMTPL = WS-AMTPL.
      PTAB-AMT30 = WS-AMT30.
      PTAB-AMT60 = WS-AMT60.
      COMPUTE PTAB-TOTAL = PTAB-AMTPL + PTAB-AMT30 + PTAB-AMT60.
      APPEND PTAB.
      WS-AMTPL = 0.
      WS-AMT30 = 0.
      WS-AMT60 = 0.
    ENDAT.
ENDLOOP.
SORT PTAB BY ZUONR PRCTR.
ENDFORM.                    " PROCESS_WTAB
regards,
Sindhu

Cumulation problem in BEX REPORT?

hi,
i am generating reporting FISCAL PERIOD WISE. the values of standard price(OPRICE_STD), moving average price(0PRICE_AVG) values are basically coming from R/3 directly.
0fiscper    Company period            std price           mov avg price
2009001     20090101                      40                         50
2009001     20090102                      40                         50
2009001     20090103                      40                         50
2009001     20090104                      40                         50
no, when i run the report by fiscal period the values are showing 160 instead of 40, and 200 instead of 50 respectively.
when u drill down the values are 40,50 only for the company period wise. but how to display overall result as 40 for std price, and 50 for mov avg price in the bex report. that means how to do it in bex query designer.
regards
vadlamudi

thanks one and all , that problem has been resolved.
i have created structure for material types( Ingredients, packaging materials in rows)
when i execute the query by fiscal period the values which are showing is very high in the final result.
when i drill down by material and keyfigure(formula) values are not matching with the final result.
and if we execute by material wise rather than period wise the values are perfect.
pl tell me the solutio
regards
vadlamudi
Edited by: venugopalv on Sep 3, 2009 10:55 AM
Edited by: venugopalv on Sep 3, 2009 11:52 AM

Week Wise Project progress w.r.t. Percentage

Hi All,
I am using Project Server SP1.I have a requirement where I have to determine the week wise percentage completion status of projects.
To elaborate the above,
If the project duration is of 100 days, then I need the data to be calculated percentage wise from week 1 to the final week. This calculation will be on the basis of how much the project percentage was supposed to be completed as per Baseline 0 for every
week and I need to compare this data to the Actual finish percentage for every week so I can see a report.
Is there a way to generate this?
Any sort of help is appreciated. Thanks in advance.
Best Regards,
Chinmay Rajput.

Have a look at the earned value fields, especially the timephased ones. One of them may fit your needs.
Rod Gill
Author of the one and only Project VBA Book
www.project-systems.co.nz

Week wise schedule quantities

Hello Team,
We are maintaining the schedule lines in SA with daily indicator. The same is showing in EKET . Now I would like to know is there any table or report which shows the same information in week wise .. Do you have any Idea.
I have tried to get the same information from MD04 > Week Tab. Howerver the information is updating from structure. Please advise me how to achieve this ...
Thanks and Reg
Pavan

Hello Padmasri,
Thanks for Quick response .....
Yes.. However, our customer need it in Day wise only ... Is there any table or report which shows the same information cumulatively in weekwise ??
My question is answered
Edited by: pavan kulkarni on Nov 28, 2011 7:46 PM

BEx Reporting on BPC 10 Model

Hi all
I've been researching the option of bringing our BPC reporting into BW in order to make BPC data available to our existing set of BW users without the need to purchase more BPC licenses and save on training in EPM.
I have got as far as making the model a data source via the web admin and creating a query based on the virual provider <model>_B.
However, I still have some key questions which I do not have answered:
- Is this method of reporting OK as it is ? I am not making use of any sort of transient query..
- How are we able to enable authorisation on this BPC data surfaced in BEx without moving the data to new InfoObjects, etc. I do not believe it is wise to modify any of the automatically created objects from BPC..
- How are we able to improve the manipulation of hierarchies in BEx (some of which have 15 levels!) ? Has anyone come across this ?
My view is (and always has been) that we should be using BPC to reporting BPC data but I need to be sure of my facts and justify exactly why that should be our approach and make sure I am not missing an easy way to do this.
Thanks
Ian

Half a year ago I reported problem to SAP because hierarchies showed wrong totals - with queries based on virtual provider. This happened after upgrading BW and BPC. I reported this to SAP and they answered, that Bex reporting on virtual provider is not supported. After that I changed all queries to basic BPC cube and applied BW authorizations.
SAP's anwer in january 2014 was:
"The transient query is the supported BEx query, please kindly work with it for BEx WEB reporting. Note that the transient query also has some limitation, please refer to note 1730125.
Customer defined BEx query on BPC generated virtual InfoProvider is currently not supported. It's an enhancement request to support customer defined BEx query, please create such a request on
SAP Idea Place where BPC product team would regular check and collect development requests."
I see that later SAP issued note 1988018 which probably solved the issue. But still I didn't see any SAP's official statement that Bex reporting on BPC cubes is supported.
Regards
Ivan

ODS reporting without Bex Reporting activated

Hello
As part of a review I have been doing on our current BW data loading strategy I have uncovered a number of ODS objects that have the Bex reprorting indicator active. The consequence of this is that it has a negative impact on performance when loading data into BW, particularly if we have to re-initialise the data.
We currently do not actually report off the ODS object and from the research I have done the consensus seems to be that you should leave the bex reporting indicator turned off unless absolutely necessary and to use an infoset for reporting.
In the coming week we will be faced with having to reload 15 millions+ records back into these ODS objects after doing a redesign so thought it a good time to untick this option.
I should mention that we are using a BW 3.5 system.
Any comments would be appreciated and if the preference is to use an infoset, then can someone give a practical example why you would ever want to set an ODS to allow bex reporting other than the obvious response of not wanting to create an infoset Would i be correct in stating that I wouldn't be able to use indexes to aid performance if i use infosets. I'm reluctant to pass this data into an infocube given the amount of data as it contains asset transaction postings.
An additional side question which is more for my personal interest is whether it is true that it is not preferential to include ODS objects (or infosets) within a multiprovider given that strictly speaking the ODS object is not multi-dimensional. I recently read this in an article and had not considered this before so was wondering if it is correct.
Thank you in advance for your responses.
Regards
Mark
Edited by: majohnson on Mar 31, 2011 1:35 PM

Hi Christoper
Thank you for your response. You seem very passionate about not reporting on ODS objects
What I do find interesting is that there are a number of standard content ODS objects which do have the bex reporting indicator active.
I'm forming the view that if you do not have performance issue considerations loading data into ODS objects and you can control the amount of data selected via reporting using indexes and query restrictions etc then an ODS is still useful for reporting or alternatively the infoset option. That said, this does not apply to the ODS objects I was referring to in my main post and I will be deselecting the bex reporting indicator before re-initialising the data.
I have always been led to believe by people who know more about BW than myself that the infocube is designed for summarised / targeted multidimensional data and that storing line item information in an infocube seems to be contrary to this position.
Our current design approach standard in that we load data into a staging layer (Generally ODS objects, most of which do not allow bex reporting, and some of which contain line item information), then into a transformation layer (generally infocubes) and finally we report out of multi-providers in our reporting layer.
Our general reporting strategy has been that operational style reports which would include line item reporting should be done within ECC and all other strategic, summarised reporting etc is delivered in BW.
Regards
Mark

Cannot build the query or generate the report. WIS 30351

I am trying to create a docuemtn using SDK. I have created a document and when I try to add dataprovider and update the document, I am facing the below error
Cannot build the query or generate the report. WIS 30351
http://help.sap.com/saphelpiis_sbo41sp5wi-sdk/frameset.htm?ec5645bc6fdb101497906a7cb0e91070.html
Any help would be appreciated...

Hi Pirabu,
here's the required steps for what you described:
1. Create a new report in folder with ID 12345:
     POST ../raylight/v1/documents
     request body:
        <document>
        <name>My New Doc</name>
        <folderId>12345</folderId>
        </document>
      response:
        <success>
        <message>The resource of type "Document" with identifier "54321" has been successfully created.</message>
        <id>54321</id>
        </success>
2. use the new document ID when adding a data provider (ie universe ID is 5543)
      POST ../raylight/v1/documents/54321/dataproviders
      request body:
        <dataprovider>
        <name>Query 1</name>
        <dataSourceId>5543</dataSourceId>
        </dataprovider>
      response:
        <success>
        <message>The resource of type "Data provider" with identifier "DP0" has been successfully created.</message>
        <id>DP0</id>
        </success>
If you are doing something different, please provide the steps you are using and the type of datasource you are adding (unv, unx, Bex query etc).
Is the error when adding the data provider, or do you have an additional step updating the document?
Also, what version of BI4 are you working with?
Dan

Bex Report week wise

Similar Messages

Maybe you are looking for