Clearing SE16N Buffer After Table Structure Changes

[Pooja_HM]

Introduction

While working on custom developments, we often modify database tables after they have already been used in transactions such as SE16N. In one of my recent developments, I increased the length of a field in a custom table. Although the table was activated successfully and the database adjustment was completed, SE16N continued to display the old field length.

This blog explains why this behavior occurs and how it can be resolved using a standard SAP program.

I created a custom database table ZPOOJ_DB_BLOG_TB in SE11 with three fields. The Email field was initially defined with a length of 5.

Initial Table Definition

 Custom table with Email field length 5

At this stage, the table was activated and some test data was maintained.

To allow future enhancements, I changed the Enhancement Category to "Can be Enhanced (Deep)" and activated the table.

After that, I used SE16N to maintain table entries.

Data Maintenance in SE16N

SE16N allowing only 5 characters for Email field

As expected, the Email field allowed only five characters.

---

Requirement Change

Later, a requirement came in to increase the Email field length from 5 to 25 characters.

I modified the corresponding domain in SE11 and activated the changes.

Modified Field Length

Email field length changed to 25

After activation, I adjusted the database table through SE14 to ensure the database structure was updated.

To verify the change, I maintained table contents using Utilities → Table Contents.

Verification Through Table Contents

Email field accepting 25 characters

The updated field length was working correctly.

---

Issue Observed

However, when I returned to SE16N and tried to create or modify entries, the Email field still allowed only five characters.

Issue in SE16N

SE16N still showing old field length

At first glance, it appeared as though the field length change had not been applied. However, the database table was already updated correctly.

The reason for this behavior is that SE16N stores table metadata in its buffer. Since the table was accessed before the modification, SE16N continued to use the buffered information instead of reading the latest table definition.

---

Solution

SAP provides a standard report called BALVBUFDEL that clears the ALV buffer information.

Execute the report using transaction SE38.

Execute Standard Program BALVBUFDEL

Running BALVBUFDEL report

After executing the report, return to SE16N and test the table again.

Result After Buffer Refresh

Email field now accepting 25 characters in SE16N

The updated field length is now correctly reflected in SE16N.

Conclusion

When changes are made to the structure of a database table, such as increasing the length of a field, the changes may not immediately appear in SE16N even though the table has been activated and adjusted successfully.

In such situations, the issue is often caused by buffered metadata used by SE16N. Executing the standard SAP report BALVBUFDEL clears the buffer and forces SE16N to read the latest table definition.

This simple check can save significant troubleshooting time when table structure changes do not seem to be reflected in SE16N.