nolihayati isma
12th July 2013, 04:31
Hi All,

who else using the session transfer planned purchase order and facing that the session is very very slow?

we have using this session but user always complaint that the session very slow, any body can share with us, the root cause why this session is very slow alt transfer only 1 PO.

Need your idea.

mbdave
12th July 2013, 11:55
You can use baan profiler which will give you the functions taking time during a process

mark_h
12th July 2013, 15:14
Or use some of the trace options to see which query might be causing the slowness. Of course "too slow" needs to be defined - is it too slow all the time or some of the time?

shah_bs
15th July 2013, 20:45
This assumes:
1. you have the source code
2. you do not have to use the Containerized Items functionality
3. you are referring to the session timrp1260m000

This is what I had to do to make a difference in performance: Comment out the following code referencing tiitm100 table

and timrp021.cmba refers to tiitm001 path tiitm100.item |#B4.0_b.n

nolihayati isma
17th July 2013, 03:58
Hi Mark,

We facing slow only some time.
Or use some of the trace options to see which query might be causing the slowness. Of course "too slow" needs to be defined - is it too slow all the time or some of the time?


Hi Shah,
We are using session tdinv3260m000

This assumes:
1. you have the source code
2. you do not have to use the Containerized Items functionality
3. you are referring to the session timrp1260m000

This is what I had to do to make a difference in performance: Comment out the following code referencing tiitm100 table

mark_h
17th July 2013, 17:04
I would try to get baseline values and snap shots of everything go on with the system when performance is good. Then I would get baseline values for when it is bad - on the system. I do not know what all options you have of capturing that information. You can also just try traces on the session when slow and not slow. The problem is just doing the session might not show what is causing the slowness if it is system related.

shah_bs
17th July 2013, 20:24
tdinv3260m000: The same change was made in this session - comment out the reference via tiitm100.

I forgot to add that, of course, you have to replace the commented code with appropriate link back to the tiitm001 table.

In case of tdinv3260m000, it would be:

tiitm310.item refers to tiitm001


The same primary assumption apply: that you have no need to use the Containerized Items functionality.