You are on page 1of 6

SYMANTEC VERISIGN DAY

TO DAY ISSUES
DOCUMENT

APPLICABLE FOR ALL SOURCE SYSTEM


STATUS CODES ERROR_CODE

VSA GK, VSA ECAS SG,VSA


ECAS,CH_GEOTRUST,EMEA ECAS,MM
CERTS, GEOTRUST, TCC, TCCE, VCCE, ECA SHIP_TO_CUSTOMER_MISSING/BILL_
CUSTOMER_ERROR Client, GCCE, GCC TO_CUSTOMER_MISSING

BILL_TO_ADDRESS_MISSING/SHIP_TO
ADDRESS_ERROR _ADDRESS_MISSING

BILL_TO_CONTACT_MISSING/SHIP_T
CONTACT_ERROR O_CONTACT_MISSING
CREDIT_CARD_BANK_ACCOUNT_CRE
ERROR ATION_ERROR
CAUSE

Scenario1: The customer record is not received into staging table from
Engg. Customer file.

Scenario2: The Customer record is received into customer staging table


but in Error due invalid address
Scenario3: Customer record received and Status Closed, but does not
match with Customer name on Transaction record.

Scenario1: The Customer record is received into customer staging table


but in Error due to wrong ship-to address and bill-to address .

Scenario2: The record is received into the staging table with the valid
ship-to and bill-to address, but transaction interface is picking customer
record with old references.

Scenario3: Customer records are not received in customer staging

Scenario4: Customer record received and status Closed but address


details are not matching with details in transaction record
Scenario5: Customer records received into staging but are in error due
to in-active sites

Scenario1: The Customer record is received into customer staging table


but in Error due to the ship-to contact details and bill-to contact details
is missing for the invoice.
Scenario2: The ship-to or bill-to contacts entered by the customer is
invalid
Scenaroi3: The Customer record is received in to the Customer staging
table but the S2 is missing in the contact info

Scenario4: The Customer record is received in to the customer staging


table and all the contacts details were correct but the Attibute2 is not
null
Scenario5: The Contact details which were received in to the customer
staging table are wrong
Scenario6: The Customer record is received in to the customer staging
table but the received contact details are in-active
Payment method derivation error
Scenario1: Wrong Merchant ref
Scenario2: Unable to create Bank Account

Scenario3: Wrong Credit card number/Credit Card number in file is of


unknown type
RESOLUTION

Create the customer manually in the TCA and cross check the customer created in
the system and then update the address and customer name into tranaction staging
table if there is a difference

User need to be noified to correct the customer through customer correction screen

Create datafix to match th customer name in both trx and customer staging table

User need to correct the customer address through Customer correction form

create datafix script to Delete old customer records.

Ask user to create customer record manually or get the cusromer record from Engg
OR ask user to provide the customer details already created in TCA and accordingly
create datafix to match customer name and address details.

create datafix to match the details

user need to query the customer site and make it active

Create the ship-to or bill-to contacts for the customer of that invoice and make sure
it should be active

User need to correct the ship-to or bill-to contacts entered


The S2 is missing for the record, The API program "<Verisign Customer Import>"
needs to run to fix the issue

The attribute2 column needs to match with attribute23 because the column always
should be the match attribute23

BSA needs to check with customer, and update contact details manually

BSA needs to change the contact details from in-active to active manually
Mostly due to wrong Merchantref, run the datafix program that will null out the
merchant-ref and other payment deails so that this trx will be again authorized from
AR.
Bill to site is in-active. Make the site ctive and re-run the trx interface

Ask user to provide correct CC number and create datafix to update the same (in
encrypted format) else make the Trx of PO type, OR check if CC number has any
spaces then create datafix to update with CC number without spaces in encrypted
format

You might also like