TMDSECATCNCD379D: Purpose of padding in PDO mapping object

I am trying to generate SSC code from SSC tool. I am using TI TMDSECATCNCD379D (and its SSC tool patch) and SSC tool 5.11. The generation is fine but I found the code genreated have padding for both PDO mapping object. e.g.

OBJCONST TSDOINFOENTRYDESC    OBJMEM asEntryDesc0x1601[] = {
{ DEFTYPE_UNSIGNED8 , 0x8 , ACCESS_READ },
{ DEFTYPE_UNSIGNED32 , 0x20 , ACCESS_READ }, /* Subindex1 - map control word */
{ DEFTYPE_UNSIGNED32 , 0x20 , ACCESS_READ }, /* Subindex2 - map target position */
{ DEFTYPE_UNSIGNED32 , 0x20 , ACCESS_READ }}; /* Subindex3 - add 16bit padding to get an 32Bit object/process data structure */

while there is none in TI TMDSECATCNCD379D own demo application:

OBJCONST TSDOINFOENTRYDESC    OBJMEM asEntryDesc0x1601[] = {
{ DEFTYPE_UNSIGNED8 , 0x8 , ACCESS_READ },
{ DEFTYPE_UNSIGNED32 , 0x20 , ACCESS_READ }, /* Subindex1 - Reference to 0x7010.1 */
{ DEFTYPE_UNSIGNED32 , 0x20 , ACCESS_READ }, /* Subindex2 - Reference to 0x7012.1 */
{ DEFTYPE_UNSIGNED32 , 0x20 , ACCESS_READ }}; /* Subindex3 - Reference to 0x7014.1 */

Both seems working fine (at least communication normal) but I would like to understand more to avoid any future problem.

Thanks for reading. Any reply is appreciated.