In this topic, we will cover the Solution Packager tool that enables partners and Software Solution Providers to create pre-packaged solutions for

Transcription

1 In this topic, we will cover the Solution Packager tool that enables partners and Software Solution Providers to create pre-packaged solutions for distribution to other partners. 1

2 This topic covers the Solution Packager tool. You will be able to: Use the Solution Packager tool to package a solution that includes an SAP Business One company database Create a new company based on a pre-packaged solution Position the Solution Packager tool compared to the Quick Copy tool. 2

3 Let us look at a business example. Auto-ssp is a Software Solution Provider (SSP) that produces and sells a micro-vertical add-on for the automotive industry. To support volume business, partners must be able to install this as a pre-packaged solution. Solution: The Solution Packager tool provided in the Implementation Center allows Auto-ssp to package the add-on together with a preconfigured company database containing item master data, user-defined fields, reports, and an embedded project plan. Partners can quickly deploy the package at a customer, and follow the project plan to fine tune the add-on. 3

4 Solution Packager is an optional tool that can be selected for install during the SAP Business One server installation. When this tool is installed with the server, the executable path is automatically entered in the Path Settings in the Implementation Center, enabling the tool to be launched from the Implementation Center. To launch this tool, choose Administration > System Initialization > Implementation Center > Implementation Tasks, then choose Package a Preconfigured Solution Using Solution Packager. Solution Packager can also be installed independently on the desktop, and can be started using the Start > All Programs menu. 4

5 A solution package consists of an SAP Business One company database together with configurations and customizations that are generic to an industry-wide or vertical solution. The concept behind Solution Packager is that Software Solution Providers (SSPs) can develop industry solution add-ons and bundle them with a preconfigured SAP Business One database. Value Added Resellers (VARs) can quickly deploy these packages at the customer, with the addition of customer-specific settings. This facilitates volume business and reduces implementation time for partners. The Solution Packager provides an easy to use wizard to create the package as a transportable file with the suffix.pak. 5

6 In a classic SAP Business One implementation, a company is created and configured individually for each new customer, usually at the customer site. The Solution Packager makes other deployment scenarios viable: In the volume scenario, a Software Solution Provider (SSP) packages a pre-configured company database and add-on, using Solution Packager. The package is sold to partners. The implementation by the partner is much faster because the partner does not have to configure the solution. Partners (VARs) can also get benefits by using Solution Packager to package horizontal solutions. A partner can package a pre-configured solution for sectors of customers with similar requirements and processes. The package can include customizations, reports, and any common add-ons. The packaging can be done remotely, saving on travel time and costs. The partner can quickly deploy the package at each customer site. This scenario is extremely useful for creating branch companies for an existing company. 6

7 Some basic differences between the Quick Copy and Solution Packager tools are shown in this slide. Quick Copy is designed for a partner to select and copy data objects from one company database to another, existing company database. Solution Packager is designed to package a complete solution including a company database. A partner can directly deploy the package as a new company. *Note this limitation - the total size of the SAP Business One and external database combined cannot exceed 2 gigabytes. 7

8 The SSP prepares an SAP Business One base company, configured to meet the generic needs of customers in that industry. This might include a chart of accounts, G/L account determination, general settings, print layouts, financial reports for the industry, customizations and installed add-ons. The SSP then uses the Solution Packager tool to create a bundled package. The SSP can even include a detailed project plan or task list for partners to follow when they deploy the package. When the package is deployed at the customer site by the VAR, a new company database is created directly from the package. This new company contains the predefined configuration from the base company, as well as the industry specific data. The partner can configure this company to meet any special requirements for each customer. The partner can change the chart of accounts in the new company, but not the localization. To distribute a solution for multiple localizations, the SSP should create a package for each localization. 8

9 When you run the Solution Packager, you first enter information describing the solution, and contact information for the vendor. You are prompted to select the SAP Business One company. You have the option to select any company database on the server as the base company for the package. 9

10 When you package the solution, in addition to the SAP Business One database, the wizard prompts you to include: External objects such as SQL scripts and stored procedures. If you have created custom SQL scripts, SAP recommends that scripts are written in Unicode to avoid any future coding problems. Split every batch of transact-sql statements (a script) by inserting a single line with the Go statement between each batch. The Go statement indicates the end of one batch. User-defined objects, tables and fields from the company database Alerts, user-defined values and queries from the company database Item groups, and associated item master data User accounts and authorizations. This makes it possible to define a job role with authorizations, that can be assigned to a user in the new company. For security reasons, when packaging users, the wizard does not copy the user password. Later, when you are creating new companies from the package, the company creator wizard sets the password of these users to be Cockpits and dashboards Reports and print layouts 10

11 Project plans related to the installation of the solution, from the Implementation Center. Other add-ons required as part of the solution. External databases required as part of the solution. The total size of the external database and the SAP Business One database must be less than two gigabytes; otherwise, the packaging may fail. You may not package an encrypted database. 11

12 To create a new company based on a solution package, choose New From Package in the Choose Company screen. Make sure that the version of the Microsoft SQL Server you select here is not lower than the version used for the original packaging. 12

13 Follow the wizard steps to select the components from the package. The first step is the select the.pak file which was built by the Solution Packager wizard and provided to you by the SSP. 13

14 Verify the solution and vendor information from the package file. 14

15 Specify a name for the new company that will be created. 15

16 You can select a different chart of accounts from the one in the package. Note that if you select a different chart of accounts template, you should verify the G/L account determination from the package and make any changes for the new accounts. 16

17 At this point, the wizard follows the normal process for creating a new company, and you can define the posting periods. 17

18 If the solution package contains an external database, you can create a database in addition to the SAP Business One database. The default database name is the name provided in the package, but you can change it. If an external database was not packaged for the solution, this step displays No external database exists for this package. Note: If earlier in the Choose Company window, you specified a remote SAP Business One server, then in this step, the External Database Name field is disabled. You need to deploy the package using the new company wizard on the SAP Business One server machine, so that you can create the external database. 18

19 Now the standard process of creating the new SAP Business One company starts, and the tables are created. When user accounts are packaged, the default password for each user (except for the user "manager") is set to "1234". When the users are re-created in the newly created company, the users are locked by default for security reasons, and you must manually unlock them. Error messages may be logged in the System Messages area during the creation of tables in the new company. 19

20 Here are some key points to take away from this topic. Solution Packager allows a Software Solution Provider to package a vertical-industry solution consisting of a company database with stored procedures, external databases, add-ons, and other customizations. A partner can deploy a new company directly from the package. SSPs can use Solution Packager to package a vertical solution for volume deployment by VARs. Partners (VARs) can also benefit by using Solution Packager to package horizontal solutions, such as creating branch companies for an existing company. The packaging can be done remotely, saving on travel time and costs. Solution Packager is one of the implementation tools provided in the Implementation Center. To launch this tool, choose Administration > System Initialization > Implementation Center > Implementation Tasks. You can also install Solution Packager on the desktop and launch it using the Start > All Programs menu. 20

21 You have completed the topic for the Solution Packager tool in SAP Business One. Thank you for your time! 21