http://www.sdn.sap.com/sdn/weblogs.sdn?blog=/pub/u/455 SAP Developer Network SAP Weblogs by Robert Eijpe © Copyright 2009 SAP. All rights reserved. SAP.com en-us http://weblogs.sdn.sap.com/pub/wlg/15023 At 25 June 2009 SAP kicks off the SAP NetWeaver Business Process Management in the Netherlands. SAP, IDS Scheer and NL for Business launch their close loop showcase for Business to Model and Model to Execute during a 1 hour session. The session starts with a presentation of IDS Scheer about the use of SAP Enterprise Modeling applications by IDS scheer. NL for Business presents the position and need of SAP NetWeaver Business Process Management. SAP ends the session with an outlook of future developments. In this blog you will find the presentations and showcase movies. Robert Eijpe Business Process Expert, Business Process Management, Business Process Modeling, Business Rules Management, Composition Environment (CE), Enterprise Performance Management, SAP NetWeaver Platform, Service-Oriented Architecture en-us 2009-07-13T04:40-08:00 text/html © Copyright 2009 SAP. All rights reserved. SAP http://weblogs.sdn.sap.com/pub/wlg/14196 The best ever additional tools for SAP Enterprise Application development have been created by Adobe. SAP Interactive Forms, Adobe Flash Islands for Web Dynpro, Web Dynpro Flex generated code of Visual Composer, SAP Business Objects xCelsius and SAP Acrobat Connect applications by Adobe are all based on products of the Adobe LiveCycle Enterprise Suite Platform. These tools are optimized to build Online Rich Internet applications and offline desktop application uniformly. This will keep development cost at a minimum. This article will tell the background for building first class Enterprise applications on top of SAP. Robert Eijpe ABAP, Analytics, Beyond SAP, Business Objects, Business Process Expert, ERP, Interoperability, SAP Interactive Forms by Adobe, SAP NetWeaver Platform, Service-Oriented Architecture, Visual Composer, Web Dynpro en-us 2009-05-14T07:50-08:00 text/html © Copyright 2009 SAP. All rights reserved. SAP http://weblogs.sdn.sap.com/pub/wlg/14198 In this weblog I will give you the link to my presentation about Adobe AIR and Flex development on top of SAP NetWeaver at the Adobe MAX 2008 in Milan. The presentation focused on three ways of connecting Flex and Air applications against SAP: - Direct connection between SAP and Flex/Air - Connecting SAP and Flex/Air using data service - Embedded Flex in SAP Robert Eijpe ABAP, Beginner, Beyond SAP, Business Objects, Business Server Pages, Composition Environment (CE), Java Programming, Open Source, SAP NetWeaver Platform, Service-Oriented Architecture, Visual Composer, Web Dynpro en-us 2009-05-05T10:51-08:00 text/html © Copyright 2009 SAP. All rights reserved. SAP http://weblogs.sdn.sap.com/pub/wlg/8902 SAP as well as Adobe would like to invite you to participate in the upcoming courses to keep your skills up-to-date, share practical experience and network with experts. SAP Netherlands has scheduled a row of trainings on "SAP Interactive Formsy by Adobe" in their trainingscenter. Robert Eijpe ABAP, Application Server, Composition Environment (CE), Java Programming, SAP NetWeaver Platform, Visual Composer, Web Dynpro en-us 2008-03-07T06:26-08:00 text/html © Copyright 2008 SAP. All rights reserved. SAP http://weblogs.sdn.sap.com/pub/wlg/7669 We would like to invite you to attend the SAP Interactive Forms Development Course taking place in Brussels/ Belgium on November 13-16, 2007. More information can be find in this blog. Robert Eijpe ABAP, JavaScript, SAP NetWeaver Platform, Web Dynpro en-us 2007-10-27T08:09-08:00 text/html © Copyright 2007 SAP. All rights reserved. SAP http://weblogs.sdn.sap.com/pub/wlg/7103 On request of Adobe EMEA and SAP Education The Netherlands, NL for Business has developed a new course curriculum for SAP Interactive Forms by Adobe. This intensive course program has three components: classroom education, sharing practical experience and networking with experts. It has been designed as an intense program to give the participants basic knowledge to avoid the known pitfalls and to make a quick start working with Interactive Forms. Robert Eijpe ABAP, Application Server, SAP NetWeaver Platform, Web Dynpro en-us 2007-08-13T08:46-08:00 text/html © Copyright 2007 SAP. All rights reserved. SAP http://weblogs.sdn.sap.com/pub/wlg/5478 More and more standard SAP Interactive forms by Adobe will be used as a solution for customer’s problems regarding much simpler data entry and automating the manual processes. But also custom development will be involved in developing interactive forms. Because the technique is new, there will be a lot of pitfalls in the first projects of the new Developers. This web log will help the starting developer to avoid these pitfalls and help to build excellent performing interactive forms Robert Eijpe ABAP, Application Server, Beginner, Composition Environment (CE), SAP NetWeaver Platform, Web Dynpro en-us 2007-01-08T01:45-08:00 text/html © Copyright 2007 SAP. All rights reserved. SAP http://weblogs.sdn.sap.com/pub/wlg/3679 When auditing XI projects, we discovered that a quite often XI consultants choose for tailor packages for standard SAP IDocs and Remote Function Modules (RFMs). We think that this is against general design principles of using software components in SAP XI, as every standard SAP IDoc and Remote Function Module already belongs to an existing Software Component Version. With this weblog we want to show you how to find the SAP Software Component Versions of standard SAP IDocs and Remote Function Modules. Robert Eijpe SAP Process Integration (PI) en-us 2006-05-22T08:48-08:00 text/html © Copyright 2006 SAP. All rights reserved. SAP http://weblogs.sdn.sap.com/pub/wlg/3524 The Dutch XI Experts, a group of customer XI experts and colleague consultancy companies in the Netherlands have planned to write a series of blogs for the SDN community to share their knowledge. In all integration scenarios you will have the possibility to exchange messages synchronous or asynchronous. Mostly XI developers choose interfaces based on technical availability and not about specific functional requirements. This blog is all about the matter of synchronous and asynchronous, seen from the point of view of the message, and not from the technique. Let this blog help you to make your own design decisions Robert Eijpe Beginner, SAP Process Integration (PI), Emerging Technologies en-us 2006-04-20T01:01-08:00 text/html © Copyright 2006 SAP. All rights reserved. SAP http://weblogs.sdn.sap.com/pub/wlg/3475 In our opinion Exchange Infrastucture implementations often suffer from too much ABAP expertise, but too less experience in specific integration issues and concepts. To improve sometimes even poor results, we initiated the Dutch XI Experts, D-XIE, as an initiative to share gained knowledge amongst customer XI experts and colleague consultancy companies in the Netherlands. D-XIE has planned to write a series of blogs, the D-XIE soap, for the SDN community to share their knowledge. In this first one we will describe different integration scenarios that XI supports. Just to set the basics for future blogs. We hope this D-XIE soap will be a good starting point for new and experienced XI developers. Robert Eijpe Beginner, SAP Process Integration (PI), Emerging Technologies en-us 2006-04-13T11:18-08:00 text/html © Copyright 2006 SAP. All rights reserved. SAP http://weblogs.sdn.sap.com/pub/wlg/3346 In the web logs The EPI model part 1 and part 2, I explained the EPI model and how we use it into our workshops. In part 3 I start explaining the approach how to implement this model. The approach exists of four main parts: Design cycle, Build cycle, Continuous improvements and Process control. In the previous web log (part 3a) I explained the design and build cycle. In this web log we will explain the Continuous improvements and Process control. Robert Eijpe Business Process Expert, Business Process Management, Business Process Modeling, Service-Oriented Architecture en-us 2006-03-20T10:43-08:00 text/html © Copyright 2006 SAP. All rights reserved. SAP http://weblogs.sdn.sap.com/pub/wlg/3344 In the web logs The EPI model part 1 and 2, we explained the EPI model and how we use it into our workshops. In this part 3 we will explain the approach how to implement this model. The approach exists of four main parts: Design cycle, Build cycle, Continuous improvements and Process control. In this web log we will explain the design and build cycle. Robert Eijpe Business Process Expert, Business Process Management, Business Process Modeling, Service-Oriented Architecture en-us 2006-03-16T23:58-08:00 text/html © Copyright 2006 SAP. All rights reserved. SAP http://weblogs.sdn.sap.com/pub/wlg/3189 In this weblog I will focus on the possibilities of SAP XML Document Object Model (DOM) processing at the ABAP stack. My objective is to explain how you can use it in abap mapping. For this I split this weblog into three parts. This document is the last-in-the-series. The first part focused on the conversion of an ABAP table into an XML file and the second part focused on the conversion from a XML file (back) to an ABAP table. This last part focuses on the use of XML DOM and ABAP mapping to convert a flat file structure (for example edifact file or legacy files) using the plain HTTP sender adapter into an XML file. The advantage for having this HTTP connection between two systems instead of using the file adapter with a FTP connection is having a simple synchronous push connection in stead of having a complex asynchronous polling connection. Robert Eijpe en-us 2006-02-20T07:58-08:00 text/html © Copyright 2006 SAP. All rights reserved. SAP http://weblogs.sdn.sap.com/pub/wlg/3161 In this weblog I will focus on the possibilities of SAP XML Document Object Model (DOM) processing at the ABAP stack. My objective is to explain how you can use it in abap mapping. For this I split this weblog into three parts. This document is the last-in-the-series. The first part focused on the conversion of an ABAP table into an XML file and the second part focused on the conversion from a XML file (back) to an ABAP table. This last part focuses on the use of XML DOM and ABAP mapping to convert a flat file structure (for example edifact file or legacy files) using the plain HTTP sender adapter into an XML file. The advantage for having this HTTP connection between two systems instead of using the file adapter with a FTP connection is having a simple synchronous push connection in stead of having a complex asynchronous polling connection. Robert Eijpe ABAP, SAP Process Integration (PI) en-us 2006-02-19T06:52-08:00 text/html © Copyright 2006 SAP. All rights reserved. SAP http://weblogs.sdn.sap.com/pub/wlg/3055 We are promoting SAP ESA for almost a year now and therefore we use our 5-layer EPI (Enterprise Process Integration) model. Our model is very successfully and big SAP customers in the Netherlands adopt it. They like it because it is useable for IT managers to create a picture about the technical impact of ESA. But it is also useable for business process owners (BPO) to give their processes the right place within the ESA concept. Robert Eijpe Business Process Expert, Business Process Modeling, Service-Oriented Architecture en-us 2006-01-23T02:46-08:00 text/html © Copyright 2006 SAP. All rights reserved. SAP