license guide - sap balance report full full profit and loss report full full financials document...

Solutions from SAP SAP Business One 2005 A SP01

License Guide June 2006

SAP Business One 2005 A SP01 License Guide

June 2006 of 29

Contents

Introduction ............................................................................................................................................ 3 Architecture ........................................................................................................................................ 3

Licensing Options ........................................................................................................................... 4 Application License......................................................................................................................... 4 SDK License ................................................................................................................................... 8 Add-On Solution License ................................................................................................................ 8 DI Server License ........................................................................................................................... 8

License Setup ........................................................................................................................................ 9 License Components for the 2005 Release ....................................................................................... 9

Available Components .................................................................................................................... 9 Partner solutions ............................................................................................................................. 9 Limitation of SAP Business One License Key .............................................................................. 10 Returning Unused Licenses.......................................................................................................... 10 Reassigning Users........................................................................................................................ 10 Shutting Down a SAP Business One System............................................................................... 10

Installing the License Service........................................................................................................... 10 Installing a License Key.................................................................................................................... 10

Step 1: Get your Hardware Key.................................................................................................... 11 Step 2: Request a License Key .................................................................................................... 11 Step 3: Install the License Key File............................................................................................... 11

Changing the Hardware Key ............................................................................................................ 13 Generating Add-On Solution Licenses ............................................................................................. 14 Single Sign-On ................................................................................................................................. 15

License Administration ......................................................................................................................... 16 Allocating licenses ............................................................................................................................ 16 Viewing License Information ............................................................................................................ 17 Changing the License Server ........................................................................................................... 17 Importing a New License File ........................................................................................................... 17 Connecting Multiple Systems to a Single License Server................................................................ 18 Frequently Asked Questions ............................................................................................................ 19 License-Related Errors..................................................................................................................... 23 Further Information ........................................................................................................................... 25 Copyright .......................................................................................................................................... 26


June 2006 of 29

Introduction This document describes the SAP Business One licensing options, mechanism, installation, and administration.

Architecture The license mechanism in SAP Business One is implemented using a License Service, a License File, and an external API. • License Service – manages license requests and can be installed on any computer in the

organization.

Do not activate a firewall on the machine on which the license service is installed.

• License File – generated by SAP upon request and contains your purchased licenses and other relevant information.

• External API – allows partners and third-parties to retrieve information from the License Service using a public interface. Release 2005 introduces an expanded API and a sample program. For more information, refer to the SDK Help Center.

The SAP Business One workstations read the name of the license service to which they connect from the SLIC table in the SBO-Common database. All Company database sharing an SBO-Common database will use the same license file. In addition, several SBO-Common databases can direct to the same license service. For example, if a user John has a Professional license in Company X, he will have the same license on any other Company database connected to the same license service.

SAP Business One License Mechanism


June 2006 of 29

Licensing Options Under the new model, SAP Business One offers four different licensing options:

• SAP Business One application license • SAP Business One SDK license • Add-on solution license • DI Server license

The packaging of SAP Business One is not connected to this licensing model. It is your responsibility to make sure that a specific package contains all the required functionality.

Application License Licensing of the SAP Business One application uses a named-user model. Under this model, license for the application is allocated per user name. Each user can get one of the following licensing options:

• Add-On Basic – includes forms that do not require a license key. For example, Master Data. • CRM-Sales – Sales Opportunities and Contact Management modules • CRM-Service –Service Management module • Professional – includes all the functions in the SAP Business One application

The Add-On Basic license is not included in The CRM Sales or the CRM Service licenses. For example, creating and editing Chart of Account, which is included in the Add-On Basic, is not available for CRM Sales or CRM Service users.

The licensing options are not connected to a specific Company database. This means that a user with a Professional license, for example, may log on to any Company database with the same username and have the same license. Using the same username, you can log on up to twice to the same Company database. Depending on the license option, a user may have:

• No Access – the user cannot open the form. The application displays a no access to the form message.

• View – the user can open the form in read only mode – the form appears disabled. • Full – the user can open the form and perform any action.


June 2006 of 29

License Comparison Chart The following chart details the access rights of each license option. Use this chart to plan the number of licenses you need from each option.

Module/Functionality Add-On Basic

CRM-Sales

CRM-Service

Professional

Choose company Full Full Full Full

Managing foreign currencies exchange rates

Full

System initialization Full

Change Password Full Full Full Full

Authorizations Full

System definitions Full

Define user Full

Define opportunities partners Full Full

Define opportunities competitors Full Full

Define opportunities Relationships Full Full

Edit Chart of Accounts Full Full

Approval procedures Full Full Full

Approval procedures Reports Full Full Full

Alerts management Full Full Full Full

Administration

Messages/Alert Overview Full Full Full

Creating and editing chart of accounts Full Full

Creating journal entries and vouchers Full

Creating posting templates and recurring postings

Full

Creating reverse transactions Full

Managing exchange rate differences and conversions in journal entries

Full

Editing financial report templates Full

Managing budgets Full

Costing Full

Financial reports Full

Balance Sheet Report Full Full

Trial Balance Report Full Full

Profit and Loss Report Full Full

Financials

Document Journal Report Full Full


June 2006 of 29


CRM-Sales

CRM-Service

Professional

Sales opportunities Full Full Full Sales Opportunities

Generating sales opportunities reports Full Full Full

Creating All sales documents Full

Sales Quotations Full Full Full

Sales Order Full View Full

Delivery View Full Full

Returns View Full Full

Down Payment Requests View Full

Down Payment Invoice Full Full

Invoice View View Full

Invoice Payment Full View Full

Credit Memo View View Full

Reverse Invoice View View Full

Sales Reports Full Full

Alternative items selection Full Full Full

Change layout for document Full Full Full

Open items list Full Full Full

Sales – A/R

Document Printing Full Full Full

Creating All purchasing documents Full

Purchase order Full Full Full

Purchase report Full Full

Open items list Full Full Full

Purchasing – A/P

Landed costs Full Full

Entering business partners data Full Full Full Full

Activities Full Full Full Full

Business partners reports Full Full Full

Business Partners

Calendar Full Full Full Full

Handling incoming and outgoing payments

Full

Depositing checks and credit card vouchers

Full

Reconciling bank statements Full

Internal reconciliation Full

Credit Cards management Full

Banking

Checks management Full


June 2006 of 29


CRM-Sales

CRM-Service

Professional

Managing Bills of Exchange Full

Automatic creation of payments Full

Entering item data Full Full Full Full

Creating serial numbers and batches Full

Creating and updating price lists Full

Inventory transactions Full

Stock counting Full

Pick and Pack Full

Inventory

Inventory reports Full Full Full

Defining BOM Full Full

Creating and processing production orders

Full Full

Updating parent item prices Full

Production

Production reports Full Full Full

Defining production forecasts Full

Generating recommendations production orders and purchase orders automatically

Full

MRP

Recommendation report Full

Creating and processing service calls View Full Full

Tracking equipment View Full Full

Creating service contracts View Full Full

Building solutions knowledge base Full Full

Service

Service reports Full Full Full

Entering employees data Full Full Full Full HR

HR reports Full

Reports Generating queries by user demand Full Full Full

Advanced search Full Full Full Full

User-defined fields Full Full

User-defined tables Full Full

User Menu Full Full Full Full

User shortcuts Full Full Full Full

Form Settings Full Full Full Full

Message Alerts Full Full Full Full

General

Drag & Relate Full Full Full Full


June 2006 of 29

SDK License The new SDK license employs a concurrent model (first-come, first-served). Under this model, there are two licensing options for the SAP Business One SDK.

Development License This license is required for partners developing add-ons and the only license allowing distribution. In Development license, the license key is shared by all developers connected to the same License Service. The License Service allocates licenses on the basis of first-come, first-served. The Development license includes both the UI API and the DI API.

Implementation License This license is required for customers intending to develop small modifications or add-ons for their own use using only the UI API. Add-ons developed under the Implementation license cannot run with a different License Service other than the one that was used for their development. The Implementation license does not allow distribution to third-parties. In the Implementation license, the license key is shared by all developers connected to the same License Service. The License Service allocates licenses on the basis of first-come, first-served.

Add-On Solution License This license is required for distributing add-ons to customers. The add-on solution license uses a named-user model – licenses are allocated per user name. Each add-on is distributed with its own unique solution license.

Compatibility License A special Compatibility license is required for running add-ons developed by previous versions of the SAP Business One SDK. The Compatibility license is valid until January 17, 2007. After this date, you must recompile your add-on with a current version of SAP Business One SDK to continue running the add-on. The Compatibility license uses a concurrent model – licenses are allocated to users on the basis of first-come, first-served.

DI Server License This license is required for running the SAP Business One Data Interface Server (DI Server). The DI Server is a COM service running on a server that enables multiple clients to access and manipulate SAP Business One company database, using SOAP messages. The DI Server enables the same functionality as provided by the DI API, but for multiple concurrent connections. The DI Server license employs a concurrent, unlimited model. The number of licenses is determined by the number of CPUs in the DI Server. Each CPU requires one DI Server license. Note that, if you have four CPUs and only two licenses, the DI Server will run on two CPUs only, the other CPUs will be blocked. The number of users that can connect to a single DI Server license is unlimited and should be determined based on the expected performance of the system.


June 2006 of 29

License Setup In-line with legal and contractual agreements for SAP Business One software, you can only operate the SAP Business One application in conjunction with a license key assigned by SAP. This section describes the process of applying for and activating a permanent license key for new or existing installations of SAP Business One. For more information about license administration and management, see the online help.

License Components for the 2005 Release You have contractually licensed the components for which you want to request a license key.

Available Components You can request a license key for the following components: • Professional users • CRM Sales users (standalone) • CRM Service users (standalone) • Software development kit – development version • DI Server • Proprietary solutions (partner solutions) • Other partner solutions

You do not need to request a separate license key for the components listed in the following table, because you receive them automatically with your request for Professional users.

Component Number of Users Validity Date

SAP add-ons 99999 December 31, 9999

Software development kit – implementation version

99999 December 31, 9999

SDK tools 99999 December 31, 9999

Compatibility license for add-ons 99999 January 17, 2007

Partner solutions Request a license key and the number of users you need for your installed partner solution(s) on the SAP Service Marketplace by selecting the solution(s).

The total number of users you request for the partner solutions must not exceed the number of add-on access license users you have contractually licensed.


June 2006 of 29

Limitation of SAP Business One License Key SAP issues a time-limited license key (two weeks or to the contract end date) when your license key request exceeds the license you have purchased by: • The number of users • Your contract end date • Modules for which you have not bought a license

Returning Unused Licenses You can return to SAP licenses that are no longer in use by posting a request in the SAP Service Marketplace.

1. At http://service.sap.com/sbo-licensekey, choose SAP Solutions for SMB.

2. Choose Request License Key and the corresponding installation number.

3. Choose the icon next to the system you want to change.

4. In the following screen, modify the number of users in the appropriate field.

5. Choose Submit to post the request. You will receive a new license key file from SAP.

6. Import the new file, as described in Step 3: Install the License Key File.

Reassigning Users You can reassign users to another computer or to a new installation number. Fist shut down the existing SAP Business One system under the old installation number (see, SAP Note 596562). Request a license key for the new installation number at http://service.sap.com/sbo-licensekey. SAP will send you a new license key by e-mail. Note that in any reassignment of users, the number of users cannot exceed the number of your licensed users.

Shutting Down a SAP Business One System You can shut down a SAP Business One system that you no longer use. For more information, see SAP Note 614911.

Installing the License Service The License service is installed as part of the Server Tools package. For detailed installation instructions, refer to the SAP Business One Installation Guide pertinent to your database server.

Installing a License Key To run SAP Business One permanently, you must install a license key assigned by SAP. In addition, you will have to install a new license key each time when:

• Requesting additional users or components • Hardware key has changed.

This can occur when changing the computer domain (including removing from the domain and adding it back) or when changing the host name.

• License key has expired


June 2006 of 29

New installations of SAP Business One Product version receive an automatic 31-days Evaluation license. If you choose to use the Evaluation license, you can see the number of remaining days until expiration on the application status bar.

Step 1: Get your Hardware Key 1. From SAP Business One → Server Tools, choose Service Manager.

2. In the Service Manager, select the License Manager 2005 option and make sure that the service is running (the Start button is disabled, while the Stop button is active).

3. Choose Settings and copy the number appearing in the Hardware Key field. Alternatively, you can get the hardware key from the SAP Business One application Help → About menu.

4. Continue with Step 2: Request a License Key.

Step 2: Request a License Key Partners that have special authorizations can request a license key only in the SAP Service Marketplace. For more information, see SAP-Notes 124703 and 103926.

1. Choose Request License Key and select your installation number. • For existing systems, choose Change System Details next to the system you want to

change and modify the required data. • For new installations, choose Request New System and enter the required information to

complete the request including: • Hardware key (see Step 1) • System type • Database type • Operating system • Number of users per component/add-on • E-mail address

2. Choose Submit to post the request. You will receive a license key file by e-mail. You can also download the license key file from the SAP Service Marketplace (service.sap.com/licensekey).

3. Continue with Step 3: Install the License Key File.

Step 3: Install the License Key File After getting your license key file, install it to activate your license.

You can also install the license key file using the License Administration window (Administration → License → License Administration). See the online help for more information.


June 2006 of 29

1. Make sure that the license service is running. If not, start it in the Service Manager or Windows Services.

2. From the Service Manager, select the License Manager 2005 service and choose Settings.

3. Under Install License File, choose and then locate and select your license key file.

4. Choose Import License File. An “Install Succeeded” message indicates a successful import. If the “Server is in startup mode try again in two minutes” message appears, wait two minutes and then try to import the file again.

5. To allocate licenses to users. See, Allocating licenses.


June 2006 of 29

Changing the Hardware Key Changing the hardware key of the license service machine results in an invalid license file that you can activate only after getting a new license file. To avoid changing the hardware key accidentally, do not perform the following actions on the license service machine: • Formatting the machine and reinstalling Windows. • Changing computer name. • Changing the domain (hardware key will not change back when returning to the previous domain) • On Linux machines, changing the network card.

The following actions are safe and will not change the hardware key: • Adding a new user login. • Adding memory or a new hard disk • Changing the computer date or time • Changing the machine IP.


June 2006 of 29

Generating Add-On Solution Licenses To run add-ons in SAP Business One 2005, the add-ons must be recognized by the License Service. This is done by creating an Add-On Identifier – a unique string identifying each add-on. In run-time, the add-on passes the identifier to the SDK during connection. The identifier that is passed determines which license will be used when the add-on is running. For example, if you pass a Development identifier, your add-on will require an SDK-Development license.

Using a Compatibility license, you can run add-ons developed in previous versions of the SAP Business One SDK. The Compatibility license is valid until January 17, 2007. After this date, you must recompile your add-on with a current version of SAP Business One SDK to continue running the add-on.

The Compatibility license is included in your Professional user licenses.

To generate an add-on identifier: 1. From Administration → License, choose Add-On Identifier Generator.

2. Choose the type of identifier you need:

• Development – to run add-ons under the SDK Development license • Implementation – to run add-ons under the SDK Implementation license • Solution – to run add-ons at customer sites (distribution). Before running the add-on, make

sure you allocate the license to users. See, Allocating licenses. Enter the License Key Name in the following format: BASIS########## (10 digits, case-sensitive, without the database extension). You can generate a solution identifier only if you have a License Key Name and a license file that includes an SDK Development license. The License Key Name is requested separately from SAP in the SAP Service Marketplace.

3. Choose Generate to generate the add-on identifier string.

4. Copy the identifier string to your code and make sure to set the AddonIdentifier property before you call the Connect method. For complete coding samples, see UI API and DI API help files and samples.


June 2006 of 29

Single Sign-On If you are developing an add-on using both the UI API and the DI API, there is no need to set the AddonIdentifier property twice. Instead, you can set the identifier string before calling the Connect method of the UI API. The single sign-on mechanism will pass the identifier to the DI API as well.


June 2006 of 29

License Administration The SAP Business One application allows you to easily manage and allocate licenses to users. License administration includes allocating licenses to users, viewing information form the current license file, importing a new license file, and modifying the license server.

Allocating licenses Allocate license in the Allocation tab of the License Administration window (Administration → License → License Administration).

Allocating licenses requires Superuser permissions in the SAP Business One application.

To allocate licenses:

1. Make sure all users are logged off from the SAP Business One application. You will not be able to allocate or modify licenses to logged-on users. Logged on users appear disabled on the list.

2. Choose the Lock icon to prevent users from connecting to the license service during allocation. Other administrators will be able to continue allocating licenses.

3. Choose Refresh to get the most recent status of available licenses.

4. In the Allocation tab, select the user you want and choose the required license under the Used column. • Users column – displays users defined in the Company to which you are logged. • Licenses column – displays the licensing options, which need to allocated to users. • Available column – displays the number or remaining licenses for each option.

5. Choose Update to save your settings. If you get the message “Data not Updated”, another administrator has updated the license allocation before you. Choose Refresh and reassign licenses.


June 2006 of 29

Viewing License Information You can view information from your current license file on the Components tab of the License Administration window.

From the Licenses list, select a license. Information for each option includes: • Total number of licenses • Number of available licenses • Begin and expiration date

Changing the License Server In the License Administration window, you can modify the license server machine by choosing Browse and selecting the required machine from the window that opens. Changing the license server affects all Company databases connected to this server. The change will be reflected upon the next log on to the company.

Do not change the default port 30000, unless you have a specific use for it. To change the License Server port, open the License Manager Settings window in the Service Manager: 1. Enter the new port and choose Set. A message appears indicating success or failure. 2. Log on to SAP Business One, the License Server Selection window appears. 3. Update the new port.

Importing a New License File The License Administration window lets you import a new license file. You will not be able to import a new file, while the DI Server is running. To import a new license file, choose Import License File, then locate and select the file you want from the window that opens.


June 2006 of 29

Connecting Multiple Systems to a Single License Server You can connect several SAP Business One systems (for example, a full product system and a demo system) to the same License Server. Any system that you connect to this License Server will run the same license service and will share the same license file. To set multiple systems:

1. After installing a subsequent system, log on to the required Company database. • If the system is already set with a License Server, it logs on using that server. Continue

with Step 2. • If the system is not set with a License Server, a window appears prompting you to enter

or select a License Server. Enter the computer name or IP address of the current License Server.

The system logs on using the license file that is installed on the current License Server.

2. In the application main menu, choose Administration License License Administration.

3. In the License Administration window, enter the computer name or IP address of the current License Server.

4. Choose OK to save your settings and exit from the application.

5. Log on again to the Company database. The system logs on using the license file that is installed on the current License Server.

6. You can repeat this procedure with as many systems as you want, each time select the same License Server. The only limitation is the number of licenses in your license file.


June 2006 of 29

Frequently Asked Questions Q: How long after installation can I continue to use Business One without a license key? Answer: For new installations, the system can be used for a period of 31 days after the first posting without a license key. This 31-day period cannot be extended. After the end of this period, you will no longer be able to access the system. You should request a permanent license key as soon as possible. For more information on the requesting process, see SAP Note 578256.

Which authorization do I need to request a license key for my customer? If you are an SAP partner and would like to request a license key for one of your customers, you will need an S-user with the authorization "license key request for SAP partner". For further information, see SAP Notes 124703 and 103926.

When do I have to request a new license key for my Business One system? • If your hardware key has changed • If the number of users has changed • If the license expiration date has changed • If components (add-ons) have changed • If you upgraded your system from release 6.x to release 2004

How can I request a Business One license key? Request your license key using SAP Service Marketplace from http://service.sap.com/sbo-licensekey, choose SAP Solutions for SMB, choose request license key. You can find more information on requesting license keys in SAP Note 578256.

Who should request license keys? License keys should be requested by the SAP partner. Prerequisite for requesting a license key is a S-user and the authorization for the partner "License key request for SAP partner" for the corresponding installation number. Only in exceptional cases if an end-customer should not have an SAP partner the license key can be requested by the customer itself. For further information, see SAP Notes 124703 and 103926.

What should I do if I have mistakenly requested a license key for a new system instead of a license key for an existing system? Delete the systems that were requested repeatedly as described in SAP Note 614911. Afterwards you can request the new license key for the existing system using SAP Service Marketplace from http://service.sap.com/sbo-licensekey, choose SAP Solutions for SMB , choose request license key. You can find more information on requesting a license key in SAP Note 578256.

What should I do if I requested a license key using an incorrect installation number? The system ordered using the incorrect installation number should be deleted and re-requested using the correct installation number on the SAP Service Marketplace. The deletion process is described in SAP Note 614911.


June 2006 of 29

How do I receive the license key from SAP? The license key is sent to you in an e-mail message. Once you have received the license file, copy it onto your computer. Then restart SAP Business One. When the license query appears, add the license file to it. You can also download the license key in SAP Service Marketplace under the Internet address service.sap.com/licensekey choose SAP Solutions for SMB. For further information, see SAP Note 742024.

How can I change the file extension of the file attached to the mail from .txt.to lic.? You must save the file locally on your computer before you change the extension. You must NOT change the content of the file.

Why is my license key only temporary? If you request a license key for more users than you have licensed or for non-licensed components or your contract or hardware data are limited, you receive a license key that expires after 14 days. Request a license key with less user or contact your local SAP contracts department. For further information, see SAP Note 765296.

How can I return users that are no longer needed to SAP? To return users to SAP:

1. Request a new license key with a reduced number of users for the existing system 2. SAP generates a new license key 3. You receive the new key in an e-mail message. You can also download it from the SAP

Service Marketplace. The users returned to SAP can then be used for other Business One systems. The maximum number of users for all systems must not exceed the number of licensed users specified in the contract. For further information, see SAP Note 596562.

How can I delete a Business One license key, also when S-user is unknown? The deletion process is described in SAP Note 614911. When S-user is unknown, see SAP Note 781853.

For which components of Release 2005 can I request a license key, which components are automatically included? You can request a license key for the following components: Professional User, CRM Sales User (standalone), CRM Service User (standalone), Software Development Kit (development version), DI Server, Proprietary Solutions (partner solutions), and other Partner Solutions. Note that you do not need to request a separate license key for the following components because you receive them automatically with your request for Professional Users: SAP Add-Ons, Software Development Kit (implementation version), SDK Tools, and Compatibility License for Add-Ons (valid until January 17, 2007).

Which features do I have to notice by requesting a license key for an existing system upgraded from release 6.x to release 2004?

You should request the according number of Professional Users and should not change the Business One users; they will be deleted when the license key is assigned.

What are the prerequisites for requesting a license key for partner solutions? If you want to request a license key for partner solution, Add-On Access Users have to be booked in your contract. If these users have not been booked, contact your local contract department.

https://websmp203.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=596562&




June 2006 of 29

What shall I do when I get the error message "this form is not a part of my software package" after installing the license key? The licenses have to been assigned to the users. For more information, see our documentation SAP Business One, chapter 5.

How many users can connect to a single DI Server license (one CPU)? The DI Server uses a concurrent, unlimited license model. This means that an unlimited number of users can access the same DI Server add-on for an unlimited number of times. The only limitation is the expected performance of the add-on.

Which type of SAP Business One users can run add-on solutions? All SAP Business One users (Basic, CRM-Sales, CRM-Service, and Professional) can run add-on solutions, provided that an add-on license has been assigned to them. However, if the add-on uses functionality that is not part of the Basic, the user must be licensed to that functionality. See the License Comparison Chart for details. Add-on solution licenses must be acquired separately.

How many times can I access the application with a single Basic, CRM-Sales, CRM-Service, or Professional license? With the same user name, you can access the same Company database up to twice.

How many times can I access an add-on with a single add-on license? With the same user name, you can access the same add-on for unlimited number of times.

If the customer uses several different add-on solutions at the same time, does the customer need add-on access user per add-on solution? Yes, Add-On Access license is a named license that must be assigned to a specific user.

Is Add-On Access License same as Add-On Basic License? Yes.

Is the Add-On Access License free of charge? No, you need to buy a specific add-on access license in order to use third-party add-ons.

Can SAP Business One Add-Ons be used free of charge? Yes, no additional license is required. This is included in SAP Business One license fee.

Does user through DI-server need add-on access license? No.

Does user through DI-server need add-on license? No.

Does user through DI-Server need application license according to the use of functionality? No.

In the following scenario, what and how many licenses do partner have to propose to the customers?

https://websmp203.sap-ag.de/~sapidb/011000358700008786992004E

https://websmp203.sap-ag.de/~sapidb/011000358700008786992004E


June 2006 of 29

A company has three employees. The company will get an ERP proposal from SAP Business One Partner. SAP Business One partner needs to propose three add-on solutions to meet the customer's requirement. All three employees need to use all the functions including all three add-on solutions. 3 Professional users, 3 Add-On Access users.


June 2006 of 29

License-Related Errors When importing a license file:

Error Message Description

Wrong license file; hardware key does not match.

The hardware key in the license file is not the same as the hardware key of the license service.

Hardware key is not the same in all modules.

Hardware key, Installation Number, or System number is not the same in all licenses in the license file.

DI Server is connected. When the DI service is running you cannot import a license file. Stop the DI service, wait three minutes and try again.

File is corrupted. The license file has been tampered with and the digital signature is ruined.

Connecting to SAP Business One:


License server is initializing. Wait one minute before reconnecting.

License Service was started, wait one minute and try to connect again.

Cannot log on; the user is already connected to the same company.

A user cannot connect more than twice to the same company. Connect with a different user name, or if previous application terminated, wait 3 minutes and try to connect again.

License server is locked by an administrator. Server is un accessible until unlocked or License server is being configured; cannot connect.

An administrator has locked the license service (through the license administration window). Cannot connect until the license service is unlocked.

Generating an Identifier:


No License. Cannot create a Solution Identifier if there is no license for SDK-DEV.

Connecting with Add-On:


License server is initializing. Wait one minute before reconnecting.

License Service was started, wait one minute and try to connect again.

License is fully used. Indicates that all licenses are in use (relevant to a concurrent license model).


June 2006 of 29


License does not exist. The relevant license does not exist in the license file. (For example, if you try to run an add-on that uses compatibility license and there is no such license in the license file).

License server is locked by an administrator. Server is un accessible until unlocked.

An administrator has locked the license service (through the License Administration window). Cannot connect until server is unlocked.

License Expired Each license has an expiration date. The license cannot be used after this date. Request a new license key.

The user is not licensed When running an add-on that uses a solution (partner) license and the user has not been assigned that license.

This Form is not included in the software package you have purchased.

The user has not been assigned a license to open a certain form. Use the License Administration window to assign a license to the user.

Add-on Identifier is invalid The string passed via the AddonIdentifier property is wrong. Create the string again.

You can find additional error message information at http://support.microsoft.com, article ID 186063.

http://support.microsoft.com/


June 2006 of 29

Further Information You can get more information at service.sap.com/licensekey and service.sap.com/smb. To access all relevant SAP Notes on SAP Business One license key: go to service.sap.com/notes and choose the component SBO-BC-LIKEY in the Application Area, then choose Search. Overview of SAP Business One License Key Notes: 622998 – Frequently asked questions about SAP Business One 561588 – The License Process in SAP Business One 574385 – SAP Business One: Installation check 578256 – Online request for license key for SAP Business One 596562 – Returning SAP Business One user licenses 614911 – Deleting SAP Business One systems


June 2006 of 29

Copyright © Copyright 2005 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SQL Server® is a registered trademark of Microsoft Corporation.


June 2006 of 29

WinFax® is a U.S. registered Trademark from Symantec Corporation. Sybase and SYBASE (logo) are trademarks of Sybase, Inc. Intel and Intel JPEG Library are trademarks of Intel, Inc. SEE4C (SMTP/POP3 Email Engine Library for C/C++) is the copyright of - MarshallSoft Computing, Inc. Victor Image Processing Library and VIC32 are trademarks of Catenary Systems. The Victor Image Processing Library is copyright material. This includes the source code, object code, dlls, examples, and documentation. This material is protected by United States copyright law as well as international copyright treaty provisions. THE APACHE SOFTWARE LICENSE, VERSION 1.1 Copyright (c) 1999 The Apache Software Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

• Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

• The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.

• The names "Xerces" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact [email protected].

• Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This product includes software developed by the Apache Software Foundation (http://www.apache.org/) and Info-Zip (http://www.info-zip.org/pub/INFO-ZIP/). This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, International Business Machines, Inc., http://www.ibm.com. For more information on the Apache Software Foundation, please see <http://www.apache.org/>. SAP and/or its distributors may offer, and charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of the software. However, SAP and/or its distributors may do so only on its/their own behalf, and not on behalf of the Apache Software Foundation or its contributors.

http://www.apache.org/)

http://www.apache.org/

http://www.info-zip.org/pub/INFO-ZIP/


June 2006 of 29

UNZIP. This is version 2003-May-08 of the Info-ZIP copyright and license. The definitive version of this document should be available at ftp://ftp.info-zip.org/pub/infozip/license.html indefinitely. Copyright (c) 1990-2003 Info-ZIP. All rights reserved. For the purposes of this copyright and license, "Info-ZIP" is defined as the following set of individuals: Mark Adler, John Bush, Karl Davis, Harald Denker, Jean-Michel Dubois, Jean-loup Gailly, Hunter Goatley, Ian Gorman, Chris Herborth, Dirk Haase, Greg Hartwig, Robert Heath, Jonathan Hudson, Paul Kienitz, David Kirschbaum, Johnny Lee, Onno van der Linden, Igor Mandrichenko, Steve P. Miller, Sergio Monesi, Keith Owens, George Petrov, Greg Roelofs, Kai Uwe Rommel, Steve Salisbury, Dave Smith, Christian Spieler, Antoine Verheijen, Paul von Behren, Rich Wales, Mike White This software is provided "as is," without warranty of any kind, express or implied. In no event shall Info-ZIP or its contributors be held liable for any direct, indirect, incidental, special or consequential damages arising out of the use of or inability to use this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: Redistributions of source code must retain the above copyright notice, definition, disclaimer, and this list of conditions. Redistributions in binary form (compiled executables) must reproduce the above copyright notice, definition, disclaimer, and this list of conditions in documentation and/or other materials provided with the distribution. The sole exception to this condition is redistribution of a standard UnZipSFX binary (including SFXWiz) as part of a self-extracting archive; that is permitted without inclusion of this license, as long as the normal SFX banner has not been removed from the binary or disabled. Altered versions--including, but not limited to, ports to new operating systems, existing ports with new graphical interfaces, and dynamic, shared, or static library versions--must be plainly marked as such and must not be misrepresented as being the original source. Such altered versions also must not be misrepresented as being Info-ZIP releases--including, but not limited to, labeling of the altered versions with the names "Info-ZIP" (or any variation thereof, including, but not limited to, different capitalizations), "Pocket UnZip," "WiZ" or "MacZip" without the explicit permission of Info-ZIP. Such altered versions are further prohibited from misrepresentative use of the Zip-Bugs or Info-ZIP e-mail addresses or of the Info-ZIP URL(s). Info-ZIP retains the right to use the names "Info-ZIP," "Zip," "UnZip," "UnZipSFX," "WiZ," "Pocket UnZip," "Pocket Zip," and "MacZip" for its own source and binary releases. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Copyright and Licensing Information for ACE(TM) and TAO(TM) ACE(TM) and TAO(TM) are copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine, and Vanderbilt University Copyright (c) 1993-2003, all rights reserved. Since ACE+TAO are open-source, free software, you are free to use, modify, copy, and distribute--perpetually and irrevocably--the ACE+TAO source code and object code produced from the source, as well as copy and distribute modified versions of this software. You must, however, include this copyright statement along with code built using ACE+TAO. You can use ACE+TAO in proprietary software and are under no obligation to redistribute any of your source code that is built using ACE+TAO. Note, however, that you may not do anything to the ACE+TAO code, such as copyrighting it yourself or claiming authorship of the ACE+TAO code that will prevent ACE+ TAO from being distributed freely using an open-source development model. You needn't inform anyone that you're using ACE+TAO in your software, though we encourage you to let us know so we can promote your project in the ACE+TAO success stories.. ACE+TAO are provided as is with no warranties of any kind, including the warranties of design, merchantability, and fitness for a particular purpose, noninfringement, or arising from a course of

http://www.cs.wustl.edu/~schmidt/ACE.html

http://www.cs.wustl.edu/~schmidt/TAO.html

http://www.cs.wustl.edu/~schmidt/

http://www.cs.wustl.edu/~schmidt/ACE-members.html

http://www.wustl.edu/

http://www.uci.edu/

http://www.vanderbilt.edu/

mailto:[email protected]

http://www.cs.wustl.edu/~schmidt/ACE-users.html


June 2006 of 29

dealing, usage or trade practice. Moreover, ACE+TAO are provided with no support and without any obligation on the part of Washington University, UC Irvine, Vanderbilt University, their employees, or students to assist in its use, correction, modification, or enhancement. However, commercial support for ACE is available from Riverace and commercial support for TAO is available from OCI and PrismTech. Both ACE and TAO are Y2K-compliant, as long as the underlying OS platform is Y2K-compliant. Washington University, UC Irvine, Vanderbilt University, their employees, and students shall have no liability with respect to the infringement of copyrights, trade secrets or any patents by ACE+TAO or any part thereof. Moreover, in no event will Washington University, UC Irvine, or Vanderbilt University, their employees, or students be liable for any lost revenue or profits or other special, indirect and consequential damages. The ACE and TAO web sites are maintained by the Center for Distributed Object Computing of Washington University for the development of open-source software as part of the open-source software community. By submitting comments, suggestions, code, code snippets, techniques (including that of usage), and algorithms, submitters acknowledge that they have the right to do so, that any such submissions are given freely and unreservedly, and that they waive any claims to copyright or ownership. In addition, submitters acknowledge that any such submission might become part of the copyright maintained on the overall body of code, which comprises the ACE and TAO software. By making a submission, submitter agrees to these terms. Furthermore, submitters acknowledge that the incorporation or modification of such submissions is entirely at the discretion of the moderators of the open-source ACE+TAO projects or their designees. The names ACE(TM), TAO(TM), Washington University, UC Irvine, and Vanderbilt University, may not be used to endorse or promote products or services derived from this source without express written permission from Washington University, UC Irvine, or Vanderbilt University. Further, products or services derived from this source may not be called ACE(TM) or TAO(TM), nor may the name Washington University, UC Irvine, or Vanderbilt University appear in their names, without express written permission from Washington University, UC Irvine, and Vanderbilt University. SAP Library document classification: PUBLIC

http://www.riverace.com/

http://www.theaceorb.com/

http://www.prismtechnologies.com/

http://www.cs.wustl.edu/~schmidt/ACE.html

http://www.cs.wustl.edu/~schmidt/TAO.html

http://www.cs.wustl.edu/~schmidt/doc-center.html

http://www.opensource.org/

http://www.opensource.org/

http://www.cs.wustl.edu/~schmidt/ACE-obtain.html

http://www.cs.wustl.edu/~schmidt/TAO-obtain.html

license guide - sap balance report full full profit and loss report full full financials document...

Documents