Troubleshoot

If you are having trouble with the output mappings from Experian to your address fields, check the address contents being returned:

1. Enter the transaction code: BP
2. Select an account group.
3. Enter address data into the mandatory fields and press Enter.
4. Select an address from the list returned in the popup window and click the envelope icon in the bottom right-hand corner.
   

The final address will be displayed. The field labels on the left correspond to the layout created earlier in step 2.1. These labels are mapped to the SAP fields within the transaction code: /QAS/YQAWB, in the Field Mappings tab.

{accordion-section|Connection errors}

1. Check which RFC connection is used to connect to the Experian Connector:
   1. Enter the transaction code: /QAS/YQAWB > QAS Setup > [Country] > RFC Destination.
2. Test the RFC connection:
   1. Enter the transaction code: SM59 > TCP/IP Connections.
   2. Search for the transaction found in step 1.
   3. Test the connection.
3. Restart the Experian Connector from Windows Services.
4. Restart Experian Pro Web from Windows Services.
5. Increase the log level. Logging is controlled by three environment variables:
   • QASPROLEVEL: 1-10 (default: 5)
   • QASPROFILE: name of the log file (default: qasprow4.log)
   • QASPROFLAG: ON/OFF (default: OFF)
6. Check the source code by adding a breakpoint to the function module:
   /QAS/OPENCONNECTION

Registration of TP PROWEB710 from host not

Configuration of the ECC environment is required in newer versions of ECC (as of 720 kernel) to allow external programs. To resolve this, ask the customer’s BASIS team to follow these instructions to allow the PROWEB710 server program to be registered.

Unable to connect to QuickAddress server

This error can be seen when triggering Address Lookup, even after the components have been installed and configured, and the RFC connection test is successful. To investigate this:

1. Enter the transaction code: SMGW and choose Goto > Logged on Clients
   

2. Stop the Experian Connector service, wait 30 seconds, and then restart the service.

3. Refresh the Logged on Clients screen and you should see approximately 15-20 entries for the PROWEB710 program from the server where the Experian Connector is installed: QASSAP.
   

4. Continue refreshing this screen. You may notice that the PROWEB710 entries begin to disappear over the next 60 seconds and you will be left with a much shorter list which does not contain any PROWEB710 entries from the QAS server.

5. If you observe this, the SAP Gateway is closing the QAS connections, which causes the Address Lookup to fail. To test resolving this, ask the SAP BASIS team to change the Gateway ACL_MODE parameter to allow the Experian connections to persist:

   1. Open the transaction code: RZ11 and maintain profile parameters.
   2. Select the parameter: gw/acl_mode.
   3. Change the default value for this parameter (1) to 0 to disable gateway security, which will allow Address Lookup to function, as expected in the current ECCDEV environment.

   Gateway security

   It is not recommended to keep the gateway security disabled in production systems. Use this as an emergency workaround in order to implement the appropriate gateway security. Find more information about gateway access control lists and disabling gateway security.