FUJ00084852
FUJ00084852
Peak Incident Management System
Call Reference PC0223870 Call Logger _Customer Call_ -- EDSC
Release ae At = HING-X09.0003.008V@l ee ~ CTR_APP_X0900_V470-V435
Call Type Live Incidents Priority B -- Business restricted
Contact EDSC Call Status Closed -- S/W Fix Available to Call
f j Logger
Target Date 22/03/2013 eo
Days)
Summary Branch 011458 has an unexplained discrepancy
All References Type Value
Release PEAK PC0228641
Problem Incident CTR APP _X0882_V450
Clone Call PC0224126
Product Baseline CTR_APP_X0900_V470-V435
SSCKEL KEL acha2230K
DevintRel-Director Live Supp.Test
SSCKEL KEL acha2230K
Problem Incident CTR_APP_X0882_V450
TRIOLE for Service A2401368
Collections Name User Date
BIFApproved Lorraine Guiblin 25-Mar-2013 11:43:17
Impact
St ee : User Date
Unknown 20-Mar-2013 15:10:25
This change would alert support teams to the existence of a system problem affecting branch accounts,
rather than having to wait for it to be reported. Such a problem, affecting 14 branches, was not reported
until 15 months after it first could have been noticed.
Progress Narrative
oate:25-Feb-2013 16:55:53 User:_Customer Call_
CALL PC0223870 opened
Details entered are:~
summary:The Branch as an unexplained discrepancy
call Type:L
call Priority:c
Target Release: HNG-X R6.50
Routed to:EDSC ~ Unassigned
Jbate:25-Feb-2013 16:55:52 User:_Customer Call_
INCIDENT MANAGEMENT
Date/Time Raised: Feb 25 2013 4:51PM
Priority: C
contact Name: Ibrahim at_™
contact Phone: {
originator: Xxxx
riginator's ref
Product Serial No:
product Site: 011458
2401368
transfer Note: Transfer Group from ‘POA-HSD. IMI! to 'POA-FJ-PEAK’
© Branch as an unexplained discrepancy. They balanced and rolled trading period on 6 Feb, they have one stock unit AA and this
anced with a loss of £39.57 which was transferred to local suspense however the figure that was cleared out from local
spense was much higher £9839.45.
Ir have carried out transaction logs for all transactions from date range 31 Jan to 06 Feb. Branch has submitted copies of the
final balance reports from TP 10 BP4 and TP10 BP 5 the balance report for TP10 BP5 shows discrepancy transferred of £39.57 and
then discrepancy resolved £9839.45, The transaction log completed for all transaction does not show any other figures being
entered into or removed from housekeeping/local suspense account.
FUJ00084852
FUJ00084852
lode 1
o6/02/2013 16:50 to 16:51
JAA TP 10 BP4/5
IHASOO1
Incident History:
2013-02-25 16:51:20 [ Richardson, Mark ]
INIT : Create a new request/incident/problem/change/issue
2013-02-25 16:54:19 [ Richardson, Mark ]
zneun_en_poa : Open Notification
2013-02-25 16:54:19 [ Richardson, Mark ]
_en_poa : Transfer Notification
25 16:54:54 [ Richardson, Mark ]
zneut_en_poa : Transfer Notification
jDate:25-Feb-2013 16:59:22 User:Clive Turrell
Product General/Other/Misc -- Unknown General/Other/Misc (version unspecified) added.
Jbate:25-Feb-2013 17:02:16 User:Clive Turrell
[fhe Call record has been assigned to the Team Member: Anne Chambers
Progress was delivered to Consumer
IDate:25-Feb-2013 17:47:51 User:Anne Chambers
he call summary has been changed from:-
[fhe Branch as an unexplained discrepancy
[fhe call summary is now
[Branch 011458 has an unexplained discrepancy
Jbate:26-Feb-2013 13:18:12 User:Anne Chambers
[Start of Response]
en they completed the balance on 6th Feb and cleared the loss from Local Suspense, the amount cleared was £9839.45 instead of
the loss they had put into local suspense, which was £39.57.
[his appears to be a consequence of something that happened during the previous TP rollover on 2nd Jan: a ‘gain to lc
lsuspense' of £9799.88 was included in the DEF opening figures.
I don't think any of the local suspense products should ever appear in opening figures, however I have found 14 such lines (all
prod 6295 Gain to LS, all different branches). Unfortunately all created Nov-Dec last year, so there is almost no remaining
counter evidence.
continuing to invetigate cause and implications.
[End of Response]
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
Response was delivered to Consumer
JDate:26-Feb-2013 13:33:23 User:Kevin McKeown
[fhe call Priority has been changed from ¢
fhe call Priority is now B
Jbate:26-Feb-2013 13:33:53 User:Anne Chambers
evidence Added - BRSS wing local suspens
oate: 26-Feb-2013 13:53:26 User:Anne Chambers
ie only keep opening figures for 3 old trading periods, so can't be sure when problem started.
bate: 26-Feb-2013 1
[Start of Response] <
sked Ibrahim at NBSC (~~ GRO if the Suspense ceport From 2nd Janliary is available < hel obtain it and email to HSD IMT.
[End of Response]
response code to call type L as Category 40 ~~ Pending ~- Incident Under Investigation
lkesponse was delivered to Consumer
5:35 Uscr:Anne Chambers
bate: 26-Feb-2013 16:51:32 Uscr:Anne Chambers
[Start of Response]
suspense report for TP9 (2nd Jan 2013) received, which shows no anomaly. I thought it might show 9799.88- c/f, since that amount
is b/f on the TP10 report, but it doesn't.
[the branch also sent the suspense report for TP10 2012, with the comment that they had the same problem last year - and although
jit is a very faint copy, it appears to show 9799.88- b/f-
FUJ00084852
FUJ00084852
Tend of Response]
lkesponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
lkesponse was delivered to Consumer
Jbate:26-Feb-2013 16:53:46 User:Anne Chambers
evidence Added -— h
Date: 26-Feb-2013 17:56:09 User:Anne Chambers
[Start of Response]
ltave asked what the branch did about the problem last year.
lAlso checking what the archiving strategy has been for BRDB_RX_SU_OPENING BALANCE in the past, and when it changed.
[End of Response]
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
lkesponse was delivered to Consumer
Jate:27-Feb-2013 16:18:08 User:Anne Chambers
evidence File Updated - Updated n extracts etc
jDate:27-Feb-2013 16:20:17 User:Anne Chambers
[Start of Response]
It have now found the cause of the problem: some data from autumn 2010 has been retained in table BRDB_RX BTS DATA, for 14
lseparate branches. These branches will all have been affected by this problem late 2011 and late 2012, though in some cases the
lamounts involved are small.
Isranch Affected TP AMOUNT
looz647 9 6.71
joozs40. 9 =—«:140.61
lo10007:«9-—s ~-0.01
jo1145a8 10-9, 799.88
joiz004 9916.12
jo54011 99 3.34
018329 «5.84
104937 9 =49.62
55025 9 =«~113.14
nSe71S 9.14.58
bi1e44. 9-41.77
243242 9 -0.51
266418 9 3,186.70
297611 9 160.92
[End of Response]
lkesponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
Iresponse was delivered to Consumer
Date:27-Feb-2013 16:22:43 Uscr:Anne Chambers
still to be investigate
Exactly how did these records cause the observed effect?
why were the records not removed by the normal archiving process?
HWwhat impact has the problem had on the branch accounts?
LWhat impact has the problem had on POLSAP?
[How do we remove the records to prevent future problems?
Were there any affected branches which have since closed?
There are 19 other branches which have old data in the affected table, but not relating to Local Suspense ? could this cause any
jproblems with the branch accounts? (some may be temporarily closed) .
Date:28-Feb-2013 14:06:00 User:Anne Chambers
[Start of Response]
Further investigations:
s* Exactly how did these records cause the observed effect?
he old data is picked up, along with the correct data, during the Branch Trading Statement production (at the end of the period
BEFORE the problem is visible at the branch). The old opening figure (which may be for one or more of the Local Suspense products
6295-6298, associated with an unknown stock unit) gets converted during branch rollover, to prod 6295 Gain to Local Suspense
(though the sign may be positive or negative), and written as an opening figure for the subsequent period, stock unit DEF.
lat the end of the second period, this is included when the amount to be cleared from Local Suspense is calculated (when the last
stock unit is rolled over), so the branch is forced to clear it.
** How to identify the problem from branch reports:
[Branch Trading Statement: the sum of the two Discrepancy Transferred lines does not match the total of the two Discrepancy
resolved Lines
suspense Account report: the B/Fwd figure on the report does not match the C/Fwd figure on the report for the previous TP.
* Why were the records not removed by the normal archiving process? The records, created Autumn 2010, belonged to stock units
that have since been deleted. Normally they would have been removed before the ‘deleted stock unit' entry itself was removed from
the list of stock units, but there were some teething problems with archiving and they were ‘orphaned' and are now ignored by the
larchiving process.
k* How do we remove the records to prevent future problems? Once well away from the problem TP, eg once into TP 1, get the
FUJ00084852
FUJ00084852
ranches to recreate a stock unit with the same name a5 the problem one, then delete it again. Of we just delete them from the
Jdatabase under MSC.
t+ Were there any affected branches which have since closed? T have checked branches closed within the last 90 days, all ok. For
ranches closed longer ago which might be under investigation, the suspense account reports and BTS could be checked (see above).
t+ There are 19 other branches which have old data in the affected table, but not relating to Local Suspense ? could this cause
jany problems with the branch accounts?
Ir have checked very carefully and conclude that these extra lines have no ongoing impact on the branch accounts.
‘* There is old data in some other tables that use the same archiving strategy - this doesn't affect the branch balancing in the
same way, but what would happen if a stock unit with the same name was recreated?
I** Any corrective actions?
Itocal suspense should always be zero when the branch is rolled over - should this be checked and reported?
I think the archiving strategy is now ok, but this may need to be reviewed.
still to a
+ What impact has the problem had on the branch accounts?
I‘* What impact has the problem had on POLSAP?
[End of Response]
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
Response was delivered to Consumer
oate:28-Feb-2013 14:24:24 User:Anne Chambers
[Start of Response]
correction:
* Exactly how did these records cause the observed effect?
[the old data is picked up, along with the correct data, during the Branch Trading Statement production (at the end of the period
IBEFORE the problem is visible at the branch). The ****old BTS data line**** (which may be for one or more of the Local Suspense
products 6295-6298, associated with an unknown stock unit) gets converted during branch rollover, to prod 6295 Gain to Local
suspense (though the sign may be positive or negative), and written as an opening figure for the subsequent period, stock unit
DEF.
it the end of the second period, this is included when the amount to be cleared from Local Suspense is calculated (when the last
jstock unit is rolled over), so the branch is forced to clear it.
[End of Response]
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
Response was delivered to Consumer
lDate:28-Feb-2013 17:17:58 User:Anne Chambers
Evidence File Updated - Another update of notes /
Joate:28-Feb-2013 17:18:31 User:Anne Chambers
evidence Added - Spreadsheat sent to POL
Date:06-Mar-2013 16:05:10 User:Anne Chambers
[Start of Response]
There was a conference call with POL (Laura Darby, Mark Wardle and others) on 28th Feb about this call, and the spreadsheet
showing the impact of the problem on the 14 branches was sent to them by Steve Bansal. We are waiting to hear from Mark whether
[this is sufficient information for them to resolve the consequences on the branches and POLSAP.
je will then need to get the old data causing the problem removed from the database (before TP 9 - Oct-Nov 2013) and consider
nether extra checks should be put in place to trap similar anomalies in the future.
[End of Response]
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
Response was delivered to Consumer
Date:08-Mar-2013 13:37:01 User:Anne Chambers
(Start of Response]
PoL will be arranging another conf call next week.
[End of Response]
Ikesponse code to call type lL as Category 40 -- Pending -- Incident Under Investigation
e was delivered to Consumer
Date: 08-Mar-2013 13:41:46 User:Anne Chambers
‘loning call so that we can get the old data removed..
Date:08-Max-2013 13:41:56 User:Anne Chambers
call has been cloned to Call:PC0224126 by User:Anne Chambers
jat¢:08-Mar-2013 15:21:37 Uscr:Anne Chambers
[Start of Response]
Cloned call PC0224126 sent to development to get old records removed from BRDB.
FUJ00084852
FUJ00084852
Tend of Response]
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
lkesponse was delivered to Consumer
bate:15-Mar-2013 11:10:18 User:Anne Chambers
lfarget Date/Time updated: new value is 22/03/2013 16:55
[Start of Response]
following another conf call Thurs 14th March, more information has been sent to POL.
[End of Response]
lkesponse code to call type L as Category 40
esponse was delivered to Consumer
Pending =~ Incident Under Investigation
jDate:15-Mar-2013 11:18:31 User:Anne Chambers
evidence Added - email, timeline example,
sheet sent to POL
other spre
bate: 20-Mar-2013 1
[Start of Response]
can we add an extra check into the branch balancing process so errors like this would be reported in future (similar to the event
hich is raised if the BTS Trading position is not zero)?
6:34 User:Anne Chambers
Possible checks are
la) do the next TP's Opening Figures, generated for stock unit DEF, include any Local Suspense products? (raise event if they
don't net to zero value)
lb) does the sum of the two Discrepancy Transferred lines on the BTS, for the Branch Total, equal the sum of the two Discrepancy
Resolved lines? (raise event if not).
ror the problem under investigation here, the first check would have identified a problem when branch 11458 rolled into TP 10,
land the second check at the end of TP 10.
[End of Response}
Response code to call type Lb as Category 40
Response was delivered to Consumer
Pending -- Incident Under Investigation
Date:20-Mar-2013 15:10:25 User:Anne Chambers
new Business Impact has been adde
[this change would alert support teams to the existence of a system problem affecting branch accounts, rather than having to wait
for it to be reported. Such a problem, affecting 14 branches, was not reported until 15 months after it first could have been
noticed.
date: 20-Mar-2013 15:20:28 User:Anne Chambers
{the Call record has been transferred to the team: BIF
Progress was delivered to Consumer
Dat e:26-Mar-2013 10:09:57 Uscr:Gareth Jenkins
routing Peak to GDC to add in alerts as requested by Anne
ambers in update timed at 2013-03-20 14:56:34.
date:26-Mar-2013 10:11:20 User:Gareth Jenkins
the Call record has been transferred to the team: xCtr GDC
lUser:Gareth Jenkins Confirmed that this Incident may be passed to the external company with the attached evidence.
progress was delivered to Consumer
joate: 26-Mar-2013 10:15:58 User:Ravindra Kumar
fhe Call record has been transferred to the team: xCtr_BAC_GDC
fhe Call record has been assigned to the Team Member: Leela Dhanalakshmi Nune
Progress was delivered to Consumer
JDate:27-Mar-2013 1:
0:55 Uscr:Leela Dhanalakshmi Nune
lAnalysis and Root cause:
lcenerally all Local suspense movement transactions are written during stock unit TP rollover (6295/6296) ,during last stock unit
rollover, and also from the Housekeeping menu (6297/6298) .
n office rollover, local suspense from branch opening figures and movements for all stock units are netted off, and should
result in 0 value carried forward.
hen Office rollover ,the previous suspense opening figures and suspense movements for current trading period are summed, netted
off, and written as new suspense opening figures to SU DEF.
in the present scenario, the previous local suspense movements for a deleted stockunit are retained in BRANCH_BTS DATA. (i.e
9799.88) .This Local suspense record was not cleared while next office rollover since SU was deleted.
lafter 205 days the stock unit was created with same name So sytem summed off old non-zero local suspense movements amount from
BRANCH BTS DATA along with Ls movements from present trading period. (i.e £9799.88 + £39.57 = £9839.45).
keproducing Steps:
h. Create a stock unit 'SU1'and attach to present user.
2. Carry out a local supense transaction by declaring cash £100 for SU1.
8, Rollover all stockunits to next TP.
4. Attach user to another stock unit and delete stockunit SU1.
FUJ00084852
FUJ00084852
Change system date to after 205 days.
Carry out a local supense transaction by declaring stock £23 for present. SU.
- Create a stock unit with same name which is deleted ‘SU1'.
- Rollover office to next Tp.
ho. Suspense Roport and Office Trading statement shows total clearted amount for current TP
SS SISH
Rollover Office to next TP.(Here system doesn't complain about LS record of SUl since 1b was deleted.)
is £123. (Bvidence attached).
jate:27-Mar-2013 13:22:50 Uscr:Leela Dhanalakshmi Nune
ction placed on Team:xCtr BAC GDC, User:Leela Dhanalakshmi Nune
jbate:27-Mar-2013 13:25:45 User:Leela Dhanalakshmi Nune
the Call record has been assigned to the Team Member: Ravindra Kumar
Progress was delivered to Consumer
Date:27-Mar-2013 13:26:16 User:Leela Dhanalakshmi Nune
Please review.
JDatc:27-Mar-2013 13:36:56 Uscr:Leela Dhanalakshmi Nune
evidence Added - evidence
joate:02-Apr-2013 11:37:15 User:Ravindra Kumar
lanalysis is fine. Please put the fix impact template.
Date:02-Apr-2013 11:37:32 User:Ravindra Kumar
[the Call record has been assigned to the Team Member: Leela Dhanalakshmi Nune
Progress was delivered to Consumer
Oate:03-Apr-2013 1
[Start of Response]
Product error diagnosed.
[End of Response]
Response code to call type L as Category 41 -- Pending -- Product Error Diagnosed
lkesponse was delivered to Consumer
8:49 Uscr:Leela Dhanalakshmi Nune
Jate:16-Apr-2013 07:24:44 User:Sarita Pujari
Action has been removed from the call
joate:18-Apr-2013 08:34:22 User:Leela Dhanalakshmi Nune
[DEVELOPMENT IMPACT OF PIX:
SPECIFY THE HNG-X PLATFORMS IMPACTE!
counter.
TECHNICAL SUMMARY;
[this change will affect counter pdl files.
IS? OF KNOWN DIMENSIONS DESIGN PARTS AFFECTED BY THE CHANG!
jone
DEPENDENCIES:
jone
DEPLOYMENT DETATL:
None
EV EFFORT IN MANDAYS:
2 days for Development + testing
IMPACT ON USER:
lan Error prompt will be shown to the user when next TP opening figures of DEF SU conatins any non zero Localsuspense movements.
lanother error prompt will be shown when the sum of the two Discrepancy Transferred lines on the BTS, for the Branch Total, Not
lequal the sum of the two Discrepancy Resolved lines.
[fhe purpose of these Error Events is to alert the support teams that something has occurred that shouldn?t have done so that they
can investigate it quickly.
HMPACT ON OPERATIONS:
impact is medium as previous local suspense movemnets of a deleted SU are processing in present TP when same SU is created again.
ser will be surprised with discrepancy of local suspense figures which is not for done for
]ZAVE RELEVANT KELS BEEN CREATED OR UPDATED?
the current TP.
FUJ00084852
FUJ00084852
aE to be created:
HMPACT ON TEST:
lExaplained testing steps above.
RISKS (of releasing and of not releasing proposed fix):
isk is low since there is two events wil be added.
jate:24-Apr-2013 1. Leela Dhanalakshmi Nune
IMPACT ON USER
Jan Error event will be generated when next TP opening figures of DEF SU conatins any non zero Localsuspense movements.
lancther error event will be generated when the sum of the two Discrepancy Transferred lines on the BTS, for the Branch Total, Not
lequal the sum of the two Discrepancy Resolved lines.
the purpose of these Error Events is to alert the support teams that something has occurred that shouldn?t have done so that they
can investigate it quickly.
[Date:24-Apr-2013 1:
lAction placed on Team:xC
6:47 User:Leela Dhanalakshmi Nune
r_BAC_GDC, User:Leela Dhanalakshmi Nune
Date:24-Apr-2013 13:46:59 User:Leela Dhanalakshmi Nune
fhe Call record has been assigned to the Team Member: Ravindra Kumar
progress was delivered to Consumer
[Date:24-Apr-2013 1:
Please Review.
7:25 User:Leela Dhanalakshmi Nune
Joate:17-May-2013 09:32:37 User:Ravindra Kumar
k With Analysis.
JDate:17-May-2013 09:32:48 User:Ravindra Kumar
[fhe Call record has been assigned to the Team Member: Leela Dhanalakshmi Nune
progress was delivered to Consumer
JDate:17-May-2013 11:09:50 Uscr:Ravindra Kumar
the call Target Release has been moved to Proposed For —- HNG-X 08.82
jate:17-May-2013 11:11:56 User:Ravindra Kumar
ction has been removed from the call
bate:17-May-2013 11:17:19 User:Ravindra Kumar
Action placed on Team:RelMngmnt Forum
JDate:20-May-2013 14:48:07 Uscr:ou Barham
[the call Target Release has been moved to Targeted At -- HNG-X 08.82
bate: 20-May-2013 14:48:27 User:Lou Barham
targeted in PTF as requested
JDate:20-May-2013 14:48:32 Uscr:Lou Barham
lAction has been removed from the call
oate:19-dun-2013 12:31:55 User:Jon Hulme
the design is to raise events on brar
la) ‘The next TP's Opening Figures, generated for stock unit DEF, include Local Suspense products that don't net to zero value.
) The sum of the two Discrepancy Transferred lines on the BTS, for the Branch Total, do not equal the sum of the two Discrepancy
Resolved lines.
rollover if:
the design is to follow the same pattern as the TradingPositionNotEqualfozero error and event created when the BTS trading
sition is non zero (see btsManagement InfoSummaySection_v2Template.vmxml, ReportingHelperBLO.java and Account ingReportBLO.pdl),
Tard en 1
lso 2 new system errors to be logged at error level, and two new deferred events. The new events will not appear on the counter
levent log report.
suggested system errors:
FUJ00084852
FUJ00084852
IRRELEVANT
levent ids:
124 "The branch local suspense opening figures for TP %TP% do not net to zero.”
h25 “fhe BTS branch discrepancy transferred totals do not match the branch discrepancy resolved totals."
[the event id spreadsheet in now formally held in Dimensions as DES/APP/HLD/2255, Please can you update
‘TRRECEVANT to refer to this HLD - half way
down the page it has a Vink to the old events spreadsheet in project web - think [ink Should be removed and the reader referred
to DES/APP/HLD/2255 in Dimensions.
Date:48-dul-2013 15:42:09 User:Leela Dhanalakshmi Nune
evidence Added - code 3
jbate:18-Jul-2013 15:42:32 Uscr:Leela Dhanalakshmi Nune
Action placed on Team:xCtr BAC GDC, User:Leela Dhanalakshmi Nune
jate:18-Jul-2013 15:42:44 User:Leela Dhanalakshmi Nune
the Call record has been assigned to the Team Member: Venkata Peddapothula
Progress was delivered to Consumer
bate:48-Jul-2013 15:43:06 Uscr:Leela Dhanalakshmi Nune
Please review code patches.
loate:26-dul-2013 07:24:53 User:Leela Dhanalakshmi Nune
evidence Added - Revised code patches.
jbate:26-dul-2013 08:12:56 Uscr:Leela Dhanalakshmi Nune
lNGX CODE FIX
FIX DESCRIPTION
explained above.
PROPOSED BRANCH
crR0g_82_00_RELEASE
COUNTER JAVA FILES CHANGED
Report ingConstants. java
Report ingle lperBLO. java
lol loverBranchBLO. java
COUNTER PDL FILES CHANGED
BalanceBranchBLO.pdl
lAccount ingReportBLO.pdl
COUNTER REFDATA FILES CHANGED
jew Message file added MSG31332.xm1
st sManagement InfoSummarySection_v2Template.vmxml
SHARED CODE FILES CHANGED
None
IBAL JAVA CODE FILES CHANGED
jone.
SQL FILES CHANGED
None
OTHER FILES CHANGED
jerrormessages .properties.
PPROPRIATE CODE COMMENTS
ves.
[DEPENDENCIES
[there is a new message file added i.e MSG31332.xml.
RELATED PROBLEMS
jone
IT TESTING EVIDENCE
ttached above along with Revised code patches.
Ik:nGRESSION TEST CLASS
Attached.
BACKWARDS COMPATIBILITY
A.
FUJ00084852
FUJ00084852
IDate:26-dul-2013 08:23:25 User:Leela Dhanalakshmi Nune
evidence Added - Kegression Te. a
[Date:26-Jul-2013 14:03:56 Uscr:Venkata Peddapothula
code looks fine. Please go ahead with the fix
Date: 26-dul-2013 14:05:06 User:Venkata Peddapothula
[Start of Response]
[End of Response]
lkesponse code to call type L as Category 46 -- Pending -- Product Error Fixed
kesponse was delivered to Consumer
Jbate:29-Jul-2013 08:31:34 Uscr:Leela Dhanalakshmi Nune
[the Call record has been assigned to the Team Member: Leela Dhanalakshmi Nune
Progress was delivered to Consumer
Date:29-dul-2013 10:18:21 User:Leela Dhanalakshmi Nune
committed the following files to branch CTRO8 82 00 RELEASE.
Ikeport inglielperBLO. java! H
Ikol loverBranchBLO. java {
[Report ingConstants. jav.
ccount ingReport BLO. pd:
Ba lanceBranchBLO.pdi I
jot sManagement InfoSummaryS
lerrormessages .properti
J_IRRELEVANT 3
IRRELEVANT I
RELEVANT
jDate:29-dul-2013 10:18:54 Uscr:Leela Dhanalakshmi Nune
[the Call record has been transferred to the team: xCtr_REL GDC
Progress was delivered to Consumer
jate:02-Aug-2013 15:34:39 User:Vikaran Bhan
Reference Added: Problem Incident CTR APP X0882_V450
Date:02-Aug-2013 15:34:43 User:Vikaran Bhan
tor Reference set to: Problem Incident CTR APP _x0882_V450
jDate:02-Aug-2013 15:35:23 User:Vikaran Bhan
Reference Added: Problem Incident CTR APP X0882 V450
Date: 08-Aug-2013 08:40:33 Uscr:Pavan Vejendla
hile testing this peak we observed an issue while doing the stock unit roll over.Use case is getting stopped in between and
returning to home.
Date: 08-Aug-2013 0
[Start of Response]
changing the status and returning to dev
[End of Response]
Response code to call type L as Category 50 -- Pending -- Fix Failed
lkesponse was delivered to Consumer
2:05 Uscr:Pavan Vejendla
Date:08-Aug-2013 08:42:25 Uscr:Pavan Vejendla
the Call record has been transferred to the team: xCtr_BAC_GDC
the Call record has been assigned to the Team Member: [eela Dhanalakshmi Nune
Progress was delivered to Consumer
bate: 08-Aug-2013 1
[Start of Response]
status is changed as the issue is because of peak fix PC0222229.
[End of Response]
lkesponse code to call type L as Category 46 -- Pending -- Product Error Fixed
Response was delivered to Consumer
8:07 User:Leela Dhanalakshmi Nune
Date: 08-Aug-2013 10:08:38 Uscr:Leela Dhanalakshmi Nune
fhe Call record has been transferred to the team: xCtr_REL_GDC
[fhe Call record has been assigned to the Team Member: Pavan Vejendla
FUJ00084852
FUJ00084852
Progress was delivered to consumer
JDate:09-Aug-2013 14:24:59 User:Vikaran Bhan
laction has been removed from the call
jate:09-Aug-2013 16:22:03 User:Vikaran Bhan
Defect cause updated to 14: Development - Code
oate:09-Aug-2013 16:22:24 User:Vikaran Bhan
the Call record has been transferred to the team: Dev-Int-Rel
User:Vikaran Bhan Confirmed that this Incident may be passed to the external company with the attached evidence.
Progress was delivered to Consumer
Date:12-Aug-2013 14:59:29 User:Matt Swain
Reference Added: Product Baseline CTR _APP_X0900_V470-V435
cTR_APP_X0900_V470-V435 available for testing
the Call record has been transferred to the team: Live Support Team
fhe Call record has been assigned to the Team Member: Unassigned_
Joate: 20-Aug-2013 14:22:17 User:Lorraine Guiblin
the call Target Release has been moved to Targeted At -- HNG-X 09.00.03.00SV&I Cycle 3
Jbate:20-Aug-2013 14:22:23 User:Lorraine Guiblin
lke targeted outside PTF as discussed in release planning
jDate:415-Oct-2013 14:27:14 User:John Budworth
Reference Added: Release PEAK PCO228641
Date:23-Oct-2013 1
[Start of Response]
tested with Anne Chambers using COUNTER APP 74 2 (LST R9.01.00.40
the behaviour of the Counter app now, on encountering such historic data, is that:
H. No messages warning of the problem are displayed when rolling an affected Counter, including rolling the last Counter
2. Following the Counter rolls, the Local Suspense includes the historic data
3. When rolling the Branch, message MSG31332 is displayed to alert the PM that "Dis
atch" and that the PM needs to report this
4. The Branch roll can complete, including the erroneous data
Once the PM reports the problem to the Help Desk, the call should be transferred to Fujitsu to resolve. The point at which the
problem is noted is at the time it arises, rather than a year later.
closing PEAK with Anne's agreement.
[End of Response]
Response code to call type L as Category 60
routing to Call Logger following Final Progress update.
lkesponse was delivered to Consumer
8:20 User:Andy Pavis
crepancies for Transferred and Resolved do not
Final -
S/W Fix Available to Call Logger
jDate:23-Oct-2013 17:30:09 User:Lina Kiang
the Call record has been assigned to the Team Member: Anne Chambers
Progress was delivered to Consumer
Date: 24-Oct-2013 18:30:59 Uscr:Anne Chambers
{Start of Response]
the original problem was fully investigated and resolved several months ago. We have now added a couple of new checks to the
balancing process, to alert us if anything similar happens again. KEL raised to document what to do if the events are seen.
closing call.
[End of Response]
Response code to call type L as Category 60 -- Final -
outing to Call Logger following Final Progress update.
service Response was delivered to Consumer
S/W Fix Available to Call Logger
Date: 24-Oct-2013 18:30:59 User:Anne Chambers
CALL PC0223870 closed: Category 60 Type L
bat e:25-Oct-2013 11:08:42 User:Gheryl Card
L acha2230K authoris:
Root Cause Development - Code
Logger _Customer Call_ -- EDSC
Subject Product General/Other/Misc -- Unknown General/Other/Misc (version unspecified)
FUJ00084852
FUJ00084852
Assignee _Customer Call_ -- EDSC
Last Progress 25-Oct-2013 11:08 -- Cheryl Card