Application Development 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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

BAPE_VBAP issue with offsetting

former_member219801
Explorer

‎2018 May 31 10:30 AM

0 Kudos
545

Hello Experts,

I have a weird situation here.

Till last week, the whole system did not ask for an offset while using extension even in the case of more than 240 characters and everything seemed to work fine. We were able to process fields which were present even at the 290th offset like below without using part2.

ls_extension-valuepart1 = ls_bape_vbap.

But after last week, it started falling apart and failing everywhere in the system. And the fix for this was using the part2.

ls_extension-valuepart1 = ls_bape_vbap.

ls_extension-valuepart2 = ls_bape_vbap+240.

Any of you had a similar situation? Or know what could have triggered this behaviour? I do not see anything odd in the transports that were involved in the last few days. Best Regards, M

3 REPLIES 3

former_member219801
Explorer

‎2018 May 31 1:02 PM

0 Kudos
297

Would really appreciate a response... 🙂

former_member259807
Active Participant

‎2018 May 31 1:05 PM

0 Kudos
297

Did you check if append structure ZABAPE_VBAP has been changed lately?

Sandra_Rossi
Active Contributor

‎2018 May 31 4:12 PM

0 Kudos
297

Obviously, you must initialize valuepart2 to go beyond the 240th character. Why it was working, impossible to say. Maybe, by the transport, you have overwritten some corrections done directly in the production system, or something like that...