Sap Business Workflow (BW) is a tool that simplifies the integration of business processes amongst applications and ensures optimization of resources via automation of business processes. For a layman, workflow is basically an approval from higher authorities to an action initiated.
The Net Weaver functionality enables the integration and management of SAP and other ERP applications across different software environment.
Workflow tracks and assigns responsibility for a multi step business process for efficient implementation, with explicit advantages relating to the optimized business processes and production.
SAP Net Weaver works on both ABAP and Java application whereas Business Workflow is based on the ABAP program in SAP and is designed for cross system workflow. Also SAP Net Weaver triggers workflow across applications connecting SAP and non-SAP systems unlike the SAP business workflow where we automate ABAP program.
The integration of SAP Net Weaver and Business Workflow provides options for workflow users to work on the workflow items on any platform via the Gateway.
This Gateway highlights the underlying functionality encompassing SAP Business Workflow and includes taking and implementing decisions.
SAP BUSINESS WORKFLOW & NET WEAVER ARCHITECTURE
Workflow architecture has three basic parts in Organization, Processes and Business Objects; the business process plays pivotal role in devising, implementing and testing Workflow.
The Net Weaver is compatible with the current SAP R/3 versions and entail minimal customization thereby ensuring adaptability and compatibility with systems. Net Weaver provides a common platform for other constituents besides applications derived from ABAP and Java and it was developed from ERP Web Application Server. Virtual Machine container permits the efficient utilization of Java applications. We could optimize the runtime by conjugation of ABAP and Java
Business Objects are critically important from the perspective of workflow. Specifically the Object types include the documents, Master data and Transaction data (the transaction code to access business objects in SAP is SW01). A link is needed to relate the events to workflow. To trigger a Workflow automatically an event is needed.
Organization structure needs to be integrated with the Workflow. Workflow assignments can be attributed to units and jobs in the organization and for scheduling the items to the concerned users/parties.
Business Workflow can be customized and the concerned transaction is SWU3.
TASK AND WORKFLOW DEVELOPMENT AND NET WEAVER
The most important tasks in Workflow are Standard, Customer and Workflow tasks along with the Work template. To create tasks it is imperative to have in hand the information about the object type, the agents and the business process to which the workflow rule could be mapped.
The Workflow container consists of system variables. Local variables could be set up in Workflow container via an editor compatible for coding purposes. The rule that defines the process of putting a selection of elements from one container to another is called a binding.
The SAP Net Weaver Developer Infrastructure entails setting up a project, coding, and testing. Once the input parameters are provided and the process is initiated the configuration steps are executed.