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.

Similar Messages

I changed an existing abap query ME80FN but not find in production system.

Hi,
I have changed an ABAP QUERY ME80FN for user group SAPQUERY/ME in Dev system via transaction SQ01 & SQ02.
But when I am searching for same query in Production via transaction SQ01 it is not existing.
Please give me some inputs.
Thanks,
Jwala

Hi Jwala
1. Check if that ABAP query is transported to production or not.
or
check the versions of the ABAP Query in dev w.r.t Production so that you will know the status of the program in production.
regards
PBI

ABAP Query Execution via Custom Transaction Code - Not working

We have created an ABAP Query in our DEV client and we then created a transaction code to run that query. We have done this because the customer does not want anyone to have access to SQ01, SQ02 in production. This works great in DEV but we can not get it to work in production.
The ABAP Query was exported to our Prod client successfully. I say exported because you do not do direct transports with queries.
We then transported the new transaction code to run the query to production and it was successful.
However, when we run the transaction is production we get a sys dump stating it can not find the query.
We believe the problem is the TRDIR table is missing an entry for the program in production (it has an entry in DEV).
I would have thought that the export on the query would have brought in this entry -but obviously not.
Any suggestions on how we can get this entry into the production client? Did we miss a step on the export that would do this? We want to only bring over this entry - not the entire TRDIR table for obvious reasons (size (1.5 million entries, programs not ready for production, etc.).
Please help!
Thanks.
Scott

Hi,
The above solution will work if you assign the transaction in one server, If you want this will not work in quality/production boxes when transported the query..the program name will not be the same in all the servers...
For this. Do the below:
In SE93, Create a Paramter Transaction
-> Transaction = Start_report
-> In default values, give the below details:
     D_SREPOVARI-REPORTTYPE = AQ
     D_SREPOVARI-EXTDREPORT = Name of the Query
     D_SREPOVARI-REPORT = User Group
Save the transaction..Now if the program is generated with different names in the quality/proudction, this will still work..
Regards
Vijay Hebbal

Transporting an ABAP QUERY

Hi guys/gals,
I've created an abap query in testing client.
May I know how to transport the ABAP query into quality and production server??
Regards
Jiku

Hi Jiku,
Transaction SQ02 menu "Envrionment/transport" (=Ctrl+F3).
For transport, select "export" and the objects you want to transport.
This will generate a request which you'll be able to process normally.
An other solution is to download your object from the source system and then to upload it from your target system, if this one is open (and if you have the requested rights).
Reward if useful.
Regards,
Aneesh.

Transport of ABAP query to production server

Hi!
I have developed a report with ABAP query in development server with transaction codes SQ01, SQ02 AND SQ03 respectively.
I also got the program name from SQ01.
Now , how to attach a transaction code with the program that is generated from ABAP query and transport it to production server
successfully.
If the program is attached directly to the tr code through SE93 and transported----- program is not found in the pr. server.
pls help me out , requirement is very urgent.
points to be rewarded .
regards
Amit

hi amit,
if i understood correctly.is ur query and infoset transported or imported to production.
Regards,
sudheer

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

Creating t.code for ABAP query and Transport it TO Production and run it .

Hi Friends
Thanks for ur reply ,
The requirement is that i want to create tcode for abap query and that query can be regenearted ,
in case of regeneration programe name i got answer programame name will be change, i created and modified query but i saw the same programe name ,,, may be it changed when it is trasnported if so then what ??
and also pls give me solution for asiging tcode for query which is going to be regenerated.
thanks and regards
farukh

Dear Farukh,
As we know,
Query is created in Production server and a corresponding program is generated by System.
What we have to do is just to assign the program to the desired transaction code in Development server and transport it.
If you have any doubts please let me know.
Kindly assign points if you find this info usefull.
Regards,
Lijo Joseph

Transports, M version of query element missing in Dev

Hello
We're trying to import transports to a system copy of our Development system but when trying to do so we get an error in RS_AFTER_IMPORT saying "Element XYZ is missing in version M". (The transports comes form Dev). The element is a Text-variable
When checking in table RSZELTDIR in Dev-Copy I do only see A and D versions of the element XYZ. The same is true in Dev. But in QUA and PROD the element exists in A, D and M versions.
Is this normal? And how do we do if the transport strategy is to Transport between Dev and Dev-Copy?
Thanks in advance
/ Daniel

Thank you for your answer.
However the same transport has entered QA and PROD correctly, it's only when transporting into Dev-Copy that it fails.
Scenario :
Day 1 : a system copy was taken
Day 2-10 : transports leaving Dev going to QA and PROD
Day 11 : Dev-Copy created from the system copy from Day 1
Day 12: The transports from Day 2-10 is being imported into Dev-Copy (and Query transports failing)
So the developers have collected needed objects in the first place, but something is happening when importing into Dev-Copy..... the M versions is missing in Dev-Copy (and Dev) compared to QA and PROD
/ Daniel

Creting t.code for ABAP query and Transport it TO Production and run it .

Hi Friends
Thanks for ur reply ,
The requirement is that i want to create tcode for abap query and that query can be regenearted ,
in case of regeneration programe name i got answer programame name will be change, i created and modified query but i saw the same programe name ,,, may be it changed when it is trasnported if so then what ??
and also pls give me solution for asiging tcode for query which is going to be regenerated.
thanks and regards
farukh

Hi farukh,
1. If any query is re-generatred,
   then some MANUAL INTERVENTION
   is absolutely required.
2. Hence, what we prefer is this :
   1. Generate first query.
   2. Copy the code to a Z Program
   3. Attach tcode to THIS z program.
   4. Transport
3. Now,
whener the query is generated again,
   AGAIN COPY THE CODE
TO OUR Z PROGRAM (2ND STEP ABOVE)
                    (which has already been created)
AND TRANSPORT JUST THIS Z PROGRAM.
REST WILL TAKE CARE OF ITSELF.
4. In such cases,
ONLY COPY-PASTE IS REQUIRED.
(and it takes not more than 15 SECONDS)
regards,
amit m.

ABAP query transport issue

Hi,
   I have copied an abap query ZGA to ZGA_IND1 and changed the title to INDIA. I gave transport number and released and transported to Quality. A transaction has been assigned to this Query
But when I execute this query from Quality machine using transaction, it says program AQZZZGA=========ZGA_IND1======   is missing.
   Transaction code is transported but not the ABAP query program. I retransported and failed couple of times.
Not sure why underlying program is not transpoorted to Quality.
Any idea, what I am missing here.
Cheers.
Sudhaker

hi,
I guess the transaction code directly calls the generated ABAP program, which is the bad approach, because the generated ABAP program might have different names in different systems (like here). You have to create a transaction, which calls transaction START_REPORT with the following parameters/attributes filled :
D_SREPOVARI-REPORTTYPE= AQ "parameter indicating Abap Query
D_SREPOVARI-REPORT= '...' "Query User group
D_SREPOVARI-EXTDREPORT= '...' "Query name
Of course you have to replace the dots with real usergoup and query names. You create this transaction code in the development system and transport it to test and production. It will work everywhere (in case the query is transported as well).
hope this helps
ec

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

Can we change the ABAP QUERY exists in Global area

Hi All,
I have a requirement to add new column in the ABAP query in layout for that I am changing a ABAP query ME80FN which is calling infoset /SAPQUERY/ME80FN defined in the global area ( Environment->query areas->global area).
1) Can I change this infoset and query
or
2) Do I need to follow any other steps.
If I change the existing query in DEV can I transport this to production.
Please clarify.
Thanks,
Jwala

Yes. We can change the background of an input field. The way you do this is by editing the theme that webdynpro application uses. To edit the theme, you will need to install NWDS PLUS the theme edit plugin (Available for download from SAP).
Once you have edited the theme, you will need to upload your theme back to application server. You can use the program : BSP_UPDATE_MIMEREPOS to do this.
Bydefault, the theme used by webdynpro applications is :
/SAP/PUBLIC/BC/UR/nw5/themes/sap_tradeshow
You can apply another theme by calling the webdynpro application with a theme parameter. For example, if my webdynpro application name is "zgopaltest", then
http://<server>:port/sap/bc/webdynpro/sap/zgopaltest?SAP-EP-THEMEROOT=/SAP/PUBLIC/BC/UR/nw5/themes/sap_tradeshow
will apply the sap_tradeshow theme.
Likewise, you can apply diffrent theme. There is another theme that SAP provides. Its called : sap_hcb. Hence, you can apply the theme to the above application by:
http://<server>:port/sap/bc/webdynpro/sap/zgopaltest?SAP-EP-THEMEROOT=/SAP/PUBLIC/BC/UR/nw5/themes/sap_hcb

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

A few Questions on ABAP Query

Hi Guru's
I would like to ask some questions on ABAP query.
1. Can you transport abab queries? Should it only be Global or you can also transport Standard Areas?
2. Once transported, am i able to change query?
Thanks,
Jograd

hi....
you can transport a quary but for that the quary should be an object itself or attached to some object
and
if once transported to production....you cannot change it there and for changing you have to get it in developement sysytem and then make any change.
regards

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.

Abap Query missing in Dev & Production

Similar Messages

Maybe you are looking for