Time_dependence switch in infoset...

Hi all!!
In some of the sap query reports we use information about previous employer of the employee (infotype 0023). All records from this infotype are usually in the past. My idea was, that report would display all records of this infotype for a person irerespective of the selected dates.
For example what i want to achieve is: when i choose data fore 'today' report gives me the current org assignment and in the same row one of the previous employer, next row would have the same org assign. and next prev. empl. ect..
in the infoset i wrote:
*$HR$ [P0023]
*$HR$ TIME_DEPENDENCE = 'INDEPENDENT'
Then generated infoset, regenerated the query.
But nothing has changed, if i select today the report does not display records of 0023 from the past..
May be i misunderstood the purpose of time_dependence switch?
Help..

Hi Praveen,
Are you mentioning about the infoset temporal joins, if yes refer to this link,
http://help.sap.com/saphelp_nw04s/helpdata/en/11/723c3b35703079e10000000a114084/frameset.htm
cheers
Sunil

Similar Messages

What is an Infoset

Hi all
Can any body explain me what an infoset mean, why do we use it and how do we create it, and finally if we are asked to add an table to the existing infoset how do we do that and is there any code to be written in that. and anything more on infosets that will help me to work on them
thanks in advance !

hi
HR InfoSets for InfoSet Query
To access data stored in the system, InfoSet Query uses an InfoSet. It provides you with a view of data in specific parts of HR that is structured by infotype. On the initial InfoSet Query screen, the InfoSet is displayed with its field groups as an overview tree. This overview tree enables you to choose selection fields and output fields.
The InfoSets used in InfoSet Query are created and managed in SAP Query. When you create an InfoSet, you select a logical database on which the InfoSet is based, and determine which infotypes are included in the InfoSet. They are displayed in the InfoSet as field groups. After you have selected the infotypes, you can determine which fields are included in the field groups for each infotype.
In the standard system, all infotype-specific fields of the selected infotypes are included in the InfoSet. You are advised to check the selection of fields carefully, and adapt the selection to your reporting concept. Appropriately adjusted InfoSets are user-friendly, which makes working with InfoSet Query much simpler.
The InfoSet determines the objects that you can select with InfoSet Query. The following scenarios are possible:
The InfoSet is based on logical database PNP
InfoSets based on this logical database enable you to use InfoSet Query to select employees. You can use data from Personnel Administration and Time Management and payroll infotypes as selection criteria. From a technical perspective, this means you can use fields from infotypes 0000 to 0999 and 2000 to 2999 and payroll infotypes as selection criteria. For example, you can use the InfoSet to run a report that determines which employees have a particular place of residence.
Furthermore, you can create InfoSets on the basis of this logical database that enable you to report on the infotypes of related objects using InfoSet Query. For example, you can select persons who participated in a particular business event, and output the qualifications of the persons selected. To do this, you must select infotypes from Personnel Planning as well as infotypes from Personnel Administration when you create the InfoSet.
The InfoSet is based on logical database PAP
InfoSets based on this database enable you to use InfoSet Query to select applicants. You can use data from Recruitment as selection criteria and for output. From a technical perspective, this means you can use fields from specific Personnel Administration infotypes (such as 0001 and 0002) and fields from infotypes 4000 to 4999 as selection and output fields.
The InfoSet is based on logical database PCH
Provided that object selection is switched on, InfoSets based on this database enable you to use InfoSet Query to select objects of one object type, such as business events, qualifications, and positions. You can use all of the fields of infotypes allowed for the object in question, and all of the object types and their allowed infotypes that can be related with the selected object type, as selection criteria and for output.
When you create an InfoSet, you determine the object type that you can select using an InfoSet. The generated InfoSet can only be used to select this particular object type. If you want to create reports for business events, qualifications, or positions, for example, you must create three separate InfoSets. This means the reports can only be executed separately.
If you do not select an object type when you create the InfoSet, you can only use the InfoSet for InfoSet Query if object selection has been switched off.
See also:
InfoSets in the HR Application
and verify the following link
http://www.sap-img.com/human/how-to-create-infoset-query.htm
hope it will helps you
regards
sreelatha gullapalli

Education Infotype

Just for verification...the BEGDA and ENDDA for IT 0022, Education infotype, should be the dates the employee attended high school, college, etc.
Correct?

Hello,
This error occurs often with IT0022 and is due to the fact that IT0022 data cannot be retrieve if there is no valid IT0000 record
There are several solutions to your problem:
1) You could use function EDIT->SETTINGS and delete the checkbox for 'Use selection conditions' on tabstrip OUTPUT. The consequence is, that the specified select-options are used only to calculate the hitlist of persons. When the output is started, ALL data is presented for these selected persons (and not only those data, that fulfills the select-options).
2) You could use the field PERNR from infotype 0022 as the select-option instead of infotype 0000.
3) You could use switch TIME_DEPENDENCE within the infoset to specify,that data records of infotype 0022 should be printed regardless of their validity.
SAP would I recommend to use solution 3). have a look at the pdf-attachment of note 305118. It describes the technique of defining switches within an infoset. The result is, that when processing the split logic for calculating validity intervals and processing records according their compliance with the calcutated splits, infotype 0022 is treated independent from its validity dates. So the fact, that an infotype 0022 record is valid BEFORE infotype 0001-records is ignored.
Hope this help Sarah

Using ldb PCH in HR

hi ,
can somebody give me sample code for using PCH logical database. and the events used in it

In Human Resources (HR), the following logical databases can be used as a data source for HR InfoSets:
PNP (PNPCE)
PAP
PCH
By selecting a logical database, you determine the HR data that can be reported on using an InfoSet.
PCH
This logical database generally enables you to report on all HR infotypes. However, you are advised not to use this logical database unless you want to report on Personnel Planning data.
The InfoSet is based on logical database PCH
Provided that object selection is switched on, InfoSets based on this database enable you to use InfoSet Query to select objects of one object type, such as business events, qualifications, and positions. You can use all of the fields of infotypes allowed for the object in question, and all of the object types and their allowed infotypes that can be related with the selected object type, as selection criteria and for output.
When you create an InfoSet, you determine the object type that you can select using an InfoSet. The generated InfoSet can only be used to select this particular object type. If you want to create reports for business events, qualifications, or positions, for example, you must create three separate InfoSets. This means the reports can only be executed separately.
If you do not select an object type when you create the InfoSet, you can only use the InfoSet for InfoSet Query if object selection has been switched off.
Kanagaraja L

HR Infosets - switch object selection question?

Dear All,
I encounter this issue. I create a HR Infosets using logical database PNPCE. As the requirement of our HR Dept, so we need to add more extras fields (by code).
The problem when we switch on/off object selection (from menu):
- When the object selection is off: all the extras fields I add are available.
- When the object selection is on: all of them are not available.
This is my idea. All the field of infosets will be display when the object selection is on depend on SAP internal field, and the extra field we add by code will not be displayed.
But it's my opinion. So please help me with this issue.
Thanks in advanced.
Thien.
Edited by: Pham Thien on Nov 18, 2008 3:12 AM

Hi,
We can hide those options by implementing the Layoutsets. If you need to hide those options for standard admin user itself, then you need to change the standard Layoutsets, which is not recommended. These options are defined in the "Command Group" of the Layoutsets.
You can Navigate to Layoutsets thru below path.
Sys Admin -> System Configuration -> Knowledge Management ->Content Management -> User Interface -> Settings -> Layoutset
Tweaking over the Layoutset Command group properties will hide the options which you mentioned.
Thanks,
Mahendran B.

FULL OUTER JOIN In InfoSet

Hi, all
Is it possible to make FULL OUTER JOIN in BI InfoSet?
If no, another question - is it possible to switch base InfoProvider? I have an InfoSet with InfoCube1 and DSO1 which I can outer join. I want to outer join InfoCube1 , not DSO1 that's why I need to switch them in the InfoSet.

Hi,
In BI 7.0 Infoset has given chance to include an Info cube also,maximum you can include 2 info Cubes only in a infoset.
check the below link which helps you in understanding of the join conditions so that you can apply to your scenario.
http://help.sap.com/saphelp_nw2004s/helpdata/en/f1/713c3b35703079e10000000a114084/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/67/7e4b3eaf72561ee10000000a114084/content.htm
Regards,
Praveena.

What is Infoset and How to create

HI Experts
Can any one please explain me what is the purpose of INFOSET in BW
and how to create a info Set between A Info Object and Cube
Thanks

Dear bw user,
Check the below link
http://help.sap.com/saphelp_nw04s/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
Purpose is,
1.To join required data from basic InfoProviders
2.This allows building a relational BI data model with unified views for reporting (seeveral InfoProviders,but only one view). Therefore, we recommend keeping data in smaller, basic InfoProviders that can be flexibly joined for reporting purposes.
3. To allow BEx Reporting on a DataStore object without turning the BEx Reporting indicator on
4. To evaluate time dependencies (for example, join time dependent master data InfoObjects)
5. To be able to create self joins and left outer joins
Creatind in simple steps
Infoset is a Virtual Infoprovider.
Click on InfoProvider under modeling in RSA1 > Select InfoArea > right click Create Infoset > give name and description.
Select the ODS / Master Data Object or more than one ODS and maintain the link.
Infoset works on Join operation.
you can include Infocube if it is BI 7.
chk this link...
http://help.sap.com/saphelp_nw70/helpdata/en/a3/96663bd194a978e10000000a11402f/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2f5aa43f-0c01-0010-a990-9641d3d4eef7
Aslo see this link contents
Creating InfoSets
Prerequisites
Make sure that the objects for which you want to define the InfoSet are active. Create any required InfoObjects that do not
exist already and activate them.
Instead of creating a new InfoSet, you can transfer one of the InfoSets that are delivered with SAP Business Content.
Procedure
1. You are in the InfoProvider tree of the Modeling function area in the Administrator Workbench.
Choose the Create InfoSet function from the context menu (right mouse-click) of the InfoArea in which you want to create an
InfoSet. You get to the Create InfoSet dialog box.
2. Type in the following information for your new InfoSet:
¡ technical name
¡ long description
¡ short description
3. In the Start with InfoProvider section, you determine which InfoProvider you want to use to start defining the InfoSet.
¡ Select one of the object types that the system offers you:
ODS Object
InfoObject
Choose an object.
If you want to choose an InfoObject, it must be a characteristic with master data. The system provides you with the
corresponding input help.
4. Choose Continue. You get to the Change InfoSet screen. For more information on editing InfoSets see Editing InfoSets.
When you create an InfoSet, the system generates a corresponding entry for this InfoSet in the subtree of the InfoArea. The
following functions are available from the context menu (right mouse-click) of this entry:
Change
Delete
Object overview
Editing InfoSets
Prerequisites
Before you can get to the screen where you edit InfoSets, the following prerequisites have to be met:
You have created a new InfoSet.
You have selected the Change function from the context menu of an InfoSet entry in the InfoProvider tree of the Modeling
function area in the Administrator Workbench.
You have called the InfoSet Builder transaction, and selected the Change function. You can find additional information
under Additional Functions in the InfoSet Builder .
Procedure
1. You are in the Change InfoSet screen.
Choose a layout for the InfoProvider tree:
InfoArea
InfoProviders Used
All ODS Objects
All InfoObjects
For more information on the screen layout, particularly the layout of the InfoProvider tree, see Screen Layout: Changing
InfoSets.
2. Use the function Where-Used List via AWB to determine which BW objects use the InfoSet that you have selected. You get to
the Administrator Workbench: Where-Used List screen. You are able to work out what would happen in the system if you made
changes to the InfoSet. This helps you to decide whether or not it is sensible to make these changes at this particular point
in time.
3. You define the InfoSet by inserting one or more InfoProviders into the join.
There are several ways of inserting an InfoProvider into the join control:
¡ From the InfoProvider tree:
§ In the InfoProvider tree, double-click on the entry that corresponds to the InfoProvider that you want to add to the join
control.
§ Use the drag-and-drop function to move the InfoProvider into position.
¡ Choose the Add InfoProvider function, to add a particular ODS object or a particular InfoObject independently of the
current layout of the InfoProvider tree. You get to the dialog box of the same name. Enter the data that the system asks you
for.
If you know the technical name of the InfoProvider that you want to add, this method is quicker than switching the layout of
the InfoProvider tree.
When this function is complete, the InfoProvider that you selected is displayed in the join control. For more information on
the structure of the join control, see Join Control.
4. Define the join conditions. For more information see Defining Join Conditions.
5. You can get general information such as object version, date created and date changed via Goto ® Global Settings. You can
also set the indicator Most recent Reporting for InfoObjects from here. You can find additional information under Most recent
Reporting for InfoObjects.
6. Via the button Documents, which appears on the pushbutton bar, you can access document editing for this InfoSet.
7. You can use Check to check the correctness of the InfoSet definition. The log display is shown in the screen area under
the join control.
8. Save the InfoSet. The log display is shown in the screen area under the join control.
9. Activate the InfoSet. After activation, the system executes the checks. The result of the activation is displayed in the
log in the screen area under the join control.
Additional Functions in the InfoSet Builder
You can also use transaction RSISET to call up the InfoSet Builder when you want to edit an InfoSet. Select the InfoSet that
you want to edit. Value help is available for this. Additional functions are also available to help you edit and manage your
InfoSet.
Compare
You use this function from the main menu to check if the InfoProviders used in the InfoSet have been changed and the InfoSet
needs to be adjusted as a result. For more information, see Matching InfoSets.
Jump to object maintenance
You use the InfoObjects and ODS Objects functions to jump to the maintenance screen for the InfoProviders included in the
InfoSet definition.
Info functions
There are various info functions on the status of the InfoSets:
The Object Catalog Entry
The log display for the save, activate, and delete runs of the InfoSet.
Display in tree
You use this function to display in a tree structure all the properties of the A version (active) of the selected InfoSet.
Header data
InfoProvider and its fields
On condition
Wherecondition
The display is empty, if no active version is available.
Version comparison
You use this function to compare the following InfoSet versions:
The active (A version) and modified (M version) versions of an InfoSet
The active (A version) and content (D version) versions of an InfoSet
The modified (M version) and content (D version) versions of an InfoSet
The Display InfoSet screen appears. Depending on which option you choose, the system displays either all of the differences
between the two versions of the selected InfoSet or all of the properties of both versions in a tree structure.
Transport connection using AWB
You use this function to transport an InfoSet into another system.
The Administrator Workbench: Transport Connection screen appears.
The system has already collected all the BW objects that are needed to guarantee the consistency of the target system.
InfoSet data display
You use this function to access the data target browser. If you have already loaded data into the InfoProviders included in
the InfoSet, you can display this data.
Delete
You use this function to delete an existing InfoSet.
Copy
You use this function to copy an existing InfoSet and, if necessary, edit it further.
Show/hide technical names
You can use this function to show alias names for fields. These alias names are necessary in InfoSets, for example to be able
to map self joins. Field alias names start with F, followed by a five-digit number.
Defining Join Conditions
Use
A join condition determines the combination of records from the individual objects that are included in the resulting set.
Before an InfoSet can be activated, the join conditions have to be defined in such a way (as equal join condition) that all
the available objects are connected to one another either directly or indirectly.
Usually, however, only rows containing a common InfoObject or rows containing InfoObjects that share the same basic
characteristic are connected to one another.
Connect tables T1 and T2 using a join and set as a join condition that the F1 field from T1 must have the same value as F2
from T2. For a record from table T1, the system determines all records from T2 for which F2(T2) = F1(T1) is true. In
principle, as many records from T2 can be found as required. If one or more records are found, the corresponding number of
records is included in the result set, whereby the fields from T1 contain the values from the record from T1 under
consideration, and the fields from T2 contain the values of the records found from T2.
Procedure
There are various ways of defining join conditions:
Using a mouse-click
Position the cursor over a row in an InfoObject. Press the left mouse-button and, keeping the left mouse-button pressed down,
trace a line between this row and a row in another object. Providing that the join condition between the two rows that you
have indicated is a valid join condition, the system confirms the join condition by displaying a connecting line between the
two rows.
Using the Link Maintenance pushbutton
You get to the Link Maintenance dialog box.
In a tree structure on the left-hand side of the screen, all of the InfoProviders that are already included in the join are
displayed along with their fields or attributes. If you double-click on one of these fields or attributes, the system
displays on the right-hand side of the screen all of the fields or attributes with which you are able to create a join
condition.
In the Selection column, set one or more of the indicators for the fields or attributes for which you want to create a join
condition. The system generates valid join conditions between the fields or attributes that you specify.
You use the Delete Links pushbutton to undo all of the join conditions.
You use the All Characteristics or the Basic Characteristics Only pushbutton to choose between the corresponding display
variants.
We recommend that you use the Basic Characteristics Only option. The All Characteristics setting displays all of the
technical options involved in a join. If you are not able to find a join condition on the basic characteristic level, then
the All Characteristics setting is useful, but this is an exceptional case.
When you have finished making your settings, click on the Continue icon.
We recommend this method, because the system searches for all the possible join conditions for any field or attribute that
the user specifies, ensuring that the join conditions are defined without errors.
Using the Context Menu Left Outer Join Inner Join
Usually inner-join operators connect all the objects in a join to one another. You can also connect each object with any of
the many other objects by using a left outer join operator.
You can find additional information about usage and special features under Left Outer Join.
If you want to use a left-outer join operator to connect an object, select the object and choose the corresponding function
from the context menu.
The system displays all of the valid join conditions that originate from this object. The connecting lines that represent
these join conditions are labeled as Left Outer Join . InfoProviders, on which a left outer join condition is affixed, are
differentiated by color from the InfoProviders that are connected using an inner join operator.
If you used a left outer join operator to connect two objects, you have to make sure that all on conditions are linked except
for these two objects with the formulation of join conditions.
Note that you cannot add an object, which you have already connected by using the left outer join operator, to another
object.
If you want to use an inner-join operator instead of the left-outer join operator, select the object that you want to
connect, and choose the Inner Join option from the context menu. Again the system displays all the valid join conditions that
originate from this object, and labels the connecting lines accordingly.
Result
Once the join conditions have been defined in such a way as to connect all the available objects to one another, either
directly or indirectly, the InfoSet is ready to be activated.
You click on the Check pushbutton in the pushbutton toolbar to find out if these preconditions for the activation have been
met.
For objects that are joined by a left-outer join operator, there is one extra condition that has to be met, namely that all
the other objects have to be connected to one another either directly or indirectly.
http://help.sap.com/saphelp_erp2004/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/a3/96663bd194a978e10000000a11402f/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2f5aa43f-0c01-0010-a990-9641d3d4eef7
Hope itr helps
Regards
Bala
Also

How to improve query performance using infoset

I create one infoset that including 4 char.and 3 DSO which all are time-dependent.When query run, system show very poor perfomance, sometimes no data show in BEX anayzer. In this case I have to close BEX analyzer at first and then open it again, after that it show real results. It seems very strange. Does anybody has experience on infoset performance improvement. pls info, thanks!

Hi
As info set itself doesn't have any data so it improves Performance
also go through the below tips.
Find the query Run-time
where to find the query Run-time ?
557870 'FAQ BW Query Performance'
130696 - Performance trace in BW
This info may be helpful.
General tips
Using aggregates and compression.
Using less and complex cell definitions if possible.
1. Avoid using too many nav. attr
2. Avoid RKF and CKF
3. Many chars in row.
By using T-codes ST03 or ST03N
Go to transaction ST03 > switch to expert mode > from left side menu > and there in system load history and distribution for a particular day > check query execution time.
Statistical Records Part 4: How to read ST03N datasets from DB in NW2004
How to read ST03N datasets from DB
Try table rsddstats to get the statistics
Using cache memory will decrease the loading time of the report.
Run reporting agent at night and sending results to email. This will ensure use of OLAP cache. So later report execution will retrieve the result faster from the OLAP cache.
Also try
1. Use different parameters in ST03 to see the two important parameters aggregation ratio and records transferred to F/E to DB selected.
2. Use the program SAP_INFOCUBE_DESIGNS (Performance of BW infocubes) to see the aggregation ratio for the cube. If the cube does not appear in the list of this report, try to run RSRV checks on the cube and aggregates.
Go to SE38 > Run the program SAP_INFOCUBE_DESIGNS
It will shown dimension Vs Fact tables Size in percent.If you mean speed of queries on a cube as performance metric of cube,measure query runtime.
3. To check the performance of the aggregates,see the columns valuation and usage in aggregates.
Open the Aggregates...and observe VALUATION and USAGE columns.
"---" sign is the valuation of the aggregate. You can say -3 is the valuation of the aggregate design and usage. ++ means that its compression is good and access is also more (in effect, performance is good). If you check its compression ratio, it must be good. -- means the compression ratio is not so good and access is also not so good (performance is not so good).The more is the positives...more is useful the aggregate and more it satisfies the number of queries. The greater the number of minus signs, the worse the evaluation of the aggregate. The larger the number of plus signs, the better the evaluation of the aggregate.
if "-----" then it means it just an overhead. Aggregate can potentially be deleted and "+++++" means Aggregate is potentially very useful.
In valuation column,if there are more positive sign it means that the aggregate performance is good and it is useful to have this aggregate.But if it has more negative sign it means we need not better use that aggregate.
In usage column,we will come to know how far the aggregate has been used in query.
Thus we can check the performance of the aggregate.
Refer.
http://help.sap.com/saphelp_nw70/helpdata/en/b8/23813b310c4a0ee10000000a114084/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/60/f0fb411e255f24e10000000a1550b0/frameset.htm
performance ISSUE related to AGGREGATE
Note 356732 - Performance Tuning for Queries with Aggregates
Note 166433 - Options for finding aggregates (find optimal aggregates for an InfoCube)
4. Run your query in RSRT and run the query in the debug mode. Select "Display Aggregates Found" and "Do not use cache" in the debug mode. This will tell you if it hit any aggregates while running. If it does not show any aggregates, you might want to redesign your aggregates for the query.
Also your query performance can depend upon criteria and since you have given selection only on one infoprovider...just check if you are selecting huge amount of data in the report
Check for the query read mode in RSRT.(whether its A,X or H)..advisable read mode is X.
5. In BI 7 statistics need to be activated for ST03 and BI admin cockpit to work.
By implementing BW Statistics Business Content - you need to install, feed data and through ready made reports which for analysis.
http://help.sap.com/saphelp_nw70/helpdata/en/26/4bc0417951d117e10000000a155106/frameset.htm
/people/vikash.agrawal/blog/2006/04/17/query-performance-150-is-aggregates-the-way-out-for-me
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1955ba90-0201-0010-d3aa-8b2a4ef6bbb2
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
http://help.sap.com/saphelp_nw04/helpdata/en/c1/0dbf65e04311d286d6006008b32e84/frameset.htm
You can go to T-Code DB20 which gives you all the performance related information like
Partitions
Databases
Schemas
Buffer Pools
Tablespaces etc
use tool RSDDK_CHECK_AGGREGATE in se38 to check for the corrupt aggregates
If aggregates contain incorrect data, you must regenerate them.
202469 - Using aggregate check tool
Note 646402 - Programs for checking aggregates (as of BW 3.0B SP15)
You can find out whether an aggregate is usefull or useless you can find out through a proccess of checking the tables RSDDSTATAGGRDEF*
Run the query in RSRT with statistics execute and come back you will get STATUID... copy this and check in the table...
This gives you exactly which infoobjects it's hitting, if any one of the object is missing it's useless aggregate.
6
Check SE11 > table RSDDAGGRDIR . You can find the last callup in the table.
Generate Report in RSRT
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cccad390-0201-0010-5093-fd9ec8157802
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4c0ab590-0201-0010-bd9a-8332d8b4f09c
Business Intelligence Journal Improving Query Performance in Data Warehouses
http://www.tdwi.org/Publications/BIJournal/display.aspx?ID=7891
Achieving BI Query Performance Building Business Intelligence
http://www.dmreview.com/issues/20051001/1038109-1.html
Assign points if useful
Cheers
SM

Information message in infoset query.

hi all,
i have added a field into the infoset query adn im using s_pho_48000513 . my probelm is when ever im opennig the query im getting information message as some selection fields are not available.does any have idea why im getting this message ..where i went wrong in ading the field to infoset.what check should i do.please suggest.and another thing when im doing switch off object selection from extras im not getting this information message but this field is comming in selection fields from infoset with default selected with enable mode and all other fields selected with disable mode.
any inputs is apreciated..
regards,
suha

Remove those fields/Infotypes from the infoset with the help of SQ02 from that infogroup
Thanks
Jaydeep jadhav

Additional field added in Infoset unable to use as a selectable field

I added 2 fields as additional fields to the Organizational Assignment infotype in a PNP Infoset that I created via SQ02. When I select the infoset to build a query via adhoc query the fields are listed in the Org Assignment infotype and available for output but are not available as a selection field. There is no check box under the Selection column, only a checkbox under the output column.
How do I make the added additional fields available as a section field as well as an output field.

Solution: in ad hoc query select Extras > Switch off object selection

What is "*$HR$ [*]" code in data section of INFOSET?

I saw "$HR$ []" code in data section of Infoset.
At Sap query, it changes the resulting abap code, and that's all I know.
How does this work?
Plz, give me some explanation.

There is infoset switch. Check IMG.

SQ01 - restriction on Infoset

Hello,
I have created an infoset via SQ02 that is joining 4 tables. (VBUK, LIKP, VBPA, ADRC).
I would like to add a restriction on a field (VBPA-PARVW = SH) so that all the values that come from this infoset are restricted to just those with the SH value on PARVW.
Is this possible? (and if possible without writing any ABAP code)
many thanks,
Allan

Allan,
The query selections are displayed in the top right-hand corner of InfoSet Query. The following displays are possible:
Editable ALV Grid Control (set by default at the start of InfoSet Query)
Selection screen (can be used as an alternative)
You can switch between the two display options by choosing Extras -> Standard Selection Screen or Extras
-> Selection Control On.
If you use the ALV grid to display the selections and choose a selection field, a new line appears in the selection field list. The selection field list contains six columns where we can input the field name, option and the value. Under "Value", you can set default values.
Thanks,
Lalitha.

SQ02 Infoset - security hole

Hi,
I have heard, that SQ02 (creating Infosets) has several security holes (regarding authority). Does anybody know about it and could specify these holes?
Thanks
Markus

Hi
Steps on how to proceed to create a Query:
ADHOC QUERY
A query can be created to extract information from master records i.e Infotypes. For example, by creating a query , the data relating to an employee contained in various Infotypes can be extracted.
Proceedure :
Decide on the various Infotypes we want to make the query. Decide on the area where we want to query i.e Global area or Standard area. Standard area is client specific and globel area will include all clients.
Menu : HR PM Admn - Information System - Adhoc Query
Select area standard and select the user group already created
Creation of new query :
TC SQ03 - Select Environment Select Standard Area - Enter -- If new user group is to be created, enter name of the user group, click on create and enter necessary information and exit after saving
TC SQ02 - Enter name of the Infoset Create enter name of Infoset - Data source -- > Table join by basis table give name of table e.g pa0000 - Enter - Click on insert table if we want to include more tables give name of table one by one and after finishing, place cursor on the joining lines and right click to delete unwanted relationships - check - and go back - field groups - include all table fields - click on generate button   - go out
TC SQ03 - Select user group -   eg. Payroll
Infoset - Enter name of newly created Infoset
Assign users and Infosets - Assign infosets - put tick on payroll - save and go back
TC PAAH - Expand the nodes and put tick on relevant fields depending upon necessity
Save the query by giving the same name as infoset for easyness..
Use
The InfoSet Query is designed for reporting on data stored in flat tables. It is particularly useful for reporting on joins for master data and joins for ODS objects.
Prerequisites
You must take the following steps before you can create Infoset queries:
·        Set up Roles for the InfoSet Query
·        Process Classic InfoSets and Assign Roles
Procedure
Define the InfoSet Query
       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 the InfoSet Query entry 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 Administrator 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.
InfoSet Query on the Web
It is possible to publish each InfoSet Query on the Web. There are the following display options:
·        MiniALV for creating MiniApps in the SAP Workplace
·        MidiALV without selection options
·        MidiALV with selection options
Both the MiniALV and the MidiALV allow you to switch between various selection/layout variants. The publishing screen for the data is adjusted individually using URL parameters.
The following prerequisites are necessary for security reasons:
Releasing the query for the Web
Specifying an authorization group for the corresponding Classic InfoSet
Call up transaction RSQ02 InfoSet: Entry, and choose Go to ® Additional Functions ® Web Administration of Queries. Make the corresponding entries.
Reward all helpfull answers
Regards
Pavan

Precautions for switch on Nav. Attr in DSO

Hi experts,
I don't know what are the detail steps if I have a requirement like below:
User wants to see the information of Char. e.g. CHARB. CHARB is a nav. attri of Material, Material now is in an DSO, but in the DSO CHARB is not switched on. So it means it must be switched on in the DSO first then change the query to meet the user's request. Now my question is that I am really consern about the data inside the DSO, could you please give me the step by step to finish this job e.g. how to make change in development box, what are the other objects need to be also transported into Q and how to protect data which is already inside the DSO ? Thanks in advance.

hi,
If you have some cubes or multiproviders or infoset using this DSO, they will get deactivated.
You need to actiavte all those objects and collect in a request and release it. You can check all the objects using this DSO by clicking where used list for this DSO.
Also, if you have any transformations from this DSO to any infoprovider, you need to activate and import into target system. You can collect all the transformations in one request and import it in Q system.
hope it helps,

How to join 4 DSOs in an InfoSet

Hi ALL,
I have a scenario in which I have 4 DSO's (e.g. D1 D2 D3 D4).
I need all the data from D1.
The field 0CS_ORDER is common to all the DSO's.
As per my understanding, there is only one Left Outer Join possible.
I tried by Keeping D1 on the left, D2 on right(Left Outer Join on D1).Then Inner joins as follows D2 with D3 and D3 with D4.
But when I check the data in InfoSet I do not get all the records in it for DSO D1.
So to get all the data from D1 in InfoSet and using inner joins for the other DSOs, how can I design the Infoset?
Thanks in Advance!!!
VIVEK

Dear Switch,
infoset is based on condion joint. To get the intersection of data, you have the options of inner joins.
in your requiremnt you wont all fiends with out condition.you go for multiprovider.
http://help.sap.com/saphelp_erp2004/helpdata/en/ed/084e3ce0f9fe3feyou ar10000000a114084/content.htm
you can link to all common char .
in bi7.0
http://help.sap.com/saphelp_nw04s/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/frameset.htm
in 3.5
http://help.sap.com/saphelp_nw04/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/frameset.htm
otherwise you can create the multiprovider.

Time_dependence switch in infoset...

Similar Messages

Maybe you are looking for