.
This is the link to the Recording from today's
#SAPSysArchs SAP Portal and SAP Fiori Architecture Call
Invitation for SAP System Architects, Development Architects, Application Architects
and Basis Architects and everybody who is interested, to join the next #SAPSysArchs
call:
Subject: SAP Fiori & SAP Portal
Date: Wednesday 17th February - 17:00 CET
Click here to add it to your calendar [thanks gregor.wolf4]
Meeting Url: https://sap.emea.pgiconnect.com/C5236419
Conference Code; Participant Passcode: 329 122 3879
Local Dial-in Numbers are here
Following on from January's #SAPSysArchs call on SAP Gateway, the February call will be
about the complimentary subject of SAP Fiori & SAP Portal.
As before, the goal of the call is a peer architectural discussion on the subjects of SAP Fiori
and SAP Portal, what they are, how they fit together and the future the SAP Portal has in a
SAP Fiori world.
The call will open with a short ppt presentation introducing the subject of SAP Fiori and SAP
Portal, and subsequently, the floor will be opened for peer discussion on these subjects.
We are very lucky, as aviad.rivlin has very kindly
accepted to join the call and act as the authority on the subject.
The call will be a unique opportunity for peers from SAP Customers and SAP Partners to
understand, in the Fiori world where the Portal fits in, what SAP's plans are for the two to exist
harmoniously and why SAP Customers should continue to invest in their SAP Portals when
there is SAP Fiori.
As has been explained here previously, the point of the call is to discuss real SAP system
architecture challenges facing real people at real companies. The call is less a lecture and
more a discussion.
Please take the opportunity to think of interesting questions and challenges on the subject of
SAP Fiori and SAP Portal and feel welcomed to post the questions here in advance of the call
(in the chat under the blog) or bring the questions and challenges to the call. The benefit of
posting challenging SAP Fiori and SAP Portal architecture questions here in advance is for
challenging subjects it will give Aviad the chance to prepare and the other peers the chance
to give feedback on their thoughts ahead of the call.
The goal of the call as usual is to learn from peers through open common discussion and
solution sharing on contempory SAP system architecture challenges.
Looking forward to all feedback and attendance.
Let's have some fun and fully understand how Fiori and Portal fit together and why we should be
investing in our Portal strategy.
About #SAPSysArchs
Together we are all #SAPSysArchs, everybody in the SAP Business who is involved in SAP
System Architecture decisions.
A global peer group enabling sharing of discussions, questions, philosophies, throughts and
experiences.
#SAPSysArchs face many challenges including pressure of having to be the subject matter
expert, the final internal technical authority, and without always having access to support.
Where is the documentation, there is not enough architecture documentation around SCN
or SMP, we're lucky if a Master Guide gives some architectural insight.
Architect's don't blog, why ? Often blogging architecture solutions, philosophies, ideas, could
risk sharing company's secrets combined with pride of not wishing to be publicly challenged.
What to do ? #SAPSysArchs creates a peer group where on a monthly basis peers can have
an open discussion on a contempary subject, and compare thoughts.
Less a lecture and more a discussion, there are mountains of documentation on SCN, SMP,
TechEd, the #SAPSysArchs calls are primarily an opportunity for open peer discussion, where
attendees bring their challenges and throughts.
Real challenges faced by real people at real companies, rather than PowerPoint Presentations.
Good architectural design and decisions bring many benefits including:
. creating competitive advantage by
. enabling End User productivity, enabling End Users to be productive and keeping them
productive
. reducing costs
. reducing time
Every company is different, running at different speeds with different budgetary and business
pressures.
What is the best architectural decision for one company, may not for a variety of reasons be the
best architectural decision for another.
However, enabling #SAPSysArchs to share and compare in peer discussions will benefit all.
The New SCN SAP NetWeaver Architecture Category - An Introduction
p.s. martin.steinberg and christian.braukmller4 have I missed anything 🙂
.
- SAP Managed Tags:
5 Comments
