-
Products and Technology
By Category
-
Groups
Activity Groups
Industry Groups
Influence and Feedback Groups
Interest Groups
Location Groups
Customer Only Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
Products
Learning and Support
-
- Products and Technology
- Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
- Explore SAP
-
Products
- Products
- SAP Business Suite
- Artificial Intelligence
- Business applications
- Data and analytics
- Technology Platform
- Financial Management
- Spend Management
- Supply Chain Management
- Human Capital Management
- Customer Experience
- SAP Business Network
- View products A-Z
- View industries
- Try SAP
- Partners
- Services
- Learning and Support
- About
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
ABAP queries
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2008 May 15 4:32 PM
- SAP Managed Tags
- ABAP Development
Hi All,
Iam trying to move an ABAP query to the Production client from the dev client. It gives me a short dump when i run the transaction code assigned to the query . Is there a specific method to move a query transport to Production
Kindly let me know
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2008 May 15 4:39 PM
- SAP Managed Tags
- ABAP Development
This is because you assigned transaction code to the query directly (with the name of dynamicaly generated report name) and it is incorrect. In your production client the system has generated another report for the query and given it the new name.
NEVER assign transaction name to a generated SAP Query report. To do it in the correct way you should better update some user role via PFCG.
Was the query itself in a transport? i.e. saved in a request via SQ02? If so, it must be imported in the target system by the same method. If not, you do need to export it by that method.
If you have done that and your transaction is a parameter transaction or a straight program name where the client is the same in both dev and prod, the most likely answeris simply that you need to generate the program. Easiest fix is to execute the query in SQ01 once, then the transaction should work thereafter.
Reward if helpfull...
Cheers,
Venkoji Babu,.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2008 May 15 4:35 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2008 May 15 4:39 PM
- SAP Managed Tags
- ABAP Development
This is because you assigned transaction code to the query directly (with the name of dynamicaly generated report name) and it is incorrect. In your production client the system has generated another report for the query and given it the new name.
NEVER assign transaction name to a generated SAP Query report. To do it in the correct way you should better update some user role via PFCG.
Was the query itself in a transport? i.e. saved in a request via SQ02? If so, it must be imported in the target system by the same method. If not, you do need to export it by that method.
If you have done that and your transaction is a parameter transaction or a straight program name where the client is the same in both dev and prod, the most likely answeris simply that you need to generate the program. Easiest fix is to execute the query in SQ01 once, then the transaction should work thereafter.
Reward if helpfull...
Cheers,
Venkoji Babu,.
Bluesky