This WDF Note contains information related to Walldorf Intercompany integration solution Version 55, as well as its embedded SAP Business One Integration Hub.
Version Installation:
This version can be used to directly upgrade, update, or install from scratch.
Compatible SAP Business One versions (only these combinations of versions are approved and supported):
SAP Business One 9.3 PL14
SAP Business One 9.3 PL14, version for SAP HANA
SAP Business One 10.0 FP2502 HF1
SAP Business One 10.0 FP2502 HF1, version for SAP HANA
SAP Business One 10.0 SP2505
SAP Business One 10.0 SP2505, version for SAP HANA
SAP Business One 10.0 SP2505 HF1
SAP Business One 10.0 SP2505 HF1, version for SAP HANA
SAP Business One 10.0 FP2508
SAP Business One 10.0 FP2508, version for SAP HANA
Attention: After installation, the Intercompany menu entries are not directly visible. The menu entries are only displayed after the solution/landscape is deployed and Walldorf licenses are allocated to the users.
Additional important Notes on Version 55:
1. Fixes from SAP Note 2969518 are required to be implemented before deployment of Intercompany Solution or Integration Hub templates if you are using SAP Business One 9.3 PL14.
Version Content:
This version includes all corrections and enhancements from the previous versions of Intercompany Integration Solution and the Integration hub template, as listed chronologically in the associated info file.
New Feature Enhancements:
Intercompany Solution:
1. SAP Business One Service Layer supports the A/R Invoice to A/P Invoice document exchange
SAP Business One Service Layer is a new generation of extension API for consuming SAP Business One data and services. It builds on core protocols such as HTTP and OData and provides a uniform way to expose full-featured business objects on top of a highly scalable and high-availability Web server.
The Intercompany solution provides service layer support for the A/R Invoice to the A/P Invoice document exchange cycle in version 55.
2. SAP Business One Service Layer supports Invoice Type Allocation in A/P Service Invoice Allocation
SAP Business One Service Layer is a new generation of extension API for consuming SAP Business One data and services. It builds on core protocols such as HTTP and OData and provides a uniform way to expose full-featured business objects on top of a highly scalable and high-availability Web server.
The Intercompany solution provides service layer support for the Invoice Type Allocation in A/P Service Invoice Allocation in version 55.
3. SAP Business One Service Layer supports Invoice Type Allocation in A/R Service Invoice Allocation
SAP Business One Service Layer is a new generation of extension API for consuming SAP Business One data and services. It builds on core protocols such as HTTP and OData and provides a uniform way to expose full-featured business objects on top of a highly scalable and high-availability Web server.
The Intercompany solution provides service layer support for the Invoice Type Allocation in A/R Service Invoice Allocation in version 55.
4. Copy GRPO to AP Invoice enhancement in the document exchange cycle
The Intercompany cycle has been enhanced to offer greater flexibility by allowing the Goods Receipt PO (GRPO) to be copied directly to the A/P Invoice in the receiving company under specific conditions. This is particularly useful when items in the Purchase Order are substituted with alternate items in the Sales Order generated from the sender company's Purchase Order.
In certain scenarios, when a GRPO is created based on a delivery, the customer may change the items in the GRPO before adding the document. As a result, the final GRPO may contain different items than those listed in the original delivery document from the sender. In such a case, the user may need to copy the GRPO to the A/P Invoice.
5. Optimized the license validation process to validate only the first logged-in super user
The periodic license validation process has been significantly improved to ensure higher operational stability, reliability, and a smoother user experience. Previously, when the license update process was initiated, it could potentially impact other super users logged in at the same time, causing disruptions or delays. With the new update, this process has been refined to isolate the license update execution, ensuring that it only affects the initiating super user while leaving other super users unaffected.
6. Support for the replication of the Transaction Code Master
The intercompany solution has been enhanced to support the replication of the Transaction Code Master across multiple companies. This feature ensures that transaction codes created in one company can be seamlessly distributed and reused in other connected companies within the intercompany landscape. By enabling replication, organizations can maintain a consistent set of transaction codes across entities, reducing manual effort, minimizing errors, and ensuring greater accuracy in consolidated financial reporting.
7. Support for replication of transaction code in journal entries and journal vouchers during financial consolidation
The replication of transaction codes in Journal Entries (JEs) and Journal Vouchers (JVs) is a critical functionality to ensure accuracy and transparency in financial consolidation. In certain localizations, transaction codes are widely used for building and filtering financial reports. By enabling the replication of these codes into the consolidation company, organizations can achieve consistent financial reporting across entities, minimize manual intervention, and significantly reduce the risk of discrepancies.
8. The Local Branch company can be selected under the Selection option in Remote Query Execution
The intercompany solution has been enhanced to support the selection of the Local Branch company under the Selection option in Remote Query Execution. This improvement allows users to run queries not only across remote companies but also within their own local branch environment. By including the Local Branch as part of the selection criteria, organizations can streamline their query execution process, gain flexibility in reporting, and ensure better visibility of both local and intercompany data.
9. The Global Data Distribution template feature is enhanced to support the replication of the Chart of Accounts
The enhancement introduces support for replicating the Chart of Accounts (COA) through the Global Data Distribution template. With this update, users can configure the Global Data Distribution template to replicate the Chart of Accounts in specific companies, based on business requirements. This flexibility ensures that organizations have control over where and how the COA is distributed, allowing them to align financial structures with operational needs. This selective replication improves efficiency and reduces unnecessary data duplication.
10. BaseUdfFtr and BaseWgtFtr properties are added to the company template for the UoM Group object
The BaseUdfFtr and BaseWgtFtr properties have been added to the company template for the UoM Group object. These properties, introduced with SAP Business One version 10.0 FP 2508, provide extended support for defining calculation factors within UoM Group configurations. By including them in the template, organizations can standardize and replicate these settings across multiple companies, ensuring greater consistency and accuracy in the unit of measure group definitions.
11. The TaxOffice and TaasEnabled properties of the Business Partner (BP) addresses are added to the Company Template
The TaxOffice and TaasEnabled properties of the Business Partner (BP) addresses have now been added to the Company Template to support replication across companies. By including these properties in the template, the system now enables seamless and accurate replication of these fields during Business Partner replication across companies.
Integration Hub:
1. Support for creating customers using the numbering series in SAP B1 within the WooCommerce connector
The WooCommerce Connector has been enhanced to seamlessly support the creation of Customer Master records in alignment with the numbering series defined in SAP Business One. With this enhancement, any new customer synchronized from WooCommerce to SAP Business One is automatically created using the predefined numbering series, ensuring accuracy, consistency, and standardized customer master data management in SAP Business One.
2. Support for creating customers using the numbering series in SAP B1 within the Magento connector
The Magento Connector has been enhanced to support the creation of customer master data using the numbering series defined in SAP Business One. When new customers are synchronized from Magento to SAP Business One, they are automatically created based on the assigned numbering series in SAP Business One. This ensures consistency, accuracy, and alignment of customer records with the established numbering sequence in SAP Business One.
Bug Fixes:
Intercompany Solution:
1. UDF list not displayed in UDF Data Replication for Projects, Journal Vouchers, and Journal Entries.
2. The well-formed character data error occurs while replicating the Project Code via the Service Layer.
3. User-Defined Field (UDF) information is not being replicated on a few objects via the Service Layer.
4. The list of receiver G/L Accounts is not displayed at the line level in the Service type PO.
5. The consolidated credit limit is also being checked for the cancellation document.
6. The event is unexpectedly recorded in the message log while creating the Draft A/P invoice automatically in the A/R service invoice allocation.
7. The deferred tax invoices are appearing in the Intercompany Vendor Payment screen.
8. Intercompany Add-on Connection Fails in Fresh Database Installation.
9. G/L Allocation Posting Templates are not saved if the branch code is entered after the validation warning.
10. The Goods Return document can be created from the Goods Return Request without accepting and confirming.
11. Incorrect syntax error when creating a draft outgoing payment from the incoming payment
12. ScriptExecutor not yet initialized error may occur while importing JEs during consolidation
13. The control buttons in UDF/UDT Structure Replication do not work once UDFs are loaded
14. Unable to replicate the G/L Accounts to the participating companies via the Service Layer.
15. An incorrect amount is displayed in the Intercompany Centralized Payment when the thousand separator in General Settings is configured as a Space.
16. The Branch Sales Analysis report displays an incorrect Gross Profit Percentage under the Profit/Sales Price calculation.
17. The Branch Sales Analysis report always exports in a detailed format to the CSV file.
18. The custom code placed after the Intercompany code in the SBO_SP_TransactionNotification stored procedure is not executed.
19. While canceling the Service A/R Invoice, the corresponding Draft Service A/P Invoice in the participating company is not getting canceled.
20. The receiver branch code appears in both the sender and receiver systems within the alerts for failed transactions.
21. Unable to replicate the Purchase Order to Sales Order when the Inventory UoM is set to Yes.
22. CFL ID already exists error occurs when selecting a vendor in the Purchase Order.
23. “Adj Trans” checkbox always selected on Journal Entry or Journal Voucher in the consolidation company.
24. Unable to replicate global item if Inventory Counting UoM Code is selected in inventory tab of Item master data.
Integration Hub:
1. Unable to Synchronize Lead Master to SAP Business One in the Dynamics 365 Sales Connector.
2. The conversion failed error occurs while synchronizing the Lead master data to SAP Business One in the Dynamics 365 Sales Connector.
3. Unable to synchronize the Item master from SAP to Dynamics in the Dynamics 365 Sales Connector.
4. The Outgoing Payment for the refund process is not being synced individually from Shopify to SAP Business One.
5. Incoming payment is not synchronized when the Shopify Order is paid using a combination of Credit Card and Gift Card.
6. The A/R Credit Memo document is not being created when canceling a Shopify Cash on Delivery (COD) order.
7. The conversion failed error occurs while initializing the Business Partner in the Dynamics 365 Sales Connector
For more information about the corrections contained in this specific version, see the WDF Notes listed in the References section.
Product
Product or Product Version
B1 INTERCOMPANY INTEGRATION
SAP B1 10.0 FOR SAP HANA
SAP B1 9.3 FOR SAP HANA
SAP BUSINESS ONE 10.0
SAP BUSINESS ONE 9.3
This document refers to :
WDF 2000005 - Unable to upgrade the SAP Intercompany between PL27 and PL34 to Walldorf Intercompany on SAP HANA
WDF 1844555 - Troubleshooting Intercompany Integration Solution for SAP Business One
WDF 2000016 - Optimizing Intercompany Solution Performance
This document is referenced by:
WDF 2550002 - SAP Business One Service Layer supports A/R Invoice to A/P Invoice document exchange
WDF 2550003 - SAP Business One Service Layer supports for Invoice Type Allocation in A/P Service Invoice Allocation
WDF 2550004 - SAP Business One Service Layer supports for Invoice Type Allocation in A/R Service Invoice Allocation
WDF 2550005 - Optimized the license validation process to validate only the first logged-in super user
WDF 2550006 - Support for the replication of Transaction Code Master
WDF 2550007 - The Local Branch company can be selected under the Selection option in Remote Query Execution
WDF 2550008 - The Global Data Distribution template feature is enhanced to support the replication of the Chart of Accounts
WDF 2550009 - Support for creating customers using the numbering series in SAP B1 within the WooCommerce connector
WDF 2550010 - Support for creating customers using the numbering series in SAP B1 within the Magento connector
WDF 2550011 - Support for replication of transaction code in journal entry and journal vouchers during financial consolidation
WDF 2550012 - Unable to Synchronize Lead Master to SAP Business One in Dynamics 365 Sales Connector
WDF 2550013 - The conversion failed error occurs while synchronizing the Lead master data to SAP Business One in the Dynamics 365 Sales Connector
WDF 2550014 - UDF list not displayed in UDF Data Replication for Projects, Journal Vouchers, and Journal Entries
WDF 2550015 - The well-formed character data error occurs while replicating the Project Code via the Service Layer
WDF 2550016 - BaseUdfFtr and BaseWgtFtr properties are added to the company template for the UoM Group object
WDF 2550017 – Master replicated to all branches instead of targeted branches in Global Data Distribution via Service Layer WDF 2550018 - Unable to synchronize the Item master from SAP to Dynamics in the Dynamics 365 Sales Connector
WDF 2550019 - User-Defined Field (UDF) information is not being replicated on a few objects via the Service Layer
WDF 2550020 - The list of receiver G/L Accounts is not displayed at the line level in the Service type PO
WDF 2550021 - The consolidated credit limit is also being checked for the cancellation document
WDF 2550022 - The Outgoing Payment for the refund process is not being synced individually from Shopify to SAP Business One
WDF 2550023 - The event is unexpectedly recorded in the message log while creating the Draft A/P invoice automatically in the A/R service invoice allocation
WDF 2550024 – Incoming Payment not synchronized when Shopify order is paid using a combination of credit card and gift card
WDF 2550025 - The A/R Credit Memo document is not being created when cancelling a Shopify Cash on Delivery (COD) order
WDF 2550026 - The deferred tax invoices are appearing in the Intercompany Vendor Payment screen
WDF 2550027 – Intercompany add-on connection fails in fresh database installation
WDF 2550028 – G/L Allocation Posting Templates not saved if branch code entered after validation warning
WDF 2550029 - Goods Return document can be created from Goods Return Request without accepting and confirming
WDF 2550030 - Incorrect syntax error when creating a draft outgoing payment from the incoming payment
WDF 2550031 - ScriptExecutor not yet initialized error may occur while importing JEs during consolidation WDF 2550032 - Conversion failed error occurs while initializing Business Partner in Dynamics 365 Sales Connector WDF 2550033 - Control buttons in UDF/UDT Structure Replication do not work once UDFs are loaded
WDF 2550034 - CFL ID already exists error occurs when selecting a vendor in the Purchase Order
WDF 2550035 - “Adj Trans” checkbox always selected on Journal Entry or Journal Voucher in the consolidation company
WDF 2550036 - PATCH or PATCH2 HTTP method issue in SAP Business One Integration Framework
WDF 2540037 - Unable to replicate the G/L Accounts to the participating companies via the Service Layer
WDF 2540038 – Copy GRPO to AP Invoice enhancement in document exchange cycle
WDF 2540039 - An incorrect amount is displayed in the Intercompany Centralized Payment when the thousand separator in General Settings is configured as a Space
WDF 2540040 - Unable to replicate global item if Inventory Counting UoM Code is selected in inventory tab of Item master data WDF 2530034 - The Branch Sales Analysis report displays an incorrect Gross Profit Percentage under the Profit/Sales Price calculation
WDF 2530035 - The Branch Sales Analysis report always exports in a detailed format to the CSV file
WDF 2530036 - The custom code placed after the Intercompany code in the SBO_SP_TransactionNotification stored procedure is not executed
WDF 2530037 - While canceling the Service A/R Invoice, the corresponding Draft Service A/P Invoice in the participating company is not getting canceled
WDF 2520035 - The receiver branch code appears in both the sender and receiver systems within the alerts for failed transactions
WDF 2510021 - The TaxOffice and TaasEnabled properties of the Business Partner (BP) addresses are added to the Company Template
WDF 2510022 - Unable to replicate the Purchase Order to Sales Order when the Inventory UoM is set to Yes