Merging Customers with Tokenized Credit Card Records/AR05:

When you merge a customer that has existing records in AR05, the following two scenarios exist:

  1. We are merging two customers, but only the first customer is allowed EFT payments:

    • Customer A has an AR Terms code in Customer Master (SU13) that allows EFT payments and the customer has existing tokenized credit card records in AR05.

    • Customer B has an AR Terms code in SU13 that does not allow EFT payments.

    • Result: the AR05 records for Customer A are merged with Customer B, however the tokenized credit cards for Customer B cannot be accessed in AR05 directly or through the order entry programs (OE30, IN41, RS41, SE30 or AR39) until the AR Terms code in SU13 for Customer B is changed to one that allows EFT payments.

  2. Only one record can be flagged as the primary credit card record in AR05. We are merging two existing customers, each with a tokenized record flagged as the primary credit card in AR05:

    • Customer A is merged into Customer B. In this scenario, all of the records in AR05 for Customer A will be merged with Customer B.

    • Result: The record flagged as the primary credit card for Customer B will remain flagged. The record flagged as the primary credit card for Customer A will no longer be selected as the primary credit card.

 
Back