Skip to Content

BPX has to deal with multi-speeds and one goal

I have been working as a Business Process eXpert (BPX) on a project and I have observed how hard it is to keep up with all the different solutions that are delivered by SAP and partners. The list is endless but lets list down a few of the obvious options when faced with a business requirement :-


  1. Implement / Configure the Platform Application – Usually done by a Platform Application eXpert (PAX)
  2. Implement an Industry Solution via an Enhancement Package and the Switch Framework – Usually known about by the Industry Solution eXpert (ISX) or BPX and implemented by the PAX.
  3. Implement User-Exits / BAdI to modify the standard logic – Usually specified by a PAX and implemented by an Platform Development eXpert (PDX)
  4. Implement a Partner Solutions that can be deployed to fill the requirements – Usually know about by the BPX and implemented by a Partner Solution expert (PSX)
  5. Implement some Portal Business Content that fulfils the requirements – Usually known about by the BPX and implemented by the Enterprise Portal expert (EPX)
  6. Implement a Composite Application from SAP or a Partner – Usually known about by the BPX and implemented by the Composite Application eXpert (CAX)
  7. Create a Custom Composite using NetWeaver CE – Usually designed by the BPX and implemented by the Composite Development eXpert  (CDX)


I realise that this list in not complete, but even in this simple example the BPX has to interact with 7 different roles to understand which solution is the best for the customer (PAX,ISX, PDX,PSX,EPX,CAX,CDX). All of the solutions have pros and cons and one of the skills the BPX needs to develop is to understand each of the potential solutions in enough detail to hold a meaningful conversation with each of the parties to help them all to determine the “right” solution. Part of this will involve interacting with more roles and more roles.


My experience is that each of these roles / people will be operating at their own “speed” and have their own ideas of what makes a “good” solution. In the role of BPX it is important to be able to empathise with these different perspectives and help to breathe life into solutions that might otherwise have been rejected.


Each person will bring their own experiences of things that have worked (or not worked) on previous projects and these “experiences” can be either a very good thing…or very bad.


In summary the role of the BPX is, IMHO, one of the most challenging as you need to be able to juggle Content, Technology and People….and be a very good diplomat as well.

Be the first to leave a comment
You must be Logged on to comment or reply to a post.