Object selection on Ad-Hoc Query

One of our users has created an infoset based on LDB PCE and selecting PA and PD objects. If this is ran through Ad-hoc query there is the option to restrict selections using "persons along the org structure" which gives the tree repreesentation that the user can then easily expand and click through.
If the user runs the infoset through SAP query this function does not seem to be available.
Can anyone advise if/how to enable this selectin of org structure positions through the tree structure in SAP query?
If not, does anyone know if there is a specific reason it's not possible?
Thanks
Phil

Martin,
In SAP HR we have 3 Logical Data Base which we can use to get the information output as report
1 . PNP/PNPCE - This database contains PA,TIME,and PAYROLL infotype & Tables (0000 - 0999 & 2000 - 2999)
2. PCH - this database contains PD infotype and tables (1000 for OM and 5000 for TEM)
3. PAP - This database contains recruitment infotype and tables (0001,0002, 4000 - 4999)
When we want to create a query we have to choose from one Logical database only ... if u want the output from different Logical database the it will be development program/report which is done by the Help of technical consulant (ABAP)
Hope this gives you the general information on ADHOC Query
In your question you trying to get output from PA and PD both has different database of each
so the output which you are expecting will not reflect
even if you create infoset .... the out put shows the values/information of the specified Logical database only rest of the fields will mark as blank in the report.
Conclution
if you want to create reports for Bussiness events, qualifications, Positions all are different objects so you need to create different infoset
Hope you get some idea
Thanks and Regards
Rajeshk

Similar Messages

Difference between sap query and sap ad hoc query

Hello Experts-
Is there any difference between sap query and sap ad hoc query. If yes, I will appreciate if you can provide some input.
Thanks,

Hi,
SAP Query
Purpose
The SAP Query application is used to create reports not already contained in the default. It has been designed for users with little or no knowledge of the SAP programming language ABAP.
SAP Query offers users a broad range of ways to define reports and create different types of reports such as basic lists, statistics, and ranked lists.
Features
The SAP Query comprises five components: Queries, InfoSet Query, InfoSets, User Groups and Translation/Query.
Classic reporting- the creation of lists, statistics and ranked lists- are covered by the InfoSet Query and Queries components. Other components range of functions cover the maintenance of InfoSets, the administration of user groups and also the translation of texts created in the SAP Query.
All data required by a user for a report can be read from various tables.
To define a report, you first have to enter individual texts, such as titles, and select the fields and options which determine the report layout. In the WYSIWYG mode, you can edit the lists using Drag & Drop and various toolbars.
AD Hoc Query
Definition
A Web item that enables you to create and change queries in a Web application on an ad-hoc basis.
Use
You can use the Ad-hoc Query Designer Web item in the Web Application Designer to structure Web applications in which you create or change queries. The Web item is as a tool for designing ad-hoc queries in a Web environment.
In particular it enables you to:
·        Create queries by assigning characteristics from an InfoProvider to rows, columns, filters, and free characteristics, and including key figures from the InfoProvider in the key figure structure of the query.
·        Restrict or filter key figures and characteristics
·        Use predefined key figure structures and restricted or calculated key figures in the query
·        Set or change query properties and key figure/characteristic properties in the query
·        Create or change conditions and exceptions
When compared with the BEx Query Designer, the Ad-hoc Query Designer Web item has the following restrictions when creating or changing queries:
·        You cannot integrate variables into the query directly.
However, you can use variables in reusable structures, or restricted or calculate key figures, which are used in the Ad-hoc Query Designer
·        The query can contain only one structure. This structure has to be the key figure structure and be in the rows or columns of the query.
-        You cannot use key figures or key figure structures in the filter.
-        You cannot define exception cells, since this requires two structures.
You cannot create the following objects using the Ad-hoc Query Designer Web item:
-         Reusable structures
-         Reusable restricted key figures
-         Reusable calculated key figures
-        Local calculated key figures
You can create local, restricted key figures using the Ad-hoc Query Designer Web item.
You can edit existing queries in the Ad-hoc Query Designer Web item, if the queries adhere to the restrictions laid out above The Ad-hoc Query Designer checks these requirements when loading a query. If the query is too complex, the query can be loaded into the Ad-hoc Query Designer but you cannot change it there. You then receive the appropriate message. You can still check and execute the query.
"Ad Hoc" is a Latin phrase which means "for this purpose" and in today's parlance generally means "on the fly," or "spontaneously."
An ad hoc query is a query that is run at the spur of the moment, and generally is never saved to run again. These queries are run using a SQL statement created by a tool or an administrator. So therefore, such a query is one that might suit a situation which is only there for the moment and later on will become irrelevant.
As queries become more complex, it can be difficult to write them correctly ad-hoc. To help with this, one can instead write the knowledge needed for queries as business rules in English, and then use a system called "Internet Business Logic" to automatically generate and run the SQL queries. One can then get explanations of the results, in English, at the business level.
Check these links....
http://help.sap.com/saphelp_nw04/helpdata/en/1f/03223c5f00612be10000000a11402f/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/80bf2f79-021d-2a10-5082-dadc79aaa92c
http://www50.sap.com/businessmaps/27FEEF3A12444F89A8524CCACAF4F5BF.htm
http://help.sap.com/saphelp_nw70/helpdata/en/15/00a042b443c56ae10000000a155106/content.htm
Reward points if useful....
Regards
AK

% Wildcard selection - extract data via Query as a Web Service

Hello all,
I am using Query as a Web Service to extract data through to my Xcelsius document. I have a series of charts that display summed data according to user selections within some combo boxes.
Is there any way to send through a wildcard selection, i.e. pass a " like '%' " query string somehow through to the database?
With the query that I have created:
I have a measure value returned
I have 4 filter objects
I have selected the "Prompt" option for each
Within the Data Manager, the prompt fields are assigned to cells which reference the combo box selections
When I build the query, the selections available are many (equal to, not equal to, greater than, greater than or equal to, etc), but there is no 'like' comparison.
Alternatively, is there a way that I can pass the selected parameter values, including " like '%' " if no value is selected within a dropdown, to the original measure calculations within the universe?
I hope this makes sense, let me know if I need to clarify anything. Any help would be very much appreciated.
Cheers,
Marco

Very easy solution - select 'matches pattern' within the filter objects selection when building the query.
Don't know why I didn't try this earlier.

Transport selection screen variant of ad-hoc query

Hi, I've created an ad-hoc query using sq01,sq02,sq03 and I've assigned it to a transaction and created a screen selection variant.
Now I want to transport the screen selection variant. RSTRANSP doesn't seem to work for that.
Thanks

Hi Alejandro,
You can transport this to other system by make use of program RSAQR3TR, before you transport to other systems, please check everything is working fine in Development system, once everything is perfect..
Please use the program which i have stated above and transport user group first, then infoset and then query,, you can do it in two ways..by downloading and uploading or else by export and import..
if you still have any queries on this. share with your screenshot what have you done,, so i will help you on it..
Thanks
Sriram

Ad hoc query - Infoset, after selection it is giving two different output

Hi All,
We are facing problem in ad hoc query, after PQAH Ad hoc query, when we go to one infoset, so after making some selection and putting some output field,
When we click on refresh data button(in lower pane) so it gives only one record, which is incorrect, but when we click on u2018Start Outputu2019 button it gives 3 records those are correct.
Can anyone tell me, why this is giving different output.(first time 1 record, and second time 3 records) record 3 output is correct.
Regards,
Kumar
Edited by: kumar r12 on Mar 18, 2011 9:00 AM

Hi Kumar,
Are you looking at the "Hit List" or the output of the results in the lower pane? The hit list will only give you the number of persons who will be in your output. The refresh button should give you a preview of the output.
What persons or fields are different or not shown in the preview area vs. the output? Also, what are the dates for the data? Are you looking at current data or looking for history? The output may be showing you history and the preview only current data. Most concerns with Ad Hoc Query output are related to dates - for the selection and the output.
Paul

How to activate Show Set Operations in Ad Hoc query

When I go into ad hoc query using an infoset I created the Extras > Show Set Operations and Switch off object selection functions are greyed out and I cannot select them. On another infoset these functions are available for selection.
Is there some setting in the info set creation that allows these function to be available for selection?

closing question

Help in Ad-hoc query and Hr form editor

any body have material links of Ad-hoc query(it means how the reports are generated with Ad-hoc query) and Hr form editor(with examples) plz forward it to me???????????

Hi,
HR Ad Hoc Query is the special version of InfoSet Query with the HR object selection.
You can find the system documentation here:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/f9/cc9138e4a0341fe10000009b38f8cf/frameset.htm
However I doubt the use of documentation of the query generator. So what is your concrete question?
Or in any R/3 via application help of transaction SQ01.
Also HR580 is a good course.
Regards,
Michael

SAP Query vs. Ad-Hoc Query

Hi guys,
Can anyone explain to a newbie like me
1. what's the difference between SAP query and Ad-hoc query?
2. Can we link all SAP Queries to tcode and thus access SAP QUeries via Tcode?
3. Ad-hoc query is unlike SAP query as in it cannot be accessed via Tcode, correct?
4. Seems to me SAP query works similarly to custom abap queries. Thus, y don't we just used custom abap queries instead?
5. Are the selection screens for all SAP queries the same? Cause I accessed 3 SAP Queries, and all their selection screen are exactly the same with fields like Object ID, Evaluation Path...
Message was edited by:
zhenmin wang

https://www.sdn.sap.com/irj/sdn/wiki?path=/pages/viewpage.action?pageId=30083
Please give me reward points...

Ad-Hoc Query Field using HR_99S_INTERVAL_BETWEEN_DATES function module

I have created an additional field in Sq02 to calculate years between two dates and am using function module HR_99S_INTERVAL_BETWEEN_DATES.
There are no syntax erros but when I run a query in Sq01 and output the field it doesn't calculate instead gives "00000" output.
The field Code in the additional field
Clear ZHR_SERVICEYRS.
DATA: V_MONTHS TYPE i.
DATA: V_YEARS TYPE i.
DATA: V_MONTHS1 TYPE char20.
DATA: V_YEARS1 TYPE char20.
CALL FUNCTION 'HR_99S_INTERVAL_BETWEEN_DATES'
EXPORTING
   BEGDA           = P0002-GBDAT
   ENDDA           = Sy-Datum
TAB_MODE        = ' '
IMPORTING
DAYS            =
C_WEEKS         =
   C_MONTHS        = V_MONTHS
   C_YEARS         = V_YEARS
WEEKS           =
MONTHS          =
YEARS           =
D_MONTHS        =
MONTH_TAB       =
V_MONTHS1 = V_MONTHS.
V_YEARS1 = V_YEARS.
CONCATENATE V_YEARS1 '.' V_MONTHS1 INTO ZHR_SERVICEYRS.
condense ZHR_SERVICEYRS.
has anybody had similar problems! Help Appreciated!

Hi Anuj,
Yes, you use Transaction Code SQ02. Find your infoset on the list - if you want to create a new infoset you can do so. If it is an existing infoset, select it and Change. On the next screen you will see all the infotypes in that infoset on the left. The fields available for Ad Hoc are on the right. Open the infotype table on the left and the field group on the right. If the field is not included in the field group all you have to do is drag and drop from the list on the left to the correct field group. If the infotype is not already in your infoset, select Edit --> Change Infotype Selection from the top menu bar. Place a check in the new infotype and then return and do the drag and drop if necessary. You will find the basic fields already moved to the field group.
You say you want information from IT0008-Basic Pay and IT1005-Planned Compensation. Problem is that if you use the standard HR logical data base, there is no link directly between a person and IT1005. IT1005 is assigned to a Position or a Job. If it is assigned to a Position, you can select the "Change Infotype Selection" action and ago to the bottom of the list to Related Objects. Here select Position and open that to find the IT1005. If the IT1005 is tied to the Job, there is no direct link. Thus, if it does not already exist, you will need to create an infoset based on the PCH logical database and object Position. Now you can link that Position to "Holder"-Person and "Described by"-Job. Again, select the infotypes and fields you want and you will be able to obtain your information via Ad Hoc Query based on that infoset.
Paul

Ad-Hoc Query for OU's and their Cost Center

Cost Centers are often inherited from parent OU's. If I try to make an Ad-Hoc query, select some OU's and show the Cost Centers via the relationship A11, the fields are empty unless the Cost Center is hardcoded for the OU.
Is there a way to create an Ad-Hoc query that shows the Cost Centers even if they are inherited? I can't make any changes to system tables or other customizing.
Thanks in advance!

Unfortunately I'm not authorized to use SE16.
This is my selection:
Object ID: xxx (Selection)
Object Type: O (Selection)
Plan Version: 01 (Selection)
Relationship Between Objects: 011 (IT1001)
Relationship Specification: A (IT1001)
Type of Related Object: K (IT1001)
Output:
Object ID (IT1000)
Object Abbreviation (IT1000)
Object Name (IT1000)
ID of Related Object (IT1001)
Any other way?

Ad Hoc Query Data Issue for Position Based Infoset

Experts,
I've created an infoset that is based on the S object using the PCH database. For this infoset, I've included several infotypes with focus on 1000, 1001, and 1028. I've included the Address infotype (1028) as this is where we store our work location information. For some reason though when I attempt to pull information from 1028, specifically the House Number and Street field, the Postal Code field, and the City field.
For some reason though, no data is being returned in those fields. I've verified for the position (in PP01) that I'm querying on that the data is maintained in 1028, and I've verified that I'm attempting to report on the correct fields by verifying the field technical names I'm pulling in the Ad Hoc Query with those I know have data stored in them on the infotype for the specific position.
Would anyone have any guidance on what could be happening here or what I might need to adjust to be able to pull this data?
Thanks in advance for your time and help.
Best Regards,
Joe

To add some further clarity to this item, the Address infotype on the Position (S) object is pulling from a dropdown of selectable Buildings. If unfamiliar, the Building drop is populated by configuration data from the IMG. The fields that are populated then in the Address infotype actually come then from the Building entries and are simply populated onto IT1028 (address) depending on which Building is selected.
I think this is what it occuring then when I select the fields from the Address infotype and I see nothing populated in the Ad Hoc query since the field information is not actually stored in IT1028 but on in the Building entry.
Has anyone else experiencing this particular problem? If so, have you found a solution?
Regards,
Joe

Hit List in ad-hoc query

Hi All:
Does anyone know how to add the "Hit List" functionality to a query infoset? My users need to be able to press the hit list to determine a count of pernrs to be included in their ad-hoc queries

Hello: This is very helpful information, however the option to "switch on objection selection" is not available for some of my query infosets. The option is grayed out. I have the option for some of my query infosets so I do not believe this is a security issue. Is there a setting that must be turned on during the build of the query infoset?
Can you help?

AAP and EEO Report by Ad Hoc Query

SAP Gurus,
My client went live with basic modules of SAP Jan 2007. The problem is with AAP EEO Report. We will develop ABAP report later. For now we want to generate the AAP EEO report by using Ad Hoc Query. We are storing the EEO and AAP codes in IT1610 for Job. If I have to build query what is the best way :
1- I tried an infoset with PNPCE and apart from the basic PA infotypes I selected 1000, 1001 and 1610 for job. But when I select EEO and AAP category in output I dont get the actual data. I know I am doing something wrong here but dont know what ?
2- If I will start a table join with IT0000, IT0001,.etc and V_T5U13 .will it work ?
Any other suggestions how can we address this issue temporarily by ad hoc query ?
Sanghamitra

First, do not try and reinvent the wheel...the EEO-1 and AAP reports are standard supplied SAP reports and can be found under Human Resources --> Personnel Management --> Administration --> Infosystem --> Reports --> Administration US --> Compliance.
The EEO-1 report is changing for 2007 and the latest support packs must be installed to give you the new tables and table entries, features and report layout needed for this year. See SAP Notes 976273, 435204 and 986115. The IT1610 itself changes as do the definitions, so the support pack installation is a must,
If you still want to try to get this information via Ad Hoc Query, you will need to utilize a PCH based Infoset. Create this based on the object Position. The position is your link between the person with HR Master Data and the Job with job related data such as IT1610. With this infoset, you can do the reporting on the EEO Job classes from IT1610 and the Ethnic groupings from IT0077-Additional Personal Data for the employee and gender from IT0002.

Date object doesn't work in query filters

I'm trying to create a universe object called Next Biweekly Pay End Date. Some background: there is an end date for our biweekly payrolls every 14 days, and the logic behind the object is basically that if there was a biweekly pay end date 7 days ago, the next one is 7 days from today (that is, sysdate + 7), etc.
I have it working so that it displays the correct date when used in a WebI report. However, when I use it in a query filter in a WebI report (like, Pay End Date = Next Biweekly Pay End Date), I don't get an error, but I also don't get any data. Somehow my object doesn't work in a query filter. The purpose of the object is for use in query filters, so I need to get this to work.
My best guess about why it doesn't work in a query filter is due to some issue with the data type. Pay End Date has a data type of date in the universe. I gave Next Biweekly Pay End Date a data type of date also, but the query filter still doesn't work; I get "no data to fetch."
We're using XI 3.1.6 and Oracle 10. Any ideas about how to get this to work?
If it helps, here is the definition of Next Biweekly Pay End Date. The logic is that it takes today's date, subtracts Oct. 31, 2009 (a biweekly pay end date), divides by 14, and looks at the remainder. If the remainder is 0, then today is a pay end date and the next one is 14 days from now. If the remainder is 1, yesterday was a pay end date and the next one is 13 days from now, etc.
case
when mod((trunc(sysdate)) - (to_date('31/10/2009')),14) = 0 then (sysdate + 14)
when mod((trunc(sysdate)) - (to_date('31/10/2009')),14) = 1 then (sysdate + 13)
when mod((trunc(sysdate)) - (to_date('31/10/2009')),14) = 2 then (sysdate + 12)
when mod((trunc(sysdate)) - (to_date('31/10/2009')),14) = 3 then (sysdate + 11)
when mod((trunc(sysdate)) - (to_date('31/10/2009')),14) = 4 then (sysdate + 10)
when mod((trunc(sysdate)) - (to_date('31/10/2009')),14) = 5 then (sysdate + 9)
when mod((trunc(sysdate)) - (to_date('31/10/2009')),14) = 6 then (sysdate + 8)
when mod((trunc(sysdate)) - (to_date('31/10/2009')),14) = 7 then (sysdate + 7)
when mod((trunc(sysdate)) - (to_date('31/10/2009')),14) = 8 then (sysdate + 6)
when mod((trunc(sysdate)) - (to_date('31/10/2009')),14) = 9 then (sysdate + 5)
when mod((trunc(sysdate)) - (to_date('31/10/2009')),14) = 10 then (sysdate + 4)
when mod((trunc(sysdate)) - (to_date('31/10/2009')),14) = 11 then (sysdate + 3)
when mod((trunc(sysdate)) - (to_date('31/10/2009')),14) = 12 then (sysdate + 2)
when mod((trunc(sysdate)) - (to_date('31/10/2009')),14) = 13 then (sysdate + 1)
end

Thanks for the suggestions.
I did some more testing, and there seems to be something more complicated going on. I ran the following code in SQL*Plus:
SELECT distinct M_PYDW1.PYSTATUS.DW_OWNER,
case
when to_date(sysdate, 'dd/mm/yyyy hh24:mi:ss') >= to_date('01/01/2010','dd/mm/yyyy hh24:mi:ss') then To_Date((sysdate - 2),'dd/mm/yyyy')
else to_date(sysdate +2, 'dd/mm/yyyy')
end
FROM M_PYDW1.PYSTATUS
The condition should be true, because the sysdate (today is Jan. 20) is greater than 1/1/2010, so I should get a result of sysdate - 2 (Jan. 18). But the result I get is Jan. 22 (sysdate +2). It seems that the comparison is failing even though I'm formatting both sysdate and 1/1/2010 as dates with a timestamp. What could cause that?
One more mystery: when I run the same code as above in a WebI report (using custom SQL), I get the error ORA-1830, date format picture ends before converting entire input string.

Out put problem in Ad hoc query reports

Hi Gurus,
I am tryting to generate a report through Ad hoc query in S_PH0_48000510 - Ad Hoc Query SAP/Query/HR_ADM - > Selected several options like personnel number / employee name / entry date / leaving date.
But when we select it shows the input details but when i try for output the entry date / leaving date even the names of the employees are not reflecting.
But the age/date of birth other fields are coming in output.
Kindly let me know the solution to get a out put. If there is any changes need to be done in the back end. Pls advice with the path details.
Thanks & Regards,
Pradeep Krishnamurthy

Hi Madhu,
Yes, I did but out put is not coming.
Regards,
Pradeep Krishnamurthy

Object selection on Ad-Hoc Query

Similar Messages

Maybe you are looking for