Skip to main content

Solutions

Products

Recommended products

Questions? We are here to help.
Contact us

Purchase

Questions? We are here to help.

Resources

ONESOURCE table configuration for SAP

Base, Route, and Journey configuration

Base Mappings

Transaction Code:
/N/IDT/BASE_MAPPING_V
The Base object makes possible the use of configurable field mappings. It is a way to dynamically represent relationships between different levels of the XML structure and how they relate to each other. This allows a configuration driven code, rather than hard coding structure relationships. It also allows Thomson Reuters make changes in the interface easier. This table is view only and not modifiable by the customer. You can see in the view above that there are base mappings listed here for the Global Next product but also several at the top for the Goods Movement (GM) product. If you do not have the GM product installed in your system you will likely not see the GM line mappings as they are now only added when you transport in the Goods Movement product to overlay over the standard Global Next table structures. The Base mapping table has been moved as of release 6.4.1.0 to the new Mappings menu along with the new field mapping table and address mapping table transactions.

Select Route for SD and Purchasing

Transaction Code:
/N/IDT/SELECT_ROUTE_V
This table controls which route is responsible for what process in SAP by mapping the route to the document category within Sales/Distribution (application V in first column) and Purchasing (application M). This table is view only and not modifiable by the customer.

ONESOURCE Route Configuration

Transaction Code:
/N/IDT/ROUTE_CONFIG
As of the transports for the 6.3.0.0 release this table will be shipped blank and you will need to enter all the fields as shown in the screenshot above.
This table is used to turn on or off the various routes in the system and tie the route to the required
Condition Formula
 (AltCty) and
Condition Base Value
 (AltCBV) that is referenced in the pricing/tax procedure. You will need to maintain the condition formula values based on the formulas created in the
Install and Programmers Guide
 -> “Creating Condition Value Formulas” before executing any transactions in SAP.
Additionally, this table can be used to control whether the Integration is to be used for a given module of SAP by country group or company code assignment. In above example we have assumed Integration is used in all countries and all business processes. However, configure this as your business might require, for example native SAP tax calculation for AP and LIV/Purchasing but use ONESOURCE Integration for SAP in SD and AR/Billing areas. More specifically you may wish to:
  • Maintain some company codes to use Integration 6.x only for Sales transaction and not for Purchasing and Accounts Payable.
  • Maintain some company codes set to use an older version of Integration for some company codes and the New Integration 6.x for others.
  • Use native SAP calculations for some modules and Integration 6.x for others.
  • Manage their conversion of company codes gradually to the new version over time.
note
Customers upgrading to 6.3 or later releases from previous version (< 6.3) of Global Next, delete the existing entries and re-create. You can use the table below as a guide to copy and paste to your configuration for either new customer or update as needed. Modify AltCTy as needed.
Route Name
Sort order
Active
Country
Group
COCD
App
AltCTy
AltCBV
/IDT/ROUTE_GROUP_BILLING_GEN
100001
*
*
V
994
0
/IDT/ROUTE_GROUP_BILLING_PA
100001
*
*
V
994
0
/IDT/ROUTE_GROUP_DELIVERY
100001
*
*
V
994
0
/IDT/ROUTE_GROUP_PURCHASING
100001
*
*
M
994
0
/IDT/ROUTE_GROUP_SALES
100001
*
*
V
994
0
/IDT/ROUTE_NON_GROUP_DOC_AP
100001
*
*
TX
991
994
/IDT/ROUTE_NON_GROUP_DOC_AR
100001
*
*
TX
991
994
/IDT/ROUTE_NON_GROUP_DOC_A_GL
100001
*
*
TX
0
0
/IDT/ROUTE_NON_GROUP_DOC_DNF
100001
*
*
TX
991
994
/IDT/ROUTE_NON_GROUP_DOC_DP
100001
*
*
TX
991
994
/IDT/ROUTE_NON_GROUP_DOC_DT
100001
*
*
TX
991
994
/IDT/ROUTE_NON_GROUP_DOC_FB5
100001
*
*
TX
991
994
/IDT/ROUTE_NON_GROUP_DOC_FI
100001
*
*
TX
991
994
/IDT/ROUTE_NON_GROUP_DOC_GM
100001
*
*
TX
0
0
/IDT/ROUTE_NON_GROUP_DOC_GM_BR
100001
BR
*
TX
0
0
/IDT/ROUTE_NON_GROUP_DOC_LIV
100001
*
*
TX
991
994
/IDT/ROUTE_NON_GROUP_DOC_PUR
100001
*
*
TX
991
994
/IDT/ROUTE_NON_GROUP_DOC_SES
100001
*
*
TX
991
994
/IDT/ROUTE_UPDATE_AUDIT_DB
100001
*
*
0
0
/IDT/ROUTE_NON_GROUP_DOC_DT_RC
100001
*
*
TX
991
994

Automatically Processed Journeys

The Auto processed Journey view ties journeys to routes for processing. A route can be made up of multiple journeys. The table controls which processes are active in what country groups and company codes.
Transaction Code:
/N/IDT/AUTO_JOURNEYS_V
Transaction Code:
/N/IDT/AUTO_JOURNEYS
You can override our standard delivered mappings in this custom view. In the sample above, Self-Assessment journey was activated for company code 4000.

This article applies to:

  • PRODUCT: ONESOURCE Indirect Tax
  • Sub-Product: SAP