‎2010 Aug 25 8:30 PM
Hello all,
This is my first post. Thank you for opening up your community to me.
I am evaluating the capabilities of BAPI_CONTRACT_CHANGE for a project by running it through SE37, and I occasionally will get the dump TSV_TNEW_PAGE_ALLOC_FAILED. I have found information about other dumps that occur during this BAPI's execution, but none on this one in particular.
This occurs when a large number of contract items are to be returned. I'd like to know if there are any workarounds so that I can update these larger contracts.
I'd appreciate any assistance you are able to provide.
Thank you.
‎2010 Aug 25 8:36 PM
Moderator message - Welcome to SCN. I'm not familiar with this BAPI. Are you updating multiple contracts in one call to the BAPI or are you calling it multiple times (once for each contract)?. Rob
‎2010 Aug 25 8:36 PM
Moderator message - Welcome to SCN. I'm not familiar with this BAPI. Are you updating multiple contracts in one call to the BAPI or are you calling it multiple times (once for each contract)?. Rob
‎2010 Aug 25 8:49 PM
Thank you for the quick response.
This BAPI updates one contract at a time. I update the header and execute, then the BAPI returns the updated header and line items.
‎2010 Aug 25 8:56 PM
So SE37 is dumping?
Try creating a program that does this.
Rob
‎2010 Aug 25 10:48 PM
This dump usually occurs during memory buffering over consumption.
Get your basis team look into the memory profile parameters for a start.
Then, how many line items are updated?
‎2010 Aug 25 10:53 PM
Hi Rob,
I have faced similar dump in one of the standard fm which picks the classification data. There were some notes related to that.
When there is huge amount of data it says the itab cannot hold such amount of data and it dumps .
‎2010 Aug 25 10:58 PM
Yes but the OP is running it through SE37 and that could be the problem. I'm suggesting that he remove a layer that could be causing the problem.
Rob
‎2010 Aug 30 3:41 PM
Hello all. Thank you for your support with this issue.
The issue has been resolved. I found that applying OSS Note 1402008 prevented the dump. The issue was with the FM itself, and not with SE37.
I hope that this helps others in the future.
Thanks again!