GP 10 Business Portal Requisition Approval Fails

(0) Share

Report

Posted on by Richard Wheeler

75,852 Moderator

We have this one requistion that cause BP to crash when trying to approve it. This requisition has 112 lines on it. It has already been past its first approver and is waiting for the second and final approver. She pulls up the requisition, clicks approve and then about 2 minutes later she gets a BP runtime error message. I see these record counts in the following tables:

MutliUserManager : 1

ReqMgmtDocument : 1

ReqmgmtLines : 112

ReqMgmtLines : 1

Is there a limit to the number of lines that can be on a requisition? I see nothing out of the ordinary on the lines. At this point it is suppose to create a PO in GP and this is where it fails.

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (1)

Sort by

Richard Wheeler 75,852 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

My mistake. The final table is called ReqMgmtOpen Tasks. I can see the first approver on this line.

Was this reply helpful? Yes No
Richard Wheeler 75,852 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

By the way, I did just do a record count check. The previous high number of records per requisition was 88. Perhaps there is a record count restriction?

Was this reply helpful? Yes No
Rob Bernhardt Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Richard,

Is there an error in the Event Viewer on the BP server that might offer any more information? Is there any more detail with the BP runtime error? If you enable custom errors and turn on the callstack (both in the web.config), this could provide some detail.

Thanks

Rob

Was this reply helpful? Yes No
Beat Bucher GP Gee... 28,061 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Richard,

Which version of Business Portal are you running ? I had users experiencing the same behavior a few times last month and it was very painfull, because the system is somehow timing out and then crashed with a sharepoint error message.

It only happens in the final approval stage... Some were pretty lengthy requisitions, some were much shorter (less then 50 lines I think)... This never happened before in BP 4.0 (we're now on 5.0).

The creator ended up to split the requisition in two or three new ones, and then could submit them and have them final approved... I didn't really had the time to debug the cause of this, because it was not something we could reproduce with certainty...

Maybe this is something we should do a bit more testing...

Beat

Was this reply helpful? Yes No
Derek Albaugh Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hello Richard,

We don't have a limit as to the number of items, lines, etc. that Requisition Management, more than we have a limit as to what SharePoint and/or IIS will allow before it times out.

First, we would want to check the server where Business Portal is installed against the System Requirements to make sure we're at least past those minimum recommendations.

Is there any related information in the Event Viewer with the error being seen for Requisition Management? Also, what error is being seen in BP?

We have seen some time-out errors with Requisition Management where we've had to change the time-out settings in the BP web.config file and/or IIS, but nothing we've seen to suggest there is any type of limit on the number of lines or items in it.

Thank you,

Was this reply helpful? Yes No
Verified answer

Mahmoud Saadi 32,738 on at

Like
a
(0)

Report
Copy link

Link copied!
I have previously had such error, I ended up splitting the requisition with more than 50 line items into several requisitions. ERP Software Blog has a considerable added- value in one of their articles (Resolving Common Errors in Business Portal's Requisition Management ) on this issue, it is stated (Quoted);

"Check if the requisition has more than 50 lines. Anything over 50 lines will result in an error. There needs to be a line added to the Web Config file that extends the time before the system times out. To do that,

Make a backup of the current Web.config file

Open the file in Notepad and do a search for MaxRequestLength

You should find a line that states: <httpRuntime maxRequestLength=”51200”/>

Change the line so that the timeout takes place after a longer period of time. Your new line should read: <httpRuntime maxRequestLength=’51200” executionTimeout=”300” />
The 300 equates to 300 seconds or five minutes.

Reset IIS and try to do the final approval.

"

Hope this helps,

Was this reply helpful? Yes No