-
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
- Autonomous Enterprise
- Artificial intelligence
- Data and analytics
- Autonomous Suite
- Technology platform
- Transformation management
- Midsize business solutions
- Financial management
- Spend management
- Supply chain management
- Human capital management
- Customer experience
- Enterprise resource planning
- Business network
- Sustainability management
- SAP Store
- Try SAP
- View all industries
- Partners
- Services
Learning and Support
-
- Products and Technology
- Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
- Explore SAP
-
Products
- Products
- Autonomous Enterprise
- Artificial intelligence
- Data and analytics
- Autonomous Suite
- Technology platform
- Transformation management
- Midsize business solutions
- Financial management
- Spend management
- Supply chain management
- Human capital management
- Customer experience
- Enterprise resource planning
- Business network
- Sustainability management
- SAP Store
- Try SAP
- View all industries
- Partners
- Services
- Learning and Support
- About
- SAP Community
- Groups
- Interest Groups
- Application Development and Automation
- Discussions
- Re: Entering in debugging mode
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Entering in debugging mode
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2008 Jul 28 3:24 PM
- SAP Managed Tags
- ABAP Development
Hello
I'm experiencing the following issue :
Iw32 is called by a call transaction in a customer program. In the process, a standard function (pm_partner_update)
ends with an abap runtime error SAPSQL_ARRAY_INSERT_DUPREC.
Instead of the short dump report, the enduser is entering in debugging mode, with the cursor placed on the failed command. Although he cannot do anything because
he has no debugging authorizations, is it possible to prevent the debug screen display?
Regards,
Philippe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2008 Jul 28 3:27 PM
- SAP Managed Tags
- ABAP Development
The error is due to the Number range problem.
Please check the Number range for the Order in SNRO.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2008 Jul 28 3:27 PM
- SAP Managed Tags
- ABAP Development
The error is due to the Number range problem.
Please check the Number range for the Order in SNRO.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2008 Jul 28 3:30 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2008 Jul 28 3:41 PM
- SAP Managed Tags
- ABAP Development
We effectively found inconsistencies with the order.
Corrected, the program is running well.
I wanted to know why and enduser with no debugging
authorizations entered in debug mode and if it's possible to prevent entering in debug mode
Regards,
Philippe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2008 Jul 28 4:14 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2008 Jul 28 4:08 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2008 Jul 29 8:04 AM
- SAP Managed Tags
- ABAP Development
The enduser have not the s_develop authorization. He enters in debugging mode after an abap runtime error on an insert operation. As he has no authorization, the only way to leave this mode is entering /nex in the command field.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2008 Jul 29 9:20 AM
- SAP Managed Tags
- ABAP Development
Hi,
Normally in Production systems, no one will have access to enter into Debugging mode even after any short dump. Even if any one has that type of access, you can check with Security team, so that they can remove those authorizations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2010 Mar 04 2:01 PM
- SAP Managed Tags
- ABAP Development
Hi Philipe,
I have the same abap runtime error SAPSQL_ARRAY_INSERT_DUPREC for the FM pm_partner_update but in the short dump report
Please, how did you solve the issue?
I appreaciate your help!
Regards,
Ari
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2010 May 03 7:35 AM
- SAP Managed Tags
- ABAP Development
we need to pass all the three key fields of IHPA table to avoid this duplicate entry error as it gets generated when you try to update duplicate records to master table . In my case i used I_count parameter of ihpa table to increament the counter . In each case if we do not use counters in that case it is bound to give you exception .so make sure you are not updating any duplicate entry .
Bluesky