Maximum Internal Sessions Reached

Tue Dec 11 12:22:14 EST 2007

Hi Mike,

Here's what SAP told me about the number of screens I was using:

Below is a list of the screens that need to be drilled into in order
to execute the work item. Maybe each screen
is counted an internal session rather than a new session.

[1] SWI1
[2] Display results screen
[3] Display work item screen
[4] Display technical details screen
[5] Edit screen
[6] Execute screen
[7] PA40 screen
[8] next screen...
[9] next screen....

Regards, 

Sue T. Doughty 
SAP Workflow Specialist

OLD DOMINION FREIGHT LINE, INC.

500 Old Dominion Way, Thomasville, NC 27360

Toll Free :(800)432-6335, ext.5189 
Phone :(336)822-5189 Fax :(336)822-5149 
sue.doughty at odfl.com

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Pokraka
Sent: Tuesday, December 11, 2007 9:57 AM
To: 'SAP Workflow Users' Group'
Subject: RE: Maximum Internal Sessions Reached

Thanks for the feedback.... one of the nicer things about the WUG.

I still find that a bit strange - how many transactions do you navigate
through in total (when starting from a blank session)? 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Sue Doughty
Sent: 10 December 2007 12:57
To: SAP Workflow Users' Group
Subject: RE: Maximum Internal Sessions Reached

Hi Mike,

Here's SAP's response to the Maximum Internal Sessions Reached:

As far as I understood, when you execute the item directly from your
inbox then it works fine. But if you execute the item from the
workflow log (for example from SWI1), then the message "Maximum Internal
Sessions Reached" is triggered.

This is due to technical reasons: maximal number of internal sessions
is limited to 9. This means that when you display the workflow log,
then display the workflow technical log, then try to execute the item
and execute PA40 transactions, too much internal sessions are opened.
Each time a CALL TRANSACTION or a CALL DIALOG occurs, then a new
internal session is created. This is the reason why the system
behaves differently according to the path you use in order to execute
the work item. PA40 uses CALL DIALOG and in the step 2032 of the
workflow WS90100045 (task TS90100152), the method BOR object calls the
transaction PA40.

More information concerning the internal session can be found under
the note 34154.

This behavior can not be changed, thank you for your understanding.

Regards, 

Sue T. Doughty 
SAP Workflow Specialist

OLD DOMINION FREIGHT LINE, INC.

500 Old Dominion Way, Thomasville, NC 27360

Toll Free :(800)432-6335, ext.5189 
Phone :(336)822-5189 Fax :(336)822-5149 
sue.doughty at odfl.com

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Pokraka
Sent: Wednesday, November 28, 2007 5:38 PM
To: 'SAP Workflow Users' Group'
Subject: RE: Maximum Internal Sessions Reached

Hi Sue, 

You don't mention how you got to the log in first place, but that's
already at least two sessions. But I'd agree with Mark that it sounds
like you're using session up a bit quick. 

Let us know what OSS come back with as I'm also curious. 

Cheers, 

Mike

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Sue Doughty
Sent: 28 November 2007 20:13
To: SAP Workflow Users' Group
Subject: RE: Maximum Internal Sessions Reached

Hi Mark,

Thanks for your suggestion.  I'll give it a try.

I opened a note with OSS yesterday, but have not received any response
as of yet.  

Regards, 

Sue T. Doughty 
SAP Workflow Specialist

OLD DOMINION FREIGHT LINE, INC.

500 Old Dominion Way, Thomasville, NC 27360

Toll Free :(800)432-6335, ext.5189 
Phone :(336)822-5189 Fax :(336)822-5149 
sue.doughty at odfl.com

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mark Pyc
Sent: Wednesday, November 28, 2007 2:59 PM
To: SAP Workflow Users' Group
Subject: Re: Maximum Internal Sessions Reached

Not sure. I wouldn't expect PA40 screens to be treated as internal
sessions. The log drill down yes, potentially.

What about if you look in the log, find the WI number and then access it
from SWI1 instead of the Log? 

I've got no sensible advice really. I think it's one for OSS.

On 28/11/2007, Sue Doughty <Sue.Doughty at odfl.com > wrote:

Hi Mark,

Thank you for your reply.

Yes, PA40 can be performed normally when not done from the Workflow.

If I start from the workflow log and execute PA40, I only get to the
second screen before I get the error.  How am I using nine sessions?
>From the log, is Display Work item one session, then Execute one session
and then clicking the decision button one session, etc?  Is each screen
of PA40 considered an internal session?

Regards, 

Sue T. Doughty 
SAP Workflow Specialist

OLD DOMINION FREIGHT LINE, INC.

500 Old Dominion Way, Thomasville, NC 27360

Toll Free :(800)432-6335, ext.5189 
Phone :(336)822-5189 Fax :(336)822-5149 
sue.doughty at odfl.com 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mark Pyc
Sent: Wednesday, November 28, 2007 2:29 AM
To: SAP Workflow Users' Group
Subject: Re: Maximum Internal Sessions Reached

G'day Sue,

Internal Sessions are the levels you drill down through and can back
navigate through. External Sessions are the GUI level windows you can
see and can have a maximum of 6 per login. 

Internal Sessions are created each time you drill down inside an
interactive ABAP. If you've been on the ABAP courses then you may
remember drilling down from SPFLI, through SFLIGHT and down to SBOOK
maybe even then into SCUSTOM. This would represent 4 internal sessions.
There is a hard maximum of 9 of these. 

As to why the navigation you performed before upgrade and now is being
treated differently I don't know. Can you process PA40 normally when not
going via the WF?

Good luck,
Mark

On 27/11/2007, Sue Doughty < Sue.Doughty at odfl.com
<mailto:Sue.Doughty at odfl.com> > wrote:

We are on ECC 6.0.

We have a custom workflow that is triggered by the APPLICATIO CREATED
event.  This workflow also has several sub-workflows that are executed.

When in DEV, I execute the steps of the workflow from within the log
(right click the step, click display work item, then Edit--> Change,
then execute) (when the work item is not in my in-box) or I click the
In-box button from within the log to execute steps from my in-box (if
they are in my in-box).  I always come back to the log, refresh it and
execute the next step.  

I have a step in one of the sub-workflows that executes transaction PA40
- Hire Applicant action.  When I get to this step in the workflow, I get
one or two screens into the PA40 transaction and then get "Maximum
Internal Sessions Reached" and it kicks me out of the transaction.

When I look in SM21, it says that the maximum of nine internal sessions
has been reached.  It also says that nine internal sessions are allowed
for each external session.  I'm not understanding how I can be using
nine internal sessions....and don't know where to look to see what they
are.

Has anyone encountered this or can anyone explain how I can find out the
internal sessions that I am creating?

We are in the middle of End of Year Support Pack testing and have a
go-live date of Dec. 1.  This did not happen before the Support Packs
were applied.

Thank you for your help.

Regards, 

Sue T. Doughty 
SAP Workflow Specialist

OLD DOMINION FREIGHT LINE, INC.

500 Old Dominion Way, Thomasville, NC 27360

Toll Free :(800)432-6335, ext.5189 
Phone :(336)822-5189 Fax :(336)822-5149 
sue.doughty at odfl.com 

**************************** 
CONFIDENTIALITY NOTICE: The information contained in this message may be
confidential, privileged, proprietary, or otherwise legally exempt from
disclosure. If the reader of this message is not the intended recipient,
or an employee or agent responsible for delivering this message to the
intended recipient, you are hereby notified that you are not authorized
to read, print, retain, copy or disseminate this message, any part of
it, or any attachments. If you have received this message in error,
please delete this message and any attachments from your system without
reading the content and notify the sender immediately of the inadvertent
transmission. Thank you for your cooperation. 

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

**************************** 
CONFIDENTIALITY NOTICE: The information contained in this message may be
confidential, privileged, proprietary, or otherwise legally exempt from
disclosure. If the reader of this message is not the intended recipient,
or an employee or agent responsible for delivering this message to the
intended recipient, you are hereby notified that you are not authorized
to read, print, retain, copy or disseminate this message, any part of
it, or any attachments. If you have received this message in error,
please delete this message and any attachments from your system without
reading the content and notify the sender immediately of the inadvertent
transmission. Thank you for your cooperation.

****************************
CONFIDENTIALITY NOTICE: The information contained in this message may be confidential, privileged, proprietary, or otherwise legally exempt from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this message, any part of it, or any attachments. If you have received this message in error, please delete this message and any attachments from your system without reading the content and notify the sender immediately of the inadvertent transmission. Thank you for your cooperation.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20071211/4aed86f4/attachment.htm