Help Center>Foundation Help

Applies to:

  • Winshuttle Foundation

Tutorial: Creating your own vendor master solution

In this tutorial, we will show you a way to design your own Vendor Master Creation solution. We will start with a basic solution, and then extend it and add more functionality in phases.

More information

You can get more information, support articles, and training videos at Winshuttle Composer articles and videos

Products used for this tutorial

  • Winshuttle Studio: Transaction, Query, and Composer
  • Winshuttle Central
  • Winshuttle Workflow

In addition:

  • Microsoft SharePoint is used to host the solution and multiple lists used for data queries.
  • SAP connections are used for data queries.

Each phase of this tutorial also includes sample files that you can download as a reference to help you build your own solutions. These files are available on each Phase page. In addition, all samples files can be downloaded from the Downloads page.


  • This tutorial assumes at least a moderate/intermediate level of familiarity with the products listed above. We have provided specific steps for some (but not all) processes and procedures--and where applicable, links to additional help and resources.
  • This tutorial was created within a specific SharePoint/SAP environment. The sample files can be used for illustrative purposes, but will not work "out of the box" unless you configure them or your own files with data connections specific to your environment.
  • Some processes may vary slightly depending on the version of the product(s) you use.

Vendor Master tutorial overview

For the purposes of this tutorial, the basic approach for developing this solution is as follows:

Phase 1

Build the SAP automation script by recording an SAP transaction for vendor master creation. We will build a basic form and a basic workflow with this script, publish it, and then test vendor master creation.

Phase 2

Enhance the form by neatly formatting it and adding some drop-downs, fixed values, and basic rules.

Phase 3

Split the form into multiple form views, and we create multiple Swim Lanes in the workflow to allow collection of data from multiple participants.

Phase 4

Enhance the form by creating SAP lookups and SharePoint list queries. We will also add more form rules and publish fields to SharePoint.

Phase 5

Improve the workflow by adding approval loops, using a variety of participant resolvers, and creating workflow branching rules. We will also customize email messages, enable email approvals, and customize SLAs.

Phase 6

(Advanced) Improve the forms and workflow by adding named templates, manager lookup, external Web-service calls, JavaScript rules, and using one or more plugins.