SAP PCMA Releases

New Features

N/A

Problems Addressed

Fixed errors when you import transports (as you upgrade) from ECC to S/4 Hana

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

N/A

Problems Addressed

• Override percentage field was not editable in the new ALV layout for Single and Multi-Customer Open AR.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

N/A

Problems Addressed

• RFC Connection Short Dump: If an RFC connection was down, any program that performs an RFC ping prior to running was resulting in a short dump if email address was not maintained in the RFC Connection Status program. An error message now displays.

• Auto AR: Changes were made to improve performance when processing large volumes.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

Stored Credentials

Added support for handling CIT/MIT message type for the stored credentials transaction framework mandates to streamline implementation within SAP.

Standardize Report Messaging

Made the no results message of the following reports consistent with other reports by providing a pop-up indicating no data found that matches selection criteria.

• Expiring Payment Card Authorizations

• Multi-capture Authorizations

• Payment Card Worklist

• Reauth & Release Billing documents

Problems Addressed

N/A

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

N/A

Problems Addressed

Web AR and echeck: Changes were made to ensure tokenized echeck details are updated in FPLTC and BSEGC.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

N/A

Problems Addressed

Open AR and Partial Payments: ALV not displaying properly when 'Display Partial Payments' processing option was selected.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

N/A

Problems Addressed

Repeat Settlement: Corrected errors occurring when running Repeat Settlement with certain processing parameters.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

New ALV Settlement Report

The Settlement programs now use SAP ALV layout to improve usability.

Problems Addressed

Reauthorize & Release Billing Document: Changes were made to ensure credit memos are processed.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

Multi-Capture Workflow Support

Added support for multi-capture workflow. Standard setup available for Vantiv Acquiring Platform (VAP/Litle), Worldpay Payment Gateway (WPG), and an Other option which can be used for FDMS North processing platforms through the XiPay cartridges.

New Multi-Capture configuration section was added to the PCMA IMG (/PMPAY/PIMG) to support this functionality. Additionally, changes were made to the existing Pre-auth, Post-auth, and Pre-settle PUE function modules. An new PUE function module was added that reads the configured values to determine if a transaction is eligible for multi-capture workflow.

XiRecon Enhancements

On the Settlement Reconciliation Report, a new feature was added that allows you to receive emails if there are failed batches. Select the Email failed batches checkbox, and then determine whether to use an SAP Distribution list or enter individual email addresses.

Problems Addressed

N/A

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

• Improvements to Intercept SAP and Open AR CVV

• Support for S/4 HANA 2021 SP2 and 2022

Problems Addressed

N/A

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

N/A

Problems Addressed

• Override percentage field was not editable in the new ALV layout for Single and Multi-Customer Open AR.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

N/A

Problems Addressed

• RFC Connection Short Dump: If an RFC connection was down, any program that performs an RFC ping prior to running was resulting in a short dump if email address was not maintained in the RFC Connection Status program. An error message now displays.

• Auto AR: Changes were made to improve performance when processing large volumes.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

Stored Credentials

Added support for handling CIT/MIT message type for the stored credentials transaction framework mandates to streamline implementation within SAP.

Standardize Report Messaging

Made the no results message of the following reports consistent with other reports by providing a pop-up indicating no data found that matches selection criteria.

• Expiring Payment Card Authorizations

• Multi-capture Authorizations

• Payment Card Worklist

• Reauth & Release Billing documents

Problems Addressed

N/A

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

N/A

Problems Addressed

Web AR and echeck: Changes were made to ensure tokenized echeck details are updated in FPLTC and BSEGC.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

N/A

Problems Addressed

Open AR and Partial Payments: ALV not displaying properly when 'Display Partial Payments' processing option was selected.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

N/A

Problems Addressed

Repeat Settlement: Changes were made to address errors occurring when running Repeat Settlement with certain processing parameters.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

New ALV Settlement Report

The Settlement programs now use SAP ALV layout to improve usability.

Problems Addressed

Reauthorize & Release Billing Document: Changes were made to ensure credit memos are processed.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

Multi-Capture Workflow Support

Added support for multi-capture workflow. Standard setup available for Vantiv Acquiring Platform (VAP/Litle), Worldpay Payment Gateway (WPG), and an Other option which can be used for FDMS North processing platforms through the XiPay cartridges.

New Multi-Capture configuration section was added to the PCMA IMG (/PMPAY/PIMG) to support this functionality. Additionally, changes were made to the existing Pre-auth, Post-auth, and Pre-settle PUE function modules. An new PUE function module was added that reads the configured values to determine if a transaction is eligible for multi-capture workflow.

XiRecon Enhancements

This enhancement allows customers to focus on items that need their attention by receiving an email report if there are transactions in error. Simply configure XiRecon report to run in update mode as a background job. You can send to individual email addresses or distribution lists or to SAP Distribution Lists.

Problems Addressed

N/A

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

• Improvements to Open AR workflow to reduce the number of confirmation clicks and streamline the process when implementing CVV with a new card via Intercept or using a card-on-file.

• Modifications to Settlement and Repeat Settlement to support S/4HANA 2021 SP2. Use appropriate transport for either SP1 or SP2.

Problems Addressed

N/A

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

• Level 2-3 Settlement Aggregation.

• Intercept SAP enhancements to make browser methods workflows more flexible and streamline saving card data in subscreens.

Problems Addressed

N/A

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

• Validated with S/4HANA 2021

• Productized minimum L2-L3 data fields

• Default values added for UPC Code and PO Number at settlement

• Enabled GUI Support for HTML

Problems Addressed

Corrected error occurring when running Reauth and Release Billing Document program in foreground in S/4HANA 2020-2021.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

All PCMA receivables management and payment card reports are now compatible with S/4HANA version 2020 on-premise.

Problems Addressed

N/A

Compatibility

• SAP S/4HANA 2020

• SAP SP Stack: Initial Shipment Stack

Paymetric SAP components

• PAS - 2.9.0 minimum

• XiSecure SAP S4 IK - 5.0.0 minimum

Version 5.0.0 is not backwards compatible with S/4HANA versions prior to 2020.

Install and Configuration Notes

For New Installs:

This is a full release of PCMA and only requires import of the full transport files.

There are no release-specific installation notes. Refer to the XiPay Platform SAP S4 Integration Guide for install, setup and integration details.

For Upgrades:

• For ALL upgrades, even if PCMA IMG modifications are not required for the upgrade, you must execute the PCMA IMG transaction code (/n/PMPAY/PIMG) to initiate the objects from the upgrade.

• When importing the transport(s),

  • The 'overwrite existing objects' flag should be selected since many of these are existing objects.

  • Allow sufficient time for each transport to complete before loading the next one to prevent syntax errors.

  • Any custom changes (including userexits configured in the Paymetric IMG's) should be evaluated and may need to be replicated in the new later versions of these userexits. There may be new PUE's (Paymetric userexits) that were not in your previous version - please review the documentation for details.

• If upgrading from a previous/older version of PCMA and were setup for 'Token Awareness', you may have custom Auth and Settle Wrapper function modules in place that may no longer be needed. There is also a related config setting to Use Tokenization for 'Token Awareness' in the PCMA PIMG.

• If upgrading from a previous/older version of PCMA, it is advised you recreate any custom userexits that are configured in the /PMPAY/PIMG. They should be recreated based on the new sample default userexits that are provided.

• As always, please test thoroughly before moving to PRD. If you would like to obtain consulting assistance with this install, please contact Support Services, https://worldpay.force.com/clients/login.

Summary of Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the new objects.

N/A

Known Issues or Limitations

There are no known issues for this release.

Supporting Integration Documents and Transports/Installers

• XiPay-PCMA SAP S4 Integration Guide

• PCMA_SAP_S4_2020.zip

Document and transport are available for download from the Merchant Portal Resources page.

New Features

In the Web AR function module, added optional parameters to disable auth RFC ping and one to assign the billing status for billing plan data.

Problems Addressed

N/A

New Features

All PCMA receivables management and payment card reports are now compatible with S/4HANA version 1909.

Problems Addressed

N/A

Compatibility

• SAP S/4HANA 1909

• SAP SP Stack: Initial Shipment Stack

Paymetric SAP components

• PAS: 2.9.0 +

• XiSecure: SAP S4 IK 4.2.0 +

Version 4.4.0 is not backwards compatible with S/4HANA versions prior to 1909.

Install and Configuration Notes

For New Installs:

This is a full release of PCMA and only requires import of the full transport files.

There are no release-specific installation notes. Refer to the XiPay Platform SAP S4 Integration Guide for install, setup and integration details.

For Upgrades:

• For ALL upgrades, even if PCMA IMG modifications are not required for the upgrade, you must execute the PCMA IMG transaction code (/n/PMPAY/PIMG) to initiate the objects from the upgrade.

• When importing the transport(s),

  • The 'overwrite existing objects' flag should be selected since many of these are existing objects.

  • Allow sufficient time for each transport to complete before loading the next one to prevent syntax errors.

  • Any custom changes (including userexits configured in the Paymetric IMG's) should be evaluated and may need to be replicated in the new later versions of these userexits. There may be new PUE's (Paymetric userexits) that were not in your previous version - please review the documentation for details.

• If upgrading from a previous/older version of PCMA and were setup for 'Token Awareness', you may have custom Auth and Settle Wrapper function modules in place that may no longer be needed. There is also a related config setting to Use Tokenization for 'Token Awareness' in the PCMA PIMG.

• If upgrading from a previous/older version of PCMA, it is advised you recreate any custom userexits that are configured in the /PMPAY/PIMG. They should be recreated based on the new sample default userexits that are provided.

• As always, please test thoroughly before moving to PRD. If you would like to obtain consulting assistance with this install, please contact Support Services, https://worldpay.force.com/clients/login.

Summary of Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the new objects.

N/A

Known Issues or Limitations

There are no known issues for this release.

Supporting Integration Documents and Transports/Installers

• XiPay-PCMA SAP S4 Integration Guide

• PCMA_SAP_S4_2020.zip

Document and transport are available for download from the Merchant Portal Resources page.

New Features

N/A

Problems Addressed

• For Multi-Customer Open AR, hotkey customer selection TCODE changed to BP (instead of XD02/XD03).

• Reverse clearing - selection method by Account Document Number failed to return detail/card information.

• Settlement programs - total fields increased avoid errors.

Compatibility

• SAP S4 HANA versions: 1610

• SAP SP Stack for all versions: Initial Shipment Stack

• Paymetric SAP components: PAS - 2.9.0+, XiSecure SAP S4 IK - 4.1.0+

Install and Configuration Notes

For New Installs:

This is a patch release of PCMA for S4 HANA; it requires PCMA 4.3.0 (full) transport and all prior patches, 4.3.1 through 4.3.5, transports already be installed.

There are no release-specific installation notes. Refer to the XiPay Platform SAP S4 Integration Guide for install, setup and integration details.

For Upgrades:

• If you are on a version prior to the latest full transport, install the full one and all subsequent patch transports.

• If you are on a version later than the latest full transport, verify all patch transports between your version and the latest are installed before installing the latest.

• For ALL upgrades, even if PCMA IMG modifications are not required for the upgrade, you must execute the PCMA IMG transaction code (/n/PMPAY/PIMG) to initiate the objects from the upgrade.

• When importing the transport(s):

  • The 'overwrite existing objects' flag should be selected since many of these are existing objects.

  • Allow sufficient time for each transport to complete before loading the next one to prevent syntax errors.

  • Any custom changes (including userexits configured in the Paymetric IMG's) should be evaluated and may need to be replicated in the new later versions of these userexits. There may be new PUE's (Paymetric userexits) that were not in your previous version - please review the documentation for details.

• If upgrading from a previous/older version of PCMA and were setup for 'Token Awareness' (if using XiSecure) you may have custom Auth and Settle Wrapper function modules in place that may no longer be needed. There is also a related config setting to Use Tokenization for 'Token Awareness' in the PCMA PIMG.

• If upgrading from a previous/older version of PCMA, it is advised you recreate any custom userexits that are configured in the /PMPAY/PIMG. They should be recreated based on the new sample default userexits that are provided.

• As always, please test thoroughly before moving to PRD. If you would like to obtain consulting assistance with this install, please contact Support Services, https://worldpay.force.com/clients/login.

Summary of Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the new objects.

N/A

Known Issues or Limitations

There are no known issues for this release.

Supporting Integration Documents and Transports/Installers

• XiPay-Platform SAP S4 Integration Guide

• XIPay_SAP_S4_2020.zip

Document and transport are available for download from the Merchant Portal Resources page.

New Features

Multi Customer Open AR added.

Problems Addressed

Incorrect error message displaying in Open AR. In a rare scenario, a settlement related error message was displaying.

Compatibility

• SAP S/4HANA versions: 1610

• SAP SP Stack for all versions: Initial Shipment Stack

Paymetric SAP components

• PAS: 2.9.0 +

• XiSecure: SAP S4 IK 4.1.0 +

Install and Configuration Notes

For New Installs:

This is a patch release of PCMA for S4 HANA; it requires PCMA 4.3.0 (full) transport and all prior patches, 4.3.1 through 4.3.4, transports already be installed.

There are no release-specific installation notes. Refer to the XiPay Platform SAP S4 Integration Guide for install, setup and integration details.

For Upgrades:

• If you are on a version prior to the latest full transport, install the full one and all subsequent patch transports.

• If you are on a version later than the latest full transport, verify all patch transports between your version and the latest are installed before installing the latest.

• For ALL upgrades, even if PCMA IMG modifications are not required for the upgrade, you must execute the PCMA IMG transaction code (/n/PMPAY/PIMG) to initiate the objects from the upgrade.

• When importing the transport(s),

  • The 'overwrite existing objects' flag should be selected since many of these are existing objects.

  • Allow sufficient time for each transport to complete before loading the next one to prevent syntax errors.

  • Any custom changes (including userexits configured in the Paymetric IMG's) should be evaluated and may need to be replicated in the new later versions of these userexits. There may be new PUE's (Paymetric userexits) that were not in your previous version - please review the documentation for details.

• If upgrading from a previous/older version of PCMA and were setup for 'Token Awareness' (if using XiSecure) you may have custom Auth and Settle Wrapper function modules in place that may no longer be needed. There is also a related config setting to Use Tokenization for 'Token Awareness' in the PCMA PIMG.

• If upgrading from a previous/older version of PCMA, it is advised you recreate any custom userexits that are configured in the /PMPAY/PIMG. They should be recreated based on the new sample default userexits that are provided.

• As always, please test thoroughly before moving to PRD. If you would like to obtain consulting assistance with this install, please contact Support Services, https://worldpay.force.com/clients/login.

Summary of Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the new objects.

N/A

Known Issues or Limitations

There are no known issues for this release.

Supporting Integration Documents and Transports/Installers

• XiPay-PCMA SAP S4 Integration Guide

• PCMA_SAP_S4_2020.zip

Document and transport are available for download from the Merchant Portal Resources page.

New Features

• Support for Get Transaction Function.

  A new function module was added in PCMA to support the new Get Transaction function in PAS version 2.9.0.

  The Get Transaction function is not tied to the SAP CA-PCI (Cross Application-Payment Card Interface) structure. It supports the use of the new function module in SAP to pull all of the transaction details from XiPay for a supplied XiPay Transaction ID. There are various uses for this data such as when implementing APMs or card network mandates around stored credentials.

  Customizations are required to supply the XiPay Transaction ID and handle the returned transaction details based upon the Merchant's business needs.

• Open AR - eCheck Enhancements. In the Open AR program, you can now enter alpha-numeric values in the Bank Number field. Additionally, the field length was extended to support various Processor requirements.

• Open AR - Additional Fields Added for Declines. In the Open AR program, the Authorization Reference Code and Authorization Number are now populated for declined transactions to facilitate research within XiPay WebGUI as well as Processor reports.

• Authorization Response by Date - Additional Fields Added for Declines. In the Payment Card Authorization Response by Date report, the Payer number is now populated in the Sold-to Party column for declined transactions.

Problems Addressed

• Open AR Partial Installment. In the Open AR program, a partial installment payment was being assigned to the first available installment invoice rather than the selected invoice.

• Manually Update Host Details of SAP Program Problem. When running the Manually Update Host Details of SAP program, the search was not finding all open batches.

Compatibility

• SAP S/4HANA versions: 1610

• SAP SP Stack for all versions: Initial Shipment Stack

Paymetric SAP components

• PAS: 2.9.0 +

• XiSecure: SAP S4 IK 4.1.0 +

Install and Configuration Notes

For New Installs:

This is a patch release of PCMA for S4 HANA; it requires PCMA 4.3.0, 4.3.1, 4.3.2, and 4.3.3 transports already be installed.

There are no release-specific installation notes. Refer to the XiPay Platform SAP S4 Integration Guide for install, setup and integration details.

For Upgrades:

• If you are on a version prior to the latest full transport, install the full one and all subsequent patch transports.

• If you are on a version later than the latest full transport, verify all patch transports between your version and the latest are installed before installing the latest.

• For ALL upgrades, even if PCMA IMG modifications are not required for the upgrade, you must execute the PCMA IMG transaction code (/n/PMPAY/PIMG) to initiate the objects from the upgrade.

• When importing the transport(s),

  • The 'overwrite existing objects' flag should be selected since many of these are existing objects.

  • Allow sufficient time for each transport to complete before loading the next one to prevent syntax errors.

  • Any custom changes (including userexits configured in the Paymetric IMG's) should be evaluated and may need to be replicated in the new later versions of these userexits. There may be new PUE's (Paymetric userexits) that were not in your previous version - please review the documentation for details.

• If upgrading from a previous/older version of PCMA and were setup for 'Token Awareness' (if using XiSecure) you may have custom Auth and Settle Wrapper function modules in place that may no longer be needed. There is also a related config setting to Use Tokenization for 'Token Awareness' in the PCMA PIMG.

• If upgrading from a previous/older version of PCMA, it is advised you recreate any custom userexits that are configured in the /PMPAY/PIMG. They should be recreated based on the new sample default userexits that are provided.

• As always, please test thoroughly before moving to PRD. If you would like to obtain consulting assistance with this install, please contact Support Services, https://worldpay.force.com/clients/login.

Summary of Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the new objects.

N/A

Known Issues or Limitations

There are no known issues for this release.

Supporting Integration Documents and Transports/Installers

• XiPay-Platform SAP S4 Integration Guide

• XiPay_SAP_S4.zip

Document and transport are available for download from the Merchant Portal Resources page.

New Features

• N/A

Problems Addressed

• Corrected a problem occurring when Payment Terms and Payment Method were entered in the selection criteria.

Compatibility

• SAP S/4HANA versions: 1610

• SAP SP Stack for all versions: Initial Shipment Stack

Paymetric SAP components

• PAS: 2.9.0 +

• XiSecure: SAP S4 IK 4.1.0 +

Install and Configuration Notes

For New Installs:

This is a patch release of PCMA for S4 HANA; it requires PCMA 4.3.0, 4.3.1, 4.3.2, and 4.3.3 transports already be installed.

There are no release-specific installation notes. Refer to the XiPay Platform SAP S4 Integration Guide for install, setup and integration details.

For Upgrades:

• If you are on a version prior to the latest full transport, install the full one and all subsequent patch transports.

• If you are on a version later than the latest full transport, verify all patch transports between your version and the latest are installed before installing the latest.

• For ALL upgrades, even if PCMA IMG modifications are not required for the upgrade, you must execute the PCMA IMG transaction code (/n/PMPAY/PIMG) to initiate the objects from the upgrade.

• When importing the transport(s),

  • The 'overwrite existing objects' flag should be selected since many of these are existing objects.

  • Allow sufficient time for each transport to complete before loading the next one to prevent syntax errors.

  • Any custom changes (including userexits configured in the Paymetric IMG's) should be evaluated and may need to be replicated in the new later versions of these userexits. There may be new PUE's (Paymetric userexits) that were not in your previous version - please review the documentation for details.

• If upgrading from a previous/older version of PCMA and were setup for 'Token Awareness' (if using XiSecure) you may have custom Auth and Settle Wrapper function modules in place that may no longer be needed. There is also a related config setting to Use Tokenization for 'Token Awareness' in the PCMA PIMG.

• If upgrading from a previous/older version of PCMA, it is advised you recreate any custom userexits that are configured in the /PMPAY/PIMG. They should be recreated based on the new sample default userexits that are provided.

• As always, please test thoroughly before moving to PRD. If you would like to obtain consulting assistance with this install, please contact Support Services, https://worldpay.force.com/clients/login.

Summary of Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the new objects.

N/A

Known Issues or Limitations

There are no known issues for this release.

Supporting Integration Documents and Transports/Installers

• XiPay-PCMA SAP S4 Integration Guide

• PCMA_SAP_S4_2020.zip

Document and transport are available for download from the Merchant Portal Resources page.

New Features

• Modified Visa card check routines to support 19 digit card numbers. Added support for the AR programs to also check Business Partner tables in addition to Customer Master tables as both can be configured in S4.

Problems Addressed

• In Open AR, the amount was not reflecting any partial payments when a specific document number was entered as filter criteria.

• Paymetric Reauthorize and Release Billing Document report was not working properly in S4.

• Documents by Settlement Date Range report had incorrect totals.

• Corrected a CVV problem when processing AMEX card type through Vantiv-Litle Processor.

• Corrected Amount fields in the XiRecon report that were displaying incorrect values for “JPY” currency. Changes made to Function Module: /PMPAY/PEX_POSTSETL.

• Expanded character length for echeck in the Web AR function module to 25 characters.

• Auto AR: On the Document info tab, the Document Type field selection criteria was not working properly.

• Auto AR: On the Processing options tab, there was no way select invoices due today. Now, entering 0 for Select invoices due in # days field returns invoices due the day you run the program. Leave the field blank to return all invoices due.

Compatibility

• SAP S/4HANA versions: 1610

• SAP SP Stack for all versions: Initial Shipment Stack

Paymetric SAP components

• PAS: 2.9.0 +

• XiSecure: SAP S4 IK 4.1.0 +

Install and Configuration Notes

For New Installs:

This is a patch release of PCMA for S4 HANA; it requires PCMA 4.3.0 transports already be installed.

There are no release-specific installation notes. Refer to the XiPay Platform SAP S4 Integration Guide for install, setup and integration details.

For Upgrades:

• If you are on a version prior to the latest full transport, install the full one and all subsequent patch transports.

• If you are on a version later than the latest full transport, verify all patch transports between your version and the latest are installed before installing the latest.

• For ALL upgrades, even if PCMA IMG modifications are not required for the upgrade, you must execute the PCMA IMG transaction code (/n/PMPAY/PIMG) to initiate the objects from the upgrade.

• When importing the transport(s),

  • The 'overwrite existing objects' flag should be selected since many of these are existing objects.

  • Allow sufficient time for each transport to complete before loading the next one to prevent syntax errors.

  • Any custom changes (including userexits configured in the Paymetric IMG's) should be evaluated and may need to be replicated in the new later versions of these userexits. There may be new PUE's (Paymetric userexits) that were not in your previous version - please review the documentation for details.

• If upgrading from a previous/older version of PCMA and were setup for 'Token Awareness' (if using XiSecure) you may have custom Auth and Settle Wrapper function modules in place that may no longer be needed. There is also a related config setting to Use Tokenization for 'Token Awareness' in the PCMA PIMG.

• If upgrading from a previous/older version of PCMA, it is advised you recreate any custom userexits that are configured in the /PMPAY/PIMG. They should be recreated based on the new sample default userexits that are provided.

• As always, please test thoroughly before moving to PRD. If you would like to obtain consulting assistance with this install, please contact Support Services, https://worldpay.force.com/clients/login.

Summary of Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the new objects.

User Exits/Wrappers Modified in this Release:

Function Module: /PMPAY/PEX_AUTO_CARD

General Objects Modified in this Release:

• Program: /PMPAY/PRE_AUTO_AR

• Program: /PMPAY/PRE_OPEN_AR

• Program: /PMPAY/PRE_DAR

Known Issues or Limitations

There are no known issues for this release.

Supporting Integration Documents and Transports/Installers

• XiPay Platform SAP S4 Integration Guide

• XiPay_SAP_S4.zip

Document and transport are available for download from the Merchant Portal Resources page.

New Features

• Added support for the AR programs to also check Business Partner tables in addition to Customer Master tables as both can be configured in S4.

Problems Addressed

• Corrected a CVV problem when processing AMEX card type through Vantiv-Litle Processor.

• Corrected Amount fields in the XiRecon report that were displaying incorrect values for “JPY” currency. Changes made to Function Module: /PMPAY/PEX_POSTSETL.

• Expanded character length for echeck in the Web AR function module to 25 characters.

• Auto AR: On the Document info tab, the Document Type field selection criteria was not working properly.

• Auto AR: On the Processing options tab, there was no to way select invoices due today. Now, entering 0 for Select invoices due in # days field returns invoices due the day you run the program. Leave the field blank to return all invoices due.

Compatibility

• SAP S/4HANA versions: 1610

• SAP SP Stack for all versions: Initial Shipment Stack

Paymetric SAP components

• PAS: 2.9.0 +

• XiSecure: SAP S4 IK 4.1.0 +

Install and Configuration Notes

For New Installs:

This is a patch release of PCMA for S4 HANA; it requires PCMA 4.3.0 transports already be installed.

There are no release-specific installation notes. Refer to the XiPay Platform SAP S4 Integration Guide for install, setup and integration details.

For Upgrades:

• If you are on a version prior to the latest full transport, install the full one and all subsequent patch transports.

• If you are on a version later than the latest full transport, verify all patch transports between your version and the latest are installed before installing the latest.

• For ALL upgrades, even if PCMA IMG modifications are not required for the upgrade, you must execute the PCMA IMG transaction code (/n/PMPAY/PIMG) to initiate the objects from the upgrade.

• When importing the transport(s),

  • The 'overwrite existing objects' flag should be selected since many of these are existing objects.

  • Allow sufficient time for each transport to complete before loading the next one to prevent syntax errors.

  • Any custom changes (including userexits configured in the Paymetric IMG's) should be evaluated and may need to be replicated in the new later versions of these userexits. There may be new PUE's (Paymetric userexits) that were not in your previous version - please review the documentation for details.

• If upgrading from a previous/older version of PCMA and were setup for 'Token Awareness' (if using XiSecure) you may have custom Auth and Settle Wrapper function modules in place that may no longer be needed. There is also a related config setting to Use Tokenization for 'Token Awareness' in the PCMA PIMG.

• If upgrading from a previous/older version of PCMA, it is advised you recreate any custom userexits that are configured in the /PMPAY/PIMG. They should be recreated based on the new sample default userexits that are provided.

• As always, please test thoroughly before moving to PRD. If you would like to obtain consulting assistance with this install, please contact Support Services, https://worldpay.force.com/clients/login.

Summary of Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the new objects.

User Exits/Wrappers Modified in this Release:

Function Module: /PMPAY/PEX_AUTO_CARD

General Objects Modified in this Release:

• Program: /PMPAY/PRE_AUTO_AR

• Program: /PMPAY/PRE_OPEN_AR

• Program: /PMPAY/PRE_DAR

Known Issues or Limitations

There are no known issues for this release.

Supporting Integration Documents and Transports/Installers

• XiPay Platform SAP S4 Integration Guide

• XiPay_SAP_S4.zip

Document and transport are available for download from the Merchant Portal Resources page.

New Features

• Added support for S4 HANA Release 1610.

Problems Addressed

• N/A

Compatibility

• SAP: component: S4CORE, release: 101, SP-Level: 0000, support package: N/A

• Product Versions:

  • S4HANA ON PREMISE, 1610, Initial Shipment Stack, SAP S/4HANA 1610

  • NW FOR S4HANA ONPREMISE, 1610, Initial Shipment Stack, NW 7.51 FOR S/4HANA OP 1610

  This release was tested with the above versions. Later SAP S4 related releases, components and/or support packs are not guaranteed to work. PCMA for S4 will not work with versions prior to the ones provided above nor with S4 Simple Finance (S4FIN).

• Paymetric SAP Components: PAS - 2.7.3, XiSecure SAP S4 IK - 4.1.0

Install and Configuration Notes

For New Installs:

This is a full release of PCMA for S4 HANA; no prior transports are required.

There are no release-specific installation notes. Refer to the XiPay Platform SAP S4 Integration Guide for install, setup and integration details.

For Upgrades:

• If you are on a version prior to the latest full transport, install the full one and all subsequent patch transports.

• If you are on a version later than the latest full transport, verify all patch transports between your version and the latest are installed before installing the latest.

• For ALL upgrades, even if PCMA IMG modifications are not required for the upgrade, you must execute the PCMA IMG transaction code (/n/PMPAY/PIMG) to initiate the objects from the upgrade.

• When importing the transport(s),

  • The 'overwrite existing objects' flag should be selected since many of these are existing objects.

  • Allow sufficient time for each transport to complete before loading the next one to prevent syntax errors.

  • Any custom changes (including userexits configured in the Paymetric IMG's) should be evaluated and may need to be replicated in the new later versions of these userexits. There may be new PUE's (Paymetric userexits) that were not in your previous version - please review the documentation for details.

• If upgrading from a previous/older version of PCMA and were setup for 'Token Awareness' (if using XiSecure) you may have custom Auth and Settle Wrapper function modules in place that may no longer be needed. There is also a related config setting to Use Tokenization for 'Token Awareness' in the PCMA PIMG.

• If upgrading from a previous/older version of PCMA, it is advised you recreate any custom userexits that are configured in the /PMPAY/PIMG. They should be recreated based on the new sample default userexits that are provided.

• As always, please test thoroughly before moving to PRD. If you would like to obtain consulting assistance with this install, please contact Support Services, https://worldpay.force.com/clients/login.

Known Issues or Limitations

There are no known issues for this release.

Supporting Integration Documents and Transports/Installers

• XiPay Platform SAP S4 Integration Guide

• XiPay_SAP_S4.zip

Document and transport are available for download from the Merchant Portal Resources page.

New Features

N/A

Problems Addressed

• Override percentage field was not editable in the new ALV layout for Single and Multi-Customer Open AR.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

Stored Credentials

Added support for handling CIT/MIT message type for the stored credentials transaction framework mandates to streamline implementation within SAP.

Standardize Report Messaging

Made the no results message of the following reports consistent with other reports by providing a pop-up indicating no data found that matches selection criteria.

• Expiring Payment Card Authorizations

• Multi-capture Authorizations

• Payment Card Worklist

• Reauth & Release Billing documents

Problems Addressed

Web AR

Changes to the WEB AR BAPI for tokenized eCheck details not being updated in FPLTC and BSEGC.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

N/A

Problems Addressed

Repeat Settlement: Changes were made to address errors occurring when running Repeat Settlement with certain processing parameters.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

Multi-Capture Enhancements

Ability to change multi-capture parameter configuration if a QA system is not locked down for editing.

Problems Addressed

Multi-Customer Structure Changes

Changes made to use standard SAP CCAUT_R structure for multi-capture workflow to avoid errors if it contains appended values.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

• Recon Report Email Batch Errors - On the Settlement Reconciliation Report, a new feature was added that allows you to receive emails if there are failed batches.

• New ALV Layout for Reports - PCMA report layouts were updated to use the standard SAP ALV layout. This allows for header and footer sections (with a scrollable detailed section in the middle) to improve navigation and usability. Additional reports will be converted in future releases.

• Multi-Capture Enhancements - Modifications were made to improve performance when determining if a transaction falls into the multi-capture workflow.

Problems Addressed

The Multi-Customer Open AR report had an error when processing large numbers of open items, with some having a partial payment. Modifications were made to correct the partial payment problem and improve overall program performance.

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

• Productized Settlement Aggregation

• Performance improvements made during CVA assessment

Problems Addressed

N/A

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

• Productized Minimum L2-L3 Data Fields

• Default Values Added for UPC Code and PO Number at Settlement

• Intercept SAP and Open AR CVV & Workflow Improvements

Problems Addressed

N/A

Release Notes

Detailed Release Notes (PDF included with transport)

New Features

Web AR Enhancement - Connectivity

• The authorization connectivity ping is only performed when the authorization is being performed from SAP

• Retry logic for RFC ping when performing authorization from SAP

Web AR Enhancement - Billing Status Parameter

• When calling /PMPAY/CLEAR_AR_OPEN_ITEMS, there is an optional import parameter for Billing Status for Billing Plan/Invoice plan data

• This value defaults to 'C' which is consistent with our other AR tools

Web AR Enhancement - Amount Currency and FI Posting Change

• The utility now uses the document amount currency rather than local amount currency when performing the FI posting

Web AR Enhancement - Handling Payments for Closed Invoice

• The utility now automatically omits incoming payments for invoices that have already been closed in SAP and continues with the FI postings on the valid ones.

• A message is returned indicating the number of open items posted of the total number submitted. It does not include further details at this time

Problems Addressed

N/A

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide and/or the BillPay SAP Integration Guide for more detailed requirements.

• SAP ECC 6.0, ABAP 702, Support Pack 0016 minimum

Paymetric SAP components:

• PAS 2.10.0

• This release should be backwards compatible back to PAS 2.8.0; however it was tested with 2.10.0. If you are implementing tokenization through TMS, 2.10.0 minimum is required.

• XiSecure-TMS SAP S/4 IK - 3.3.0 minimum

Install and Configuration Notes

Upgrades

To upgrade PCMA, you only need to import the full 2.8.0 transports. See the following bullet points for additional considerations:

• For ALL upgrades, even if you do not make configuration changes, as a best practice you should always you should always execute the PCMA IMG transaction code (/n/PMPAY/PIMG) and BillPay Menu (/n/PMPAY/PBP if have implemented BillPay) to initiate the objects from the upgrade.

• If you are upgrading from version 1.7.3 or prior you will need to configure the PAS communication method in the PCMA Execution Settings (/PMPAY/XSET - accessible from the PCMA menu). First make note of the configured RFC Destinations Select PAS or PSNS as the Communication Method and set the RFC Destination(s).

• For BillPay Clients, in addition to importing the PCMA transport, please obtain and deploy the associated BillPay Enterprise Adapter for SAP. Contact Support Services or your Implementation Consultant.

• Consulting services are available upon request for all upgrades. If you are upgrading from a version that is multiple versions prior to the latest release, we highly recommend you seek consulting services.

For New Installs

Perform the setup and integration tasks as defined in the following integration guide(s):

• XiPay Platform SAP ECC Integration Guide – Instructions on importing the transport and Paymetric credit card processing and receivables management setup.

• BillPay SAP ECC Integration Guide – Instructions on Paymetric BillPay Solution setup.

Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the updated objects.

• /PMPAY/PEX_WEB_AR_FILTER - added new billing parameter; see PCMA-XiPay SAP ECC Integration Guide for details.

Known Issues or Limitations

There are no known issues for this release; however, the new SAP installation payment functionality does not support partial payments on an installation invoice.

Supporting Documentation and Transports/Installers

Following are all of the integration documents and transports/installers that support the PCMA component.

• PCMA-XiPay SAP ECC Integration Guide

• BillPay SAP Integration Guide

• PCMA_SAP_ECC.zip (transport files)

Paymetric Adapter for SAP (PAS) for connectivity:

• PAS Setup Guide

• PAS_Windows_Installer.zip

All of these documents and transports/installers are available for download from the Resources page in Merchant Portal and internally in the SharePoint Integration Library.

New Features

Multi-Capture Workflow Support

Added support for multi-capture workflow. Standard setup available for Vantiv Acquiring Platform (VAP/Litle) and Worldpay Payment Gateway (WPG) processing platforms through the XiPay cartridges.

New Multi-Capture configuration section was added to the PCMA IMG (/PMPAY/PIMG) to support this functionality. Additionally, changes were made to the existing Pre-auth, Post-auth, and Pre-settle PUE function modules. An new PUE function module was added that reads the configured values to determine if a transaction is eligible for multi-capture workflow.

See Getting Started with Multi-capture Integration document for the overall setup and integration summary. This document is available internally in SharePoint Integration Library and externally on Merchant Portal Resources page. The standard PCMA-XiPay SAP ECC Integration Guide was updated with the menu settings. You can also find help content within SAP in the IMG menu node help as well as screen help for the new multi-capture configuration screens.

Web AR Enhancement - Billing Status Parameter

• When calling /PMPAY/CLEAR_AR_OPEN_ITEMS, there is an optional import parameter for Billing Status for Billing Plan/Invoice plan data

• This value defaults to 'C' which is consistent with our other AR tools

Problems Addressed

N/A

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide and/or the BillPay SAP Integration Guide for more detailed requirements.

• SAP ECC 6.0, ABAP 702, Support Pack 0016 minimum

Paymetric SAP components:

• PAS 2.10.0

• This release should be backwards compatible back to PAS 2.8.0; however it was tested with 2.10.0. If you are implementing tokenization through TMS, 2.10.0 minimum is required.

• XiSecure-TMS SAP S/4 IK - 3.3.0 minimum

Install and Configuration Notes

Upgrades

To upgrade PCMA, you only need to import the full 2.8.0 transports. See the following bullet points for additional considerations:

• For ALL upgrades, even if you do not make configuration changes, as a best practice you should always you should always execute the PCMA IMG transaction code (/n/PMPAY/PIMG) and BillPay Menu (/n/PMPAY/PBP if have implemented BillPay) to initiate the objects from the upgrade.

• If you are upgrading from version 1.7.3 or prior you will need to configure the PAS communication method in the PCMA Execution Settings (/PMPAY/XSET - accessible from the PCMA menu). First make note of the configured RFC Destinations Select PAS or PSNS as the Communication Method and set the RFC Destination(s).

• For BillPay Clients, in addition to importing the PCMA transport, please obtain and deploy the associated BillPay Enterprise Adapter for SAP. Contact Support Services or your Implementation Consultant.

• Consulting services are available upon request for all upgrades. If you are upgrading from a version that is multiple versions prior to the latest release, we highly recommend you seek consulting services.

For New Installs

Perform the setup and integration tasks as defined in the following integration guide(s):

• XiPay Platform SAP ECC Integration Guide – Instructions on importing the transport and Paymetric credit card processing and receivables management setup.

• BillPay SAP ECC Integration Guide – Instructions on Paymetric BillPay Solution setup.

Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the updated objects.

• /PMPAY/PEX_PREAUTH - check multi-capture flag, if Yes then calls new MC FM configured in IMG

• /PMPAY/PEX_POSTAUTH - check multi-capture flag, if Yes then calls new MC FM configured in IMG

• /PMPAY/PEX_PRESETL - check multi-capture flag, if Yes then calls new MC FM configured in IMG

• /PMPAY/PEX_WEB_AR_FILTER - added new billing parameter; see the PCMA-XiPay SAP ECC Integration Guide for details.

Known Issues or Limitations

There are no known issues for this release; however, the new SAP installation payment functionality does not support partial payments on an installation invoice.

Supporting Documentation and Transports/Installers

Following are all of the integration documents and transports/installers that support the PCMA component.

• PCMA-XiPay SAP ECC Integration Guide

• BillPay SAP Integration Guide

• PCMA_SAP_ECC.zip (transport files)

Paymetric Adapter for SAP (PAS) for connectivity:

• PAS Setup Guide

• PAS_Windows_Installer.zip

All of these documents and transports/installers are available for download from the Resources page in Merchant Portal and internally in the SharePoint Integration Library.

New Features

Added support to integration to Credential Management Platform (CMP). For PCMA, there is a new TMS option on the IMG (/n/PMPAY/PIMG) for Encryption. This setting controls the TMS-related IMG nodes on the XiSecure/TMS IMG (/n/PMENC/BIMG).

Problems Addressed

N/A

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide and/or the BillPay SAP Integration Guide for more detailed requirements.

• SAP ECC 6.0, ABAP 702 Support Pack 0016

Paymetric SAP components:

• PAS 2.10.0

• XiSecure-TMS SAP S/4 IK 3.3.0 minimum

Install and Configuration Notes

Upgrades

To upgrade PCMA, you only need to import the full 2.7.0 transports. See the following bullet points for additional considerations:

• For ALL upgrades, even if you do not make configuration changes, as a best practice you should always you should always execute the PCMA IMG transaction code (/n/PMPAY/PIMG) and BillPay Menu (/n/PMPAY/PBP if have implemented BillPay) to initiate the objects from the upgrade.

• If you are upgrading from version 1.7.3 or prior you will need to configure the PAS communication method in the PCMA Execution Settings (/PMPAY/XSET - accessible from the PCMA menu). First make note of the configured RFC Destinations Select PAS or PSNS as the Communication Method and set the RFC Destination(s).

• For BillPay Clients, in addition to importing the PCMA transport, please obtain and deploy the associated BillPay Enterprise Adapter for SAP. Contact Support Services or your Implementation Consultant.

• Consulting services are available upon request for all upgrades. If you are upgrading from a version that is multiple versions prior to the latest release, we highly recommend you seek consulting services.

For New Installs

Perform the setup and integration tasks as defined in the following integration guide(s):

• XiPay Platform SAP ECC Integration Guide – Instructions on importing the transport and Paymetric credit card processing and receivables management setup.

• BillPay SAP ECC Integration Guide – Instructions on Paymetric BillPay Solution setup.

Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the updated objects.

• There are no modifications to existing customizable objects.

Known Issues or Limitations

There are no known issues for this release; however, the new SAP installation payment functionality does not support partial payments on an installation invoice.

Supporting Documentation and Transports/Installers

Following are all of the integration documents and transports that support the PCMA component.

• XiPay Platform SAP ECC Integration Guide

• BillPay SAP Integration Guide

• PCMA_SAP_ECC.zip (transport files)

Paymetric Adapter for SAP (PAS) for connectivity:

• XiPay Platform SAP S4 Integration Guide

• PAS_Windows_Installer.zip

All of these documents and transports/installers are available for download from the Resources page in Merchant Portal.

New Features

N/A

Problems Addressed

• PCMA Settlement: Modified to increase various field sizes that were causing a short dump in some instances.

• Open AR: When processing echeck transactions make changes to prevent duplicate error transaction record.

• Multi-customer Open AR:

  • Correct financial posting problem occurring when combining residual data with a credit.

  • Manual Authorization total amount is incorrect when multiple customers are selected.

• CMMS: Correct short dump problem related to field names within the CMMS function module.

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide and/or the BillPay SAP Integration Guide for more detailed requirements.

• SAP ECC 6.0, ABAP 702, Support Pack 0016

Paymetric SAP components:

• PAS 2.9.0+

• XiSecure SAP ECC Integration Kit: 3.2.0 (+ any patches)

Install and Configuration Notes

Upgrades

To upgrade PCMA, you only need to import the full 2.6.0 transports. See the following bullet points for additional considerations:

• For ALL upgrades, even if you do not make configuration changes, as a best practice you should always you should always execute the PCMA IMG transaction code (/n/PMPAY/PIMG) and BillPay Menu (/n/PMPAY/PBP if have implemented BillPay) to initiate the objects from the upgrade.

• If you are upgrading from version 1.7.3 or prior you will need to configure the PAS communication method in the PCMA Execution Settings (/PMPAY/XSET - accessible from the PCMA menu). First make note of the configured RFC Destinations Select PAS or PSNS as the Communication Method and set the RFC Destination(s).

• For BillPay Clients, in addition to importing the PCMA transport, please obtain and deploy the associated BillPay Enterprise Adapter for SAP. Contact Support Services or your Implementation Consultant.

• Consulting services are available upon request for all upgrades. If you are upgrading from a version that is multiple versions prior to the latest release, we highly recommend you seek consulting services.

For New Installs

Perform the setup and integration tasks as defined in the following integration guide(s):

• XiPay Platform SAP ECC Integration Guide – Instructions on importing the transport and Paymetric credit card processing and receivables management setup.

• BillPay SAP ECC Integration Guide – Instructions on Paymetric BillPay Solution setup.

Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the updated objects.

• There are no modifications to existing customizable objects.

Known Issues or Limitations

There are no known issues for this release; however, the new SAP installation payment functionality does not support partial payments on an installation invoice.

Supporting Documentation and Transports/Installers

Following are all of the integration documents and transports/installers that support the PCMA component.

• PCMA-XiPay SAP ECC Integration Guide

• BillPay SAP Integration Guide

• PCMA_SAP_ECC.zip (transport files)

Paymetric Adapter for SAP (PAS) for connectivity:

• PAS Setup Guide

• PAS_Windows_Installer.zip

All of these documents and transports/installers are available for download from the Resources page in Merchant Portal and internally in the SharePoint Integration Library.

New Features

New Customer and Credit Card Report

A new report was added that works with our Customer Master Management Suite (CMMS) consulting solution. This solution extends the ability to store and manage payment cards within SAP's standard customer master functionality.

The report allows the user to view a list of all Customers Master entries including the card number token, cardholder name, and validity dates based on the selection criteria provided. You can select by Customer, last 4 digits of a card number, payment card type, and/or cardholder name.

• There is a PCMA IMG setting that controls whether the report displays in the PCMA Main Menu.

• eCheck field length increased from 18 to 19.

• Added Document Posting Date and Time to XiRecon Reconciliation Report.

• The Payment options pop-up dialog box now displays duplicate credit card numbers with Customer number if applicable. It also now excludes any blocked or expired cards. The following screenshot shows example of duplicate card on different Customers.

Problems Addressed

• Settlement Program Ping inactivated other fields – When selecting either of the Ping options on the Settlement program, various other fields were being grayed-out and the user could not make changes to them.

• Incorrect error message in Open AR – In a rare scenario, a settlement related error message was displaying.

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide and/or the BillPay SAP Integration Guide for more detailed requirements.

• SAP ECC 6.0, ABAP 702, Support Pack 0016.

Paymetric SAP components:

• PAS 2.9.0 minimum

• XiSecure SAP ECC Integration Kit: 3.2.0 (+ any patches)

• BillPay Enterprise Adapter for SAP: 2.2.0 minimum, if implementing BillPay

Install and Configuration Notes

Upgrades

To upgrade PCMA, you only need to import the full 2.5.0 transports. See the following bullet points for additional considerations:

• For ALL upgrades, even if you do not make configuration changes, as a best practice you should always you should always execute the PCMA IMG transaction code (/n/PMPAY/PIMG) and BillPay Menu (/n/PMPAY/PBP if have implemented BillPay) to initiate the objects from the upgrade.

• If you are upgrading from version 1.7.3 or prior you will need to configure the PAS communication method in the PCMA Execution Settings (/PMPAY/XSET - accessible from the PCMA menu). First make note of the configured RFC Destinations Select PAS or PSNS as the Communication Method and set the RFC Destination(s).

• For BillPay Clients, in addition to importing the PCMA transport, please obtain and deploy the associated BillPay Enterprise Adapter for SAP. See the release notes provided with the Adapter for upgrade steps.

• Consulting services are available upon request for all upgrades. If you are upgrading from a version that is multiple versions prior to the latest release, we highly recommend you seek consulting services.

For New Installs

Perform the setup and integration tasks as defined in the following integration guide(s):

• XiPay Platform SAP ECC Integration Guide – Instructions on importing the transport and Paymetric credit card processing and receivables management setup.

• BillPay SAP ECC Integration Guide – Instructions on Paymetric BillPay Solution setup.

Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the updated objects.

• There are no modifications to existing customizable objects.

Known Issues or Limitations

There are no known issues for this release; however, the new SAP installation payment functionality does not support partial payments on an installation invoice.

Supporting Documentation and Transports/Installers

Following are all of the integration documents and transports/installers that support the PCMA component.

• PCMA-XiPay SAP ECC Integration Guide

• BillPay SAP Integration Guide

• PCMA_SAP_ECC.zip (transport files)

Paymetric Adapter for SAP (PAS) for connectivity:

• PAS Setup Guide

• PAS_Windows_Installer.zip

All of these documents and transports/installers are available for download from the Resources page in Merchant Portal and internally in the SharePoint Integration Library.

New Features

Support for Get Transaction Function

A new function module was added in PCMA to support the new Get Transaction function in PAS version 2.9.0.

The Get Transaction function is not tied to the SAP CA-PCI (Cross Application-Payment Card Interface) structure. It supports the use of the new function module in SAP to pull all of the transaction details from XiPay for a supplied XiPay Transaction ID. There are various uses for this data such as when implementing APMs or card network mandates around stored credentials.

Customizations are required to supply the XiPay Transaction ID and handle the returned transaction details based upon the Merchant's business needs.

Problems Addressed

Customer Number Cutoff in Multi-Customer Open AR. When choosing a payment method in Multi-Customer Open AR program, the Customer number was being cutoff for the default card entry.

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide and/or the BillPay SAP Integration Guide for more detailed requirements.

• SAP ECC 6.0, ABAP 702, Support Pack 0016

Paymetric SAP components:

• PAS 2.9.0 minimum

• XiSecure SAP ECC Integration Kit: 3.0.0 minimum (+ any patches)

• BillPay Enterprise Adapter for SAP: 2.2.0 minimum if implementing BillPay

Install and Configuration Notes

Upgrades

To upgrade PCMA, you should already have PCMA 2.4.0 imported then import the 2.4.1 patch transport. See the following bullet points for additional considerations:

• For ALL upgrades, even if you do not make configuration changes, as a best practice you should always you should always execute the PCMA IMG transaction code (/n/PMPAY/PIMG) and BillPay Menu (/n/PMPAY/PBP if have implemented BillPay) to initiate the objects from the upgrade.

• If you are upgrading from version 1.7.3 or prior you will need to configure the PAS communication method in the PCMA Execution Settings (/PMPAY/XSET - accessible from the PCMA menu). First make note of the configured RFC Destinations Select PAS or PSNS as the Communication Method and set the RFC Destination(s).

• For BillPay Clients, in addition to importing the PCMA transport, please obtain and deploy the associated BillPay Enterprise Adapter for SAP. See the release notes provided with the Adapter for upgrade steps.

• Consulting services are available upon request for all upgrades. If you are upgrading from a version that is multiple versions prior to the latest release, we highly recommend you seek consulting services.

For New Installs

Verify you have PCMA 2.4.0 imported and then import the 2.4.1 patch transport and perform the setup and integration tasks as defined in the following integration guide(s):

• XiPay Platform SAP ECC Integration Guide – Instructions on importing the transport and Paymetric credit card processing and receivables management setup.

• BillPay SAP ECC Integration Guide – Instructions on Paymetric BillPay Solution setup.

Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the updated objects.

• There are no modifications to existing customizable objects. Only a new function module was added to support Get Transaction.

Known Issues or Limitations

There are no known issues for this release; however, the new SAP installation payment functionality does not support partial payments on an installment invoice.

Supporting Documentation and Transports/Installers

Following are all of the integration documents and transports/installers that support the PCMA component.

• PCMA-XiPay SAP ECC Integration Guide

• BillPay SAP Integration Guide

• PCMA_SAP_ECC.zip (transport files)

Paymetric Adapter for SAP (PAS) for connectivity:

• PAS Setup Guide

• PAS_Windows_Installer.zip

All of these documents and transports/installers are available for download from the Resources page in Merchant Portal and internally in the SharePoint Integration Library.

New Features

• Multi-Customer Open AR Tool Added. A new tool was added that allows you to select multiple customers for open AR processing. This tool functions exactly the same as the single customer Open AR program, BUT note that the customer address information defaults to the first customer found when executing the program. The Multi-Customer Open AR tool also has a separate Paymetric User Exist that can be customized.

• BillPay Response Log Report Enhancements. Added Refresh capability so you do not have to back out of report to refresh results. Added Number of Records value to the report results header.

• BillPay Notification Report Enhancements. Added Refresh capability so you do not have to back out of report to refresh results. Added Total totalButton function to the report.

• Open AR eCheck Enhancements. In the Open AR program, you can now enter alpha-numeric values in the Bank Number field. Additionally, the field length was extended to support various Processor requirements.

• Open AR - Additional Fields Added for Declines. In the Open AR program, the Authorization Reference Code and Authorization Number are now populated for declined transactions to facilitate research within XiPay WebGUI as well as Processor reports.

• Authorization Response by Date - Additional Fields Added for Declines. In the Payment Card Authorization Response by Date report, the Payer number is now populated in the Sold-to Party column for declined transactions.

Problems Addressed

• BillPay Response Log Report Date Problem. Report results were not correctly being returned when both the date and time were specified in the criteria.

• Open AR Partial Installment. In the Open AR program, a partial installment payment was being assigned to the first available installment invoice rather than the selected invoice.

• Open AR RDFI Number Field Length Increased. In the Open AR program, the Canadian RDFI number field (RDFICA) length was increased to 9.

• BillPay Notifications Report Spool Email Failing. When running the BillPay Notifications Report as a background job, the spool email was not working properly.

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide and/or the BillPay SAP Integration Guide for more detailed requirements.

• SAP ECC 6.0, ABAP 702, Support Pack 0016.

Paymetric SAP components:

• PAS 2.8.1 minimum

• XiSecure SAP ECC Integration Kit: 3.0.0 minimum and any patches

• BillPay Enterprise Adapter for SAP: 2.2.0 minimum, if implementing BillPay

Install and Configuration Notes

Upgrades

• For ALL upgrades, even if you do not make configuration changes, as a best practice you should always you should always execute the PCMA IMG transaction code (/n/PMPAY/PIMG) and BillPay Menu (/n/PMPAY/PBP if have implemented BillPay) to initiate the objects from the upgrade.

• If you are upgrading from version 1.7.3 or prior you will need to configure the PAS communication method in the PCMA Execution Settings (/PMPAY/XSET - accessible from the PCMA menu). First make note of the configured RFC Destinations Select PAS or PSNS as the Communication Method and set the RFC Destination(s).

• For BillPay Clients, in addition to importing the PCMA transport, please obtain and deploy the associated BillPay Enterprise Adapter for SAP. Contact Support Services or your Implementation Consultant.

• Consulting services are available upon request for all upgrades. If you are upgrading from a version that is multiple versions prior to the latest release, we highly recommend you seek consulting services.

For New Installs

• XiPay Platform SAP ECC Integration Guide - Instructions on importing the transport and Paymetric credit card processing and receivables management setup.

• BillPay SAP ECC Integration Guide - Instructions on Paymetric BillPay Solution setup

Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the updated objects.

• N/A

Known Issues or Limitations

There are no known issues for this release; however, the new SAP installation payment functionality does not support partial payments on an installation invoice.

Supporting Documentation and Transports/Installers

Following are all of the integration documents and transports/installers that support the PCMA component.

• PCMA-XiPay SAP ECC Integration Guide

• BillPay SAP Integration Guide

• PCMA_SAP_ECC.zip (transport files)

Paymetric Adapter for SAP (PAS) for connectivity:

• PAS Setup Guide

• PAS_Windows_Installer.zip

All of these documents and transports/installers are available for download from the Resources page in Merchant Portal and internally in the SharePoint Integration Library.

New Features

SAP BillPay Installment Payments

• Added a new Paymetric BillPay feature that allows SAP installment payments.

• The Invoice # field (Document #) now consists of the following data separated with hyphens: <Document #>-<Company Code>-<Fiscal Year>-<Accounting Line Item #>. Each Accounting Line Item is created as a separate Invoice in BillPay.

• There is no BillPay specific configuration required for SAP installment payments; just set the installment payment terms in standard SAP (Tcode: OBB8).

Ability to Use Duplicate Invoice Numbers in Paymetric BillPay

• For Paymetric BillPay Invoices and Transactions, the Invoice # (SAP Document Number) can never be a duplicate value in BillPay. This means that the Merchant could not recycle document numbers.

• Now when Invoices are sent to BillPay, the Invoice # field will consist of the following data separated with hyphens: <Document #>-<Company Code>-<Fiscal Year>-<Accounting Line Item #>.

• This new format not only allows for duplicate Invoice #s, but supports SAP Installment payments.

  Preauth User Exit Changes for Auth Line Item and Troubleshooting

• The Preauth Paymetric User Exit (PUE: /PMPAY/PEX_PREAUTH) was modified as follows:

  • By default, the Preauth User Exit will not send line item details at authorization. This information will be sent at settlement. The user exit can be modified to send line items at authorization if needed such as when implementing XiVerify fraud calls with authorization.

  • Added informational data to identify the username and the tcode/program whenever an authorization is created. This information can viewed in XiPay WebGUI on the Compare page accessed by drilling down on a transaction and clicking the Compare button on the Transactions Detail page. The fields display in the Header InfoItems section as BillPayWeb_TRANS_ID and BillPayWeb_USER.

Problems Addressed

Payment Card Authorization Response by Date Expiration Date Problem. Payment Card Authorization Response by Date report was not reporting correctly when the Expiration date was entered on the Payment Card Data tab.

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide and/or the BillPay SAP Integration Guide for more detailed requirements.

• SAP ECC 6.0, ABAP 702, Support Pack 0016.

Paymetric SAP components:

• PAS Minimum version 2.8.0

• PSNS: 1.0.0. 1.1.0 if you want mass tokenization

• SAP NetWeaver PI: Minimum version SAP PI version 7.11, SP013.

  SP013 is required for password security. SAP PI version 7.3, EHP1 required for encrypting message content at the database level.

• XiSecure SAP ECC Integration Kit: 3.0.0 (+ any patches)

• XiSecure SAP CRM Integration Kit: 3.0.0 minimum (+ any patches)

• BillPay Enterprise Adapter for SAP: 2.2.0 minimum

Install and Configuration Notes

To upgrade PCMA, import the new transport and see the following bullet points for additional considerations.

For Upgrades

To upgrade PCMA, import the new transport and see the following bullet points for additional considerations.

• For ALL upgrades, even if you do not make configuration changes, as a best practice you should always you should always execute the PCMA IMG transaction code (/n/PMPAY/PIMG) and BillPay Menu (/n/PMPAY/PBP if have implemented BillPay) to initiate the objects from the upgrade.

• If you are upgrading from version 1.7.3 or prior you will need to configure the PAS communication method in the PCMA Execution Settings (/PMPAY/XSET - accessible from the PCMA menu). First make note of the configured RFC Destinations Select PAS or PSNS as the Communication Method and set the RFC Destination(s).

• For BillPay Clients, in addition to importing the PCMA transport, please obtain and deploy the associated BillPay Enterprise Adapter for SAP. See the release notes provided with the Adapter for upgrade steps.

• Consulting services are available upon request for all upgrades. If you are upgrading from a version that is multiple versions prior to the latest release, Paymetric highly recommends you seek consulting services.

For New Installs

Install the full transport and perform the setup and integration tasks as defined in the following integration guide(s):

• XiPay Platform SAP ECC Integration Guide – Instructions on importing the transport and Paymetric credit card processing and receivables management setup.

• BillPay SAP ECC Integration Guide – Instructions on Paymetric BillPay Solution setup.

Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the updated objects.

• /PMPAY/PEX_PREAUTH

Known Issues or Limitations

There are no known issues for this release; however, the new SAP installment payment functionality does not support partial payments on an installment invoice.

Supporting Documentation and Transports/Installers

Following are all of the integration documents and transports/installers that support the PCMA component.

• PCMA-XiPay SAP ECC Integration Guide

• BillPay SAP Integration Guide

• PCMA_SAP_ECC.zip (transport files)

Paymetric Adapter for SAP (PAS) for connectivity:

• PAS Setup Guide

• PAS_Windows_Installer.zip

All of these documents and transports/installers are available for download from the Resources page in Merchant Portal and internally in the SharePoint Integration Library.

New Features

SAP BillPay Installment Payments

• Added a new Paymetric BillPay feature that allows SAP installment payments.

• The Invoice # field (Document #) now consists of the following data separated with hyphens: <Document #>-<Company Code>-<Fiscal Year>-<Accounting Line Item #>. Each Accounting Line Item is created as a separate Invoice in BillPay.

• There is no BillPay specific configuration required for SAP installment payments; just set the installment payment terms in standard SAP (Tcode: OBB8).

Ability to Use Duplicate Invoice Numbers in Paymetric BillPay

• For Paymetric BillPay Invoices and Transactions, the Invoice # (SAP Document Number) can never be a duplicate value in BillPay. This means that the Merchant could not recycle document numbers.

• Now when Invoices are sent to BillPay, the Invoice # field will consist of the following data separated with hyphens: <Document #>-<Company Code>-<Fiscal Year>-<Accounting Line Item #>.

• This new format not only allows for duplicate Invoice #s, but supports SAP Installment payments.

  Preauth User Exit Changes for Auth Line Item and Troubleshooting

• The Preauth Paymetric User Exit (PUE: /PMPAY/PEX_PREAUTH) was modified as follows:

  • By default, the Preauth User Exit will not send line item details at authorization. This information will be sent at settlement. The user exit can be modified to send line items at authorization if needed such as when implementing XiVerify fraud calls with authorization.

  • Added informational data to identify the username and the tcode/program whenever an authorization is created. This information can viewed in XiPay WebGUI on the Compare page accessed by drilling down on a transaction and clicking the Compare button on the Transactions Detail page. The fields display in the Header InfoItems section as BillPayWeb_TRANS_ID and BillPayWeb_USER.

Problems Addressed

Payment Card Authorization Response by Date Expiration Date Problem. Payment Card Authorization Response by Date report was not reporting correctly when the Expiration date was entered on the Payment Card Data tab.

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide and/or the BillPay SAP Integration Guide for more detailed requirements.

• SAP ECC 6.0, ABAP 702, Support Pack 0016.

Paymetric SAP components:

• PAS Minimum version 2.8.0

• PSNS: 1.0.0. 1.1.0 if you want mass tokenization

• SAP NetWeaver PI: Minimum version SAP PI version 7.11, SP013.

  Note SP013 is required for password security. SAP PI version 7.3, EHP1 required for encrypting message content at the database level.

• XiSecure SAP ECC Integration Kit: 3.0.0 (+ any patches)

• XiSecure SAP CRM Integration Kit: 3.0.0 minimum (+ any patches)

• BillPay Enterprise Adapter for SAP: 2.2.0 minimum

Install and Configuration Notes

To upgrade PCMA, import the new transport and see the following bullet points for additional considerations.

For upgrades:

To upgrade PCMA, import the new transport and see the following bullet points for additional considerations.

• For ALL upgrades, even if you do not make configuration changes, as a best practice you should always you should always execute the PCMA IMG transaction code (/n/PMPAY/PIMG) and BillPay Menu (/n/PMPAY/PBP if have implemented BillPay) to initiate the objects from the upgrade.

• If you are upgrading from version 1.7.3 or prior you will need to configure the PAS communication method in the PCMA Execution Settings (/PMPAY/XSET - accessible from the PCMA menu). First make note of the configured RFC Destinations Select PAS or PSNS as the Communication Method and set the RFC Destination(s).

• For BillPay Clients, in addition to importing the PCMA transport, please obtain and deploy the associated BillPay Enterprise Adapter for SAP. See the release notes provided with the Adapter for upgrade steps.

• Consulting services are available upon request for all upgrades. If you are upgrading from a version that is multiple versions prior to the latest release, Paymetric highly recommends you seek consulting services.

For new installs:

Install the full transport and perform the setup and integration tasks as defined in the following integration guide(s):

• XiPay Platform SAP ECC Integration Guide – Instructions on importing the transport and Paymetric credit card processing and receivables management setup.

• BillPay SAP ECC Integration Guide – Instructions on Paymetric BillPay Solution setup.

Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the updated objects.

• /PMPAY/PEX_PREAUTH

Known Issues or Limitations

There are no known issues for this release; however, the new SAP installment payment functionality does not support partial payments on an installment invoice.

Supporting Documentation and Transports/Installers

Following are all of the integration documents and transports/installers that support the PCMA component.

• PCMA-XiPay SAP ECC Integration Guide

• BillPay SAP Integration Guide

• PCMA_SAP_ECC.zip (transport files)

Paymetric Adapter for SAP (PAS) for connectivity:

• PAS Setup Guide

• PAS_Windows_Installer.zip

All of these documents and transports/installers are available for download from the Resources page in Merchant Portal and internally in the SharePoint Integration Library.

New Features

Residual Payments

Added support for residual payments. Residual payments must be enabled by Paymetric in the Merchant's profile and then enabled by the Merchant (or Consultant) in Merchant Portal BillPay Configuration.

In SAP, this is configured in the BillPay Menu (/PMPAY/PBP) under Configuration >> Document Posting Options.

If you have also implemented Paymetric Open AR with BillPay residual payments, that program must be configured for residual payments as well. If Open AR configuration does not match BillPay, a message displays indicating that Open AR configuration will be changed to match BillPay configuration whenever you run the program.

The following messages only display if you also have BillPay configured. This is not applicable if you are not implementing that solution.

Problems Addressed

N/A

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide and/or the BillPay SAP Integration Guide for more detailed requirements.

• SAP ECC 6.0, ABAP 702, Support Pack 0016.

Paymetric SAP components:

• PAS 2.8.0 minimum version

• PSNS: 1.0.0, 1.1.0 (if you want mass tokenization)

• SAP NetWeaver PI: Minimum version SAP PI version 7.11, SP013.

• XiSecure SAP ECC Integration Kit: 3.0.0 minimum (+ any patches)

• XiSecure SAP CRM Integration Kit: 3.0.0 minimum (+ any patches)

• BillPay Enterprise Adapter for SAP: 2.2.0 minimum

Install and Configuration Notes

This is a full release and only requires the PCMA full transport 2.2.0 be imported. BEFORE you perform any installation activities, refer to Read Me provided with the transports. This is especially important for upgrades. For Clients using PAS, if they upgrade from a version PRIOR to PCMA 1.8.0, they must go back into the PCMA Execution Settings (/PMPAY/XSET - accessible from the PCMA menu) and select PAS as the Communication Method and set the RFC Destinations.

Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the new objects.

User Exits/Wrappers modified in this release:

• /PMPAY/PEX_PBP_FILTER_INV

• /PMPAY/PEX_PBP_FILTER_TRAN

General objects modified in this release:

• N/A

Known Issues or Limitations

There are no known issues for this release.

Supporting Documentation and Transports/Installers

• XiPay Platform SAP Integration Guide

• BillPay SAP Integration Guide

• PCMA v2.2.0 ECC full zip (transport files)

For connectivity, choose one of the following packages:

• Paymetric Adapter for SAP (PAS)

  • PAS Setup Guide

  • PAS_Windows_Installer.zip -OR-

  • PAS_RHEL_Install_Pkg.zip

• Paymetric SAP NetWeaver Solution (PSNS)

  • PSNS Setup Guide

  • PSNS_Package_<ver#>.tpz (PSNS import file)

All of these documents and transports/installers are available for download from the Resources page in Merchant Portal.

New Features

Added Credit Invoices support for the Paymetric BillPay solution. There are no specific configuration settings nor Utility changes related to this new feature.

Refer to the BillPay SAP Integration Guide for details on setup and configuration.

The card check routines were modified to accommodate the new Visa 19-digit credit card numbers.

Problems Addressed

• XiRecon report runtime errors occurring when processing large data amounts.

• Open AR: When running the program with a specific Document Number entered on the Document information tab, any partial payments already applied did not display in Amount paid and therefore the Amount to process was inaccurate.

• Auto AR: On the Processing options, if the user entered '0' in the Select invoices due in # days field, he/she was expecting to have all invoices due today returned, but all open items were being returned.

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide and/or the BillPay SAP Integration Guide for more detailed requirements.

• SAP ECC 6.0, ABAP 702, Support Pack 0016.

Paymetric SAP components:

• PAS minimum version 2.8.0

• PSNS: 1.0.0, 1.1.0 (if you want mass tokenization)

• SAP NetWeaver PI: Minimum version SAP PI version 7.11, SP013.

• XiSecure SAP ECC Integration Kit: 3.0.0 minimum (+ any patches)

• XiSecure SAP CRM Integration Kit: 3.0.0 minimum (+ any patches)

Install and Configuration Notes

This is a full release and only requires the PCMA full transport 2.1.0 be imported.

For Clients using PAS, if they upgrade from a version PRIOR to PCMA 1.8.0, they must go back into the PCMA Execution Settings (/PMPAY/XSET - accessible from the PCMA menu) and select PAS as the Communication Method and set the RFC Destinations.

Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the new objects.

User Exits/Wrappers modified in this release:

• N/A

General objects modified in this release:

• /PMPAY/P_BPCK_VISA

• /PMPAY/P_CHK_VISA

Known Issues

There are no known issues for this release.

Supporting Documents and Transports/Installers

This release is supported by the following:

• XiPay Platform SAP Integration Guide

• BillPay SAP Integration Guide

• PCMA v2.1.0 ECC full.zip (transport files)

For connectivity, choose one of the following packages:

• Paymetric Adapter for SAP (PAS) for connectivity:

  • PAS Setup Guide

  • PAS_Windows_Installer.zip -OR-

  • PAS_RHEL_Install_Pkg.zip

• Paymetric SAP NetWeaver Solution (PSNS)

  • PSNS Setup Guide

  • PSNS_Package_<ver#>.tpz (PSNS import file)

All of these documents and transports/installers are available for download from the Resources page in Merchant Portal.

New Features

• Added BillPay support. The transport Includes the configuration and utilities to implement the Paymetric BillPay solution. Refer to the BillPay SAP Integration Guide for details.

• For details on implementing XiPay and the additional Paymetric SAP extended reporting and receivables management functionality, refer to the XiPay Platform SAP Integration Guide.

• Expanded character length for echeck in the Web AR function module to 25 characters.

• Added new MasterCard 2 series BIN range to card check routine.

Problems Addressed

• Corrected a CVV problem when processing AMEX card type through Vantiv-Litle Processor.

• In Open AR configuration, made Reason Code required if Residual item is selected under Payment posting options. Leaving this field blank caused an error.

• Corrected Amount fields in the XiRecon report that were displaying incorrect values for “JPY” currency. Changes made to Function Module: /PMPAY/PEX_POSTSETL and /PMPAY/GET_BATCH_STATUS.

• Expanded character length for echeck in the Web AR function module to 25 characters.

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide for more detailed requirements.

• SAP ECC 6.0, ABAP 702, Support Pack 0016

Paymetric SAP components:

• PAS minimum version 2.7.3

• PSNS: 1.0.0, 1.1.0 (if you want mass tokenization)

• SAP NetWeaver PI: Minimum version SAP PI version 7.11, SP013.

• XiSecure SAP ECC Integration Kit: 3.0.0 minimum (+ any patches)

• XiSecure SAP CRM Integration Kit: 3.0.0 minimum (3.0.1 patch also available)

Install and Configuration Notes

This is a full release and only requires the PCMA full transport 2.0.0 be imported.

For Clients using PAS, if they upgrade from a version PRIOR to PCMA 1.8.0, they must go back into the PCMA Execution Settings (/PMPAY/XSET - accessible from the PCMA menu) and select PAS as the Communication Method and set the RFC Destinations.

Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the new objects.

User Exits/Wrappers modified in this release:

• /PMPAY/PEX_POSTSETL

General objects modified in this release:

• /PMPAY/P_BPCK_MC

• /PMPAY/P_CHK_MC

• /PMPAY/GET_BATCH_STATUS

Known Issues

There are no known issues for this release.

Supporting Documentation and Transports/Installers

• XiPay Platform SAP Integration Guide

• BillPay SAP Integration Guide

• PCMA v2.1.0 ECC full zip (transport files)

For connectivity, choose one of the following packages:

• Paymetric Adapter for SAP (PAS)

  • PAS Setup Guide

  • PAS_Windows_Installer.zip -OR-

  • PAS_RHEL_Install_Pkg.zip

• Paymetric SAP NetWeaver Solution (PSNS)

  • PSNS Setup Guide

  • PSNS_Package_<ver#>.tpz (PSNS import file)

All of these documents and transports/installers are available for download from the Resources page in Merchant Portal.

1.9.2 is a patch release that only requires 1.9.0 full transport be installed. There is no 1.9.1 ECC release.

Problems Addressed

• Corrected Amount fields in the XiRecon report that were displaying incorrect values for “JPY” currency.

• Changes made to Function Module: /PMPAY/PEX_POSTSETL and /PMPAY/GET_BATCH_STATUS.

New Features

N/A

Problems Addressed

Corrected a syntax import error for related to Program /PMPAY/SAPLPAYFUNCTIONS.

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide for more detailed requirements.

• SAP ECC 6.0, ABAP 700.

Paymetric SAP components:

• PAS minimum version 2.7.3

• PSNS: 1.0.0, 1.1.0 (if you want mass tokenization)

• SAP NetWeaver PI – Only applicable if using PSNS: Minimum version SAP PI version 7.11, SP013.

• SP013 is required for password security. SAP PI version 7.3, EHP1 is required for encrypting message content at the database level.

• XiSecure SAP ECC Integration Kit: 3.0.0 minimum

• XiSecure SAP CRM Integration Kit: 3.0.0 minimum (3.0.1 patch also available)

Install and Configuration Notes

This is a full release and requires the PCMA full transport 1.9.0 be imported.

Objects Modified

This section identifies any objects that were modified that should be taken into account when upgrading if you have existing customizations that need to be brought into the new objects.

User Exits/Wrappers modified in this release:

• N/A

General objects modified in this release:

• N/A

Known Issues

There are no known issues for this release.

Supporting Documentation and Transports/Installers

This release is supported by the following:

• XiPay Platform SAP Integration Guide

• PCMA v1.9.0 ECC full.zip (transport files)

For connectivity, choose one of the following packages:

• Paymetric Adapter for SAP (PAS) for connectivity:

  • PAS Setup Guide

  • PAS_Windows_Installer.zip -OR-

  • PAS_RHEL_Install_Pkg.zip

• Paymetric SAP NetWeaver Solution (PSNS)

  • PSNS Setup Guide

  • PSNS_Package_<ver#>.tpz (PSNS import file)

All of these documents and transports/installers are available for download from the Resources page in Merchant Portal and internally in the SharePoint Integration Library.

New Features

• Added support for the Paymetric SAP NetWeaver Solution (PSNS). A new drop down in the PCMA Execution Settings provides the options to select either PAS or PI Communication Method. (PI is the value for PSNS).

• Modifications made to XiRecon Settlement Report Configuration to support PSNS. A new node has been added in the PCMA IMG Settlement Reconciliation Report. This has a drop-down menu with values YES or NO. Whether using PSNS or PAS, you must select either YES or NO. If YES is selected then the 'Settlement PUE: Edit Settlement' will begin logging settlement data for the reconciliation report.

Problems Addressed

N/A

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide for more detailed requirements.

• SAP ECC 6.0

Paymetric SAP components:

• PAS: All versions back to minimum version supported.

• XiSecure SAP ECC Integration Kit: 3.0.0 minimum

• XiSecure SAP CRM Integration Kit: 3.0.0 minimum (3.0.1 patch also available)

Install and Configuration Notes

This is a full release and requires the PCMA full transport 1.8.0 be imported.

For Clients using PAS, if they upgrade to PCMA 1.8.0, they must go back into the PCMA Execution Settings (/PMPAY/XSET - accessible from the PCMA menu) and select PAS as the Communication Method and set the RFC Destinations.

Objects Modified

• N/A

Known Issues

There are no known issues for this release.

Supporting Documentation and Transports/Installers

• XiPay Platform SAP Integration Guide

• PCMA v1.8.0.B0003 ECC full.zip (transport files)

For connectivity, choose one of the following packages:

• Paymetric Adapter for SAP (PAS)

  • PAS Setup Guide

  • PAS_Windows_2.7.1-install.zip -OR-

  • PAS_Linux_2.7.1.zip (RHEL package)

• Paymetric SAP NetWeaver Solution (PSNS)

  • PSNS Setup Guide

  • PSNS_Package_1.0.0.tpz (PSNS import file)

All of these documents and transports/installers are available for download from the Resources page in Merchant Portal.

New Features

Intercept SAP: Popup a new session of B2B Intercept SA if Payer Partner changes after F4 is pressed.

If the user presses F4 from the Sales Order Screen to launch XiIntercept SA and then changes the Payer Partner, a new XiIntercept SA browser session will be launched. Users can implement this option by uncommenting and adding/modifying the code in their local PUE.

There are no configuration or user exit changes required in PCMA for this feature. See once the following release notes for deployment details: Latest GA Release Notes for 46c/ECC - 2.4.3 or Latest GA Release Notes for CRM - 2.4.1.

Problems Addressed

Intercept SAP: Incorrect Credit Card Saved to Personal List when using B2B Intercept Customer Master code.

If a user adds cards for customer A to his/her Personal Value List, only those cards will be displayed for customer A when using F4 on the Card Number field. If the user then goes to customer B, the Personal Value list for Customer A is displayed in error for customer B.

Now the Personal Value List of card numbers displays correct values based on the Customer/Payer.

There are no configuration or user exit changes required in PCMA for this feature. See once the following release notes for deployment details: Latest GA Release Notes for 46c/ECC - 2.4.3 or Latest GA Release Notes for CRM - 2.4.1.

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide for more detailed requirements.

• SAP GUI 4.6c, Support Pack 48 and higher

• SAP GUI 4.7, Support Pack 22 and higher

• SAP ECC 5.0, Support Pack 7 and higher

• SAP ECC 6.0

Paymetric SAP components:

PAS: All versions.

Intercept SAP SSO, minimum version 2.7.1

Install and Integration Notes

This patch release requires the PCMA full transport 1.7.0 and 1.7.2 be imported first. It does not require 1.7.1.

FOR UPGRADES from versions prior to 1.7.0:

The following Paymetric User Exits were modified in release 1.7.0, which is the full transport required for this patch release. If you have any customizations, they will need to be re-created based on the new sample default user exits provided with the transports.

• /PMPAY/PEX_PRESETL

• /PMPAY/PEX_POSTSETL

Objects Modified

User Exit samples modified in this release:

• None in this patch release, but see the note above if upgrading from a version prior to 1.7.0.

General objects modified in this release:

• Program: /PMPAY/PRE_AR_PAY

• Program: /PMPAY/PRE_OPEN_AR

• Program: /PMPAY/PRE_PART_ACT

Known Issues

There are no known issues for this release.

Supporting Documentation and Transports/Installers

• XiPay Platform SAP Integration Guide (includes PAS documentation)

• PCMA v1.7.3.H0031 (4.6 patch).zip transport file

• PCMA v1.7.3.H0031 (ERP unicode patch).zip transport file – For both ECC and 4.7 systems

• Cartridge Data Mapping spreadsheet for your chosen payment processor

New Features

XiRecon – Settlement Reconciliation Detail Report Displays Authorization No and Auth. Ref. Code by Default.

In the detail reconciliation report, the Authorization No and Auth. Ref. Code fields are now displayed by default; they were previously hidden and had to be added.

XiRecon – Settlement Reconciliation Report

Settlement Date and Batch ID Changes. Now you are only required to enter either the Batch ID or Settlement date or date range in the Settlement Reconciliation Report select criteria. The Settlement date is now blank by default and is only required if the batch number is not entered.

PCMA IMG Web AR Node Help Content for PUE: Filter Data Modified

In the PCMA IMG under Web AR, the node help content for PUE: Filter Data has been modified to include the remote-enabled function module called which is /PMPAY/CLEAR_AR_OPEN_ITEMS.

Problems Addressed

XiRecon Status Codes Not Included in Transport

The XiPay status codes are now populated in /PMPAY/RECON_T during the initial transport import.

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide for more detailed requirements.

• SAP GUI 4.6c, Support Pack 48 and higher

• SAP GUI 4.7. Support Pack 22 and higher

• SAP ECC 5.0 Support Pack 7 and higher

• SAP ECC 6.0

Paymetric SAP components:

• PAS: All versions.

• XiSecure - Intercept SAP Integration Kit: All versions.

Install and Integration Notes

This patch release requires PCMA 1.7.0 be imported first.

For upgrades from versions prior to 1.7.0:

The following Paymetric User Exits were modified in release 1.7.0, which is the full transport required for this patch release. If you have any customizations, they will need to be re-created based on the new sample default user exits provided with the transports.

• /PMPAY/PEX_PRESETL

• /PMPAY/PEX_POSTSETL

Objects Modified

User Exit samples modified in this release:

• None in patch 1.7.2. See upgrade note above for 1.7.0 full transport.

General objects modified in this release:

• Program: /PMPAY/RECON

• Table: /PMPAY/RECON_T

Known Issues

There are no known issues for this release.

Supporting Documentation and Transports/Installers

• PCMA-XiPay SAP Integration Guide

• Cartridge Data Mapping spreadsheet for your chosen payment processor

New Features

Intercept for SAP Single Sign-On Support

Note this feature has dependencies on other components. See B2B Intercept Solutions – B2B Intercept SAP version 2. Direct AR was modified to use the CCNUM domain to support B2B Intercept for SAP single sign-on (SSO) functionality. No other changes were required in PCMA to support this feature. This feature requires minimum PAS 2.7.1 and XiSecure SAP Integration Kit 2.4.0 as well. The configuration for B2B Intercept SAP SSO occurs in the XiSecure SAP Integration Kit.

Reverse Clearing with Payment Card Data Report Enhanced

Transactions originating from third party software outside the SAP systems occasionally do not pass the sales order document but only provide the billing document. The Program /PMPAY/PU_FBRC has been enhanced to display the corresponding billing document when there is no sales document number.

Direct AR now Accepts Tokens in a Fully Token-Aware Environment

When using Direct AR in a fully token aware environment, Direct AR was not allowing entry of a token. A modification was made to Function Module /PM/PAY/PRE_DAR so that Direct AR will now accept a token.

Profit Center added to Direct AR - XiRecon

A new Reconciliation Report added. A profit center can now be specified on the posting documents when using Direct AR. For SAP integrations, XiRecon provides settlement status reporting capabilities within SAP via PCMA. There is Standard XiRecon and Enhanced XiRecon. Enhanced XiRecon provides another level of reporting that confirms transaction statuses after the processor has received, processed and verified the data. See the PCMA-XiPay SAP Integration Guide for details on implementation and XiAssist for details on using the report.

Changes were made for this functionality to the default samples for the /PMPAY/PEX_PRESETL and /PMPAY/PEX_POSTSETL Paymetric User Exits (PUEs). If you have customizations, please copy these new samples and incorporate your customizations.

The Settlement Reconciliation Report (program /PMPAY/Recon) can be run from the PCMA main menu.

RFC Connection Status Program enhanced

Program /PMPAY/PRE_RFC_CON previously only pulled the RFC Destinations that were configured via the Execution Settings in PCMA. You can now manually enter the RFC Destinations for Authorization, Settlement, and Encryption (Tokenization) and Reconciliation (used by the Settlement Reconciliation Report feature).

Problems Addressed

N/A. This is an enhancement release.

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide for more detailed requirements.

• SAP ERP 4.6c, support pack 48 and higher

  SAP ERP 4.7, support pack 22 and higher

  SAP ECC 5.0, support pack 7 and higher

  SAP ECC 6.0

Paymetric SAP components

• PAS:

• XiSecure-XiIntercept SAP Integration Kit: all versions

Install and Configuration Notes

For upgrades:

The following Paymetric User Exits were modified in this release. If you have any customizations, they will need to be re-created based on the new sample default user exits provided with the transports.

• /PMPAY/PEX_PRESETL

• /PMPAY/PEX_POSTSETL

Known Issues

There are no known issues for this release.

Supporting Documentation and Transports/Installers

• PCMA-XiPay SAP Integration Guide

New Features

XiSecure Flex Token support added

XiSecure OnDemand has FlexToken technology that allows you to preserve the format of the data being represented which supports the use of existing programs and validations against tokens. Depending upon the format selected, it also provides the ability to obtain BIN ranges from the token as well.

A set of commonly used FlexTokens have been created and tested. The format type library is in the Paymetric Onboarding Request Form on the XiSecure tab in the column heading comment for FlexToken. If a custom format is selected, your Paymetric Implementation Consultant or Relationship Manager will discuss the additional implementation time required for creation and testing of the new format.

The PCMA IMG has a new Encryption type, FLX, with corresponding PUE's and configuration to accommodate FlexTokens. Refer to the Review PCMA IMG Settings topic in the PCMA Install and Configuration Guide for additional information. Refer to the Convert to FlexToken format topic in the XiSecure SAP Integration Guide for additional information on configuring the XiSecure component for this functionality.

Customers need to change or add RFC Destinations in the PCMA Execution Settings for FlexTokens.

Problems Addressed

• Web AR now distinguished as eCommerce. The field CSOUR has been added to function module /PMPAY/CLEAR_AR_OPEN_ITEMS so that authorizations and settlement transactions from the WEB are designated as eCommerce transactions rather than MOTO transactions.

• Reverse Clearing with Payment Card Data Report enhanced. Transactions originating from third party software outside the SAP systems occasionally do not pass the sales order document but only provide the billing document. The Program /PMPAY/PU_FBRC has been enhanced to display the corresponding billing document when there is no sales document number.

• Direct AR now accepts tokens in a fully token-aware environment. When using Direct AR in a fully token aware environment, Direct AR was not allowing entry of a token. A modification was made to Function Module /PM/PAY/PRE_DAR so that Direct AR will now accept a token.

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide for more detailed requirements.

• SAP

  • SAP GUI 4.6c, Support Pack 48 and higher

  • SAP GUI 4.7. Support Pack 22 and higher

  • SAP ECC 5.0 Support Pack 7 and higher

  • SAP ECC 6.0

    ** For B2B Intercept for SAP SSO, Minimum version SAP GUI 7.1. Note that B2B Intercept for SAP is not supported in NWBC nor SAP GUI for HTML.

• PAS: Minimum version 2.5.0

Install and Configuration Notes

PCMA Patch Release 1.6.0 is a prerequisite to installing this patch. Note that after importing the transport, you must execute the Transaction /n/PMPAY/PIMG to initiate the IMG, then you will perform any configuration settings as needed. Refer to the PCMA-XiPay SAP Integration Guide for detailed installation instructions.

There are no configuration notes specific to this release. Refer to the PCMA-XiPay SAP Integration Guide for details.

Known Issues

There are no known issues for this release.

Supporting Documentation and Transports/Installers

• PCMA-XiPay SAP Integration Guide version 1.6.1

• Payment and Tokenization SAP User Guide, version 1.6.1

• Performing Paymetric E-4 Key Rotation_NOV 2009-110-R1 (PDF (supports PCMA 1.2.x and prior)

• Performing Paymetric E4 Key Rotation_NOV 2009-R2 (PDF) (supports PCMA 1.3 and above)

New Features

N/A

Problems Addressed

• A syntax error was causing the Reverse Clearing program to fail when customers upgraded their ECC system due to a change made by SAP.

• The /PMPAY/PU_FBRC program has been modified to reference individual fields and not reference the SAP standard structure RF05R since SAP has a different version of the structure.

• The Use Tokenization PIMG setting will now default to T indicating that Tokenization has been selected for use. If the setting is not 'T', it is set to 'C' indicating that raw card numbers are entered instead of tokens.

New Features

Enhancement to the Payment Card Activity by Partner Number report.

Problems Addressed

• Raw card numbers transferred to XiPay during Repeat Settlement.

• Settlement report shows incorrect sales document number.

New Features

• Sample code to display PO# and/or SO# in XiPay Web GUI.

• Ability to Clear RFC Destination in Execution Settings.

• Test Authorization and Settlement RFC Tool Enhancements.

Problems Addressed

• Corrected Reversal Errors in Open and Direct AR Programs.

• Reversal Document Not Displaying.

• Raw Cards Potentially Used During Settlement.

• Credit Card Number Dropdown Limitation.

New Features

Authority Check enhancements as follows:

• Added before all transactions calls.

• Added before remote enabled function modules.

• Added a user exit to allow additional customized authority checks.

Problems Addressed

• Corrected an issue in which Open AR Clearing was saving the raw card number instead of the token when using a blind authorization.

• Modifications were made to the Settlement and Resubmission programs in support of SAP OSS

  1260263 that affect PCMA's pre-checks for security objects
  V_VBRK_FKA
  V_VBRK_VKO

• Updated Discover BIN ranges in card check routine.

Release Notes

Detailed Release Notes

New Features

The first release of PCMA for S4 HANA. This initial release includes the authorization, settlement, and tokenization wrappers as well as the Receivables Management (Open, Direct and Auto AR) functionality. A follow-up release is planned which will include the SD, FI, and XiRecon (Settlement Reconciliation) reports. Refer to the XiPay Platform SAP S4 Integration Guide for details.

Problems Addressed

• N/A

Compatibility

The basic compatibility for this release is listed below. See the XiPay Platform SAP Integration Guide for more detailed requirements.

• SAP: SAP ECC 6.0, ABAP 700

• **For XiIntercept for SAP SSO, Minimum version SAP GUI 7.1

• PAS: Minimum version 2.7.3

• XiSecure SAP ECC Integration Kit: 3.0.0 minimum. Note that the same transport used for ECC is used for Simple Finance for XiSecure.

• XiSecure SAP CRM Integration Kit: 3.0.0, minimum ( 3.0.1 patch also available)

Install and Configuration Notes

This is a full release of PCMA for Simple Finance; there are no prior transports required.

Supporting Integration Documents and Transports/Installers

This release is supported by the following:

• XiPay Platform SAP Integration Guide

• PCMA v3.0.0 Simple Finance full.zip (transport file)

Paymetric Adapter for SAP (PAS)

• PAS Setup Guide

• PAS_Windows_Installer.zip -OR-

• PAS_RHEL_Install_Pkg.zip

Document and transport are available for download from the Merchant Portal Resources page.

New Features

The first release of PCMA for S4 HANA. This initial release includes the authorization, settlement, and tokenization wrappers as well as the Receivables Management (Open, Direct and Auto AR) functionality. A follow-up release is planned which will include the SD, FI, and XiRecon (Settlement Reconciliation) reports. Refer to the XiPay Platform SAP S4 Integration Guide for details.

Problems Addressed

• N/A

Compatibility

Software Component Versions

• Component: S4CORE

• Release: 100

• SP-Level: 0002

• Support Package: SAPK-10002INS4CORE

Product Versions

• Component: S4HANA ON PREMISE

• Release: 1511

• SP Stack: 02 (05/2016) FPS

• Component: NW FOR S4HANA ONPREMISE

• Release: 1511

• SP Stack: 03 (04/2016)

Release 4.0.0 was tested with the above versions. Later SAP S4 related releases, components and/or support packs are not guaranteed to work. PCMA for S4 will not work with versions prior to the ones provided above nor with S4 Simple Finance (S4FIN).

Paymetric SAP Components

• PAS 2.7.3

• XiSecure SAP S4 IK 4.0.0

Install and Configuration Notes

This is a full release of PCMA for S4 HANA; there are no prior transports required. There are no release-specific installation notes. Refer to the XiPay Platform SAP S4 Integration Guide for install, setup, and integration details.

Supporting Integration Documents and Transports/Installers

This release is supported by the following:

• XiPay Platform SAP S4 Integration Guide

• XiPay_SAP_S4.zip

Document and transport are available for download from the Merchant Portal Resources page.