Taulia Business Exchange

SAP Add-On

Release Notes
Company sensitive. For official use only.

Last Updated: January 04, 2016

Contents

Release 2.1.3 1
New Features and Enhancements 1
Fixed Issues 4
Release 2.1.2 6
New Features and Enhancements 6
Fixed Issues 11
Release s2.1.1 13
New Features and Enhancements 13
Fixed Issues 17
Upgrade Considerations 19
Release 2.1.0 19
New Features and Enhancements 20
Fixed Issues 23
Release 2.0.8 24
New Features and Enhancements 24
Fixed Issues 30
Release 2.0.7 32
SAP Add­On Component 33
Release 2.0.6 34
Release 2.0.5 34
Release 2.0.4 35
SAP Add­On Component 35
Releases 2.0.3 35
SAP Add­On Component 35
Releases 2.0.2 36
SAP Add­On Component 36
Releases s1.3.121and 2.0.1 36
SAP Add­On Component 36

i
Release 2.1.3
Released to Production November 9, 2015 at 3PM PDT

New Features and Enhancements

The 2.1.3 release of the Taulia SAP Add-On contains the following new features:

Create TED Offered Invoice GIFT Code [SAP-2436]

The Taulia engineering team has identified recommended SAP enhancements to facilitate TED
processing. These code areas are outside the Taulia SAP Add-On and have been researched as part of
good business process and practice. Contact Taulia Customer Success or Professional Services for
information on these areas.

EPASSIGN Improvements [SAP-2607]

Taulia has updated the methods of assigning suppliers to Early Payment groups. The following
functionalities have been adopted into our processes:

l The "Execute" option for the ALV has been moved from the top of the screen, to under the
search fields.
l The Spend and Commitment Data has been removed from the /TAULIA/EPASSIGN view.
l The paying company code statistics have been removed from the /TAULIA/EPASSIGN view,
but are present in the /TAULIA/MONITOR transaction.
l The ALV has been updated to remove fields not commonly used. The fields are still available
for user specific layouts.
l The ALV search criteria has been adjusted to allow for searching by EP group, Enrollment
Status and Payment Methods.
l All background restrictions (for example, if a vendor is blocked) for the ALV search have been
removed.
l An early payment group assignment status has been added to the ALV to provide a visual aid
for confirming that a supplier is in a EP group successfully.
l Suppliers may now be removed from a group by right clicking the group name in the folder
structure.
l Individual suppliers or groups of suppliers may now be invited directly from the EPASSIGN
transaction.

1
 l Quick Transaction Links have been added to the INVITER, EPASSIGN and MONITOR
transactions to facilitate easy movement among the screens for users. Authorization
checks for transactions will be enforced.
l The ALV layout for ENROLLMENT and INVITER has been adjusted to show relevant
fields. The EP Assignment Status and the EP group has also been added to the ALV. All
fields are still available in the background to allow for user specific layouts.

SAP TED Bank Configuration Should Not Be Transportable [SAP-

3109]

Configuration for TED permitted payee and banking will no longer request transport. It is possible
that if a transport is desired, you may still include your configuration entries in a transport.

Send Reminder for Enrollment to a User Email Rather than User ID

[SAP-3184]

Reminders for confirming Taulia enrollment have been enhanced to allow the use of both an
email address as well as a SAP user. Use this configuration to ensure you remember to send
enrollment conformations!

User Exit Point to allow SOD for Inviter and Enrollment Users [SAP-
3185]

A user exit point (DD21) has been created to allow for a further authorization check related to
enrollments. As part of this work, we now also record the user who performs invitation
processing.

Remove SAP Date Validation when the TED EP Comes from the
Platform [SAP-3189]

SAP has relaxed the checks for EP date against the current date for TED invoices. This date is
already checked in the platform and issues have been experienced where a timezone or file
delay issue has caused a failure within SAP for an already approved invoice early payment. This
solution will improve the stability of the Taulia Enhanced Discounting product.

2
POD Work for Purchase Order Custom Attributes & Condition for PO or
PO Item [SAP-3209]

POD has been updated to support custom attributes for Purchase Orders. Support for this feature is at
the header and line level.

POD Work for Vendors Get Custom Attributes [SAP-3210]

POD has been updated to support custom attributes for Vendors. The current solution supports general
custom attributes rather than company code level.

Add User Exit Point to PO Image Program [SAP-3272]

A user exit point (CT85) has been created to allow for management of PO images in relation to the
new PO Image program.

Improve Transaction Links in /TAULIA/MONITOR [SAP-3277]

The ability to "jump" from /TAULIA/MONITOR to /TAULIA/EPASSIGN has been added to the
screen. This is to facilitate movements between these transactions and make it easier for users to
assign suppliers to EP groups. The button will respect user authorizations, so users who do not have
access to /TAULIA/EPASSIGN will not be permitted to access the transaction.

Insufficient Threshold Notification Mail - Create Template for

Notification Mail [SAP-3386]

To facilitate custom requests for emails related to Early Payment thresholds, the configuration for
Early Payment thresholds has been enhanced with a configurable template. A generic template
containing Taulia standards is delivered and can be adjusted as seen fit by the Buyer or consultants.

Improve Layout for INVITER and ENROLLMENT for Early Payment

Groups [SAP-3485]

The default layout for both /TAULIA/ENROLLMENT and /TAULIA/INVITER has been streamlined.
Only those fields that are directly relevant to invitations are now shown. All fields are still available

3
using the standard SAP "adjust layout" functionality if a particular business process requires
additional fields.

Additionally, the ability to view Early Payment group and assignment statuses has been added to
the ALV to facilitate Early Payment Group management. A link has also been provided within the
screen to allow the user to make adjustments to an Early Payment assignment when desired,
without loosing in process invitation work.

Fixed Issues
The 2.1.3 release of the Taulia SAP Add-On contains the following fixed issues:

TED Failures due to Cross Company EP Config [SAP-3104]

When Cross Company EP Groups are active in Taulia SAP configuration, an issue is encountered
during EPASSIGN for TED. The supplier record can not be successfully updated with the banking
information.

With this fix, Cross Company EP groups are fully supported.

Previously Existing Discount Raises During EP Assign [SAP-3107]

Previously, a notification to the user indicated that a supplier being transferred to a group had a
previous traditional discount. This message does not facilitate the Taulia process and may lead a
user to not assign a supplier to an EP group, when it is permissible and does not negatively
impact downstream processes. It is highly preferable for all suppliers to be placed in an EP group.
Therefore, if a single invoice is a NET term invoice, it will be offered for Early Payment.

Incorrect VAT Tax Displayed for Invoice - Pfizer [SAP-3200]

Incorrect VAT tax amount was displayed on invoices if debit and credit lines are posted in BSET
table for a given document and the respective tax code is not self-assessed. This solution resolves
this issue.

Configuration Code Allows BUSDOC_OUT to Erroneously Transfer

Same PO Image Twice and Portal Sends Back Two Confirmations
Messing POD Log Entries [SAP-3271]

4
When multiple configuration lines are set up in table /taulia/std_xfer, PO images might be
unnecessarily transferred more than once for the same document. This also causes the BUSDOC_CNF
POD job to log unnecessary error messages.

Discount is Rounded Up on JPY and Does Not Use Internal Number

Correctly [SAP-3282]

In instances where the currency is Japanese yen (JPY) there is a mismatch in formatting of the
currency. JPY is an example of currency where there are no fractions of the currency.

Note that even after this fix it is possible that the discount amount may not match the Taulia
platform if configuration settings in transaction OY04 does not match with real world currencies. It
is recommended that these settings be reviewed. (Traditional SAP systems should come with this
configured, however older systems or in any case where a customer may have deleted these table
contents, an update may be needed).

For example, Japanese Yen has no fraction amounts (1.00, 2.00, 5.00 are valid Yens but 1.50, 2.35,
8.99 are not valid Yens). If a customer decides to allow fractional Yens in SAP, the discount amount
will never match.

Short Dumps in the DPT OFFER DATA CHANGE Job [SAP-3308]

The DPT OFFER UPDATE job short dumps when an entry exists in table /TAULIA/TDPT_UPD but no
corresponding entry is found in /TAULIA/DD_TACT. This fix adjusts the program to accommodate
the scenario.

Configuration for Vendor Email Address Handling - Request to Support

Multiple Company Codes [SAP-3309]

The configuration activity "Configure for vendor email address handling," directly accessed by
/TAULIA/CVNDEML, has been altered to allow for multiple company code email address updates.
This configuration allows for outbound email configuration as well as inbound email configuration.
Previously, a company code was a required field. This has been changed so that the presence of a
company code field only indicates that company code clerks internet address shall be updated for
inbound requests. If the company code field is left blank, all company codes will be updated for the
vendor master for inbound requests. Vendor specific exceptions can be maintained.

5
 This configuration should be reviewed during system upgrades to ensure appropriate email
management.

Create Duplicate Checker in PO, INV_OUT and PAYMENT RFC's [SAP-

3414]

Taulia re-transfers documents based upon enrollment, change, re-transfer request, and other
factors. It is possible that the same document could be transferred to the platform within the
same batch. If this happens, the digital signature in the platform is harmed. To resolve this, a
duplicate check has been incorporated to remove redundant data.

Vendor Selection in RFC - Improve Data Selection [SAP-3444]

The following Vendor Selection issues were addressed to improve the collection of vendor master
issues:

l Vendor Master data was not being fully transferred if the number of new invitations
performed in transaction /TAULIA/INVITER exceeds batch size.
l Batch size was not being respected in certain scenarios when too many records in table
/TAULIA/DD_TNROL didn't have field SENT_TO_VEND_AT updated.

Release 2.1.2
Released to Production September 8, 2015 at 3PM PDT

New Features and Enhancements

The 2.1.2 release of the Taulia SAP Add-On contains the following new features:

6
Currency Not Configured, TED Invoice is not Offered for Early Payment
[SAP-1707]

This is an improvement for TED processing. If an invoice currency does not have a TED bank account
configured in the same currency, the invoice will not be offered for early payment.

Supplier Spend Report [SAP-2160]

The transaction /TAULIA/SUPP_SPEND has been created to allow the Taulia Value Enablement
team and the teams at our buyers to review spend across date ranges for suppliers at the currency
and company code level.

PO Images are Transferred for POs Subjected to a Release Strategy

[SAP-2338]

Updates have been made to purchase order (PO) image delivery. If a PO is subjected to a release
strategy, but has not yet been released, the PO image transfer will not respect the release strategy
status.

Code Improvement in Partner Solution for BSIK and BSAK Checks [SAP-

2425]

Performance improvements have been made in data selection for any customers running a third-
party AP automation solution. These improvements reduce processing time related to the selection of
payment data.

Authorization Check for /TAULIA/BS_MASS_MESS [SAP-2484]

The transaction /TAULIA/BS_MASS_MESS may now be managed using Taulia functional

authorization ZTAU_MBUK.

Authorization Check for /TAULIA/MONITOR [SAP-2485]

The transaction /TAULIA/MONITOR may now be managed using Taulia functional authorization
ZTAU_RBUK.

7
Authorization Check for /TAULIA/TR_PAST [SAP-2487]

The transaction /TAULIA/TR_PAST may now be managed using Taulia functional authorization
ZTAU_RBUK.

Authorization Check for /TAULIA/TR_FUTURE [SAP-2488]

The transaction /TAULIA/TR_FUTURE may now be managed using Taulia functional

authorization ZTAU_RBUK.

Authorization Check for /TAULIA/EP_REPORT [SAP-2489]

The transaction /TAULIA/EP_REPORT may now be managed using Taulia functional

authorization ZTAU_RBUK.

EP_CHECK Lists Every Open TED EP That has Not Been Paid [SAP-
2492]

Background checks for dynamic discounting payments have been improved. A notification now
appears only if the invoice is due to the funder at the net due date and the funder has not yet
paid the invoice to the supplier. Previously, TED invoices would indicate that they had not been
paid during the dates between funder payment to the supplier and the buyer's payment to the
funder. This was confusing as it indicated that the invoice hadn't been paid when, in reality, it
had been paid but the buyer had not yet paid the funder. These misleading messages have been
removed.

8
TED Multiple Bank Account Early Payment Accepting in SAP [SAP-2653]

This update lets invoices that are associated with at least one TED-funder bank account to become
eligible for Early Payments. Typically, all funder bank accounts would be associated with the
supplier.

This update prevents a situation where the buyer invokes a manual data update and could potentially
miss one of the associated TED-funder bank account.

New Configuration Entry for Early Payment Request Status [SAP-2741]

A new Business Action in configuration, TED Early Payment (EP) Request, has been created. The
TED EP Request lets buyers know if an EP has been requested for a TED invoice so that the buyer does
not make any changes to that invoice. This business action must be enabled on the Taulia platform
at the buyer level. The action must be configured and a function module developed to describe how
the action should be handled.

Populate Original Vendor Term Table from DPT_PREP [SAP-2797]

For suppliers who have not previously had interaction with Taulia in the buyer SAP system, DPT_
PREP now facilitates recording the supplier's original supplier term. In the event that the supplier

9
term is defaulted to a DPT, you may see a message indicating that the original term has not been
recorded. In this case, use /TAULIA/BILL_STAT to record the term for the supplier.

Create Transaction Code /TAULIA/BILL_STAT for Exception Original

Term Updates [SAP-2798]

The Taulia invitation process now records the supplier payment term at the time of invitation.
There are cases where this term may not be recorded (if it was missing, in error, or was
inadvertently set to a DPT). In these cases, the transaction /TAULIA/BILL_STAT has been
created to allow the buyer to accurately record the original term of the supplier.

Due to the limited use of this transaction code (tcode), it has not been added to a
functional authorization role. At a buyer, the SAP security team must add this transaction
directly to the user if applicable.

Change DPT Prep and Check Payment Date to Less Than or Equal To
[SAP-2858]

Previously, if a vendor was paid in a payment run that was run early in the day, the DPT jobs
would advance the due date of the invoice and the relevant discount to the following payment
day (assuming that the invoice missed its payment run). The logic has been adjusted to not make
this assumption. If the invoice is not paid at the end of the day, then it will be advanced to the
following day.

Conversion Program for Upgrades [SAP-2919]

The Taulia invitation process will now record the supplier payment term at the time of
invitation. For any buyers upgrading to a new version of Taulia Business Exchange, it is necessary
to record the term for past suppliers. In these cases, the transaction /TAULIA/CONV_OTERM
has been created to allow the buyer to accurately record the original term of the supplier.

Due to the limited use of this tcode, it has not been added to a functional authorization
role. At a buyer, the SAP security team must add this transaction directly to the user if
applicable.

10
Make the POD Process BUSDOC_OUT searchable by PO Number [SAP-
2970]

SAP users who regularly utilize /TAULIA/POD will have improved functionality for searching PO
images. Previously, the BUSDOC_OUT did not support this granular search. This has been improved.

Enable Search Results from /TAULIA/POD Processes to be Filtered

Through Most Recent Time Intervals [SAP-2971]

A new field has been created for the /TAULIA/POD transaction to limit activity to the most recent
user defined minutes. For users who have a defaulted variant view, Taulia recommends updating
your view. The default for users entering the transaction is the last 30 min.

Fixed Issues
The 2.1.2 release of the Taulia SAP Add-On contains the following fixed issues:

Supplier Spend - Run Very Long and Got Shot Dump [SAP-1702]

This program calculates Supplier Spend only for those invoice documents which are defined as
invoices in Taulia Configuration.

Data Model Issue - Tables/Taulia/DD_CDPTP and /Taulia/DD_CSCFG

[SAP-1915]

/TAULIA/DD_CDPTP and /TAULIA/DD_CSCFG are now manual cutover tasks. These transactions
are leveraged for defining Early Payment Group in each environment.

Invoice Data with Incorrect Workflow ID [SAP-2431]

A change to the logic has been made when retrieving FI/MM document data from the ReadSoft
cockpit. In instances where the FI and MM document number range is the same, the wrong document
was being derived.

Supplier Bank Changes Fail to Update in the Portal and XK02 [SAP-
2661]

11
In a case where there is inconsistent bank information on a supplier master record in SAP, TED
invoices were not sent as "TED" eligible. The checks around this has been strengthened.

Additionally, inconsistencies in bank information are recorded in ED_RECONCILE.

Incorrect Invoiced Amount in Purchase Order [SAP-2683]

The invoiced value for purchase orders was overstated in specific tax procedure configurations.

Down Payment clearing "Payment" not Transferred with Pay Delay

[SAP-2685]

In specific scenarios where payment delay takes a long time and POD frequency is very rapid,
the payments were not sent to the Taulia platform.

PO Images are Transferred to the Portal for Suppliers not Invited to

Taulia [SAP-2763]

Previously, PO images were being sent for all suppliers rather than just the suppliers invited to
Taulia. This has been resolved.

Short Dump in EPASSIGN Program while Changing Paying Company

Code [SAP-2793]

Resolved a message handling issue in /TAULIA/EPASSIGN when EP groups are not yet defined
for the client.

Invoiced Amount is Incorrect in PO-Pfizer [SAP-2958]

Resolved an error where credit notes are added incorrectly in the PO invoiced value.

Early Payment Discount Posted as Credit Note with Multiple Taxes

[SAP-3043]

Early Payment requests follow configuration in /TAULIA/DD_CPAY. For instances where the
discount configuration is to create a credit note and the original invoice contained multiple tax
codes, the credit was incorrectly leveraging only the first tax code. Logic has been added to
proportionately distribute the discount amount across the tax codes.

12
DD Posting as CR - Commit Issue [SAP-3046]

Early Payment requests follow configuration in /TAULIA/DD_CPAY. For instances where the
discount posting configuration is to create a credit note, failures in the credit note creation resulted
in an incorrect, immediate pay invoice. Further processing has been added to revert the invoice to
the original status if the credit note creation fails and additional messages will be shown in the POD
monitor to facilitate diagnosing the error.

UE VM01 Change Importring Parameter to Changing Parameter [SAP-

3059]

Update to VIM Integration. This fix is only applicable to buyers using VIM AP solution. Existing
implementations of UE VM01 should be reviewed and migrated to use the new CHANGING parameters
if any of the old EXPORTING parameters were used to pass data back to the caller. Data passed back
through the EXPORTING parameters will no longer be used by the caller. Should also re-create UE
from updated template FM.

Release s2.1.1
Released to Production May 13, 2015 3PM PDT

New Features and Enhancements

The 2.1.1 release of the Taulia SAP Add­On contains the following new features:

Down Payment Request Display [SAP­2043]

Businesses processes for down payments require significantly further processing within SAP to post
and communicate to suppliers. Taulia Business Exchange can now facilitate the display of Down
Payment Requests to your suppliers based upon Company Code, Document Type, and Special G/L
indicator. Documents will show as invoices to the supplier so that they may reconcile down payment
requests. Taulia also supports a display of the liquidation/clearing of the down payment request with
the material invoice. For added flexibility, Taulia offers the ability to show a summary of these
invoice values in the PO display.

Accounts Receivable clearing with supplier payments [SAP­1896]

13
SAP standard processing permits the linkage of vendor and customer master records for use in
consolidated clearing. Taulia Business Exchange now offers the ability to enable the display of
customer invoice & credit documents within the supplier's account in the Taulia Supplier Portal.
This allows you to communicate a holistic view to your supplier covering all transactions for
their account.

For more configuration and implementation information, see the SAP Configuration Guide.

New exit to associate a vendor with a customer record [SAP­2099]

A new user­exit CT84 has been added to map suppliers to customer numbers. The goal behind this
user­exit is to identify suppliers of Accounts Receivable documents that are being sent to the
platform.

New and complete messaging for invoices that were not offered
early payment [SAP­2181]

Additional messaging is now provided when an invoice is not offered for early payment. In
previous releases, the message were incomplete. The long version of the new message provides
recommended actions to  take.

Mandatory system setting for ERP identifier [SAP­1936]

There is a new configuration transaction to define a name for the Client­ID. This is intended for
deployments in which a buyer company has multiple SAP and non­SAP connectors communicating
with the Taulia Platform. Even if you are not using multiple ERP systems, this setting will be
required in the future. The setting is located under Taulia Configuration (/TAULIA/CONFIG) >
General Settings > Basis Settings > Setup the Taulia System Id:

14
The field accepts an 8 character customer name and should be meaningful to identify your system

Do not change this configuration once initially set without conferring with Taulia Support.

This field must be set before you start the POD.

High liquidity limit caused dump [SAP­1872]

The allowable values Liquidity Settings have been shortened. Before you upgrade to the version 2.1.1
or later, you must reduce the entry in this field to avoid a shortdump.

For example, If you put a value of 999,999,999,999,999.00 in the liquidity limit (today and next
day), you will see a dump with the EP job runs. This value should be restricted to 9,999,999,999.00
to avoid the dumps when disabling the liquidity check.  Change the values in the following  dialogs:

l /TAULIA/DD_CSCFM­
DEF_DAILY_LIMIT
l /TAULIA/DD_CSCFM­
TOMORROW_LIMIT
l /TAULIA/DD_CSCFG­
SCF_LIMIT_MAX

For example:

15
Custom Fields Max Size increased to 255 characters [SAP­1820]

The custom value fields have been extended to support 255 character length for incoming
invoices. This can be updated in the Max Size column in Taulia Custom Fields
(/TAULIA/CCUSTF):

New messages displayed for invoices that are not offered Early
Payment [SAP­1809]

When an invoice is not offered for Early Payment, a dialog box containing the reason is now
displayed when viewing invoice status from the GOS menu. In addition, the
/TAULIA/OPTIMIZER report will also display this information.

For example:

16
EP Assign lockout notification easier to locate [SAP­1752]

In EP Assign ( /TAULIA/EPASSIGN), if the transaction is currently locked by another user, you will
now receive a message indicating who has the transaction locked. This was previously at the bottom
of the screen and it has been moved to make it easier to locate.

Fixed Issues
The 2.1.1 release of the Taulia SAP Add­On contains the following fixed issues:

EP offers before the cliff based on company code were unsuccessful

[SAP­2349]

A regression issue was fixed in which Early Payment Offers before the Cliff for DPT terms were not
successful when the configuration was company­code specific.

l Double clicking a field in a message no longer sends message [SAP­2178] In the Taulia Message
Board (/TAULIA/MSG), if you opened a message and double clicked on any field besides the
message body, the message would incorrectly send. This no longer occurs, as only clicking the

17
 Send Message icon will send the message.
For example:

l Incorrect parameter data type no longer causes short dump [SAP­2121] An incorrect
parameter data type no longer results in a short dump when running T­c ode /TAULIA/TR_
PAST.

Line item amounts with credits did not transfer correctly [SAP­1880]

For invoices posted with both debit and credit lines, the amounts sent to the portal for the total
value and line items were not represented properly because the debit/credit indicator was not
respected. This has been corrected to add or subtract the values according to the debit/credit
indicators.

Tax value is not displayed on PO invoiced value SAP­1855]

When sending PO data to the portal, Taulia might also display the invoiced value related to the
PO. An issue was found in which the PO invoiced value may appear incorrectly based on various
tax posting procedures, such as if it is posted on a separate line or the if the tax code is self
assessed. This fix resolves the summary of the PO invoiced value.

18
Taxes for both debits and credits now correctly considered [SAP­1181]

For taxable invoices, SAP taxes might be posted as both debits and credit based on the business
process. Taulia now appropriately considers debit and credit indicators for the summing the tax
value when transmitting the invoice value to the portal.

Upgrade Considerations
If you are upgrading from a previous release of the SAP Add­On to this version, it is important to be
aware of the issues described in this section. They could affect your upgrade procedures. For more
information about upgrading the SAP Add­On, contact your Taulia program manager and request the
Taulia SAP Add­On Upgrade Guide.

Custom fields not viewable in the RFC data dump [SAP­2312]

If you are upgrading your SAP Add­On and you leverage custom fields on the invoices or PO get, the
values will not be viewable in the RFC data dump for historical data. This only applies to these
custom field, and this is only a limitation to the RFC data dump and does not affect processing. This
was an accepted consequence to avoid disrupting in place user exits and avoid data disruption.

High liquidity limit caused dump [SAP­1872]

See SAP­1872 in the Fixed Issues section for more information.

Must set the Client ID header before you start the POD [SAP­1936]

As part of the upgrade process, it is recommended that you complete a fresh install of the POD. It is
important to note that you MUST have the Client ID set in the SAP Add­On before you restart the POD.
For more information, see:

l The release note SAP­1936 in the Ne w F e a t ur es section

l The Taulia SAP Add­On Upgrade Guide

Release 2.1.0
Released to Production February 18th, 2015 at 3PM PDT

19
 Taulia did not release a 2.0.9 version of the SAP Add­On.

New Features and Enhancements

The 2.1.0 release of the Taulia SAP Add­On has the following new features:

New configuration to maintain text IDs (item and header) [SAP­

1665]

In previous releases, all of the PO texts IDs (item and header) were sent to the Taulia Platform
and no filter was applied to them. This could have caused the PO job to never finish successfully
in SAP and the SAP Add­On would have repeatedly attempted to send the same POs.

In this release, Taulia provides a configuration in which you can set which text IDs should be sent
to the Taulia Platform. You configure this information under Taulia Configuration > Taulia
Connect > Purchase Order transfer > Setup Purchase Order Text Transfer:

Add the company codes, the item text location (TxtSrc), and the SAP Txt ID to be transferred.
If you want to map the text ID to an alternate portal text ID, populate that ID in the Portal ID
field. If the Portal ID is not defined, the SAP text ID will be transferred as the portal text ID.  You

20
can leave the Company Code field blank to make the configuration apply to all company codes. If
you do not define any entries in this transaction, all available text IDs will be attached to a purchase
order that is being passed to the portal.

Vendor Master can now be created “manually” in the Vendor Master

Cockpit [SAP­1796]

The SAP Add­On now allows you to send the vendor number to the portal to associate the SAP vendor
record with the Supplier Launch user on the Taulia Platform.

In previous releases, certain circumstances could have prevented the supplier record to be linked
with the user record that was created during the Supplier Launch when the vendor was manually
created in the Vendor Master Cockpit.

Improved performance for /TAULIA/INVITER and TAULIA/ENROLLMENT

[SAP­1772]

Performance improvements have been made to Application Log window for the supplier invitation
(/TAULIA/INVITER) and supplier enrollment (TAULIA/ENROLLMENT) processes.

Approve Me Now report email improvements [SAP­1705]

In the Approve Me Now program (/TAULIA/DD_APPROVE_ME_NOW), the following enhancements

have been made to the Email Approver functionality:

l When you enter a value in the Approver field, and then either submit it, or cancel it and then
select another entry for Email Approver, the field in the dialog box is cleared. The exception
to this is if the value is invalid. In this case, an error message is displayed and the value
remains so that you can correct it. In earlier releases, the original value would persist.

21
 Multiple Email To Approver dialog boxes are no longer erroneously displayed.
l Double clicking on the Subject heading or the Subject field no longer sends the email. The
send email button (bottom right) will complete the send action.

l The Approver field now has the proper search help.

l The acknowledgement message for a successfully sent email is now displayed on the
bottom of the screen.

Self-assessed tax codes are now used for invoiced value [SAP­1572]

22
The configuration for self-assessed tax codes are now used when calculating the Invoiced Value for
POs, in addition to the existing functionality of calculating the tax values the Invoice Header.

Self-assessed tax codes are defined under Taulia Connect > Outgoing Documents Transfers > Self
Assessment Tax codes (/TAULIA/CT_CTAXO).

Fixed Issues
The following issues have been fixed in the 2.1.0  release:

Company Code Selection removed in Vendor Master Cockpit [SAP­

1744]

23
In the Vendor Master Cockpit (/TAULIA/MASTER), the Company Code field has been removed
from the selection criteria, because the rest of the information in this screen was specific to a
company code. In previous releases, this field was located just above the Vendor file.

Release 2.0.8
Released to Production December 21st, 2014 at 3PM PDT

New Features and Enhancements

The 2.0.8 release of the Taulia SAP Add­On contains the following new features:

New output type-based PO image transfer option [SAP­938]

PO image transferring allows you to transfer an image of your PO in a specific format from SAP
to the Taulia Platform. This allows your suppliers to be able to view or obtain an image of the PO
from the Supplier Portal that is formatted to their specific needs, directly from the PO data
created in SAP.

24
In this release of the SAP Add­On, a new PO image transfer option has been added to the currently
existing Document­
based output type. The new Output­
based image transfer relies on existing
output types (that is, PO message type) to extract and use for the generation of document images.

The following steps describe the basic workflow to configure image transferring. Note that the
configuration options are located in Taulia Configuration (/TAULIA/CONFIG) under Taulia Connect
> Outgoing Document Transfers > Define image transfer:

1. Configure the type of PO image document type under Set document image transfer type
method (n/TAULIA/IMG_XFER).
2. Configure the default values for the output type under Set default values for output­based image
transfer (n/TAULIA/DEF_XFER).
These values are used to maintain the output types that will be used by the SAP Add­On. These
values can be either new Taulia­specific output types or existing output types that are copied
over to be Taulia­specific.
3. Set the relative priority for transferring documents from SAP to the Taulia Platform under Set
output types for standard image transfer (n/TAULIA/STED_XFER).
4. Configure all trigger points that need an output type assigned so that the images are retrieved
and sent to the Taulia Platform.
This is located under Set trigger points for image transfer (n/TAULIA/TRIGXFER).

For configuration information, see the SAP Add­On Configuration Guide.

25
Handling attachments for new PO Image functionality [SAP­1500]

As part of the image transferring, you can use attachment handling to transfer attachments for
business objects. This configuration acts as a framework in which you can provide a function
module that can be specified to handle the retrieving and formatting of the attachment.
Attachments can be linked to source documents through any standard SAP-supported methods,
such as:

l ArchiveLink
l GOS (Generic Object Services) attachments
l DMS (Document Management System)
l KPRO (Knowledge Provider)

The configuration options are located under Taulia Configuration.

(n/TAULIA/CONFIG) > Taulia Connect > Outgoing Document Transfers > Configure
attachment handling. 

For example:

For usage information, see the SAP Add­On Configuration Guide.

Configuration options to prevent Closed POs upon supplier enrollment­[SAP­480] appear Under
Taulia Configuration (n/TAULIA/CONFIG) > General Settings > Basic settings > Activate
General Taulia Switches, you can set the SKIP_CLS_PO_NROL_ON switch to disable the
sending of historical Closed POs to the Taulia Portal during the enrollment of a supplier. New or
Changed POs are still sent with this option enabled.

26
Extended message notifications [SAP­1379]

There is a new configuration for extended message notifications under Taulia Configuration
(n/TAULIA/CONFIG) under Taulia Connect > Incoming and outgoing messages > Extended
notifications.

This configuration allows extended notifications to be sent when certain Taulia messages are
triggered. For configuration and usage information, see the SAP Add­On Configuration Guide.

Penny Invoice references removed for un­enrolled customers [SAP­1497]

References and buttons that configure Penny Invoice test functions  in /TAULIA/MASTER have been
removed for users that are not configured to use the Penny Invoice feature.

Early payments available for DPT during cliff period [SAP­1683]

Early payment is now available when a DPT (Dynamic Payment Terms) invoice is approved on the
cliff. For example, assume the following scenario:

l An invoice is set to Dynamic Payment Terms: 2% 10 Days NET 30 – ASAP

l The supplier’s invoice is approved on Day Two

27
In this 2.0.8 release, your supplier is now able to request an early payment between Day three
and Day nine using the Pay Me Early button on the Supplier Portal. The discount percentage will
follow the upper line on the graph above.

Before the 2.0.8 release, the supplier was paid automatically on day 10 with 2% discount without
the option to get paid earlier.

This functionality is enabled for DPT, defined with a underlined SAP terms configured the
same way (DPT: 2% 10 days, net 30 ASAP and underlined SAP terms: 2% 10 days, net 30).
It will be released for all DPT in the next  release.

Email address updates in /TAULIA/INVITER [SAP­1618]

The Invitation and Enrollment table under /TUALIA/INVITER has the following enhancements:

l The email column name has been changed from Clerk’s internet address to E­mail
Address.

28
 l A new column has been added, named E­mail Source. It reports one of the following values:
l C Clerk’s internet address
l S SMPT_ADDR
l N Notes
l M Manual
l The SAP Add­On will select an email address from one of the values above (Clerk’s address,
SMPT_ADDR, and so forth) and is used to populate the new E­mail Source field. This will be
the email that is used to invite the supplier.

EPASSIGN allows suppliers with Purchasing Blocks [SAP­1672]

Once enabled, suppliers with Purchasing Block (LFA1­

SPERM) will be available for EPASSIGN
selection. To allow this functionality, go to Taulia Configuration (n/TAULIA/CONFIG) > General
Settings > Basic settings > Activate General Taulia Switches, and enable the VEND_ALW_PURCH_
BLCK switch.

New Reference column for Taulia Message Board [SAP­1538]

In the Taulia Message Board (/n/TAULIA/MSG), you can now add the Reference column to be
displayed. The reference code allows you to locate a particular message by a reference number.

To add this column:

1. Select Change Layout from the layout menu.

29
 2. Locate the Reference in the Column Set list and add it to the Displayed Columns list.

Taulia determines Invoicing Party code [SAP­1634]

The SAP Add­On now determines the invoicing party based on the internal partner function code,
RS.

Column name change in the Tauila Job Scheduler [SAP­1675]

In the Taulia Job Scheduler (/TAULIA/JOB_SCHEDULE), the ServerName column has been
renamed to Background Server.

Fixed Issues
The following issues have been fixed in the 2.0.8  release:

Performance improvement for Invite Suppliers and Enrollment [SAP­

1677]

There have been several improvements made to enhance performance to the Invite suppliers
action and the confirmation action pop­up dialog box that is displayed after the Invite suppliers
action is completed. In addition, there is a noticeable improvement in the performance of Taulia
Enrollment (/n/TAULIA/ENROLLMENT).

30
 l Fixed runtime errors in TAULIA/MONITOR and TAULIA/EPASSIGN [SAP­1612] Several issues
have been fixed that could have resulted in shortdumps or runtime errors on the following:
l In TAULIA/MONITOR by incoming EP invoices.
l In TAULIA/EPASSIGN if there were suppliers across multiple Early Payment groups that
requested early payments after the transfer.
l Several issues have been fixed that could have resulted in short dumps or runtime errors on
TAULIA/MONITOR for incoming EP invoices or on TAULIA/EPASSIGN after the suppliers
transferred across multiple EP groups and requested early payments after the transfer.

Early Payment Group Reporting displays correct values [SAP­1611]

Under Taulia Reporting (/TAULIA/EP_REPORTING) > Early Payments and Dynamic Payment term
usage > Group Reporting, the currency of group is now displayed, the currency and summed
amounts are correctly reported /TAU/CONV.

Vendors with multiple TaxID types no longer produce error [SAP­1605] An issue is fixed in which the
following error was reported in the display log: TaxId type GST country US vendor found but not
mapped. This message may have occurred if a vendor had multiple, valid TaxId types.

Posting period no longer reported incorrectly [SAP­1590]

Fixed an issue in which an error was produced because there was a posting period check using the
month as the posting period. The error that was reported was similar to the following:

l No period is open for period 7 until period 12 of year 2014.

Calculate Send for EP Groups option now displays for valid company
codes [SAP­1586]

Fixed an issue with the Calculate Spend for EP Groups checkbox in the Paying Company Code pop­up
in the /n/TAULIA/EPASSIGN transaction.

In previous releases, if a paying company code was entered that did not have early payments
configured, an error message was displayed. When a valid company code was subsequently entered,
the Calculate Spend for EP Groups checkbox would display, but the checkbox was not actionable
(grayed out) . The checkbox can now be selected.   For example:

31
Fixed short dump during SPEND calculation [SAP­1585]

Fixed an issue in which a short dump would occur in SPEND analysis calculation when the total
amount was larger than maximum standard amount  fields.

NON­PO invoices no longer rejected with purchasing blocking [SAP­

1534]

For suppliers that are Non­PO only (the supplier is not associated with a purchasing organization),
Taulia no longer rejects Non­PO invoices from that supplier even if you have applied a purchasing
block for the supplier.

Attachment pop­up in the Vendor Master Cockpit would not close [SAP­1494] When the
attachments button in the Vendor Master Cockpit was clicked and multiple attachments were
included, a popup was displayed with a list of all the files. This pop­up would continue to display,
even if you attempted to close it. This no longer occurs. To access the Vendor Master Cockpit,
navigate to the Taulia Add­On Menu Tree (/n/TA/1).

Under Vendor Communication, select the Monitor master data and bank changes option.

Release 2.0.7
Released to Production September 9th, 2014 at 3PM PDT

32
SAP Add­On Component

l Developed a test tool for testing ASN (Advance Shipment Notice). This tool supports:
l ASN number
l Bill of Lading
l Carrier
l Shipping date
l Expected arrival date
l Ship From
l Ship To
l Line item quantity fields.
This test tool can be used to test the ASN functionality as provided in the supplier
portal.
l Developed a test tool for testing PO confirmation. This tool supports confirmation of line item
quantity, and line item delivery date. As above, this tool can be used to test PO Confirmation
functionality as provided in the supplier portal.
l Error fixed in Supplier Dashboard (trx /TAULIA/SUPPLIER) so that user can navigate to the
right Early Payment group by clicking on the hot­link in the ALV.
l Error fixed during vendor enrollment in the following cases:
l Vendor is invited (confirmed in /taulia/inviter), but has not yet enrolled and a
DPT campaign has been initiated (through /taulia/dpt_offer) to extend their
terms.
l Vendor is not yet invited (and has therefore not enrolled) and a DPT campaign has been
initiated (through /taulia/dpt_offer) to extend their terms.
l Improvement performance so we now send DPT offers only to selected vendors (based on line
selection on the screen) rather than to all vendors.
l Improved performance of /TAULIA/EPASSIGN, by executing query to calculate spend of EP
groups only if the user wants that level of detail.
l Enhanced supplier launch to support externally managed number ranges for supplier as well as
provide adhoc assignment of Account group for these suppliers.
l New config under Taulia Connect > Master data cockpit > Configure additional data
default value for new vendor request
l Provided the right error message when adding a Notification recipient in /TAULIA/CT_
CMSGN.
This error message relates to inputting the language which is now a mandatory field.

33
Release 2.0.6
Released to Production June 5th, 2014 at 3 PM PDT

SAP Add­On Component

l Developed a test tool in SAP Add­On for Invoice Creation.

The tool supports comments fields, which makes the test tool support all functionalities as
on the portal.
l Fixed a bug to support APRs with more than 4 digits for Enhanced Payment Terms
l Fixed an bug that locked vendor objects before updating the vendor master data
l GOS messages for PO/Invoices shows messages that are related to that object
previously they were showing all messages related to that supplier
l Ensure that data for vendors with bank accounts as IBAN in /XK03 will be updated
correctly while executing a vendor master change

Release 2.0.5
Released to Production May 22nd, 2014 at 3 PM PDT

SAP Add­On Component

l When a supplier submitted ASN (Advance Shipment Notification) fails in SAP, a success
messages was sent incorrectly to the Portal.
With this fix, the ASN shows up as "Error" status and with the submitted amount still
remaining open for ASN.
l When a supplier deletes a Tax Id on the portal, the Tax Id was not being deleted in SAP
vendor master.
This issue has been fixed, ensuring that the supplier information on the Portal and in SAP
remain consistent.
l Messages sent to the supplier can now contain a hyper­text URL that will show up as a link
for the supplier on the Portal.
l To fully make use of the bi­directional feature on the portal, the vendor information is re­
transferred when a VMC change is rejected so the supplier will still see the information
that the buyer has in SAP. This is controlled by a Admin Config (Switch > VMC_XFROFF).
l Traffic lights icon in VMC would show incorrect status if a supplier made multiple changes
to any vendor master attribute (for example, address). Since the subsequent changes by

34
 the supplier override the earlier changes, the icons have now been fixed to show the correct
status.
l Users can now filter messages in the Message Board by "Purchasing Group". This helps users
retrieve the right messages based on Purchasing Group.
l Ability to add Company Code to Supplier Launch. An Add button is available in the Company
Code data tab the vendor administrator can click on the Add button, select from the list of
the company code.
l Added a new selection parameter to TAULIA/INVITER for “Creation Date” of the vendor.
This parameter will allow buyers to restrict the invitation list to suppliers that were newly
created in SAP.

Release 2.0.4
Released to Production on March 27th, 2014 at 3 PM PDT

SAP Add­On Component

l Supplier can add comments to an invoice submitted through the portal. We created a
configuration where a customer can decide if the supplier comment on an invoice should be
converted into a "note" that is "attached" to the FB60 / MIRO posting ("on the note tab")
(Taulia Configuration,­Taulia Connect,­Incoming invoices, and­Assign text id for supplier
comments on submitted invoices.)
l Fixed an issue related to multiple tax lines/rates and calculation of tax value in that scenario.
l If a PO has no relevant message issued (print, fax), no PO image is generated to be submitted
to the portal. With this change, those POs are excluded from being transferred thereby
preventing unnecessary error message creation.

Releases 2.0.3
Released to Production on February 28rd, 2014 at 3 PM PDT

SAP Add­On Component

l In certain scenarios, the PO status was not getting updated correctly. This would cause an
incorrect PO status to be shown to the supplier thereby causing confusion. This fix ensures PO
statuses are updated correctly.

35
 l Suppliers have the ability to reply to system messages. However customers could not reply
to them in the Message board. With this enhancement, customers can view these message
easily and can reply back to them.
l Improved the email validation done on the supplier email address used for the enrollment
emails. This helps detect mistakes upfront with email addresses.

Releases 2.0.2
Released to Production pn February 4th, 2014  at 3 PM PDT

SAP Add­On Component

l Delivery address and company code field structures have been increased to accommodate
larger data strings.
l Better visibility to /taulia/sys_refresh. It allows a customer to "wipe" (refresh) Taulia data
from the tables in a QA system from production and also allows to to reset the Taulia add­
on data for new testing in QA.
l Before this fix, cross company clearing documents were not sent from SAP. This issue only
appeared when the buyer's SAP system is set up to use the same document type for sending
and paying company codes in a cross company clearing scenario. Now all documents are
sent from SAP.
l Unconfirmed company codes and invoices being incorrectly sent to portal. This root cause
was identified and the issue fixed.

Releases s1.3.121and 2.0.1

Released to Production on September 17th, 2013 January 6th, 2014 at 3 PM PDT

SAP Add­On Component

l Transaction related improvements:

l Changes to ensure that special ledger line items posted against the vendor are
handled correctly
l Handle failure of PO image creation graciously
l Extend GAP functionality for changed workflow documents
l Ability to create custom field in the add­on at either header level or line item level
for the Invoice document

36
 l Ability to configure field as mandatory/optional with help text appearing to supplier
user on the portal
l Ability to configure both Credit and Debit type of special charges that get posted
correctly with the invoice document
l Fixed issues around PO line count
l Message Board Improvements:
l Improve user experience for viewing and responding to email message
l Ability to assign messages to another user shows message as unread for the assignee
l Ability to search for assignee based on name and address
l Bug fixes related to display of messages
l EP/DD/SCF:
l Ability to configure the funder as a permitted payee so payments can be re­routed to
the funder instead of supplier when using SCF
l VMC changes:
l Support custom workflow for vendor master cockpit
l Automatically retransfer vendor master when VMC change is rejected
l Efficiency/Performance:
l Data sizing tool to provides data storage estimates
l Ability to purge RFC diagnostic data
l Export RFC data to excel for analysis
l Central background job management

37