Error in BDC implementation (Input value is longer than dynpro field)

[former_member602116]

Hi All,

I am encountering an error

I know this is because a longer value is fed to the dynpro field. Per checking, only 8 characters are fed in this field, however I do not know how to check the length of 'RKEAK-FIELD(03) since when I open SE11, and input RKEAK, it only shows FIELD and not FIELD(03).

I have checked the code and the code of

PERFORM bdc_field USING 'BDC_CURSOR' 'RKEAK-FIELD(03)' .

was replaced with

PERFORM bdc_field  USING  'RKEAK-FIELD(03)' t_upload-pdline.

where t_upload-pdline is declared as

pdline  TYPE ztf0008-pdline.

My question, is this the cause of the error? Also, how do I check the length of field(03)?

Thanks in advance.

Regards,

Katherine Darunday

[former_member602116]

Hi All,

I am encountering an error

I know this is because a longer value is fed to the dynpro field. Per checking, only 8 characters are fed in this field, however I do not know how to check the length of 'RKEAK-FIELD(03) since when I open SE11, and input RKEAK, it only shows FIELD and not FIELD(03).

I have checked the code and the code of

PERFORM bdc_field USING 'BDC_CURSOR' 'RKEAK-FIELD(03)' .

was replaced with

PERFORM bdc_field  USING  'RKEAK-FIELD(03)' t_upload-pdline.

where t_upload-pdline is declared as

pdline  TYPE ztf0008-pdline.

My question, is this the cause of the error? Also, how do I check the length of field(03)?

Thanks in advance.

Regards,

Katherine Darunday

[FredericGirod]

BDC_CURSOR means you have recorded the clic of the mouse in a field, not you have enterred a value in a field

The (03) does not impact the size of the field, it is the t_upload-pdline.

Sometimes you have to check if the domain is linked to a field-exit. If yes, just using the function or a WRITE ... TO data(my_new_field) solve the issu

[former_member602116]

Hi Frederic,

Thanks so this means the value fed to the field is actually t_upload-pdline right? But how do I check the length of the said field, I am unable to see it in SE11.

[FredericGirod]

it is CO-PA .... so it is a generic field used to store a specific characteristic.

You have to know by your functional team or find the customizing table to set the correct size.

PERFORM bdc_field  USING  'RKEAK-FIELD(03)' t_upload-pdline+0(8).

(03) should be the line number in a grid

[Sandra_Rossi]

RKEAK-FIELD(03) refers to the field in column RKEAK-FIELD of the 3rd row (because it's in a "table control").

I fear that the concerned table control ("account assignment") has the list of fields vary depending on the customizing (I mean, list and order of fields, and output length), so your code must evaluate the same customizing and guess at what row the concerned field is. Unfortunately, I can't help about what customizing it is.