Symptom

This WDF Note describes known limitations of the intercompany integration solution for SAP Business One.

Solution

1. SBO-ICO: Release with restrictions
1. Add-on installation in SAP HANA Database environment
   Installation in SAP HANA database environment may take up to 1-2 hours. The background is the way SAP HANA 1.0 handles a huge number of UDFs. With SAP Business One 9.1 PL09, significant improvements were realized. Nevertheless, the situation is not satisfactory and we are working on further improvements.
   (Changed on 24.08.2018)
2. Restrictions on the replication of deletion operations for certain sub-objects
   Any fields that are subject to be replicated are specified in the "Administrator’s Guide for the Intercompany integration solution for SAP Business One"
   The replication of the deletion of sub-object records for the following business objects is currently not supported:
• Business Partner Master Data (see Note WDF 1770678)
  In an update transaction in the sender company, the deletion of sub-object records for the following objects is not replicated to the receiver companies:
• BPAddresses
• ContactEmployee
• BPPaymentMethods
• BPBankAccounts
• BPFiscalTaxID
• BPPaymentDates
• Item Master Data
  The deletion of sub-object records such as barcodes and Preferred Vendors in an update transaction in the sender company is not replicated to the receiver companies.
• Users Master Data
  The deletion of sub-object record of User Groups in an update transaction in the sender company is not replicated to the receiver companies.
• Purchase Order to Sales Order Document Exchange
  The deletion of sub-object records for
• Document_Lines
• Document_LinesAdditionalExpenses
• DocumentsAdditionalExpenses
3. Restrictions on adding a new document line
   The addition of a new document line before a closed line in an update transaction in the sender company is not replicated to receiver companies. One of these DI errors occurs: "(-5002) Invalid value [ORDR.Transfered]" or "You cannot open rows in the document" (See SAP Note 1888322) 
4. Restrictions on the replication of payment method
   Selection of more than one payment method in an Add or Update transaction in the sender company is not replicated to the receiver companies.
5. Restrictions on the replication of customer/vendor group
   Changes made in customer/vendor group master data in an update transaction in the sender company is not replicated to linked business partner master data in the receiver companies.
6. A/R Correction Invoice to A/P Correction Invoice Document Exchange
   An A/R correction invoice based on an existing A/R correction invoice does not support the replication as an A/P correction invoice. See SAP Note 1770616.
7. Delivery to Goods Receipt PO Document Exchange
   A delivery based on an existing A/R correction invoice, to be replicated as a goods receipt PO, is currently not supported. See Note WDF 1770639.
   A status update from a goods receipt PO based on an A/P reserve invoice having serial managed items and warehouses with bin locations enabled in the sender system does not update the status of the delivery document in the receiver system.
8. Document Exchange Cycle
   The document line level freight amount (FC) from the sender company is not replicated to the draft document in the receiver company. See Note WDF 1898139.
9. Barcode Master Data Replication
   The deletion of barcode master data in the sender company is not replicated to the receiver companies.
   (Changed on 19.12.2014) 
10. Key Mapping
    Intercompany does not list all items when user chooses a key mapping value from Intercompany Administration Console → Setup → Key Mapping  → Key Mapping Data section.
    (Changed on 13.10.2015)  
• Root cause: The '*' character is used in the name/description of one of the Items (e. g. Item Group, Business Partner Group, ...). You can list all Items to check this in Key Mapping → "Process Company Data" section → View Object Data.
• Workaround a) Remove the '*' character from any item that is necessary for Key mapping; Workaround b) Perform the key mapping using the Export and Import Excel Template function. 
11. SAP Business One client access via Terminal Services
    When SAP Business One client is accessed via Terminal Services and the intercompany add-on is running, users may face a minor delay while inputting large text in marketing document. Additionally, performance issues may arise when opening the screens or doing the transactions.
    (Changed on 05.05.2016)
12. Branch Inventory Warehouse Report
    Branch inventory warehouse report gives error "Name excepted : 0x20 (:main :, row:2, col:)" if one of the items has the "&" character in the description field. 
    (Changed on 21.12.2016)
13. Currency issues under certain conditions in the consolidation process
    When the intercompany solution runs the consolidation process in the consolidation company for a foreign branch (subsidiary) having consolidation source as local currency in the intercompany landscape, the solution uses the exchange rates based on the translation method (Historical Rate, Closing Rate, Average Rate) defined for each account in the branch company to calculate the journal entries value.
    When the translation method is a closing rate, the solution uses the exchange rate defined for the closing date of the consolidation period. For example, if consolidating between Jan 1st and Jan 31st, the closing rate will be the exchange rate for Jan 31st.
    Once the journal entries are imported into the consolidation company, the same journal entry will not be imported again; hence, the journal entries sum up to make the opening balance of the earlier consolidation period in the consolidation company and are not considered again for the translation purpose on the Closing/Historical/Average rate. 
    (Changed on 24.08.2018)
14. A/R Invoice to A/P Invoice Document Exchange for India Localization
    While creating the A/R Invoice to A/P Invoice document with header level freight for the India localization, DI error message appears as "Error (-5002) Tax code not defined for freight [PCH3.TaxCode][line: 1]". 
    (Changed on 01.10.2021)
15. Documents added via DI-API won't be replicated by Intercompany
    When using an add-on or application creating SAP Business One documents using the SAP Business One SDK via DI-API, these documents won't be valid for the Intercompany document exchange cycle.
    (Changed on 17.11.2021)
16. Language Changed via Custom Language Tool by SAP
    The SAP B1 DI API is not supporting the update on the User master if the new custom language is imported by the SAP Custom Language Tool. E.g. Romanian, etc. Therefore, if you use the Custom Language Tool then you will not be able to use the User Master Replication feature of Intercompany until the SAP fixes this.(Changed on 22.05.2023)
17. G/L Account Replication  
• While replicating the G/L account using the intercompany solution, the G/L account may be located at a different place under a parent in receiving company if the parent account has more than one active account because the SAP B1 DI API does not support the location of the G/L account under a parent account. (Changed on 22.05.2023).
• The deletion of G/L Account master data in the sender company is not replicated to the receiver companies. (Changed on 31.10.2023).
  
18. Working with multiple SAP B1 localization on Terminal Services
    The decimal and thousand separator settings on the terminal server should match the decimal and thousand separator settings of the SAP Business One company that users are working in. If the operating system's decimal and thousand separators differ from the dot (.) and comma (,) convention, the solution will align with the decimal and thousand separators set in SAP B1's display settings. If they do not match, an error message will appear, and the add-on will fail to connect. (Changed on 25.08.2024)
19. Restrictions on the replication of "Do Not Apply Discount" settings in Item Master
    The replication of the "Do Not Apply Discount" setting in the Item Master is not supported, as the SAP B1 DI API does not expose the DI property for this setting. (Changed on 20.03.2025)
20. Maximum Line Items in the Document Exchange Cycle
    To ensure smooth processing and optimal system performance, it is recommended not to create a document with more than 1,500 line items for Intercompany Trade. If you encounter a scenario where a document requires more than 1,500 line items, we strongly recommend splitting it into multiple smaller documents. This approach helps maintain system stability, enhances data accuracy, and ensures the efficient handling of transactions.

2. SBO-ICO: Fixed Limitations (selected)

• Restrictions on the Replication of Deletion Operations for Certain Sub-Objects
  The Interest on Arrears % and Total Discount % fields in an update transaction in the sender company is not replicated to the receiver companies. (Fixed with Intercompany integration solution PL08)
  (Changed on 19.12.2014)
• Item Master Data
  The Valuation Method field in an update transaction in the sender company is not replicated to the receiver companies. (Fixed with Intercompany integration solution PL08)
  (Changed on 19.12.2014)
• Bill of Material (BoM) Replication
• The deletion of sub-object records for Document_Lines in an update transaction in the sender company is not replicated to the receiver companies. (Fixed with Intercompany integration solution PL08).
• Payment Terms of Business Partner Master Data Replication
  While updating Payment Terms for the Business Partner, SAP Business One GUI displays "Do you want to apply the associated payment terms to the business partner". In case "No" is chosen, the Price List in Payment Terms tab of the Business Partner Master Data is not updated to the one assigned in this Payment Terms. But after the change replication to the receiver company database, the Price List in Payment Terms tab of the same global Business Partner Master Data is updated unexpectedly to the one assigned to the Payment Terms. (Fixed with Intercompany integration solution PL26)
  (Changed on 03.05.2018) 
• Restrictions on the replication of Payment terms
  Changes made to the payment terms master data in an update transaction in the sender company is not replicated to linked business partner master data in the receiver companies. (Fixed with Intercompany integration solution PL26)
  (Changed on 03.05.2018)