Summation button missing in abap query ..

Hi,
How to activate summation button in Abap query..
Problem is ,we had instaled some service packs in our production system..
After this we found that ,when we run one of our Abap query (with transaction code) in output summation button is not there.
Can you please let me know how can we activate this summation button..
Thanks,
Parnith..

Hi Amit,
Thanks For Reply..
Even though there are summables in list ,summation button is deactive..( It is not being dispalyed on output list)
Can you please suggest the process to activate this summation button..
Thanks
Parnith

Similar Messages

Reg:Radio button in ABAP Query

Hi ABAPers ,
I created radiobuttons in SQ02 there i have to write the coding for it ... what type of coding we have to write
ALV coding wll work out or what type of coding we have to write can you guys plz suggest me
Help me out from this problem i am not familiar with ABAP Query
Regards,
Y Ravichandra.

Hi Ravichandra,
   You have to use at selection-screen output event for this purpose here is a sample code try it and you will get the logic.
PARAMETERS :
   p_flight RADIOBUTTON GROUP r1 ,
   p_book RADIOBUTTON GROUP r1 .
PARAMETERS :
w_temp1 RADIOBUTTON GROUP r2 MODIF ID sc1 ,
w_temp2 RADIOBUTTON GROUP r2 MODIF ID sc1 .
SELECT-OPTIONS s_carrid FOR sflight-carrid MODIF ID sc1 .
                                       " Airline Code
PARAMETERS :
w_temp01 RADIOBUTTON GROUP r3 MODIF ID sc2 ,
w_temp02 RADIOBUTTON GROUP r3 MODIF ID sc2 .
SELECT-OPTIONS s_bookid FOR sbook-bookid MODIF ID sc2 .
                                       " Airline Code
*                       AT SELECTION-SCREEN OUTPUT                    *
AT SELECTION-SCREEN OUTPUT .
IF p_flight = 'X' .
    fl_flag = 1 .
    LOOP AT SCREEN.
      IF screen-group1 = 'SC2'.
        screen-active = 0 .
        MODIFY SCREEN .
      ENDIF.                           " IF SCREEN-GROUP1 = 'SC2'
    ENDLOOP.                           " LOOP AT SCREEN
ELSEIF p_book = 'X' .
    fl_flag = 2 .
    LOOP AT SCREEN.
      IF screen-group1 = 'SC1'.
        screen-active = 0 .
        MODIFY SCREEN .
      ENDIF.                           " IF SCREEN-GROUP1 = 'SC1'
    ENDLOOP.                           " LOOP AT SCREEN
ENDIF .                                " IF P_FLIGHT = 'X' .
Here in this case, There are 2 radio buttons and 2 select options. On clicking the first radio button one of the select option is hidden. If you you just have a single radio button then you can avoid using at selection-screen output and just write your code start-of-selection.
Much Regards,
Amuktha

Abap Query missing in Dev & Production

Hello all,
I've got a query report named AQFKSYSTQV000004ZLISTMAT====== which does not have infoset neither user group assigned, however it can be lauch through SE38.
As seen on FM RSAQ_GENERATE_PROGRAM.
* Namenskonventionen
* AQwwbbbbbbbbbbbbqqqqqqqqqqqqqq:
*   ww             - 00..99 Mandant 000 bis 099 im Standardbereich
*                    A0..YZ Mandant 100 bis 999 im Standardbereich
*                    ZZ     im globalen Standardbereich
*   bbbbbbbbbbbb   - Benutzergruppe
*   qqqqqqqqqqqqqq - Query
Query: ZLISTMAT
User Group: SYSTQV000004
I already launched START_REPORT with usergroup SYSTQV000004 and query name ZLISTMAT, look up through SAP Notes, report RSAQR3TR import/export utility, but this can't be done because it does not exist in our client
We're on an upgrade from 5.0 to 6.0 and SAP suggests not to tranport OT between different systems.
Question is, how can we find out where Abap Query is defined?
Thank you and have a nice day,
Ruben.

Hi Ruben,
You could try the following Work around
1. Goto Table TRDIR with your program name and find who created the program. This would mean that the Quick View has been created by the same person.
2. Goto transaction SQ01 in each of the available clients of your system and goto the following path QUERY->Convert Quickview
3. Now give the user name from TRDIR in the field USER and use the F4 of the field Quickview to check if the Query ZLISTMAT exists in the same client. If it does convert it into a ABAP query and then using the download option in SQ02 move the query to the Dev environment and Prod also if required.
Hope this helps.

ABAP Query Transport request related

Hi,
I have created a Abap query,
1) User group
2)Infoset
3) Query
But when i transport the request in to Quality, I can see only Infoset, not able to see User group and query which i created in the
Development
Please suggest, is this std behaviour or is anything missed
Rgds,
Jai

Thanks to all,
I just created TR with new package for user group and included ifoset and query in the same TR
and imported, issue is resolved
But my question is,where we can utilize below help material, I have spent much time to understand below given explaination and finally left without any conclusion
Short text
SAP Query: Transport tool
Description
The report RSAQR3TR handles all tasks concerning the transport of queries, InfoSets and user groups.
General information
Queries, InfoSets and user groups are stored in the table AQDB. This table is client-specific. For the transport of queries, InfoSets and user groups, there is a special client-independent transport table called TAQTS. You can carry out transports either
·     from a client (source client) of an SAP system to another client (target client) in the same SAP system or
·     from a client (source client) of an SAP system (source system) to a client (target client) in another SAP system (target system).
In both cases, you have to perform similar actions.
The objects to be transported must first be copied from the source client using an export from the table AQDB into the transport table TAQTS. At the same time, a transport request is created for the transport system that includes all entries created by the export from table TATQS (transport dataset). The name of this transport request conforms to the transport system naming conventions (sysKnnnnnn) and is included in the export log. The transport dataset is stored in the table TAQTS under a key which matches the name of the transport request.
If you are transporting within one SAP system (from one client to another), you can import the transport dataset from the target client. The name of the transport request to use for this purpose is that specified during the export, since it should match the key of the transport dataset in the table TAQTS. With this import, the transport dataset is read from the transport table TAQTS and inserted into the table AQDB, where extensive checks ensure that there are no inconsistent statuses in the table AQDB.
If you are transporting from one SAP system to another, you must first use the transport system to release and export the transport request generated by the export. This transports the transport dataset from the transport table TAQTS into the target system. Then, you can import from the target client of the target system, as described above.
The transport datasets generated by exports in the transport table TAQTS are not deleted after successful import unless this is explicitly requested. Therefore, you can import a transport dataset several times (when copying a functional area to several different clients, for example).
This report handles exports (generation of transport datasets), imports (reading of transport datasets) as well as the management (display and deletion) of transport datasets.
As transport action, you must specify one of the values EXPO (export), IMPO (import), SHOW (display transport dataset) or DELE (delete transport dataset).
Transport action EXPO (exports)
If you select the 'Test only' parameter when exporting (no blank characters), the system determines only those queries, InfoSets and user groups that would be selected according to the selections for transport described below and generates an appropriate log. A transport dataset is not generated in the table TAQTS. This allows you to check whether a selection really includes the queries, InfoSets and user groups to be transported.
With exports, there are four different options for selecting objects (user groups, InfoSets, queries) to be transported. These are 'Transport of user groups', 'Transport of InfoSets', 'Transport of InfoSets and queries' and 'Transport of queries'. You must choose exactly one of these transport types.
In each case, you can also define an import option depending on the transport type. This allows you to determine how the transport dataset is inserted in the table AQDB of the target client during a later import.
The import options, each of which has an abbreviated syntax,
are as follows:
REPLACE or R
MERGE    or M
GROUP=ug or G=ug    (ug = name of a user group)
UNASSIGN or U
If you use the transport type 'Transport of user groups', all user groups are transported according to the select option 'user groups' and the selected import option. The import options REPLACE and MERGE are allowed.
If you use the transport type 'Transport of InfoSets', all InfoSets are transported according to the select option 'InfoSet' and the selected import option. The import options REPLACE, MERGE, GROUP=ug and UNASSIGN are allowed.
If you select the transport type 'Transport of InfoSets and queries', all InfoSets are transported according to the select option 'InfoSets' and the selected import option. The import options REPLACE and MERGE are allowed. Also, all queries are transported for each functional area selected, according to the select option 'queries'. In this case, the user groups of the queries are irrelevant and only the import option REPLACE is allowed.
This transport type allows you to transport a modified InfoSet and all the associated queries.
For the transport type 'Transport of queries', all queries are transported according to the select option 'User groups' and the select option 'Queries' as well as the selected import option. The import options REPLACE and GROUP=ug are allowed.
The export log displays which user groups, which InfoSets and which queries are transported, as well as the import options used.
Transporting a user group
Transporting a user group means transporting all members of the group from the source client. However, the InfoSet assignment to the user group in the source client is NOT transported.
The import option REPLACE first deletes all members of the group in the target client and then enters the members from the source client.
The import option MERGE leaves all members of the group assigned in the target client and adds the members of the group from the source client.
Entering a new member in a user group in the target client is possible only if a user master record exists.
In the target client, the assignment of InfoSets to this user group remains.
Transporting an InfoSet
Transporting an InfoSet means transporting the InfoSet and the InfoSet assignment to user groups in the source client.
Importing an InfoSet is possible only if the same logical database exists in the target client. Extensive checking is also performed to ensure that there are no inconsistencies between the InfoSet and the logical database.
The import option REPLACE first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries dependent on the InfoSet. The InfoSet is then transported to the target client and the assignment of the InfoSet to user groups is copied from the source client, if user groups also exist in the target client.
The import option GROUP=ug first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client and assigned to the user group ug of the target client, if such a user group exists.
The import option MERGE leaves the assignment of the InfoSet to user groups in the target client and transports it to the target client. It then copies the assignment of the InfoSet to user groups from the source client if user groups also exist in the target client.
The import option UNASSIGN first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client. No assignment of the InfoSet to user groups is performed.
Transporting a query
Transporting a query means only the query itself is transported.
Importing a query is possible only if a corresponding user group (see below) and a corresponding InfoSet exist in the target client and if the InfoSet is assigned to the user group. To demonstrate the effect of the import options, suppose that the query has the name QU and belongs to the user group BQ in the source client.
The import option REPLACE overwrites the query QU of the user group BQ in the target client if the user group exists.
The import option GROUP=ug overwrites the query QU of the user group UG in the target client if the user group exists. In this case, the query is explicitly assigned to a user group in the target client. This target user group may be differnet from the user group in the source client.
Transport action IMPO (imports)
If you choose the 'Test only' parameter with imports, only a test import is performed. This means that the system performs checks as for a real import and generates an import log. The import log contains information on the locks that have to be set. With a test import, you can check whether a transport dataset can be imported without any problem and which changes it would make in the table AQDB of the target client. A test import itself never makes changes in the table AQDB of the target client.
All transport datasets are imported according to the select option 'transport request'. In this case, the system outputs a detailed log of all checks carried out and all changes made in the table AQDB.
If you select the parameter 'Delete after successful import', the transport dataset in the table TAQTS is deleted after the import of each transport dataset if no errors occur during the import.
Transport action SHOW (display)
All transport datasets included in the transport table TAQTS are output with name (also the name of the transport request) and contents in the form of an overview.
Transport action DELE (delete)
All transport datasets are deleted according to the select option 'transport request'. To avoid unintentional deletion, the select option 'transport request' must contain values, meaning that the transport action DELE is not performed if this select option is empty.
Transport of ABAP Query
I am involved in this upgrade project to 4.7
The users are not able to find any reports (in QA System) which were there before the upgrade in SQ01. But they can see them in production which is not yet upgraded. They want me to copy all the reports to the QA system now....I dont have any idea how to do that.
I remember a similar problem upgrading to 4.6C from 4.5B ......
Take a look at OOS note 672784.
You can transport queries between systems in SQ02 (hit the lorry button) or run program RSAQR3TR.
You download the infosets, queries etc into a file and load them into whichever system you wish.
Just wanted to share my experience of transporting queries:
I needed to move a user group, 2 infosets and 3 queries from a 4.6 system to a 4.7 system.
When I tried doing this via the SQ* transactions I did not get the import/export option, so instead ran RSAQR3TR.
Step 1. Run RSAQR3TR in 'old' system. Select EXPORT and specify the objects to be transported.
(System includes these in an automatically created transport request)
Step 2. Release this transport and request it be transported to 'new' system.
(This results in the entries being populated in transport table AQTDB in 'new' system).
Step 3. Run RSAQR3TR in 'new' system. Select IMPORT and tick the Overwrite checkbox. Specify the transport number in the field labelled 'dataset with imports'.
(RSAQR3TR gives the message that stuff has been imported OK).
Step 4. In my example I still couldn't find the queries, so ran RSAQR3TR one more time, this time specifying 'Copy Standard Area -> Global Area'.
(Now my queries etc were available in new system).
Perhaps there are better ways, but after 1.5 days of struggling I was glad to get this far.
regards,
Jai

Adobe Bridge shortcut button missing in PS CS6 menu bar, how to install as in PS CS5 [essentials]

Adobe Bridge shortcut button missing in PS CS6 menu bar, how to install as in PS CS5 [essentials]

Yes, Bridge shortcut has been removed from PS CS5. However, you can go to File->Browse in Bridge option to open the file in Br CS6.
Similar query has been answered here.
http://forums.adobe.com/message/4285441

Wrong sequence in selection screen generated by ABAP Query

Hi,
I am developing a query to display the data in the view.
My query has 8 selection fields totally.
As part of my requirement I have added selection parameter in the
selections tab of the infoset and maintained the sequence as 9.
Inspite of maintaining the sequence number as 9 in the infoset, It is
appearing first in the selection screen of the query.
I tried putting different numbers in the sequence number, but even it
is appearing first in the selection screen.
Can you please let me know how to display the selections declared in
the infoset as per the sequence required.
Thanks,
Madhuri.

Actually what happen when you declare your own fields in ABAP query . you have to care about the sequence . As an example if youre selecting lets say state name , you have two variables
1-state
2- land
for state you have to select land first , if your state is first and land is 2nd it gave you the error of sequence .
Because you have to get data in land first in order to get state specific to the land .
it should be
1-Land
2-State
Just see the your fields , Im sure youre missing that .
You can also see the NO ( field ) in Query ( Sq03 ) . where you can define the seqence on selection.
hope thisll help you .
Pl...Award the points .
Thanks
Saquib
Message was edited by: Saquib Khan

How to hide some fields in ABAP Query

Hi,
My ABAP Query has a long list of extracted fields. I wanted to set some of these output to "HIDE".
This allow User the flexibility to decide what fields to show.
How can I set the field to "HIDE" in my query?
Thanks
bye

Hi Tim,
You can do this by setting the Report layout variant in following steps:
1. First define the parameter on selection screent for report variant.
2. Data decelaration for variant.
3. Value request to get already present variants on report:
4. If doesn't choose the layout take out the default report layout.
5. Initialize the report variant.
6. Apply the variant to the REUSE_ALV_GRID_DISPLAY funtion module.
 Here to generate report variant first to open report output and then as per according to user set the layout of report using the layout icon of ALV with summation on value fields (as required) and create layout name.
*Data Deceleration as below:
Data :g_save(1) TYPE c,
** g_default(1) TYPE c,
g_exit(1) TYPE c,
gx_variant TYPE disvariant,
g_variant TYPE disvariant.
*First Define the parameter to give layout of Report variant.
SELECTION-SCREEN BEGIN OF BLOCK 3 WITH FRAME TITLE text-003.
PARAMETERS: p_vari TYPE disvariant-variant.
SELECTION-SCREEN END OF BLOCK 3.
* Process on value request
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_vari.
PERFORM f4_for_variant.
* Selection-Screen Checking
AT SELECTION-SCREEN.
PERFORM pai_of_selection_screen.
INITIALIZATION.
w_repid = sy-repid.
PERFORM variant_init.
* Get default variant
gx_variant = g_variant.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
EXPORTING
i_save = g_save
CHANGING
cs_variant = gx_variant
EXCEPTIONS
not_found = 2.
IF sy-subrc = 0.
p_vari = gx_variant-variant.
ENDIF.
FORM f4_for_variant .
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
EXPORTING
is_variant = g_variant
i_save = g_save
IMPORTING
e_exit = g_exit
es_variant = gx_variant
EXCEPTIONS
not_found = 2.
IF sy-subrc = 2.
MESSAGE ID sy-msgid TYPE 'S' NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
** ELSE.
** IF g_exit = space.
** ENDIF.
ENDIF.
ENDFORM. " f4_for_variant
FORM pai_of_selection_screen .
IF NOT p_vari IS INITIAL.
MOVE g_variant TO gx_variant.
MOVE p_vari TO gx_variant-variant.
CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
EXPORTING
i_save = g_save
CHANGING
cs_variant = gx_variant.
g_variant = gx_variant.
ELSE.
PERFORM variant_init.
ENDIF.
ENDFORM. " pai_of_selection_screen
FORM variant_init .
CLEAR g_variant.
g_variant-report = w_repid.
ENDFORM. " variant_init
**While Showing report pass the variant :::
g_save = 'A'.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = w_repid
i_structure_name = 'IT_MAIN'
is_layout = i_layout
is_print = i_print
it_fieldcat = i_fieldcat[]
it_events = i_events[]
i_save = g_save
is_variant = g_variant
TABLES
t_outtab = it_main
EXCEPTIONS
program_error = 1
OTHERS = 2.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Many Thanks / Himanshu Gupta

How to set default value in select option for ABAP query

Hi experts,
What is the way to set up default values for select-options in ABAP query.
e.g.
I have one field 'Year' in my ABAP query selection screen.
I want value of current year to be appeared here whenever user execute report
Thanks in Advance
-Harkamal

Hi Harkamal,
execute your Query via SQ01. On Selection-Screen
goto save Variant. Mark your field
as selection variable an press Button election variable.
Take variable from TVARV and use it.
Than save the Variant.
Look at TVARV if the 'Year' is updated to the actualYear!
regards, Dieter

Getting error while assigning ABAP Query to Tr.Code

Hi Guys,
There is a problem iam facing with ABAP query while transporting which need to solved asap. It will very greatfull if u guys can resolve this problem.
My problem is, I created one ABAP Query with Name ASSETOVERVIEW. I had transported this even, now when iam going to assign it to one transaction code with se93 lets say ZAOR. I need to give its description and program name in se93 right. now my question is what is program name i need to give in se93. Bcoz in SQ01 where i created the query, there is no name as 'program name' rather there is 'Name' in that we will create the query name i.e, ASSETOVERVIEW. In se93 u give tr.code and when u see down there will be radiobuttons in 'start object',in that i had checked program and selection screen (report transaction) is this right button i had checked or any other i need to check?. I had assigned this name i.e,ASSETOVERVIEW and development class and then when i check the name for syntax check its giving "'ASSETOVERVIEW' does not exist". I don't understand what program name i need to give.
If u guys can help me out with this problem it will be very much appreciable and definetly can get the reward points.
Thanks for as usual help in advance.
Regards.

Hi omer,
1. Just run the query.
2. one selection screen will come
3. then using SYSTEM---->STATUS, (from menu)
look for the program name
4. the program name will be something wired foramt.
/asdfasdf/asdfdas etc.
5. Give that name in se93.
regards,
amit m.

Creation of local field in ABAP Query

Hi
Please let me know how to create a local field in ABAP query. I am finding the option inactive in SQ01.
Regards
Priyadarshini

hi priya,
     *__Adding u201CLocal Fieldu201D (user defined field) in SAP Query_ :
There is also facility to add the user defined fields in SAP query output. Also we can provide calculation formula for calculating values for this user defined field.
Calculation formula consists of standard fields from standard SAP tables. So the values fetched for particular standard SAP fields from standard SAP tables get calculated as per the calculation formula defined for the user defined field and displays the value accordingly.
To do this first go to change mode for Query which automatically takes you to screen shown below and click on icon   , as below :
Then further screen will appears. So select the Field group and again click on the same icon button   .
Then switch on the Short names for the fields and give the short names to fields which we need to use in Calculation formula.
Give the short names and then created u201CLocal Fieldu201D, as shown in below screen shot. Also Short names are given to fields, which can be used further for calculation.
Defining Local Field u201CREM_QTYu201D along with its field type and Calculation formula.
In this case we have
defined field type for new
field as similar to
ORD_QTY and
Calculation formula is
defined.
Also its possible to have Conditional logic for Local field by putting Condition in u201CConditionu201D line.
Now activate this newly added Local field for coming it in output screen. To do the same again go to u201CBasic Listu201D and activate the Local Field as shown below :
i think this will help u
regards,
sindhu.

PNPCE in ABAP Query(SQ01) Selection is not working completely

Hi All,
I have developed an ABAP query using LDB PNPCE. I am reading data from IT000,IT0001 etc . I test the query in QA and I noticed that the PNCPCE screen doesnt care about the selection in query. Like I have given the date range in PNCPE default screen. But its not filtering that data at all. It pulling up the employees regardless of date, it behaves the same for field action type (P0000-MASSn). The surprising thing is that for company code its working fine. My question is that Why PNPCE standard screen-selection not filtering data in ABAP query.
Did any one of you also experience that?
FYI
I also find an OSS note # 730005 but we are already on 52 Patch !!
OSS note :PNPCE: Incorrect data of infotype 0000 and 0001
Symptom
When you carry out a reprot which is based on logical database PNPCE, errors occur during the processing of infotypes 0000 and 0001.
Other terms
PNPCE, AS PERSON, P0000, P0001, data selection period, person selection period, CHECK_IT_0000_DATA_RESTRICTED, CHECK_IT_0001_DATA_RESTRICTED
Reason and Prerequisites
You start a report which is based on logical database PNPCE. In the report, infotype 0000 or 0001 is processed (that is, it was declared via the INFOTYPES statement). At event 'GET GROUP' or 'GET PERAS', the system either returns too few data records in the infotype tables or it returns data records twice.
The error (missing data records) has only occured since the implementation of Note 687004 or the import of Support Package SAPKE47028.
Solution
Implement the attached corrections. or import the corresponding Support Package.
Thanks,
Saquib Khan

Hi Saquib,
Recently i am facing the same issue can u pls do reply how you have overcome this issue..The data is not getting picked up at the right time it is lately picked up by the program . Earlier it was PNP and it has been changed to PNPCE also we had implemented OSS Note 687004 and the later's Notes were also implemented but still now we are unable to track down why there is delay in picking up the records this has been happening for the past 8-10 Months(i m not sure far more before). I am finding 2 main issues,
1. we are using GET peras in PNPCE and no other event after that may be this is not fetching all the data because my selection screen does contain PERSONID where i suppose there should be GET PERSON event to define it
2. RP_READ_INFOTYPE macro while using for P0000 ,, the code in the macro is such that it fetches using P0001 also ...I suppose if there are any inconsistency between IT0 and IT1 then this might one to take care ...
kindly let me know how you have approached to resolve this issue.

PNPCE in ABAP Query !!! Slection is not working completely

Hi
I have developed an ABAP query using LDB PNPCE. I am reading data from IT000,IT0001 etc . I test the query in QA and I noticed that the PNCPCE screen doesnt care about the selection in query. Like I have given the date range in PNCPE default screen. But its not filtering that data at all. It pulling up the employees regardless of date, it behaves the same for field action type (P0000-MASSn). The surprising thing is that for company code its working fine. My question is that Why PNPCE standard screen-selection not filtering data in ABAP query.
Did any one of you also experience that?

FYI
I also find an OSS note # 730005 but we are already on 52 Patch !!
OSS note :PNPCE: Incorrect data of infotype 0000 and 0001
Symptom
When you carry out a reprot which is based on logical database PNPCE, errors occur during the processing of infotypes 0000 and 0001.
Other terms
PNPCE, AS PERSON, P0000, P0001, data selection period, person selection period, CHECK_IT_0000_DATA_RESTRICTED, CHECK_IT_0001_DATA_RESTRICTED
Reason and Prerequisites
You start a report which is based on logical database PNPCE. In the report, infotype 0000 or 0001 is processed (that is, it was declared via the INFOTYPES statement). At event 'GET GROUP' or 'GET PERAS', the system either returns too few data records in the infotype tables or it returns data records twice.
The error (missing data records) has only occured since the implementation of Note 687004 or the import of Support Package SAPKE47028.
Solution
Implement the attached corrections. or import the corresponding Support Package.
Thanks
Saquib Khan

Hi Saquib,
Recently i am facing the same issue can u pls do reply how you have overcome this issue..The data is not getting picked up at the right time it is lately picked up by the program . Earlier it was PNP and it has been changed to PNPCE also we had implemented OSS Note 687004 and the later's Notes were also implemented but still now we are unable to track down why there is delay in picking up the records this has been happening for the past 8-10 Months(i m not sure far more before). I am finding 2 main issues,
1. we are using GET peras in PNPCE and no other event after that may be this is not fetching all the data because my selection screen does contain PERSONID where i suppose there should be GET PERSON event to define it
2. RP_READ_INFOTYPE macro while using for P0000 ,, the code in the macro is such that it fetches using P0001 also ...I suppose if there are any inconsistency between IT0 and IT1 then this might one to take care ...
kindly let me know how you have approached to resolve this issue.

ABAP Query error

Hello! can anyone help pls?
I am in the process of constructing an ABAP query and I'm getting an error message which is quite puzzling. Here's the details:
I'm creating the query using an infoset constructed from logical database VAV. When I try to add field VBUP-GBSTA to my basic list design, I get the following error:
"You placed fields from different parallel branches of the hierarchical data source in the same line. . This makes no sense. The list will not be displayed as you desire. . List is only displayed in simple format for correction purposes. . Please check the sequence. Button allows you to color list fields according to the hierarchy. "
I don't know why this is the case, and I really need to report on that field. Any ideas would be most appreciated!
Thanks in advance!

Hello Elizabeth,
I hope you have selected VBUP also in the hierarchy in the infoset. If this is selected and the field which you are looking for (GBSTA) is assigned to a field group, then u should be able to select this in the basic list.
Hope this helps
Abhijit

ABAP Query Selection screen

Hi,
I have an existing ABAP Query, my req is to add new Radio buttions block after the current seelction paramertes.
i created radiobuttons in SQ02 infoset query with radiobuttons but when i run the report, selections screen has radio buttons first and then previous selection criteria fields displaying...
my req is first previous selection fields then radio buttons.
how to change the sequence of the fields in selection screen?
and based on the radio buttons, i need to filter the output data...
in which event i have to write the code?
Thanks
Giri

Sudheer,
it is ABAP Query report... from SQ02... i cant modify those in SE38...
current selection parameters are from table fields selected in SQ01 Query.... and radio buttons are in SQ02 Infoset.
Giri

ABAP Query Selection screen parameters

I need to add an additional selection screen parameter in existing ABAP Query. How to modify the selection screen fields in existing ABAP query ? Kindly help me.

Hi,
GO to info set transaction SQ02
Give the infoset
Press change
Press the selections button..Shift F7
In the right hand side you will get a table control to enter the selection screen parameters..
Press create button on top of the table control to create new parameters
Thanks,
Naren

Summation button missing in abap query ..

Similar Messages

Maybe you are looking for