Why did i create a SAP PI/PO course

I have seen many developers who were trying to start using the tool, but many did not know where to start. Others couldn’t afford a PI training that could guide them through SAP PI/PO. In other cases, the developer simply missed the course – if your timing is bad, you might have to wait for months in order to enroll in another course.

If you are a new employee, it is quite difficult to wait for the start of a new course. Until then, your role at the company is on par with that of a paperweight. If you are a new developer just waiting around for a new course, you are unable to use your skills to their fullest extent, and you are basically unable to complete the tasks you were hired to do.

This course offers new developers a good foundation. They will be able to understand what components are there in the PI landscape, they will progress in their ability to develop scenarios, and they will be able to understand the projects created by others working at their company, so they can leverage their accumulated knowledge. Furthermore, understanding the work done by others will also lead them to new enhancement ideas.

As I’ve been working as an SAP consultant for approximately 11 years now, I have seen many scenarios. A lot of them were created after I taught people how to use the tool. Whenever I was leaving, I had to be sure that there was someone in the organization who could manage the scenarios and handle whatever was going on.

My consulting experience has provided me with a lot of insight and inspiration for this course. I created the course in order to help people learn and improve their skills quickly. That is my main goal.

If you want to join my SAP PI Training you can join it at the SAP PI/PO training site. On the site you can also find free tutorials that guides you to how to get started and create an end to end scenario.

Robot demostration af Asimo

IMG_20150418_150009Vi fik i dag set Hondas Asimo Robot demonstration i dag i Experimentariumet. Det var en sjov oplevelse at se hvad det nyeste inden for robotteknologi er.

Honda har i 30 år arbejdet på gående robotter. Og nu viser de den nyeste version.

Den nuværende robot kan gå og løb op til 9 km/t. Hvilket er en forbedring i forhold til tidligere version. Det så mægtigt sjovt ud at se den løbe, da den var meget nede i knæene.  Asimo kan også gå op af og ned af trapper. Da den skulle gå ned af trapper skulle den først have justeret sin placering så det kom til at passe med at gå ned af, og den var vist ikke i stand til at justere sin placering på vejen ned. Så det tog lidt tid før at den kunne placere sig korrekt for at gå ned af.

Asimo kunne også hente drikkevare med en special bakke, sparke til en fodbold, danse og skulle kunne hælde fra en flaske til et pap bærer (vi så det kun på video).

IMG_20150418_150911Asimo var kodet til at kunne bevæge sig mellem nogle forud mærkede punkter på scenen. De var markeret med klistermærker med reflekser på. Showet var korregraferet så Asimo viste at den skulle stå et bestemt sted og så bevæge sig et andet sted hen og viste hvad den kan på den tur. Der var nogle forskellige programmer som den kunne gå igennem som blev styret via stemme kommandoer og en operatør inde bagved.

I demonstrationen blev der benyttet stemme komandoer til at bede roboten om forskellige ting. Jeg ved ikke hvor meget disse kommandoer den kender og hvad man kan få den til, om det bare var til at få roboten til at starte dens operationer.

For at se Hondas præsentation af Asimo her

Det er pt ikke muligt at bruge Asimo til noget, den kan primært bruges til at vise hvordan robotten kan bevæge sig. Hvis den skal kunne bruges til noget bliver den kunne genkende objekter og selv hen til dem.

Der er et stykke vej til at robotten kan fungere i hjemmet eller hospitaler. Det kommer til at tage noget tid, da der er nogle ting som den skal kunne. Jeg vil tro at inden for 5 år vil en sådan robot kunne lystre kommando og foretaget opgaver i hjemmet som madlavning og rengøring. Så er det spørgsmålet hvad sådan en robot vil komme til at koste. Om det er muligt at få den ud i hjemmet eller det kun vil være hospitaler der vil have råd til en sådan robot.

Bog: Fra Knoglekræft til Ironman

Jeg har fået læst Gert Runes nye bog ” Fra Knoglekræft til Ironman” som udkommer i dag. Jeg var så heldig at få hørt hans foredrag torsdag hvor han også solgte bogen.

Fra Knoglekræft til Ironman Bog

Bogen indeholder Gerts historie fra han var ung og mistede sit ben til kræft. Alt det han har været igennem efter det med kun at have 1½ ben. Og hvordan han er han fandt på og gennemførte en Ironman i København.

Gert har et rigtigt levende sprog som får sig til virkeligt at leve sig ind i den teenagers liv, der lige pludselig skulle til at klare sig selv med kun et ben. Der bliver malet rigtig mange billeder som for det til at være livligt.

Det som er interessant er hvor meget det kun at have et ben gør ved en person. Vores samfund er bygget op på at vi ser ud på en måde. Hvis vi er uden for de normer er det meget svært for os at blive en del af fællesskabet, det kræver en indsats fra vores side at blive en del af det.

Et stor tema i bogen er udfordringer, Gert har oplevet hans liv med et ben. Det kan være hvordan får man fundet en cykel som man kan cykle med 1 ben og 2 arme eller hvordan man kan være teenageren.

Vi har alle udfordringer i vores liv og det er ikke alle nogle som vi selv har sagt ja til. Og vi helst ville undgå dem. Men de udfordringer skaber os som personer. Nogle kan få store betydninger for vores liv og vi skal derfor kunne find ud af hvordan vi håndtere dem. Gerts udfordringer sætter vores egne i perspektiv og det er meget brugbar i nogle situationer.

Sidst i bogen er en opsummering, hvor Gert Rune beskriver hvordan man kan håndtere udfordringer/problemer og det er nok den del som er mest brugbar. I den forstand at man kan bruge det på sig selv. Der er en god beskrivelse af hvordan man ser udfordringerne, som han illustrere med en pose. Det er en meget visuel måde at se på problemer. Denne del måtte gerne være lidt større.

Et andet tema er sygedoms historien, hvordan det opleves for en patient at være indlagt og få kræft behandlinger Gert fik. Bogen vil nok være meget god læsning for andre som oplever sådanne medicinske udfordringer og hvordan man alligevel kan komme tilbage og få et ”normalt liv”.

Nu hørte jeg hans foredrag før jeg læste bogen, der er nogle gentagelser men bogen er meget mere detaljeret på nogle områder. Der var også emner som egnede sig bedre til at høre ved foredraget. I den forbindelse passer bogen meget godt sammen og giver en mulighed for at sætte sig lidt mere ind i Gerts udfordringer. Bogen kan så tjene til inspiration af at man godt kan klare de udfordringer.

Du kan købe bogen http://gertrunesbog.dk/ eller til Gert Runes foredrag.

 

 

SAP Process Orchestration is ready

I have been working on creating a course for PI developers so they could learn how to useProcess Orchestration/BPMN. I was missing a good tutorial to get started with BPMN so I could help my customers move to the single stack.

So I decided to create a course on the topic of BPMN and PI.  One of the things I learned most from was on interview with some of the people how have been suing BPMN for some time.  In this blog I’ll share some of the information that I got from the interviews.

  • BPMN is a beautiful tool that, we as PI developers, must understand how to use. Yes it was the word beautiful on a SAP product. Really nice. The reason is that it enables developers to draw the processes much better and is easier to understand. There is also the concept that there is the Business Rules Management (BRM) which makes some actions easier.
  • BPM is easy to get started with. It was not so difficult to use if you had the background on ccBPM. The basic building blocks are much the same and then it can do a bit more. Most experts agreed that it was a good idea to start small and with a simple process. Then you could enhance it to make sure that you covered the business. If you stared with designing the full process you would have a hard time validating it.
  • Performance is improvement is much better. So there is not the requirement to try to avoid using BPMN for all cost. With ccBPM the goal was to avoid using it because of the negative performance that it had. The people that I interview did not share this concern and thought that BPMN was a much better performing tool and the PO was a good solid platform.
  • BPMN can be eliminated in many patterns in the migration. In a lot of instances we want can avoid using BPMN when migrating. A lot of ccBPM is from old releases of XI where we often had to create collect patterns and async/sync bridges.  Well this mean that you will not end up having the same number of ccBPMs and BPMN if you do a migration. In some scenarios you may also end up creating new processes, to make the business process better supported.
  • Data structures/message types is being validated much more. In ccBPM you could put whatever message into the process. BPMN requires you to have the exact data structure, so you will have to define the data as it are. This is giving some issues if you want to have idoc data into the process. One workaround is to use CDATA structures for the data you don’t want to define.
  • Versioning can cause some challenges. The best is to use NWDI to handle the projects. NWDI did make all of the change management and version control much better. The challenge is that not all clients have NWDI. So there is the option to export the software components

You can get access to the all information on the interview at http://picourse.com/po

*) I don’t know if any of the issues has been change with the newer services packs, but this is the results of my interviews.

Berlin Marathon 2013

Berlin Marathon var i år slået op til at være det største efter som de har 40 års jubilærum. Så det tog 6 timer at få solgt alle 40.000 billetter til løbet. Til en pris af mellem 60 og 120€ har det nok været en god forretning.

Daniel på rullemarathonJeg havde også købt adgang til inlineskate marathonet som blev løbet om søndagen. Jeg havde ikke planer om at gennemføre det, da jeg ikke havde trænet særligt meget til det. Men jeg blev tænt af den hellige sports ild. Så jeg tog afsted med det mål at prøv og hvis jeg ikke kunne få fart på rulle skøjterne ville jeg stoppe tidligere. Men det gik ret godt og jeg kom igennem på 1.55. Så lidt hurtigere en Kenyaneren løb i dag til marathonnet. Så det går pænt hurtigt igennem byen. Det var ikke specielt hårdt, hvilket nok også hang sammen med at jeg ikke lavede så meget.

Der var rigtig mange som kom galt afsted på turen. Jeg så flere styre og nogle af dem så ret slemt ud. Der udover er der dem som sad i vej kanten. Jeg har nu fundet ud af at jeg ikke skal løbe flere rulleskøjte løb. Det er alt for farligt til at jeg tør gå i gang med det. Det var sjovt men jeg har ikke lyst til at komme tilskade ved at placere skøjten forkeret eller at en den gør det foran mig.

Så er der marathonet som blev startet kl 8.45 om søndagen. Jeg havde glemt min chip til løbet som var den samme som jeg benyttede til at rulle med. Så Kenneth måtte løbe hjem og hente den. Han var så flink også at tage en velcro strips med til benet, da chippen er lidt svær at få til at være på skoen.

Det var ret kolt da vi gik over til starten. Så det var med jakke og ekstra bukser på. Jeg kunne aflevere dem til Kenneth og Martin, og kunne så få min pose når jeg kom i mål. Ellers tror jeg ikke jeg kunne nå at aflevere tasken. Det var helt stort af mennesker, der nok alle skulle aflevere deres poser inden for en kort periode.

Starten

Jeg kom ud af start blokken ret hurtigt og holdt 4.20 -4.30 de første 5 km og det føltes ret godt. Jeg prøvede at sætte tempoet lidt ned, men det kunne ikke lade sig gøre. Der var lidt at følge dem omkring mig, og så blev jeg nød til at over hale nogle.

Jeg kunne holde et godt tempo indtil omkring 30 km, hvorefter min tid gik ned. Jeg kunne ikke holde ud at løbe så jeg tænte at jeg skulle gå lidt. Første gang jeg gik føltest ret mærkeligt, det var jo et helt andet tempo. Jeg gik måske 50m pr gang. Så det var ikke meget, men det havde da en betydning på min tid. Men det betød jo nok nogle minutter

Det var ellers motiverende ind til 20km at få at vide at jeg havde en forventet tid på omkring 3:10. Hvilket var mit strech goal. Så jeg viste at det kunne gå hen og blive god tid.

Distance Tid
5km 22:30
10km 45:27
15km 1:08:19
20km 1:31:30
Halv marathon 1:36:39
30km 2:20:13
40km 3:13:08
Marathon 3:24:44

Daniel vinder billed

Jeg har ikke været så meget ud over de 21 km i min træning, hvilket nok er noget jeg skulle have gjort lidt mere. Jeg kunne godt mærke at der ikke var så meget blødhed i mine fivefingers,  og når man træder hårdt ned får jeg lidt for meget ond i føderne. Der var også en vabel på indersiden af fødderne hvor der var noget stof inden i.

Derudover vil nogle længere turer formentligt også have gjort mig mere stabil på de længere ture.

Et stort problem ved træning har været at kunne holde tempoet. Jeg kan ikke holde 4:40 når jeg er ude at træne alene. Det er meget svingende. Jeg prøvede sidste uge at holde 4:40 på løbebånd for en 20km. Men så blev mine fødder alt for våde, så jeg følte at jeg gled en gang imellem.

Væske

Jeg drak ved hvert depot, undtagen det sidste. For det meste et og nogle gange 2 glas. Jeg fik ikke tisset undervej, så jeg har nå fået lige i underkanten.

Energi.

Jeg prøvede med Powerbars gel og fik taget 2 jeg havde taget med efter 10 og 20 km. Jeg skulle så bruge lidt tid på at få vand nok så det krævede to vand depoter for en gel. Efter 27km var der uddeling, så der fik jeg to som jeg brugte på resten af turne.

Jeg føler ikke at jeg mangler noget energi. Men jeg havde meget dårligt i maven, men det er nok ligeså meget det at jeg har holdt mig i gang så længe.

Benene

Jeg har ikke haft så mange problemer med at gå rundt efterfølgende. Jeg var i spaen og fik spuglet mine ben i 30 minutter og det hjalp godt at få varmen. Efterfølgende var jeg på tur rundt i byen med Emil, og det gik godt. Jeg har forsat lidt ondet under fødderne.

Første ekstra tur fra fredag, hvor der forsat var lidt langsomme og tunge ben.

New SAP PI/PO Course

I have not been as active as I was hoping on on this blog.

I have been focusing a lot on creating different online products for the SAP Process Integration market and for Experts.

My newest product is a course about SAP PI, which will teach you all the thing you need to know before you get started as a SAP PI consultant.

What can we learn from The Lean Startup

I was listening to Eric Ries The Lean Startup with the subtitle How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses, last week.


I have not thought myself as a startup where the thoughts from the book could apply. In my definition a startup create a product/service to put into the market and is a team to deliver this work. I’m just a single person working on a bunch of different ideas. I’m working on software and information products to the SAP market.

The way Eric defines a Startup is:

    A startup is a human institution designed to create a new product or service under conditions of extreme uncertainty.

In this context I am a startup and I can see that the contexts and ideas apply much more to me. I do work under conditions of extreme uncertainty. I’m not really sure how I can make sure to sell my product and services. I know that it is possible, but I need to find the solution to really expand the market.

One probably more important aspect is the ability to measure how we are doing. For the startup to be successful and compete with big companies, they need to be learning at a much faster pace. The only way to be a better learner is to have ability to measure what works and what does not work.

I have always known that it is a good thing to make A/B testing of website or other solutions that you put into the market. Also look at the number of visitors on your website and see what makes everything convert. It take consistent practice to be sure that you follow up on the areas. But it is one of the things that often are not done. It is a bit too complicated and you don’t know what the result means.

What was your take aways from the book.

 

Book review: The SAP Consultant Handbook

I have been reading “The SAP Consultant Handbook” by Jon Reed and Michael Doane on my flight home from San Diego. It is a nice short book about how it is to be a part of the SAP eco system.

It is always nice to be reconfirmed in some of the ideas you have, of what you see the business you are in. The book is old from 1999 and updated in 2004. A lot of things have happened in the SAP field over the last years.

The book goes into details with all the different aspect of how you can approach the SAP marked either as a consultant or as an end user. The premise for those has not changed over the years. So it is the same type of decisions you will have to make today. In that perspective I think it is a killer book for everybody how wants to move into the SAP field.

There is a nice way of balancing what to do in some situations, should you take a higher paying job to work with older systems or getting the job that makes you travel.

One issue I have been seeing is that people may not have the long term for what they want to do in the business. They just have a job and like or don’t like it. The long term vision is important when you are selecting the job and when you have to select if you want to move.

One interesting thing the is

The Catch-22 of SAP: there are not enough trained consultants because those who have training are consulting and none of them are teaching.

It makes it really hard for new people to enter the space and make sure that companies are getting more qualified jobs.

One of the reasons is that it is either a job as a trainer or as an implementer. This means that you do not get the information for people how really do the implementation. It would be nice if it was possible for some of the top implementers/specialists to be able to deliver content they know.

 

 

Personal Kanban Mapping work | Navigating Life

Personal Kanban Mapping work | Navigating Life by Jim Benson and Torianne DeMaria Berry.

i have an interest in lean or agile development , be cause it gives great opportunities for making improvments in a place where you don’t have fixed processes. Kanban is one of the principles related to ie scrum. It is a little different how you are visulatizing the data.

 

Personal Kanban is about visualizing the work you are doing so you are able to handle it. I think the kanban part is really important because it gives some great options for users. This is normally done on a board of some part.

 

An important part is to limit your Work in progress (WIP). This is all the task that you are currently working on in any way. If you can reduce the number of distinct items you are working on at any one point you have more mental capacity and it will be easier to handle the different work items.

 

With the visualisation you will be able to see what your throughput is and how long time it takes to handle any one task.

 

We are dealing with the real world, so it is not always that we are able to block everything off and just work on what we want. A good example is now when I was just interrupted by a Text message that I choose to react to. It could be import, but it was not.

Personally we often get stuck in the state over complication, where we make everything way to complicated to handle.

The goal is to have task that are pulled, where you as a person decide which one to use. Push is just to take the first thing in the inbox and react on it.

A list programmer is most often superior because they take the time to know why they are building the software in the first place. This gives some clarity and makes it more compelling to workon. I guess that it is something like building a wall or a cathedral. The clarity helps with giving growth.

I you cannot see the work it is uncontrolled and we should never do more work than we can handle. I guess that it is an important part that we are able to know what we can do and not do more.

Currently I think I have too many tasks on that I’m working on to be successful with it. I know that it is difficult to say no to projects whey they are there and you think it is good for you.

The last thing is the POMODORO principle where you are focusing on some work for 25 minutes and then take 5 mintus of. This will help build your focus and make sure that you can get much longer in your progress. It is a really difficult discipline to use and it requires a lot of self control. It is so nice and much easier to work on other peoples projects than our own.

I’m currently reading about how to use normal Kanban in product development.

I did like the book it gave an overview of what kanban is about and the importace of stopping with all the work that you are doing.

Great by choice by Jim Collins and Morten Hansen

 

Great by choice by Jim Collins and Morten Hansen

 

This book is the sequel to Build to last and Good to Great. It is also a research focus book, where they are comparing a bunch of different companies of different perspectives. The book validates the principles of the previous books.

They have found 10 different companies and have compared how they are performing compared to other companies in similarly niches.

 

They companies they have selected did a lot better. And they introduced the concept 10 x companies to identify the behavior of the better performing companies.

 

The things they are finding the companies are doing better are the following.

  • They are performing constituent. They don’t grow because they thing the market can bare it. They strive for a 20 mile walk everyday to make sure that people are not getting too tired have something to go for. This is like Southwestern which only open a few new routes every year. For every year they have started new routes.
  • They try to experiment with something. Shoot bullets and when they find something where they can excel in they do the bet for it. They need to have the time to bet on next big and work on solving the problems.
  • Innovate but still keep the old ideas that work. Know when to kill the products.
  • Have a deadline, for when the product can no loger be used or when something should be done before. If we cannot make it to the top today, we have to turn around.
  • Luck there does not seem to be any indication on if one or the other part is doing any bether. They seem to have been gotten the same number of luck. The difference is that the 10x was able to use the unluck to propel them forwards.
  • They are Specific Methodolical and consistent (SMaC ) with their content. It makes a difference in the way to are able to communicate. It could be like the bill of rights where they have a clear understanding of what will work in the future.

 

To contain the presentation they are using a framework. It does make it a bit more clear on what they are doing and how things will be explained.

 

 

One thing I like about the book is there is some questions that you can ask your self at the end of each section on how this apply to my organization. This really helps and makes it much more interesting to read. The questions give a sense that there is something that I’m cheating when I don’t answer the questions.

 

There is also use of explores to show how the ideas works for them. It could be the comparison between Scott and Amundsen South Pole journey. They use a lot of the same principles as the 10x companies.