Hello all,
Usually I have the functional consultants activate the business functions, because the are usually prerequisites from the functional side, and the majority of these are not reversible. However, this past week I was tasked with turning on PPS in an SRM system. Okay, there were 5 switches the team wanted turned on, so I figured that was easy enough. Unfortunately I kept hitting an error while trying to activate a PPS function:
"PPS can only be activated in the extended classic scenario..."
So, naturally I started looking for the Business Function that matched that description... except there wasn't one. I did look up the prerequisites, and from a business function standpoint they were already met. After a quick Google search I came up with the solution (which was surprising, considering I misspelled my primary search term).
In order to fix this, one must dive into SPRO and activate the following:
Supplier Relationship Management → SRM Server → Cross-Application Basic Settings → Activate Extended Classic Scenario
Just set that, and you can activate PPS to your heart's desire. Keep in mind this setting is client dependent and must be set in EVERY SRM client.
Hope this helps...
Joey
Sunday, August 5, 2012
Various Connection Errors with SAP Portal, SRM, PI, UWL, etc...
Hello readers,
I know it has been a while since I posted anything here. I have been busy. Just thought I would pop by and enter another little note.
On a client site I was having some sporadic connection issues between the portal, SRM, SUS, ECC, PI, etc. All configuration and system settings seemed to be correct, however after several minutes of moderate use (or several hours of light use) things would stop working. The UWL would begin throwing "credential" issues, the SSO connection tests would begin to give error, and iViews stopped providing information from the backend.
After some digging I found the following line in the Java logs in multiple locations:
"Max number of 100 conversations exceeded..."
Then it hit me.
So I went to the server and made sure to check for the CPIC_MAX_CONV system environment variable in windows. Sure enough, it was not set. Thus the system was stopping CPIC connections at 100 (the default).
After setting CPIC_MAX_CONV to 2000, and restarting the SAP system all these sporadic errors went away.
Just an FYI, this is something that should be set at initial install, and as observed it can cause many strange communication errors if it is not set.
Hope this helps...
Joey
I know it has been a while since I posted anything here. I have been busy. Just thought I would pop by and enter another little note.
On a client site I was having some sporadic connection issues between the portal, SRM, SUS, ECC, PI, etc. All configuration and system settings seemed to be correct, however after several minutes of moderate use (or several hours of light use) things would stop working. The UWL would begin throwing "credential" issues, the SSO connection tests would begin to give error, and iViews stopped providing information from the backend.
After some digging I found the following line in the Java logs in multiple locations:
"Max number of 100 conversations exceeded..."
Then it hit me.
So I went to the server and made sure to check for the CPIC_MAX_CONV system environment variable in windows. Sure enough, it was not set. Thus the system was stopping CPIC connections at 100 (the default).
After setting CPIC_MAX_CONV to 2000, and restarting the SAP system all these sporadic errors went away.
Just an FYI, this is something that should be set at initial install, and as observed it can cause many strange communication errors if it is not set.
Hope this helps...
Joey
Subscribe to:
Posts (Atom)