Requirements
.Net Framework 4.0+ installed on your computer.
Getting started – download the files
Avatax Event Service (AES) is a service that runs in the background, which runs all the time, but doesn’t have an interface. This application detects any sales document created outside of SAP, with other addons or systems, and automatically calculates taxes using Avatax.
Link : http://www.axapsolutions.com/en/downloads
Scroll down until you find the AES (Avatax Event service), as shown:
Download it, create a folder in your unit, and extract all the files from the Zip folder.
Once is saved on your PC, please, check that the file is unblocked by clicking on properties with the right button of the mousse. If the checkbox shown below is not checked, please, check it and then press apply and ok.
3.1 Prepare the console
Go to the Windows bar, and search for the cmd (command prompt); once you find it, press right-click to run as administrator.
Then add in the console “cd” following the path where the solution is saved. For example: C:\argentis\aes
3.2 Add the framework path to run the “install uti”
It is necessary to run the “install uti”, which is in the Framework folder, to install the service. This is executed from the console, so you must add the path to it.
Depending on the Framework the customer has is the path to run the “install uti”. The path can be found on the web or inside the Microsoft.NET folder. Always take the latest version.
This is an example:
Copy and paste the path into the console and add “\installutil” as shown:
After taking the service name from the .exe file, add it into the console and press enter as shown:
32 bits: C:\Windows\Microsoft.NET\Framework\v4.0.30319\installutil Argentis.AvataxEventService.exe
64 bits: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\installutil Argentis.AvataxEventService.exe
This is going to install the service. If everything is correct you should see this message in the console:
3.3 Look for the service.
If the installation was completed successfully then you should find the service.
Go to the “aes” folder and open the file named “Argentis.AvataxEventService.exe.config” with the notepad++
In order to connect the service to your SAP, you must add the SAP server and other details in that file. All the specific information must be added from row 46 to 71.
4.1 DataServerName > Add the customer database name.
The customer can provide it. Alternatively, you can get this information from the customer SAP as shown:
Take the “Current server” name to add it into row 46 after “value=”
4.2 DatabaseServerType > Add the number from the table based on the customer data.
If the custoemr SAP runs with SQL, add the numebr dependign o nthe version or add the Hana number
4.3 DatabaseUsername and password
This information must be provided by the client, because it is not available from SAP, to complete the below rows:
4.4 LicenseServer and port
Then you must add the License server name and port
This information can be found in SAP, under Licenses, as shown:
Take the information from the top, where it says “License Server” and “Port”
4.5 Company database name, user and password to connect
Add the SAP details into the below rows from the symbol “=”
You can take the detaisl from this screen:
4.6 SLD Server
Add the same information that is in “dbserver name” (row 46)
Any ulterior change to this information requires to refresh the service from the service screen.
Go back to the services. To start running the application select the service, right-click and press “start”.
The startup type must always be “Automatic” to warranty compliance with the company processes.
Depending on the SAP database is the script to create a Queue table and modify the SBO_SP_TransactionNotification procedure.
For SQL, create the below Queue table
CREATE TABLE [dbo].[Queue](
[ID] [int] IDENTITY(1,1) NOT NULL,
[object_type] [varchar](20) NOT NULL,
[list_of_key_cols_tab_del] [varchar](255) NOT NULL,
[Time] [datetime] NOT NULL,
[transaction_type] [varchar](1) NOT NULL,
[app_name] [varchar](255) NOT NULL,
[list_of_cols_val_tab_del] [varchar](255) NOT NULL,
[retries] [int] NOT NULL
) ON [PRIMARY]
And add this script to the SBO_SP_TransactionNotification stored procedure in your SAP Company DB
--Avatax Event Service Post Transaction Notification
INSERT INTO "Queue" ([Time],[object_type],[transaction_type],[list_of_key_cols_tab_del],[list_of_cols_val_tab_del],[app_name],[retries])
VALUES (GETDATE(), @object_type, @transaction_type, @list_of_key_cols_tab_del, @list_of_cols_val_tab_del, app_name(),0)
For Hana
CREATE COLUMN TABLE "InsertDBName"."Queue"
(
"ID" INTEGER CS_INT GENERATED BY DEFAULT AS IDENTITY NOT NULL ,
"object_type" NVARCHAR(20) NOT NULL ,
"list_of_key_cols_tab_del" NVARCHAR(255) NOT NULL ,
"Time" DATE NOT NULL ,
"transaction_type" NVARCHAR(1) NOT NULL ,
"app_name" NVARCHAR(255) NOT NULL ,
"list_of_cols_val_tab_del" NVARCHAR(255) NOT NULL ,
"retries" INTEGER CS_INT NOT NULL ,
PRIMARY KEY ("ID")) UNLOAD PRIORITY 5 AUTO MERGE ;
And alter the SBO_SP_TransactionNotification procedure, including the following:
--Avatax Event Service Post Transaction Notification
INSERT INTO "Queue" ("Time", "object_type", "transaction_type", "list_of_key_cols_tab_del", "list_of_cols_val_tab_del", "app_name", "retries")
SELECT CURRENT_DATE, object_type, transaction_type, list_of_key_cols_tab_del, list_of_cols_val_tab_del, SESSION_CONTEXT('APPLICATION'), 0
FROM Dummy;
Search for the event viewer from the windows bar. Once open, go to “Application and services logs” and select “Argentis”.
From here you can check the information of what the service has been processing, If there is an error you would find it here.
You can also check if the connection details are correct.
Prior to changing any settings, you should clear the log, then stop the service. Then you can modify the details and then restart the service.