OGT is a bridge between Ariba and OneSource tax determination. OGT is responsible to transform the data from source system (Ariba) to tax engine and sending the tax response back to engine. It works similarly like GlobalNext for SAP.
Four XML files are generated during data transmission.
OGT is web-based interface. User should use his/her determination id/password to log in OGT system.
Step 1: Enable the Ariba system for OGT
Ariba Realm Specific Configurations >> Activate the Ariba system for external tax calculation in OGT. It is
system dependent configuration. Realm configuration should be activated in each OGT environment.
Step 2: XML Log Enablement
Enable the xml log for each Ariba company codes under each realm. There are two calls, one is at
purchase requisition level and other is at Invoice requisition level.
Every transaction has four XML files.
Step 3: Tax Summarization Configuration
For US, all the sales taxes summed up to one single line. For VAT, single summarization option has been
selected since Ariba does not allow duplicate tax types for multiple lines.
Tax Type Mapping >> OITD Tax code qualifier will return additional attribute (tax mapping), which would
map to Ariba tax type.
Example >> US = “SalesTax” / EU countries = “VATTAx”
Step 4: Custom Field Mapping
Any additional field is required from Ariba source system for tax calculation then custom field mapping
option would be used.
Example: Line level attribute16 has been mapped to pass WBS project type value.
Step 5 OITD Configuration
There is no such difference in OITD in terms of configuration except following.
1. All the users should have “integration user” role at each company level in OITD to access the
OGT log and “integration configurator” role for OGT configuration
2. TCQ should have “tax type” parameter to determine the Ariba tax type.
Example for US has given below:
