ONESOURCE INDIRECT TAX

INTEGRATION FOR SAP

PRODUCT UPDATES
VERSION 6.2.0.1
This document provides the following information
Upgrade Note
Technical Changes
Bug Notes
Download Instructions
Previous Releases
For additional information, see the following on the Software Support Network:
ONESOURCE Indirect Tax Integration for SAP Documentation
ONESOURCE Indirect Tax Platform Support Guide
ONESOURCE Indirect Tax Global Software Suite End of Product Service Notice Update
Past Product Updates

VERSION 6.2.0.1
UPGRADE NOTE
Customers who have already installed version 6.2.0.0 will ONLY need to apply transport DO3K902546. No configuration
changes or other setup steps will be needed. The 6.2.0.1 patch only contains code changes.

TECHNICAL CHANGES
TAX CODE IN ITEM CONDITIONS IS NOT UPDATING IN PO'S FOR US SCENARIOS
Issue:

Tax code on the item conditions for US scenario is not correctly updating the tax code from I1 to V1, or U1 to C1.

Solution:

Correction was made to the unboard train method within the standard response journey to correct this.

ERROR MESSAGE RECEIVED WHEN SUMMARIZATION ON FOR FB60 AND FB65 REDUCED RATE
TAX, DIFFERENT TAX CODES
Issue:

If summarization was turned on for G/L account only and multiple tax codes were tied to the same G/L account
then an error occurred that was caused by the additional tax code missing a representation in the summarization
logic.

Solution:

Logic was changed to correct for this error with overall adjustments to the summarization logic.

BRACKET TAXES AND FREIGHT ENTERED TOGETHER

Issue:

Bracket taxes and Freight entered together gives error VH806 Errors while transferring conditions: duplicate
found.

Solution:

Logic fix to the tax condition sorting has fixed this issue.

Issue:

Bracket taxes and TN extended taxes seeing issues in MIRO where it is posting additional 'income difference'
lines in the accounting document when there are special taxes.

Solution:

Resolved by fixing a bug in the LIV tax processes and by fixing a bug in the PO item tax process.

SUMMARIZATION ERROR ON DIFFERENT TAX CODES

Issue:

Error message received when summarization is turned on for FB60 and FB65 using different tax codes, or when
there are positive and negative (e.g. acquisition tax) on a document that has the same base amounts for each
line.

Solution:

Adjustment to the summarization logic has been applied in order to keep lines with the same positive or negative
amount for tax summarized separately rather than netted together.

FI PROCESS FOR LIV CREDIT MEMO NOT WORKING AS EXPECTED

Issue:

LIV credit memo process was being used on LIV invoice causing amount to show in calculation as negative on an
invoice.

Solution:

Amounts are now showing as positive when invoice process and as negative in credit memo process.

US U1 TAX CODE SHOWS TAXES LISTED IN WRONG ORDER IN ITEM CONDITIONS FOR LINE
Issue:

The various condition lines on single line items are not in the correct sort order and are showing the higher state
level on a US scenario later in the list below county, city, and district level authorities.

Solution:

The sort order of the authority lines was fixed.

IDT TAX SUMMARIZATION CONFIGURATION TABLE - UPDATE VIEW /IDT/V_TAX_SUM_C

Issue:

The active button needed to be moved in the order of columns so that it is next to the sort order column as is per
our standard setup.

Solution:

The column order on the table was fixed.

ADD BADI TO ALLOW DOCUMENT-SPECIFIC DECISION TO SUMMARIZE TAX DATA LINES

Issue:

More flexibility was needed for users to do tax line summarization on BSET and BSEG table tax lines based on
customer designed features like number of lines, etc.

Solution:

BAdI /IDT/BADI_ADJUST_TAX_SUMMATION was added to the program and a new line added to the summation
table to allow users to customize with ABAP code further summarization logic beyond the use of summing based
on G/L account, Tax Code, Account key, and UUID. User can customize additional logic using ABAP for various
other additional conditions such as providing summarization based on number of lines, document type, etc.
Further instructions for this have been added to the Installation and Programmers Guide and the Configuration
Guide.

2014 Thomson Reuters/ONESOURCE. All rights reserved.

Page 2 of 15

MIX OF POSITIVE AND NEGATIVE LINES IN MIRO

Issue:

When there is mix of positive and negative lines in MIRO, issues appear including incorrect address assignment
and short dump messages.

Solution:

Logic has been fixed to allow positive and negative lines on same MIRO LIV document including correct address
assignment.

FEE FUNCTIONALITY FOR US NVV PROCESS (FB60 AND LIV)

Issue:

Issue with posting FB60 documents using U1 tax codes with a fee. Receiving message "Posting is only possible
with a zero balance; correct document" Message no. F5060. There is also a related issue when posting MIRO for
PO's with fees using U1 tax code.

Solution:

Logic has been fixed and error is not occurring now for this scenario.

BUG NOTES
NOT YET SUPPORTED BUSINESS PROCESSES
Issue:

Down Payments, Consignment/Pipeline Orders are not yet fully productized and workable.

Workaround:

Consult with Thomson Reuters Product Management via a support ticket about timelines of features not yet
fully supported. We will work closely with you to determine best solutions.

UPGRADE INSTALLATIONS
Issue:

Upgrading from an existing 5.x Integration to the newest version hasnt been fully documented and tested.

Workaround:

Engage with Thomson Reuters Professional Services to assist in an upgrade plan and implementation.

GOODS MOVEMENT PROCESS

Issue:

The Goods Movement solution has not yet been ported to version 6.

Workaround:

We are planning to provide a solution in this area as soon as possible. Consult with Product Management
timeline.

HEADER CONDITIONS
Issue:

On a cancellation document for a Plants Abroad invoice the header conditions arent properly displayed.

Workaround:

There is no implication to the G/L posting, this issue is cosmetic only.

SUMMATION IN BSEG AND BSET OF TAX DATA

Issue:

When summarization is turned off, the tax base amount for exempt tax lines are overstated.

Workaround:

This is a known issue with how SAP, specifically the ABAP layer, does its summarization. Given that this is
only occurring on exempt items there is no workaround.

2014 Thomson Reuters/ONESOURCE. All rights reserved.

Page 3 of 15

ISSUE WITH IDT CODE HOOK TO REPLACE TAX CODE ON BSEG

Issue:

A user should be able to post a MIRO document with combination of PO line and a non-tax relevant credit GL
line.

Workaround:

If a non-tax line is entered as a credit the user should not leave the tax code blank but instead assign an
exempt tax code to the line. If the field is left blank the system will sometimes default it to the tax code from
the prior line in the calculation.

DOWNLOAD INSTRUCTIONS
To download and install this release:
1. Retrieve the ONESOURCEIDTIntegrationSAP_6201.zip file from the Customer Center. To do so:

Open the Customer Center at http://customercenter.sabrix.com/sabrixcc

Log on using the user name and password provided by Technical Support.

Find Integration for SAP (Enhanced Global) in the Available Products list and verify that Installed Version
is set to None.

Click Download for Integration for SAP (Enhanced Global).

Save the file.

2. Unzip the ONESOURCEIDTIntegrationSAP_6201.zip file.

3. Download the User, Install and Programmers, and Configuration Guides from the Support Network at
https://www.onesourceidtsupport.com
Upgrade Note:
Customers who have already installed version 6.2.0.0 will ONLY need to apply transport DO3K902546. No configuration
changes or other setup steps will be needed. The 6.2.0.1 release only contains code changes.

PREVIOUS RELEASES
6.2.0.0

VERSION 6.2.0.0
UPDATE SUMMARY
This release of the ONESOURCE Indirect Tax Integration for SAP is a product update to the new Global Next version 6
interface. Version 6 is designed to significantly improve the user experience and dynamically expand current and future
system capabilities for indirect tax calculations, reporting, and data mapping. The new platform moves away from the use of
the SAP Standard Tax Interface and SAP JCo adapter to new functionality based on ABAP coding directly within
ONESOURCE Indirect Taxs SAP registered namespace. Users are no longer limited by jurisdiction code based calculations
and design originally written for the US and Canada sales tax structure. This provides far greater flexibility to meet challenging
and ever changing global tax requirements and simplifies US and Canadian tax.
The new interface is designed with the global customer in mind and closely to SAPs structure and logic for global VAT
processing. Users can take advantage of many standard SAP functions that are only made available with a non-jurisdiction
based configuration. As future SAP features and functions become available to customers, the new design will likely avoid
costly modifications to Integration programs.
Tax Code usage within the new interface provides static assignment of tax codes based on downstream reporting and
compliance needs without the requirement of assigning a tax rate, eliminating setup of different tax codes when tax rates

2014 Thomson Reuters/ONESOURCE. All rights reserved.

Page 4 of 15

change. This new logic allows the use of SAP standard reports and functions and avoids running out of possible tax code
assignments. Support of a large number of global taxing authorities and historical rate changes are not an issue.
Users can now take advantage of standard VAT reports, plants abroad configuration, and many other standard SAP features
that were a challenge or impossible with the prior jurisdiction code based interface. Exciting improvements have also been
made to remove limitations on the summarization of taxing authorities, number of fields mapped to Determination requests
and responses, and other key elements required for meeting current and future global tax challenges.
Below is a list of some of the many new features and functions that are now added to version 6 with this new update release
6.2.0.0. Throughout the installation, configuration, and user guides, we will discuss in more detail each of the new features
listed and further explain what additional opportunities are now available to the system user.
Some of the key new additions within this 6.2.0.0 release include:

FUNCTIONAL CHANGES
ONESOURCE MENU REORGANIZED
Issue:

New tables and transactions were added to the menu requiring reorganization.

Solution:

ONESOURCE menu has been updated and several transactions moved to improve flow and logical processing.
The updated menu is shown in the User Guide.

LOG CONFIGURATION TABLE CHANGE

Issue:

Log configuration table needed to be updated.

Solution:

The log configuration table has been changed and split into two views. A standard view addresses the default
setting for all areas using Error log status. The new Customer view allows user to override the standard setting
and add configurations for specific users and transactions.

AUDIT DATABASE REPORT

Issue:

Adjustments and new codes were needed on the Audit Database report.

Solution:

Additional document status codes have been added to the Audit Database Report and improvements made to the
selection options and processing. New documentation updates are now provided in the User Guide.

Issue:

Audit Database Report did not include the date of the transaction in the display.

Solution:

Date of the transaction has now been added to the audit database report and update logic.

CASH DISCOUNTS LOGIC

Issue:

A new table and updates to cash discounts logic were needed.

Solution:

Cash Discount recognized at time of payment has been improved in this release with new logic, journey, route,
and configuration table additions. /IDT/D_CASH_DISC table has been added within the Configuration Tables
section of the new user menu in order for the customer to map the tax codes in SAP to the required tax code
designations in Determination. Additional Tax Code Qualifier entries will also need to be added in Determination
in order to correctly map the VAT adjustment on the cash discount back to the correct tax code and account key.
New process and configuration requirements are noted in the Configuration Guide Special SAP Functions section
on cash discounts.

2014 Thomson Reuters/ONESOURCE. All rights reserved.

Page 5 of 15

RECONCILIATION EXTRACT REPORT

Issue:

Reconciliation Extract report needed to be updated to work with 6.X Integration.

Solution:

Reconciliation extract report was ported to 6.x environment and code was adjusted for fields that were moved to
the new IDT/Tax_Data table. A menu option and transaction code was assigned. A new section was added to
the User Guide giving instruction on use of the new extract function.

DEFERRED TAX
Issue:

Deferred Tax process needed to be added.

Solution:

Deferred Tax process was tested and new journey and route established to work with SAP transfer program f.38
(RFUMSV25). New documentation was added to User Guide and Configuration Guide to outline all set up
requirements.

LOG ARCHIVE AND DELETE FUNCTION

Issue:

User ability to delete or archive xml log data was needed.

Solution:

New feature added for deletion or archival to zip file for XML log information in order to give user a means to
maintain the size of the XML log table within SAP. The User Guide outlines this new function. An additional
configuration step is shown in the Configuration Guide.

MENU ADDITIONS FOR BETTER TABLE VISIBILITY

Issue:

In the 6.1.0.1 release of Integration the following tables are available as part of the product but were not included
in the user menu: /IDT/D_FI_CONTRL, /IDT/D_NEG_TTYP, /IDT/D_PLNTS_ABD.

Solution:

/IDT/D_NEG_TTYP and /IDT/D_FI_CONTROL tables are now split into a standard view and a customer
configuration view. The IDT/D_PLNTS_ABD table is available via a single customer view within the Configuration
Tables section of the new user menu.

USE TAX FOR FOREIGN VENDOR IN US COMPANY CODE

Issue:

US logic table was not designed to work with foreign vendor use tax accrual logic. Table needed modifications to
include foreign vendors.

Solution:

New columns were added for ship from country group and ship to country group, in order to provide needed logic
for configuring foreign countries as possible vendors for self-accrued use tax in US Sales Tax logic.

TAX CODE RELEVANCY LOGIC

Issue:

Customer desired to have ability to prevent a specific tax code from making a call to Determination for exempt
taxes.

Solution:

A new tax relevancy table was created so that a user could call out certain tax codes by country group or
company code that they do not want to include in a call to and calculation within Determination.

TAX REGISTRATION USING BUSINESS PLACE

Issue:

Certain countries outside of the EU need to get VAT registration numbers and other data from Business Place
configurations in SAP.

Solution:

Functionality was added to utilize Tax 1 and Tax 2 fields from the J_1BBRANCH table within the Flexible Field
Mapper for the following journeys:

2014 Thomson Reuters/ONESOURCE. All rights reserved.

Page 6 of 15

/IDT/JOURNEY_HEADER_REQUEST
/IDT/JOURNEY_ITEM_REQUEST
/IDT/JOURNEY_NG_ITEM_REQUEST
Tax 1 and Tax 2 fields from the business place table can be used in the field mapper, just like Customer or
Vendor Tax 1 - 5 fields are mapped.

CORRECTION TO ADDRESS SOURCES TABLE

Issue:

The standard view of the Address Source table contained optional address sources that required additional
customized ABAP code additions by the customer in order to activate them specifically for their field
requirements. (Each customer application could be different depending on fields used).

Solution:

In order to avoid confusion the optional address sources were removed from the list including: WBS Element,
Internal Order, Network Element, Profit Center, Sales Organization, and Storage Location. Users have the ability
to utilize these optional address sources by using the customer view of the table in System Enhancements menu
option, and insert the required customer specific ABAP code to activate them according to their field requirement
needs.

MIX OF TAX CODES ON SAME LINE

Issue:

User may encounter error FF-753 if multiple tax codes are assigned on the same line item. OSS note 495737
provides a resolution to this issue but the user may not elect to change the error message as outlined in the note.

Solution:

An alternate method of tax code and account key assignment may be needed. A knowledge base article with
optional TCQ templates is available on the customer support web site and the Configuration Guide notes the two
alternative assignment methods.

SUPPORT OF CUSTOM ADDRESS DURING MIRO INVOICE ENTRY ON G/L TAB AND PO REF. TAB
Issue:

Some users may need the ability to change the ship to address at the line item level during MIRO, FB60, FB65,
FB70, and FB75 transactions for the PO reference line item or related manual G/L item entry.

Solution:

A function was added for an address number field with look up capability that can pull up address from ADRC
table in SAP and use it to replace ship to address at time of invoice line item entry. User can add this to the PO
reference tab as desired.

SETTING I1 DRIVER TAX CODE AS DEFAULT

Issue:

A user may desire ability to set I1 driver tax code as the default in calculation schema for PO.

Solution:

Documentation was added to the Appendix 1 in Configuration Guide on setting defaults.

CURRENCY ON AUDIT POSTING

Issue:

Local currency amounts going to audit were different from amounts shown on the general ledger.

Solution:

Amounts in local currency were taken from the G/L entry in order to populate the amount for the audit response.

AUDIT REPROCESS REPORT

Issue:

Audit reprocess reports incorrectly showed documents as status "U" (untried) that have not yet been posted to FI
general ledger balances.

Solution:

We added new code so that the not-yet-posted documents are marked as "N" - Not posted to G/L.

2014 Thomson Reuters/ONESOURCE. All rights reserved.

Page 7 of 15

COMPANY ROLE LOGIC

Issue:

FI documents that do not engage a customer or vendor number in the transaction needed a way to identify a
<COMPANY ROLE> in Determination.

Solution:

FI documents without a customer or vendor now look at the tax code used on the first line. If tax code field T007AMWART is set to V then company role is set to Buyer. If tax code field T007A-MWART is set to A then the
company role is set to Seller.

FIELD MAPPING SIMPLE EXPRESSION LOGIC

Issue:

An added logic function was needed for field mapping simple expressions so as to populate a field if the initial
value of blank is or is not present.

Solution:

We added "IS_INITIAL" as a special function for simple expressions in field mapping.

USER SPECIFIC PROXY AVAILABILITY

Issue:

A customer may wish to have a user test a proxy configuration setting separate from other users on the system.

Solution:

A new specific user column is added to the proxy configuration table to enable separate set up of the proxy
configuration by user.

U.S. U1 TAX CODE SUMMARIZATION ISSUE

Issue:

Use of US self-accrual of consumer use tax and NVV account key on multiple line items was not allocating the
amounts to the correct line items. Instead it divided the tax amounts evenly between the lines.

Solution:

Logic was corrected for NVV account key lines so that they applied the amount to the correct expense/revenue
account and line number on a line by line basis.

CONFIGURATION TABLE CONSISTENCY

Issue:

There were different meanings to sort orders and functions within our configuration tables.

Solution:

Changes were made to configuration tables in order to give a more consistent style, function, and view where
applicable across the various tables.

ATTRIBUTE 41 TO 50 RESTRICTION
Issue:

Attributes 41- 50 are reserved for use by ONESOURCE however they were accessible via the customer view of
the field mapping table. No error message was sent when a customer tried to map to these reserved attributes.

Solution:

Logic was added to restrict use of these reserved attributes. If a user tries to map to these reserved attributes a
special error message will appear at the beginning of the XML log data. Due to the current structure an error will
not display at time of saving the field mapping. Additional structure may be added in a future release in order to
improve field drop down lists and mapping error messages within the tables.

DELIVERY ADDRESS SOURCE

Issue:

Delivery address was not available via the address sources table.

Solution:

Delivery address was added to the address sources standard view of the table.

NOTE:

For customers who have enabled mappings for the DELIVERY_ADDRESS in the customer address mapping
table (/n/IDT/ADDRESS_MAPPING) all entries will need to be replaced with an entry for DELIVERY ADDRESS
instead." (We removed the underscore key from the name.)

2014 Thomson Reuters/ONESOURCE. All rights reserved.

Page 8 of 15

TRIANGULATION
Issue:

Improvement to Triangulation scenario support was needed.

Solution:

New logic is in place that utilizes triangulation indicator on the sales order. Additional notes have been added to
the Special SAP Functions of the Configuration Guide.

TAX CALL ON FBD1, FB1S, FB1K, FBD5, FB05

Issue:

The following transactions were not making a call to Determination and needed to be adjusted: FBD1, FB1S,
FB1K, FBD5, and FB05.

Solution:

Transactions were adjusted to make a tax call to Determination.

GROSS AMOUNT CALCULATION

Issue:

Using FB00 transaction to set the tax calculation to use the gross amount calculation rather than the check mark
for Net amount causes an incorrect calculation based on Gross amount.

Solution:

The logic used for the calculation of tax based on input of the gross amount has been corrected.

RECURRING ENTRY DOCUMENT POSTING TO AUDIT DATABASE

Issue:

Initial FBD1 recurring entry documents were posting to audit and should not as they are not yet posted to G/L
account balances and are in a pending status.

Solution:

Logic was added to avoid passing to audit transactions like recurring docs and parked documents that are not
officially posted to G/L balances yet. When a final document is posted off of the recurring, parked, or sample
document, then a final is audited call will be activated.

Note:

This change may result is some reconciling items when using the reconciliation download extract and
reconciliation report for your first period following this change. This would be due to the prior process where the
incomplete pending document was sent to audit. The entry will show as in audit per the reconciliation report but
not in the new version of the G/L data extracted from the G/L for this comparison report. The reconciling items
will have a non-blank transaction status code in the BSEG table.

SUMMARIZATION OF TAX LINES IN BSEG AND BSET TABLES

Issue:

Due to the SAP limit of 1000 lines on a document going to BSET and BSEG users need the ability to summarize
like tax lines to decrease the size of the document.

Solution:

A new table for Summarization has been added to allow user to summarize the tax data lines by G/L account, Tax
Code, Account Key, and UUID taxing authority as desired.

US VENDOR CHARGED TAX WITHOUT A CALL TO DETERMINATION

Issue:

Users needed ability to accept US vendor charged sales tax per invoice rather than make a call to have it
calculated in Determination.

Solution:

Functionality was added to allow user to enter the tax amount on the vendor invoice and not make a call to
Determination. This can only be used with vendor charged tax in US sales tax scenario as no call is made and
nothing is recorded in audit of the /IDT/D_Tax_Data table. See User Guide section by this title for further
information.

2014 Thomson Reuters/ONESOURCE. All rights reserved.

Page 9 of 15

TECHNICAL CHANGES
AUDIT DATABASE REPORT CHANGE
Issue:

A change was needed regarding Audit Database report and use of user exit.

Solution:

A new user exit was applied using OSS Note 449861. Customers on an earlier version of 6.x will need to remove
the include statement in user-exit EXIT_SAPLV60B_008. Install guide has been updated with additional notes for
this change.

LOCAL CURRENCY CONVERSION FOR FREIGHT AMOUNT

Issue:

Freight amounts were not being converted to local currency like the gross amount at time of audit update.

Solution:

A change was made to also convert the freight amounts to local currency at time of audit.

STANDARD S.O. WITH NEGATIVE AMOUNTS DUE TO DISCOUNTS POST POSITIVE TO G/L
Issue:

Discounts greater than 100% caused the net taxable amount to show appropriately as negative and was not
captured correctly in the tax calculation to the G/L and to the audit database.

Solution:

Logic was corrected so that this is now correctly reflected in the tax G/L posting and in audit.

REMOVED /IDT/JOURNEY_NG_NDOC_ITEM_REQ MAPPINGS

Issue:

/IDT/JOURNEY_NG_NDOC_ITEM_REQ is no longer being used and is not supported.

Solution:

Journey was removed from the standard mappings.

ST22 ERROR WHEN TRANSACTION TYPE IS NOT AN EXPECTED VALUE

Issue:

ST22 error occurs when transaction type is not an expected value. The program was trying to assign a route to a
transaction type that was not expected to be part of the Integration.

Solution:

This logic has been corrected so that the system will do nothing and not attempt to make a call on the transaction
if not configured to do so.

INCOMING INVOICE (MIRO) FOR SERVICE PO'S NOT WORKING AS EXPECTED

Issue:

MIRO transaction on a PO with two or more service lines. If the user selects only some of the service items from
the original PO on the MIRO our line index between KONV and BSEG gets out of sync.

Solution:

The line index was corrected to adjust for this issue.

POSTING IN G/L FOR PLANTS ABROAD TRANSACTIONS IS REVERSED

Issue:

Posting in G/L for Plants Abroad transactions is reversed for ESA and ESE account keys.

Solution:

The account assignment keys for ESA and ESE were reversed and posting in the incorrect direction. Negation
logic corrected for this and is now correct.

PLANTS ABROAD INCORRECT CUSTOMER AND VENDOR NAME

Issue:

When billing multiple documents on same VF01 transaction the partner function may get inadvertently passed
between document numbers.

Solution:

The partner function information is being cleared now between documents.

2014 Thomson Reuters/ONESOURCE. All rights reserved.

Page 10 of 15

INVOICE DATE MAPPING FOR SD

Issue:

Date mapping in standard view of field mapping table was not working for a given sort order.

Solution:

Mappings for invoice date were adjusted with the addition of a simple expression in order to correct the issue.

COMPRESSION OF SOAP DATA IN LOG

Issue:

Logs in the log table were not compressed causing the table to become large and require management sooner.

Solution:

Logs are now saved in a compressed format to minimize table size.

IS_CREDIT ELEMENT MISSING

Issue:

IS_CREDIT element was missing in the log for FI documents using external document number assignment.

Solution:

IS_CREDIT element is now being populated for external document number assignment document types.

CROSS COMPANY CODE TAX SPLIT ISSUE

Issue:

Taxes are being split up equally between the number of expense lines for cross company code transactions.

Solution:

The logic was adjusted so that the correct tax calculation is being applied to the correct expense/revenue line on
the transaction.

LOG CONFIGURATION TABLE

Issue:

Users had the ability to set the log level to blank which caused run time errors.

Solution:

Blank was removed from the drop down options for log level on the log configuration table.

VF11 ORDER CANCELLATION

Issue:

Cancellation against a VA01 sales order was not posting to the audit database when included as part of VF11
batch process.

Solution:

Cancellations using VF11 transaction are now going to audit correctly as required.

SERVICE PO DATA ISSUE

Issue:

Incoming Invoice (MIRO) for Service PO's not working as expected. Service details are not accessible in user-exit
from LIV.

Solution:

This has been corrected. Service details are now accessible in user-exit from LIV. This is done by linking the
RSEG line item to the corresponding BSEG line item.

CURRENCY FORMAT ISSUE

Issue:

SOAP error was occurring for large amounts in "European" decimal notation.

Solution:

Currency format error corrected for European decimal notation.

2014 Thomson Reuters/ONESOURCE. All rights reserved.

Page 11 of 15

IDT/D_TAX_DATA TABLE ADJUSTMENTS

Issue:

Fields were needed that were not in the tax data table.

Solution:

We added Role, Credit/Debit indicator, and Document Date to /IDT/D_TAX_DATA table.

Issue:

The Authority Name field in /IDT/D_TAX_DATA table was too short resulting in truncation of the authority name.

Solution:

The Authority Name changed in /IDT/D_TAX_DATA table to 100 characters.

Note:

Other fields such as the tax amount were not added to the /IDT/D_TAX_DATA table however a user has the
option to add additional fields as desired.

FI DOCUMENT NUMBER IS DEFINED EXTERNALLY

Issue:

When a FI document is created and an external document number is used, the audit update process sometimes
cannot find the correct shuttle.

Solution:

The code was changed so that the correct shuttle will be found.

CURRENCY DECIMAL PLACES ARE NOT TAKEN INTO ACCOUNT FOR AMOUNT FIELDS
Issue:

Currency decimal places are not taken into account for amount fields.

Solution:

Program is now doing a look up V_CURX-CURRDEC and adjusts for decimal places, using function module
TCURX_READ.

AUTHORIZATION CHECK ISSUE

Issue:

Authorization is not checked when refreshing the XML log, allowing data to populate in log and audit screen when
a user does not have authorization.

Solution:

Warning message is now received when no results are displayed either due to lack of data or lack of
authorization.

/IDT/V_ADDR_TYPE TABLE CHANGE

Issue:

/IDT/V_ADDR_TYPE table was confusing with the word Base in the descriptions.

Solution:

/IDT/V_ADDR_TYPE table changed to remove the word "Base" from the address type.

Note:

User must change their custom mappings after this fix or they will fail due to the name change. Go to change
mode in custom mappings version of the /IDT/V_ADDR_TYPE table and delete the word "-BASE" from each line
of mappings.

TRACKING OF INTEGRATION RELEASE VERSION

Issue:

We needed ability to track or note the release version of the product that the user has in their system.

Solution:

A table was added /IDT/D_VERSION which will be populated with the current version number of the Integration
software release as part of the load of the transports at installation.

2014 Thomson Reuters/ONESOURCE. All rights reserved.

Page 12 of 15

BUG NOTES
NOT YET SUPPORTED BUSINESS PROCESSES
Issue:

Down Payments, Consignment/Pipeline Orders are not yet fully productized and workable.

Workaround:

Consult with Thomson Reuters Product Management via a support ticket about timelines of features not yet
fully supported. We will work closely with you to determine best solutions.

UPGRADE INSTALLATIONS
Issue:

Upgrading from an existing 5.x Integration to the newest version hasnt been fully documented and tested.

Workaround:

Engage with Thomson Reuters Professional Services to assist in an upgrade plan and implementation.

GOODS MOVEMENT PROCESS

Issue:

The Goods Movement solution has not yet been ported to version 6.

Workaround:

We are planning to provide a solution in this area as soon as possible. Consult with Product Management
timeline.

HEADER CONDITIONS
Issue:

On a cancellation document for a Plants Abroad invoice the header conditions arent properly displayed.

Workaround:

There is no implication to the G/L posting, this issue is cosmetic only.

SUMMATION IN BSEG AND BSET OF TAX DATA

Issue:

When summarization is turned off, the tax base amount for exempt tax lines are overstated.

Workaround:

This is a known issue with how SAP, specifically the ABAP layer, does its summarization. Given that this is
only occurring on exempt items there is no workaround.

MIX OF POSITIVE AND NEGATIVE LINES IN MIRO

Issue:

When both positive and negative line items are processed within a MIRO invoice document the tax calculation
happens correctly but upon simulation of the document the invoice amounts get reversed causing the invoice
to go out of balance.

Workaround:

Currently one must process the invoice lines as a MIRO invoice document and the credit memo lines from the
return on the purchase order as a credit memo invoice. Credits cannot be included on the MIRO invoice at
this time. Two documents must be processed separately. This is targeted for correction in our next release.

2014 Thomson Reuters/ONESOURCE. All rights reserved.

Page 13 of 15

ISSUE WITH IDT CODE HOOK TO REPLACE TAX CODE ON BSEG

Issue:

Should be able to post a MIRO document with combination of PO line and a non-tax relevant credit GL line.

Workaround:

Currently one must process the invoice lines as a MIRO invoice document and the credit memo lines from the
manually entered G/L line as a credit memo invoice. Credits cannot be included on the MIRO invoice at this
time. Two documents must be processed separately. This is targeted for correction in our next release.

TAX CODE IN ITEM CONDITIONS IS NOT UPDATING IN PO'S FOR US I1 SCENARIOS

Issue:

Tax code in item conditions is not updating in PO's for US I1 scenarios.

Workaround:

This is due to code added in the unboard_train method of the standard response journey. A fix is not available
with this release but is targeted to be fixed in our next release.

SUMMARIZATION ERROR ON DIFFERENT TAX CODES

Issue:

Error message received when Summarization on for FB60 and FB65 Reduced Rate Tax, different tax codes.

Workaround:

User should set summarization configuration in the table as being for both G/L account number AND by tax
code in order to avoid this error. A fix for this is targeted for our next release.

Issue:

Summarization issue when there are positive and negative taxes (e.g. acquisition) on a document that has the
same base amounts for each line.

Workaround:

There is no current workaround for this scenario however we will have a patch release to fix this shortly.

BRACKET TAXES AND FREIGHT ENTERED TOGETHER

Issue:

Alabama, Florida and Maryland bracket taxes and freight entered together raises error VH806 Errors while
transferring conditions: duplicate found.

Workaround: This is limited to the three states and mostly only applicable to retail/ecommerce transactions and only will
happen if the authorities in question have been turned on in Determination (shipped off by default). There is
no current workaround for this scenario however we will have a patch release to fix this shortly.

2014 Thomson Reuters/ONESOURCE. All rights reserved.

Page 14 of 15

DOWNLOAD INSTRUCTIONS
To download and install this release:
4. Retrieve the ONESOURCEIDTIntegrationSAP_6200.zip file from the Customer Center. To do so:

Open the Customer Center at http://customercenter.sabrix.com/sabrixcc

Log on using the user name and password provided by Technical Support.

Find Integration for SAP (Enhanced Global) in the Available Products list and verify that Installed Version
is set to None.

Click Download for Integration for SAP (Enhanced Global).

Save the file.

5. Unzip the ONESOURCEIDTIntegrationSAP_6200.zip file.

6. Download the User, Install and Programmers, and Configuration Guides from the Support Network at
https://www.onesourceidtsupport.com

2014 Thomson Reuters/ONESOURCE. All rights reserved.

Page 15 of 15