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

Dump in Bapi_contract_createfromdata.

Former Member
0 Likes
982

Hello,

  I am getting dump "DATA_OFFSET_LENGTH_TOO_LARGE" when i execute the BAPI to create contracts, also in creating Quotation.

" The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not

caught in

procedure "MAP_VBAK_TO_BAPISDHD" "(FORM)", nor was it propagated by a RAISING

clause.

In the running program "SAPLVBAK", the field "CH_PAREX", which is of the type

"u" and

length 990, was to be accessed with the offset 30 and the length 1401. ".

Note '1137897' was implemented to resolve this issue but the dump is still there.

What do i need to do to get rid of this ?

Anjani

4 REPLIES 4
Read only

Former Member
0 Likes
774

Hi Anjani,

As the dump says, the code is trying to access the field CH_PAREX with offset 30 and length 1401 which is more than its length 990. Is this part of your code? Can you find something like CH_PAREX+30(1401) in the FORM given?

Regards,

Sindhu Pulluru.

Read only

0 Likes
774

Hi Sindhu,

  No, this is SAP standard code. Here's the code.

* Daten übertragen * CHECKMAN / UNICODE

               call method cl_abap_container_utilities=>fill_container_c

                    exporting

                       im_value     = da_bape_vbak

                    importing

                       ex_container = ch_parex+lenstruc(da_length_bape_vbak)

                    exceptions

                       illegal_parameter_type = 1

                       others                 = 2.

In which 'da_length_bape_vbak' value is 1401. which is when i calculate no of chars in BAPE_VBAK structure of total fields.


Read only

RaymondGiuseppi
Active Contributor
0 Likes
774

or

- The internal table that you passed to parameter EXTENSIONIN is not correct (structure must be BAPIPAREX, structure length is 1.604) ?

- You extension of VBAK is far too big (Did you put a long text in it ?)

Regards,

Raymond

Read only

0 Likes
774

Hello Raymond,

  I am not passing EXTENSIONIN Parameter in the BAPI as i don't need to update any custom field.

   Is there any limitation in defining the no.of fields in BAPE_VBAK, because when i see the structure BAPIPAREX used for Extension in param, i find it's permissible length 960 chars only.