SAP Adhoc Query by payroll area and respective periods

Hello,
I would get an idea of how to make SAP query by having a selection screen for Payroll area and its respectve periods (respective control record). I was able to get the selection screen where I can input payroll area. But the date range for the report is a manual feed. I want something like when we select the payroll area, then I want the periods to be shown (payroll period - current period or other period). I'm new to making this SAP query. Any inupt is appreciated. Thanks.
Raj.

in the adhoc query we can select the periods based on the frequency but the dates will not get default
As in the Pay roll driver the dates get defaulted based on the settings made in Control Record Status
so i dont think this is possible thru Standrad
let wait for expert views

Similar Messages

Adhoc query - Total payroll day issue on infotype 2001

Dear Expert,
I am working on the adhoc query and would like to generate the total number of payroll days taken by a particular employee.
E.g. Employee A has 4 leave record in Nov 2011
14-Nov, 16, Nov, 23 Nov, 25 Nov
When I select the reporting period between 1-Nov-2011 to 30-Nov-2011, the total payroll days generated by the adhoc query is only 1. I am not sure why. Please help
Best Regards,
WF

Hi,
Might be remaining days are Non working days/Weekly offs/ Holidays falls..
You Better Check through PA30 Overview of Absence records, Whether the Days are deducted from Quota or not.
Need to check absence class in V_554s_0

SAP ADHOC Query execute only

dear all,
I have setup a new role and made adhoc query for users to be able to maintain, change etc......
You can set up authorizations in such a way, that certain end-users in a user group are authorized to maintain and execute queries, while other members of the same user group are authorized only to execute existing queries."
the above statement, states other memebrs can be setup to execute only?
what must I do to make the endsers allow them to execute the query only?
for the first set of users i have within object S_QUERY made them to use change, maintain and translate.
thanks all

There is info here: http://help.sap.com/SAPHELP_NW70EHP1/helpdata/EN/de/45daf69ef111d195050000e82de14a/content.htm and here: http://help.sap.com/saphelp_46c/helpdata/en/de/45daf69ef111d195050000e82de14a/content.htm
Users with S_QUERY actvt=02 can move between infosets with no problem. If you are removing this then you need to specify which infosets are assigned to a user group and which users are assigned to the user group. If you have lots of users and queries already then this may be a big piece of work and illustrates why use of queries may save time for one team (developers) but give more work for others.

Adhoc Query iview for IT0006 and IT0021

Hi All
SAP has given page in MSS for IT0006 and IT0021 - 'Generic iview Test Page'. This page has 3 iViews : one for employee search , second for IT0006 and third for IT0021. This page is working ok and retrieving data from back end.
But If I replace IT0006 or IT00021 query with my own query then the error on Page is 'System cannot retrieve data'
SAP standard query given in iview property is MSS_IT0006, If I replace this query with my query ZMSS_IT0006 then I get above error.
I have created query ZMSS_IT0006 in work area:- global , usergroup:- /SAPQUERY/MS
Is there any aditional config need if we replace standard SAP query by our own query?
Amit.

in the adhoc query we can select the periods based on the frequency but the dates will not get default
As in the Pay roll driver the dates get defaulted based on the settings made in Control Record Status
so i dont think this is possible thru Standrad
let wait for expert views

Basic query regarding work-area and select query

hi
dear sdn members,
thanks too all for solving all my query's up till now
i am stuck in a problem need help
1) why basically work-area has been used ? the sole purpose
2) different types of select query ? only coding examples
note: no links pls
regards,
virus

hi,
Work Area
Description for a data object that is particularly useful when working with internal tables or database tables as a source for changing operations or a target for reading operations.
WORKAREA is a structure that can hold only one record at a time. It is a collection of fields. We use workarea as we cannot directly read from a table. In order to interact with a table we need workarea. When a Select Statement is executed on a table then the first record is read and put into the header of the table and from there put into the header or the workarea(of the same structure as that of the table)of the internal table and then transferred top the body of the internal table or directly displayed from the workarea.
Each row in a table is a record and each column is a field.
While adding or retrieving records to / from internal table we have to keep the record temporarily.
The area where this record is kept is called as work area for the internal table. The area must have the same structure as that of internal table. An internal table consists of a body and an optional header line.
Header line is a implicit work area for the internal table. It depends on how the internal table is declared that the itab will have the header line or not.
.g.
data: begin of itab occurs 10,
ab type c,
cd type i,
end of itab. " this table will have the header line.
data: wa_itab like itab. " explicit work area for itab
data: itab1 like itab occurs 10. " table is without header line.
The header line is a field string with the same structure as a row of the body, but it can only hold a single row.
It is a buffer used to hold each record before it is added or each record as it is retrieved from the internal table. It is the default work area for the internal table.
With header line
SELECT.
Put the curson on that word and press F1 . You can see the whole documentation for select statements.
select statements :
SELECT result
FROM source
INTO|APPENDING target
[[FOR ALL ENTRIES IN itab] WHERE sql_cond]
Effect
SELECT is an Open-SQL-statement for reading data from one or several database tables into data objects.
The select statement reads a result set (whose structure is determined in result ) from the database tables specified in source, and assigns the data from the result set to the data objects specified in target. You can restrict the result set using the WHERE addition. The addition GROUP BY compresses several database rows into a single row of the result set. The addition HAVING restricts the compressed rows. The addition ORDER BY sorts the result set.
The data objects specified in target must match the result set result. This means that the result set is either assigned to the data objects in one step, or by row, or by packets of rows. In the second and third case, the SELECT statement opens a loop, which which must be closed using ENDSELECT. For every loop pass, the SELECT-statement assigns a row or a packet of rows to the data objects specified in target. If the last row was assigned or if the result set is empty, then SELECT branches to ENDSELECT . A database cursor is opened implicitly to process a SELECT-loop, and is closed again when the loop is ended. You can end the loop using the statements from section leave loops.
Up to the INTO resp. APPENDING addition, the entries in the SELECTstatement define which data should be read by the database in which form. This requirement is translated in the database interface for the database system´s programming interface and is then passed to the database system. The data are read in packets by the database and are transported to the application server by the database server. On the application server, the data are transferred to the ABAP program´s data objects in accordance with the data specified in the INTO and APPENDING additions.
System Fields
The SELECT statement sets the values of the system fields sy-subrc and sy-dbcnt.
sy-subrc Relevance
0 The SELECT statement sets sy-subrc to 0 for every pass by value to an ABAP data object. The ENDSELECT statement sets sy-subrc to 0 if at least one row was transferred in the SELECT loop.
4 The SELECT statement sets sy-subrc to 4 if the result set is empty, that is, if no data was found in the database.
8 The SELECT statement sets sy-subrc to 8 if the FOR UPDATE addition is used in result, without the primary key being specified fully after WHERE.
After every value that is transferred to an ABAP data object, the SELECT statement sets sy-dbcnt to the number of rows that were transferred. If the result set is empty, sy-dbcnt is set to 0.
Notes
Outside classes, you do not need to specify the target area with INTO or APPENDING if a single database table or a single view is specified statically after FROM, and a table work area dbtab was declared with the TABLES statement for the corresponding database table or view. In this case, the system supplements the SELECT-statement implicitly with the addition INTO dbtab.
Although the WHERE-condition is optional, you should always specify it for performance reasons, and the result set should not be restricted on the application server.
SELECT-loops can be nested. For performance reasons, you should check whether a join or a sub-query would be more effective.
Within a SELECT-loop you cannot execute any statements that lead to a database commit and consequently cause the corresponding database cursor to close.
SELECT - result
Syntax
... lines columns ... .
Effect
The data in result defines whether the resulting set consists of multiple rows (table-like structure) or a single row ( flat structure). It specifies the columns to be read and defines their names in the resulting set. Note that column names from the database table can be changed. For single columns, aggregate expressions can be used to specify aggregates. Identical rows in the resulting set can be excluded, and individual rows can be protected from parallel changes by another program.
The data in result consists of data for the rows lines and for the columns columns.
SELECT - lines
Syntax
... { SINGLE }
| { { } } ... .
Alternatives:
1. ... SINGLE
2. ... { }
Effect
The data in lines specifies that the resulting set has either multiple lines or a single line.
Alternative 1
... SINGLE
Effect
If SINGLE is specified, the resulting set has a single line. If the remaining additions to the SELECT command select more than one line from the database, the first line that is found is entered into the resulting set. The data objects specified after INTO may not be internal tables, and the APPENDING addition may not be used.
An exclusive lock can be set for this line using the FOR UPDATE addition when a single line is being read with SINGLE. The SELECT command is used in this case only if all primary key fields in logical expressions linked by AND are checked to make sure they are the same in the WHERE condition. Otherwise, the resulting set is empty and sy-subrc is set to 8. If the lock causes a deadlock, an exception occurs. If the FOR UPDATE addition is used, the SELECT command circumvents SAP buffering.
Note
When SINGLE is being specified, the lines to be read should be clearly specified in the WHERE condition, for the sake of efficiency. When the data is read from a database table, the system does this by specifying comparison values for the primary key.
Alternative 2
Effect
If SINGLE is not specified and if columns does not contain only aggregate expressions, the resulting set has multiple lines. All database lines that are selected by the remaining additions of the SELECT command are included in the resulting list. If the ORDER BY addition is not used, the order of the lines in the resulting list is not defined and, if the same SELECT command is executed multiple times, the order may be different each time. A data object specified after INTO can be an internal table and the APPENDING addition can be used. If no internal table is specified after INTO or APPENDING, the SELECT command triggers a loop that has to be closed using ENDSELECT.
If multiple lines are read without SINGLE, the DISTINCT addition can be used to exclude duplicate lines from the resulting list. If DISTINCT is used, the SELECT command circumvents SAP buffering. DISTINCT cannot be used in the following situations:
If a column specified in columns has the type STRING, RAWSTRING, LCHAR or LRAW
If the system tries to access pool or cluster tables and single columns are specified in columns.
Note
When specifying DISTINCT, note that you have to carry out sort operations in the database system for this.
SELECT - columns
Syntax
| { {col1|aggregate( col1 )}
{col2|aggregate( col2 )} ... }
| (column_syntax) ... .
Alternatives:
1. ... *
2. ... {col1|aggregate( col1 )}
{col2|aggregate( col2 )} ...
3. ... (column_syntax)
Effect
The input in columns determines which columns are used to build the resulting set.
Alternative 1
Effect
If * is specified, the resulting set is built based on all columns in the database tables or views specified after FROM, in the order given there. The columns in the resulting set take on the name and data type from the database tables or views. Only one data object can be specified after INTO.
Note
If multiple database tables are specified after FROM, you cannot prevent multiple columns from getting the same name when you specify *.
Alternative 2
... {col1|aggregate( col1 )}
{col2|aggregate( col2 )} ...
Effect
A list of column labels col1 col2 ... is specified in order to build the resulting list from individual columns. An individual column can be specified directly or as an argument of an aggregate function aggregate. The order in which the column labels are specified is up to you and defines the order of the columns in the resulting list. Only if a column of the type LCHAR or LRAW is listed does the corresponding length field also have to be specified directly before it. An individual column can be specified multiple times.
The addition AS can be used to define an alternative column name a1 a2 ... with a maximum of fourteen digits in the resulting set for every column label col1 col2 .... The system uses the alternative column name in the additions INTO|APPENDING CORRESPONDING FIELDS and ORDER BY. .
Column labels
The following column labels are possible:
If only a single database table or a single view is specified after FROM, the column labels in the database table - that is, the names of the components comp1 comp2... - can be specified directly for col1 col2 ... in the structure of the ABAP Dictionary.
If the name of the component occurs in multiple database tables of the FROM addition, but the desired database table or the view dbtab is only specified once after FROM, the names dbtab~comp1 dbtab~comp2 ... have to be specified for col1 col2 .... comp1 comp2 ... are the names of the components in the structure of the ABAP Dictionary.
If the desired database table or view occurs multiple times after FROM, the names tabalias~comp1 tabalias~comp2 ... have to be specified for col1 col2 .... tabalias is the alternative table name of the database table or view defined after FROM, and comp1 comp2 ... are the names of the components in the structure of the ABAP Dictionary.
The data type of a single column in the resulting list is the datatype of the corresponding component in the ABAP Dictionary. The corresponding data object after INTO or APPENDING has to be selected accordingly.
Note
If multiple database tables are specified after FROM, you can use alternative names when specifying single columns to avoid having multiple columns with the same name.
Example
Read specific columns of a single row.
DATA wa TYPE spfli.
SELECT SINGLE carrid connid cityfrom cityto
INTO CORRESPONDING FIELDS OF wa
FROM spfli
WHERE carrid EQ 'LH' AND connid EQ '0400'.
IF sy-subrc EQ 0.
WRITE: / wa-carrid, wa-connid, wa-cityfrom, wa-cityto.
ENDIF.
Alternative 3
... (column_syntax)
Effect
Instead of static data, a data object column_syntax in brackets can be specified, which, when the command is executed, either contains the syntax shown with the static data, or is initial. The data object column_syntax can be a character-type data object or an internal table with a character-type data type. The syntax in column_syntax, like in the ABAP editor, is not case-sensitive. When specifying an internal table, you can distribute the syntax over multiple rows.
If column_syntax is initial when the command is executed, columns is implicitly set to * and all columns are read.
If columns are specificied dynamically without the SINGLE addition, the resulting set is always regarded as having multiple rows.
Notes
Before Release 6.10, you could only specify an internal table with a flat character-type row type for column_syntax with a maximum of 72 characters. Also, before Release 6.10, if you used the DISTINCT addition for dynamic access to pool tables or cluster tables, this was ignored, but since release 6.10, this causes a known exception.
If column_syntax is an internal table with header line, the table body and not the header line is evaluated.
Example
Read out how many flights go to and from a city. The SELECT command is implemented only once in a sub-program. The column data, including aggregate function and the data after GROUP BY, is dynamic. Instead of adding the column data to an internal l_columns table, you could just as easily concatenate it in a character-type l_columns field.
PERFORM my_select USING `CITYFROM`.
ULINE.
PERFORM my_select USING `CITYTO`.
FORM my_select USING l_group TYPE string.
DATA: l_columns TYPE TABLE OF string,
l_container TYPE string,
l_count TYPE i.
APPEND l_group TO l_columns.
APPEND `count( * )` TO l_columns.
SELECT (l_columns)
FROM spfli
INTO (l_container, l_count)
GROUP BY (l_group).
WRITE: / l_count, l_container.
ENDSELECT.
ENDFORM.
SELECT - aggregate
Syntax
... { MAX( col )
| MIN( col )
| AVG( col )
| SUM( col )
| COUNT( DISTINCT col )
| COUNT( * )
| count(*) } ... .
Effect
As many of the specified column labels as you like can be listed in the SELECT command as arguments of the above aggregate expression. In aggregate expressions, a single value is calculated from the values of multiple rows in a column as follows (note that the addition DISTINCT excludes double values from the calculation):
MAX( col ) Determines the maximum value of the value in the column col in the resulting set or in the current group.
MIN( col ) Determines the minimum value of the content of the column col in the resulting set or in the current group.
AVG( col ) Determines the average value of the content of the column col in the resulting set or in the current group. The data type of the column has to be numerical.
SUM( col ) Determines the sum of the content of the column col in the resulting set or in the current group. The data type of the column has to be numerical.
COUNT( DISTINCT col ) Determines the number of different values in the column col in the resulting set or in the current group.
COUNT( * ) (or count(*)) Determines the number of rows in the resulting set or in the current group. No column label is specified in this case.
If you are using aggregate expressions, all column labels that are not listed as an argument of an aggregate function are listed after the addition GROUP BY. The aggregate functions evaluate the content of the groups defined by GROUP BY in the database system and transfer the result to the combined rows of the resulting set.
The data type of aggregate expressions with the function MAX, MIN or SUM is the data type of the corresponding column in the ABAP Dictionary. Aggregate expressions with the function AVG have the data type FLTP, and those with COUNT have the data type INT4. The corresponding data object after INTO or APPENDING has to be selected accordingly.
Note the following points when using aggregate expressions:
If the addition FOR ALL ENTRIES is used in front of WHERE, or if cluster or pool tables are listed after FROM, no other aggregate expressions apart from COUNT( * ) can be used.
Columns of the type STRING or RAWSTRING cannot be used with aggregate functions.
When aggregate expressions are used, the SELECT command makes it unnecessary to use SAP buffering.
Null values are not included in the calculation for the aggregate functions. The result is a null value only if all the rows in the column in question contain the null value.
If only aggregate expressions are used after SELECT, the results set has one row and the addition GROUP BY is not necessary. If a non-table type target area is specified after INTO, the command ENDSELECT cannot be used together with the addition SINGLE. If the aggregate expression count( * ) is not being used, an internal table can be specified after INTO, and the first row of this table is filled.
If aggregate functions are used without GROUP BY being specified at the same time, the resulting set also contains a row if no data is found in the database. If count( * ) is used, the column in question contains the value 0. The columns in the other aggregate functions contain initial values. This row is assigned to the data object specified after INTO, and unless count( * ) is being used exclusively, sy-subrc is set to 0 and sy-dbcnt is set to 1. If count( *) is used exclusively, the addition INTO can be omitted and if no data can be found in the database, sy-subrc is set to 4 and sy-dbcnt is set to 0.
if helpful reward points

SAP ADHOC Query

Hi,
Please let me know how to export ADHOC query from one client to another client.
Thanks
Somashree

Hello, Somashree!
Maybe it will be useful for you: for exporting query to another client it's very simple using "Download" option in the report RSAQR3TR. It will be downloaded (as file) on your local machine.
To upload the query into another client using report RSAQR3TR you just need to select "Upload" option -> select saved file and press F8.
Regards,
Sergey Ignatov.

Change in existing Payroll Area and its impact on existing PA records.

Hello,
Can anyone let me know please how easy / difficult it would be to change the description of the existing payroll area lets say "AB" to be the one as per requirment lets say "AC" so that it will show employees as AC rather than AB in the future? Also, if this can be done, would there be any impact on existing PA records (eg, how would they get updated to show the new code & description)?
Many Thanks,
Rachana.

Could you please tell the name of that custom report?
One more question is that do the change in payroll area could create the problem while running the retro for the previous payroll area for those employees?
Many thanks
Rachana.
Edited by: Rachana L on Jul 21, 2010 1:06 PM

Pay roll area and control period

hai experts
we have pay roll area ,control period in personal administration and we have the same options in pay roll so can any body help me out in which option we have to choose
thanks
thjea
points will ne rewarded

Hi Theja,
Actully we have same options in country specific payroll and control record. If i am not wrong its control record not period.
Its upto you how do you acutally makes use of those options.
You can release payroll anyways and even exit the same.
Let me know if you need anything else.

SQ01 SAP adhoc query error

Hi,
We face a very peculiar problem. A particular user is not able to
execute the SQ01 queries for some reasons. All the other users are able
to execute the queries correctly.
When this particular user is trying to execute the query, he gets an
error message that says
"No archive information found for object type and document type"
The details of this error message is as follows:
No archive information found for object type and document type
Message no. PT019
Diagnosis
No information was found about optical archiving. This may be due to
either of the following reasons:
1. No valid archiving parameters were passed
2. Your system is not configured for optical archiving
System response
Processing is cancelled.
Procedure
Specify valid archiving parameters or check whether your system is
configured for optical archiving.
Please let us know why this error is coming and that too for this user
only. We've checked the other settings like Infoset - user-group
assignments etc which are perfectly fine.
Can anyone figure what could be the issue?
Thanks & regards,
Sam

Hi to all,
I have the same problem as you. I have an user that cannot execute any query. When this particular user is trying to execute the query, he gets an
error message that says
"No archive information found for object type and document type"
The details of this error message is as follows:
No archive information found for object type and document type
Message no. PT019
Diagnosis
No information was found about optical archiving. This may be due to
either of the following reasons:
1. No valid archiving parameters were passed
2. Your system is not configured for optical archiving
System response
Processing is cancelled.
Procedure
Specify valid archiving parameters or check whether your system is
configured for optical archiving.
Please let us know why this error is coming and that too for this user
only. We've checked the other settings like Infoset - user-group
assignments etc which are perfectly fine.
IT IS THE SAME ISSUE.... PLEASE CAN ANYONE TELL ME THE SAP NOTE ... OR HOW TO FIND IT... HOW TO FIND THE TABLE ENTRY AND DELETE IT
Moderator message - Welcome to SCN.
Moderator message - But please do not use all caps or use words like ASAP - everyone's problem is important
Edited by: Rob Burbank on Sep 23, 2009 5:03 PM

SAP HR Adhoc query

Hi
How we can develop HR REPORTS without programming knowledge.
If it is by SAP Adhoc query.what are the steps to create.
Thanks

Dear Archana,
Use the following three transactions for creation and Maintaining queries :-
SQ01, SQ02 and SQ03.
Details are available in :-
http://help.sap.com/saphelp_47x200/helpdata/en/f6/c39138e4a0341fe10000009b38f8cf/frameset.htm
Best Regards
Satish Nair

Re: Transport problem of SAP Query in Global Area

Hi All,
I am facing a problem in transporting the query which is created in Global area.
I created a Query in Global Area and saved in a Transport Request. Now i created a Transaction code for this query by taking the Program name generated by this Query.
then i released the TR to Quality sys, which contains User Group, Infoset, Query & Transaction code. I see User Group & Infoset in my Quality sys but i dont see th Query & Transaction code assigned to this Query, and when i try to run the transaction code assigned to this query its giving dump saying 'LOAD_PROGRAM_NOT_FOUND'.
Could anyone please help me in resolving this..am i missing any steps here...kindly do the needful...
Regards,
Pavan

Hi i solved my problem by myself.
I have to set Query as external available and have to use the MDX Query.
Its strange because if i build a new report the query dont have to be set as external available.

ADHOC Query - display field OPELO IT 0045

hi experts,,,
really need your help on this, i really need to add field OPELO - Loan amount balance in SAP Adhoc query.
Please help.
Thank You

Hi,
Where do we find this customizing field we need to select? We have tried accessing sq01 and changed a query we have created. We clicked on the basic list button and checked the checkboxes for list field and selection field. When we got to infoset query, the selection checkbox is still missing. Are we checking the right path? The infoset is also missing that checkbox.
We also got a suggestion here that maybe the problem is on the "extras" tab in SQ02 - that our field should have an entry there.

Is there any standard Adhoc query to get the Previous employers list

Hi Experts,
Is there any standard Sap Adhoc query available to get the details of Previous empoyers list.
Please advice me to get the list of employees with their previous employers..
Thank you very much.
Regards,
Vishnu.

Hi Vishnu,
U could go as per wat Suhasini has said. But if u want the end user to view this report time and again, then u need to create a query.
The steps are as follows:
1) T-code: SQVI
2) Qucik View: give some name here and then click on "Create"
3) You will get a "Create Quick View" screen.
4) Goto "Datasource" and select "Logical Database" from the drop down
5) Then goto "Tableview" and enter "PNCPE" and click on enter.
6) A screen pops up and click on the Infotypes u would want to extract the data from and press enter.
7) Now, u would get the following screen "Qucik Viewer: Initial screen". Here u can see coulple of tabs.
8) Goto the tab "List selcted field" and select watever fileds u want in the output screen and then press "Execute".
Hope this would solve ur issue.
Thanks

Prompt List of Values in WebI - SAP BI Variable - SAP BI Query -BI Infoset

Hi,
We have a Multiprovider built on an Infoset. SAP BI Infoset is built using 2 DSOs.
There is a SAP BI Query on top of this Multiprovider.
Multiple-Single Values type Optional Variables are created for some of the Objects of this SAP BI Query.
Universe is created on top of this SAP BI Query, using SAP Integration kit.
WebI is created on top of this Universe.
Prompts are created on some of the Universe Objects, for the WebI report.
We are facing a typical problem.
When a WebI prompt is created on one particular object, (which also has a Multiple Single Value type Optional Variable in SAP BI Query), its List of Values is showing up only first three values in WebI. The SAP BI Variable in BEX Analyzer shows up all the 8 values for the List of Values, for the same object.
The Output WebI report has more values for the object than shown up in the List of Values & this is the problem.
We tried to keep the settings in Info-object, DSO, Infoset, Multiprovider = Values in Master Data (for the List of Values).
Similar objects and similar variables for the same query / webi show all the List of Values.
Any guidance on aspects to be checked would be helpful.
regards,
Rajesh K Sarin

Problem :
If an SAP BI Infoset is used in data modelling, and a restricted key
figure is created in the SAP BI Query; the resultant WebI Object Prompt
for the Info-object, only shows up LOVs which have been used for the
restricted Key Figure. Both the things are not related except for the
fact that some of the values for the same object are used for the
restricted key figure.
Details :
We have a Multiprovider built on an SAP BI Infoset.
SAP BI Infoset is built using 2 DSOs.
There is a SAP BI Query on top of this Multiprovider.
There is a restricted key figure in the sap bi query. KeyFigure "Number
of Records" is restricted for 3 of the relevant Info-object "Meter
Reading Status" values.
Universe is created on top of this SAP BI Query, using SAP Integration
kit. WebI is created on top of this Universe.
Prompt is created on the Universe Object for Meter Reading Status, in
the WebI report.
List of Values is showing up only the three values in WebI (which were
used in the Restricted Key Figure calculation).
SAP BI Variable in BEX Analyzer for the same Info-object Meter Reading
Status shows up all the 8 values for the List of Values.
The Output WebI report has more values for the object than shown up in
the List of Values & this is the problem.
We have kept the settings in Info-object, DSO, Infoset,
Multiprovider, Query = Values in Master Data (for the List of Values).
When we delete the "Restricted Key Figure" from the SAP BI Query, the
refreshed Universe and Webi have a complete set of List of Values
applicable.
Steps for Reconstruction
1. Create Infoset
2. Create SAP BI Query on Infoset
3. Create Restricted Key Figure for Number of Records and few of the
values for a characteristic info-object "X".
4. Create BO Universe on SAP BI Query
5. Create Webi on BO Universe
6. Create a Prompt on the characteristic info-object "X".
7. Check List of Values for the characteristic info-object "X" in SAP
BI Query and WebI.
8. LOVs in WebI are equal to the values used for restriction in the
restricted key figure.
9. Delete the restricted key figure from SAP BI Query.
10. Refresh Universe
11. Webi prompt shows all the values for the prompt on "X".

UK Payroll (Payroll Area)

Hi Experts
A new payroll area has been set up for MM from NN(with employees being ended on and restarted on different payroll areas/personnel numbers) an example of this is personnel number 1234 (the new number), adminstrators need to input the past absences against the new personnel numbers in the new payroll area and they are getting the error message (Does not Exists in IT0001) .Please analyise and let us know your findings.
Thanks
Githa

Hi Sri,
I cant give Proper inputs now bcz i am not aware of the Eaxct Reuirement still Investigating.Please look in to the Following it may be help to know the Requirment
I think this is Related to "Multiple Employement"
Bcz for the New Perner IT000 Over view.(Perner Numbe 60256)
Start Date      End Date     Action Type
01.04.2009    31.12.9999   New Starter
In IT0031 have the Two Perner Numbers for the New Perner.(15025 & 15024)
The Inputs of these Two perner Numbers
For the Perner 15024      IT000
Start Date      End Date     Action Type
01.04.2006    31.03.2008   Data Migration Hiring (Legact)
01.04..2008    31.03.2009 Automatic Pay Increase
01.04.2009     31.12.9999   Leaver
Perner 15025 : IT000 Over View
Start Date      End Date     Action Type
01.04.2006    31.12.2007   Data Migration Hiring (Legact)
01.01.2008    31.12.9999   Leaver -Multiple Employment
Thanks
Githa

SAP Adhoc Query by payroll area and respective periods

Similar Messages

Maybe you are looking for