Taulia experience center

Article Number: 000010689

Configuration activities

IMG tree node

The configuration transactions for the Taulia add-on for the SAP integration suite, managed gateway can be found in an IMG tree node.
In the transaction code, SPRO, go to the node → Integration with Other SAP Components → SAP Taulia Cloud Integration Gateway.

Define document types for transfer
This configuration item can be reached in the IMG tree under → Integration with Other SAP Components → SAP Taulia Cloud Integration Gateway → Application Specific Settings → Define document types for transfer, or via transaction code TAUCIG_DOCS.

This configuration activity defines which invoice, credit memo, reversal, and payment documents will be transferred to the Taulia Platform. Add all company codes and document types that should be transferred. Mark document types that are used for payments as a payment.

The company code field can be left blank if all company codes are applicable to the setting.

This is a required configuration to facilitate Taulia Working Capital solutions. A recommendation is only to add document types that must be transferred, and that will enable suppliers to obtain status information.

Prerequisites
Configure all invoice and credit memo document types, which must be transferred to the Taulia Platform for Taulia Working Capital solutions. Add relevant payment document types to facilitate supplier self-service and Taulia Analytics. Also, add reversal document types: these will be used to update the status of the original invoice to present them as “Cancelled” to suppliers.

Activities
Add all company codes and document types that should be transferred. Mark document types that are used for payments as payment by selecting the “Payment” checkbox.

You can just leave the company code blank if all company codes apply.

Please add all document types that should be in scope for Taulia Working Capital Solutions.

Down payment transfer configuration
This configuration item can be reached in the IMG tree under → Integration with Other SAP Components → SAP Taulia Cloud Integration Gateway → Application Specific Settings → Define down payments for transfer, or via transaction code TAUCIG_DWNPMT.

This configuration activity defines which document types and special GL indicators are used for down payment requests and down payments, which should be transferred to the Taulia Platform. Add all combinations of company codes, document types, and special GL indicators that should be transferred. If a special GL document is not defined here, it will not be transferred to the Taulia Platform.

The company code field can be used to differentiate combinations used in different company codes. The company code field can be left blank if the same combinations of doc types and special GL indicators are used for down payments globally.

Prerequisites
Please configure all down payment requests and down payment documents, which must be transferred to the Taulia Platform to facilitate Taulia Working Capital solutions. Please add relevant down payment documents which are used to pay your down payment requests.

Activities
Add all combinations of company code, document type, and special GL indicator that should be transferred.

You may leave the company code blank if the same document type and special GL indicator combinations apply to all company codes.

Special clearing
This configuration item can be reached in the IMG tree under → Integration with Other SAP Components → SAP Taulia Cloud Integration Gateway → Application Specific Settings → Define clearing documents, or via transaction code TAUCIG_CLEARING.

This configuration activity defines which document types and transactions are used for the clearing of invoices and credit memos. If an invoice or credit memo is cleared with one of the defined doc type/ transaction combinations, it will be transferred to the Taulia Platform with a status of “Cleared.” The clearing document itself will not be transferred.

The company code field can be used to differentiate combinations used in different company codes. The company code field can be left blank if the same combinations of clearing doc types and transaction codes are used globally.

Prerequisites
Please configure all combinations of document types and transaction codes that could be used to clear invoices and credit memos per company code. These will be used to update status of the original document to present them as “Cleared” to suppliers.

Activities
Add all combinations of company codes, document types, and transaction codes that should be considered internal clearing documents.
You may leave the company code blank if the same doc type and transaction code combinations apply to all company codes.

SCF Collection Accounts
This configuration can be reached in the IMG tree under → Integration with Other SAP Components → SAP Taulia Cloud Integration Gateway → Application Specific Settings → Configure SCF Collection Accounts, or via transaction code TAUCIG_SCFCOLL.

This configuration is used to identify applicable third-party funding accounts to enable document-level funding instructions. These are the accounts where the funds will be sent at the invoice due date and will be updated on the document when the supplier requests early payment.

Activities
Enter the Partner Bank Type(s) and Vendor/Business Partner number(s) for all Payees eligible for funding Taulia programs. All applicable bank types and funder numbers should be maintained here. The bank identifier must be unique and present on the funder vendor master/business partner before being maintained here.

Interface setup program
This program is used to set up the required interfaces for inbound and outbound communications with the Taulia Platform via the SAP integration suite, managed gateway. This task is a one-time activity.

On the selection screen, the program lists all the inbound and outbound interfaces that can be set up for system integration. As a preparation step, make sure to run the program TAUCIG_ADD_SETUP_ENTRIES via SE38 or execute transaction code TAUCIG_SETUP. The checkboxes for all tables must be marked when the program is executed.

Once the preparation step is done, the Interface setup report can be accessed via the IMG node under → Integration with Other SAP Components → SAP Taulia Cloud Integration Gateway → Configure the connections to send messages.

The report can also be executed by transaction code TAUCIG_INTERFACE_EXE or via SE38 program TAUCIG_INTERFACE_SETUP.

Program selection screen
This screen consists of two main sections and lists all supported transactions in each flow:

• Outbound Messages sent to SAP integration suite, managed gateway - Select the outbound interfaces in scope for your implementation.
• Inbound Messages sent from SAP integration suite, managed gateway - Select the inbound interfaces in scope for your implementation.

You can either select the transactions individually, as required or click Select All to select all listed transactions for both flows.
You are required to provide the following information:

Data Center
1. To update your data center details, click the Choose a data center drop-down, and then choose your data center.

Logon Data
2. Select one of the following to indicate if the connection is to a production or test instance:

• Connect to SAP integration suite, managed gateway Production Instance
• Connect to SAP integration suite, managed gateway Test Instance

3. Select one of the following types of authentication methods:

• Select User ID / Password and enter authentication information to connect to the SAP integration suite, managed gateway
• Select X.509 SSL Client Certificate and choose the Certificate Name (TAULIA, for example).

4. Enter the following details for HTTP Proxy options:

• Name of the Proxy Host
• Port Number of Proxy Host
• User name of Proxy Server
• Proxy User Password

Once the program is executed, the attributes for the relevant interfaces will be properly set. These attributes can be displayed in the transaction SOAMANAGER.

The Logical Port setting is overwritten each time you run the interface settings for outbound web services.

After you run the report, you can view the status in transaction code SLG1 using the object TAUCIG_INTERFACE and subobject IF_LOGS.

Global parameters
This configuration item can be reached in the IMG tree under → Integration with Other SAP Components → SAP Taulia Cloud Integration Gateway → General Settings → Maintain Global Taulia Parameters, or via transaction code TAUCIG_CPARAM.

This configuration activity allows parameter definition to facilitate variable behaviors within the Add-on. The following parameters come with pre-defined logic, but additional parameters may be defined for use in custom logic.

Prerequisites
The required parameters may be specified in each client or may be added to a transport to apply the same parameters across the entire landscape.

Table cleanup
This program allows the cleanup of old records from transactional data in various Taulia database tables and can also be used for test system data refreshes.

The report can be accessed via the IMG node under → Integration with Other SAP Components → SAP Taulia Cloud Integration Gateway → Table Cleanup

The report can also be executed by transaction code TAUCIG_CLEANUP or via the SE38 program TAUCIG_CLEANUP.

Schedule this cleanup program to run on a periodic basis to delete old records. When a test system refresh is done, a manual run with the Refresh option should be executed.

Program selection screen

• Delete entries older than

Provide a date that will be used to delete records that have a creation date before the input date. The recommended value is (current date - 90 days).

• Refresh the whole table

Caution! This will clear the transactional data tables completely.

Only run the program with this option on a test system where data has been recently refreshed, and communication to Taulia must be reset. This option will not be executed in productive systems.

• Batch size

Provide a number of records to be deleted at a time. Recommended value: 100

Scheduling jobs
The Taulia extractions happen in 2 steps:

• Feeders detect new objects and object changes and add them to an outbound queue
• Collectors read a batch of object IDs from the outbound queue, collect the related data, and send the data out.

These two processes must be scheduled for each object to transfer (vendors, invoices, payments). In addition, a Company Code extract must also be scheduled to be executed on a periodic basis.

Company Code Extraction
Report TAUCIG_COMPANYCODE_EXPORT must be scheduled to run on a periodic basis.
The recommended frequency for scheduling is once a day. This report does not contain any selection screen parameters, so no variants are needed.

Feeders
Report TAUCIG_QUEUE_FEEDER is the feeder program. Its selection screen has one input field, “Taulia integration process.” Different variants for the feeder program must be created so that the different objects are considered and added to the outbound queue.
Create the variants as follows:

The feeder program must be scheduled multiple times, one for each variant created. Schedule these jobs to run on a periodic basis. Typical frequencies vary from 15 to 5 minutes of interval. Please take a look at your system load to schedule recurring jobs properly.

Collectors
Report TAUCIG_QUEUE_COLLECTOR is the data collector program. Its selection screen has two input fields, “Taulia integration process” and “Batch size.” Different variants for the collector program must be created so that the different objects are considered and sent out to the Taulia platform.

Create the variants as follows:

The default (and recommended) value for Batch size is 500. This indicates the number of object IDs retrieved from the queue and sent in one job run. The batch size can be adjusted to be more adequate for system performance.

Table clean-up
Report TAUCIG_CLEANUP must be scheduled to run on a periodic basis.
This report cleans up temporary data no longer needed in the system. Make sure to choose the option “Delete entries older than” and create a dynamic variant with date calculation. The recommended value is (current date - 90 days).

Customizing behavior through BAdIs
The Business Add-Ins (BAdIs) on the Taulia Add-on are grouped under the structure node → Integration with Other SAP Components → SAP Taulia Cloud Integration Gateway → Business Add-Ins(BAdIs)

You can implement these BAdIs to enhance the standard functionality.

End-user transactions

Queue manager
The Queue manager shows which objects are queued for transfer to the Taulia Platform. Objects which have been successfully transferred are automatically removed from this queue.

The report can be accessed via the IMG node under → Integration with Other mySAP.com Components → SAP Taulia with Managed Gateway → Taulia Working Capital Integration → General Settings → Maintain the Taulia Queue for Object Transfer.

The report can also be executed by transaction code TAUCIG_QUEUE or via SE38, program TAUCIG_QUEUE_MANAGER.

The Queue manager can also be used to manually add objects that need to be transferred to Taulia or to retransfer objects as necessary. Removing objects from the queue will also function to prevent their transfer.

To manually add objects that must be transferred to Taulia, click "Insert Row" and enter the Object Type and Object ID of the items you wish to transfer. You may do this for multiple items at the same time by clicking "Insert Row" multiple times. Save your entries to add the objects to the queue.

To prevent an item from being selected for transfer to Taulia, select the checkbox next to the item and click "Delete Row." You may do this for multiple items at the same time by selecting the checkbox next to multiple rows. You can save your entries to remove the objects from the queue.

Blocklist Monitor
Once the required jobs are activated, data will be transferred to the Taulia platform at the prescribed intervals and according to the configuration defined. The Blocklist monitor is a user interface to limit data transfer from the SAP add-on that can be used to display and maintain the blocklist. A blocklist is a list of manually maintained entries via the blocklist monitor. Once on the blocklist, a given object (or its related objects) will not be added to the outbound queue and won’t be transferred to the Taulia platform unless it’s already in the outbound queue.

The following types of objects are allowed for blocking from being sent to Taulia:

• Company Code
• Supplier
  • For all company codes
  • For a specific company code
  • by country
  • by account group
• Invoice
• Payment

Any data previously sent to the Taulia platform will not be deleted. However, the object will no longer be updated and adjusted with further updates as long as the item is on the block list.

The report can be accessed via the IMG node under → Integration with Other mySAP.com Components → SAP Taulia with Managed Gateway → Taulia Working Capital Integration → General Settings → Maintain Blocklist.

The report can also be executed by transaction code TAUCIG_BLOCKLIST or via the SE38 program TAUCIG_BLOCKLIST.
When the blocklist transaction is open, the following buttons are available at the top of the screen:

• Add Row - Allows the user to add a single entry to the blocklist
• Remove Row - Removes the highlighted row(s) from the blocklist

When entries are added or removed, the SAVE button must be hit to record the updates in the database.

Note: Object IDs are not validated upon insertion into the blocklist. Ensure the values added are correct and contain the necessary leading zeroes. Inputting an incorrect value will result in no block occurring.

The following describes the behavior of the blocklist according to the object type and the "all related" flag:

Retransfer and transfer priorities
Transaction TAUCIG_TRANSFER or via SE38, program TAUCIG_TRANSFER can be used to trigger a mass retransfer of Vendor master, invoices, and/or payments based on a selection by vendor and date range. Users can also choose the priority on which the objects will be added to the queue. Objects with higher priorities are picked first by the data Collectors.

The retransfer transaction can be used to:

• Transfer objects that were previously out-of-scope due to blocklist restrictions
• Transfer missed or incorrectly transferred documents due to a system issue
• Adjust the priority of objects already in the queue, waiting to be transferred
• Retransfer objects that have not changed recently

There is an option to either manually mark the desired documents for transfer or to automatically add all of the relevant objects to the queue for transfer in a background process.

Processing options:
If the "Display selection for further processing" radio button is selected, An ALV output is displayed with an object list based on the selection screen criteria. The user can then select the lines and click on the button "Add marked ones" to add them to the outbound queue.
A ‘Priority’ dropdown will be displayed to choose the priority on which the objects will be added to the queue.
10 - High Priority
50 - Standard Priority
100 - Low Priority
Objects with higher priorities are picked first by the data collectors.

If the "Retransfer selection in the background automatically" radio button is selected,
There’s no option to select objects to be added to the queue. The program will select the data according to the selection criteria and will add all the relevant items into the outbound queue with standard priority in the background. 

Visualizing application logs
The Taulia add-on creates application logs with execution details for every process. These logs can be visualized via transaction SLG1.
The following Objects and subobjects can be used to filter the relevant information:

The "message ID" field displayed in SRT_MONI for a given message can also be provided on the “External ID” field in SLG1. This ID will refer to logs generated when the particular message was created.

Message monitoring
Transaction SRT_MONI can be used to monitor inbound and outbound messages sent and received by the Taulia add-on.
The following table lists all the interfaces used by the Taulia add-on for sending and receiving messages:

The “Message-ID” value for a given message can be used as selection criteria in transaction SLG1, field “External ID.” This will list all the logs recorded when the message was generated and sent through the interface.

User-defined search criteria in SRT_MONI
To enable searching in SRT_MONI based on payload content, the specific search fields require configuration. This configuration can be accessed by executing transaction SOAMANAGER and navigating to Monitoring → User-Defined Search.

To create a new configuration, select the Create button and locate the interface for which you wish to configure the search fields. All Taulia interfaces are available in the http://sap.com/xi/TAUCI1 namespace. Below is a list of suggested interfaces and fields. However, you may choose to configure fewer or more fields based on your preferences.

Once in the configuration screen, to add a field into the search parameters section, either drag and drop the desired field or right-click and select Add. Once the fields have been added, save the configuration into a transport request, which can be moved to other systems.