Skip to Content
author's profile photo Former Member
Former Member

Random blank screen in SRM 7.0 with IE 10 punching out to catalog

Hi -

After 4 days of insane hours testing, we're running into a complete brick wall with SRM 7.0 and IE 10. We have a Punchout Catalog that loads the initial page, but the second the page is submitted to go to the second page inside the catalog, the page throws a blank white screen and you can't continue.

We've more or less ripped the catalog down to bare bones to see if we can get it to submit a form, which we have a couple of times, but then we've had the same code fail other times.

Its worth noting the following:

1) SSL is turned on.

2) we currently use this catalog in production with IE7/8 without any problems.

3) the catalog is deployed hundreds of times around the world and this is the ONLY instance where anything of the sort is happening.

4) if you reference the same catalog outside of SAP, with the same browser, it works flawlessly.

I'm at a loss.

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on May 30, 2014 at 08:26 AM


    please check following thread

    and sap note



    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 02, 2014 at 04:12 PM

    I'm adding additional information here guys. I made a more complete post elsewhere. Here it is:


    Hi -

    One of our customers has been standardized on IE8 for punching out to our catalog. They want to move to IE10, but we're having really bizarre issues during the testing phase. As a prereq, please note that the way this solution works is that they start their session inside SAP, punchout to our e-catalog, but the site retains a "frameset" (a traditional frameset...not iframes/ajax div etc) with the top frame being a way to return to the SAP system, and the bottom frame being the catalog. The bottom frame is encoded and we don't really have any way to know if its manipulating our catalog code, or what.

    ISSUE: In IE8, there are no issues with the system. They use our shopping cart, add things to the cart, go to the review cart on the next page, and punch the data back into SAP. In IE10, it blank screens on the second page, almost like a custom SAP 404 error - just completely blank...when you view source, it IS a 404 "this page cannot be displayed", but the URL that is given is for the internal SAP system, rather than our catalog (which it SHOULD be trying to look for a page on our catalog rather than an internal SAP page. So its more or less like it doesn't like something on our catalog page, environment, whatever...and then redirects to a internal SAP page that doesn't exist/isn't working correctly). Every time anything is clicked on the page (form submission, link, etc) that has to refresh the entire page/frame, the system white screens. We are using iframes (yes, I know 😊 . Ajax issues with IE8 was the driver there, IE8 was a requirement for our customer due to SAP...) to submit certain datapoints on the page, and we don't have any problem submitting to the iframe. The second you submit to the whole page (or frame, I guess, if you want to look at it that way), white screen/404 issue.


    • It works fine in IE8. It also works perfectly in IE10 OUTSIDE of the frameset SAP is generating. Even inside of the customers secure environment. The second SAP gets involved, the issue occurs. We've never seen this issue with any other deployment of anything, anywhere...other ERPs, other browsers, etc.

    • SSL: We managed to get the testers to get past the first page by turning off SSL, but they had to work their way outside of the traditional security in SAP as well so I'm not sure if this has any relevance at all. But SSL compatibility with SAP or frameset as it pertains to IE10 was a thought process.

    • It doesn't seem to be a form submission issue. We initially thought it might have something to do with the way IE10 interprets frame ID as we were submitting to _self, etc, but turns out traditional links don't work either with no sort of target information.

    • It's definitely on the page load itself, not on the submission of form data to the page, when the white screen happens. We noticed that half of the page would load for a split second before it white screened. Initially we thought it was based on something that was being sent, but its definitely past any header submissions or form posts.

    • We pretty much broke apart the entirety of the code and weeded out all kinds of factors and tested them independently and in different extensively that I'm almost positive it isn't a traditional coding issue. The result pages ("second page") we set for the tests had almost no content at all...all of which is traditional HTML that has been supported by every browser since the dark ages. We could not find any true consistent patterns. Sometimes the user could make it to the second page, other times not (only on the tests, never on the actual catalog), but usually it was the same for all test scenarios (so if we had 9 test scenarios, they'd all fail, or they'd all succeed).

    Conclusions thus far:

    • We're almost positive it isn't code related. However, it could absolutely be caching related? Although we have the user clearing caching almost every page test, I'm not sure if that clears everything like page load over SSL or something of that nature?

    • Clearly there is some major difference between IE10 and IE8 and how they interpret the same environment. This might (probably is) just be a SAP issue. Could it be our SSL type? What is interpreted differently in those scenarios between the two browsers inside the same SAP wrapper?

    Anything else you can think of would be greatly helpful. We've been testing for countless hours....we have a really technically advanced team...really can't catch a break on this one or find any consistencies. If SAP wasn't a factor, we'd have this solved in 15 minutes. I'm not really sure what else to explore since the SAP environment is in play. Thanks for your help!

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.