INTERCEPTAS GO LIVE Validations

v2 07-Nov-10

BUSINESS VALIDATION
a) ValidateSCOPE:
the accuracy and data completion (by comparing with SAP/GEM) o
region––preferably from different
countries (e.g., AMR: 1 x USA, 1 x Canada, 1 x Mexico, 1 x Brazil).
b) Validate the accuracy and data completion (by comparing with SAP/GEM) o
each region––this can be done by
viewing the details of LINKED SEARCHES to the LIVE QUEUE orders noted
c) Perform various actions on the LIVE QUEUE Orders, ideally each Region sh

1 x RELEASE w/ or w/out Contact

1 x CANCEL: Reject Fraud Review
1 x CONTACT: Email w/ PCD (Pending Cancel Date) EDIT
1 x HOLD: Pending Further Action.

If it proves difficult for each region to find candidate orders in production t

least 1 x region performs it
successfully,we can infer it will be fine globally. But we'd like each Region
d) After performing the INTERCEPTAS actions noted above, we should validat
IMMEDIATELY; b) AFTER SAP
CONFIRMATION IS REC'D (≤ 5 Min), and AGAIN AFTER INTERCEPTAS TRIG
e) After performing the INTERCEPTAS actions noted above, we should also va

f) Record the results of your validations in the matrix below, using the validat
columns provided.

INTERCEPTAS
Order Details
(Original:
Compare
Sales Org INTERCAPTS w/
Region (Country) Sales Doc #(s) Scenario Notes SAP)

IS&T Validations
AMR 7155433300 Fraud Review - √ OK - MATCH
INTERCEPTAS-driven
RELEASE
AMR a) Fraud Review - a) X Some Initial
7155717318 INTERCEPTAS-driven Issues w/ SPACES
CANCEL-Reject Fraud in PC PRINT &
b) Review EMAIL ADDRESS
7156777639 (later explained as
normal by Bruce @
Accertify) and Apple
Region (s/b Sales
Org Description);
Otherwise OK

b) Marc is testing
now.

AMR Fraud Review with Pre-

Existing PCD (Pending
Cancel Date) from SAP R/3
… Just Validate PCD is
present in INTERCEPTAS.
AMR Fraud Review - SAP/GEM-
driven RELEASE
AMR 7156782616 Contact Cust: Voicemail w/
PCD Edit via INTERCEPTAS
AMR 7156686979 Contact Cust: Voicemail w/
PCD Edit * Notes via SAP-
GEM … Subseq. CLAIMED
and clicked [Get Current
Status] in INTERCEPTAS

AMR 7156164852 CONVERSION of Fraud

Review Order w/ Previously
Set PCD of 11/7/10
 Asked Randy Randy's Request: "Double
via iChat if We fraud review check" Multi-
Have a card Error Issue
Candidate
Order We sometimes have a multi-
card order on fraud review,
and when we release
it from fraud review in SAP,
SAP then performs a second
fraud check on the
second card and the order
stays on fraud review.
When we come across
these issues, we end up
having to release the order
twice in SAP.

We need to test this to see

how it works in Accertify.

We'd think that the 2nd

fraud check on the second
card would eventually
assure the order goes back
on fraud review in
Interceptas, but we haven't
tested it yet.
AMR 7156700252 CONVERSION of 6-Nov
"F02" Orders w/ SAP/GEM-
driven Contact Cust: Email
and Hold: Add GEM Notes
actions made TODAY (7-
Nov-2010) w/ GEM Notes
and PCD Edit.

7156688561 Linked Search of Previously

Fraudulent Order

Business Validations
AMR 3400 7156834983 release w/o contact all details match

AMR
AMR
AMR
AMR
AMR
AMR
AMR
AMR
AMR
AMR
AMR
AMR
AMR
AMR
EMEA
EMEA
EMEA
EMEA
EMEA
EMEA
EMEA
EMEA
EMEA
EMEA
EMEA
EMEA
EMEA
EMEA
EMEA
APAC
APAC
APAC
APAC
APAC
APAC
APAC
APAC
APAC
APAC
APAC
APAC
APAC
APAC
APAC
paring with SAP/GEM) of at least 4 x representative orders within the LIVE QUEUE (F02-Fraud Review) per

ico, 1 x Brazil).
paring with SAP/GEM) of at least 4 x representative orders within ORDER HISTORY (NON-Fraud Review) within

E QUEUE orders noted above or by querying Order History itself.

ideally each Region should hopefully find candidates within production to perform at the very least:

EDIT

e orders in production to perform all 4 of these actions (especially the CANCEL: Reject Fraud Review), then if at

we'd like each Region to get a chance to validate for themselves.

bove, we should validate the orders are updated properly within INTERCEPTAS at 3 x points in time: a)

TER INTERCEPTAS TRIGGERS AUTO-ORDER REFRESH (> 15 Min ≤ 45 Min).

bove, we should also validate the orders are updated in SAP R/3 in various sections: a) ZV33/VA03; b) Z016;

below, using the validation columns that apply and noting your APPROVAL or any ISSUES / TICKETS in the

INTERCEPTAS
Order Status,
Exception Data Order Status,
& Resolution Exception Data Order Status,
Panel & Resolution Exception Data &
~~~ Panel Resolution Panel
Upon ~~~ ~~~
INTERCEPTAS- Immediate After SAP After Subseq Auto-
triggered Update Confirmation Order Refresh
Action(s) (≥ 1 Sec) (≤ 5 Min) (> 15 Min ≤ 45 Min)

√ OK: 45 - FR-INT:
Release w/out
Contact
 a) √ OK: 86 - FR- a) NEED TO RE- a) NEED TO RE- a) √ Order Status
INT: Cancel: Reject TEST to catch it in TEST to catch it "Cancelled",
Fraud R time. in time √ Exception Data
"Fraudulent Flag = X",
b) Marc is testing b) Marc is testing b) Marc is testing ~ MIXED Resolution
now. now. now. Panel still shows
"CANCELLED in SAP-
GEM" and Validation
Status "C - Order
Successfully Cancelled",
which should have been
cleared after
"automated" Get Order
Status following SAP
Confirmation––but
given issues we had
with Confirmations and
Update in INTERCEPTAS
(since resolved), this
should be fine in other
orders - NEED TO RE-
TEST.

b) Marc is testing now.

release w/o contact
(F02-Fraud Review) per

(NON-Fraud Review) within

at the very least:

ect Fraud Review), then if at

x points in time: a)

: a) ZV33/VA03; b) Z016;

SSUES / TICKETS in the

SAP R/3

GEM Order History ZV33 (Order

via Z016 or Inquiry) /
ZZV311 VA03 (Display Z016 [GEM ZV313 [GEM
(Original: Compare Order) Action Screen & Action History
SAP (Original & AFTER Log] Report]
w/ INTERCEPTAS) Action) (≤ 5 Min) (≤ 5 Min)

√ OK: 45 - FR-INT: √ OK: Open √ OK √ OK

Release w/out
Contact
√ OK: 79- TO-INT:
Send Resol Conf to
Accertify
 a) √ OK: 86 - FR- a) √ OK: Open -> a) √ OK a) √ OK
INT: Cancel: Reject Cancelled
Fraud Review b) Marc is testing b) Marc is testing
√ OK: 79- TO-INT: b) Marc is testing now. now. now.
Send Resol Conf to
Accertify

b) Marc is testing
now.
 actions and notes Before: Fraud Review; matches matches
from INT transferred After: Fraud Review transaction transaction history
to INT correctly Accepted history panel in panel in INT
INT
 Esprsso
Problem Ticket #
√ OK or X & Title
ISSUE (if req'd)

√ OK
 a) - MIXED … a) • CLOSED (Works
NEED TO RE- As Designed) - P3
TEST <exp2://Ticket/792
2290>
b) Marc is testing INTERCEPTAS: PC
now. Print Parameter
shows SPACE in
INTERCEPTAS
(which is not in
SAP)

• OPEN (Still
Researching - P3
<exp2://Ticket/792
2363>
INTERCEPTAS-
ORDER DATA:
REMOVE "Apple
Region" & REPLACE
with "Sales Org
Desc"

• OPEN (Need to
Make Update to
ZTEMUSR Table) -
P3
<exp2://Ticket/792
2463>
INTERCEPTAS-
>SAP-GEM:
C1502943SS Shows
Up in GEM Log
w/out Name

√ OK upon 2nd
Re-Test; after
more servers
added and we no
longer got an
"access denied".
√ OK (Non-
Conversion) upon
WORKAROUND of

- GAP: Need a
means of sending
Edit PCD Updates
from SAP-GEM ->
INTERCEPTAS.

X ISSUE: Even Jim/Sapna/Sanjay

subsequent will raise a technical
attempts at Espresso Ticket for
editing PCD via the program
INTERCEPTAS still change.
does NOT show
up in P3
INTERCEPTAS. <exp2://Ticket/792
Nor does SAP- 2689>
GEM-driven Notes INTERCEPTAS: 18 x
show up in Lines of CC Details
INTERCEPTAS. in INTERCEPTAS for
SAP Single
X ISSUE: Card/Auth
Sapna / Sanjay
state that the P2
SAT-6-Nov data <exp2://Ticket/792
went out, but 2734>
Bruce believe INTERCEPTAS: SAP
there may be a PCD of "11/7/10"
BAD XML Record Shows Up as BLANK
(special character DEFAULT of
unsupported "12/31/99"
perhaps?) causing
parsing errors. P2
<exp2://Ticket/792
X KNOWN GAP: 2840>
Multiple Credit INTERCEPTAS: NO
Card Data Historical GEM
Records (partially NOTES Captured in
empty), also seen Conversion Data
in UAT; awaiting
change.
X CONVERSION Jim/Sapna/Sanjay
ERROR / GAP: will raise a technical
Sapna still Espresso Ticket for
working w/ the program
Sanjay on change.
resolving ERROR
on 2-3,000 x
batch (as we
have approx.
15,000 of the
40,000 x
transactions still
missing.

Sapna / Sanjay
state that the
SAT-6-Nov data
went out, but
Bruce believe
there may be a
BAD XML Record
(special character
unsupported
perhaps?) causing
parsing errors.
X ISSUE: Fraud P2
Indicator NOT <exp2://Ticket/792
Sent on Interim 2426> SAP-
Order History >INTERCEPTAS:
(Nov 6th) Fraud Indicator NOT
Sent on Interim
Order History (Nov
6th)

√ OK