Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Rows missing in table when viewed using transaction SM30

former_member184386
Active Participant
0 Likes
1,255

Hello, I cant figure out what's goin on here so I need some help.

I created a custom table with these fields:

MANDT - Key

PERNR - Key

WBSID - Key

ENDDA - Key

BEGDA

BILLAB

AVAIL - This field is using a custom domain ZAVAIL with value range (AV, PD, PI, PC, etc).

Then I created a table maintenance for this custom table and added some entries using SM30, using diffrent ZAVAIL such as AV, PI, PC).

I exited the table maintenance and went back in but this time I just wanted to display all the entries created, I left the radio button to "No Restrictions' and clicked on "Display" button. I noticed that all the data displayed are all the AV entered, the other ZAVAIL entries are not displayed. But if you tried to restrict the data and specify say PD it will be displayed. Also, all entries are present if you just looked at the table using SE16.

Strange, anybody have any idea what I'm missing here?

Thanks in advance.

Ricky

2 REPLIES 2
Read only

Former Member
0 Likes
861

Ricky,

I feel that it is your miss-out to view the other entries as well, though they will also be available there.

If you can see them is 'Enter Conditions', then definitely will see them in 'No restrictions' also.

You might be able to view only AV data first, because table might have large data and other Pl, PC data will be lingering down bottom somewhere.

Just Display All, and press the 'Position' button, then put your values 'PC' in the Z field and check, if you can find the data then it means everything is OK.

Regards,

Diwakar

Read only

former_member209703
Active Contributor
0 Likes
861

Try the Expand-Collapse button.

Looks like the structure of your table with the ENDDA field as key, allows the SM30 to group different records (due to date splits) in the same one.

That maybe your case.