User manual BUSINESS OBJECTS INTERCOMPANY 5.1 FIXPACK 3 RELEASE NOTES 09-2008

[. . . ] BusinessObjects Intercompany Release Notes BusinessObjects Intercompany 5. 1 FixPack 3 Copyright © 2008 Business Objects, an SAP company. Business Objects owns the following U. S. [. . . ] · Details on the corrections made in the patch. 6 BusinessObjects Intercompany Release Notes Installing Intercompany 5. 1 FixPack3 2 2 Installing Intercompany 5. 1 FixPack3 To install Intercompany 5. 1 FixPack3: 1. Uninstall the current version on the server. Install the latest version of Intercompany. In the Intercompany Files Folder panel, select the same folder location as in the previous installation. For example, if your Intercompany files were in C:\IntercompanyFiles\ for the current installed version, then you need to select the same folder for FixPack 3. Run the Intercompany database upgrade tool to install the latest version of the stored procedures. Manually update the database schema by running the SQL statements below: · For SQL SERVER: ALTER TABLE tblExternalAuthenticationInfo ALTERCOLUMN [primaryHost] [NVARCHAR] (300)NULL ALTER TABLE tblExternalAuthenticationInfo ALTERCOLUMN [accountAccessLDAP] [NVARCHAR] (300)NULL · For ORACLE: ALTER TABLE tblExternalAuthenticationInfo MODIFY (primaryHost NVARCHAR2(300)); ALTER TABLE tblExternalAuthenticationInfo MODIFY (accountAccessLDAP NVARCHAR2(300)); 8 BusinessObjects Intercompany Release Notes Corrections in FixPack3 3 3 Corrections in FixPack3 Too many invoice child account transactions can generate an error message Too many invoice child account transactions can generate an error message In the Invoice Child Account page, if there are a lot of transactions, the following error message appears when you click to delete an invoice: value was either too large or too small for an int16 (ADAPT01121596) Distinguish name limitation in the LDAP authentication For an LDAP authentication it is not possible to specify a Distinguish Name consisting of more than 64 characters in the Authentication tab of the Control Panel. (ADAPT01110218) Intercompany 5. 1 does not support BOE XI 3. 0. 1 The reference platform for The FPM 7. 0 Intercompany 5. 1 is part of the FPM 7. 0 Suite, but was based on BOE XI R2. The FPM 7. 0 Suite is based on BOE XI 3. 0. 1 Fixpack 1. If the BOE XI 3. 0. 1 client is installed on the Intercompany 5. 1 server, BOE authentication does not work. (ADAPT01103579) Field headers in invoice reports In invoice reports the header for Invoice Text, Invoice Date, and Invoice Amount field columns is always the default one, not the alternative names created by the administrator. (ADAPT01099711) 10 BusinessObjects Intercompany Release Notes Corrections in FixPack3 Invoice date formats incorrectly changed after export and import 3 Invoice date formats incorrectly changed after export and import When you export invoices in French or German, the date formats are changed to US. When you reimport the invoices, the system expects a French or German format and rejects the lines. If you have a problem with the wrong export and import date format appearing, the ExpectedDateFormat setting needs to be added to the appSettings section of the Intercompany Import Service configuration file as shown in the sample below. [. . . ] (cqics00004409) Documentation Some sections of the online help in English were not accessible. (cqics00004421) Invoice Addition/Adjustment The Invoice Edit page incorrectly displayed non-integer amount values. (cqics00004059) 16 BusinessObjects Intercompany Release Notes Index A authentication modes with Oracle 16 M manual invoice matching 14 I installation 6 installation procedures 8 invoice group state 14 invoice IDs 14 N non-integer amount values 16 O online help 16 Oracle 16 BusinessObjects Intercompany Release Notes 17 Index 18 BusinessObjects Intercompany Release Notes [. . . ]