Comments for SAP Tricks | SAP Tips & Tricks | SAP Basis & Applications | SAP Solutions

Comment on Mass change of Sales orders in VA05 by Felix

Felix — Fri, 18 May 2012 03:41:39 +0000

Hi All,
I have an issue with VA05. For some of the users, the output is displayed in ALV Grid and for some users it is displayed in ALV LIST. Why is that happening? Does this have anything to do with user profile settings? If not, how can I make it to display in ALV Grid for all the users?

Comment on Find a BADI by BADI’s in 5 Minutes | SAP Tricks | SAP Tips & Tricks | SAP Basis & Applications | SAP Solutions

Mon, 14 May 2012 03:15:13 +0000

[...] you can find out the BADI name by following this post: http://saptricks.com/2438/find-a-badi Read more from ABAP, BADi, Cross App, Custom ABAP, Interfaces, SAP Technical, SAP Tips ABAP, [...]

Comment on CRM – Bdoc Analysis Guide by Alex

Alex — Wed, 09 May 2012 05:08:52 +0000

Very good presentation!
Thank you for sharing this information.

Comment on LIS SIS Update Analysis by admin

admin — Fri, 04 May 2012 03:42:18 +0000

Thanks for the feedback Kiran – glad you liked it.

Comment on LIS SIS Update Analysis by kiran

kiran — Thu, 03 May 2012 15:36:27 +0000

Excellent post

Comment on SAP Tips – Debugging technique by admin

admin — Thu, 03 May 2012 07:54:28 +0000

Hi Robin,

Thanks for the tip, it is a good idea to set a break-point at the beginning of the form or Function module which calls the message. Funnily I used to only set it at the message and then read backwards….painful.

Comment on SAP Tips – Debugging technique by Robin Ferali

Robin Ferali — Thu, 03 May 2012 02:33:19 +0000

Hello Glynn,

to go faster to determine reason of an error message, i proceed as follow:
1) transaction /h
2) I set a breakpoint for the statement “message” to have the program stopped at each messages. once I stop on my error message, I set a manual breakpoint at the begining on the form or module function and relaunch the program
3) I look for the reason of the error with F5.

You can check as well the Call and/or Overview screen to see what were some values upstream and set breakpoints.
So many things we can do to debug a program…

Comment on Table Edit without SM30 or Maintenance Dialog by Robin Ferali

Robin Ferali — Thu, 03 May 2012 01:41:04 +0000

Indeed, all modification done within SE16N are traced in table SE16N_CD_DATA & SE16N_CD_KEY.
It is not the case if you modify the table with Transaction SE16.

I do agree with Glynn and Sapguy, because of the dependencies we need to be careful when we modify any table.
More, by modifying customizing table in a system you will loose the consistency between the different system.

Cheers
Robin

Comment on Find a BADI by Sundar Raghuraman

Sundar Raghuraman — Sat, 21 Apr 2012 23:12:25 +0000

A Very useful Tip. Thanks a lot to the contributor.

Comment on SAP Solution Manager – Bullet Point Overview by Niall Pithey

Niall Pithey — Thu, 19 Apr 2012 17:10:06 +0000

Liked this one : SAP Note 1605780 – Remove “Copy From” in title for copied documents.
When copying a document in Solution Manager, the original title gets “Copy From” as a prefix for the new title. When the length of a document title approaches the limit of 64 characters, relevant parts at the end can get truncated by putting the prefix at the beginning.
This correction avoids the prefix and thus keeps the original title for the copied document.

Solution
Correction Instructions:1351507