what are the step doing classical infoset

[Former Member]

what are the step doing classical infoset not infoset

[Former Member]

Hi,

A classic InfoSet provides a view of a dataset that you report on. You use the InfoSet query for this purpose. The classic InfoSet determines which tables, or fields within a table, an InfoSet query references.

Use

As of Release BW 2.0B, InfoSets are used in the Business Information Warehouse for InfoObjects (master data), DataStore objects, and joins for these objects. These InfoSets are not BI Repository objects but SAP Web Application Server objects. The InfoSet query can be used to carry out tabular (flat) reporting on these InfoSets.

As of Release BW 3.0, these InfoSets are called classic InfoSets.

Steps:

1. Call the Query Builder. There are various ways of doing this:

· To call the Query Builder from the corresponding role menu or from the BEx Browser, double-click on InfoSet Query in the menu that is created when you set up a role.

· Developers and testers of Classic InfoSets are able to call up the Query Builder directly from the Classic InfoSet overview in the Data Warehousing Workbench.

If several Classic InfoSets are assigned to a role, and one of them has been identified as a standard Classic InfoSet, this Classic InfoSet is used as a template when the query is called up. To change the template, choose Create New Query – Classic InfoSet Selection. Any of the Classic InfoSets that are assigned to the role can be the new template.

2. Define your query. The procedure is similar to the procedure for defining queries in the BEx Analyzer.

Transfer individual fields from the field groups you have selected in the Classic InfoSet into the preview. To do this, use the drag and drop function, or highlight the relevant fields in the field list.

Use either of these two methods to select any fields you want to use as filters. These fields are displayed in the Selections area of the screen (top right).

When you are preparing the query, only example data is displayed in the Preview. When you choose the Output or Refresh function, the actual results are displayed on the same screen.

3. Execute the query.

4. Choose from the following options:

Ad hoc reporting

You do not want to save the query for later. Save the Query Builder without saving.

Reusable queries

You want to save the query, because you want to work on it later, or use it as a template. Use either the Save or the Save as function to save the query.

In addition to the Classic InfoSets that you assigned to the role, you are also able to use the query as a template. It is not possible, however, to access the query from other roles.

After you save the query, a second dialog box appears, asking you if you want to save the query as a separate menu entry within the role. If you choose this option, you are able to start the query directly from the user menu or from the BEx Browser. It is also possible to use the Role Maintenance transaction (PFCG) to save this kind of role entry.

Choose Menu Refresh to display the query.

If you want to change or delete the saved query, use the Edit function from the context menu in the BEx Browser to call the maintenance tool for InfoSet Queries with this query as a template.

I hope this helps u,

regards anil

[Former Member]

hi,

select your ods-- context menuselect classic infosetit leads to screen-

there u write the technical name of infoset corresponding box---then select

create button in the upper right hand side--it will lead to infoset title and

data baseselect direct read of tables radio button go with tick(enter)--

it will lead to field group defaults-- select include all table fileds radio button-enter

it will take u to SQ02( change infoset screen)select save button--

select generate button(top left hand side)select back you can able to see

your classic infoset is get activated

if helpful provide points

regards

harikrishna.N

[Former Member]

Hi,

check this link

http://help.sap.com/saphelp_nw04s/helpdata/en/ad/2225391d4f000be10000000a114084/frameset.htm

Hope this helps,

K Janardhan Kumar