Skip to main content

How to change records in SAP using debug mode

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 the table contents.

if we are required to Create or Delete entry then we have enter 'INSR' or 'DELE' instead of 'EDIT' as we do now.




After changing the Code entry to 'EDIT' click on enter and execute. The below screen with table entries enabled for changing will be displayed.


Change the required entry and click on save.



Case 2: Transaction Code SE16N

In this case, I have taken a sample example to update the VBAP table entry through debug mode.



Enter sample sales order for which data need to be edited


enter '/H' in the command bar and click on enter or OK button. Then the message with 'Debugging mode will be switched on' will be displayed. Click on enter again to enter into debugging screen


Similar to field 'CODE' in SE16 screen we are required to amend 'GD-SAPEDIT' and 'GD-EDIT' field to enable the change.

Click on GD-VARIANT field and change it to 'GD-SAPEDIT' and 'GD-EDIT' initial values of both will be  blank



Change the values of both variables  'GD-SAPEDIT' and 'GD-EDIT' to 'X' to enable table edit and click on execute.


Table entry in EDIT mode is displayed. Through this, We can ADD/EDIT and DELETE table entry leveraging the application toolbar command buttons.


Now change the entry to the required field and save.



Thank you.









Comments

  1. Hey very nice website!! Man .. Beautiful .. Amazing .. I will bookmark your site and take the feeds also…I am happy to find a lot of useful info here in the post, we need work out more techniques in this regard, thanks for sharing. shipping container sizes and prices

    ReplyDelete

Post a Comment

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.

Determinations in SAP SD

Plant Determination in Sales Order 1st Preference: System fetches Delivering plant from Customer Material Info Record if Plant is not found at this level then system will look into 2nd Preference:   Delivering plant from Customer Master data if Plant is not found at this level then system will look into 3rd Preference : the Delivering plant for Material Master data If business user overwrites Plant at sales document level then this will be given highest preference. Shipping Point Determination Delivering Plant (Based on above conditions) + Shipping Conditions ( Sales Document Type or  Customer Master Data) + Loading Group ( Material Master ) Storage Location Determination Plant + Shipping Point + Storage Conditions ( Material Master )  ( MALA) Plant + Shipping Point + Situation  ( RETA) Route Determination Departure Zone or Country of the Delivering Plant + Destination Zone or Country of the Ship to Party + Shipping Condition from the Customer Master + Transport