5

Are there known performance issues with BAPI_CONTRACT_CREATEFROMDATA related to...

 1 year ago
source link: https://answers.sap.com/questions/13659461/are-there-known-performance-issues-with-bapi-contr.html
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Jun 14 at 07:28 AM

Are there known performance issues with BAPI_CONTRACT_CREATEFROMDATA related to SD_COND_ACCESS?

86 Views

Hi All!

We are currently investigating why the creation of contracts with BAPI_CONTRACT_CREATEFROMDATA is causing extreme performance issues. The BAPI gets triggered from an outside system via a Webservice and we've been testing the creation of one contract with 46 line items where the contract runs for 5 years. Each item comes with a special price condition which - as far as I understand - overwrites whatever else the condition schema would provide, so should be fairly straightforward.

Because the process takes extremly long (we are talking hours for just this one contract!) I was able to grab some snapshots of what is happening in the background via SAT executed in a parallel session. I also kept an eye on the SCMOND data captured in the test system while the process was running. The latter provided some interesting input related to the number of times some routines get called - and the numbers look weird to say the least:

contractcreate-01.jpg

(1) - the 8 about matches the times the webservice process got triggered during testing with only one of the executions progressing (the others had some data issues which needed to be fixed first)

(2) - the 46 could be related to the number of line items (or is just a big coincidence!)

(3) - the 32+ million times both SD_COND_ACCESS and SD_COND_GET_CALL_MODE look completely out of place. Why would anything trigger this many calls to function modules to set up one contract?

The very high number of calls to SD_COND_ACCESS is also visible in SAT-snapshots where I had it collect data for +/- 2 minutes a couple of times:

contractcreate-02.jpg

I didn't pay too much attention to the overall runtime but after 3 to 4 hours a contract with 46 line items had finally made an appearance in the system with the creation time fitting the time we had started the testing.

We had also saved the importing parameters for BAPI_CONTRACT_CREATEFROMDATA and I used that to rerun the process via SE37 to take a closer look and debug the process. This again showed the regular calls to SD_COND_ACCESS but also that internal table KOMT2 kept growing and growing.

At one point it had 92,278 entries:

contractcreate-03.jpg

A short while later this had grown to 101610 lines:

contractcreate-04.jpg

So, what I'm wondering is if anybody else has run into comparable issues performance-wise with BAPI_CONTRACT_CREATEFROMDATA and SD_COND_ACCESS? Searching OSS or SAP Community didn't produce anything thus far. It would already help to at least know if the above is expected behaviour or really as weird as I think it is. Any pointers what else to check are obviously appreciated!

We are on NW 7.50 EHP8 SP22.

Thanks much and cheers

Bärbel


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK