EREC - ASSIGN_BASE_TOO_SHORT error

[former_member214276]

Hi All,

At a client, they want to enlargen the data model of e-rec. This means adding fields to the standard SAP tables. For example HRP5125.

I created append structures to do this (best practice as far as I know). On activation, there are no problems.

I also enhanced the structure P5125 with the same fields. No error on activation.

Now, when i open the recruiter dashboard in the portal with all the query's (POWL), system tells me there is an error.

When I go to ST22 I get

ASSIGN_BASE_TOO_SHORT

in

RH_BASE_READ_INFTY_NNNN

Function Module

This happens on line

ASSIGN bnnnn TO <bnnnn_wa> CASTING TYPE (dbtab).

data declaration is

DATA : BEGIN OF bnnnn OCCURS 100.
          INCLUDE STRUCTURE hrinnnn.
  DATA : END   OF bnnnn.

Does anyone know if I forgot something or how to solve it ?

Thx

[Former Member · Accepted solution]

Hey Jan,

You've mentioned that you enhanced both structure HRI51xx and P51xx, It's a bit confusing... The only structure you should change, is the CI_P51xx. The customer include is included in all others.

The dump ASSIGN_BASE_TO_SHORT means that the structure of the field symbol (dynamicaly defined in T77D-DBTAB), is bigger than the field structure (typed TABLE HRINNNN) .

HRINNNN is a generic structure which is composed of the key structure, the historic structure and the VDATA field which has a lenght of 1000 char. You may check how long is HRP5125, and if it's bigger than 1000chars you will get a dump. Did you add a string field ?

best regards

Hadrien

[former_member214276 · Accepted solution]

Hi Hadrien,

Indeed, one of my fields was 255 chars, which caused the problem.

So not the append structure was the problem (off course it is better to use the CI) but the length of one of the fields.

Anyway problem solved ! Thx !

[Former Member]

Hello Jan,

You shouldn't append a new structure in HRP51xx but customized the infotype 51xx throug t-code PPCI/PPCM, There is an include CI_P51xx in HRI51xx where you can add all customer fields. As soon as you add the fields into the customer include CI_P51xx, all other structure will take it into account. Therefore no other appending is necessary.

Try first to customized properly the infotype then check again.

Best regards

Hadrien

[former_member214276]

Hi Hadrien,

Nice to see you again !

Thx for your answer. Indeed, I put all the fields in the CI structure.

However problem still remailns ... When I clear the CI structure, the POWL in the portal works fine.

When I add fields to the structure I still get an error on the same place as before ...

[dsharmak]

Hello Jan,

Please check the fields you have enhanced are correctly defined. Please check by removing the fields and then again add the enhancement to the table. It has worked fine for a customer.

Best Regards,

Deepak..

[former_member214276]

What do you mean by correctly defined ?

Can I have warnings for my datatypes on activation ?

There are no errors and activation was succesfull