2008 Jul 29 2:47 PM
Hi, Gurus:
When I use VA42 to update one contract, If some contract has about 5,000 partner in the header/partner tab. It will take long long time.
Is there solution for it or oss notes.
Thanks in advance!
Hi, Gurus:
When I use VA42 to update one contract, If some contract has about 5,000 partner in the header/partner tab. It will take long long time.
Is there solution for it or oss notes.
Thanks in advance!
2008 Jul 29 2:49 PM
2008 Jul 29 2:51 PM
I tried to find notes on it, but I can't find anything for this issue.
Thanks,
2008 Jul 29 2:55 PM
Contact SAP then, that's why you pay for they. They will solve the problem soon(er or later).
2008 Jul 29 2:50 PM
Hi!
I suggest you to look for some OSS notes...
Regards
Tamá
2008 Jul 29 2:53 PM
2008 Jul 29 2:56 PM
a) duplicate post
b) there are a large number of notes for this
Rob
2008 Aug 01 5:01 AM
At one of my clients we had this same issue. We were dealing with contracts that had thousands of partners on them. We contacted SAP regarding it and they:
- Told us to impliment some OSS notes, which we did but didn't really help much in the overall runtime
- Told us that it was reasonable for it to take several minutes just to open a contract or scroll through the the partners once it was open
I spent some time anaylzing the problems and the majority of the runtime was actually being spent loading in the address data for each individual partner. So we ended up utilizing enhancment points to modify the standard transaction to supress the loading of the addresses associated with the partners on loading up of the contract. Once a user went into the partner screen they still wouldn't see any addresses (because we had supressed them) but once they double-clicked on an individual partner it would show the address in the detail screen becuase the standard code would see that it wasn't loaded and would load the individual address data.
I also located several spots in the code where they were doing non-efficient access to internal tables such as unnesasary sorts embeded with loops. We contacted SAP and they wouldn't address this so I did further enhcnament point modifications to fix several of these routines.
It does require putting in several fixes to get it right, but we did get it down to opening in seconds instead of minutes. This was about a year ago, so SAP may have addressed it finally in OSS patches because we did have many dialogs with them about what we were doing.
~Ian
2008 Aug 01 2:54 PM
Hi, ~Ian:
Thanks for your good information. Can you give me some detail information such as which subroutine and enhancement-points we need change. that's save my time. Appreciate!
2008 Aug 01 3:03 PM
Yunfa Zhang
did you look at OSS 205774,771604,144229.
in that there are sevral correction are suggested for us.
Amit.
2008 Aug 01 3:04 PM
From where I am at the moment I can't log into the system where I made the changes, so what I'll try and do is maybe log in later and provide you a summary of where we made the modifications.
~Ian
2008 Aug 08 8:11 PM
Hi, ~Ian:
Do you have chance to logon to the system to find out the change you made for this performance issue(va42).
Thanks
2008 Aug 11 5:55 PM
Hello,
Please check the following SAP Notes..
385139
74776
144229
394334
205774
365037
395117
771604
198806
332154
Yours sincerely
Dileep
| User | Count |
|---|---|
| 5 | |
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |