Combining Embedded and Unbounded Processes 

You can combine the use of embedded processes and unbounded processes in SAP applications:

●     Integration processes for the automation of processes beyond application and system boundaries

●     SAP Business Workflows for the automation of processes within SAP applications

Advantages

By combining integration processes and workflows, you can benefit from the advantages of both types of processes:

●     Adaptability

You define and configure integration processes and interfaces in a central repository. This allows you to adapt integration processes in line with any changes in conditions, such as an exchange of software components, a change in business partner or changes in the underlying business processes. You avoid high-maintenance point-to-point integration and can react quickly to changes in heterogeneous system landscapes.

●     Integration

SAP Business Workflows are very closely integrated with SAP applications. This enables you to make full use of the benefits and potential of SAP applications. As a customer you can use the same platform and underlying software for the choreography of your processes that SAP business suites use for their automated embedded processes.

●     Reuse of process logic

By combining embedded and unbounded processes, you can reuse existing process logic instead of having to recreate it. This allows you to avoid unnecessary expense.

●     Reduced costs

The model-driven approach and central repository ensure transparency and more efficient maintenance. This enables you to keep costs at a minimum without losing out on adaptability or functionality.

Required or Optional Installable Units

To use this IT scenario you require the following installable units:

System with activated usage types:

●     Process Integration (XI)

●     Application Server ABAP (AS ABAP)

●     Application Server JAVA (AS JAVA)

●     Enterprise Portal (EP)

Application Example

You can use the processes of this variant for the following business application case, for example:

A business trip for multiple employees is to be booked in a travel booking system. The business trip must be approved by each of the employee’s managers. A travel request must therefore be generated for each employee and then sent to the relevant manager.

IT Processes of the Scenario Variant

This scenario variant comprises the following IT processes:

Process	Description
Executing Embedded Processes	The flight booking is created and the travel booking system sends a message to the integration process.
Handling Messages	The integration process splits the message and creates a message for each employee as appropriate. The integration process then sends the individual messages to the application system and starts a workflow for each employee.
Dispatching to Users	Each workflow creates a corresponding work item for the approval process in the Universal Worklist (UWL) of the Enterprise Portal.
Executing a Task	The manager processes the work item by approving or rejecting the request.

See also:

For more information about this application example of integrating SAP Business Workflows and integration processes, see SAP Service Marketplace at service.sap.com/nw-howtoguides  → Cross-Component Technical Scenarios.