Prerequisites

Software

To use our validation solution inside your SAP instances, you will have installed and configured:

• The Address Validation solution in your environment
  • Pro Web for on-premise data, or
  • Pro OnDemand for hosted datasets
• The Microsoft .NET Connector for SAP on your server
• The SAP Transports and Remote Function Call’s (RFC’s) inside SAP

To learn more about Experian Pro Web solution or if you’d like help with installing, configuring, and activating Pro Web please visit our documentation webpage for instructions, or contact our support team or your assigned Professional Services Consultant.

If you have chosen the hosted Experian solution, Pro OnDemand for hosted datasets, then the authentication tokens you will have been given upon purchasing these products must be activated and layouts chosen for use within SAP. For instructions on how to do this, please refer to this guide.

The Microsoft .NET Connector for SAP will need to be installed and configured on your server. The Real-Time validation component is a part of the Experian SAP .NET Connector (‘Connector’) that enables the Experian Pro Web and Experian OnDemand products to communicate together, along with the use of Remote Function Calls (RFC’s). Configuration files along with guidance will be provided during installation. The Connector enables the Search and Format requests made to the Experian Address Validation service to be called, based on the Authentication Token available. See section 2.2.

Where Pro Web validations are being called, you will also need to install and configure the Pro Web product together with the relevant country datasets. Don’t forget to track for Data expiration dates or set up Electronic Updates (EU) from Experian. See Section 2.1.
Where Pro OnDemand validations are being called, you will require a valid Authentication token and a fully configured connector.

There are several SAP Transports which must be imported into your SAP S/4HANA Development system for transport onto QA, Production or other instances of SAP where the functionality is needed. See section 2.3.

New RFC connections will then need to be created, in order that the configurations within the new Experian transports can talk to the Experian Address Validation solution. See section 2.4.

Transactions supported in SAP

The integration uses an SAP business add-in (BAdI) to trigger verification within the SAP Business Address Service (BAS) areas. Anywhere BAS is used, our integration is supported. For example, these may include:

• Business Partners
• Contacts
• Individual and Corporate Accounts
  If you require integrations outside of the BAS areas, please speak with your Experian Professional Services Consultant.

Access required

For a successful implementation, the below access & authorizations will be required during the project. Please provide the following access or make the relevant resources available to your Experian Professional Services Consultant.