2017 Oct 22 8:58 AM
*EDIT* Fixed. Apparently the container object name didn't match the hard-coded name I sent to the SALV factory, even though I thought I checked it a couple of times. My hard-coded name is of type STRING, converted into C length 20 for the factory, and maybe there is a length limit. I couldn't find it anywhere inside the inner methods of SALV, so I'll just stick with names that are 10 characters or less.
Hello all,
I have a Z infotype with a table control in its screen 2000. I'm trying to replace this TC with an editable SALV, using naimesh.patel's guide. In the screen I have a custom control, and the SALV is defined to sit inside it (in a CL_GUI_CUSTOM_CONTAINER object). In PBO I'm executing all of the needed code for setting up the SALV object and data, but nothing is displayed when I get to the screen itself. The other fields and existing table control are displayed without any problem.
Does anybody know what could be the cause of this problem?
I think something may be wrong in my implementation of Naimesh Patel's method, but I can't figure out what exactly.
Thanks everyone!
My code is in the attached file due to its length.
2017 Oct 22 2:31 PM
You must make sure that the custom container area is named identically in both the dynpro and in the program. I see "GO_SALV_CC" in the program, so just check that the name is the same in the dynpro.
BTW: there's no reason to prefix the area name with GO as with object reference variables.
2017 Oct 22 11:58 AM
After all calls to the methods of the SALV class, you must call the DISPLAY method to transfer all data to the frontend, otherwise nothing is displayed.
2017 Oct 22 1:29 PM
I forgot to mention that I'm already calling it, but outside of the main SETUP_SALV method.
I've now edited the original question to mention it.
2017 Oct 22 2:31 PM
You must make sure that the custom container area is named identically in both the dynpro and in the program. I see "GO_SALV_CC" in the program, so just check that the name is the same in the dynpro.
BTW: there's no reason to prefix the area name with GO as with object reference variables.
2017 Oct 22 3:32 PM
I thought I made sure the names are identical, but apparently there was a difference. It's working now.
Thank you!