Report on Supporting Details

Hi,
Our client has purchased a tool to load supporting details directly into Planning. This is to have the granularity of the cost details. Is there any way that we can generate a report of the supporting details. Will that be restricted to that particular combination or we can have a report of complete P&L where the accounts which have supporting details have also the list displayed below.
Can this view be possible? Please let me know.
Thanks,

hi,
For a data form ,which might be any report ( from business sense) can have supporting details ,which can be easily spotted in green colour.
For example , if its expense of some kind, and it has got supporting details , you can dig into its depth by looking into it to find it constituents ex: travel expense , hotel expense...etc.
Its like a in built calculator, and it does display list. Revert if you need any further info
Sandeep Reddy Enti
HCC
http://hyperionconsultancy.com/

Similar Messages

Financial Reporting with supporting details row suppression doesn't work

Hi,
I've a report on Planning data with a conditional suppression on Row (Advance Set-up ) and it works exactly as I want. When I activate the supporting details and run the report... the suppression does NOT WORK ANY MORE.
Can somebody help me ????
Esample of the report (I have 3 dimension in the row):
BUDGET Year
Account 1 ActivityTot WorkTot 20
Account 1 Activity1 Work1 10
Account 1 Activity1 WorkTot 10
Account 1 Activity2 Work1 10
Account 1 Activity2 WorkTot 10
Account 2 ActivityTot WorkTot 200
Account 2 Activity1 Work1 100
Account 2 Activity1 WorkTot 100
Account 2 Activity2 Work1 100
Account 2 Activity2 WorkTot 100
Account TOT ActivityTot WorkTot 220
Account TOT Activity1 Work1 110 <-- I want to suppress this
Account TOT Activity1 WorkTot 110 <-- I want to suppress this
Account TOT Activity2 Work1 110 <-- I want to suppress this
Account TOT Activity2 WorkTot 110 <-- I want to suppress this
I want to suppress in the Total Account all the rows with Activity and Work on leaf level.
Condition of suppression:
Level ACCOUNT > 0 and
( Generation ACTIVITY > 2 or Generation WORK > 2 )
Without supporting detail it works, with supporting detail not. What's wrong ?????

Another BB known issue
Users may not to able to take and restore data of the BB10 devices using BlackBerry Link if these ar...
Scenario 2:
While taking a backup using BlackBerry Link the following error is displayed:
Note: This error appears if the device is activated on BES12 using Work Space onlyActivation profile.
Backup did not complete
Verify that your device is turned on and connected to BlackBerry Link, and try again.

Report with Summary & Detail - Exporting to PDF in Crystal Report

Hi,
I am using Crystal Reports XI (release 2). I am trying out a report with Summary and Detail sections.
Requirement:
1.     Report should display both Summary and Detail Sections
2.     Summary section should be displayed first followed by Detail Section
3.     A field in summary section should have a hyperlink to Detail Section
4.     On clicking the hyperlink the user should be navigated to the corresponding detail record
5.     User should be able to download the whole report as a single PDF (i.e., both summary and detail together)
Implementation in Crystal Report:
This feature could be implemented using
a.     Linked On Demand Sub report
b.     Using Hide (Drill down ok) option
c.     Hyperlinks
Issue Faced:
I used the on demand sub report option. When i clicked on the sub report (hyperlink), the details get displayed. But the details get displayed in separate viewer and hence when we export to PDF both summary and detail are not getting exported together. User has to select each detail report and export to PDF. Is this a limitation in CR XI? - proprietary Crystal Report features, such as drill-down and on-demand subreports, are supported only in the native Crystal Report format. These special features are ignored when exporting a report to a non-Crystal format like pdf.
Is there any workaround for exporting both the summary and detail (in subreport) as a single PDF file?
Any help will be greatly appreciated.
Thanks,
Viji.

Hi
Hyperlink would not be a solution to what you are asking for.
If you want to see the records related to a particular employee id by clicking on emp id, you can try the below:
- Apply a group on employee id on the main report.
- Insert a subreport with the required fields and place it on the Employee id Group header. You can put a name of the subreport as "Check Employee details" or something else as per requirement and make it a on demand subreport.
- Link the subreport on Employee id.
Hope this helps!!!
Regards
Sourashree

Cell Comment and Supporting Detail with User ID

Hi,
I have created couple of SQL to generate the report on Cell Comments and Supporting detail from Planning repository tables 11.1.2.1.
This is working as expected Now I have additional requirement to provide the User information who added the cell comments or Supporting detail
Please let me know if anyone has this before - I wanted to know where the user information stored in these tables when someone entered cell comments
--Cell Text
SELECT
HSP_UNIQUE_NAMES.OBJECT_NAME AS Scenario,
HSP_UNIQUE_NAMES4.OBJECT_NAME AS Version,
HSP_UNIQUE_NAMES2.OBJECT_NAME AS Department,
HSP_UNIQUE_NAMES5.OBJECT_NAME AS YEAR,
HSP_UNIQUE_NAMES3.OBJECT_NAME AS Period,
HSP_UNIQUE_NAMES1.OBJECT_NAME AS Account,
HSP_CELL_NOTE.NOTE_ID,
HSP_CELL_NOTE_ITEM.CONTENTS
FROM HSP_CELL_NOTE
INNER JOIN HSP_CELL_NOTE_ITEM
ON HSP_CELL_NOTE.NOTE_ID = HSP_CELL_NOTE_ITEM.NOTE_ID
LEFT JOIN HSP_UNIQUE_NAMES
ON HSP_CELL_NOTE.DIM1 = HSP_UNIQUE_NAMES.OBJECT_ID
LEFT JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES1
ON HSP_CELL_NOTE.DIM2 = HSP_UNIQUE_NAMES1.OBJECT_ID
LEFT JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES2
ON HSP_CELL_NOTE.DIM3 = HSP_UNIQUE_NAMES2.OBJECT_ID
LEFT JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES3
ON HSP_CELL_NOTE.DIM4 = HSP_UNIQUE_NAMES3.OBJECT_ID
LEFT JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES4
ON HSP_CELL_NOTE.DIM5 = HSP_UNIQUE_NAMES4.OBJECT_ID
INNER JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES5
ON HSP_CELL_NOTE.DIM6 = HSP_UNIQUE_NAMES5.OBJECT_ID
--Supporting Detail
SELECT
HSP_UNIQUE_NAMES.OBJECT_NAME AS Scenario,
HSP_UNIQUE_NAMES4.OBJECT_NAME AS Version,
HSP_UNIQUE_NAMES2.OBJECT_NAME AS Department,
HSP_UNIQUE_NAMES5.OBJECT_NAME AS YEAR,
HSP_UNIQUE_NAMES3.OBJECT_NAME AS Period,
HSP_UNIQUE_NAMES1.OBJECT_NAME AS Account,
HSP_COLUMN_DETAIL_ITEM.LABEL,
HSP_COLUMN_DETAIL_ITEM.POSITION,
HSP_COLUMN_DETAIL_ITEM.OPERATOR,
HSP_COLUMN_DETAIL_ITEM.VALUE,
HSP_COLUMN_DETAIL.DETAIL_ID,
HSP_COLUMN_DETAIL_ITEM.GENERATION
FROM HSP_COLUMN_DETAIL
INNER JOIN HSP_COLUMN_DETAIL_ITEM
ON HSP_COLUMN_DETAIL.DETAIL_ID = HSP_COLUMN_DETAIL_ITEM.DETAIL_ID
LEFT JOIN HSP_UNIQUE_NAMES
ON HSP_COLUMN_DETAIL.DIM1 = HSP_UNIQUE_NAMES.OBJECT_ID
LEFT JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES1
ON HSP_COLUMN_DETAIL.DIM2 = HSP_UNIQUE_NAMES1.OBJECT_ID
LEFT JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES2
ON HSP_COLUMN_DETAIL.DIM3 = HSP_UNIQUE_NAMES2.OBJECT_ID
LEFT JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES3
ON HSP_COLUMN_DETAIL.DIM4 = HSP_UNIQUE_NAMES3.OBJECT_ID
LEFT JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES4
ON HSP_COLUMN_DETAIL.DIM5 = HSP_UNIQUE_NAMES4.OBJECT_ID
INNER JOIN HSP_UNIQUE_NAMES HSP_UNIQUE_NAMES5
ON HSP_COLUMN_DETAIL.DIM6 = HSP_UNIQUE_NAMES5.OBJECT_ID
Regards,
KP

I like to think of the cell comments like post-it notes. If you use them sparingly, they're very useful. If you use them all the time (or use comments in every cell) it's unlikely that they will be as effective.
With regards attaching a document, I think the same can be said.
With regards supporting detail, it always strikes me that if you need more detail within a given cell, that the system should be accommodating this through component child members, rather than a mix of some cells containing supporting detail and others not. I understand that it's quite nice functionality to have though, and looks good when demo'ing.
I think the main take away from this is that every time you show the comments etc to people the first question you get is "Can you report all the comments for a given time period?" and the answer is of course unfortunately "Not easily using a supported method".
Just my thoughts...

Cell comment, Documentation, annotation and supporting detail.

Hi All,
I am actually new to 'Hyperion Planning'. I know what comment, documentation, annotation and supporting detail means. But, can anyone tell me 'WHEN' to use each of these.
Thanks

I like to think of the cell comments like post-it notes. If you use them sparingly, they're very useful. If you use them all the time (or use comments in every cell) it's unlikely that they will be as effective.
With regards attaching a document, I think the same can be said.
With regards supporting detail, it always strikes me that if you need more detail within a given cell, that the system should be accommodating this through component child members, rather than a mix of some cells containing supporting detail and others not. I understand that it's quite nice functionality to have though, and looks good when demo'ing.
I think the main take away from this is that every time you show the comments etc to people the first question you get is "Can you report all the comments for a given time period?" and the answer is of course unfortunately "Not easily using a supported method".
Just my thoughts...

Displaying Supporting Details in FR

hi expert,
is there any way to display Supporting details in fr horizontally ?? i want to display supporting detail just like a pivot...do you have some clue??
regrd,
tyo

Hi,
To show supporting detail for the Planning Details database connection:
1 Open a report and select a row in the grid that contains a member with supporting detail.
2 In the Row Properties sheet, select Display Supporting Details.
3 Specify whether to allow page breaks with the rows of supporting detail:
a) To allow a page break within the rows of supporting detail, select the Allow Page Break Within check box.
b) To keep the parent member and the supporting detail on the same page, deselect the Allow Page Break Within check box. If the supporting detail does not the currentpage, the parent member and supporting detail is moved to the next page.
Note: If the supporting detail spans multiple pages, this option defaults to Allow Page Break Within and page breaks are used.
4 Optional: To position the supporting detail before or after the parent member, select the Grid
Properties sheet, select the Position category and select an option in the Position of Supporting Detail
box:
a) To display supporting detail before the parent member, click Before Members.
b) To display supporting detail after the parent member, click After Members. This is the default.
Regards,
Vinit

Alv Report for invoice details

Dear All,
             I need to develop one alv report for following details. i developed coding for this requirment but i am getting some error.kindley help me to how to move data from different internal table to final internal table. I used LOOP AT and READ Statement even i didn't get any output.
kindley help me out.
TYPES: BEGIN OF XT_TAB,
         LIFNR LIKE LFA1-LIFNR,
         NAME1 LIKE LFA1-NAME1,
         STCD1 LIKE LFA1-STCD1,
         STCD2 LIKE LFA1-STCD2,
         STCD3 LIKE LFA1-STCD3,
         STCD4 LIKE LFA1-STCD4,
       END OF XT_TAB.
TYPES: BEGIN OF YT_TAB,
        BUKRS LIKE BSEG-BUKRS,
        BELNR LIKE BSEG-BELNR,
        BUZEI LIKE BSEG-BUZEI,
        LIFNR LIKE BSEG-LIFNR,
        GJAHR LIKE BSEG-GJAHR,
       END OF YT_TAB.
TYPES: BEGIN OF ZT_TAB,
        LIFNR LIKE LFA1-LIFNR,
        NAME1 LIKE LFA1-NAME1,
        STCD2 LIKE LFA1-STCD2,
        BELNR LIKE BSEG-BELNR,
        BUZEI LIKE BSEG-BUZEI,
        GJAHR LIKE BSEG-GJAHR,
       END OF ZT_TAB.
       I N T E R N A L   T A B L E   D E C L A R A T I O N S         *
*-----Internal table to store data
DATA: ITAB1   TYPE STANDARD TABLE OF XT_TAB INITIAL SIZE 0,
      WA_TAB1 TYPE XT_TAB.
DATA: ITAB2   TYPE STANDARD TABLE OF YT_TAB INITIAL SIZE 0,
      WA_TAB2 TYPE YT_TAB.
DATA:   ITAB TYPE STANDARD TABLE OF ZT_TAB WITH HEADER LINE,
        WA_ITAB TYPE ZT_TAB,
        ITAB_FINAL2 TYPE STANDARD TABLE OF ZT_TAB.
DATA: ITAB_TEMP1 TYPE STANDARD TABLE OF ZT_TAB WITH HEADER LINE.
                Selection Screen Declarations                        *
SELECTION-SCREEN BEGIN OF BLOCK bk1 WITH FRAME TITLE text-001.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN begin OF LINE.
SELECTION-SCREEN COMMENT (23) text-003 FOR FIELD P_LIFNR.
PARAMETERS P_LIFNR LIKE LFA1-LIFNR OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN END OF BLOCK bk1.
START-OF-SELECTION.
      PERFORM XTRACT_DATA.
END-OF-SELECTION.
*-----Filling the Output table
PERFORM populate_main_table.
      PERFORM BUILD_FIELDCATALOG.
     PERFORM SORTING.
      PERFORM BUILD_LAYOUT.
      PERFORM BUILD_ALV_GRID_DISPLAY.
     Form XTRACT_DATA
FORM XTRACT_DATA .
*SELECT
      a~LIFNR
      a~NAME1
      a~STCD2
      b~BELNR
      b~BUZEI
      b~GJAHR
INTO TABLE ITAB
FROM LFA1 as a INNER JOIN BSEG as b
ON aLIFNR = bLIFNR
WHERE a~LIFNR = P_LIFNR.
SELECT LIFNR
       NAME1
       STCD1
       STCD2
       STCD3
       STCD4
FROM LFA1
INTO TABLE ITAB1
WHERE LIFNR = P_LIFNR.
IF NOT ITAB1[] IS INITIAL.
    SORT ITAB1 BY LIFNR.
    SELECT BELNR
           BUZEI
           LIFNR
           GJAHR
INTO TABLE ITAB2
      FROM BSEG
FOR ALL ENTRIES IN ITAB1
WHERE LIFNR = ITAB1-LIFNR.
ENDIF.
ENDFORM.                    " XTRACT_DATA
*&      Form POPULATE_MAIN_TABLE
      text
--> p1        text
<-- p2        text
FORM POPULATE_MAIN_TABLE .
   LOOP AT ITAB1 INTO WA_TAB1.
           ITAB-LIFNR = ITAB1-LIFNR.
           ITAB-NAME1 = ITAB1-NAME1.
           ITAB-STCD2 = ITAB1-STCD2.
   READ TABLE ITAB2 INTO WA_TAB2 WITH KEY LIFNR = WA_TAB1-LIFNR.
           IF sy-subrc = 0.
           ITAB-BELNR = ITAB1-BELNR.
           ITAB-BUZEI = ITAB1-BUZEI.
           ITAB-GJAHR = ITAB1-GJAHR.
           ENDIF.
ENDLOOP.
ENDFORM.                    " POPULATE_MAIN_TABLE
     Form BUILD_FIELDCATALOG
FORM BUILD_FIELDCATALOG .
REFRESH t_fcat.
CLEAR t_fcat.
wa_fcat-col_pos = 1.
wa_fcat-row_pos = 1.
wa_fcat-seltext_s = 'Vendor Number'.
wa_fcat-seltext_m = 'Vendor Number'.
wa_fcat-seltext_l = 'Vendor Number'.
wa_fcat-fieldname = 'LIFNR'.
wa_fcat-tabname = 'ITAB'.
APPEND wa_fcat TO t_fcat.
CLEAR t_fcat.
wa_fcat-col_pos = 2.
wa_fcat-row_pos = 1.
wa_fcat-seltext_s = 'Vendor Name'.
wa_fcat-seltext_m = 'Vendor Name'.
wa_fcat-seltext_l = 'Vendor Name'.
wa_fcat-fieldname = 'NAME1'.
wa_fcat-tabname = 'ITAB'.
APPEND wa_fcat TO t_fcat.
CLEAR t_fcat.
wa_fcat-col_pos = 3.
wa_fcat-row_pos = 1.
wa_fcat-seltext_s = 'Vendor TIN Number'.
wa_fcat-seltext_m = 'Vendor TIN Number'.
wa_fcat-seltext_l = 'Vendor TIN Number'.
wa_fcat-fieldname = 'STCD2'.
wa_fcat-tabname = 'ITAB'.
APPEND wa_fcat TO t_fcat.
CLEAR t_fcat.
wa_fcat-col_pos = 4.
wa_fcat-row_pos = 1.
wa_fcat-seltext_s = 'Document No'.
wa_fcat-seltext_m = 'Document No'.
wa_fcat-seltext_l = 'Document No'.
wa_fcat-fieldname = 'BELNR'.
wa_fcat-tabname = 'ITAB'.
APPEND wa_fcat TO t_fcat.
CLEAR t_fcat.
wa_fcat-col_pos = 5.
wa_fcat-row_pos = 1.
wa_fcat-seltext_s = 'Item Number'.
wa_fcat-seltext_m = 'Item Number'.
wa_fcat-seltext_l = 'Item Number'.
wa_fcat-fieldname = 'BUZEI'.
wa_fcat-tabname = 'ITAB'.
APPEND wa_fcat TO t_fcat.
CLEAR t_fcat.
wa_fcat-col_pos = 6.
wa_fcat-row_pos = 1.
wa_fcat-seltext_s = 'Fiscal Year'.
wa_fcat-seltext_m = 'Fiscal Year'.
wa_fcat-seltext_l = 'Fiscal Year'.
wa_fcat-fieldname = 'GJAHR'.
wa_fcat-tabname = 'ITAB'.
APPEND wa_fcat TO t_fcat.
CLEAR t_fcat.
ENDFORM.                    " BUILD_FIELDCATALOG
     Form BUILD_LAYOUT
FORM BUILD_LAYOUT .
GD_LAYOUT-NO_INPUT = 'X'.
GD_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
GD_LAYOUT-TOTALS_TEXT = 'TOTALS'.
ENDFORM.                    " BUILD_LAYOUT
     Form BUILD_ALV_GRID_DISPLAY
FORM BUILD_ALV_GRID_DISPLAY .
gd_repid = sy-repid.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
            i_callback_program      = gd_repid
            i_callback_top_of_page = 'TOP-OF-PAGE' "see FORM
            i_callback_user_command = 'USER_COMMAND'
            is_layout               = gd_layout
            it_fieldcat             = t_fcat[]
            it_events               = gt_events
            is_print                = gd_prntparams
            it_sort                 = it_sortcat[]
            i_save                  = 'X'
       TABLES
            t_outtab                = ITAB
       EXCEPTIONS
            program_error           = 1
            OTHERS                  = 2.
thanks and regards
Murugesh

TYPES: BEGIN OF XT_TAB,
         LIFNR LIKE LFA1-LIFNR,
         NAME1 LIKE LFA1-NAME1,
         STCD1 LIKE LFA1-STCD1,
         STCD2 LIKE LFA1-STCD2,
         STCD3 LIKE LFA1-STCD3,
         STCD4 LIKE LFA1-STCD4,
       END OF XT_TAB.
TYPES: BEGIN OF YT_TAB,
        BUKRS LIKE BSEG-BUKRS,
        BELNR LIKE BSEG-BELNR,
        BUZEI LIKE BSEG-BUZEI,
        LIFNR LIKE BSEG-LIFNR,
        GJAHR LIKE BSEG-GJAHR,
       END OF YT_TAB.
TYPES: BEGIN OF ZT_TAB,
        LIFNR LIKE LFA1-LIFNR,
        NAME1 LIKE LFA1-NAME1,
        STCD2 LIKE LFA1-STCD2,
        BELNR LIKE BSEG-BELNR,
        BUZEI LIKE BSEG-BUZEI,
        GJAHR LIKE BSEG-GJAHR,
       END OF ZT_TAB.
       I N T E R N A L   T A B L E   D E C L A R A T I O N S         *
*-----Internal table to store data
DATA: ITAB1   TYPE STANDARD TABLE OF XT_TAB INITIAL SIZE 0,
      WA_TAB1 TYPE XT_TAB.
DATA: ITAB2   TYPE STANDARD TABLE OF YT_TAB INITIAL SIZE 0,
      WA_TAB2 TYPE YT_TAB.
DATA:   ITAB TYPE STANDARD TABLE OF ZT_TAB WITH HEADER LINE,
        WA_ITAB TYPE ZT_TAB,
        ITAB_FINAL2 TYPE STANDARD TABLE OF ZT_TAB.
DATA: ITAB_TEMP1 TYPE STANDARD TABLE OF ZT_TAB WITH HEADER LINE.
                Selection Screen Declarations                        *
SELECTION-SCREEN BEGIN OF BLOCK bk1 WITH FRAME TITLE text-001.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN begin OF LINE.
SELECTION-SCREEN COMMENT (23) text-003 FOR FIELD P_LIFNR.
PARAMETERS P_LIFNR LIKE LFA1-LIFNR OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN END OF BLOCK bk1.
START-OF-SELECTION.
      PERFORM XTRACT_DATA.
END-OF-SELECTION.
*-----Filling the Output table
PERFORM populate_main_table.
      PERFORM BUILD_FIELDCATALOG.
     PERFORM SORTING.
      PERFORM BUILD_LAYOUT.
      PERFORM BUILD_ALV_GRID_DISPLAY.
     Form XTRACT_DATA
FORM XTRACT_DATA .
*SELECT
      a~LIFNR
      a~NAME1
      a~STCD2
      b~BELNR
      b~BUZEI
      b~GJAHR
INTO TABLE ITAB
FROM LFA1 as a INNER JOIN BSEG as b
ON aLIFNR = bLIFNR
WHERE a~LIFNR = P_LIFNR.
SELECT LIFNR
       NAME1
       STCD1
       STCD2
       STCD3
       STCD4
FROM LFA1
INTO TABLE ITAB1
WHERE LIFNR = P_LIFNR.
IF NOT ITAB1[] IS INITIAL.
    SORT ITAB1 BY LIFNR.
    SELECT BELNR
           BUZEI
           LIFNR
           GJAHR
INTO TABLE ITAB2
      FROM BSEG
FOR ALL ENTRIES IN ITAB1
WHERE LIFNR = itab1-lifnr.
ENDIF.
ENDFORM.                    " XTRACT_DATA
*&      Form POPULATE_MAIN_TABLE
      text
--> p1        text
<-- p2        text
FORM POPULATE_MAIN_TABLE .
LOOP AT ITAB1 INTO WA_TAB1.
          ITAB-LIFNR = ITAB1-LIFNR.
          ITAB-NAME1 = ITAB1-NAME1.
          ITAB-STCD2 = ITAB1-STCD2.
READ TABLE ITAB2 INTO WA_TAB2 WITH KEY LIFNR = WA_TAB1-LIFNR.
          IF sy-subrc = 0.
          ITAB-BELNR = ITAB1-BELNR.
          ITAB-BUZEI = ITAB1-BUZEI.
          ITAB-GJAHR = ITAB1-GJAHR.
          ENDIF.
ENDLOOP.
LOOP AT itab1 INTO wa_tab1.
   MOVE: wa_tab1-lifnr TO itab-lifnr,
          wa_tab1-name1 TO itab-name1,
          wa_tab1-stcd2 TO itab-stcd2.
      Append itab.
READ TABLE itab2 TRANSPORTING NO FIELDS WITH KEY lifnr = wa_tab1-lifnr.
IF sy-subrc eq 0.
    MOVE: wa_tab2-lifnr TO itab-lifnr,
          wa_tab2-belnr TO itab-belnr,
          wa_tab2-buzei TO itab-buzei,
          wa_tab2-gjahr TO itab-gjahr.
Append itab.
endif.
endloop.
*LOOP AT t_agr_tcodes INTO s_agr_tcodes.
READ TABLE t_tstc
TRANSPORTING NO FIELDS
WITH KEY tcode = s_agr_tcodes-tcode.
IF sy-subrc eq 0.
   MOVE: s_agr_tcodes-tcode TO it_agr_tcodes-tcode,
         s_agr_tcodes-agr_name to it_agr_tcodes-agr_name,
         t_tstc-pgmna to it_agr_pgmna.
*Append it_agr_tcodes.
*endif.
*endloop.
ENDFORM.                    " POPULATE_MAIN_TABLE
     Form BUILD_FIELDCATALOG
FORM BUILD_FIELDCATALOG .
REFRESH t_fcat.
CLEAR t_fcat.
wa_fcat-col_pos = 1.
wa_fcat-row_pos = 1.
wa_fcat-seltext_s = 'Vendor Number'.
wa_fcat-seltext_m = 'Vendor Number'.
wa_fcat-seltext_l = 'Vendor Number'.
wa_fcat-fieldname = 'LIFNR'.
wa_fcat-tabname = 'ITAB'.
APPEND wa_fcat TO t_fcat.
CLEAR t_fcat.
wa_fcat-col_pos = 2.
wa_fcat-row_pos = 1.
wa_fcat-seltext_s = 'Vendor Name'.
wa_fcat-seltext_m = 'Vendor Name'.
wa_fcat-seltext_l = 'Vendor Name'.
wa_fcat-fieldname = 'NAME1'.
wa_fcat-tabname = 'ITAB'.
APPEND wa_fcat TO t_fcat.
CLEAR t_fcat.
wa_fcat-col_pos = 3.
wa_fcat-row_pos = 1.
wa_fcat-seltext_s = 'Vendor TIN Number'.
wa_fcat-seltext_m = 'Vendor TIN Number'.
wa_fcat-seltext_l = 'Vendor TIN Number'.
wa_fcat-fieldname = 'STCD2'.
wa_fcat-tabname = 'ITAB'.
APPEND wa_fcat TO t_fcat.
CLEAR t_fcat.
wa_fcat-col_pos = 4.
wa_fcat-row_pos = 1.
wa_fcat-seltext_s = 'Document No'.
wa_fcat-seltext_m = 'Document No'.
wa_fcat-seltext_l = 'Document No'.
wa_fcat-fieldname = 'BELNR'.
wa_fcat-tabname = 'ITAB'.
APPEND wa_fcat TO t_fcat.
CLEAR t_fcat.
wa_fcat-col_pos = 5.
wa_fcat-row_pos = 1.
wa_fcat-seltext_s = 'Item Number'.
wa_fcat-seltext_m = 'Item Number'.
wa_fcat-seltext_l = 'Item Number'.
wa_fcat-fieldname = 'BUZEI'.
wa_fcat-tabname = 'ITAB'.
APPEND wa_fcat TO t_fcat.
CLEAR t_fcat.
wa_fcat-col_pos = 6.
wa_fcat-row_pos = 1.
wa_fcat-seltext_s = 'Fiscal Year'.
wa_fcat-seltext_m = 'Fiscal Year'.
wa_fcat-seltext_l = 'Fiscal Year'.
wa_fcat-fieldname = 'GJAHR'.
wa_fcat-tabname = 'ITAB'.
APPEND wa_fcat TO t_fcat.
CLEAR t_fcat.
ENDFORM.                    " BUILD_FIELDCATALOG
     Form BUILD_LAYOUT
FORM BUILD_LAYOUT .
GD_LAYOUT-NO_INPUT = 'X'.
GD_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
GD_LAYOUT-TOTALS_TEXT = 'TOTALS'.
ENDFORM.                    " BUILD_LAYOUT
     Form BUILD_ALV_GRID_DISPLAY
FORM BUILD_ALV_GRID_DISPLAY .
gd_repid = sy-repid.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
            i_callback_program      = gd_repid
            i_callback_top_of_page = 'TOP-OF-PAGE' "see FORM
            i_callback_user_command = 'USER_COMMAND'
            is_layout               = gd_layout
            it_fieldcat             = t_fcat[]
            it_events               = gt_events
            is_print                = gd_prntparams
            it_sort                 = it_sortcat[]
            i_save                  = 'X'
       TABLES
            t_outtab                = ITAB
       EXCEPTIONS
            program_error           = 1
            OTHERS                  = 2.
Edited by: Murugesh P on Apr 6, 2009 10:54 AM
Edited by: Murugesh P on Apr 6, 2009 10:54 AM

Summary Report using Master-Detail Data on Siebel BI Publisher Report

I have to create a Summary Report using Master-Detail relationship. Report fields are Account Name, Special Need Type, Customer Status, No of Customers, No of Claims. I am using rtf to create template and any help is highly appreciated
<?xml version="1.0" encoding="UTF-8" ?>
- <ListofIO>
- <ListOfBipCustomerSpecialNeeds>
- <Account>
<Name>CVNE</Name>
- <ListOfContact>
- <Contact>
<SpecialNeedsFlg>Y</SpecialNeedsFlg>
<SpecialNeedsType>Large Text</SpecialNeedsType>
<PersonUId>1-6NI9</PersonUId>
- <ListOfContact_Claims>
- <Contact_Claims>
<AccountNumber>TEST0015362272</AccountNumber>
<ClaimNumber>1-4FVL</ClaimNumber>
<ClaimStatus>Closed</ClaimStatus>
<ClaimGBPAmount />
</Contact_Claims>
</ListOfContact_Claims>
</Contact>
- <Contact>
<SpecialNeedsFlg>Y</SpecialNeedsFlg>
<SpecialNeedsType>Braille</SpecialNeedsType>
<PersonUId>1-L0A</PersonUId>
- <ListOfContact_Claims>
- <Contact_Claims>
<AccountNumber />
<ClaimNumber>1-ACX6</ClaimNumber>
<ClaimStatus>Open</ClaimStatus>
<ClaimGBPAmount>818.18196694218</ClaimGBPAmount>
</Contact_Claims>
- <Contact_Claims>
<AccountNumber />
<ClaimNumber>1-GI58</ClaimNumber>
<ClaimStatus />
<ClaimGBPAmount>45454.099173473</ClaimGBPAmount>
</Contact_Claims>
</ListOfContact_Claims>
</Contact>
- <Contact>
<SpecialNeedsFlg>Y</SpecialNeedsFlg>
<SpecialNeedsType>Large Text</SpecialNeedsType>
<PersonUId>1-6FPP</PersonUId>
- <ListOfContact_Claims>
- <Contact_Claims>
<AccountNumber>CVNE</AccountNumber>
<ClaimNumber>1-7BRL</ClaimNumber>
<ClaimStatus>Reviewed</ClaimStatus>
<ClaimGBPAmount>562</ClaimGBPAmount>
</Contact_Claims>
</ListOfContact_Claims>
</Contact>
</ListOfContact>
</Account>
<Login>SADMIN</Login>
</ListOfBipCustomerSpecialNeeds>
</ListofIO>
Edited by: user2298324 on 13-Aug-2010 09:36

Thanks for the reply. The many to many relationship between Claims and Payments are achieved through intersection table in siebel. When Customer has multiple claims, single payment issued for both claims. Also single claim can multiple payments such (part compensation, interests, final compensation etc)

Report with multiple Detail Area

Hi All,
Please see the Report pointed to the link below:
[Report with multiple Detail Area|http://us.share.geocities.com/felix5ac/fairway.jpg]
Some Explanations:
========================
(1) The line with "ABCDEFGH..." is variable data coming from the database in the Detail Area
(2) The lines with "WBLNX'" "123, 123.12",
"WBLNX'"
are variable data associated with the same Heading: "ABCDEFGH..."
(2b) There can be multiple lines of data in the detail area (i.e. 1 or more "ABCDEFGH..." and the associated WBLNX and numbers...)
(3) Item Code Descriptions ==> is a Header Info
(4) ARL ... and FPHI... ==> are variable data and lines in these area can be 1 line; it can be 4 lines; it can be 10 lines...
(5) Lines FROM "Artwork Procedures..." to the the end of the page are static.
QUESTION:
===================
How do I best design these Report with the multiple detail areas? Again, please see link of the Report above...
Thanks and Best regards,
Felix

Hi Felix
You can place the less detailed fields in the regular sections of the report and wherever you require multiple lines you can use the subreports.
Hope this helps.
Regards
Nikhil

Report Row With Detail (AJAX) by Carl - How to implement?

I just had a look at Carl's example place and I'd like to implement his Report Row With Detail feature. But how, it's made up of 3 sections:
1. a query
2. javascript
3. application process
The query on which the report is based and where I want this feature is:
select leverancier, artnr, vendorcode from plijst where productgroep = :p1_assortiment_tree or subgroep = :p1_assortiment_tree
A break is defined on Leverancier
I understand the query and the application process part. But where goes the Java part???
Peter
Message was edited by:
Pete

Tried to upload your example application, unfortunately it does not seem to upload properly in my APEX v2.0 environment
Can you please confirm if your example works with APEX version 2
and does the Javascript go in the Page Header or Region Header/ Footer area
thankyou
Frank

Report Row With Detail (IFRAME)

Hi,
I am trying to implement the Report Row with Detail but not successful.
I have gone thru the various threads in the forum.. but i am unable to
get it. It would be great if I could know the step by step process to do the same.
I have created two regions. The first region (the query to it) also
has a show_region link.. I have copied and pasted the javascript given
by Carl.
Thanks,
shilpa.

Hello,
Ok then you are almost there so when you submit the form to update your data on a sucessful save you are going to create a plsql region that just uses htp.p() to write out the javascript to update the report in the main page.
a simple example would be something like this.
Lets say I'm getting back values to update the two first table cells on my parent report.
<script>
/*set up call back function*/
function ReportRowUpdate(){
var lRow = parent.g_LastRowOpened; /* hook to last row clicked */
lRow.cells[0].innerHTML = 'SOME VALUE FROM DATABASE 1';
lRow.cells[1].innerHTML = 'SOME VALUE FROM DATABASE 2';
/*call call back function*/
ReportRowUpdate();
</script>
And that should be it.
Carl
Message was edited by:
Carl Backstrom

Report Row With Detail (IFRAME) - How to reload Main Page within iFrame

Hi,
Based on Carl's example - Report Row With Detail (IFRAME), i.e:
http://htmldb.oracle.com/pls/otn/f?p=11933:17
Within my scenario, I have a button within the iframe section of my report that calls a pl/sql process that performs some database processing.
What I basically need is a means of performing a page refresh of the main page, when this button within the iframe is pressed. In Carl's example, that would be page 17.
As mentioned, I call a PL/SQL process within the iframe, but unsure how to then refresh the main page - parent page.
Any help would be appreciated.
Thanks.
Tony.

Tony,
you could insert the following script to the region footer of a region located on your "iframe"-page.
<script>
parent.location.reload();
</script>
But this is dangerous because everytime the parent is being reloaded, the iframe is loaded, too. Risk of loop...
A possible solution is to conditionally display a html region (with the script) on your iframe-page basing on a request. You could post the request as a result after your plsql processing in a branch.
Regards,
Jens

Report row with detail (AJAX)

Hi,
In Carl's report row with detail (AJAX) demo, is there any way to show all detail row by default when the page is loaded?
http://apex.oracle.com/pls/otn/f?p=11933:13
Thanks.
Andy

Hi Andy,
In Carl's example, the "details" content seems to be from a table that has a one-to-one relationship with the main table. If this is the case, you would probably find it easier to use a "Named Column (row template)" type of report template and lay out the report as you need it rather than use Ajax
Otherwise, I'm sure it would be possible to loop through a report and make a series of Ajax calls to retrieve the details should there be multiple records required.
Andy

Which Table will have 'Report to Report Interface (RRI)' Details?

Hi all,
Which table will have 'Report to Report Interface (RRI)' Details after creating them with RSBBS Tcode, PLEASE.
Thanks in advance.

Hi,
Serach in these tables
RSBBSCUBE
RSBBSCUBEDIR
RSBBSQUERYDIR
Cheers..
Krishna

Planning Application - Supporting Details

Hi,
We deleted around 4000 members from our planning application and later realised that the few members have budget values tagged to them and also supporting details are included for few of the members. Now we would like to bring back those members to our application. Could you please suggest the best method to bring back those members and the associated supporting details. We donot want to restore the entire the entire application. Is there a way to restore only that particular dimension and its members and the supporting details associated with them. If yes, could anyone of you let me know the process. Our relational DB is SQL 2005.
Request your help for the closure
Thanks,

Assuming you have a backup of your SQL database somewhere (this would be the Planning repository), the following code will extract Supporting Detail:
Supporting Detail
SELECT
     "Plan Type" = P.TYPE_NAME,
     "Scenario" = O1.OBJECT_NAME,
     "Account" = O2.OBJECT_NAME,
     "Entity" = O3.OBJECT_NAME,
     "Month" = O4.OBJECT_NAME,
     "Version" = O5.OBJECT_NAME,
     "Year" = O6.OBJECT_NAME,
     "Activities" = O7.OBJECT_NAME,
     "Employee" = O8.OBJECT_NAME,
     "Value" = I.VALUE,
     "Position" = I.POSITION,
     "Generation" = I.GENERATION,
     "Operator" = I.OPERATOR,
     "SD" = I.LABEL
FROM HSP_COLUMN_DETAIL D
     INNER JOIN HSP_PLAN_TYPE P
          ON D.PLAN_TYPE = P.PLAN_TYPE
     INNER JOIN HSP_COLUMN_DETAIL_ITEM I
          ON D.DETAIL_ID = I.DETAIL_ID
     INNER JOIN HSP_OBJECT O1
          ON D.DIM1 = O1.OBJECT_ID
     INNER JOIN HSP_OBJECT O2
          ON D.DIM2 = O2.OBJECT_ID
     INNER JOIN HSP_OBJECT O3
          ON D.DIM3 = O3.OBJECT_ID
     INNER JOIN HSP_OBJECT O4
          ON D.DIM4 = O4.OBJECT_ID
     INNER JOIN HSP_OBJECT O5
          ON D.DIM5 = O5.OBJECT_ID
     INNER JOIN HSP_OBJECT O6
          ON D.DIM6 = O6.OBJECT_ID
     LEFT OUTER JOIN HSP_OBJECT O7
          ON D.DIM7 = O7.OBJECT_ID
     LEFT OUTER JOIN HSP_OBJECT O8
          ON D.DIM8 = O8.OBJECT_IDYou'll want to modify it a bit to get it to work with your dimensions -- this is from an old project of mine.
I have never tried to write Supporting Detail back in -- I know it has been done, just not by me. I would tread very carefully and only do it on a test database and be really, really, really sure you've got everything working just so. You could easily blow up your data.
Another approach might be to restore that Planning app backup (making sure you made a backup of the current app), and then use LCM to export out Supporting detail, and then suck it back into the app that no longer has it.
^^^I like that idea a lot more even if it is a bit more tedious.
With either approach, you are going to have to sync the Essbase data to the SD data -- hopefully you have a good Essbase backup as well.
Regards,
Cameron Lackpour

Report on Supporting Details

Similar Messages

Maybe you are looking for