April 2012 Setup, Configuration and Use. Document Version: Product Version: SAP Version: Localization:

(1)

1.1.0 All regions 8.80.103 8.8 Document Version: Product Version: SAP Version: Localization: April 2012

Setup, Configuration and Use

(2)

All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems - without the written permission of the publisher.

Products that are referred to in this document may be either trademarks and/or registered trademarks of the respective owners. T he publisher and the author make no claim to these trademarks.

While every precaution has been taken in the preparation of this document, the publisher and the author assume no responsibility for errors or omissions, or for damages resulting from the use of information contained in this

document or from the use of programs and source code that may accompany it. In no event shall the publisher and the author be liable for any loss of profit or any other commercial damage caused or alleged to have been caused directly or indirectly by this document.

(3)

3

4

Removing a Batch ₆₃

3. 2 Importing Bank T ransactions 64

Processing the Bank Reconcilliation 65

(5)

Installing the Application

5

1 Installing the Application

1.1 Installation

T he installation of the add-on is a simple wizard driven process which uses the standard add-on tools available inside SAP Business One.

1.1.1 Installation Prerequisites

T he following prerequisites must be met before the add-on is installed:

1. A compatible version of Microsoft Windows, which includes only the professional versions of Windows, not the home versions. T he Enprise products are tested against the versions of Windows supported by SAP Business One. Currently these include:

1.1. Workstation Software 1.1.1. Windows 2000 1.1.2. Windows XP 1.1.3. Windows Vista 1.1.4. Windows 7 1.2. Server Software 1.2.1. Windows Server 2000 1.2.2. Windows Server 2003 1.2.3. Windows Server 2008

2. T he SAP Business One client must be installed on the local machine. Please ensure that the correct version of the Enprise product is selected for the SAP version that is being run. Currently, the 8.00 series of Enprise products can be run on both SAP Business One 2007 and 8.8x. T he 8.80 version of the application can only be used with the 8.8x series of SAP Business One.

3. Microsoft .Net Framework is installed on the local machine.

3.1. For 2005 / early 2007 versions of the Enprise products you will require .Net Framework 1.1 3.2. With the 8.00 series of Enprise products .Net Framework 2.0 is required.

(6)

6

3.3.For the 8.80 series of Enprise products .Net Framework 4.0 is required.

4. T he user that is logged in and will be doing the installation has administrative rights to the client machine.

5. Login credentials are required to access the SQL server.

6. SAP DI_API of the same version as the currently installed patch of SAP Business One is installed on the local machine.

Once these prerequisites are met installation of the add-on can proceed.

1.1.2 Installation Procedure

Installation of Enprise products is a simple process, which makes use of the standard add-ons functions within SAP Business One.

T he following screenshots and steps are based on the installation of the Enprise Job add-on. However, the process for installing any of the Enprise applications, with the exception of the web based Enprise Service and Enprise Service Pro applications, is the same.

1.1.2.1 Step 1 - Extract Zip File

Versions of Enprise products can be downloaded from the Enprise partner portal (www.enprise.com/ partner). You will need to register for access to this portal.

T he download will consist of a single zip file which will contain all the necessary files to enable you to install or upgrade the relevant Enprise product. In general the zip file will contain:

1. A .ard file which is the add-on configuration file required by SAP Business One 2. T he install executable file

(7)

7

1.1.2.2 Step 2 - SAP Business One Add-on Administrator

Once you have extracted the files, you will need to add the add-on to SAP Business One using the Add-on AdministratiAdd-on utility. T his can be found under AdministratiAdd-on -> Add-Ons -> Add-On AdministratiAdd-on

(8)

8

1.1.2.3 Step 3 - Register the Add-on

1. Click the "Register Add-on" button on the left hand side of the Add-on Administration form to open the registration screen.

2. Select the Add-on Registration Data File (.ARD) and the Add-on Installation Package from the location you chose to unzip the files.

3. Assign it to the current company and tick to activate for the current company this will automatically initiate the installation.

4. Click "OK" to update and close.

5. Set the "Default Group" and "Force Install" settings as required for your business scenario.

Default Group allows you to set whether the add-on is automatically run upon opening SAP Business One, is mandatory or is started when and as required (manually).

If Force Install is selected, it will automatically install the add-on on each computer that SAP Business One is opened on, against any company that is connected to. If Force Install is turned off then the add-on will not install (recommended).

(9)

9

6. Click "OK" to close the add-on manager.

(10)

10

1.1.2.4 Step 4 - Add-on Install Wizard

T he installer will take you through several wizard driven steps required to install the add-on

(11)

11

Installer Step 2

(12)

12

In order to proceed with the installation you need to acknowledge and agree to the end user license agreement. T his is a copy of the same agreement that needs to be signed and returned to Enprise when purchasing any software.

(13)

13

(14)

14

1.1.2.5 Step 5 - Database Connection

During the initial installation of the add-on, a screen will open requesting that you enter the credentials to be used when connecting to the SQL server on which the SAP Business One company databases are stored.

(15)

15

If at any stage the password to your assigned SQL user changes, the Enprise product will not be able to connect to the SQL database. T his password utility will then need to be run manually in order to update the saved password, which will need to be done on each client machine. T he utility can be found in the install folder of the Enprise product which by default is ..\Program Files\SAP\SAP Business One\AddOns\Enprise Solutions\Enprise Solutions\<Product Name>

1.2 Installation Troubleshooting

Below are some common reasons why the installation may fail, and their related resolutions.

Issue Resolution

Is Enprise Bank showing as an installed application in Control Panel > Add/Remove Programs?

If not, then the installation procedure for this client has not completed

restart the SAP Business One Client and installation should begin.

Is the add-on registered in SAP Business One? If not, register the add-on in SAP Business One using the process

detailed in Step 4. Has the SA user password been successfully

stored in the registry?

T his can be checked using REGEDIT and checking HKEY_LOCAL_COMPUT ER > SOFT WARE > ENPRISE SOLUT IONS.

If the registry is not present, run SET PASSWORD.EXE to create the

(16)

16

Have the Enprise Bank files been copied to the relevant product folder found by default in \Program Files\SAP\SAP Business One\AddOns\Enprise Solutions\<Product Name>?

If the files are not showing in that directory but the add-on is installed add-on

the client, then manually remove the add-on via the control panel

and edit the AddOnsLocalRegistration.sbo document and remove the

Enprise Bank Interface entry. T he AddOnsLocalRegistration.sbo is located on each client machine in the primary SAP Business One folder which is usually: \Program Files\SAP\SAP Business One

T he file contains XML data relating to the add-ons that have been installed. T he entry that needs to be removed for Enprise Bank will be similar to the script below:

<AddOn Exe="EnpriseBank.exe" Installer="EnpriseBankInstaller.exe"

InstallerMD5="1A7A6AFAC7DE430F13BF757C49D1E 0F6" Name="Enprise Bank" Path="C:\Program

Files\SAP\SAP Business One\AddOns\Enprise Solutions\Enprise Bank" SelfUpgrd="false" Space="Enprise Solutions" UID="Enprise Solutions_Enprise Bank" UnInstEstT ime="60" UnInstParams="/x" UnInstaler="EnpriseBankInstaller. exe"

(17)

17

UnInstallerMD5="1A7A6AFAC7DE430F13BF757C49D 1E0F6" Ver="8.80.100"><Common ID="15"

Name="REM-HPJAMESB\SQL08R2"/></AddOn>

Restart the SAP Business One client and the add-on will re-install on

this client. Is Enprise_Bank.exe showing as a current

operating process for this machine?

Yes > End the process manually and restart SAP Business One.

No > Restart the add-on or the SAP Business One client.

Ensure the add-on is registered in the SAP Business One Add-On

Administrator and the files are present in the correct directories in SAP

(18)

18

2 Setting Up Enprise Bank

Enprise Bank uses XML templates which define the file layouts used in the import and export process. T hese XML files are created via the built-in template designer and can be easily imported and exported between SAP Business One databases.

T he successful setup of Enprise Bank Interface requires the following:

Define Import Bank T emplates (Or import existing pre-defined templates) Define Export Bank T emplates (Or import existing pre-defined templates)

Define SAP Business One Payment Methods. Please refer to standard SAP Business One documentation for more information on this.

Link the Export T emplate to the Payment Method this is a user defined field.

Payment Run Defaults must have the relevant payment methods selected. Please refer to standard SAP Business One documentation for more information on this.

2.1 Creating Export Templates

T he export templates contain the design and layout of the file that needs to be generated for the particular bank, in order to export the payment transactions generated within SAP Business One into the bank's desk banking software.

T hese templates can either be manually created, or if an existing template has been created, imported using the import routines. In order to edit or create an export template, the bank's export file layout specification will need to be obtained from the specific bank. Each bank has different file layout requirements which are generally outlined in detail in a whitepaper which the bank can provide. Banks also often have multiple file formats that they can accept, and it is worthwhile asking for all available options in order to establish if one of their alternate formats resembles an existing template.

(19)

Setting Up Enprise Bank

19

Creating the file is carried out under the Administration -> Setup -> Enprise Bank -> Export Template menu option.

Export Template Designer

T his form uses the standard SAP Business One Find / Add functionality, allowing the user to set the form to

Find mode and search for an existing template, or set the form to Add mode to create a new template.

Multiple export templates can be created for each bank format required.

Field

Options

Details

(20)

20

Field

Options

Details

unique reference to each export template created. Bank Name _{A user-entered description of the template, which} is generally used to identify which bank the template relates to.

Output File _{Folder browse dialog} _{T his is used to identify the path and the file name} used when an export file is generated. T he system will use the name that is inserted as the base name for files created, but will also append date details to the file.

Remove underscores

from filename Yes / No When the system appends the date to the file name, the system will generally add an _ (underscore) to the file. If this creates issues with the bank import, the user can choose to remove these.

File Format _CSV

Fixed Length

Determines the nature of the file that is exported. T he bank will indicate the type of file that they require.

1. CSV - each field added to the export file will be separated by a comma when exported, to designate the separation between fields. T his allows the width of the fields to adjust according to the length of the data being exported into the field.

2. Fixed length - each field has a predefined width and the system separates the field data

(21)

21

Field

Options

Details

based on these widths. No separator exists between the fields. If the data that needs to be exported is too long for the field, the system will omit any data that exceeds the specified length of the field. If the exported data does not fill the entire space of the field, as part of the setup of the field, the system can fill the space either with predefined characters or leave the space blank. T his requirement will be indicated by the bank.

Grid Area _{Each row within the grid relates to a column to be} exported to the output file.

Grid: Layout Position _Header Body Footer

1. Header - this is information created at the start of the file. T he information is not repeated and generally contains information about the batch being exported.

With a number of bank formats the bank may require file title information and file header information. T his can be accommodated by using the header option and adding a row with a carriage return between the title information and the header information.

(22)

22

Field

Options

Details

information created within the file, related to each payment that was included within the batch.

3. Footer - the footer is similar in nature to the header with the exception that it is written at the absolute end of the file.

Grid: Order _{User-entered numerical} value

Allows the company to control the order in which the field is exported. T his order will be determined by the bank's requirements.

Grid: Description _{User-entered value} _{T his field is used to provide a description of the} field that will be exported and is primarily used for the person creating the template, to understand what each field is for. T he description field is not exported when creating an export file.

Grid: Type _{T he type field controls the information that is} exported. T his will be discussed in greater detail in the Export Data section.

Data Format Field Width Text Alignment Pad Char

T his area provides additional information relating to the grid row that is highlighted, and controls additional details relating to the information being exported.

T hese fields will be explained in greater detail in the Export Data section.

(23)

23

2.1.1 Export Data

T he data that is exported in each field of the export file is controlled by a combination of the T ype and Format options that are selected within the rows of the template grid. T he various options available are:

Type Description Footer Fields

Options Description

Account Field

T he account field is a carry-over from historical versions of Enprise Bank, which only supported outgoing payments. T his category provided information about the vendor business partner that was linked to the payment.

T his category has been left in the system due to some templates still using the category, but it has not been updated to bring through customer business partner information. Customer and supplier information

Data Format

Account Field Single option

Acc Field Name

Code T he extended Acc

Field Name option allows the company to identify the specific master data element that is required in the export file.

If information is required that resides in a User Defined Field on the master data, an additional data type

User Defined Fields is

used. Name Foreign Name T elephone 1 T elephone 2 Mobile Phone Fax E-Mail Active OnHold Account balance Street

(24)

24

can be obtained through the Payee and Creditor information. Block Zip Code County State Country Reference DME Identification Instruction Key Amount T he actual payment

transaction amount. Depending on the currency set on the payment, the system will either export the local currency value or the foreign currency value.

Data Format 0 Decimal places 2 Decimal places

Controls whether the system exports a separator between the decimal points of the payment. If 0 decimal points are selected then the system will not add a separator.

Batch Referenc e

Provides a unique reference to the batch being exported.

Data Format

Batch Reference

(25)

25

Count Provides a count of the number of records that are exported. T his relates to the number of payment transactions that have been included within the batch.

Data Format

Count Records X Factor Integer Value

Default = 1

Multiplication factor that is applied to the count of payment records. T his is used for certain bank formats where a payment record is split into multiple rows and the the count needs to total the multiple rows. Count +

x

Provides a count of the number of records that are exported and then adds an additional user defined factor to the result. T his is to accommodate certain bank requirements to include the footer / header rows in the count totals.

Data Format

Count + x

X Value Integer value Identifies the factor that needs to be added to the record count.

X Factor Integer Value Default = 1

Multiplication factor that is applied to the count of payment records. T his is used for certain bank formats where a payment

(26)

26

record is split into multiple rows and the the count needs to total the multiple rows. Creditor

Bank Account

Contains all the available bank details relating to the vendor / customer linked to the payment.

Data Format

Option Details

2472 Combination string of bank, branch, account number and suffix in one string value.

The first option will not have an separators between the different elements while the second option will insert a - between the elements.

The first two digits will be taken as the bank number.

The second 4 digits will be taken as the branch number.

The following 7 digits will be taken as the account number.

The last 2 digits will be used as the suffix. 2-4-7-2

The first option will not have an separators between the different elements while the second option will insert 2-4-7-3

(27)

27

a - between the elements.

The last 3 digits will be used as the suffix. 2474 Combination string of

bank, branch, account number and suffix in one string value.

(28)

28

2-4-8-3 bank, branch, account number and suffix in one string value.

The second 4 digits will be taken as the branch 2-4-8-4

(29)

29

number.

The last 4 digits will be used as the suffix. Branch

No Only Exports only the branch number associated to the bank account.

Bank No

Only Exports only the bank number associated to the account.

Account No Only

Exports only the bank

account number

associated to the account. Suffix 2 _{Exports only the suffix of} the account number. T his option will deem the last 2 digits to be the suffix. Suffix 3 _{Exports only the suffix of}

the account number. T his option will deem the last 3 digits to be the suffix. Suffix 4 _{Exports only the suffix of}

(30)

30

the account number. T his option will deem the last 4 digits to be the suffix. BSB

Number BSB code from the Business Partner user defined field.

Unformat ted Bank Account Number

Bank account details with no formatting applied. T his option will take the information as it has been entered into SAP Business One.

User No.

1 User fields from the bank setup.

OCRB.UsrNumber1 User No.

3

User fields from the bank setup.

(31)

31

OCRB.UsrNumber4 Account

Name Name of the bank account Control

Key Control key from bank account setup.

ABA Routing Number

T his option is only relevant to certain localizations. T he field maps to OCRB. UsrNumber1.

IBAN _{IBAN code from the bank} account setup.

Creditor Details

If the transaction type is an outgoing payment, the system will bring through the name of the Business Partner linked to the payment.

Where the transaction is an incoming payment, the system will bring through the SAP Business One company name. Data Format String from account table Acc Field Name

Code T he extended Acc

Field Name option allows the company to identify the specific master data element that is required in the export file.

If information is required that resides in Name Foreign name T elephone 1 T elephone 2 Mobile Phone Fax Email

(32)

32

Active a User Defined Field on the master data, an additional data type

User Defined Fields

should be used. On Hold Account Balance Street Block City Zip code County State Country Reference DME Identification Instruction Key Creditor Number

If the transaction type is an outgoing payment, the system will bring through the account number of the Business Partner linked to the payment.

Data Format

String from account table

(33)

33

Where the transaction is an incoming payment, the system will bring through the SAP Business One company name

Date Date information relating to the payment

Data Format

HH:MM With all the format options, the following references are used:

YY = 2 digit year value

YYYY = 4 digit year value MM (not when associated with HH) = 2 digit month reference DD = 2 digit day reference HH = 2 digit hour reference MM (when associated to HH) = 2 digit minute YYYYDDD HHMM HH:MM:SS HHMMSS MM/DD/YYYY MM/DD/YY YYYY/MM/DD YY/MM/DD DD/MM/YYYY DD/MM/YY YYDDD MMDDYYYY MMDDYY

(34)

34

YYYYMMDD reference

YYYYDDD = special case Julian date format

YYDDD = special case Julian short date format

YYMMDD DDMMYYYY DDMMYY

Date If the format selected above is HHMM, the available options are: T oday's time Payment date For all other formats the available options are: T odays date Payment date

(35)

35

Date + x Date information relating to the payment made but allowing the company to add on additional days to incorporate a file expiry date.

Data Format

HH:MM With all the format options, the following references are used:

YY = 2 digit year value

YYYY = 4 digit year value MM (not when associated with HH) = 2 digit month reference DD = 2 digit day reference HH = 2 digit hour reference MM (when associated to HH) = 2 digit minute reference YYYYDDD = special case Julian date format

YYDDD = special case Julian short YYYYDDD HHMM HH:MM:SS HHMMSS MM/DD/YYYY MM/DD/YY YYYY/MM/DD YY/MM/DD DD/MM/YYYY DD/MM/YY YYDDD MMDDYYYY MMDDYY YYYYMMDD YYMMDD DDMMYYYY DDMMYY

(36)

36

date format Date If the format

selected above is HHMM, the available options are: T oday's time Payment date For all other formats the available options are: T odays date Payment date

X Value Integer value Identifies the number of days that need to be added to the selected date,.

Payer Bank

Contains all the banking details of the SAP

Data Format

(37)

37

Account Business One company using Enprise Bank.

2-4-7-2 bank, branch, account number and suffix in one string value.

The second 4 digits will be taken as the branch 2-4-7-3

(38)

38

number.

The first option will not have an separators between the different elements while the second option will insert 2-4-8-3

(39)

39

a - between the elements.

(40)

40

Option Details Branch

No Only Exports only the branch number associated to the bank account.

Bank No

Only Exports only the bank number associated to the account.

Account No Only

Exports only the bank

account number

associated to the account. Suffix 2 _{Exports only the suffix of} the account number. T his option will deem the last 2 digits to be the suffix. Suffix 3 _{Exports only the suffix of}

the account number. T his option will deem the last 3 digits to be the suffix. Suffix 4 _{Exports only the suffix of}

the account number. T his option will deem the last 4 digits to be the suffix. BSB

Number BSB code from the Business Partner user

(41)

41

Type Description Footer Fields Options Description Option Details defined field. Unformat ted Bank Account Number

Bank account details with no formatting applied. T his option will take the information as it has been entered into SAP Business One.

User No.

DSC1.UsrNumber1 User No.

2

User fields from the bank setup.

DSC1.UsrNumber4 Account

Name Name of the bank

account Control

(42)

42

Option Details account setup. Swift

Number Swift number

IBAN _{IBAN code from the bank} account setup.

Payer Details

If the transaction type is an outgoing payment, the system will bring through the SAP Business One company name.

Where the transaction is an incoming payment, the system will bring through the account name of the Business Partner linked to the payment. Data Format Code Name Foreign Name T elephone 1 T elephone 2 Mobile Phone Fax Email Active OnHold Account Balance Street Block City

(43)

43

Type Description Footer Fields Options Description Zip Code County State Country Reference DME Identification Instruction Key Payment Currenc y

Identifies and brings the

currency symbol

associated to the payment into the export file.

T he currency option has an impact on the

Payment Field that is

brought through into the export file. If the currency is the same as the system currency, the system will export the

Data Format

Payment Currency

(44)

44

local currency value of the payment transaction. If the currency has any other value, the system will export the foreign currency payment value.

T he payment currency is set on step 6 of the payment wizard for foreign or multi-currency business partners. Payment Field Additional payment information. Data Format Payment Field Pay Field Name Payment Doc Number Payment Reference Details T he Payment Doc Number links directly to either the incoming or outgoing payments tables (OVPM or ORCT ).

T he reference information relates to the reference field that

(45)

45

is entered on step 6 of the payment wizard. ( PWZ3.IsrRef)

Sequenc e

Number

Provides a unique reference number for each payment row transaction.

Data Format

Sequence Number

Seed Allows the user to

identify a starting number for the sequence number.

Increment Determines the value

by which the sequence

number should

increase with each payment row.

Sum Calculates the total value of the payment batch which can be added to the batch as a hash total.

Data Format Sum amount with DP Sum Accs (HSBC with DP) Sum Accs.

Sum amount with DP = totals the local currency value of all the payments in the batch.

Sum Accs (HSBC) = a format specific to

(46)

46

Type Description Footer Fields Options Description (HSBC) Sum Accs (BNZ) Sum Amount (Header/ Footer) the HSBC bank which sums the last four digits of the bank account number and then forces the result to be 4 characters by either padding the right of the string with zeros or removing the left portion that exceeds 4 characters.

Sum Accs (HSBC with DP) = similar to the Sum Accs (HSBC) however inserts a decimal point in the middle of the 4 characters.

Sum Accs (BNZ) = a format specific to the BNZ bank which combines the 4 digit branch and 7 digit

bank account

(47)

47

totals this new number. Based on

the bank

requirements, the system then forces the result to be 11 characters long by either padding the right of the string with zeros, or dropping the left portion of the string that exceeds 11 characters.

Sum Amount

(Header / Footer) = T otals the local currency value of all the payments in the batch, ignoring the decimal point. i.e -the decimal values are assumed to be part of the actual number 123.45

(48)

48

Type Description Footer Fields Options Description becomes 12345. Unmodif ied String T he unmodified string option provides controls around the file layout and the ability to enter non-database related information. Data Format Carriage Return Empty Field No Formatting Carriage Return -forces a carriage return in the export file allow for the separation between title and header rows, or where each payment requires multiple rows.

Empty Field provides the ability to insert a blank space in the file for data that may no longer be required by the bank.

No Formatting provides the ability to enter static, non-database related information. T his information will be brought through into

(49)

49

the database file with

no formatting

manipulation being carried out.

User Bank

T he user bank option will bring through the bank details of the SAP Business One company that is used is relation to the payment.

Data Format

User Bank T he exported data will include the bank code, branch ID and account number.

User Defined Fields

Provides the ability to insert data from user-defined fields on the business partner or payment methods screen into the export file.

Data Format

User Defined Fields

Field Name List of user defined fields on the BP master and the Payment Methods master.

(50)

50

2.1.2 Linking export templates to payment methods

In order to export transactions based on the SAP Business One payments wizard, export templates need to be linked to the relevant payment method that has been set up within SAP Business One. T he link is established via a user defined field on the standard SAP Business One Payment Methods form, which is created when the Enprise Bank add-on is installed.

Access to the SAP Business One Payment Methods form is from the following menu option:

Administration -> Setup -> Banking -> Payment Methods

Payment Methods Setup

T he same export template can be attached to multiple payment methods.

Having the Check Bank Details option selected is recommended as it will ensure that all the bank details are correctly entered against the Business Partners assigned to this payment method.

(51)

51

T he system does not add a formatted search to the field, however, if the company requires a search to be added, the script below will return the required result.

SELECT RECNO AS [Template ID],DESCRIPTION AS [Template Name] FROM

ENPRISE_BANKREC_EXPORT_HEADER_DEF

2.2 Creating Import Templates

T he import template designer allows the company to design the layout of the bank statement files that are generated by the desk banking software that then need to be imported into SAP Business One for reconciliation processing. Within the designer, the company needs to identify the column number within the export file that relates to specific information that the system will then import.

T he actual processing of a bank reconciliation is outside the scope of this document, but this information can be obtained from SAP.

(52)

52

Import Template Designer

Field

Options

Details

Format ID _{T his is a system-generated field value providing a} unique reference to each import template that is created.

Bank Name _{A user-entered description of the template which} is generally used to identify which bank the template relates to.

(53)

53

Field

Options

Details

One relating to this bank template. T his is a default value and can be altered when processing the import allowing the user to have multiple bank accounts linked to the same template.

Transaction Date _{T he column number in the bank-generated import} file that relates to the date of the transaction. Cheque No _{T he column number in the bank-generated import}

file that relates to the cheque reference number.

Details _{T he column number in the bank-generated import}

file that relates to the details about the transaction. Reference _{T he column number in the bank-generated import}

file that relates to reference information about the transaction.

Particulars _{T he column number in the bank-generated import} file that relates to other party information about the transaction.

Header Row Skip _{T he header and footer rows which usually contain} column titles which are for the benefit of the file user, but not required by the system when importing the file. T hese rows within the import file need to be ignored when the system carries out the import. T his option identifies to the system the number of rows that should be ignored and not imported into SAP Business One.

(54)

54

Field

Options

Details

Footer Row Skip _{T his option is the same as the Header Row Skip} function but applies to footer information within the import file which is not relevant to the import. Field Has Total

Amount Certain import files separate out the incoming and outgoing amounts into two columns, while other files contain a single column for all the transactions with a designator (such as a - sign) to identify whether the value is an incoming or outgoing transaction.

Total Amount _{T he column number in the bank-generated import} file that relates to the total transaction value. T his option is only enabled if the Field Has Total

Amount option is checked.

Credit Amount _{T he column number in the bank-generated import} file that relates to the incoming transaction value. T his field is only enabled if the Field Has Total

Amount option is not checked.

Debit Amount _{T he column number in the bank-generated import} file that relates to the outgoing transaction value. T his field is only enabled if the Field Has Total

Reverse Sign _{With certain bank files, the file is generated from} the bank's perspective rather than from the customer's perspective. T his results in a negative

(55)

55

Field

Options

Details

amount (which in the bank's perspective is an outgoing transaction) actually reflecting an incoming amount for the customer and vice versa for positive amounts.

T he reverse sign orders the import process to reverse the sign on the transaction so that negative amounts are treated as incoming amounts, and positive amounts are treated as outgoing transactions.

T his field is only enabled if the Field Has Total

Amount option is checked.

Evaluation Column _{Where the actual transaction amount does not} designate an incoming or outgoing payment, but rather another column in the file provides this information, the company can specify the column number related to this field.

T his field is only enabled if the Field Has Total

Value _{If the company chooses the Evaluation Column} option, then the value column needs to provide the information that the system must use to evaluate whether the transaction is an incoming or outgoing value.

T his field needs to hold the field value from the file that relates to either the incoming or outgoing

(56)

56

Field

Options

Details

transaction.

Type _{Debit - Column Value}

indicates Debit

Credit - Column Value indicates Credit

T he type field identifies whether the value entered in the Value field reflects the designator for an incoming (credit) transaction or an outgoing (debit) value. If the system encounters a transaction that does not contain the value entered in the Value field, the system will automatically assign it to alternate the Type value.

Date Format _DMY

DYM MDY MYD YMD YDM YD

T he format of the date that the bank uses when exporting the data.

Date Separator _/ -. ~

T he separator that is used by the bank to separate the different date elements.

Values Have Decimal _{Identifies whether the amount columns within the} bank file contain decimal values or not. If the option is unchecked, the system will then assume that the last two digits in the amount columns are decimal values.

(57)

57

Field

Options

Details

Remove

Non-Numeric Characters from Value

T his option will automatically remove any non-numeric characters from the amount columns on import of a file. T his is to accommodate the scenario where the bank files automatically contain the currency symbol in the amount columns.

Use Non Default

Separator Character T he system assumes that the file is a comma separated file and evaluates the columns based on this structure. If the bank uses an alternate separator between columns, the separator needs to be identified.

Character _{T his field allows the company to specify which} character is used to separate fields within the bank export file. T his field is only enabled if the

Use Non Default Separator Character option is

checked.

2.3 Data Export / Import

An import and export function is available to allow templates to be transferred between databases. T he functions can be accessed from the Administration -> Data Import/Export -> Data Import or Data Export.

(58)

58

Data Import / Export Options

1. Import Enprise Bank Export Template: allows export templates that have been exported from another database, to be imported into the current database.

2. Import Enprise Bank Import Template: allows import templates that have been exported from another database, to be imported into the current database.

3. Export Enprise Bank Export Template: allows export template details to be exported to an XML file which can then be imported into another database using the Import Enprise Bank Export Template function.

4. Export Enprise Bank Import Template: allows import template details to be exported to an XML file which can then be imported into another database using the Import Enprise Bank Import Template function.

2.3.1 Importing Templates

(59)

59

2.3.1.1 Importing Export Templates

Importing an Export Template

Field

Options

Details

Export Template File _{Browse field for the user to select the relevant XML} file to be imported.

Template Output

Path A browse function to allow the user to define a

folder on the system where the export files should be saved.

2.3.1.2 Importing Import Templates

Importing an Import Template

Field

Options

Details

Import Template File _{Browse field for the user to select the relevant XML} file to be imported.

(60)

60

2.3.2 Exporting Templates

T he only information required when exporting templates is the actual template ne that needs to be exported and where the resulting XML file should be saved. With both the export options, a dialogue box similar to the one below is presented:

Export Templates

Field

Options

Details

Import / Export

Template A drop-down option listing all the import / export templates that have been created in the database. Output File _{A path identifying where the system should save}

the resulting XML file.

2.4 Batch Removal Password

T he Batch Removal function resets the status of a batch of payments that have been exported via Enprise Bank, to a status permitting them to be exported again. Once a batch has been exported Enprise Bank will not allow the batch to be re-exported unless the batch removal process has been carried out. T he ability to reset the batch status is password controlled.

(61)

61

T he default batch removal password is: ENPRISEBANK101

Changing this password is encouraged and is carried out under the Administration -> Setup -> Enprise

(62)

62

3 Using Enprise Bank

Enprise Bank has been developed around two primary functions:

1. Allowing bank transactions created within SAP Business One to be exported to desk banking software 2. Allowing statements downloaded from desk banking software to be imported into SAP Business One

and used in bank reconciliations.

3.1 Exporting Bank Transactions

T he bank-related transactions that are exported by Enprise Bank are all a direct result of processing that is carried out via the SAP Business One Payment Wizard. T he payment wizard allows batch processing of either incoming or outgoing payments based on criteria selected when running the wizard. T his document is not intended to explain the Payment Wizard, and therefore we encourage the use of official SAP documentation on this topic.

When processing a payment run via the Payment Wizard, the initial parameters allow you to choose whether or not the payment means are via Check or Bank Transfer. Enprise Bank will only export details relating to Bank Transfer payment means.

During the processing of the Payment Wizard a selection of Payment Methods is made. Only Payment

Methods that have been linked to an Export Template will be exported via Enprise Bank.

3.1.1 Processing the export

At the conclusion of the Payment Wizard, the export of the transactions is carried out at Banking ->

(63)

Using Enprise Bank

63

Export to Desk Banking

T he user is then able to choose which payment methods they wish to export, along with the date range if applicable. T he system will then generate the file based on the template specifications linked to the payment method and save the data in the folder specified in the template.

Once the file has been generated it can be imported into the desk banking software.

3.1.2 Removing a Batch

For security's sake, after a batch of payments has been exported via Enprise Bank, the batch is not able to be exported again. T his is to prevent a batch being uploaded to the banking software, and potentially being paid, multiple times.

However, if there is an issue with the initial creation of a batch, it is possible to reset the batch status to allow the batch to be exported using the Remove a Batch option. In order to remove a batch the following information is required:

1. T he batch number 2. T he batch total

(64)

64

3. T he batch removal password

Once the batch status has been updated, the transactions can be exported using the standard export functions.

If some details have changed on the Business Partner master data relating to the Payment Run that has been executed, an option does exist within SAP Business One to recreate the export file. T his will refresh the data within the database tables to reflect the new data. However, if this process needs to be carried out, it is important that if you have already exported the batch within Enprise Bank, you first remove the batch and then recreate the file using the Payment Wizard. T his will then allow the payment details to be re-exported with the amended information.

3.2 Importing Bank Transactions

T he importing of transactions is carried out from the Banking -> Enprise Bank -> Import External Bank

Statement menu option.

Importing a Bank Statement

Field

Options

Details

File Format _{Drop down selection of} import templates

T he list of import templates that have been set up within the system.

(65)

Using Enprise Bank

65

Field

Options

Details

File Path _{Browse option to identify where the bank} statement file has been saved from the desk banking software.

G/L Account _{Choose from list of G/L} account

T he general ledger account associated with the bank transactions being imported. T his will default to the G/L account specified in the template design, but can be altered if needed.

Reference _{Batch reference.}

Description _{Batch description.}

Transaction Date _{T he transaction date of the bank statement.}

3.2.1 Processing the Bank Reconcilliation

T his document does not intend to explain the bank reconciliation process within SAP Business One and would rather encourage the use of the official SAP documentation on this topic.

Enprise Bank however, is not intended to be used in conjunction with the Manual Reconciliation within SAP Business One, rather to allow the use of theReconciliation function which then allows the user to choose between the Manual, Automatic or Semi-Automatic reconcilliation options.

3.3 Check Export Setup

T he Check Export Setup, which is located under the menu option Banking -> Enprise Bank -> Check

(66)

66

data is available on the Business Partner master records. T he check can highlight inconsistencies where data required for the export template does not exist on the Business Master data.

April 2012 Setup, Configuration and Use. Document Version: Product Version: SAP Version: Localization:

Setup, Configuration and Use

3

Table of Contents

4

5

1

Installing the Application

1.1

Installation

1.1.1

Installation Prerequisites

6

1.1.2

Installation Procedure

1.1.2.1

Step 1 - Extract Zip File

7

1.1.2.2

Step 2 - SAP Business One Add-on Administrator

8

1.1.2.3

Step 3 - Register the Add-on

9

10

1.1.2.4

Step 4 - Add-on Install Wizard

11

12

13

14

1.1.2.5

Step 5 - Database Connection

15

1.2

Installation Troubleshooting

16

17

18

2

Setting Up Enprise Bank

2.1

Creating Export Templates

19

Field

Options

Details

20

Field

Options

Details

21

Field

Options

Details

22

Field

Options

Details

23

2.1.1

Export Data

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41