Skip to Content

RIP Documents (Resolved)

I'm guessing these two posts are related as both refer to the documents with links to old SDN location that are no longer available:

https://answers.sap.com/questions/95209/missing-unavaiable-document.html

https://answers.sap.com/questions/99689/abap-oo-tutorial-series-is-not-visible-anymore.html

Apparently it is now up to the "SAP owners" to decide whether to re-publish the documents. I wonder if they all know (or care) about this.

Update 2 months later: This has been resolved for the majority of documents. Thanks to the SCN team for following up on this!

* Please Login or Register to Comment on or Follow discussions.

40 Comments

  • Jan 10, 2017 at 07:23 PM

    I didn't know...and do care...but not sure anyone would notice. I actually don't even know how to get to my old ones now and revive them.

    • Jan 10, 2017 at 10:40 PM

      Well, I checked the old blog that listed items to be done in preparation for migration and there is no action item like "backup your documents" or something. It vaguely mentioned "content posted by SAP employees" but it seemed as if it'd be migrated in some form.

      • Jan 10, 2017 at 11:52 PM

        Ok, I just double-checked, and all my old "documents" did indeed migrate over as blogs.

        • Jan 11, 2017 at 05:56 AM

          affected are the documents which got created in SDN times, before 2012. They were created in SAP given forms and were added as pdf attachments, an option that was only available for SAP employees in SCN times.

          These documents were entirely controlled and approved and have - what I saw - a much higher quality as many that were created without guidance in SCN.

  • Jan 10, 2017 at 08:01 PM

    if we only had a coffin bell ...

    coffin-bell.png (89.4 kB)
    • Jan 10, 2017 at 10:10 PM

      I guess we have a bell in form of the concerned SCN members who suddenly realized their beloved documents went missing. Now if only anyone would hear the bell...

    • Jan 10, 2017 at 11:49 PM

      Cause, you know, zombies need a way out... ;)

  • Jan 10, 2017 at 11:19 PM

    Hi Jelena,

    It's not quite like that, but I don't want to get into the specifics here.

    Let me just say that I hear the bell and am going to let the team know we have an issue.

    Regards,

    Audrey

    • Jan 13, 2017 at 05:24 PM

      Thanks, Audrey! The questions about missing documents are starting to pile up already, so perhaps some urgency can be given to this.

  • Jan 11, 2017 at 07:44 AM

    Oh, this reminds me a tweet i made when SAP announced big chunks of improvement for mid january...

    Call me Cassandra.

    Now, trying to make a check on the actual status of SCN:

    -We got problem posting answers...from 24th november

    -We have NO mail notifications

    -We have thousands of tags

    -We have NO a good search engine

    -We have NO shoutout

    -We have no more Documents

    -We have a wonderful Activity stream, with alot of redundant informations

    I'm critic by nature and i'm also pretty pessimistic but... how does SAP think to build a community this way?

    Again, i feel sorry for who is putting his/her face here (Audrey and Jerry in first place) trying to calm the waters, but guys, seriously, you killed your own community.

    1.png (31.5 kB)
    • Jan 11, 2017 at 10:58 PM

      More movie clips filling my brain after seeing your final comment Simone, and 'not dead yet' came to mind.

      Enjoy: https://youtu.be/Jdf5EXo6I68?t=45s

      @Veselina - sorry about the cat...but I feel happy :)

    • Jan 12, 2017 at 05:24 AM

      I skimmed SAP Community Release Notes since October (the new features part).
      The single improvement, which did not turn into a design disaster and did not introduce/re-introduce a number of bugs, that I know of, is Changes to the list of alert categories (SOC-4209).
      If minuscule improvements lead to serious problems like non-functioning activity stream and notifications, imagine the destructive potential of the 'big improvements'.

    • Jan 13, 2017 at 07:12 PM

      Hi, Simone, Jeremy, and Veselina:

      In case you may have missed it (it was around the holidays): We published a post last month outlining the bigger priority improvements coming in January: https://blogs.sap.com/2016/12/12/2016-wrap-up-looking-forward-to-the-new-year/.

      We are on track to start rolling these out next week.I am hopeful that they'll cover some of the items Simone listed -- without triggering disaster (per Veselina's point).

      We'll post an announcement, of course, to explain what is new. And, of course, I'll keep an eye on the comments to address any concerns, questions, and criticisms.

      Best regards,

      --Jerry

      • Jan 16, 2017 at 07:36 AM

        Jerry, i'm not so impatient to see the improvements since the results are under everyone eyes (now i'm getting the notification bug too, hurray!).

        I'm at the point i fear the upcoming changes.

        Please, refer to my (or Veselina or Jelena or Eli ) answer to Jamie in this thread: it's the same discussione we had about a month ago.

        • Jan 17, 2017 at 02:25 PM

          Hi, Simone:

          I've been following that "Pfft" thread very closely. I haven't chimed in because my colleague Jamie has already been involved in responding.

          I'm understanding the concern that people fear new features will create new (or trigger old) bugs. I'd like to share information about the QA process, but I also want to address specifics.

          Is there anything from the release notes, new features, etc., that you found particularly problematic? Perhaps you could refer me to other threads I've overlooked? I read the "Pfft" thread, and I didn't notice anything about a specific bug related to a feature roll-out. (The thread is primarily about a drop in traffic and dissatisfaction with the tagging scheme. In the conversation you mentioned, you and others point out that old feedback -- going as far back as beta -- was not taken into consideration. But I didn't notice anything about bugs caused by new fixes/features, and that's a concern I'd like to tackle separately.)

          I can add that, just as we are using community feedback to implement new features, we are using the same feedback to prioritize bug fixes. I admit that we (or I) need to do a better job of tying fixes and features back to proposals/reports in Coffee Corner, Idea Place, and things tagged with "Using SAP.com." Jamie and I have posted information about new features and fixes, but moving forward, we plan to cite specific feedback (where we can) while, at the same time, commenting back in threads to let the posters know how their feedback is reflected in new versions of the community platform.

          Best regards,

          --Jerry

          • Jan 18, 2017 at 07:50 AM

            Hi Jerry, we are beating a dead horse, you know it?

            Is there anything from the release notes, new features, etc., that you found particularly problematic? 

            It's the whole structure which is wibbling wobbling unstable *bite my finger to avoid to sound totally unprofessional*

            i do not keep track of the bugs anymore (i pointed out one last week without having a single feedback from your team. It's a really silly and minor bug but yet, no word and, looking at Jurgen's 24th november bug, maybe it's better!), really, just trying to endure and live with them (and my activity here is almost...flat line apart Coffee Corner) and i'm not receiving the mail with release notes anymore since mid-last november, so i cannot link a bug to a particular release or feature.


            So, thanks, but no, i stop here: SAP community, for me, is dead.

            I'm so tired to read the jargon about how much Mommy SAP cares about our feedbacks and keeps asking them, asking our involvement: it sound exactly like when i'm really sick of my kids and turn their questions in other questions back to gain some time.

            As i repeated urbi et orbi, i already provided all the feedback, all the bugs and many more things: it's not my job collecting them and following them, i'm not paid for it at all.

            Instead, the feedback I had are a completly feeling of.... helpless fatigue.

            So, thanks, but no more.

            Have a good day and my best wishes for your work, this is my stop, i'll take a walk.

            • Jan 18, 2017 at 04:12 PM

              Hi, Simone:

              I hate to see you go, and I never wanted to come across like anyone's mommy (although, like you, I'm a daddy...and I'm familiar with the tactic you described). I don't think I'm being evasive to buy time. I'm not dancing around the tough questions or complaints. I compile each and every one of these conversations, and all of your feedback has indeed been part of the prioritization process for bug fixes and features.

              If you do happen to check back in the community, I wanted you to see a response at least:

              1) I believe we may have been talking about two different things. I was under the impression that these are complaints about new features introducing new bugs. That's what I was asking about so I could provide information about the QA process related to those specific rollouts. I wasn't trying to dismiss the proliferation of bugs (existing and otherwise), which I think is how my response was perceived.

              2) I apologize if you didn't get a response to a recent bug report. My colleagues and I are doing everything we can to talk to people here, in discussions with Using SAP.com, and Idea Place. Sometimes a single response can trigger a whole new conversation (I give you Exhibit A), and we fall behind. I'm not making excuses, but I certainly wouldn't want anyone to think that we are deliberately ignoring anyone. I hope the fact that I am responding here -- and my concern about losing an important community member -- shows that we take things seriously. Progress is slow, frustration is high, and I realize people may have stopped listening to me. But that doesn't mean I won't continue to try to work with community members, take my lumps, and try to push improvements.

              3) In another discussion, I got plenty of criticism about the lack of visibility into bugs and how we're addressing them. And I respect that community members are under no obligation to share their feedback or work with us to improve the community experience. As you noted: It's not your job. It's our job to give you what you want. That being said, I am truly grateful for people who take the time to report and give input, and I am sorry if these efforts feel unappreciated. Does that sound like jargon? I hope not. I do my darnedest not to write in corporate speak.

              4) Getting back to bugs: I again admit that our communications reporting features and bug fixes isn't enough. (As an aside: I seem to recall you explaining that you turned off wiki notifications for the release notes because you found it annoying when someone added something new, someone else deleted it -- and you got notifications both times. This is why we've been doing a regular blog post highlighting the most significant stuff from the release notes, so no one feels obligated to go to the wiki every two weeks for detailed lists.) Context is required. When a new feature comes along or a bug is fixed, we should go back to the relevant discussions and let people know how their feedback has been addressed. Otherwise, we put it on them to keep track and interpret. This is going to change moving forward.

              If you don't see this, then I hope other community members might. And maybe, just maybe, it will be enough to convince them to stick around. If not, I hope that eventually you'll see that I'm not just shoveling BS and we'll make enough solid progress to win you back.

              Until then, I'll keep the lights on.

              Best regards,

              --Jerry

  • Jan 13, 2017 at 07:06 PM

    Hi, Jelena (and everyone posting here):

    We are working on both a short-term and long-term solution to this issue. We're planning to post something next week explaining these solutions -- as well as explaining what happened to the documents and why. But to give some brief background: As we were preparing for the transition from SCN to SAP Community, we had an old repository of 20,000 assets (accessible from what were essentially cover pages in SCN). The repository was scheduled for shut down, and some of the documents were very old (and rarely accessed), so we conducted an audit using specific criteria and working with internal content owners to migrate the best stuff. We thought this audit would protect the most useful materials, clear out the outdated content that was no longer wanted or supported..

    So as to whether "SAP owners" know or care...they were notified, but that doesn't mean things weren't overlooked (obviously, given the recent issues). That's why we were inviting the owners to alert us if their content wasn't migrated. We were also allowing community members to alert us if they wanted files that were no longer available. Clearly, far too many useful ones became unavailable.

    Again, we'll share more details next week...including the steps we are taking to make the materials accessible. For now, I wanted to assure everyone that we are aware of the significance of the issue and we are working to deliver a fix.

    Best regards,

    --Jerry

    • Jan 17, 2017 at 10:55 AM

      @Jerry "content that was no longer wanted or supported.." is relative. There are many people in SAP who think 4.6x systems are out of date systems and content no longer wanted or supported. Yet, there are still plenty of customers out there who are on such outdated systems and would need content

      • Jan 17, 2017 at 01:59 PM

        Hi, Colleen:

        That is a fair point. Perhaps using age shouldn't have been part of the criteria, but we had hoped that traffic would be a good metric for determining whether customers found the content useful. Regardless, we recognize that this approach has caused (yet another) problem, and I believe a short-term solution will be available this week while the team works to come up with a better, long-term option.

        Best regards,

        --Jerry

    • Jan 19, 2017 at 05:40 PM

      So is this "next week"? Is it all happening Friday? Saturday?

      Craig

  • Mar 09, 2017 at 03:15 PM

    Hi, everyone:

    IT implemented a fix today for the broken archive links. Before I post a "yay, we did it!" announcement, I am checking each individual report/complaint first -- to make sure those have been addressed.

    For the two above, I can confirm that everything seems OK.

    Per https://answers.sap.com/questions/95209/missing-unavaiable-document.html : If you go to https://archive.sap.com/documents/docs/DOC-14296 and click View Document, you'll get the document.

    For https://answers.sap.com/questions/99689/abap-oo-tutorial-series-is-not-visible-anymore.html : These were not screenshots, not links, so I searched for one at random. And I got this: https://archive.sap.com/documents/docs/DOC-10238

    In this case, clicking View Document will download a zip that contains swf files. These are no longer supported, so you can't watch them on the site -- but you should have other options for viewing the files.

    Again, I'm not ready to celebrate just yet...but so far, so good (as far as the few I've checked thus far).

    Best regards,

    --Jerry

  • avatar image
    Former Member
    Mar 16, 2017 at 11:03 AM

    I feel this is horrible. horrible. horrible. horrible.

    • Mar 16, 2017 at 02:23 PM

      Hi, Nakil:

      It most certainly was. But it has been fixed for thousands of documents with broken links.

      Best regards,

      --Jerry

      • Mar 16, 2017 at 03:13 PM

        This is a discussion, so I can't close it but I updated the OP to reflect current situation. Thank you!

      • avatar image
        Former Member
        Mar 17, 2017 at 05:56 AM

        The Thomas Jung tutorials used to have source codes also whose formatting was broken during SDN to SCN transition. Now that broken code is replaced by a code box having a dead link. Not that I am all of a sudden planning to learn OO using those tutorials, but just saying because the link is mentioned in this article.

        • Mar 17, 2017 at 01:30 PM

          Personally, I'm OK with getting just the videos back. Those tutorials are quite old and there are newer/better code examples available these days. Also the code can be seen in the video, so not required to follow along. And I'm totally using those tutorials to learn OOP! :) They are the best.

          As Jerry mentioned, not 100% was recovered but I believe it'll be more practical to report any missing items that are still needed in the Using SAP.com tag.

          Thank you!

      • avatar image
        Former Member
        Mar 17, 2017 at 08:02 AM

        I'd like to point you to this.

        https://answers.sap.com/questions/155638/question-to-migrate-abap-templates-from-sapgui-edi.html

        It talks about missing code in:

        https://blogs.sap.com/2015/10/29/tool-to-migrate-abap-templates-from-sapgui-editor-to-eclipse/

        which could have been a missing .txt or .nugg or .xml or .zip file attachment.

        • Mar 17, 2017 at 11:45 AM

          Hi, Nakil:

          I'll look into everything you reported above.

          Best regards,

          --Jerry

  • Add comment
    10|10000 characters needed characters exceeded