SAP Teched 2016 best practive BPMN development

INT210: Does and Don’ts from
BPMN Development
SAP Teched Las Vegas © Figaf 2016

• SAP PRO expert
• Worked on two BPM projects
• Product developer of Figaf Tools to
improve PI/PRO for customers
• SAP PRO Instructor
Daniel Graversen

• Based on my conversation with other developers and experts
• Gives you lessons on what you need to avoid in order to complete a
successful project

• Technical BPM
• Process Development
• Process information
Agenda

Technical BPM

• Can be avoided on many occasions because of new design patterns
• Data types
• BPMN does not support full XSD formats like IDOC, RFC and some external
definitions need to be changed
• Create own internal data types in ESR to simulate data
• Use the claim check pattern to save messages if you need more data
after
When used with ”PI”

• Performance of the BPM engine is much better ccBPM
• Not a valid reason for avoiding processes
• Can use it in more instances
• Avoid Big Data structures/contexts that are updated many times
Performance

• No tool auto process
• Do a redesign if a BPMN should be used
• Sync/async patterns supported
• For a lookup, forward the message into PI on the new interface
• Bundling
• Simplify the process
• Testing will be required
ccBPM to BPMN

• If you seriously want to use BPM, you will need to use NWDI
• Multiple developers to support and develop on the process
• One track for the BPM development
• CM Services work well with CTS+
• One track for supporting processes if you are doing long term releases
and bug fixing.
• CMS seems better for this
• One software component for each process
• It will also require EAR, EJB, and Web for J2ee and UI components
• May also have BRM for rules, DB for tables
NWDI

Process Development

• A flexible platform where it is possible to model the process
• Integration to different systems
• Easy to create first model and show who it can handle the process
Why make process in NW BPM

• The business know how the first process should work
• Have a change log of what is going on; otherwise, nobody will know
what is going on when making changes
• Be as precise as possible:
• Process diagram of what should happen
• Field level information
Business Modeling

• Business model
• Where the business can make their design
• May have multiply steps that will be executed within one task
• Can use NWDS as a modeling tool and NWDI as a repository, although it is a
little too complex to be used as such otherwise SAP PowerDesigner may be
useful.
• Technical model
• The one that will run.
• May have technical details not required on main process
• PI interfaces
• Reporting to data sources for OPI
Models

• Now only develop in SAPUI5--other methods are not relevant
• Generator for Start and Tasks
• Easy to use
• Now it supports the use of tables and substructures
• Ordering of the message follows the XSD
• Easy for creating simple tasks
• If you want an abundance of logic, you will need to code it yourself
• Gives good flexibility to monitor what is going on
SAP UI5

• Introducing fields into already generated screens
• Logic based on the field and the information
• Hidden fields need to be deleted in UI
• Value help and help values are supported in OData, but need to be
implemented
SAP UI5 Challenges

• Be able to see what was done earlier
• In comment setting a comment about how to see completed form
• Make few changes in document to be able to read the submitted
form
Look into history

• If you want bigger projects, the abilities of the BPM may be limited
• Only persist data at end of process step or save button.
• You may not be able to complete a lookup with backend data
• Limit data in the BPM context
• Persist data in JPA, and make extra calls to it in UI
Larger Processes

• Framework that builds on top on the BPMN solution
• Screen generation based on Excel with fields/variables for process
• Handles UI operations using UI5
• Gives you the ability to persist the UI between tasks
• Callbacks made in Java to give an easy way of interacting with the
user
• Services like lookup, help values, and overview screens
ABPM from SAP Consulting

• Minimal data in the process context; the rest should be in Gateway
services
• Use Gateway services to call the backend service to execute data in
the backend
• UI5 frontend
• SAP Mentor Abdulbasıt Gülşen has tried this approach
Make Your Own Framework

Process Information

• Process documentation can become too much
• Need governance in progress, otherwise the documentation is outdated =
worthless
• If it becomes to difficult to update, it will not be updated
• Consider:
• Legal requirements
• Support cases--what can go wrong and how to solve the cases
• Future development with the new development team; the team’s needs
Documentation

• BPM information can be shown in the inbox to give the user more
information on what is happening
• Inbox is Fiori-style, so it has extension points
• Customize the inbox to give more information regarding the task, so
the user doesn’t need to open more of the task
Fiori Inbox

• Process can stop working if an illegal operation happens
• Use a monitoring tool to figure out what is happening
• JMS events has been added
• Listen to the JMS queue of the BPM events
• Either an application or setup at JMS communication channel on it
• SOLMAN has a monitor for failed BPM
• Must have the organization to support the processes that will fail
Monitoring

/bpmanalytics

• Gives much better opportunity to monitor what is going on
• Must be the business that requests it, it is not an IT decision
• BPM must have reporting data source to get data to process
• The auto generated data must be extended with data from the view
to select even more from the process
• Basic work can be done some what easy
• More advance development require HANA experience
OPI

Considerations

• Processes is complicated.
• The first attempt will not be correct so be flexible
• Expect that it will take longer time to get it done
• Support organization new tools can require a different set of skills to
monitor
• Short running process is best otherwise versioning should be used on
UI code
Considerations

Remember to leave your feedback
Q and A

SAP Teched 2016 best practive BPMN development

Recomendados

Recomendados

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Destacado

Destacado (15)

Similar a SAP Teched 2016 best practive BPMN development

Similar a SAP Teched 2016 best practive BPMN development (20)

Más de Daniel Graversen

Más de Daniel Graversen (20)

Último

Último (20)

SAP Teched 2016 best practive BPMN development

Notas del editor