Taulia experience center
CUSTOMER SUPPORT SERVICES
There are settings and configurations located on the Taulia platform that affect the behavior of the platform for your suppliers. If you want to make changes to those settings, you should contact Taulia Technical Services describing the changes. Some changes can be completed quickly while others may require additional requirements gathering, testing, and can incur an implementation fee.
Please notify Taulia Technical Services a minimum of (5) business days before you intend to perform the SAP system refresh. Please provide the SAP system ID to be refreshed and (if applicable) the XMLRPC user ID configured in the POD.
Please check your ERP system to ensure that a duplicate document does not exist. If you do not find a duplicate document, please contact Taulia Technical Services for assistance.
We are excited to support you with your upgrade! Please contact Taulia Technical Services to get your upgrade started.
If your supplier has selected a new Admin for their account, they can send an invitation in the User Manager to the new admin. If the supplier did not appoint a secondary admin, please advise the supplier to contact Taulia Technical Services to assign a new admin. Note, Technical Services will require the new admin to authenticate themselves prior to being added to the account.
There are a couple scenarios which can cause your supplier to not receive their invitation, whether it is a delay in the email being received or even an issue with the email address. Please log into the Supplier Center in the Taulia Buyer UI and search for suppliers with Needs Attention in the Status filter. Here you can drill down to additional error types for resolution.
Taulia is unable to “un-invite” a supplier but there are self service options you may consider. You may log into the Supplier Center in the Taulia Buyer UI and edit the invited emails to invalid dummy emails to further prevent enrollment. If there are a large number of suppliers, you may correct this action in SAP by adding the suppliers to the Taulia blocklist.
There are a few reasons your suppliers may not see a Purchase Order. We initially suggest you trigger a retransfer of the Purchase Order from within SAP. Open the PO and select "Mark object for retransfer" via the Taulia Generic Object Services. If there are any errors, you can view them in the Connection monitor (/n/TAULIA/CONNECTOR). If this does not resolve the issue, please contact Taulia Technical Services for additional troubleshooting.
Log into the Supplier Center in the Taulia Buyer UI. Select Enrolled in the Status filter and search to see the list. If you do not have access to this feature, contact your Taulia administrator.
We are a technology company dedicated to helping simplify business transactions and increase cash flow through an easy to use platform.
Taulia Support and the entire Technical Services team is dedicated in helping you succeed. To do that, we have policies in place to show our unwavering commitment to you. Take a moment to read through our support policies to learn more.
The Taulia POD runs as a service on a locally hosted server. The POD is the communication device which directs connectivity between the Taulia Platform and your Taulia SAP Add-On. There may be a need to stop, start or restart the POD in order to troubleshoot the connectivity, upgrade the POD version or re-enable the service.
The Taulia POD may be installed on a Linux or Windows server. This document shows how to restart the service from both systems.
Please find below the steps for Stop, start or restart the POD from a Windows and Linux system:
Stop, start or restart the POD from a Windows system:
1 - Locate the POD folder and make sure the POD files are present.
2 - Determine whether the Taulia POD service is in the service list. The services can be found by pressing Windows + R to open the Run dialog. Type services.msc.
3 - Locate the POD service in the service list and select it.
4 - If the POD is currently running, the status shows Running here. The service can be stopped if needed. Common reasons for stopping the POD include POD upgrade or server maintenance. Click the Stop button to stop the service. When you are ready to start the POD again, follow instructions in Step 6.
5 - Alternatively, if you have been advised to restart the POD to resolve or troubleshoot an issue, click the Restart button to stop/restart the service immediately.
6 - If the POD is turned off or has never been started, the status shows blank here. Click the Start button to start the service.
7 - Starting or restarting the service will produce the below service control window:
8 - Make sure the POD status shows as Running after it is started/restarted.
Stop, start or restart the POD from a Linux system:
1 - Locate the POD folder and make sure the POD files are present.
2 - Check the POD status by typing the following command: ./tauliapod status
3 - If the POD is currently running, the daemon process can be stopped if needed. Common reasons for stopping the POD include POD upgrade or server maintenance. Type the following command to stop the POD: ./tauliapod stop
4 - Confirm the POD was stopped successfully by running the status command: ./tauliapod status
5 - Alternatively, if you have been advised to restart the POD to resolve or troubleshoot an issue, type the following command to restart the POD: ./tauliapod restart
6 - Confirm the POD was restarted successfully by running the status command: ./tauliapod status
7 - If the POD is turned off or has never been started, the status will show Taulia POD is not running. Run the following command to start the POD: ./tauliapod start
8 - Confirm the POD was started successfully by running the status command: ./tauliapod status
If you are not able to perform some of these POD maintenance activities, you may not have authorization. Please confirm that you have Admin access on the POD server or contact the server administrator to perform the required maintenance.
Restarting the POD did not resolve my issue. How can I pull POD logs for further troubleshooting?
The Taulia POD automatically writes logs for each process to the following directory: [install folder]/wrapper/pod/log
Follow the instructions here to extract the necessary log files.
Information on Taulia’s supplier deactivation policy.
Information on how Pfizer’s Taulia users can reset their passwords.
This article explains the standard way credit notes are handled on the Taulia platform for buyers set on the standard credit note blocking solution.
What to do when program /TAULIA/BS_SYS_REFRESH to perform the refresh steps in SAP fails with the message 'Can not run this Program on same system.' in the job log.
New users can be added to the Buyer UI or existing users can be deactivated at any given point in time. This can be done by any Admin user that has access to the Buyer UI.
Information on how to mass retransfer supplier masters, purchase orders, invoices, workflow invoices and payment documents from SAP to the Taulia Platform.
Vanessa, Technical Services Manager