FUJ00081875
FUJ00081875
Peak Incident Management System
Call Reference PC0223870 Call Logger _Customer Call -- EDSC
Release ee At= TINGS 090003008V81 CTR_APP_X0900_V470-V435
Call Type Live Incidents/Defects Priority B -- Business restricted
Contac EDSC Call Status Closed -- S/W Fix Available to Call
— ; Logger
Target Date 22/03/2013 Ean y
Days)
Summary Branch 011458 has an unexplained discrepancy
All References Type Value
DevIntRel-Director Live Supp.Test
Release PEAK PC0228641
Product Baseline CTR_APP_X0900_V470-V435
TRIOLE for Service A2401368
Clone Call PC0224126
Problem Incident CTR APP _X0882_V450
SSCKEL KEL acha2230K
Problem Incident CTR_APP_X0882_V450
SSCKEL KEL acha2230K
Collections Name User Date
: BIFApproved Lorraine Elliott 25-Mar-2013 11:43:17
Be 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
:The Branch as an unexplained discrepancy
call Type:L
fall Priority:c¢
ffarget Release: HNG-X R6.50
jouted to:EDSC - Unassigned
jDate:25-Feb-2013 16:55:52 User: Customer Call_
HNCIDENT MANAGEMENT
[Date/Time Raised: Feb 25 2013 4:51PM
riority: ¢
contact Name:
Contact Phon
riginator: XxX
Originator's reference: A2401368
Product. Serial No:
[Product Site: 011458
Ibrahim at NB!
Iransfer Note: Transfer Group from 'POA-HSD IMT' to 'POA-FJ-PEAK’
@ Branch as an unexp
d with a
tuspense was much higher £9839.45.
xr removed from housekeeping/local suspense account.
ined discrepancy. They balanced and rolled trading period on 6 Feb,
of £39.57 which was transferred to local suspense however the figure that was cleared out from local
It 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
Hiscrepancy resolved £9839.45. The transaction log completed for all transaction does not show any other figures being entered into
they have one stock unit AA and this
FUJ00081875
FUJ00081875
jode 1
6/02/2013 16:50 to 16:51
A TP 10 BP4/5
HASOOL
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
b013-02-25 16:54:19 [ Richardson, Mark }
neut_en poa : Transfer Notification
2013-02-25 16:54:54 [ Richardson, Mark ]
neut_en_poa : Transfer Notification
Jbate:25-Feb-2013 16:59:22 User:Clive Turrell
Product General/Other/Misc ~~ Unknown General/Other/Misc (version unspecified) added.
pate:25-Feb-2013 17:02:16 User:Clive Turrell
the Call record has been assigned to the Team Member: Anne Chambers
Progress was delivered to Consumer
joate:25-Feb-2013 17:47:51 User:Anne Chambers
Whe call summary has been changed from
he Branch as an unexplained dis
fhe call summary is no
branch 011458 has an unexplained discrepancy
JDate:26-Feb-2013 13:18:12 User:Anne Chambers
[Start of Response]
nen they completed the balance on 6th Feb and cleared the loss from Local Suspense, the amount cleared was £9839.45 instead of thel
floss they had put into local suspense, which was £39.57.
This appears to be a consequence of something that happened during the previous TP rollover on 2nd Jan: a ‘gain to local suspense!
ff £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
rod 6295 Gain to LS, all different branches). Unfortunately all created Nov-Dec last year, so there is almost no remaining counter]
lbvidence.
continuing to invetigate cause and implications.
[End of Response]
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
esponse was delivered to Consumer
Date:26-Feb-2015 13:33:23 User: Kevin McKeown
fhe call Priority has been changed from C
fhe call Priority is now B
jbate:26-Feb-2013 13:53:26 User:Anne Chambers
IWe only keep opening figures for 3 old trading periods, so can't be sure when problem started.
t6:26-Feb-2013 14:55:35 User:Anne Chambers
[Start of Response] ,.
Asked Ibrahim at nssc! GRO
[End of Response] ‘
esponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
esponse was delivered to Consumer
I
{if the suspense report from 2nd January is available - he'll obtain it and email to HSD IMT.
€e: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 ig
p/f on the TP10 report, but it doesn't.
whe branch also sent the suspense report for TP10 2012, with the comment that they had the same problem last year - and although it]
is a very faint copy, it appears to show 9799.88- b/f.
FUJ00081875
FUJ00081875
Tend of Responsel
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
esponse was delivered to Consumer
Date:26-Feb-2013 16:53:46 User:Anne Chambers
l:vidence Added - Branct ts
pense rep:
(fo:26-Feb-2013 17:56:09 User:Anne Chambers
[Start of Response]
Have asked what the branch did about the problem last year.
Also checking what the archiving strategy has been for BRDB_RX_SU_OPENING_BALANC
[End of Response]
lesponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
lkesponse was delivered to Consumer
in the past, and when it changed.
‘te:27-Feb-2013 16:18:08 Usor:Anne Chambers
lsvidence File Updated - Upd.
lated notes
jDate:27-Feb-2013 16:20:17 User:Anne Chambers
[Start of Response]
I have now found the cause of the problem: some data from autumn 2010 has been retained in table BRDB RX BTS DATA, for 14 separate
branches. These branches will all have been affected by this problem late 2011 and late 2012, though in Some cases the amounts
involved are small.
ranch Affected TP AMOUNT
02647 9-6. 71
02840 9 «140.61
10007 9 = -0.01
11458 10 «= -9, 799.88
12004. 9 16.12
54011 9 3.34
o1s32 95.84
04937 9-49.62
55025 9 -113.14
H56715 9 (11.55
bi1sa4. 9-41.77
43242 9 -0.51
beesis 9 3,186.70
b97611 9 160.92
[End of Response]
esponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
esponse was delivered to Consumer
(to:27-Feb-2015 16:22:43 User:Anne Chambers
Still to be investigated:
FExactly how did these records cause the observed effect?
Lihy were the records not removed by the normal archiving process?
Hwhat impact has the problem had on the branch accounts?
HWhat impact has the problem had on POLSAP?
[How do we remove the records to prevent future problems?
Here there any affected branches which have since closed?
There are 19 other branches which have old data in the aff.
problems with the branch accounts? (some may be temporarily c
ed table, but not relating to Local Suspense ? could this cause any
osed) «
(e:28-Feb-2013 14:06:00 User:Anne Chambers
[Start of Response]
Further investigations:
* Exactly how did these records cause the observed effect?
Ihe 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
Jat 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.
b+ 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 ResolvedI
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
h* 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
hist of stock units, but there were some teething problems with archiving and they were ‘orphaned’ and are now ignored by the
rchiving process.
t+ How do we remove the records to prevent future problems? Once well away from the problem TP, eg once into TP 1, get the branchesI
FUJ00081875
FUJ00081875
fo recreate a Stock unit with the Same name as the problem one, then delete It again. OF we just delete them from the database
inder MSC.
It* Were there any affected branches which have since closed? I 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).
H+ There are 19 other branches whi
roblems with the branch accounts?
Ir have checked very carefully and conclude that these extra lines have no ongoing impact on the branch accounts.
have old data in the affected table, but not relating to Local Suspense ? could this
ean’
t+ 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?
* Any corrective actions?
Local suspense should always be zero when the branch is rolled over - should this be checked and reported?
It think the archiving strategy is now ok, but this may need to be reviewed.
still to do:
'* what impact has the problem had on the branch accounts?
f+ What impact has the problem had on POLSAP?
[End of Response]
esponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
lkesponse was delivered to Consumer
Date: 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
BEFORE the problem is visible at the branch). The ****old BTS data line**** (which may be for one or more of the Local Suspense
3 6295-6298, associated with an unknown stock unit) gets converted during branch rollover, to pred 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.I
produc!
At 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.
[End of Response]
esponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
esponse was delivered to Consumer
jbate:28-Feb-2013 17:17:58 User:Anne Chambers
evidence File Updated - Anoth:
update of n
Date:28-Feb-2013 17:18:31 User:Anne Chambers
evidence Added = ads! 2 BOL
jate: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
he 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.
le will then need to get the old data causing the problem removed from the database (before TP 9 ~ Oct-Nov 2013) and consider
ihether 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
esponse was delivered to Consumer
fe:08-Mar-2013 13:37:01 User:Anne Chambers
[Start of Response]
OL will be arranging another conf call next week.
[End of Response]
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
esponse was delivered to Cc
sumer
e:08-Mar-2013 13:41:46 User:Anne Chambers
cloning call so that we can get the old data removed....
Te:08-Mar-2013 13:41:56 User:Anne Chambers
call has been cloned to Call:PC0224126 by User:Anne Chambers
[Date:08-Max-2013 15:21:37 Uscr:Anne Chambers
[Start of Response]
Cloned call PC0224126 sent to development to get old records removed from BRDB.
[End_of Response]
FUJ00081875
FUJ00081875
Fesponse code to call type b as Category 40 -- Pending => Incident Under Tnvestigation
kesponse was delivered to Consumer
te:15-Mar-2013 11:10:18 User:Anne Chambers
farget 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]
esponse code to call type L as Category 40 -- Pending ~~ Incident Under Investigation
esponse was delivered to Consumer
[Date:45-Mar-2013 11:18:31 User:Anne Chambers
evidence Added - email, timeline example
[e:20-Mar-2013 14:56:34 Uscr:Anne Chambers
[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)?
ossible checks are
ls) 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 Discrepanc:
esolved lines? (raise event if not).
For the problem under investigation here, the first check would have identified a problem when branch 11458 rolled into TP 10, and
the second check at the end of TP 10.
[End of Response]
lkesponse code to call type L as Category 40 -- Pending -- Incident Under Investigation
esponse was delivered to Consumer
6:20-Mar-2013 15:10:25 User:Anne Chambers
J new Business Impact has been added:
[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.
pate :20-Mar-2013 15:20:28 User:Anne Chambers
[the Call record has been transferred to the team: BIF
progress was delivered to Consumer
[Date:26-Mar-2013 10:09:57 User:Gareth Jenkins
outing Peak to GDC to add in alerts as requested by Anne Chambers in update timed at 2013-03-20 14:56:34.
[Date:26-Mar-2013 10:11:20 Uscr:Gareth Jenkins
the Call record has been transferred to the team: xCtr_GDC
User:Gareth Jenkins Confirmed that this Incident may be passed to the external company with the attached evidenci
rogress was delivered to Consumer
jDate:26-Mar-2013 10:15:58 User:Ravindra Kumar
[the 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
[Date:27-Max-2013 13:20:55 Uscr:Leela Dhanalakshmi Nune
nalysis and Root caus:
lbenerally all Local suspense movement transactions are written during stock unit TP rollover (6295/6296) ,during last stock unit
ollover, and also from the Housekeeping menu (6297/6298) -
On 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.
en Office rollover ,the previous suspense opening figures and suspense movements for current trading period are summed, netted
££, 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.
fter 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).
eproducing Steps:
h. Create a stock unit 'SUl'and attach to present user.
b. Carry out a local supense transaction by declaring cash £100 for SUl.
Bb. Rollover all stockunits to next TP.
4. Attach user to another stock unit and delete stockunit SU1.
5. Rollover Office to next TP. (Here system doesn't complain about LS record of SU1 since it was deleted.)
FUJ00081875
FUJ00081875
e- 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'.
Io. Rollover office to next Tp.
HO. Suspense Roport and Office
ading statement shows total clearted amount for current TP is £123. (Evidence attached) .
Date:27-Mar-2013 13:22:50 Uscr:Leela Dhanalakshmi Nune
ction placed on Team:xCtr BAC GNC, User:Leela Dhanalakshmi Nune
Date: 27-Mar-2013 13:25:45 Uscr:Leela Dhanalakshmi Nune
[fhe Call record has been assigned to the Team Member: Ravindra Kumar
rogress was delivered to Consumer
jate:27-Mar-2013 13:26:16 User:Leela Dhanalakshmi Nune
please review.
Date:27-Mar-2013 13:36:56 User:Leela Dhanalakshmi Nune
Added = cv idence
Ividenc
jbate:02-Apr-2013 11:37:15 User:Ravindra Kumar
lnalysis is fine. Please put the fix impact template.
te:02-Apr-2013 11:37:32 Uscr:Ravindra Kumar
Whe Call record has been assigned to the Team Member: Leela Dhanalakshmi Nune
Progress was delivered to Consumer
Date:03-Apr-2013 15:08:49 Uscr:Leela Dhanalakshmi Nune
[Start of Response]
oduct error diagnosed.
[End of Response]
esponse code to call type L as Category 41 ~~ Pending
Response was delivered to Consume:
Product Error Diagnosed
ate:d6-Apr-2013 07:24:44 User:Sarita Pujari
ction has been removed from the call
Date?i8-Apr-2013 08:34:22 Uscr:Leela Dhanalakshmi Nune
EVELOPMENT IMPACT OF FIX:
SPECIFY THE HNG-X PLATFORMS IMPACTED:
counter «
[TECHNICAL SUMMARY:
Hhis change will affect counter pdl files.
LIST OF KNOWN DIMENSIONS DESIGN PARTS AFFECTED BY THE CHANGE:
lone
EPENDENCL.
jone
EPLOYMENT DETAIL:
DEV EFFORT IN MANDAYS
days for Development + testing
IMPACT ON USER:
An Error prompt will be shown to the user when next TP opening figures of DEF SU conatins any non zero Localsuspense movements.
Another error prompt will be shown when the sum of the two Discrepancy Transferred lines on the BTS, for the Branch Total, Not
lcqual the sum of the two Discrepancy Resolved lines.
[he purpose of these Error Events is to alert the support teams that something has oc
can investigate it quickly.
rred that shouldn?t have done so that they
IMPACT 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 the current TP.
HAVE RELEVANT KELS §
et to be created,
REATED OR UPDATED?
FUJ00081875
FUJ00081875
IMPACT ON TEST:
Ixaplained testing steps above.
RISKS (of releasing and of not releasing proposed fix):
isk is low since there is two events wil be added.
jpate:24-Apr-2013 13:46:20 User
IMPACT ON USER:
n Error event will be generated when next TP opening figures of DEF SU conatins any non zero Localsuspense movements.
nother error event will be generated when the sum of the two Discrepancy Transferred lines on the BTS, for the Branch Total, Not
equal the sum of the two Discrepancy Resolved lines.
[the purpose of these Error Events is to alert the support teams that something has
can investigate it quickly.
‘Leela Dhanalakshmi Nune
rred that shouldn?t have done so that they
Date:24-Apr-2013 13:46:47 Uscr:Leela Dhanalakshmi Nune
ction placed on Team:xCtr BAC GDC, User:Leela Dhanalakshmi Nune
[pate:24-Apr-2013 13:46:59 Uscr:Leela Dhanalakshmi Nune
he Call record has been assigned to the Team Member: Ravindra Kumar
s was delivered to Consumer
rogres
Te:24-Apr-2013 1
Please Review
7:25 User:Leela Dhanalakshmi Nune
Date:i7-May-2013 09:32:37 User:Ravindra Kumar
k With Analysis.
[Date:d?-May-2013 09:32:48 Uscr:Ravindra Kumar
he Call record has been assigned to the Team Member: Leela Dhanalakshmi Nune
s was delivered to Consumer
ogres
terl7-May-2013 11:09:50 User:Ravindra Kumar
[the call Target Release has been moved to Proposed For -- HNG-X 08.82
Date:17-May-2013 11:11:56 User:Ravindra Kumar
ction has been removed from the call
ate: 7-May-2013 11:17:19 User:Ravindra Kumar
Action placed on Team:RelMngmntForum
jDate:20-May-2013 14:48:07 User:Lou Barham
the call Target Release has been moved to Targeted At -- HNG-X 08.82
Date:20-May-2013 14:48:27 User:Lou Barham
ffargeted in PTF as requested
Ce:20-May-2013 14:48:32 User:Lou Barham
ction has been removed from the call
Jbate:19-sun-2013 1:
[the design is to raise events on branch rollover if:
) The next IP's Opening Figures, generated for hat don't net to zero value.
p) ‘The sum of the two Discrepancy Transferred lines on the BTS, for the Branch Total, do not equal the sum of the two Discrepancy
esolved lines.
ock unit DEF, include Local Suspense product
The design is to follow the same pattern as the TradingPositionNotEqualToZero error and event created when the BIS trading position]
fis non zero (see btsManagement InfoSummaySect ion_v2Template.vmxml, Report ingHelperBLO. java and AccountingReportBLO.pdl), ive. error
"0903.com. fujitsu.poa.ctrc.businesslogic.reporting.nonZeroTradingPosition" and event id 117.
Iso 2 new system errors to be logged at error level, and two new deferred events. The new events will not appear on the counter
vent log report.
suggested system errors:
'0904.com. fujitsu.poa.ctre.businesslogic.report.ing .nonZeroLocal SuspenseBranchOpeningFigures"
"0905.com. fujitsu.poa.ctre. business logic. reporting .mismatchedBTSdi screpancyTransferredandResolved"
FUJ00081875
FUJ00081875
event ids:
N24 "The branch local suspense opening figures for TP $TP% do not net to zero."
N25 “The BTS branch discrepancy transferred totals do not match the branch discrepancy resolved totals."
[fhe event id spreadsheet in now formally held in Dimensions as DES/APP/HLD/2255. Please can you update
http: //10.182.7.102/doku/doku. php?id=appserv:recordbusinessevent _190&s=record$20business%20event to refer to this HLD — half way
own the page it has a link to the old events spreadsheet in project web - think link should be removed and the reader referred to
DES/APP/HLD/2255 in Dimensions.
Date:18-Jul-2013 15:42:09 Uscr:Leela Dhanalakshmi Nune
Evidence Added ~ code patch
‘te:18-Jul-2013 15:42:32 User:Leela Dhanalakshmi Nune
ction placed on Team:xCtr BAC GDC, User:Leela Dhanalakshmi Nune
Jate?18-Jul-2013 15:42:44 Uscr:Leela Dhanalakshmi Nune
[fhe Call record has been assigned to the Team Member: Venkata Peddapothula
progress was delivered to Consumer
jbate:18-sul-2013 15:43:06 Uscr:Leela Dhanalakshmi Nune
Please review code patches.
[Date:26-Jul-2013 07:24:53 Uscr:Leela Dhanalakshmi Nune
evidence Added ~ Revised code patches.
Te:26-Jul-2013 0
WNGX CODE FIX
2:56 User:Leela Dhanalakshmi Nune
FIX DESCRIPTION
explained above.
PROPOSED BRANCH
TROB 82 _00_RELEASE
COUNTER JAVA FILES CHANGED
eport ingConstants.java
eport ingle lperBLO. java
rol loverBranchBLO. java
COUNTER PDL FILES CHANGED
a lanceBranchBLO.pdl
count ingReport BLO. pal
COUNTER REFDATA FILES CHANGED
lew Message file added MSG31332. xml
ptsManagementInfoSummarySect ion_v2Template. vmxm1
SHARED CODE FILES CHANGED
IAL JAVA CODE FILES CHANGED
jone.
SQL FILES CHANGED
[OTHER FILES CHANGED
lerrormessages.properties.
PPROPRIATE CODE COMMENTS
es «
DEPENDENCIES
[here is a new me: MSG31332.xml.
sage file added i.
RELATED PROBLE!
one
INIT TESTING EVIDENCE
Attached above along with Revised code patches.
EGRESSION TEST CLASS
ttached.
Bac
A.
KWARDS COMPATIBILITY
FUJ00081875
FUJ00081875
Date:26-Jul-2013 0!
evidence Added - 5:
dence &
ate:26-Jul-2013 14:03:56 User:Venkata Peddapothula
Code looks fine. Please go ahead with the fi
[Date:26-gul-2013 1
[Start of Response]
5:06 User: Venkata Peddapothula
[End of Response]
jesponse code to call type L as Category 46 -- Pending -- Product Error Fixed
Response was delivered to Consumer
Date:29-dul-2013 0
[fhe Call re igned to the Team Member: Leela Dhanalakshmi Nune
ogress was delivered to Consumer
i:34 User:beela Dhanalakshmi Nune
rd has been as
jbate:29-sul-2013 10:18:21 User:Leela Dhanalakshmi Nune
‘omitted the following files to branch CTR08_82_00_ RELEASE.
ReportingHelperBLO.java 1.38.16.1
ol loverBranchBLO. java 1.10.130.1
Report ingConstants.java 1.14.330.1
\ccount ingReportBLO.pdl 1.18.272.1
BalanceBranchBLO-pdl 1.14.130.1
t sManagement InfoSummarySect ion_v21
lbrrormessages.properties 1.148.2.1
mplate.vmxnml 1.2.278
‘ommitted the following files to branch REFDATAO8 82 00 RELEASE.
1SG31332.xml 1.1.2.1
[Date:29-sul-2013 1
[the Call record has been transferred to the team: xC
18:54 User:Leela Dhanalakshmi Nune
rv REL GDC
progress was delivered to Consumer
Date:02-Aug-2013 15:34:39 User:Vikaran Bhan
leference Added: Problem Incident CTR APP X0882_v450
[Date:02-Aug-2013 15:34:43 Uscr:Vikaran Bhan
[TOP Reference set to: Problem Incident CTR APP Xt
0882 _V450
jbate:02-Aug-2013 15:35:23 User:Vikaran Bhan
eference Added: Problem Incident CTR APP_X0882_V450
ate: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
Ieturning to home.
getting stopped in between and
[pate:08-Aug-2013 08:42:05 Uscr: Pavan Vejendla
[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
[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: Leela Dhanalakshmi Nune
Progress was delivered to Consumer
[Date:08-Aug-2013 10:08:07 Uscr:Leela Dhanalakehmi Nune
[Start of Response]
Status is changed as the issue is because of peak fix PC0222229.
[End of Response]
Response code to call type L as Category 46 -- Pending ~~ Product Error Fixed
esponse was delivered to Consumer
jDate:08-Aug-2013 10:08:38 Uscr:Leela Dhanalakshmi Nune
the Call record has been transferred to the team: xCtr_REL_GDc
fhe Call record has been assigned to the Team Member: Pavan Vejendla
ogress was delivered to Consumer
FUJ00081875
FUJ00081875
[ater0S-Aug-2013 14:24:59 Uscrivikaran Bhan
ction has been removed from the call
ate:09-Aug-2013 16:22:03 User:Vikaran Bhan
Defect cause updated to 14: Development ~ Code
Date:09-Aug-2013 16:22:24 User:Vikaran Bhan
the Call record has been transferred to the team: Dev-Int-Rel
ser:Vikaran Bhan Confirmed that this Incident may be passed to the external
ogress was delivered to Consumer
company with the attached evidenc
ate:12-Aug-2013 14:59:29 Uscr:Matt Swain
ference Added: Product Baseline CTR APP X0900_V470-V435
STR APP_X0900 V470-V435 available for testing
Ihe Call record has been transferred to the team: Live Support Team
The Call record has been assigned to the Team Member: Unassigned
jate:20-Aug-2013 14:22:17 Uscr:Lorraine Elliott
Target. Release has been moved to Targeted At -- HNG-X 09.00.03.00SVéI Cycle 3
jpate:20-Aug-2013 14:22:23 Uscr:Lorraine Elliott
lke targeted outside PTF as discussed in release planning
te:15-Oct-2013 1
eference Adde:
jate:23-Oct-2013 17:28:20 User:Andy Pavis
[Start of Response]
tested with Anne Chambers using COUNTER APP 74_2 (LST R9.01.00.40):
he behaviour of the Counter app now, on encountering historic data, is that:
Hh. 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
B. When rolling the Branch, message MSG31332 is displayed to alert the PM that "Discrepancies for Transferred and Resolved do not
latch" and that the PM needs to report this
The Branch roll can complete, including the erroneous data
nce 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]
esponse code to call type L as Category 60 -- Final -- $/W Fix Available to Call Logger
outing to Call Logger following Final Progress update.
esponse was delivered to Consumer
[Date:23-Oct-2013 17:30:09 UseriLina Kiang
[fhe Call record has been assigned to the Team Member: Anne Chambers
Progress was delivered to Consumer
jate:24-Oct-2013 1
[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
pall.
[End of Response]
esponse code to call type L as Category 60 -- Final -- S/W Fix Available to Call Logger
outing to Call Logger following Final Progress update.
service Response was delivered to Consumer
30:59 User:Anne Chambers
[Date:24-Oct-2013 18:30:59 Uscr:Anne Chambers
CALL PC0223870 closed: Category 60 Type L
Date:25-Oct-2013 11:08:42 User: Cheryl Card
2230K authorised
Root Cause Development - Code
Logger _ Customer Call_ -- EDSC
Subject Product General/Other/Misce -- Unknown General/Other/Misc (version unspecified)
Assignee _Customer Call_ -- EDSC
Last Progress 25-Oct-2013 11:08 -- Cheryl Card