SAP Logistics

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th

There is a common requirement from functional consultants on how to do debugging. Below is the raw info on the debugging and different ways of doing it. Debugging is a common tool used by the technical team to analyze dumps during transactional processing and program behavior. Through debugging we will come to know the run values of the program as well. Debugging can be performed in two different ways : 1. Debugging by watchpoint 2. Debugging by Breakpoint Debugging based on watchpoint At times, we are unsure about how the value is getting determined for a variable then we can put the watchpoint on the variable deriving the value so that the system will stop at all points where the value is being fetched for the variable. Debugging based on Breakpoint Debugging based on break point will be done only when the consultant is aware of the exact piece of code where a breakpoint can be enabled. The breakpoint can be done in two ways. Internal breakpoint External b