Taulia experience center

Article Number: 000010759

HIGHLIGHTED ITEMS FOR THIS RELEASE

Added Flexibility for S/4 Migrations

An ERP client ID is included with all data sent to the Taulia Platform in order to ensure correct partitioning of data for customers that send data from multiple SAP clients. The default value for this client ID is the logical system ID from the SAP Clients table (T000). With this release, this ID can be overwritten by a new variable (ERP_CLIENT_OVERRIDE) in the Global Taulia Parameters (t-code: TAUCIG_CPARAM) in case there is a need to mask the current ERP Client ID with a different one. This could be used for certain ECC to S/4 migration scenarios and should only be used in consultation with your Taulia representative.

NEW FEATURES AND ENHANCEMENTS

Improvements to Compliance Credit Notes for Dynamic Discounting

The configuration for DD Credit Note Posting Settings (t-code: TAUCIG_CNPOST) has been improved to make both the document type and the posting type be required fields. This avoids posting errors due to null values maintained in the configuration. The default document type and posting type will still be used if no configuration is maintained for a given company code.

Improved Tax Determination in Payables Invoice Collector Process

The logic to determine supplier tax country and supplier tax type on the Payables Invoice Collector integration process has been improved to be more accurate for suppliers that have multiple VAT registration numbers. Now, if there is a VAT registration number present on the invoice, the tax country associated with that ID will be selected. If a VAT registration number is not present on the invoice, the tax country will be the supplier's address country. The tax type will be determined as either VAT, GST, or SALES based on the tax country.

Performance Improvement in Payables Payment Feeder Process

A performance improvement has been implemented in the logic to identify cleared documents during the Payables Payment Feeder process.

Enhanced Payables Payment Collector Process

The Payables Payment Collector integration process ensures that the payment program has time to link invoices to their payment records during large payment runs by retrieving documents posted further in the past than the last payment run. This is known as the payment GAP interval, and the default value for this interval is 5 minutes. Customers with extremely large payment runs that take longer than 5 minutes to complete may need to increase this interval in order to ensure that all invoices processed in the payment run are linked to the payment record when the payment is sent to the Taulia Platform. A new variable (PAYMENT_GAP) has been added in the Global Taulia Parameters (t-code: TAUCIG_CPARAM) in order to overwrite the default interval with with a customer-defined value.

The resetting of a payables payment document without the posting of a reversal will now trigger a retransfer to the Taulia Platform in order to have the status updated to show that the payment was cancelled.

Handling of Reversed Partial Payments

The reversal of a payables partial payment will now trigger a retransfer of the partial payment and the partially paid invoices to the Taulia Platform in order to have the status updated to show that the payment was voided and that the invoices are now open.

New Early Payment Request Validation

A new check has been added to the Early Payment Request integration process to reject the early payment request if the requested invoice is part of a payment order. This check applies to all payables finance types.

Improved Job Handling

The handling of background jobs for Taulia processes is enhanced to log messages when creating, submitting, and releasing a job, and to delete any job that fails to release.

Improved Logging

Enhanced the application logging with the following changes:

• Removed a superfluous message that was being raised when the Taulia Business Add-in (BAdI) for Blocklists was implemented
• Added a message to identify when custom code is executed within the BAdIs for Blocklist and Vendor master update
• Enhanced the queue feeder processes to raise an info message when there is no new/changed data to be added to the queue table
• Adjusted the log object and sub-object texts to be more descriptive and consistent across objects

FIXED ISSUES

Miscalculated Invoice Net Amount

Fixed an issue with invoice net amount calculation where credit line items were being added to the total net amount rather than deducted. This was causing the net amount to be overstated for invoices with credit items.

Absent Tax Rate for GST

Fixed an issue that was causing the GST tax rate to be cleared from the tax summary data on payables invoices sent to the Taulia Platform. The tax rate will continue to be cleared for invoices with Sales tax.

Bug in Early Payment Request Validation

An issue was discovered with the validation, which checks that the requested invoice is not locked in a payment proposal during the Early Payment Request integration process. The validation looked at payment proposals from prior years, which incorrectly caused the early payment request to be rejected. This has now been resolved.

Missing Item Details in Payables Invoice Collector Process

Resolved a defect in the Payables Invoice Collector integration process, which was preventing the item details from being extracted on non-PO invoices that have an MM document. This was only problematic when there were multiple documents extracted in a given batch, as it did not affect the first document in the batch.

Mishandling of Documents in Payables Payment Feeder Process

Fixed a bug in the Payables Payment Feeder process which incorrectly caused internal clearing documents with a vendor line to be added to the Taulia queue table. Internal clearing documents should not be transferred to the Taulia Platform but their related cleared items are retransferred so that their status can be updated to cleared.

Resolved an issue in the Payables Payment Feeder process which was causing clearing documents to be ignored when their document type and transaction code are configured as company code agnostic entries in the Taulia Clearing Documents table (t-code: TAUCIG_CLEARING).

Incorrect Error Handling

Resolved an issue in the Early Payment Request and Early Payment Cancel integration processes that was preventing errors from being captured when opening, submitting, or releasing the relevant background job. Now these errors are captured in the application logs, and the process ends.

Short Dumps in Early Payment Request Process

Fixed an issue that was causing a short dump in the Early Payment Request integration process for Dynamic Discounting.

Short Dumps in Vendor Data Collector Process

Resolved an issue that was causing a short dump in the Vendor Data Collector integration process when the vendor does not have a corresponding business partner.