Prerequisites

Software

To use our validation solutions inside your SAP S/4HANA instances, you must:

1. Have an authentication token: Your Address, Email and/or Phone Validation API authentication token. If you don’t already have a token sign into the Self Service Portal or contact one of our regional sales teams.

2. Have the SAP Transports and Remote Function Call’s (RFC’s) inside SAP. 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.

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

3. Deactivate any already active implementations of the BAdi 'ADDRESS_CHECK'. This must be done prior to any Experian Transports being imported to your SAP system. To deactivate:

   1. Go to transaction SE18, then key in BAdI name ADDRESS_CHECK and click display.
   2. Navigate on the Menu bar by clicking on Implementation and then select Overview.
   3. Double-click on the custom implementation and click on Deactivate icon on the application bar while in change mode of the screen.

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.