Display an extra column in the standrad report using LDB

my requirement is like this
1) to add one more parameter region in the selection screen of VI98
2) Display the region column in the output in the 3rd position
is there any way to add one more parameter in the selection screen of transaction VI98 and based on the region entered the output should be filterd(ie the records of given region only should come)
this program is using ldb VXV
and selection screen 600
is there any way to achieve this ?

hi first check the report catagory of the LDB report and check whether is there any field available there...other wise create a new report catagory..

Similar Messages

How can I add extra tick-box columns to the Evaluation report template?

Is there a simple way to add additional tick-box columns to the evaluation report template? I want to have a column for every day of the week.

Are you part of a class project? We've just had another query on this template.
+Menu > View > Show Ruler/Invisibles+
The "columns" are just boxes and text aligned with tabs.
Select all of them and slide the tabs on the ruler across to tighten up the spacing.
Add more tabs to the ruler by clicking on the ruler where you want them, then right clicking on the Tab markers to change them to the type you want.
Copy and paste extra copies of the +tabs plus box+ in each line.
Peter

GR and IR as separate columns in the BEx report

Hi,
I am working on a Purchasing report in which the user needs the snap shot of PO history,Like PO no.,Item,Netprice,PO Qty,Net order value,GR no.,IR number etc.
I created a view on EKPO and EKBE.Here,based on the BELNR(Material document) field we are taking GR and IR values.(When VGABE =1 BELNR=GR and VGABE = 2 BELNR=IR).I created DSO to load the data.The problem is they need the GR and IR as separate columns in the BEx report.Could u please help me how to achieve this in BI?
Thanks & Regards,
Dinakar.

Hi Neel,
I need the BELNR has to be split into GR No.and IR No. separately based on VGABE field.
Thanks & Regards,
Dinakar.

Urgent: Issue while displaying the PDF Reports Using XDO Common region

Hi all,
In our product code we are trying to display the PDF Reports, using the xdo common region.
Previously we were writing the pdf reports direclty onto the response direclty.
This displays the report onto the browser but if navigate throw browser back button, it doesn't displays the report as the response stream is empty while navigating through back button.
So to solve this issue, i tried to write the report using the OAHTMLWebBean and xdo common region. Here is the code:
ByteArrayOutputStream xdoOutput = new ByteArrayOutputStream();
XDOUtility.retrieveReport(xdoOutput,
parameters,
prop,
appMod
BlobDomain bxdoOutput = new BlobDomain();
bxdoOutput.setBytes(xdoOutput.toByteArray());
String redirectURL = DocumentHelper.getOutputURL(pageContext,
bxdoOutput,
"Report",
"PDF");
OAHTMLWebBean outRegion = (OAHTMLWebBean)createWebBean (pageContext, OAWebBeanConstants.HTML_WEB_BEAN, null, "IFRAME");
outRegion.setHTMLAttributeValue("src", redirectURL);
outRegion.setHTMLAttributeValue("width", "100%");
outRegion.setHTMLAttributeValue("height", "100%");
outRegion.setHTMLAttributeValue("title","Report");
outRegion.setHTMLAttributeValue("name","Report");
pageContext.getPageLayoutBean().addIndexedChild(outRegion);
This successfully displays the report in the XDO Common region. But now the issue is that there are hyperlinks in the Report displayed where from where the user can navigate to other detail pages.
When we click on these links, a new session starts in the xdo common region.
Is it possible that when the user click the links in the report displayed, instead of starting a new session in the xdo region, the detail pages is displayed with in the older session.
Regards
Sandeep

Hi all,
In our product code we are trying to display the PDF Reports, using the xdo common region.
Previously we were writing the pdf reports direclty onto the response direclty.
This displays the report onto the browser but if navigate throw browser back button, it doesn't displays the report as the response stream is empty while navigating through back button.
So to solve this issue, i tried to write the report using the OAHTMLWebBean and xdo common region. Here is the code:
ByteArrayOutputStream xdoOutput = new ByteArrayOutputStream();
XDOUtility.retrieveReport(xdoOutput,
parameters,
prop,
appMod
BlobDomain bxdoOutput = new BlobDomain();
bxdoOutput.setBytes(xdoOutput.toByteArray());
String redirectURL = DocumentHelper.getOutputURL(pageContext,
bxdoOutput,
"Report",
"PDF");
OAHTMLWebBean outRegion = (OAHTMLWebBean)createWebBean (pageContext, OAWebBeanConstants.HTML_WEB_BEAN, null, "IFRAME");
outRegion.setHTMLAttributeValue("src", redirectURL);
outRegion.setHTMLAttributeValue("width", "100%");
outRegion.setHTMLAttributeValue("height", "100%");
outRegion.setHTMLAttributeValue("title","Report");
outRegion.setHTMLAttributeValue("name","Report");
pageContext.getPageLayoutBean().addIndexedChild(outRegion);
This successfully displays the report in the XDO Common region. But now the issue is that there are hyperlinks in the Report displayed where from where the user can navigate to other detail pages.
When we click on these links, a new session starts in the xdo common region.
Is it possible that when the user click the links in the report displayed, instead of starting a new session in the xdo region, the detail pages is displayed with in the older session.
Regards
Sandeep

How to use one report column into the another report in obiee

How to use one report column into the another report in obiee

i dont want to use column as a filter for another report it should be report column for another report
Thanks,
Vivek

Change Column Headings in ALV Report Using OO

Hi Friends,
I am using OO to display a report with ALV Grid
I tried to change the column names but it still takes the column names from the DDIC.
My declaration is as follows
Data: num type dmbtr.
TRY.
            lr_column ?= lr_columns->get_column( columnname = 'NUM' ).
            lr_column->set_output_length('7').
            lr_column->set_long_text( ' Value' ).
           lr_column->set_short_text( ''() ).
            lr_column->set_medium_text( 'Value' ).
          CATCH cx_salv_not_found INTO gr_error.
            gr_msg = gr_error->get_text( ).
            MESSAGE gr_msg TYPE 'I'.
        ENDTRY.
*--- display report
        gr_table->display( ).
      CATCH cx_salv_msg.
        WRITE: 'Error displaying grid! - cx_salv_msg'(044).
      CATCH cx_salv_not_found.
        WRITE: 'Error displaying grid! - cx_salv_not_found'(004).
      CATCH cx_salv_data_error.
        WRITE: 'Error displaying grid! - cx_salv_data_error'(005).
      CATCH cx_salv_existing.
        WRITE: 'Error displaying grid! - cx_salv_existing'(006).
I need the column name as VALUE but it displays as Amount LC in the alv report.
Thanks
chaithanya

Hey hello,
you have to change short medium and log text
look at this:
gr_columns = (Table got from factory)->get_columns( ).
gr_column = gr_columns->get_column('NAme').
gr_column->set_long_text('new name long').
gr_column->set_medium_text('new name medium').
gr_column->set_short_text('new name short ).
it will help
thanks
Edited by: Alfito on Nov 28, 2011 9:31 AM

How to migrate the discoverer reports using the PPM tool

Hi,
Did Any One Migrate the Discoverer Reports Using The PPM (Kintana Tool) From One Oracle Instance To The Other?
Please Help Me If Any One Knows?
Thanks,
Ankit

Hi User,
Create a new shared folder.
Provide access to all the users.
Now, ask the user who created the report in 'My Folders' to save the report in this new shared folder.
And, Delete those reports in 'My Folders'.
Now, as the report is saved in New shared folder you can access - this one.
Else--- Ask the user who created the report in my folder to make sure that it is available to all users. (Permissions - Permission should need to be provided for Administrator group)
Thank you.

How to print out multilingual reports from the main report using Xliff temp

Hi all,
How to print out multilingual reports from the main report using Xliff temp?
When I want main report call subtemplate and finish xliff tranlation
<?for-each@section:INVOICE?><?end for-each?>
<?import:xdo://XXIH.XXNR_XXINVPRINT_SUB.en.FI/?>
<?start:body?><?call:Header?><?call:Line?><?call:Weights?><?call:Banks?><?end body?><?call:Footer?>
Prints out fine with Finnish translation
But if I want in main program to check what language is used e.g.
if trx_number = 142 call Finnish translation and if trx_number =144,
call English translation.
<?for-each@section:INVOICE?><?end for-each?>
<?if:TRX_NUMBER=’142’?>
<?import:xdo://XXIH.XXNR_XXINVPRINT_SUB.en.FI/?>
<?start:body?><?call:Header?><?call:Line?><?call:Weights?><?call:Banks?><?end body?><?call:Footer?>
<?end if?>
<?if: TRX_NUMBER=’144’?>
<?import:xdo://XXIH.XXNR_XXINVPRINT_SUB.en.US/?>
<?start:body?><?call:Header?><?call:Line?><?call:Weights?><?call:Banks?><?end body?><?call:Footer?>
<?end if?>
Prints out always in English and never the Finnish translation.
Program goes fine to if branch but does not print out Finnish
Does anybody know what could be wrong?
BR
Kari

Thanks Amit,
I have two layout, main-layout and sub-layout
Main layout call subtemplate
I have registered layout and xliff-file
Main template
Localized Templates
File Name           Language Territory
XXNS_INVOICE_MAIN.rtf      English
SUB template
Localized Templates
File Name           Language Territory
XXNS_INVOICE_SUB.rtf      English
Translatable Template
File Name           Language      Territory
XXNS_INVOICE_SUB.rtf      English      United States
Available Translations
Language Territory Progress
English Finland Complete
If main report call subtemplate and finish xliff tranlation
<?import:xdo://XXIH.XXNR_XXINVPRINT_SUB.en.FI/?>
Prints out fine with Finnish translation
But if I want in main program to check what language is used e.g.
if....
<?import:xdo://XXIH.XXNR_XXINVPRINT_SUB.en.FI/?>
.....end if;
if....
<?import:xdo://XXIH.XXNR_XXINVPRINT_SUB.en.US/?>
.....end if;
Prints out always in English and never the Finnish translation.
Program goes fine to if branch but does not print out Finnish
Do you it's set up problem or program problem
BR
Kari

Option Click on the Volume menubar icon doesn't display ALL airplay devices, just the last one used

Option Click on the Volume menubar icon doesn't display ALL airplay devices, just the last one used. I've seen other peoples display all their devices. Why can't I?

I've discovered that those screenshots where you see more than one speaker listed in the menubar icon are actually bluetooth devices, not airplay. When you check the shot of the system preferences pane and see them all listed there too, the Type says Bluetooth. Not sure why bluetooth gets them all listed and apple's own airplay standard does not. Hope a developer writes a mac app to do it!

Want to have own selection screen in HR-ABAP report using LDB

Hi experts,
        I am working on HR-ABAP report using LDB pnp and infotypes..But, here we get the built in selection criterion..but I want my own selection screen to be displayed..whats the solution for this??? Is it possible to create my own selection screen instead of default one..and how???
Please help me..its very urgent..

Hi,
chk this out:
Create Report Categories
In this step, you define the report categories and determine the layout
   of the standard selection screen for these report categories. You can
   create report categories for programs or queries that are based on the
   PNP or PNPCE logical databases.
The definition of report categories is divided into two sections:
o   In the Change Report Category view, you define general attributes
       such as sort order, input fields for date, and so on.
o   In the Change Selection Criteria view, you define which selection
       fields of the logical database should be avaliable on the selection
       screen.
Example
You want to set up your system so that your employees can only start
   evaluation reports for Payroll if they use a payroll area. Within a
   payroll area, you should be able to select according to personnel
   number. Additional selection criteria should not be possible and you
   should not be allowed to enter a sort sequence.
Standard settings
The standard system already contains report categories. You can find the
attributes of the report categories in the table.
Note the following five report categories in particular:
o   Report category ' ' is the SAP default report category for
    programs that are based on the PNP logical database.
o   Report category PNPCE is the SAP default category for programs that
    are based on the PNPCE logical database.
o   Report category '00000000' is the customer-specific default category
    for programs that are based on the PNP logical database.
o   Report category '0PNPCE' is the customer-specific default category
    for programs that are based on the PNPCE logical database.
o   Report category __X2001 is the default category for Queries that
    are based on an InfoSet of the PNP LDB.
o   Report category QUEPNPCE is the default category for queries that
    are based on an InfoSet of the PNPCE LDB.
The default report categories are used when a report is called if
    the report has not been assigned a report category.
Parameters and Options for Report Categories of the LDB PNP and PNPCE
Parameters and Options in Screen Area General Data
   If you activate this parameter, you can only enter data on the data
   selection period if you use reports that have been assigned. The
   same date entries are then used for the person selection as for the
   date selection.
o   Matchcode allowed
   If you activate this parameter, you have use of a Matchcode
   pushbutton (search help) if you use reports that have been assigned.
   This pushbutton enables you to perform the person selection.
o   Sort allowed
   If you activate this parameter, you have use of a Sort pushbutton if
   you use report that have been assigned. This pushbutton enables you
   to define a sort order before you execute the report.
o   Organizational structure allowed
   If you activate this parameter, you have use of an Org.Structure
   pushbutton if you use reports that have been assigned. This
   pushbutton enables you to perform the person selection.
   Note:
   For more information about these options, see the online
   documentation under this path:
   SAP Library -> Human Resources -> Reporting in Human Resources
   Management -> Standard HR Reports -> Report Selection Screen in
   Human Resources Management.
Parameters and Options in Screen Areas Data Selection Period/Person
Selection Period/Payroll Area/Period/Year
o   Options for data selection period and person selection period (key
    date and so on)
    Here you define which options for date and person selection are
    available for reports that have been assigned.
o   Options for payroll area/period/year
    Here you define which options for selection using payroll
    area/period/year are available for reports that have been assigned.
Parameters and Options in Screen Area Selection View
o   Type/Name
    This parameter enables you to use selection views to define report
    categories. You use the selection view selected here to determine
    which fields are available in the Dynamic Selectionsy.
Note:
    You create selection views for the PNP and PNPCE logical databases
    in the Object Navigator (SE80):
    1. Start the Object Navigator (SE80)
    2. Choose Workbench -> Edit Object.
    3. Choose the More... tab page and the Selection view on this tab
    page.
    4. Choose Create.
    5. In the Create Selection View dialog box, choose the For any
    tables option.
    6. In the Name of view field, enter a name for your selection view.
    7. In the Tables dialog box, enter the name of the table from which
    you want to use fields.
    Note:
    When you enter the table name, observe the naming convention in
    Personnel Administration:
    Infotype number: nnnn -> table name: PAnnnn
    8. Choose Continue.
    9. In the Functional groups area, define functional groups by
    assigning a name and a number.
    10. Assign fields from the selected tables to the functional groups
    by entering the number of the desired functional group in front of
    each field.
    11. Save your entries.
For more information about adjusting the dynamic selections using
your own selection views, see the online documentation under the
following menu path:
SAP Library -> Human Resources -> Reporting in Human Resources
Management -> HR Standard Reports -> Report Selection Screen in
Human Resources Management -> Enhancing the Selection Screen -
Dynamic Selections.
If you do not want to offer dynamic selections, make the following
settings:
-   LDB PNP: In the Selection view field, enter PNP_NO_FREE_SEL.
-   LDB PNPCE: Leave the Selection view field empty.
Parameters and Options in Screen Area Data Selection Period/Person
Selection Period/Payroll Area/Period/Year
o   Available input parameters, date or period entry (today, key date,
   all, and so on), and standard value.
   Using the Standard value option, you define which of the selected
   options is shown.
Parameters and Options in Screen Area CE Selection Fields
o   CE selection fields (external person ID, grouping reason, grouping
   value)
   Using the options in this area, you define whether the external
   person Id, grouping reason, or grouping value are available on the
   selection screen.
   Note:
   These parameters are only relevant for you if you implement
   Concurrent Employment (see also note 517071).
Parameters and Options in Screen Area Selection view
o   Dynamic selections as dialog box
    If this switch is set, you can call the dynamic selections as a
    dialog box.
o   Dynamic selections active
    If this switch is set, the dynamic selections of the logical
    database are active at the start of the report.
Note that the following combinations are possible for the last two
    options mentioned:
Dyn.Sel. as dialog box/Dyn.Sel. active: inactive/inactive
    Dyn.Sel. as dialog box/Dyn.Sel. active: inactive/active
    Dyn.Sel. as dialog box/Dyn.Sel. active: active/inactive
Activities
1. Choose Edit -> New entries.
2. Enter an abbreviation and a long text for the report category.
    The customer name range for report categories is 0-9.
3. Select the For the PNPCE logical database checkbox, if you want to
    create a report category for a program or for queries of the PNPCE
    logical database.
4. In the General Data screen area, choose the desired options.
    If you want to use selection IDs, you must have first created and
    grouped selection Ids. The IMG path to do this is given in the
    parameter description section.
5. In the Data selection period/person selection period or Selection
    period screen area, choose the desired options.
6. In the Selection view screen area, choose the desired options.
7. In the CE selection fields screen area, choose the desired (only
    possible for report categories of the LDB PNPCE).
8. Save your entries.
9. Choose the subactivity Permitted selection criteria.
10. Choose Edit -> New entries.
11. In the Select option field, use the input help to select each field
    that should be available on the selection screen.
12. Select the checkbox in the 1.page column, if you want this selection
    field to be available directly when you call the selection screen.
Further notes
13. If you want to copy entries, you still have to enter the selection
    parameters again in the subsequent screen.
o   If you create the report category '000000000', a selection screen is
    generated according to report category '00000000'for all reports for
    which a report category has not explicitly been assigned.
Assign Report Categories
In this step, you assign a report category to your reports.
Example
You have created your own report, for example ZPCTEST1, and would like
    it to have the selection screen that corresponds to that of the
    evaluation report for Payroll, which is assigned to report category
    '__M00001'.
    Assign report category '__M00001' to the report.
Requirements
You must have defined the Report Categories.
Standard settings
SAP Standard Reports:
In the standard system, reports are assigned a report category. If you
    want to override these assignments, perform the activities described
    here. If you want to assign report categories to standard reports using
    SE38, this represents a modification.
Customer-Specific Reports:
For reports you have developed yourself, you can either assign report
    categories by performing the activities described here or directly in SE38.
Recommendation
Only assign a report category if you have created your own reports or if
the selection screens in the standard system do not meet your
requirements.
Activities
1. Choose Edit -> New entries.
2. Perform the required assignment using the Program name and Report
   category fields.
3. Save your entries.
reward if helpful
regards,
madhumitha

Facing Problem while Debugging a custom report using LDB

Hi Gurus,
I have requirement to modify a custom report program related to FI. This program used Logical database ZDF ( Copied original DDF) for data fetching.
when i am trying to see the data in debugging mode, its not allowing to check in start-of-selection event. only in the initialization & end-of-selection i could able to debug.
when i put breakpoint in initialization, it is allowing to see the flow till a Get Event occurs in the code, once a Get event occur the debugger is coming out and displaying the report.
If anybody faced this kind of problem when debugging a report using LDB, please share how you resolved it. If there are any other ways to debug a program of this kind please help me.
Thanks,
Nanda

Hi Amith,
I checked that way also, i put break point in database program of the copied LDB, but its not allowing to check the flow in that program also.
Please suggest any other ways.
Thanks,
Nanda

Steps for Creating Report using LDB

hellow sirs
can u please tell Step by Step method for creating Reports using LDB method...
if possible with screen Shots..
thanking You
Rahul

Hi,
Please refer the code below:
Use the PNP LDB for this program,
*: Report: ZP_POSTCODE                                                :
*: Date : 2004                                                       :
*: Description: Displays report of employees by postcode area,         :
*:              includes current travelling allowances (i.e. parking   :
*:              permit or transport card etc..)                        :
*: Use:         Help encourage the use of car sharing and public       :
*:              transport where appropriate.                           :
REPORT zp_postcode.
type-pools: slis.                                      "ALV Declarations
NODES: pernr.
INFOTYPES: 0000, 0001, 0002, 0006, 0008, 0014, 0105, 0121.
SELECTION-SCREEN BEGIN OF BLOCK pcode WITH FRAME TITLE text-s01.
SELECT-OPTIONS: so_pcode FOR p0006-pstlz.
SELECTION-SCREEN END OF BLOCK pcode.
TYPES: BEGIN OF t_output,
pernr       TYPE p0001-pernr,   "personnel name
anredtxt    TYPE t522t-atext,   "title (based on p0002-anred)
fname       TYPE p0002-vorna,   "first name
lname       TYPE p0002-nachn,   "last name
orgtx       TYPE t527x-orgtx,   "dept
fte         TYPE p0008-bsgrd,   "fte
parking(20) TYPE c,
payslip     TYPE t526-sachn,        "payslip address
telno       TYPE p0105-usrid_long, "tel number(p0105-usrty = 0020)
email       TYPE p0105-usrid_long, "email (p0105-usrty = MAIL)
postcode    type p0006-pstlz,
END OF t_output.
DATA: it_output TYPE STANDARD TABLE OF t_output INITIAL SIZE 0,
      wa_output TYPE t_output.
*ALV data declarations
data: fieldcatalog   type slis_t_fieldcat_alv with header line,
      gd_tab_group   type slis_t_sp_group_alv,
      gd_layout      type slis_layout_alv,
      gd_repid       like sy-repid,
      gt_events      type slis_t_event,
      gd_prntparams type slis_print_alv,
      gd_count(6)    type n,
      gd_outtext(70) type c,
      gd_lines       type i.
*START-OF-SELECTION.
START-OF-SELECTION.
clear: gd_count.
GET pernr.
* Infotype 0121 is used to store multiple contracts for personnel.
* Field p0121-hpern contains the personnel number for the main contract.
PROVIDE * from p0121 between pn-begda and pn-endda.
*   Check if main contract
    if p0121-pernr ne p0121-hpern.
      reject.
    endif.
ENDPROVIDE.
add 1 to gd_count.
concatenate 'Processing personnel data'(m10) gd_count into gd_outtext
            separated by ' '.
* Display indicator for employee count
perform progress_indicator using gd_outtext.
* Retrieve datd from infotypes
rp_provide_from_last p0000 space pn-begda pn-endda.
rp_provide_from_last p0001 space pn-begda pn-endda.
rp_provide_from_last p0002 space pn-begda pn-endda.
rp_provide_from_last p0006 space pn-begda pn-endda.
rp_provide_from_last p0008 space pn-begda pn-endda.
rp_provide_from_last p0014 space pn-begda pn-endda.
* Check post code
CHECK p0006-pstlz IN so_pcode. "cp
* Post code
wa_output-postcode = p0006-pstlz.
* Personnel number
wa_output-pernr = pernr-pernr.
* Personnel title
SELECT SINGLE atext
    FROM t522t
    INTO wa_output-anredtxt
   WHERE sprsl EQ sy-langu AND
         anred EQ p0002-anred.
* First name
wa_output-fname = p0002-vorna.
* Last name
wa_output-lname = p0002-nachn.
* Organizational Unit text (dept)
SELECT SINGLE orgtx
    FROM t527x
    INTO wa_output-orgtx
   WHERE sprsl EQ sy-langu AND
         orgeh EQ p0001-orgeh AND
         endda GE sy-datum.
* FTE
wa_output-fte = p0008-bsgrd.
* Parking / travel deducted?
CASE p0014-lgart.
    WHEN '7180' OR '7181' OR '7182'.
      wa_output-parking = text-002.
    WHEN '7183'.
      wa_output-parking = text-001.
    WHEN '7171' OR '7172' or '7173' or '7174' or
         '7175' or '7176' or '7177' or '7178'.
      wa_output-parking = text-003.
ENDCASE.
* Payslip Address
SELECT SINGLE sachn
    FROM t526
    INTO wa_output-payslip
   WHERE werks EQ p0001-werks AND
         sachx EQ p0001-sacha.
PROVIDE * from p0105 between pn-begda and pn-endda.
*   Telephone numbers
    if p0105-usrty = '0020'.
       wa_output-telno = p0105-usrid_long.
    endif.
*   Email address
    if p0105-usrty = 'MAIL'.
       wa_output-email = p0105-usrid_long.
    endif.
ENDPROVIDE.
append wa_output to it_output.
clear: wa_output.
*END-OF-SELECTION.
END-OF-SELECTION.
describe table it_output lines gd_lines.
if gd_lines gt 0.
perform build_fieldcatalog.
perform build_layout.
perform display_alv_report.
else.
message i003(zp) with 'No records found'.
endif.
*&      Form PROGRESS_INDICATOR
*       Displays progress indicator on SAP screen
form progress_indicator using p_text.
call function 'SAPGUI_PROGRESS_INDICATOR'
      exporting
*         PERCENTAGE = 0
           text       = p_text.
endform.                    " PROGRESS_INDICATOR
*&      Form BUILD_FIELDCATALOG
*       Build Fieldcatalog for ALV Report
form build_fieldcatalog.
fieldcatalog-fieldname   = 'PERNR'.
fieldcatalog-seltext_m   = 'Personnel No.'.
fieldcatalog-col_pos     = 0.
fieldcatalog-outputlen   = 10.
* fieldcatalog-emphasize   = 'X'.
* fieldcatalog-key         = 'X'.
* fieldcatalog-do_sum      = 'X'.
* fieldcatalog-no_zero     = 'X'.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'ANREDTXT'.
fieldcatalog-seltext_m   = 'Title'.
fieldcatalog-col_pos     = 1.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'FNAME'.
fieldcatalog-seltext_m   = 'First Name'.
fieldcatalog-col_pos     = 2.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'LNAME'.
fieldcatalog-seltext_m   = 'Last Name'.
fieldcatalog-col_pos     = 3.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'ORGTX'.
fieldcatalog-seltext_m   = 'Department'.
fieldcatalog-col_pos     = 4.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'FTE'.
fieldcatalog-seltext_m   = 'FTE'.
fieldcatalog-col_pos     = 5.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'PARKING'.
fieldcatalog-seltext_m   = 'Parking/Metrocard'.
fieldcatalog-col_pos     = 6.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'PAYSLIP'.
fieldcatalog-seltext_m   = 'Payslip Add.'.
fieldcatalog-col_pos     = 7.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'TELNO'.
fieldcatalog-seltext_m   = 'Telephone'.
fieldcatalog-col_pos     = 8.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'EMAIL'.
fieldcatalog-seltext_m   = 'E-mail'.
fieldcatalog-col_pos     = 9.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname   = 'POSTCODE'.
fieldcatalog-seltext_m   = 'Post code'.
fieldcatalog-col_pos     = 10.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
endform.                    " BUILD_FIELDCATALOG
*&      Form BUILD_LAYOUT
*       Build layout for ALV grid report
form build_layout.
gd_layout-no_input          = 'X'.
gd_layout-colwidth_optimize = 'X'.
gd_layout-totals_text       = 'Totals'(201).
gd_layout-zebra             = 'X'.
endform.                    " BUILD_LAYOUT
*&      Form DISPLAY_ALV_REPORT
*       Display report using ALV grid
form display_alv_report.
gd_repid = sy-repid.
call function 'REUSE_ALV_GRID_DISPLAY'
       exporting
            i_callback_program      = gd_repid
            is_layout               = gd_layout
            it_fieldcat             = fieldcatalog[]
            i_save                  = 'X'
       tables
            t_outtab                = it_output
       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_ALV_REPORT

Need to display the BW documents as a column in the Bex report

Hi,
I know, from Bex you can Goto "Goto -> Documents" or "Goto -> Documents for navigation status" context menu to display documents.
But I was wondering, is there a way to display the documents as a column in the report, instead of going through the menu?
Thanks a bunch.

Sonali,
the very purpose of it being a document is that it can have any data that might be required to identify the value like an image etc... this would be the reason why you cannot display the document directly on the page..
Options are :
1. When loading the data - have a routine that looks into the document and populates the text attribute of the IOBJ
2. Use a virtual characteristic to pick up the value of the characteristic and fetch the document content ( Not sure if this can be done )
3. If you are using Web reporting - use the table interface to fetch the value of the document and put it into the cell.
Arun
Assign points if it helps..

Can We Display a Tabular Format in the Decision Report?

Hello,
One of my current OPA integrations is replacing an Excel-based application that calculates entity values across rows and columns. In the OPA version, the rows are separated into screens, and the columns - the results - are displayed in a decision report that shows a single value per line, and is not vertically aligned. This makes the results much more difficult to view "at a glance" compared to the legacy solution. I'm wondering if there's any way to incorporate tabular formatting (mainly vertical alignment) within the decision report - does anyone know?
Thanks!
- Patrick

With version 10.3 and the BI publisher integration you can design virtually any format for the decisions you wish. When using BI publisher, a completely customized decision report is quite easy. See the OPM help topic "BI Publisher code for Oracle Policy Modeling" and/or the example that ships with 10.3 for more info. If using the web service to make determinations, you could also post process the XML for the decision report (i.e. using XSLT or code) to produce a table in XML or HTML. Customizing the "default" decision report into a tabular view would probably prove more difficult than the other options.

Problem with dynamic columns in the BEx report

Hi Gurus,
I am tryging to build some planning application using BI-IP and input ready queries.
I'm facing issues with making the columns in the query 'dynamic'. The example is given below: -
Lets say there are states and cities for which we have to plan sales volumes. Depending on the value I choose for 'State' it should create as many columns for 'Cities' as per the hierarchy of the cities.
Lets say if I choose Maharashtra then the report shud look like :-
State-> Maharashtra
Rows               Column1                      Column2                      Column3
GL Account      Mumbai/0quantity        Pune/0quantity            Aurangabad/ 0quantity
1000000            1000                               1500                              1200
State--> Karnatka
Rows                 Column1                  Column2
GL account        Bangalore                 Mangalore
1000000
Any idea how this can be achieved?
Best Regards,
SSC

Hi friend,
See the link below it is having the solution of hiding the columns in smart forms
Hide table columns in smart form?
Create a table to display your values with 12 col and hide the columns based on the idea provided in the link above.
I think this will solve your issue if you still have queries please revert back to me i will help you.
Thanks,
Sri Hari

Display an extra column in the standrad report using LDB

Similar Messages

Maybe you are looking for