topic Re: BAPE_VBAP issue with offsetting in Application Development and Automation Discussions

BAPE_VBAP issue with offsetting

former_member219801 — Thu, 31 May 2018 09:30:25 GMT

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

Re: BAPE_VBAP issue with offsetting

former_member219801 — Thu, 31 May 2018 12:02:36 GMT

Would really appreciate a response... 🙂

Re: BAPE_VBAP issue with offsetting

former_member259807 — Thu, 31 May 2018 12:05:39 GMT

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

Re: BAPE_VBAP issue with offsetting

Sandra_Rossi — Thu, 31 May 2018 15:12:11 GMT

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...