This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Hi Group,
After a long time I'm sending a mail to this group. I need an urgent halp to understand the functional benefit to having line level status for contract lines. In our environment we are facing problem due to this. I was thinking to remove this, the reason is we have the contracts with thousands of lines, when we revise or change the status the system is taking too long and sometimes its getting times-out the users are complaining. The only possible solution I'm seeing is customize the code to stop chenging the status of the line always. Any suggestion or can anyone explain the functional requirement of line level status.
Rgds
JJ
"If you take PROBLEMS as PROBLEMS they become a big PROBLEM,
but if you take PROBLEMS as CHALLENGES they become an OPPORTUNITY"
JJ
Hi Jomon,
The Line Status for Contract lines allows users to change status of individual lines on the contract to Cancelled or WAPPR without having to revise the contract.
Using the action "Change Line Status" from select action menu, you can cancel some lines on the contract or change status to WAPPR then approve later.
Contract Lines that have a status of CAN (cancelled) will not be viewable on any purchase document.
Thanks.
Dina
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Jomon Jacob
Sent: December-11-13 1:13 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Contact-line Status - Please and Urgent help required.
Hi Group,
After a long time I'm sending a mail to this group. I need an urgent halp to understand the functional benefit to having line level status for contract lines. In our environment we are facing problem due to this. I was thinking to remove this, the reason is we have the contracts with thousands of lines, when we revise or change the status the system is taking too long and sometimes its getting times-out the users are complaining. The only possible solution I'm seeing is customize the code to stop chenging the status of the line always. Any suggestion or can anyone explain the functional requirement of line level status.
Rgds
JJ
"If you take PROBLEMS as PROBLEMS they become a big PROBLEM,
but if you take PROBLEMS as CHALLENGES they become an OPPORTUNITY"
JJ
Hi Jomon,
Just checking... Have you tried to optimize queries behind the contract revision?
I would enable sql logging in Dev environment to trace all running SQLs and would try to tune DB so they all run as fast as it can. Start with slowest queries.
Another option:
Users should understand when you have thousands lines it will be slow.
Can they break down contracts into smaller chunks?
Regards,
Alexey
Hi Dina & Alexy,
Thanks a lot for the reply.
Dina,
How are you? This is Jomon from ACC :-) Hope you remember me.
How is things with you?
Rgds
JJ
"If you take PROBLEMS as PROBLEMS they become a big PROBLEM,
but if you take PROBLEMS as CHALLENGES they become an OPPORTUNITY"
JJ
On Thursday, December 12, 2013 5:54 AM, "spivot@gmail.com" <spivot@gmail.com> wrote:
Hi Jomon,
Just checking... Have you tried to optimize queries behind the contract revision?
I would enable sql logging in Dev environment to trace all running SQLs and would try to tune DB so they all run as fast as it can. Start with slowest queries.
Another option:
Users should understand when you have thousands lines it will be slow.
Can they break down contracts into smaller chunks?
Regards,
Alexey