Symptom

You have followed the Administrator's Guide and the User Guide for the intercompany integration solution for SAP Business One (integration solution). However, you require assistance and troubleshooting.

Solution

In addition to this WDF Note, you can find instructions on common topics related to the intercompany solution on the intercompany solution product page on Walldorf Portal.

Table of contents:

1. Version compatibility with SAP Business One
2. Tips on Identifying Errors
3. Installation Prerequisites
4. Errors During Installation
5. Errors During Setup and Configuration
6. Errors During Run-time
7. Standard Integration Solution Maintenance
8. Performance Optimizations  

1. Version compatibility with SAP Business One

When installing or upgrading the integration solution, make sure that the version/patch level is compatible with SAP Business One as specified in the list below.
If you upgrade SAP Business One and have the integration solution already installed, please make sure that the new SAP Business One version/patch level you are upgrading to and the integration solution version are compatible and available as specified.

The integration solution is always adapted to the latest patches of SAP Business One, full compatibility is assured and extensively tested. Therefore, respective patches for the integration solution are delivered about 3 weeks after the release of SAP Business One patches, at the latest.

2. Tips on Identifying Errors

2.1. The intercompany integration solution must be deployed again from the landscape page whenever any of the below situations are verified (see Intercompany Administrator's Guide, point 5.2.7):

• Any SLD registration, details or email connectivity settings are updated
• A new company template is assigned to a branch company in the Landscape page, under the company details
• Any update is performed on the Landscape page on the setup window for any branch 

Note: Whenever you deploy the solution, you must perform the currency key mapping.

2.2. Intercompany Solution Troubleshooting Tool

This tool is designed to help partners or customers identify problems themselves or export all necessary information when creating support incidents. For details, refer to Note WDF 2177037.

Note: This tool can only be used for intercompany solutions running with B1iF 1.x. If this tool is used for intercompany solution running with B1if 2.0, then the Landscape Details section will not retrieve any information (as can be seen in the attachment "Troubleshooting Tool on ICO with B1iF 2.0.png") and the status of CXS.IC package in Version section will not be correct. Please go to B1if 2.0 →  Scenario → open package CXS.IC → Deployment panel to check status.

2.3. The following paths can help you identify the problem:

• In the SAP Business One Main Menu, choose Window → Messages/Alerts Overview.
• In the Intercompany Administration Console, choose Monitoring → Message Log.
• In the Integration Framework, choose Monitoring → Message Log and click the Result Message link to view the error string; click Msg to see the complete payload; click Exp to export the complete message for debugging.
• In the Integration Framework, choose Monitoring → Queue Monitor. Is the queue stuck and not processing? If so, which streams are blocked?
• In the Integration Framework, choose Control Center → Monitoring → IPO - Step Status. Select Deactivated Steps only and choose Submit. When an exception occurs, you will receive a list of IPO steps that were deactivated along with the error messages.
• Use the Troubleshooting Tool to provide detailed information when creating a support incident: In Integration Framework, choose Tools → Troubleshooting, and in the Functional Group field, select B1 Intercompany (see Note WDF 2177037).
  

Note: Error messages help resolve the issue and should be included in support incidents.

3. Installation Prerequisites

The integration solution relies on a proper setup of the integration framework. Please verify that the following steps have been performed prior to installation of the integration solution:

• To troubleshoot integration framework installation and setup issues, see SAP Note 1618978.
• EventSender setup has been configured and is running. To troubleshoot Event Sender issues, see SAP Note 1882000.
• All companies were automatically created in B1iF → SLD; if not, follow the steps in SAP Note 2032666 to create all company entries.
• In integration framework → SLD, for all company databases and the IC_Landscape entry, the DI and JDBC test connections must be successful. If you receive any errors, check SAP Note 2029714.
• In integration framework → SLD → SBO-COMMON and IC_Landscape entry, the test connection for JDBC section succeeds.
• The SBO-COMMON.SEVT table is cleared of old entries from old systems. 
• If the intercompany solution is running on SAP HANA, you must install HDB client 32 bit on the machine on which you want to install the intercompany solution.

4. Errors During Installation

4.1. The add-on cannot be installed on SAP HANA databases. The intercompany solution add-on log contains: "... [HDBODBC32] General error;258 insufficient privilege: Not authorized"

Solution: See Note WDF 2639423.

4.2. Error: "B1iadmin runtime user is deactivated"

• Root cause: The B1iadmin user is deactivated because there were too many failed attempts to log on/connect to the integration framework.
• Solution:
• Log on to integration framework and choose Maintenance → User Administration → click Admin Users. For the B1iadmin user, verify that active=true.
• Click Runtime Users to verify that for the B1iadmin user, active=true.
• Go to Start → All Programs → Integration Solution for SAP Business One → SAP Business One EventSender → Setup. In Step 3/5, ensure that the test connection to the integration framework server is successful.

4.3. Error: "Intercompany Add-on failed to update the database"

• Root cause 1: Relevant code for the integration solution does not exist in the SBO_SP_TransactionNotification stored procedure.
• Solution 1: Manually copy the code in the SBO_SP_TransactionNotification stored procedure from a working installation and paste it into the corrupted one. Ensure that all intercompany solution stored procedures (which start with "sbo.CTX_IC_SP_XXX") exist in the company database.
• Root cause 2: Partner customization is the SBO_SP_TransactionNotification stored procedure.
• Solution 2: Temporarily remove (not only comment) partner customization from stored procedure. After installing the add-on, revert to the customization.
• Root cause 3: UDTs starting with @CTX_* are missing in the database.
• Solution 3: Create a support incident. 
• Root Cause 4: In the intercompany solution logs, you get the error: "General error;329 cannot use duplicate name of function or procedure:CTX_IC_UPDATEFRENCHRESOURCESTRINGDATA"
• Solution 4: Please perform the below mentioned steps for all the company databases where the issue occurs:
1. Delete the CTX_IC_SP_UPDATEFRENCHRESOURCESTRINGDATA stored procedure from the database.
2. Log on to SAP Business One Client → Tools → User Defined Window → CTX_CONF and remove the row.
3. Log out from SAP Business One Client and log in again. The intercompany solution add-on starts the initial setup again. 

4.4. When installing the integration solution, the application displays the error: "Unable to connect to Database Server. Please check the credentials."

• Root cause: SAP HANA client is not installed in Windows server.
• Solution: Install both 32-bit and 64-bit SAP HANA client in Windows server (recommend to use the C: drive).

4.5. The intercompany add-on registration process takes a long time to complete

• Root cause: Huge number of files in the Windows Temp directory can cause the system to slow down.
• Solution: Clear Windows temporary files:
1. Open the Windows run prompt (Windows+R) and enter %temp% in the search box.
2. Press Enter and delete files from this folder.
3. Go to C:\Windows\Temp and delete files from this folder.

4.6. Error: "Add-on Intercompany - uninstall failed"

• Root cause 1: Add-on does not have write permission to the SAP folder. 
• Solution 1: Assign write permission to the SAP folder and run SAP Business One client as an administrator. 

4.7. Error: Intercompany add-on menus are not displayed in the SAP Business One client after the add-on installation is complete

• Root cause 1: The intercompany solution is not deployed 
• Solution 1: Deploy the intercompany solution

4.8 Error: Intercompany menu item not visible

• Root Cause 1: Existing intercompany installation with IC PL 34, 35, 36, intercompany not deployed
• Solution: Deploy intercompany installation with IC PL 34, 35, 36 to view intercompany menu
• Root Cause 2: Existing intercompany installation with IC PL 37, intercompany deployed
• Solution: Existing intercompany installation with IC PL 37 will always display the intercompany menu
• Root Cause 3: Fresh intercompany installation with IC PL 37, intercompany not deployed
• Solutions: Deploy intercompany for fresh intercompany installation with IC PL 37

4.9 "Branch inventory warehouse report" is not visible and below error occurs:

      com.sap.b1i.xcellerator.XcelleratorException: XCE001 Nested exception:com.sap.b1i.bizprocessor.BizProcException: BPE001 Nested exception: com.sap.b1i.utilities.UtilException: UTE001 Nestedexception: com.sap.engine.lib.xml.parser.ParserException:
Name expected: 0x20(:main:, row:2, col:1614)

• Root cause: The are special characters (! @# &*:;) in the item master data.
• Solution: Remove the special characters from item master data for all Intercompany participant companies.
  

5. Errors During Setup and Configuration

5.1. When opening the Landscape menu from the Intercompany Administration Console, the application displays: "SAP B1iP detected an error: Login failed for user 'sa'"

• Root cause: Wrong JDBC credential is stored in the company system entry from integration framework SLD.
• Workaround: In the Administration Console, choose UI → SLD → B1i Server. Ensure that the JDBC and DI test connection for all listed company system entries are successful.

5.2. You are running Microsoft Internet Explorer 9.0 or higher and some fields and menus do not respond when clicked

• Workaround: Use the latest Google Chrome or Microsoft Internet Explorer version 11 or higher. Otherwise add the integration framework server to be viewed in compatibility view: Open integration framework in IE, choose Tools → Compatibility View Settings and choose Add.

5.3. In the Intercompany Landscape window, you are unable to set a company as the head office

• Root cause: A company that was previously designated as the head office has been removed from the system.
• Solution: Open a support incident. In future, when removing a company that is set as head office, follow the steps provided in Note WDF 2022025.
  

5.4. When opening the Landscape menu from the Intercompany Administration Console, the application displays: "SAP B1iP detected an error: 500 - Internal Server Error"

• Root cause: Wrong JDBC credential is stored in the company system entry and SBO-COMMON system entry from integration framework SLD.
• Workaround: In the Administration Console, choose UI → SLD → B1i Server. Ensure that the JDBC and DI test connection for all listed company system entries are successful; ensure that the JDBC test connection for SBO-COMMON is successful.

5.5. In the Key Mapping option on the Intercompany Administration Console, in the Import Data area, you choose ALL for both Branch Company and Object Name; then you click Import, and the application displays: "Violation of PRIMARY KEY constraint 'PK_XXXX_XXXX'. Cannot insert duplicate key"

• Root cause: Duplicate entries in the keymapping tables.
• Workaround: Perform a backup of the Landscape Database; clear the 'KeyMappingUI' table and import the KeyMappings again in the Intercompany Administration Console (choose Setup → Key Mapping and click Import in the Import Data area).

5.6. In Intercompany Administration Console → Landscape → Deploy option, the deployment fails in steps "Initializing Solution Stage 1 - Validating Database Connections" and/or "Initializing Solution Stage 2 - Configuring Participant Companies" and displays: "com.sap.b1i.xcellerator.XcelleratorException: XCE001 Nested exception: java.lang.Exception: com.sap.b1i.xcellerator.XcelleratorException: XCE001 Nested exception: com.sap.b1i.adapter.jdbc.JdbcAdapter$LoadJdbcDriverFailureException: Could not find the driver"

• Root cause: Missing SLD entry for the Landscape Database in integration framework → SLD → B1iServer.
• Workaround: Add the SLD entry for the Landscape Database manually:
1. Choose Integration Framework → Tools → Control Center → Development → Execute BizFlow:
• Bizflow: com.sap.b1i.vplatform.system/bfd/SLDcreateSysId.bfd(unified)
• Parameters: sysid=001CXS0000,systype=J.AnySystem
2. Press Submit!.
3. In Integration Framework → SLD, change the name of the newly created "001CXS0000" entry to "IC_Landscape" and correct the connectivity parameters.
4. Retry the deployment for the solution.

5.7. In Intercompany Administration Console → Setup → Key Mapping → Keymapping Object Selection section, choose object value for the Object Name - Object ID field, click the Auto Map button, click Save → Notification window "This action will save the records. Do you want to continue?" pops up, click OK → Information window "Saving data... This may take some time" pops up. No success message appears.  Key mapping data is not saved.

• Root cause: Microsoft Internet Explorer compatibility issue.
• Workaround: In IE, press [F12] or start Developer Tools → Change "Browser Mode: IE8" and "Document Mode: IE8". Complete key mapping for each object. Verify that the key mapping values are saved successfully.

 5.8. When a user adds a document in the SAP Business One Client, a system message pops up: "The selected branch company is no longer active"

• Root cause: Inconsistent branch codes defined in Intercompany Admin Console and SAP Business One database. 
• Workaround:
• To find the branch code defined in SAP Business One, run this query in each company DB:
  Select distinct U_CTX_ICPC from OCRD where U_CTX_ICPC!='NULL' and U_CTX_ICPC!=''
• Edit sysid.xml: Integration Framework → Tools → Control Center → Development → X-Edit and choose BizStore URI as "/com.cxs.b1i.directory.cc/Deployment/sysid.xml(unified)" → Submit → Update with correct branch code in the Branch field for each company → Save
• Redeploy the Intercompany landscape

5.9. When a user maps keys in Intercompany Administration Console → Setup → Key Mapping → Key Mapping Data section → Choose a Key Mapping Value, the list does not show all items

• Root cause: The asterisk (*) character is used in the name/description of one of the objects (for example, Item Group, Business Partner Group, and so on). You can list all objects to check this in Key Mapping → Process Company Data section → View Object Data.
• Workaround 1: Remove the * character from any object that is necessary for Keymapping
• Workaround 2: Perform the Keymapping using the Export and Import Excel Template function

5.10. When you perform manual consolidation in SAP Business One Main Menu → Consolidation → Manual Consolidation, Import and Export of Journal Entries displays the error: 'At least one of the mapped accounts is not available in chart of accounts'.

• Root cause: Blank row in account mapping table
• Workaround: In SAP Business One, go to Tools → User-Defined Windows → CTX_ACCMAP-COA Account Mapping. Check if there is a blank row in this table. Delete this row and update the table, then perform manual consolidation.

5.11. In the Intercompany Administration Console → Landscape → Deploy option, the deployment fails in step "Initializing Solution Stage 1 - Validating Database Connections" and displays: "XCE067 The port specified with the given IPO-Step URI does not exist /DLA.PMisc/com.cxs.b1i.ipo/ipo/DP.PMisc.ipo/PMisc#Xs(B1DI)"

• Root cause: Incorrect previous deployment
• Workaround: Clear the deployment files from the bizstore, as follows:

1. In Intercompany Administration Console → Landscape write down or take a screenshot of all the branch codes and configuration.
2. Click the Reset button on the Deployment Result screen.
3. Log on to the Integration Framework page, and go to Tools → Control Center → Maintenance → BizStore Delete.
4. Choose:

• dataset: com.cxs.b1i.directory.cc / group: Deployment / Index: unified / Document: sysid.xml (only in case sysids have changed for the participating branch companies)
• dataset: com.cxs.b1i.log / group(s): Deployment, ConfirmResult, InitializationStatus, SetDefaultDataStatus and UpdateCurrency

5. Go to Intercompany Administration Console → Landscape  → click Refresh Companies and redeploy the solution.

5.12. In Intercompany Administration Console → Landscape → click the ellipsis (...) button to configure a company; error occurs: 'SAP Business One intercompany integration solution add-on is not yet installed in this company'. 

• Root cause 1: The JDBC connection URL (Integration framework → SLD → <DATABASE_NAME> → JDBC) is referring to a different database name. 
• Workaround 1: Correct the JDBC's URL to refer to the correct database. 
• Root cause 2: Add-on is not correctly installed in company database
• Workaround 2: 
1. Back up the company database. 
2. Clear the records in table [@CTX_CONF].
3. Log on to the company database in SAP Business One client as administrator.
4. The add-on will be installed again. 
5. Log on to Integration framework → Tools → Control Center → Maintenance → BizStore Delete → enter details as below → click Submit!
   

In Constrain to dataset - com.cxs.bidirectory.cc
In Constrain to group - Deployment
In Constrain to Index Alias - Unified
In Constrain to Document Name - sysid.xml

6. Log on to Integration framework → SLD, find the company database from the list, click Test Connection for the DI section and make sure the connection is successful. 
7. Log on to Integration framework → SLD, find the company database from the list, check the JDBC section, and make sure the database name is correct; click Test Connection and make sure the connection is successful.
8. Log on to Intercompany admin console → Landscape, configure and redeploy the solution.
    
• Root cause 3: The SAP Business One company database name has invalid characters.
• Solution 3: Refer to SAP Note 2261068 for details.

5.13. In Intercompany Administration Console → Setup → Key Mapping  → Key Mapping Data section  → choose a Key Mapping object; the list does not show any "Key Mapping Data" on UI.

• Root cause: Space character in database name, or the schema name is in lower case (in the case of SAP HANA). Refer to SAP Note 2098725 for details.
• Workaround 1: In SQL server management studio, remove the space character from the database name. In case of HANA, export the schema and rename the schema in upper case only when importing it. 

5.14. While executing the Chart of Accounts distribution process in a Consolidation company, Import task, you get a failure (SAP Business One Client → Administration → Setup → Intercompany → Chart of Accounts Distribution); by choosing the "Failure" link, the XML result shows "Process not executed because of previous error".

• Root cause: A semi-colon character (;) is included in one of the Chart of Accounts' account names or descriptions. 
• Workaround: Remove all semi-colon characters from all account names and description fields, and retry the Chart of Accounts Distribution Export/Import process. 

5.15. When you map keys in Intercompany Administration Console → Setup → Key Mapping → Key Mapping Data section → choose a Key Mapping Value, save the Key mapping, a message states the save action was successful. When you check the status of key mapping for the object again, you see it was not saved.

• Root cause: The colon (:) character is used in the name/description of one of the objects (for example, Item Group, Business Partner Group, and so on). You can list all objects to check this in Key Mapping → Process Company Data section → View Object Data.
• Workaround 1: Remove the colon character from any object that is necessary for Keymapping.

5.16. After renaming an SLD Category in the Intercompany Administration Console → SLD or Integration Framework → SLD, you cannot modify the company templates in  → Company Template, however you can still assign the company templates to companies in Landscape.

• Root cause: Renaming the SLD Category does not rename the association of company templates to the new SLD Category name.
• Workaround 1: Export the company templates before renaming the SLD Category and import them to the new.
  

6. Errors During Run-time

6.1. "Error: Access to the path 'C:\Program Files\SAP\SAP Business One\Addons\SAP\Intercompany\CTX_IC_DAL.dll' is denied"

• Root cause: Another instance of CTX_IC_Intercompany.exe is running
• Solution: In Windows Task Manager, on the Processes tab, choose End Process for all instances of CTX_IC_Intecompany.exe

6.2. When starting the integration solution, the application displays: "Input string was not in a correct format"

• Root cause: The local settings defined in the operating system regional settings have a thousands separator.
• Workaround: In Windows Control Panel, change the property in the local settings so that the thousands and decimal separator values are the same as specified in SAP Business One. You can verify the local settings by choosing Control Panel → Clock, Language, and Region → Region icon → Formats tab → Additional settings button → Numbers tab, and checking the value set for theDecimal symbol field (=decimal separator) and Digit grouping symbol field (=thousands separator).  

6.3. These or similar errors occur: "Incorrect syntax near ')'", "DI Error: (-2028)  No matching records found"

• Root cause: Key mapping has not been completed for all companies.
• Solution: In Intercompany Administration Console, choose Setup → Key Mapping. Complete the key mapping process for all objects in all companies and then choose the Save button.

6.4. When running the consolidation process, this or similar error occurs: "ClassNotFoundException", "The first argument to the non-static Java function 'subtract' is not a valid object reference"

• Root cause: During upgrade, the installer was not run as administrator and not all upgrade files were copied.
• Solution: Please refer to Note WDF 2665974.  
  

6.5. Master data does not replicate, although no errors are shown 

• Possible root cause: In the Intercompany Administration Console, on the SLD tab, for one of the company databases, in the userName field, the manager user details have been entered.
• Solution: In the SLD, the integration framework user details must be configured for all companies.

6.6. When exporting Chart of Accounts in the consolidation database (Administration → Setup → Intercompany → Chart of accounts distribution → Export tab), the application displays: "Your integration Server is down"

• Root cause: The configuration in SAP Business One is incorrect.
• Solution a: In the integration framework Server Details window (Administration → Setup → Intercompany → B1i Server Details), ensure the correct server and port are specified. The server address must be set identically to the one set in integration framework (Integration Framework → Maintenance → Cfg Runtime → Integration Framework Server). For HTTP connection, the default port number is 8080; for HTTPS connection, the default port number is 8443. Also ensure that the User Name field is set to B1iadmin and that the password is correct.
• Solution b: The user name is deactivated in B1i. To activate B1i user, go to Integration Framework → Maintenance → User Administration → Runtime Users → click Toggle Activation for B1iadmin user. If you change the password for B1iadmin runtime user, make sure you update in SAP Business One client and event sender setup afterwards.  

6.7. Auto map account in the consolidation database (Consolidation → Consolidation Account Mapping) is not working

• Root cause: If you are using single level consolidation, account mapping is not required in the consolidation company. You only need to perform account mapping in branch companies where it is required to determine to which account the balance will be transferred upon consolidation.

6.7. When importing Chart of Accounts in the consolidation database (Administration → Setup → Intercompany → Chart of accounts distribution → Import tab), the application displays 0% progress

• Solution:
1. Go to Integration Framework → Tools → Control Center → Maintenance → BizStore Delete → choose com.cxs.b1i.Consolidation in Constrain to dataset → click Submit!
2. Export Chart of Accounts again from SAP Business One client (Administration → Setup → Intercompany → Chart of accounts distribution → Export tab).
3. Import Chart of Accounts, company by company.

6.8. When importing journal entry in the consolidation database (Administration → Consolidation → Manual Consolidation → Import tab), DI Error: (-5012) Unbalanced Transaction or DI Error: (-10) Transaction Without Amount

• Root cause a: Add-on version (SAP Business One Client → Administration → Add-Ons → Add-On Manager) is not compatible with scenario version (Intercompany admin console → About) of the integration solution.
• Solution a: Make sure versions are compatible; refer to 1. Version compatibility with SAP Business One.
  
• Root cause b: For consolidation company, currency decimal setting needs to be change, depending on rounding method defined in Administration→ System Initialization → Document Settings → General tab → Rounding Method
  
  
•  If Rounding Method is "By currency":
  
  
• Workaround for Consolidation company running on MS SQL Server instance:
• Ensure that there is no active connection to the consolidation company. You can view details about the connections that are linked to the current company database using Microsoft SQL Server Management Studio.
• Go to Administration → Setup → Financials → Currencies screen. In the Decimals field, change the value to "6 Digits" for the currency which is related to the consolidation method you defined in the landscape.
  
  
• Workaround for Consolidation company running on SAP HANA DB instance:
• Ensure that there is no active connection to the consolidation company. You can view details about the connections that are linked to the current company database using the query "select * from m_connections". Note that even the sleeping process will block transactions.
• Log in to the consolidation company.
• Go to Administration → Setup → Financials → Currencies. In the Decimals field, change the value to "6 Digits" for the currency which is related to the consolidation method you defined in the landscape. 

Note: Even the sleeping process will block transactions. Check if Eventsender is active and running; if so, stop the service to be able to change the settings.

•   If Rounding Method is  "By document":
  
  
• Workaround for Consolidation company running on MS SQL Server instance:
• Ensure that there is no active connection to the consolidation company. You can view details about the connections that are linked to the current company database using Microsoft SQL Server Management Studio.
• Log in to the consolidation company.
• Go to Administration → System Initialization → General Settings → Display tab → Amounts and change the amount setting.
  
  
• Workaround for Consolidation company running on SAP HANA DB instance:
• Ensure that there is no active connection to the consolidation company. You can view details about the connections that are linked to the current company database using the query "select * from m_connections".
• Log in to the consolidation company.
• Go to Administration → System Initialization → General Settings → Display tab → Amounts and change the amount setting.

Note: Even the sleeping process will block transactions. Please check if Eventsender is active and running; if so, stop the service to be able to change the settings.

6.9. When opening the Company Template (Administration → Setup → Company Template), an error message is displayed: "SAP B1iP detected an error: Variable '$col.disabled' has not been bound to a value"

• Root cause: Version mismatch between the integration solution and SAP Business One.
• Solution: Make sure that versions are compatible; refer to 1. Version compatibility with SAP Business One.

6.10. Creating an A/P invoice outside of the Intercompany Marketing Document Exchange using one of the branch partners generates the error message: “(1) Intercompany type BP cannot be selected for non-branch documents”

It is not possible to create such a document because the A/P Invoice for the branch partner should be generated automatically by the Intercompany Marketing Document Exchange.

6.11. Sales order draft based on purchase order could not be created with error "DI Error: (-5002) Chosen BP is not a customer [ORDR.CardCode], ..."

• Root cause: Corrupted intercompany store procedure.
• Solution: Go to SAP Business One client → Tools → User Defined Window → CTX_CONF → remove the row. Then log out from SAP Business One client and log in again; the intercompany add-on starts and registers again.    

6.12. When exporting journal entry in the consolidation database (Administration → Consolidation → Manual Consolidation → Export tab), a System Message is displayed: Unable to connect to the selected company

• Root cause 1: Integration framework is busy processing other transactions. To check what transactions are running, go to Integration Framework → Monitoring → Queue Monitor and Integration Framework → Tools → Control Center → Monitoring → Execution Status).
• Solution 1a: Wait until the messages are processed. Try to export again later.
• Solution 1b: Delete the transactions and do a quick clean-up:
  a. Go to Integration Framework → Monitoring → Queue Monitor and delete the queue.
  b. Go to Framework → Tools → Control Center → Maintenance → TLog Delete, choose status as "STARTED" and "INCOMMIT"; click Submit!.
  c. Make sure that no transactions are listed in Integration Framework → Tools → Control Center → Monitoring → Execution Status.
  d. Restart DI proxy services.
• Root cause 2: DI test connection for the companies from integration framework SLD is not successful (Integration Framework → SLD → B1i Server).
• Solution 2: Refer to SAP Note 2029714.

6.13 When importing journal entry in the consolidation database (Administration → Consolidation → Manual Consolidation → Import tab), Failure Message: com.sap.b1i.xcellerator.XcelleratorException: XCE001 Nested exception: com.sap.b1i.bizprocessor.BizProcException: BPE001 Nested exception: com.sap.b1i.xcellerator.XcelleratorException: XCE001 Nested exception: com.sap.b1i.xcellerator.XcelleratorException: XCE001 Nested exception: java.lang.RuntimeException: Invoke of: DoQuery Source: SAPbobsCOM.Recordset.90.0 Description: 1). [Microsoft][SQL Server Native Client 11.0][SQL Server]Incorrect syntax near ')'. 2). [Microsoft][SQL Server Native Client 11.0][SQL Server]Statement(s) could not be prepared

• Root cause 1: Keymapping for currency object is not completed. 
• Solution 1: In the intercompany solution, complete keymapping for currency object.
• Root cause 2: Exchange rates for consolidation database are not defined in SAP Business One.
• Solution 2:
1. Check Exchange Rates and Indexes in SAP Business One for consolidation company. If there is any gap, complete the exchange rates, save, and then sync to other companies.
2. Restart SAP Business One Integration Service.
3. Export the Journal Entries and then import.

6.14 Adding intercompany type documents (Global Business Partner/Global Items/Purchase Order/Sales Order, and so on) and receiving error: "To generate this document, first define the numbering series in the management module"

• Root cause: Default manual series is locked for the affected document. 
• Solution: Please check the default manual series for the document:
1. Go to SAP Business One Client → Main Menu → Administration → System Initialization → Document Numbering.
2. Double-click the row for which the error occurs and verify document series. If default manual series is locked then unlock and update this.
   Example: If the error occurs in adding of global business partner then in the Document Numbering window, double-click the row Business Partners - Customer. In Series - Business Partners - Customer - Setup, deselect the Lock column for the Manual series and save Settings.

6.15. Exporting journal entry in the consolidation database (Administration → Consolidation → Manual Consolidation → Export tab), and receiving System Message: Error occurred while exporting journal entries

• Root cause 1: DI test connection for the companies from Integration Framework SLD is not successful (Integration Framework → SLD → B1i Server).
• Solution: Refer to SAP Note 2029714.
• Root cause 2: Automatic Consolidation was attempted but stopped before the Manual Consolidation was run; however the system did not refresh properly and still is on Automatic Consolidation.
• Solution: Refresh the system status:
1. Go to Administration → Setup → Intercompany → Consolidation Automation.
2. Change the Execution Time (Hour) to 00.
3. Click OK.
4. Start and stop the consolidation.

6.16. After user rejects intercompany draft A/P Invoice in sender company, an error occurs in receiver company when system tries canceling the corresponding A/R Invoice. Error: "B1 Transaction was terminated implicitly by DI-API, internal status will switch to unusable status"

• Root cause: Incorrect setting.
• Solution: 
1. After rejecting the A/P Invoice from the sender company please go to the receiver company. 
2. In the receiver company, go to Administration → System Initialization → Document Settings → increase the number of Max. No. of Days for Cancelling Marketing Documents Before or After Posting.
3. Right-click the A/R Invoice and choose Cancel. A new window A/R Invoice - Cancellation appears; click the Add button.

6.17. User adds a global Business Partner in sender company and error occurs in receiver company when replicating: "G/L account not defined in house bank account; define a G/L account for this house bank account"

• Root cause: G/L accounts are not correctly defined in receiver company.
• Solution:  Go to Administration → Setup → Banking → House Bank Accounts and in the House Bank Accounts- Setup window, define a G/L account in the G/L Account column.

6.18. When using G/L branch allocation feature, you encounter DI Error: (-10) Transaction Without Amount

• Root cause: Currency change in branch company
• Solution: 
  a. Go to Intercompany Administrator UI → SETUP → Landscape, and click Refresh Companies.
  b. Click Deploy to redeploy the landscape.
  c. Go to Intercompany Administrator UI → SETUP → Key Mapping, and complete key mapping for currency object.

6.19. Update any field of a global Item and you encounter DI Error: (-10) Item code already exists, in the Intercompany message log failed section

• Root cause: Incorrect JDBC schema name in SLD section
• Solution: Go to Integration Framework UI → SLD, check the schema name in the JDBC section for sender and receiver companies, and update the value to the correct schema name.

6.20. When you perform Manual Consolidation in SAP Business One Main Menu → Consolidation → Manual Consolidation, Export of Journal Entries displays the error: 'Export Failed: There is another process ongoing for this Branch Company'

• Root cause: Another task is pending or deleted in this branch company.
• Workaround: Reset the Consolidation from Intercompany Admin Console:
1. Go to Intercompany Administration Console → PREFRENCES → Consolidation Configuration.
2. Click the Reset button in the Reset Consolidation section.
3. Log on to the company and perform the Manual Consolidation again. 

6.21. When adding a marketing document in the SAP Business One client, the "DRF16" error occurs

• Root cause: After you installed the integration solution add-on in one company, you restored the company to a second company. This results in the first company/schema name in the intercompany stored procedure being called in the second company.
• Solution: To correct the stored procedure:
1. Back up the second company database.
2. Open the SBO_SP_TRANSACTIONNOTIFICATION definition. Drop the stored procedure, correct the company/schema name in the "XXX" field below, and create the stored procedure again.
   CALL "XXX"."CTX_IC_SP_TRANSACTIONNOTIFICATION"

6.22. While adding a marketing document in the SAP Business One client, the error "Error description: Item - Invalid item [xxx-xx]. Form Unique Id: 'x_xxx'. Item Unique Id: 'Combo" occurs

• Solution:

1. Back up the company database in which the issue occurs.
2. Clear the records in table [@CTX_CONF].
3. Log on as administrator to the company database in SAP Business One client.
4. The add-on will be installed again.
5. Log on again to the company database and add the marketing document.

6.23. While adding a document in the SAP Business One client, the error "com.sap.engine.lib.xml.util.NestedException:Error parsing query" occurs

         Solution: Refer to Note WDF 2665974.

6.24. When exporting Chart of Accounts in the consolidation database (Administration → Setup → Intercompany → Chart of accounts distribution → Export tab), the application displays: "Connection has failed"

         Solution 1:

1. Go to Intercompany Administrator UI → SETUP → Landscape and click Refresh Companies.
2. Click Deploy to redeploy the landscape.
3. Go to Intercompany Administrator UI → SETUP → Key Mapping, and complete key mapping for the currency object.

         Solution 2: 

Create a support incident with support.

6.25. When performing transactions which involve B1i Server Details configured with "HTTPS" protocol, and ICO add-on version PL35, PL36 or PL37, the application displays: "Either integration server is down or invalid B1i Server Details."

• Root cause: The generated url configured with HTTPS protocol is incorrect.
• Solution a: In the integration framework Server Details window (Administration → Setup → Intercompany → B1i Server Details), use HTTP connection. Also ensure that the user specified is active.

6.26. When creating a Sales Order in the Intercompany Document flow, the transaction fails in the intercompany message log with: "Invalid column name: U_CTX_RCBID"

• Root cause: Missing licenses for the SAP Business One user when running the intercompany initialization script.
• Solution:
1. In the License Administration window of the SAP Business One client (Administration → License → License Administration), assign a Professional, B1i, SAP Add-ons, SDK Tools and SAP-Intercompany to the user
2. In the SAP Business One client Tools → User Defined windows → CTX_CONF, change the SQL version to "0" and save
3. Close the SAP Business One client and open it again
4. Wait for the intercompany solution add-on initialization script to finish

6.27. Master Data replication of Items or Business Partners fails and in the intercompany solution message log you can see the exception: "[Microsoft][SQL Server Native Client 11.0][SQL Server]Incorrect syntax near ';'. 3). [Microsoft][SQL Server Native Client 11.0][SQL Server]Incorrect syntax near ','. 4). [Microsoft][SQL Server Native Client 11.0][SQL Server]Statement(s) could not be prepared. -The di call #1 did fail"

• Root cause: Invalid characters in the master data ("&" or "'")
• Solution: Remove the invalid characters from master data.
  

7. Standard Integration Solution Maintenance

 7.1. Removing an existing company from the system

• Ensure that there are no pending processes in integration framework → Monitoring → Queue Monitor and in SBO-COMMON.SEVT.
• If the company is a head office, follow the steps in Note WDF 2022025.
  
• Remove the database from the SQL Server (optional).
• Redeploy the integration solution.
• Perform key mapping.

7.2. Restoring the backup of an existing company

• Ensure that there are no pending processes in integration framework → Monitoring → Queue Monitor and in SBO-COMMON.SEVT.
• Note the current System ID in the SLD.
• Restore the database.
• Verify that the System ID has changed in the SLD.
• Redeploy the integration solution.
• Perform key mapping.

7.3 After running intercompany solution for a while, you decided to uninstall intercompany scenario and add-on. However, you cannot unmark the global attribute for items. To entirely clean up intercompany solution related setup, follow these steps:

1. Back up the company databases.
2. Modify stored procedure "SBO_SP_TransactionNotification".
3. Delete/Comment out intercompany stored procedure "CTX_SP_TransactionNotification".
4. Execute stored procedure "SBO_SP_TransactionNotification".

8. Performance Optimizations

Please refer to Note WDF 2353460.