6.9.1.0 Integration for SAP Documentation
Release summary
The latest release for Global Next Integration 6.9.1.0 comprises of a new ERP Reconciliation report that is compatible with ONESOURCE Indirect tax Enterprise Cloud version. This report extracts tax transactions from SAP in a specific format that's easily ingested into the Integration layer via APls. The result is a detailed report in NGRA, streamlining the reconciliation process by matching SAP transactions with those in the ONESOURCE Indirect Tax Determination Audit database.This release also includes various bug fixes and minor enhancements.For SAP ECC users, this release version is compatible with
SAP ECC EHP6 and above.
Global Next release 6.9.1.0 has also been validated and tested for compatibility with the latestS/4HANA 2023 FPS03.
New ERP Reconciliation Report
For ONESOURCE Indirect Tax Enterprise Cloud customers, this release brings a new tool: ERP Reconciliation report. It simplifies the reconciliation process by extracting tax transactions from SAP, formatting them for seamless integration with the ERP Recon Integration layer via API calls, and generating a matching report in NGRA. This report bridges the gap between SAP transactions and the entries in ONESOURCE Indirect Tax Determination Audit database, making it easier to ensure accuracy and consistency.
FIORI APPS COMPATIBILITY
The Global Next 6.9.1.0 version is compatible with the following applications:
- Apps with the type SAPGUI for HTML that support external tax systems.
- Transactional apps supporting external tax systems.
The following Fiori apps have been supported with version Global Next 6.9.to.
Fiori App | Area | |||
Manage Purchase Orders - F0842 | P2P | |||
Post Goods Receipt for Purchasing Document - F0843 | P2P | |||
Manage Supplier Invoices - F0859 | P2P | |||
Manage Service Entry Sheets - Lean Services - F2027 | P2P | |||
Manage Sales Orders - F1873 | SD | |||
Create Billing Documents - F0798 | SD | |||
Manage Sales Contracts - F1851 | SD | |||
Create Incoming Invoice - FB60 | Fl - | Incoming invoice | ||
Post Outgoing Payments - F1612 | Fl - | Incoming invoice | ||
Clear Outgoing Payments - F1367 | Fl - | Incoming invoice | ||
Manage Supplier Down Payment Requests - F1688 | Fl - | Incoming invoice | ||
Assign Open Items - F2626 | Fl - | Outgoing invoice | ||
Create Outgoing Invoice - FB70 | Fl - | Outgoing invoice | ||
Post Incoming Payments - F1345 | Fl - | Outgoing invoice | ||
Manage Customer Requests - F1689 | Down | Payment | Fl - | Outgoing invoice |
Post General Journal Entries - F0718 | Fl - | Journal entries | ||
Clear G/L Accounts - F1579 | Fl - | Journal entries | ||
Post Tax Payables - F1597 ( FB41) | Fl - | Journal entries | ||
Create Single Payment - F0743 | Fl - | Journal entries | ||
Domestic Scenario for DT | Deferred Tax | |||
Cross-Border Scenario (DT + RC) | Deferred Tax | |||
Technical changes
PO Self-Assessment feature not working with Global Next offset configuration.
Issue:
Due to a bug, the offset configuration in Global Next, that facilitates Self-assessment determination in the Purchase Order process was not working as expected.Resolution:
The issue has been resolved by fixing the code in the UNBOARD_TRAIN of class/IDT/JOURNEY_SELF_ASSESSMENT.An ABAP dump occurs in the function module FI_TAX_DISTRIBUTE_AMOUNT when a user overrides the zero rated tax determined by ONESOURCE Indirect Tax Determination tool ( IDT ) with a non-zero tax amount in FB60.
Issue
: SAP introduced additional code via SAP NOTE: 3016863, which causes the manual tax override process to fail when IDT returns a zero tax amount in FI process.Resolution
: In the current release, created a new journey class,/IDT/JOURNEY_FI_TAX_DISTRIBUTE, for updating the Tax Code in /IDT/AUTO_JOURNEYS (Automatically Processed Journeys).Display Purchase Order (T-Code ME23N), the Taxes section on the line-item’s invoice tab does not display tax details.
Issue
: When a PO is created, saved and then displayed via transaction ME23N, the previously calculated taxes are not displayed on the tax screen on the line-item invoice tab.Resolution:
A code fix has been made to obtain the calculated values from the KONV structure for each respective line item in method COLLECT_DATA_AND_CALL_DETERMIN of class/IDT/ROUTE_NON_GROUP_DOC_PUR.Balance issue during Rebate Sales Settlement process using T-Code WB2R_SC on S/4HANA2023.
Issue:
The Rebate Sales Settlement document displays the error "Accounting Interface: Balance in Transaction Currency" during automatic settlement in S/4HANA 2023.Resolution:
Code changes made in include /IDT/WLF_ACC_CHANGE_BEFORE_SUM to clear the local structures.Reference Document Number in LIV is not being populated in the tax request.
Issue:
The custom field mapping for the LIV route, specifically for the XBLNR field, is not retrieving the value fromRBKP-XBLNR.Resolution:
A code change was made in the SET_PRICING_DATA method of class/IDT/JOURNEY_HEADER_REQUEST to resolve this issue.Tax data entries are updated incorrectly in /IDT/D_TAX_DATA table for Customer Downpayment Settlement process during Cancellation.
Issue
: An error in tax amount calculation occurred during the cancellation of the Customer Down Payment Settlement Invoice, leading to incorrect table updates and erroneous postings in the document.Resolution
: The method ARRANGE_FI_TAX_SOLUTION in class /IDT/TRAFFIC_CONTROL was updated to read the relevant settlement document line, ensuring accurate amounts are used for calculation. Performance issue noticed while archiving AUDIT data through ILM
Issue:
Noticed a code improvement was needed in archiving /IDT/D_AUDIT_STA table entries with SAP Information Lifecycle Management (ILM).Resolution:
Code change made in report /IDT/AUDIT_STA_REC_WRI. Refined and split the select statement to read the data from table /IDT/D_AUDIT_STA.Bug notes
This section lists known bugs in Current release 6.9.1.0, workarounds (if applicable) and limitations within the overall Global Next integration.
Issue:
During the Customer Down Payment settlement process, the address elements are not retrieved from the sales order specified in the line item when posting incoming down payments.Root Cause:
When posting Customer Down Payment documents during the downpaymentsettlement process, where a sales order is specified at the line item level, the system retrieves addresses from the down payment document instead of from the associated sales orderinformation.Resolution:
If you encounter this issue, please contact Customer Support or the Engineering team to obtain the necessary hotfix.Issue
: Tax calculation does not give accurate results In a Service Purchase Order with multiple account assignment.Reason
: The Global Next integration (GN) has a limitation: Service PO line numbers must be 99 or less.Exceeding this number will make the GN mix up taxes between different line items on your service purchase order due to a bug in the sub-line item(Multiple account assignment lines) numbercreation logic.Workaround
: If the line item number exceeds more than 99 then split into multiple Purchase Orders. So that the Taxes calculated would be accurate.Download instructions
To download and install this release:
- You'll need to retrieve theONESOURCEIDTIntegrationSAP_6910.zipfile from the Customer Center.
- Open the ONESOURCE Indirect Tax Customer Center.
- Log on using the username and password provided by Technical Support.
- Find theIntegration for SAP (Enhanced Global)in the available Products list and verify that Installed Version is set toNone.
- SelectDownloadforIntegration for SAP (Enhanced Global).
- Save the file.
- Unzip the file.
- Download the User, Install and Programmers, and Configuration Guides from the Support Network at Customer Support and follow the steps per Install guide.
Installing integration
Importing transport objects
To set up ONESOURCE Indirect Tax Integration for SAP, you'll need to import the transports provided by Thomson Reuters into your development system. All the objects are located in the Thomson Reuters Indirect Tax namespace
/IDT/
. It's important to note that these transports don't alter any customer-owned objects.All code and objects delivered by Thomson Reuters are in the
/IDT/
namespace. The transports provided won’t directly update SAP-owned objects, user exits, or similar elements. After successfully importing the transports into your SAP system, you'll need to perform additional manual steps to add coding blocks into SAP objects to call the Thomson Reuters tax interface code.With this release, the India transports are included with the other transports and are no longer provided separately.
This installation document assumes a fresh installation of the integration. If you received a pre-General Release version, please contact Thomson Reuters Customer Support for assistance.
If you're upgrading your system from a prior
6.X.X.X Integration version
, you need to apply an additional upgrade transport to remove objects no longer used in the new release. It's important to complete this upgrade transport first to prevent errors in the code transport.Import the provided transports in the following order:
TRANSPORT | CONTENT |
|---|---|
STGK901126 | Thomson Reuters ONESOURCE IDT Integration 6.9.1.0 – Upgrade |
STGK901102 | Thomson Reuters ONESOURCE IDT Integration 6.9.1.0 – Code |
STGK901103 | Thomson Reuters ONESOURCE IDT Integration 6.9.1.0 - Config |
STGK901104 | Thomson Reuters ONESOURCE IDT Integration 6.9.1.0 – BTE |
STGK901105 | Thomson Reuters ONESOURCE IDT Integration 6.9.1.0 - Roles |
STGK901106 | Thomson Reuters ONESOURCE IDT Integration 6.9.1.0 - CDS Tax
note
This transport is for those whose landscape supports the use of the CDS view for the /IDT/D_TAX_DATA table. |
When generating and importing ABAP objects, it may take some time to complete. It's important to ensure that each transport is successfully imported before moving on to the next one in the list.
For a new installation, import the transports in the specified order. You don't need the upgrade transports for a new installation.
TRANSPORT | CONTENT |
|---|---|
STGK 901102 | Thomson Reuters ONESOURCE IDT Integration 6.9.1.0 – Code |
STGK 901103 | Thomson Reuters ONESOURCE IDT Integration 6.9.1.0 - Config |
STGK 901104 | Thomson Reuters ONESOURCE IDT Integration 6.9.1.0 – BTE |
STGK 901105 | Thomson Reuters ONESOURCE IDT Integration 6.9.1.0 - Roles |
STGK 901106 | Thomson Reuters ONESOURCE IDT Integration 6.9.1.0 - CDS Tax
note
This transport is for those whose landscape supports the use of the CDS view for the /IDT/D_TAX_DATA table. |
Refer to the "
Clearing of Dynamically Generated Programs
" section in the Install guide, as you need to run this program during your upgrade. Check the KB article number
000082741
for information on a possible error in transport loads if you use custom code with reference to /IDT/TRAFFIC_CONTROL
. If you are using an earlier version of 6.x, remove the include in user-exit EXIT_SAPLV60B_008
.In the previous release (6.4.5.0), we removed the included program
/IDT/CE_BILLING_DOC_SAVE_EVENT
from the product. You may encounter an error when loading the transports if you haven't removed this include. If you haven't yet removed the include from the user exit, please do so now.