Download Release Notes - Orbis Software Ltd

Revision HistoryRevision HistoryDate Name Version Comments14 th May 2009 Paul Garratt 0.1 First draft15 th May 2009 Paul Garratt 0.2Corrections to issue fixes followingreview.15 th May 2009 Paul Garratt 1.0 First Issue1

Copyright & TrademarksCopyrightThe copyright in this document is owned by Orbis Software 2009. All rights reserved.This publication may not, in whole or part, be reproduced, transmitted, transcribed, storedin a retrieval system or translated into any language in any form or by any means withoutthe prior written consent of Orbis Software Limited.TrademarksOrbis Software Ltd owns the registered Trademark ‘TaskCentre’.All other Trademarks used within this documentation are acknowledged as the property oftheir respective owners.The information provided in this publication may contain errors, omissions, ortypographical errors or may be out of date. Orbis Software may change, delete, or updateany published information at any time and without prior notice. The information publishedin this document is provided for informational purposes only and is not binding on OrbisSoftware in any way except to the extent that it is specifically indicated to be so.1

IntroductionIntroductionPurpose of the documentTo describe the new functionality and issues resolved in this release.Build InformationTaskCentre Tools for SAP Business One V1.3.4 is a complete new build of all components.2

New FunctionalityNew FunctionalityV.1.3.4No new functionality.V.1.3.3No new functionality.V.1.3TitleDescriptionNew objects made available in Event ToolAdmin Info (Company Info)Correction Invoices (Business One 2007 - Polish customisation only)Correction Invoice Reversals (Business One 2007 - Polish customisationonly)Purchase Correction Invoices (Business One 2007 - Polishcustomisation only)Purchase Correction Invoice Reversals (Business One 2007 - Polishcustomisation only)TitleDescriptionNew objects in Communicator ToolAdmin Info (Company Info) (Business One 2007 only)Correction Invoices (Business One 2007 - Polish customisation only)Correction Invoice Reversals (Business One 2007 - Polish customisationonly)Purchase Correction Invoices (Business One 2007 - Polishcustomisation only)Purchase Correction Invoice Reversals (Business One 2007 - Polishcustomisation only)TitleDescriptionSpecial line support (subtotal/text lines) added for following documents(Business One 2007 only)Credit NotesDelivery NotesReturnsSales OrdersInvoicesDraft documents3

Purchase OrdersPurchase Delivery Notes (Goods Receipt PO)Purchase ReturnsPurchase InvoicesPurchase Credit NotesQuotationsTitleDescription64 bit Web ServiceWeb Service component can now be installed on Windows 2003 64-bitand Windows XP 64-bit.V.1.2TitleDescriptionNew objects made available in Event ToolUsersAccount SegmentationAccount Segmentation CategoriesCredit CardsUser DefaultsTeamsSales PersonsEmployeesVAT GroupsWarehouse LocationsWarehousesItem GroupsManufacturersWeights and MeasuresShipping TypesPrice ListsBanksHouse Bank AccountsTerritoriesPayment TermsBP GroupsSpecial PricesActivity TypesActivity status4

Chart of accountsCurrencyJournal EntriesIncoming paymentsOutgoing paymentsProjects (Business One 2007 Only)Sales Quotations (Business One 2007 Only)Messages (Business One 2007 Only)TitleDescriptionNew objects in Communicator Tool (Business One 2007 only)ProjectsSales QuotationsMessagesTitleDescriptionSerial and Batch number support added for following documents(Business One 2007 only)InvoicesCredit NotesDelivery NotesReturnsPurchase InvoicesPurchase Credit NotesPurchase Delivery Notes (Goods Receipt PO)Purchase ReturnsGoods ReceiptGoods IssueTitleDescriptionmyTaskCentre SAP B1 add-onIncluded as part of the distribution, this is a Business One Add-on thatadds a TaskCentre menu item, and allows you to view myTaskCentrefrom within the Business One environment. To install, unzip themyTaskCentreBrowserInstaller.zip file to a temporary directory, andfollow the standard Business One add-on installation procedure,pointing Business One at the unzipped files.TitleDescriptionEvent IconIcon for Event Tool improved.5

V.1.1TitleDescriptionSupport for SAP Business One 2007 ANote that you enable this support on a per connection basis by settingthe "Version" item in the connection configuration to "2007". Thismeans that it is possible to have a single TaskCentre installation thatconnects to multiple SAP Business One servers, of either version.TitleDescriptionAbility to add variables to the source fields when Connector Tool isusing an XML data sourceIn the same way as it has always been possible to create Task/Globalvariables and add these to the source fields when using a TaskCentrerecordset data source, it is now possible to add these variables to thesrouce fields when using an XML data source.TitleDescriptionImprovements to the configuration screen of the Event ToolThe field selection boxes have been improved so that they are in linewith other selection lists in TaskCentreTitleDescriptionImprovements to the messages returned to the TaskCentre client andEvent Log when tasks run.More detail is now shown, including connection messages whenconnecting to the SAP DI Server, and feedback denoting if and SAPerrors were reported during the task run.TitleDescriptionImprovements to the mapping screens in the SAP Business OneConnector ToolSelecting fields in the source or destination lists now selects the linkedfields in the other list, making it easier to see what fields are linked.Also the links themselves highlight when selected. The Right click menuto remove links is now available by right clicking the fields in the list aswell as the links themselves.TitleDescriptionAutomatic translations from SAP Business One database field values toSAP Business One DI Server field valuesWhen adding/updating SAP Business One objects, many fields arerestricted to a SAP-defined set of values (e.g. the "Gender" field on aBusiness Partner Contact must be passed as "gt_Female", "gt_Male" or"gt_Undefined"). However, most data sources (including the SAPDatabase tables themselves, if directly queried by an OLEDB/ODBC6

query tool) do not store data according to these values. Convertingfrom the source values into the format required by the SAP DI Servercan be tricky to set up. A mechanism has been provided to allow theSAP Business One Connector Tool to automatically do this. A newschema file, "Enumerations.xml" is installed with V1.1 which details theDI Server field values, and also the values that when found in thesource data will be automatically translated in the correct value to passto the DI Server. The most-used SAP Business One object schemashave been altered to include the most commonly performedtranslations (e.g. "Y" and "N" to "tYES" and "tNO"). If any additionalsource data translation is required, the values can simply be added tothe schema files and the Connector tool will pick these up.7

Issues ResolvedIssues ResolvedThe following issues have been resolved in these releases.V1.3.4Issue Number 33097DescriptionTC Variables containing numeric values within certain ranges translatedincorrectly to SAP Date formatIssue Number 33103DescriptionAlternate Catalogue Numbers Schema correctedProduct AreaV1.3.3Issue Number 33019DescriptionConversion fails when setting date fields in Sales QuotationsIssue Number 33033DescriptionEvent Tool config, removing of event listening on a database fails ifevent tables not presentIssue Number 33053DescriptionResolution of numeric values in event tool variables in connector toolfailsIssue Number 33057DescriptionInstaller override to suppress pre-installation checks addedIssue Number 33062DescriptionItemGroups schema correctionsIssue Number 33074Description Occasional timeout when sending large amounts of data to DI Server -option added to increase timeout on connection in global settings.8

Issues ResolvedV1.3Issue Number 32609DescriptionSuperfluous errors in Windows Event Log from Agent after installIssue Number 32727DescriptionInstaller DI API check failing in some circumstancesIssue Number 32792DescriptionInstaller SQL SMO check failing in some circumstancesIssue Number 32825DescriptionError reporting from UDT operations with single transactions correctedIssue Number 32825DescriptionPayment Draft schema correctionsIssue Number 32825Description Sales Quotations and Messages made available in SBO 2005Issue Number 32840DescriptionCurrencies schema correctionsIssue Number 32844DescriptionLooping Connector tools within a task gives Invalid Session ID errorIssue Number 32849DescriptionItem Groups made available in Event ToolIssue Number 32852DescriptionWarehouse schema correctionsIssue Number 32854DescriptionManufacturer schema corrections9

Issues ResolvedIssue Number 32861DescriptionVersion of connector and xml to recordset tools now show inTaskCentre clientIssue Number 32875DescriptionNull value in change of field causes errorIssue Number 32887DescriptionTask and step failure options not honoured by connector and xml torecordset toolsIssue Number 32896DescriptionIntermittent error when mapping multiple fields in event tool to taskvariablesIssue Number 32902DescriptionIncoming Payment schema correctionsIssue Number 32907DescriptionSales Employee and Team schema correctionsIssue Number 32928DescriptionInstaller error when modifying web service componentIssue Number 32942DescriptionSBO 2005 PL34 error when modifying Sales Order by adding new linesIssue Number 32952DescriptionUDT Date fields fail for add/updateIssue Number 32966DescriptionBusiness Partner Groups schema correctionsIssue Number 32968DescriptionBanks and House Banks schema corrections10

Issues ResolvedIssue Number 32971DescriptionDefault button on connector tool not set to the OK buttonIssue Number 32982DescriptionTeam and Sales Employee schema correctionsIssue Number 32991DescriptionUnderscore in UDT name causes error in XML to Recordset toolIssue Number 32995DescriptionEmployees schema correctionsIssue Number 32996DescriptionBlank value in dynamic connection not trappedIssue Number 33002DescriptionOffline database causes error in event tool global configIssue Number 33003DescriptionAgent hang when incorrect information passed from Business OneIssue Number 33012DescriptionInstaller failure for web service on Polish Windows 2003 serverIssue Number 33023DescriptionOutgoing payments schema correctionsIssue Number 33024DescriptionUnicode data gets lost in connector toolV1.2Issue Number 32612DescriptionEvent agent tries to remove database scripts twice11

Issues ResolvedIssue Number 32614DescriptionError when clicking whitespace in field listIssue Number 32617DescriptionErrors when registering event DBs out of orderIssue Number 32623DescriptionUsing linenum field on documents where lines have been deletedIssue Number 32631Descriptionweb.config setting for web service authorisationIssue Number 32632DescriptionVarious help file correctionsIssue Number 32637DescriptionParameter variable doesn't resolve on mappingIssue Number 32638DescriptionStep loses variables and formulas on child object tabsIssue Number 32643DescriptionTimeout issue with web serviceIssue Number 32675DescriptionCardCode on Goods Receipt (oInventoryGenEntry) should not bemandatoryIssue Number 32676DescriptionCrash in task when formula used as change of fieldIssue Number 32682DescriptionImproved errors from web service12

Issues ResolvedIssue Number 32688DescriptionImproved errors from Agent database registrationIssue Number 32689DescriptionDraft document should allow delete operationIssue Number 32697DescriptionSpecial price list updating fails with XML recordsourceIssue Number 32808DescriptionRemove Delete and Close operations from Incoming Payments schemaIssue Number 32809DescriptionRemove Delete and Close operations from Outgoing Payments schemaIssue Number 32813DescriptionObject mapping not found in object map when opening Connector stepif source step removedIssue Number 32819DescriptionMailAddres field incorrect for events in BusinessPartner schemasIssue Number 32821DescriptionEvent tool database unregistration sometimes does not clear SAP SPCodeIssue Number 32822DescriptionNbSbAmntFC field incorrect for events in document schemasIssue Number 32824DescriptionObj ref error from tool when error response from SAP received for UDTadd operationV1.1Improved error handling and messages in global configuration screens13

Issues ResolvedXML to Recordset mapper error handling improvedSmall memory leak in SAP Business One Event Agent fixed (leak was about 7MB for every53000 SAP Business One events processed)Schema refresh now picks up changes to the main schema files as well as changes to theUDFs within the SAP Business One databaseFixed bug where changing the name of the connection in the global config was breakingsteps that used that connection.Global config screen error when just the name of the connection entered and no other datafixed.More checking added to installer for prerequisites (e.g. a check is made that theTaskCentre ToolStub API is installed)Bug fixed in Event tool which prevented the docentry value for draft documents beingbrought through to the taskEvent Tool global config error when accessing an SQL server that contains offlinedatabases fixed.Various fixes to SAP Business One object schemas14

Upgrade InstructionsUpgrade InstructionsPre-requisite TaskCentre VersionsThis is a complete installation of the TaskCentre Tools for SAP Business One. It is notnecessary to have a previous version of these tools installed before installing this release.TaskCentre must be installed with a minimum version of 4.5 Service Release 2.Other Pre-requisite Software VersionsThe following software versions are required to use the SAP Business One tools:- SAP Business One 2005 SP01 - Patch Level 36 onwards - SQL Server 2005 database only- SAP Business One 2007 - Patch Level 30 onwards - SQL Server 2005 database onlyUpgrade StepsStart the installation application and follow the on screen instructions.When upgrading from V1.0 or V1.1 the instructions from one of the following two chaptersmust be followed.Upgrading from V1.1After the upgrade has been performed, you should re-register your SAP Business Onedatabases with the SAP Business One Event Agent. This can be done as follows:1) Start the TaskCentre client.2) Go to the SAP Business One Event global configuration screen (Manage->Tools->SAPBusiness One->SAP Business One Event)3) Select the first Agent shown in the list and press Edit4) Remove all Registered SAP Business One Databases5) Select OK6) Repeat steps 4 and 5 for each Agent7) Select OK8) Re-enter the global configuration screen9) Select the first Agent shown in the list and press Edit10) Select Add to add a database11) On the "Register SAP Business One Database" screen, select the SAP Business Onedatabase you wish to register.12) Check the box where you wish the event capturing code to be inserted (this is usuallyjust below the "Add your code here" comment)13) Select OK14) Repeat steps 10 to 13 for each database you wish to register, and for each agent youare using.To enable the schema fixes that have been made, you will need to refresh the schemas foreach connection defined in the SAP Business One Connector and XML to Recordset toolglobal configuration settings. This can be done as follows:15

Upgrade Instructions1) Start the TaskCentre client.2) Go to the SAP Business One Connector global configuration screen (Manage->Tools->SAP Business One->SAP Business One Connector)3) Select the connection you wish to refresh. Double click it or highlight it and press edit.4) Press "Refresh Schemas"5) Press OK on the information message box.6) Press OK on the connection configuration screen.7) Repeat steps 3 to 6 for each connection.8) Repeat steps 2 to 7 for the SAP Business One XML to Recordset global configurationscreen (Manage->Tools->SAP Business One->SAP Business One XML to Recordset)Upgrading from V1.0IMPORTANT NOTE WHEN UPGRADING FROM V1.0Due to changes that have been made to the SAP Business One event notification system,upgrading from V1.0 of the tools necessarily involves a few manual steps. These are asfollows:1) Before upgrading, start the TaskCentre client.2) Go to the SAP Business One Event global configuration screen (Manage->Tools->SAPBusiness One->SAP Business One Event)3) Select the first Agent shown in the list and press Edit4) Remove all Registered SAP Business One Databases5) Select OK6) Repeat steps 4 and 5 for each Agent7) Select OK8) Close the TaskCentre clientNow upgrade the tools by running the V1.1 installation program. After the upgrade, theCSTCTOOLS database that is no longer used can be removed from the SAP SQL Server,along with the clean-up job that was used by V1.0 (this can be found in the "SQL ServerAGent->Jobs" section in SQL Management Studio).Once the tools have been upgraded, the registered Event databases can be re-configuredin the TaskCentre client:1) Start the TaskCentre client.2) Go to the SAP Business One Event global configuration screen (Manage->Tools->SAPBusiness One->SAP Business One Event)3) Select the first Agent shown in the list and press Edit4) Select Add to add a database5) On the "Register SAP Business One Database" screen, select the SAP Business Onedatabase you wish to register.6) Check the box where you wish the event capturing code to be inserted (this is usuallyjust below the "Add your code here" comment)7) Select OK16

Upgrade Instructions8) Repeat steps 4 to 7 for each database you wish to registerReporting Installation ProblemsIf you have any problems upgrading your current version of TaskCentre please contactOrbis Support.• Tel: 01202 241115• Email: support@orbis-software.com17