Sr Functional Change

No# Issue Description Area JDA's Recommendation Type Busines Priority Phase Status Notes
1 Updating Orginator Reference to C to Close PO XD-Inbound New Close PO Screen do following Screen High Phase 1 In-Progress 2203 - Manish to follow-up with customer.
1. Release Critical Hold to Available. 1903 - This will not be available in go-live.
2. Close the PO with Closing Date for reporting Signed PRS from TRI sent to JDA, JDA to provide estimation and workplan.
3. Closing of multiple POs
2 Excel Database Connection Errors for Receiving Summary XD-Inbound Receiving Summary Report Page Builder High Phase 1 In-Progress 1903 - Part of the page builder reports built and sent for testing.
Signed PRS from TRI sent to JDA, JDA to provide estimation and workplan.
4 Automatic Wave Planning XD-Outbound Automatic Wave Planning Standard Feature High Phase 1 In-Progress 2203- Have a discussion with TRI to set the timing of auto run.
1903 - As of writing, this has been tested multiple times and waves are being grouped as per client_id.
0103- Tesiting in progress. Found issue with grouping of order in wave.
Solution for auto waving was presented to TRI during the refresher's training, TRI operation (Iskandar) confirmed to use the auto waving.
6 Excel Database Connection Errors for Outbound Report XD-Outbound Outbound Summary Report print from JDA Page Builder Medium Phase 1 Testing In-progress 1903 - Only reports made available for next go-live are those part of the Finance/Operational reports. For TRACE/TRANCEN, still not completed testing.
2602 - This was identified to be related to the additional scripts for TRACE/TRANCEN. Awaiting TRI's confirmation on the db mirroring. TRI to update before end of week (0103).
10 Interface Issues System Recommended to use JDA Standard Interfaces (csv) Integration Medium Phase 2 Not Started JDA integrator will be implemented as phase 2 of PU and Surabaya.
11 Ops unable to complete the WMS processes due to big volume/large Order during first go-live Migration Migrate by business unit, start with small volume customer first (for ex. ARI - XD). Implementation Medium Phase 1 In-progress Cutover meeting is to be planned with TRI.
14 System Performance / Maintenance Issues System Enable Archieve and Purge Process Standard Feature High Phase 1 In-Progress As confirmed by TRI, 90 days of online retention and 180 days of archiving on Archive server to be done. GTI to setup the archive and purging jobs in system as per JDA's recommendation.
17 Label Template/Printing Labels External/Standard Feature Medium Phase 1 In-Progress 1903 - Development on-going, target 21st March
18 Reports (Finance & operation) Reports Page Builder Medium Phase 1& 2 Testing In-progress 1903 - Testing on-going
19 Reports (Trace and Transcen) Reports External interface Medium Phase 1& 2 In-Progress
21 1903 - Honeywell devices are made ready to replace the incompatible ones. TRI to confirm with vendor how to connect to JDA. Devices to be tested during UAT.
Check Compatible RF Guns to available & Lead Time for delivery Infra High Phase 1 In-Progress 2802- Followup Putra for the update on the RF guns.
22 RF Pick qty to be displayed in carton instead of pallets. XD-Outbound RDT Customization High Future In-Progress 2802- GTI to check if the display UOM for pick qty can always be shown in CN instead of pallet. Requirement is for Cikarang DC.
23 0403 - Received email from TRI that load balancer implementation will be determined by performance testing (which will happen after UAT)
Load Balancing Infra -- Medium Phase 1 In-Progress 2802- Send followup email to Hidyat if load balancer is needed? TRI need to make a decision on whether load balancer is required.
26 Inbound Receiving Cross-Dock Process Inbound Configuration High Phase 1 In-Progress 2802- Check the possibility of receiving in items instead of PO. RF form change may be required.
27 Solution Summary Document Document High Phase 1 In-Progress 2802- Details of the integration to be incorporated for PU and SB. Target date to complete the document is 0403.
28 GTI's Integration & Report Integration Integration & Reports High Phase 1 In-Progress 1903 - 9 open items (see SIT Open Items)
29 Migrating GTI tool report to JDA page builder Reports Migrate all the GTI tool reports to JDA using page builder Integration & Reports MEdium Phase 2 Not Started 2203- 3 reports to be moved in JDA after Go Live.
11
Ref # GTI Case # JDA Case Logged Issue Description Reported Type Business Due Date Closed Owner Stage Status Status Update Root Cause PIC
Date By Priority Date 0705- Unable to replicate the issue, however issue did not
reoccur. Case to be kept open for next 2 weeks.
PUSTD 2404 - For re-creation of the issue to send to JDA support.
7 Apr Wave not getting released Ranaa 5-Config 2-High GTI AS 10-Go Live 12-Pending RCA 0704 - Checked pckrelmngr.sts log file for the issue. System was Manish
01
not able to find staging location for specific rescod which the
system should have assigned. Set the correct rescod to the staging
location to release the pick.
0704:- Code changed to increase the character length.
Issue to be raised to GTI/ JDA support team for RCA on priority.
7 Apr 7 Apr 7 Apr 0704:- Escalated issue to Robbie.
PUSTD Last digit on TOID missing 0704:- Code fixed by Dev. Report working fine. Updated tool is
02 in loading summary. Jafar 7-Data 3-Medium GTI 10-Go Live 9-Closed provided to TRI. SQL Script
Network Issue- no
8 Apr connection available from 8 Apr 8 Apr
PUSTD S03 to S06 storage
03 location. Nicko 12-Infrastructure 2-High TRI 10-Go Live 9-Closed 0804- TRI changed adapter for access point.
2904- Operations successfully dispatched the shipment after
printed the packing list, no issues reported.
2704- Updated tool deployed to PROD by Iskandar.
2504- Updated tool provided to TRI. Iskandar tested and
8 Apr 26 Apr 29 Apr confirmed the testing is positive in TRAIN env. Pending to deploy
the tool in PROD.
2404 - Provided to TRI for testing. Once confirmed OK, to migrate
to PROD.
PUSTD LoadID not found during 2304- Full rollback will be released 2604 afternoon. Prior to that
04 1028749 1458633 loading Jafar 3-External App 2-High GTI DEV 10-Go Live 9-Closed will apply a workaround with the 2404 release.
0904-
1804-Updated
JRF sent to scripts
DEV and
team. provided new version of the tool.
8 Apr 9 Apr 9 Apr Report is testedcounter
1504- Reprint by Iskandar, Ikbal, Dedy
to be removed andthe
from no tool
issuesforreported
all the
PUSTD RR qty Mismatch (double further.
reports as confirmed by all users after adding of new custom
05 1028765 qty) Iskandar 8-Build 2-High GTI 10-Go Live 9-Closed 0904- Issues
column escalated
rejected by Arjanto (JDA).
dev team.
Dev team to start working on fix
2204.
0904-
1204-Updated
Updatedscripts and custom
tool using provided new version
column sent byofDev
theteam,
tool. to be
9 Apr 9 Apr 9 Apr Report
tested by is tested
GTI teamby Iskandar,
in TRAIN. Ikbal,
JDA toJafar, Dedy
confirm onand
theno issuesto
signoff
PUSTD Loading summary qty reported further.
migrate to PROD and adding the custom column.
06 1028762 mismatch (double qty) Iskandar 8-Build 2-High GTI 10-Go Live 9-Closed 0904-
1104- Issues
Changeescalated
request sentto devto team.
Dev team to fix the issue. No
2904-
standardConfirmed
fields onDCOD is being
JDA table generated
to be updated.the sameon
Change time
theas DD
during dispatch.
mapping to be done.
9 Apr 24 Apr 29 Apr 2504- GTI
1004- Updatedteam tool provided
identified the to TRI. Awaiting
subucc is gettingconfirmation
populated while from
TRI on testing.
printing the packing list. SQL script needs to be fixed, dev team is
PUSTD Interface - DCOD* File not 2304 - Part of the
informed about the2404 release, deploy to PROD after completing
issue.
07 generated Tris 8-Build 2-High GTI TC 10-Go Live 9-Closed testing
0904:- in TRAIN. done with Dinesh, pending response from JDA
Follow-up
1504-
support.Updated tool unable to be deployed to PROD as new
9 Apr 9 Apr 9 Apr version also contains
0804- Issue identifiedthe withfixSub
for PUSTD04
UCC codethat wasn't(inventory
in Invsub signed offsubto
PUSTD
be migrated
detail) to PROD.
table which Will deploy with
Thelatest version after
08 1028760 Unable to close ISN Ikbal 5-Config 4-Low GTI 10-Go Live 9-Closed 0904- Setting done populates value.
for user authorization value should
to close ISN.be "NULL" as
confirming
it is not parttheof requirement
configuration. for PUSTD04.
JDA case # 01458633 registered for
0904-
1204-Updated
Updated scripts and provided
tool provided by DEVnew
team.version
GTI tooftest
thein tool.
TRAIN
further
Report investigation.
is tested by Iskandar, Ikbal, Dedy and no issues reported
PUSTD 9 Apr Packing List qty mismatch 9 Apr 9 Apr environment.
Set up a scheduled job to clear out the subucc every hour
further.
0904- No issue since DD file generates only after trailer Dispatch
09 1028768 (double qty) Iskandar 3-External App 2-High GTI 10-Go Live 9-Closed completed.
0904- Issues escalated to dev team.
status.
2404 - As per meeting 2-3 days testing no longer needed as
PUSTD Identified issue is on the DCOD file which got generated without
10 Apr 26 Apr 24 Apr confirmed by Budi. Him and Anand agreed to close.
10 Store validation failing for dispatch status. JRF sent to Dev team for this change.
2304 - TRI to test this for 2-3 days starting today.
STD Ikbal 8-Build 2-High TRI PM 10-Go Live 9-Closed
1904- Fix tested by GTI and TRI in TRAIN. Deployed to PROD by
0805- Yolman sent
GTI. Requested TRI an emailand
to test to revert
TRI forback confirmation
for closure. if the
PUSTD following
1504- GTIconfiguration
testing finished. is acceptable
TRI to testto onoperation.
TRAIN by 1604.
1478586 11 Apr 24 Apr
11 0705-
1104- New GTI toconfiguration
test the validation to be tested
which on Train environment
is added for relabel and to
1028823 Shipment not yet staged Jafar 10-Oper 1-Critical NL BC 10-Go Live 4-In Progress
have Yolman
Move1inventory
TOID for 1scenario. Shipment ID. Current
Validation set istohaving
applies PICKED 1 TOID
TOIDwiththat is
3004-
multiple Report
in P1 location shipment.confirmation
For STDgiven no changeby TRI.required.
Report deployed to
PUSTD Page Builder- Some picked PROD.
11 Apr 26 Apr 30 Apr 0205- Validation
1004- No more issue reported.
is working duringP781 had issue
picking. Issueasisthefoundpicksduring
were
12 dates not shown on 2904- No transfer.
direct way
not completed
inventory NLtoteamget thehaspick date for
updating theXD on report. Criteria
script.
1028823 Pending Pallet Detail Jafar 8-Build 3-Medium GTI TC 10-Go Live 9-Closed for XD pick Byrone
2904- One date issuesconfirmed
reported with Iskandar to incorporate to report.
by operations.
0905-
2604-Awaiting
2604- Byrone
Check with isfor release
working
TRI onofcan
if this hotfix
the script
be from JDA.
update.
closed.
0705-
2204 --Next
2204 Update
To re-review
Karla (NL) providedfrom
whatsupport
are team
and for
missing/incorrect
findings bestrelease as itofwas
practices fix isreported
that on
the
PUSTD
12 Apr 26 Apr 1005.
that not only
operation team picked
should dates are not
follow. showing.
Training on this has been
13
Over allocation progress 0205-
1104- No
completed SQLmore Query
by Yolman.issue
to be reported
fixed. by
Pending TRI. Can be closed
documentation on theforprocess
TRI.
1028857 1463979 showing in WebUI Dedy 7-Data 1-Critical GTI/JDA 10-Go Live (emailtorefbe0105).
11-Awaiting Deployment
steps provided to TRI. Yolman
0205- Awaiting JDA's response on fix. Fix release date from JDA is
PUSTD 1204-
10th TRI reported incorrect data while interfacing supplier
May.
12 Apr 12 Apr 12 Apr "- Pending work (picks /replenishments/shorts) should be
14 Supplier address record master in TRAIN.TRI's
2904- Awaiting Identified old dataif existed
confirmation the issue in can
DB. beData shown
closed.
completed for the shipment.
mismatch in TRAIN Ikbal 7-Data 3-Medium GTI/JDA 10-Go Live 9-Closed correctly after TRI removed old data and reinter faced thetofile.
-2504- configuration
All picked inventoryoffor thethatwork assignment(picking
shipment should be deposited list) group
in
pickshipping
1504-
the ngMasterdata
list bystagestore, order type
uploaded
location. & picking zone. Rules & shipment
by GTI.
ID is tested
1204-
- Stage While bytrying
shipment Iskandar
option on
to updateinTRAIN and deployed
thefootprint
shipment inpage
web can to PROD
user be cannot
used env.
find
by the
PUSTD
12 Apr 12 Apr 15 Apr 2504-
the
user in NL/GTI
record
order . Intodid training
database
stage to TRIexists.
record
a shipment tothat
notWebUI
do not
has partial
anymovement
uses the warehouse
pending after
work.
15
item
ID is picked.
" value '----' unlike in MCS client that uses the actual warehouse
Missing footprint in webUI Ikbal 7-Data 2-High GTI/JDA 10-Go Live 9-Closed ID2504-
that Issue
user replicated
is logged in by
to. JDA
GTI intolocal
upload
1804- GTI shadowed the user and found incorrect operational instance.
the JIRA
Masterdata.wmd-229491
created.
2704-
issues Updated
(i.e. pending toolpicks
deployedto beto PROD byTo
finished). Iskandar.
check more with
2404- Test
2504-
operation Email sent to
result
team. JDA support
confirmed with theTool
by Iskandar. details
to beof the affected
deployed to
table
1504-and
PROD, GTI column
awaiting
to shadow name.
confirmation
the userfrom TRI.
to understand the process steps if
2304 followed.
2204
being Updated
- Initial trace files
fix failed. Onlywere 1 WH_IDalready sent
(----) wastobeing
JDA for their
updated
review.
with
1104- the Tonewescalate
Workaround footprint to Arjan
detail.
provided. (JDA)
To
Issue tologged
push
revisit 2304support
to supportteam. team. JDA
PUSTD 1804 -Dev
1804-
support Identified
team team needs one
to scenario
start
trace working
file butforon thefixissue.
team 2204
cannot To check
onreplicate
priority withthethe
for JDA
issue.
12 Apr 24 Apr 27 Apr
16 standard
release
GTI will on code
get or
the to
DBsee
before if working
2304.
backup file toassenddesigned.
to JDA.
1504- Dev
1204- Issueteam is related to PUSTD11
is informed aboutwhen the issue.split Code
shipment to behappens.
fixed.
GTI tofound
Issue shadow while theadding
users on new how the splitinformation
footprint shipment process for existingis
handled.
SKU with existing footprint. Integration tool fails to add new
Footprint Update Logic 1204- Unable
footprint details towhile
replicateonlythe theissue to getheader
footprint the trace file. GTI will
information gets
1028883 not working Ikbal 3-External App 2-High GTI Dev 10-Go Live 9-Closed get the DB file copy and send to JDA for analysis.
added.
0205- No more issue reported by TRI. Can be closed (email ref
0105).
2904- Awaiting TRI's confirmation if the issue can be closed.
2604- Check with TRI if this can be closed.
2404- “Move LPN to a different shipment” process should be
PUSTD
15 Apr 24 Apr 5 May done before the user starts the loading process in JDA
17
2304 - Training pending to the users by 2403.
1504- GTI to check and replicate the process with TRI. Issue
identified when shipment is already in loading status. Workaround
Unable to add shipment provided to Jafar to move TOID to another new shipment ID with
1028882 to LOAD ID Ikbal 10-Oper 2-High NL BC 10-Go Live 9-Closed no loading status. Yolman
2904- Received confirmation from Tris and Iskandar.
2604:- Awaiting Tris's confirmation on testing of DCOD. SQL script
fixed for DD and updated tool release to TRI. Awaiting Handi to
send the list of load ID's for which DD file need to be sent.
PUSTD 2404 - Byrone to help Ikbal with testing. Deploy to PROD after
15 Apr 24 Apr 29 Apr
18 completing testing in TRAIN.
2204 - JRF raised and approve. Dev to start working 2304.
Mismatch between 2004- Byrone provided script to TRI for generating the DCOD file
1028883, DCOD/DD and physical as temporary workaround.
1028896 shipped Tris 3-External App 2-High GTI Dev 10-Go Live 9-Closed 1504- Tris manually updating the Profit. Dev team to fix the code. Byrone
2904- Received confirmation from Tris and Iskandar.
2404- Awaiting confirmation from Tris for the date format.
2204 - TRI IT changed the date format in the server the tool was
running on. To discuss whether there are any changes left to be
PUSTD
15 Apr 24 Apr 29 Apr done on GTI end.
19
2104- Script to generate DCOD file manually sent by Byrone to
Tris and Handi.
1028823, 1504- Dev team to fix the issue. Auto generation of file not
1028896 DCOD file not generated Tris 3-External App 2-High GTI TC 10-Go Live 9-Closed working. Manually generated the file.
PUSTD User Error in work 1504- GTI to check and replicate the process with TRI. After
15 Apr 15 Apr 15 Apr
20 1028900 management Dedy 10-Oper 4-Low GTI BC 10-Go Live 9-Closed review, found as operational error. Training done with the users.
2504- Positive testing confirmed by Iskandar.
2404- Released to TRI for testing in TRAIN. Ikbal/Iskandar tested
and confirm for closure.
PUSTD 2204- Dev team to start working on fix 2204. Priority after
15 Apr 25 Apr 24 Apr
21 PUSTD16 and PUSTD21 is cleared.
1504- Dev team to fix the code.
RR mismatch between line 1504- Issue identified with mismatch of PO line # appearing on RR
1028896 ID and PO line nos Moniqa 3-External App 3-Medium GTI Dev 10-Go Live 9-Closed file and PO line # in JDA for SKU's.
2904- Received confirmation from Tris.
2604- Reminder sent to Tris.
PUSTD 2404- Awaiting confirmation from Tris for the date format.
15 Apr 24 Apr 29 Apr
22 2204- As date format already fixed on TRI end. To discuss
Incorrect Date Format on whether there are any changes left to be done on GTI end.
1028920 DCOD Handi 3-External App 3-Medium GTI TC 10-Go Live 9-Closed 1504- Dev team to fix the date format on code.
0905- Received email from Budi. 6 orders that are not allocated
have been cancelled, for the orders allocated 54 out of 635 orders
have been cancelled, ongoing for the rest. This case is closed as it
is considered as part of PUSTD24.
0205- Requested Iskandar and Budi to confirm the orders/lines
which need to be cancelled.
2904- TRI to review the list of orders provided by David and
confirm on further action.
2504- Config change related to disabling of Auto- Staging have
been deployed to Production env upon testing confirmation by
TRI in Train Env.
2404 - Tested 2304 c/o TRI w/ Glo after deploying the Config
change in PROD. To provide the same data for store 10119 on all
PUSTD other old orders for other stores with the same issue.
18 Apr 30 Apr
23 2204 - From further investigation, it was found out that a
different configuration is wrong and not the
backorders/replenishment. To test with TRI on TRAIN 2304 after
setting the configuration on auto-staging. Integration tool changes
no longer needed.
1904- Testing completed by Glo in Train environment (for back
order and replenishment) Pending update on the integration.
1804- Identified issue in mapping of integration fields where
backorder flag is set to 0 and also on replenishment which is set to
Cancel pending Replenishment and Cancel pending Order Lines..
On integration, mapping needs to be changed to 1 for backorder
Backorder- Order lines lines and change the replenishment to setting to cancel
getting cancelled / not replenishment only. Further testing to be done in TRAIN
100% allocation. 5-Config 1-Critical NL BC 10-Go Live 9-Closed environment. Karla
0905- Received email from Budi. 6 orders that are not allocated
have been cancelled, for the orders allocated 54 out of 635 orders
have been cancelled, ongoing for the rest
0105- Reminder email sent to TRI.
2904- TRI to review the list of orders provided by David and
confirm on further action.
PUSTD
19 Apr 24 Apr 2204 - To follow up on TRI.
24
1904- Issue identified for the orders which has stocks in Cikarang
but SO is pushed in JDA for PU. GTI provided list of the orders and
SKU's to TRI which has stocks in Cikarang DC. Based on discussion
Order not getting order with Cikarang stocks will be handled outside JDA.
allocated -(Cikarang Need to confirm with TRI on the action to be taken for open
stocks) 10-Oper 2-High GTI BC 10-Go Live 4-In Progress orders.
0905- Budi confirmed on following the correct process, admin will
ensure that no more pending replenish prior assign to picker. No
more issue reported by operations.
0205- Requested Iskandar and Budi to confirm the orders/lines
which need to be cancelled.
PUSTD
23 Apr 24 Apr 2904- Confirm with TRI if this issue can be closed. Training already
25
provided to TRI operation.
Order not getting 2304 - Issue identified during the allocation of order which does
allocated due to not not have stocks in pick location. Operation need to complete the
having any stock in the replenishment process. Replenishment task were cancelled and
system. 10-Oper 2-High GTI BC 10-Go Live 9-Closed need to be reallocated.
0805- Issue forwarded to Steven for further reference.
PUSTD 2904- Unable to replicate the same scenario. Workaround
23 Apr 26 Apr
26 Issues with undirected provided to operation (Cancel and reallocate).
picks 10-Oper 2-High NL BC 10-Go Live 12-Pending RCA 2304 - To review what the raised issue is. Karla
0205- Testing completed and confirmed by Dedy.
2904- To be started after pending pallet issue is closed.
PUSTD 2504- Script sent by Iskandar which is used in old label system.
23 Apr TBD 2 May
27 Byrone to compare script used in JDA vs old system.
Wrong qty on the STD 2304- Need to check the sql script used, to request the script to
label 7-Data 2-High GTI TC 10-Go Live 9-Closed Iskandar. Byrone
0905- Status 00 is ok. Issue for mismatch still open for status 05
and 10. email sent to David for further action.
0805- Awaiting confirmation on status 00 and 05 from TRI. Email
sent to TRI.
0505- Iskandar tested and reported data issue on status 10.
2904- Ikbal validated the data for status 10, 20, 30, 40
Req01 NA NA 25 Apr
2504- : 1. Shipment Status - Summary Report. Script deployed to
train and Prod.
2. Shipment Status - Detailed Report. It will be started after the
Monitoring report first one is completed and validated by TRI team.
-10,20,30,40,50 for XD and
STD 1-Request 2-High NL TC 4-In Progress 2304- Requirement confirmed by Iskandar.
3004- RC file sent to TRI.
PUSTD
30 Apr 30 Apr 3004- RC file not generated due to error on 28th April. Of 30th
28
RC file not generated Tris 3-External App 2-High GTI 10-Go Live 9-Closed April thee was no transactions so no file generated.
0305- As confirmed by Tris, staging script is already able to merge
the multiple files before send to Profit. No changes required in
Req02 NA NA 25 Apr integration tool.
DCOD file to be generated 3004- Request made to generate DCOD file per loaded. Current
per LOAD ID Tris 1-Request 2-High GTI TC 10-Go Live 9-Closed design generates DCOD file shipment ID.
 0905- Budi sent an email confirming the filtering of packing list is
done based on picked date.
0805- Confirm with TRI if issue can be closed.
0705- Date range selection not done by user to pull the
PUSTD
1029186 NA 7 May information. After selecting the date range the TOID was printed
27
with right information.
Qty mismatch between 0705- Reviewing the occurance of the issue. 1st time printing
Packing list and WebUI shows incorrect data whereas 2nd time printing shows correct
(Date range) Apriyanto 3-External App 2-High GTI TC 10-Go Live 9-Closed data. GTI team to check with user.
0905- Budi sent an email confirming the filtering of packing list is
done based on picked date.
PUSTD 0805- Issue identified with old default footprint set on item. Set
NA 8 May
28 Qty mismatch between the new/correct footprint as default on webUI. Awaiting
Packing list and WebUI Iskandar's confirmation.
(Default footprint) Iskandar 7-Data 2-High GTI TC 10-Go Live 9-Closed
TRI Issues Log
Ref # JDA Case Logged Date Issue Description Reported By Type Business Priority Due Date Closed Date Owner Stage Status Status Update Root Cause

Operations Stop for 2 days. Database compatibility

PU005 NA 28/12/18 System Slowdown TRI 12-Infrastructure 1-Critical 10/01/19 04/01/19 GTI 10-Go Live 9-Closed
Resolution: Migrated from 2017 to 2016 GTI and TRI. issues.

Cannot allocate and perform pick, Slow down/delay for 4 hrs. Duplicate footprint detail
PU006 1374450 26/12/18 Wave Planning Error TRI 7-Data 1-Critical 26/12/18 26/12/18 GTI 10-Go Live 9-Closed
Resolution: GTI removed duplicate records of Footprint. record

PU007 NA 26/12/18 Bad Login on the RF (Terminal ID) TRI 5-Config 3-Medium 26/12/18 26/12/18 GTI 10-Go Live 9-Closed Resolution: GTI modified the users and restarted Daemon server. Users not set to "Active"

PU008 NA 26/12/18 Receiving Report.- No actual Verification Time is displayed TRI 1-Request 2-High 26/12/18 26/12/18 GTI 10-Go Live 9-Closed Resolution: GTI added requested column. This is a change in design request. N/A

Workaround provided as interim solution. GTI Re-configured and tested, no issues.

1328978 Partial Inventory Move Error:

23/01 - JDA raised JIRA WMD-225832 to PD for further investigation.
10/02 - Followed up with JDA Support.
13/02- Followed up with JDA Support.
Misalignment design vs
15/02 - JDA Support confirmed that this is expected behavior when the load being moved has multiple shipments. For final testing
operations
1328978 22/02 - Testing Passed.
PU009 1355942 26/12/18 Multiple Ship ID to 1 TOID TRI 6-General 3-Medium 20/02/19 GTI 10-Go Live 9-Closed
For the pending case
1395502 1355942 Negative QTY when reversing picking
with JDA, RCA to be
08/02 - Sagar Shah (JDA Support) Recommended correct configuration for distribution as to not encounter this issue.
determined.
08/02 - Re-test passed.

1395502 TOID not showing when multiple shipment is consolidated

07/02 - Sagar Shah (JDA Support) confirmed that the issue will only occur for specific scenarios. Current design doesn't deal with this scenario,
reported should not occur.
08/02 - Re-test passed.
Workaround provided initially as interim solution.
Misalignment during
PU010 NA 26/12/18 Simultaneous Loading of Shipment ID TRI 5-Config 3-Medium 26/12/18 26/12/18 GTI 10-Go Live 9-Closed
design
Resolution: GTI Re-configure and test.

Cannot receive and pick for selected PO and SO.

PU011 NA 26/12/18 Master Data - Completeness TRI 3-Integration 1-Critical 26/12/18 26/12/18 GTI 10-Go Live 9-Closed Incorrect data
Resolution: Re-map interface document from Profit application to JDA.

Incorrect config by RF
PU012 1364906 13/12/18 RF on Sleep Mode Add Special Character TRI 12-Infrastructure 1-Critical 17/01/19 17/01/19 RF Vendor 10-Go Live 9-Closed Resolution: RF Vendor addressed the hardware issue. No error encountered after RF vendor did the setup on wavelink.
vendor

Master file data

PU013 NA 25/12/18 STD Inventory TRI 7-Data 2-High 30/12/18 30/12/18 GTI 10-Go Live 9-Closed TRI: There was incosistency in the data to be uploaded into JDA. For further cleanup and validation.
inconsistency.

PU014 NA 26/12/18 PO not on JDA TRI 10-Operation 2-High 27/12/18 27/12/18 GTI 10-Go Live 9-Closed TRI: To double check if all PO is extracted in Profit application before sending to JDA. User error - Validation

PU015 NA 26/12/18 Change Status from Hold to Available of item inventory TRI 10-Operation 3-Medium 27/12/18 27/12/18 GTI 10-Go Live 9-Closed GTI: Refresh Receiving Admin on the Process User error - Process

PU016 NA 26/12/18 Picking Errors Link to "Hold Status Receiving" TRI 10-Operation 3-Medium 27/12/18 27/12/18 GTI 10-Go Live 9-Closed GTI: Refresh Receiving Admin on the Process User error - Process

0203- Hot fix deployed. Tested on putty and no issues found.

The problem was fixed after restarting the MTF server, but it was frequently observed during the PU go live. GTI logged the case with JDA
accordingly.
Expire DB session should be enabled since it controls piling of the inactive sessions. JDA have escalated this issue to PD team for further
investigation.
Awaiting response from
PU017 1379026 19/12/18 RF bad login TRI 8-Build 1-Critical 20/02/19 19/01/19 GTI 10-Go Live 12-Pending RCA
GTI 19/01: PD on RCA
JDA Support raised WMD-225695 to PD to further investigate.
Workaround to change parameter settings of "EXPIRE DB SESSION" to "No". No errors encountered during testing.

JDA PD team to give an update on RCA. By default value of Expire DB session should be "Yes" but as a workaround JDA support set the Expire DB
Session to "NO".
This is a code issue in JDA WMS as the inventory being put away has more inventory than what is needed for the distribution and quantities are not
PU018 1366660 15/12/18 XD picking- Could not allocate location TRI 8-Build 1-Critical 19/01/19 19/01/19 GTI 10-Go Live 9-Closed being evenly divisible for the distribution. Code issue

JDA+GTI:Patch is applied and testing is completed. No error encountered during testing.

Mismatch of unit per
PU019 1385982 10/01/19 Unable to perform STD picking TRI 7-Data 1-Critical 11/01/19 11/01/19 GTI 10-Go Live 9-Closed GTI: Corrected the mismatch of footprint and inventory unit case qty. Retested Mload and no errors encountered during testing. case value between
stock and footprint
record.
JDA PD suggested to upgrade to 2018.1.2.2.
PU020 1386499 [1] 10/01/19 Cannot Dispatch shipment TRI 7-Data 1-Critical 22/01/19 22/01/19 GTI 10-Go Live 12-Pending RCA Unknown
22/01 Patch deployed and tested.

Arjan Kuhl 02/05/19 -

PU021 NA 27/12/18 RF replenishment process (after wave allocation) TRI 10-Operation 1-Critical 23/01/19 23/01/19 GTI 10-Go Live 9-Closed "JDA Product done
GTI: Training Development suspected
for operations not following right process, data or configuration issue and recommended installing patch – which enriched
on 1/21/2019 WH Retraining
the code of staging, added validation to prevent following wrong steps. Unclear which issue was rootcause at this moment"

GTI: To configure and test.

PU022 NA 10/01/19 Validation of PO in JDA and restrict picking TRI 1-Request 1-Critical 20/02/19 05/02/19 GTI 10-Go Live 9-Closed BL 0502 - Validation set in place. Testing on-going. NA
BL 0902 - Reviewed by JDA, confirmed set correctly.
BL 1102 - Testing completed, works as expected.
BL 1902 - RR to be retained. Updated tool provided and tested 04/02/19
BL 1402 - Awaiting report specifications, most likely reports will be done all in JDA. Refer to ALL04
Tool and computer date
PU023 NA 20/01/19 RR filter issue to be checked with Robbie TRI 13-Report 3-Medium 20/02/19 04/02/19 GTI 10-Go Live 9-Closed BL 0902 - Will be reconsidered during the 14/02/19 report meeting.
format doesn't match
GTI: To provide updated tool version

Printer not setup on the

PU024 NA 26/12/18 Admin has to set the printer every time to printer RR TRI 13-Report 3-Medium 14/01/19 14/01/19 GTI 10-Go Live 9-Closed GTI: Tool updated to have a printer already set.
tool.
0403 - JDA confirmed there was a confusion with the recommendation given. Same workaround (as the current one) was confirmed: "Higher UOM
qty for Pallet UOM in the footprint of the articles."
0103 - JDA recommended a policy change that will make the RF display as needed. GTI reverted about the policy not existing in standard.
2802 - Confrimed by CK in weekly meeting (2802 )to update footprint configuration for pallet qty (SB&PU). For Cikarang need to check during design
phase.
2702- For PU, SBY, increase carton qty for pallet to dislay pick qty on UOM as carton instead of Pallet. for Cikarang need to customize.
2502 - During training, a concern was raised for the amount of work the current receiving process will add to the Receiving Admin. Discussion to be
PU025 NA 10/01/19 Available LPN qty display (in carton) on RF during picking TRI 1-Request 3-Medium 20/02/19 GTI 10-Go Live 2-On Hold N/A
made with TRI by 2702.
2202 - To touchpoint with TRI on the decision (this is related to Receiving). PRS to be produced after confirming if needing modification.
BL 14/02 - As per Ramesh, this will be needing a full RF Form modifications. Confirm with TRI if this will be done for SU/PU go-live or after.
BL 09/02 - Requirements to be discussed between JDA and GenieTech
BL 05/02 - To discuss as this will need customization.
14/01 - Tool updated and provided to customer.

Mload has no validation check before data is inserted in DB.

PU026 1377886 10/01/19 More than 1 default footprint in 1 item TRI 7-Data 3-Medium 10/01/19 10/01/19 GTI 10-Go Live 9-Closed
Need to ensure additional validations are done to prevent this.
0604 - All Printers and Reports are setup in PROD. Tested, ready for go-live. Ready for go-live.
2803 - Reports discussion finished. GTI to provide feedback on how the changes will be made.
2203 - TRI to consolidate and send feedback on the reports. Currently receiving summary and receiving details have issue in extracting data on CSV. . Jitendra to fix the issue.
1403 - All reports are awaiting to be tested on TRI end.
0403 - 2 reports have been built and ready for testing: Finance Reports – Inbound Reports, DC Stock Summary Report. GTI to validate the report before handing over to TRI to confirm data is correct.
07/02/19 2802 - Reports development on-going. Signoff to be requested.
26/06 - Review points addressed and acknowledged between GTI/TRI. Final specification for Fincance/Operation reports to be sent to JDA for development after signoff.
22/02 - Reports specification sent for TRI review. Review points received from Finance.
18/02 - Operation/Finance reports identified and finalized. Rajat to send documentation for sign-off. KPI is pending for discussion.
14/02 - TRI to get back with all reports that needs to be created from WMS end. TRI to also provide report specifications (i.e. what fields are needed/etc)
ALL04 NA Reports via JDA TRI 1-Request 3-Medium GTI 10-Go Live 9-Closed 07/02- All the report are planned to be printed via JDA. Detailed discussion will be done on 14/02 at LB office with Finance and operation.
26/02 - Closing and be tracked on ALL04.
18/02 - To confirm with Putra/TRI if this can be closed if this will be addressed when reports are generated in JDA.
07/02/19
QTY mismatch issue between receiving report and excel report sent 14/02 - Dependent on ALL04
ALL05 NA to Finance TRI 7-Data 2-High GTI 10-Go Live 9-Closed 07/02- Discussion with Finance is planned on 14-Feb to understand the actual issue.
20/02 - Testing completed.
12/02/19 20/02/19 14/02 - Design is being finalized and will be ready for development 15/02
ALL06 NA Validate store code during scanning of TOID TRI 1-Request 2-High GTI 10-Go Live 9-Closed 12/02- GTI/JDA to check further on how verification and validation of store code can be done
1004 - With how the performance testing is planned, to discuss with Arjan what the plan is going to be.
SU009 NA 28/02/19
Surabaya Go Live TRI 10-Oper 3-Medium TRI 10-Go Live 2-On Hold 2802- Due to current Operational Issues and Peak Period, Go Live Date to be decided after Go Live for Pondok Ungo
STD Directed Picking- Store Validation is not woring 0604 - Tested and confirmed to be working as expected.
because the validation applies only on the Distro RF Page 0504- TRI raised an issue regarding mismatch on the TOID Store Code Vs. the Packing List Store Code. After investigating, the reason was the Store Validation is for XD and not for STD.
PU17 NA 04/04/2019 06/04/2019 05/04/2019 GTI
and not for STD Directed Picking. 0504- Netlogistiks Team with Jitendra worked on the validation and have deplyed and tested to Production Environment.
Packing List Store Code vs. TOID is not matching. TRI 4-Requirement 0-Urgent 0-All 9-Closed 0504- Glo tested STD Directed List Pick for 2 list IDs and it was working as expected.
0409 - Fix was released, tested and confirm values are correct.
ALL18 NA 05/04/2019 Mismatch of qty between Loading Summary and load_id 06/04/2019 06/04/2019 GTI 0504- Issue was raised.
TRI 4-Requirement 0-Urgent 0-All 9-Closed 0604- Query of load_id was updated to be tested by user.
10-Go Live
TRI Issues Log
Ref # JDA Case Logged Date Issue Description Reported By Type Business Priority Due Date Closed Date Owner Stage Status Status Update Root Cause
TRI Issues Log
Ref # JDA Case Logged Date Issue Description Reported By Type Business Priority Due Date Closed Date Owner Stage Status Status Update Root Cause
TRI Issues Log
Ref # JDA Case Logged Date Issue Description Reported By Type Business Priority Due Date Closed Date Owner Stage Status Status Update Root Cause
TRI Issues Log
Ref # JDA Case Logged Date Issue Description Reported By Type Business Priority Due Date Closed Date Owner Stage Status Status Update Root Cause
 Type Date Raised Issue # Process Issue Description Action / Resolution Status Complexity Owner Next Update Date Comment
0503 – TRI was able to provide interface files
containing the needed information
Date controlled settings TRI managed to
Master Data 4/3/2019 MD1 Item Master Download for specific items under populate the needed Closed TRI 8/3/2019
0403 - As part of the mapping, several fields were
client STDARI/STDTRI fields. identified to be filled by TRI for items under
"Grocery" category/item family.
Item Master interface 0603 - This is addressed. TRI is sending 7
TRI is now sending 7
mapping for characters.
Master Data 5/3/2019 MD2 Item Master Download characters for this Closed TRI 8/3/2019
TIME_TO_WARN_FOR_EX 0403 - Identified from issue 01. Currently TRI to
field. send 5 character files for SIT.
P
1503 - Fix tested. Passed.
1203 - As per DEV Team fix will be released on
the 14th of March.
1103 - JRF raised to GTI Dev Team. Development
will start tomorrow and be closely monitored.
Retesting of affected scenarios will be done as
soon as fix is deployed.
0803 - Meeting held with GTI Dev Team on the
requirements. Technical specification document to
Records for items be sent by 11/03/19 to commence work.
GTI Dev to modify
10000000001 and 0603 - Raising to GTI Dev Team
integrator tool to
Master Data 5/3/2019 MD3 Item Master Download 10000001001 under Closed Medium GTI 14/3/2019 0503 - Attempt to downloading these items wasn't JRF Sent 4
accommodate
STDTRI/STDARI were not successful even though log file indicated they were
change in mapping. inserted:
inserted.

"03-05-2019 04.30 PM : Item Number:

10000000001, STDARI, ---- successfully inserted,
lvl 0 inserted, lvl 1 inserted, lvl 2 inserted, Barcode
inserted
03-05-2019 04.30 PM : Item Number:
10000000001, STDARI, DC001 successfully
inserted, DSC exist, lvl 0 inserted, lvl 1 inserted, lvl
2 inserted, Barcode not inserted"
1503 - Fix tested. Passed.
1203 - As per DEV Team fix will be released on
the 14th of March.
1103 - JRF raised to GTI Dev Team. Development
will start tomorrow and be closely monitored.
GTI to check with Retesting of affected scenarios will be done as
Incorrect dimension TRI for the values soon as fix is deployed.
Master Data 5/3/2019 MD4 Item Footprint Detail Values values. (Piece > set. GTI Dev to Closed Low GTI 14/3/2019 0803 - Meeting held with GTI Dev Team on the JRF Sent 1
Carton/Pallet) update the default requirements. Technical specification document to
value set. be sent by 11/03/19 to commence work.
0603 - Checking mapping file vs the default values
previously provided.
0503 - Noticed that piece uom is larger than
carton/pallet uom. Need to check if came from file
or integrator tool's calculation.
0903 - It was made known that the requirement
was that for Level 1 and Level 2 to be equal as
PROFT doesn't have the data needed. Tagging as
closed.
GTI to check with 0803 - Meeting held with GTI Dev Team on the
requirements. Technical specification document to
Incorrect weight (Carton TRI for the values
Master Data 5/3/2019 MD5 Item Footprint Detail Values Closed Low GTI 15/3/2019 be sent by 11/03/19 to commence work.
= Pallet) set. GTI to discuss
0603 - Checking mapping file as well as the logic
with Dev Team. set in integration tool. To discuss with GTI Dev
Team.
0503 - Noticed that carton weighs the same as
pallet. Need to check if came from file or integrator
tool's calculation.
1503 - Fix tested. Passed.
1203 - Fix by Dev team to be delivered 1403
0903 - Test Failed. Re-raising as issue.
Stk_flg not set for Piece 0803 - As per GTI Dev Team, this has been fixed
Master Data 5/3/2019 MD6 Item Footprint Detail Values GTI Dev Team to fix. Closed Low GTI 14/3/2019 JRF to be drafted 1
UOM on another version of the tool. For re-test.
0603 - Raising to GTI Dev Team
0503 - This flag needs to be set as system checks
for this during pick release.
0603 - Not an issue, can be either PC or CN
UOMCOD value needs to be
Master Data 5/3/2019 MD7 Item Barcode (ALT_PRTMST) Value N/A Closed GTI 8/3/2019 0503 - UOMCOD value needs to be confirmed if
confirmed
PC or CN
1203 - Fix by Dev team to be delivered 1403
0903 - Test Failed. Re-raising as issue.
0803 - As per GTI Dev Team, this has been fixed
Trust_flg is set to 1 instead of on another version of the tool. For re-test.
Master Data 5/3/2019 MD8 Supplier Values GTI Dev Team to fix. Closed Low GTI 14/3/2019 JRF to be drafted 1
0 0603 - Raising to GTI Dev Team
0503 - Since Transretail doesn't have any ASN, no
supplier should be set as trusted. Checking if this
came from the interface file or logic set in tool.
2103 - Tested fix. Working as expected.
1903 - Fixed and is currently being tested. Release
by 21st of March
1503 - SUPMST is good, ADRMST is still
unupdated. To re-raise back to DEV
1203 - As per DEV Team fix will be released on
the 14th of March.
1103 - JRF raised to GTI Dev Team. Development
ADR_ID duplicate across will start tomorrow and be closely monitored.
Master Data 5/3/2019 MD9 Supplier Values GTI Dev Team to fix. Closed Medium GTI 21/3/2019 JRF Sent
clients Retesting of affected scenarios will be done as
soon as fix is deployed.
0803 - Meeting held with GTI Dev Team on the
requirements. Technical specification document to
be sent by 11/03/19 to commence work.
0603 - Identified that TRI is not responsible as per
the supplier mapping. To raise to GTI Dev Team.
0503 - Address should be unique for each
supplier+client combination.
Based on the number of 0308-Mismatch of count of orders per client/file
Dos provided via email by to be verified by TRI
Pak Handi, below is the 0309- Checked the file, there was no mismatch of
breakdown vs. inserted TRI to double check count. In JDA it shows more number of DO
DO in JDA:There is a huge the interface file and because the naming of DO in JDA is concatenated
Outbound Interface- March
Outbound 8/3/2019 TR1 mismatch of count of verify the correct Closed TRI with customer code. 1 DO number is tagged to
5,2019 multiple customer code in Profit. Outbound Order
orders. Orders inserted in number of Dos in
JDA is greater than what each file. Number in JDA should be unique thats why the
was reported to us. naming is DO# + customer code.

0309- Validation file was updated

0308-There are Inbound Files which was not
Number of Pos provided 0309-TRI to clean provided over the email but was included on the
Inbound Interface for March 6, to us via email is greater the files, ensure that interface.
Inbound 8/3/2019 TR2 In-progress TRI 11/3/2019
2019 than what was inserted to Pos are not 0309- PO not inserted due to duplicate from other
JDA. duplicated previous day's files

0309-TRI to
0309- PO with order type
Inbound Interface for March 6, interface PO linked
Inbound 8/3/2019 TR3 XDSC were not included In-progress TRI 11/3/2019 0309- PO with order type XDSC were not included
2019 to DO with order
on the interface files. on the interface files.
type XDSC
0309-TRI to provide
complete list of files 0308-There are Outbound Files which was not
Number of Dos inserted to
over the email to provided over the email but was included on the
Outbound Interface- March JDA is greater than the
Outbound 8/3/2019 TR4 ensure the accuracy In-progress TRI 11/3/2019 interface.
6,2019 no. of Dos provided over
of count.
the email

0604 - Confirmed pass during the cutover file

0309- PO tagged to Dos
which have Order type
XDSC were not interfaced,
Outbound Interface- March but the DO was inserted.
Outbound 8/3/2019 TR5
6,2019 Part of the validation is
that, when PO does not
exist, it should reject the
whole order.
testing.
0104- Initial testing done by GTI and passed.
Further testing to be done by TRI.
2703 – Rejected the order when the associated
PO is not existing in the system. One odd
0309- Additional behaviour noticed was that the process stops after
validation is being the error while the expectation is that it will
Closed High GTI 27/3/2019 JRF-02202019124718
developed. Check continue on processing the next lines.
Target completion 1203 - Due to high complexity of change needed,
will be after go-live. GTI to provide a workaround
to mitigate any impact this will make.
0309- PO tagged to Dos which have Order type
XDSC were not interfaced, but the DO was
inserted. Part of the validation is that, when PO
does not exist, it should reject the whole order.
 Type Date Raised Issue # Process Issue Description Action / Resolution Status Complexity Owner Next Update Date Comment
ARI PO count shows 237
in backend using query.
But when I checked on
the extracted file from
Inbound Interface for March 5, webUI, ARI PO count GTI to check data in 0308- GTI to check internally
Inbound 8/3/2019 TR6 Closed GTI
2019 shows 238. Checked the backend vs. webui. 0309- PO was inserted at different date
log file if there is any log
generated for the rejected
order for ARI, there was
none.
File name TRI to double check
OD20190308155006 was why this file
Inbound Interface for March 8, 0309- OD20190308155006 Not dropped on ftp
Inbound 9/3/2019 TR7 provided in the list via OD20190308155006 In-progress TRI 11/3/2019
2019 folder- not part of the processed files
email, but was not part of was not dropped at
the interfaced files. ftp for processing.
2703 – Tried inserting an 4-line order with the final
0308- Item does not exist. 0309- GTI- line’s SKU not valid. Rejected the whole order as
Whole order must not be Validation is being expected.
Outbound Interface- March 8,
Outbound 9/3/2019 TR8 inserted because item does fixed-Check Target Closed Medium GTI 27/3/2019 1203 - Fix done but will be packaged together with Fix
2019
not exist. completion TR5 as several tests need to be done.
0308- Item does not exist. Whole order must not
be inserted because item does not exist.

0309- TRI to correct

the Order Type being
used for regular
0309- Order Type used to all
Outbound Interface- March 8, orders at DC002. It
Outbound 9/3/2019 TR9 DC002 orders was XDSB In-progress TRI 11/3/2019 0309- Order Type used to all DC002 orders was
2019 which should be XD for should be XD, then XDSB which should be XD for regular orders.
regular orders. XDSB for orders
which are treated as
transfer to Pondok
Ungu.

1203 - As per Dev Team, only need a process log.

0309- Item and Customer
0309- Item and Customer does not exist. No error
does not exist. No error log
Outbound Interface- March 8, 0309- GTI- Check log file has been generated for this rejection, only
Outbound 9/3/2019 TR10 file has been generated for Closed Medium GTI 14/3/2019 Fix
2019 with Dev Team process log.
this rejection, only process
log.
Customer Code=91003

0309-Only XD, STD, XDAI, XDSB and XDSC were

Order Types requested to be 0309- TRI to
Outbound Interface- March 8, interfaced. The rest are still pending. Note that PO
Outbound 9/3/2019 TR11 interfaced are not yet interface requested In-progress TRI 11/3/2019
2019 or Planned Inbound Order for XDSC was not yet
complete. Order Types interfaced.
1203 - As per DEV Team fix will be released on
0311- Expected Receipt Area
the 14th of March.
is in B1 which is EXPR. 0311- GTI to put in
Inbound 11/3/2019 TR12 STD Inbound Closed Low GTI 14/3/2019 0310- Expected Receipt Area is in B1 which is JRF
Needs to change it to Interface Tool
EXPR. Needs to change it to EXPR000003 which
EXPR000003 which is in B2.
is in B2.
2103 - Tested fix. Working as expected.
0311- Process Logs is being 1903 - Fixed and is currently being tested. Release
overriden by the next file by 21st of March
being processed on the same 1503 - Even after adding seconds, not all message
day which only retains the for each processed file is appearing on the log file.
Outbound details of last file being 0311- GTI to put in 1203 - As per DEV Team fix will be released on
11/3/2019 TR13 Inbound and Outbound Interfaces Closed Medium GTI 21/3/2019 Fix
Inbound processed. Need to have the Interface Tool the 14th of March.
process Log of all the 0310- Process Logs is being overriden by the next
processed files of the day file being processed on the same day which only
both for Inbound and retains the details of last file being processed.
Outbound. Need to have the process Log of all the processed
files of the day.
1103 - Counts does not match for some DOs and
Mismatch in the files sent for
Outbound PO suppliers. GTI to advise TRI to provide count
11/3/2019 TR14 Inbound and Outbound Interfaces 09/03 from PROFIT vs what TRI to re-provide counts. In-progress TRI 12/3/2019
Inbound for each order+customer combination rather than
is received in JDA
just sending count for distinct order number.
0311- Number of suppliers mismatch for TRI cleint
Outbound 0311- Number of suppliers 0311- TRI to check the ID. On the list provided in email was 16 while 13
11/3/2019 TR15 Inbound and Outbound Interfaces In-progress TRI
Inbound mismatch for TRI cleint ID. number of Suppliers suppliers are inserted even if the number of POs
Interfaced are matching.
2803 - Monitoring all orders that came in, no distro
ID populated on standard orders.
2103 - Tested fix. Working as expected.
GTI to raise to DEV
1903 - In-progress. Release by 21st of March
JDAtoHost 14/3/2019 TR16 Outbound JDAtoHost Incorrect shipped qty team for the correct Closed Low GTI 21/3/2019
1503 - Confirmed the design from GTI BC/TC. To
logic to be set.
raise back to GTI DEV Team to fix.
1403 - Confirmed the discrepancy between the
shipped quantity vs the order quantity.
3103 - All STD orders doesn't have distro_id,
tagging as closed for now until issue reoccurs.
GTI Dev to check as 2103 - Cannot recreate issue. Will monitor the feed
Non-distro Orders having
HosttoJDA 18/3/2019 TR17 HosttoJDA Outbound this was resolved Closed Low GTI 21/3/2019 for UAT to confirm if this is still occuring.
distro ID
before 1803 - Confirmed that after the fix, non-distro
orders are having distro ID values. This was
previously fixed under JRF - 011120191219.
2103 - Tested fix. Working as expected.
1903 To be checked in parallel by both team.
No lines to write – message
GTI Dev Team to 1803 After the new version, JDAtoHost for
JDAtoHost 18/3/2019 TR18 Inbound JDAtoHost receive when attempting to Closed Low GTI 21/3/2019
check and fix. JDAOutBoundRV is no longer working. Checking
trigger interface back to host.
the query to fetch the data, it was working.

2203 - Fixed
2103 - Tested fix. Not all scenarios working as
expected, DEV has fixed and to resume testing
Inbound orders are incorrectly GTI Dev Team to tomorrow.
JDAtoHost 18/3/2019 TR19 HosttoJDA Inbound Closed Low GTI 21/3/2019
being written into the system check and fix. 1903 - In-progress, to be released 21st
1803 - After the new version, inbound orders
written are incomplete making the system not
show them completely.
 Type WH Date Raised Issue # Process Issue Description Action / Resolution Status Complexity Owner Next Update Date Comment
0604 - Tris said that they have an updated script
that will make the files to have only 1 order type
each file. To be tested 1004-1104.
2903 - GTI Dev Team responded that the change
Orders of different inbound will be huge and will not be on time for go-live.
order type are being written GTI to raise to GTI DEV team to Looking for other options.
Integration PU 21/3/2019 UA1 Inbound Order Download For-Testing High GTI 30/03/2019
into JDA as just 1 order rewrite the interface. 2503 - Raised to GTI Dev Team.
type. 2103 - There was a misconception on how the
interface file for inbound should be. TRI sends
over files that may contain several order types
and GTI tool only takes 1 order type per file per
SUPPLIER+CLIENT+DATE combination.
0204 - Release fixed the issue.
2903 - Release date scheduled for 01/04.
Incorrect value for QTY per PC/ GTI to raise to GTI DEV team to
Report PU 21/03/2019 UA2 Packing List Closed Low GTI 30/03/2019 2503 - CR Raised to GTI Dev Team.
QTY per BOX fix.
2103 - Report does not return the sum of all items
inside the LPN. To be fixed
0604 - Jitendra deployed all updated reports in
PROD.
2703 - Operations re-raised the issue wherein the
date between the Receiving Report and the page
builder report is not the same. Identified that the
Report PU 21/03/2019 UA3 Receiving Report Incorrect Data Value (?) JDA to change report date. Closed Low GTI 30/03/2019
two reports are using different date fields, to
change by JDA.
2503 - From the details provided, still cannot see
the issue. To confirm with TRI.
2203 - Currently checking the details of the issue.
0204 - Release fixed the issue.
2903 - Release date scheduled for 01/04.
Mismatch in data between
GTI to raise to GTI DEV team to 2703 - GTI Dev to work on the CR. Pending
Report PU 21/03/2019 UA4 Loading Summary/ Packing List Loading summary and Packing Closed Low GTI 30/03/2019
fix. release date.
List.
2503 - Drafted as part of change request
2203- Currently checking the details of the issue.
0204 - Release fixed the issue.
3003 - Confirmed part of Dev Team fix to be
GTI to raise to GTI DEV team to released 01/04
Report PU 21/03/2019 UA5 Loading Summary Cannot Print Closed Low GTI 30/03/2019
fix. 2503 - From the details provided, still cannot see
the issue. To confirm with TRI.
2203- Currently checking the details of the issue.
0604 - Glo updated permission configuration
2903 - TRI confirmed to provide the list of
process per user role/group
Config PU 22/03/2019 UA6 Authorization Incorrect Role Permission GTI to configure Closed Med GTI 30/03/2019 2603 - Meeting to be held 2803 to finalize the list
2203- TRI to provide update list of user roles. GTI
to assign the roles to relevant users based on the
updated list.
2504- Updated tool relased.
3003- Set up a scheduled job to clear out the
subucc every hour
2903- Issue identified with Sub UCC code in
Invsub (inventory sub detail) table which
Established workaround while populates value. The value should be "NULL" as
Operation PU 27/03/2019 UA7 Shipping Unable to Load LPN Closed Med GTI 30/03/2019
confirming RCA for permanent fix it is not part of configuration. JDA case #
01458633 registered for fruther investigation.
2703 - Based on the trace file, there is a
persistent Load ID that is being referenced by the
system. Checking the validity of this data and if
this needs cleaning up.
2903 - After identifying the issue that some put-
Incorrect RESCOD for to-store location configuration is incorrect due to
Config PU 29/03/2019 UA8 Config GTI to configure Closed Med GTI 30/03/2019
PUTTOSTORE location a misprocessing of the IT Admin during UAT, GTI
reconfigured to the correct value.
3003 - Deleted the user id 1001 and re created
Cannot Change User Account
the user again
Status from Inactive to Active for
Config PU 30/03/2019 UA9 Config GTI to configure Closed Med GTI 30/03/2019
User 1001- Adress ID of 57
Found from trace that the adress ID of the user is
users are not existing at adrmst
not existing to adress master.
Item Description not reflecting in
WebUI (Configuration
>Items>Items)- Cannot modify 3003 - Need to upload 4 dashes for Item related
Masterdata PU 30/03/2019 UA10 Masterdata GTI to Upload Closed Med GTI 30/03/2019
Item Configuration- Need to Masterdata
upload 4 dashes for Masterdata
related to Items
3003 - GTI to check the sequence of stores
3003- Upon checking the Configuration at
Distro Picking to Put To Store Processing Location Reservation, user
Config PU 30/03/2019 UA11 Config GTI to check Closed Med GTI 30/03/2019
not in sequence mistakenly done some changes. Upon reverting
to the correct configuration, the picking sequence
is resolved.
3003 - Data Issue due to the DB Backup and
restore which might have affected the data.
Config PU 30/03/2019 UA12 Config Cannot Apply Hold GTI to check Closed Med GTI 30/03/2019
Deleted the Existing holds and re created, and it
works.
3103- This is not a system issue, the inventory in
Wave Short Allocated due to the system is already allocated to another order.
Config PU 30/03/2019 UA13 Config Items with footprint level 1 equal GTI to check Closed Med GTI 31/03/2019 3103 - Shorted wave was allocated and picked
to level 0 unit qty normally after using correct stock.
3003 - GTI to check how to resolve
STD RF Picking- Showing 0cn
to pick while in system it shows
6pc. Upon checking on the 3103- After updating the unit per case in
Item's Footprint Detail it has unit inventory detail, tried to do the picking again for
Data Upload PU 31/03/2019 UA14 Data per case value of 6 while in the GTI to check Closed High GTI 31/03/2019 the item affected, then it already shows the
inventory detail it shows 12. correct qty which is 1cn.
There is a mismatch between -Jitendra to add the script validation.
the Footprint Detail masterdata
and the stock upload file.
3103- check with Jitendra
User prints 5 XD LPN but the 3103- Resolved by Jitendra by chnaging the
Label Printing PU 31/03/2019 UA15 Label Printing GTI to check Closed Med GTI 31/03/2019
printer only prints 3. maximum value to print in policy from 3 to 100 as
suggested by Ikbal
User wants to reprint an STD
Put Away Label, upon entering 3103- check with Jitendra
Label Printing PU 31/03/2019 UA16 Label Printing the PO and LPN which needs to GTI to check Closed Med GTI 31/03/2019 3103- fixed by changing the seqnum to use
be reprinted, system prompts seqnum>=1 because we may have data with >=1
"Invalid PO"- 9191014221
3103- This is not a system issue. Error message
encountered was a valid message because the
status of carrier move id is already in "Loading"
User wants to add a Shipment to status.
Cannot Add Shipment to a
Operation PU 31/03/2019 UA17 a Load which is in "Loading" GTI to check Closed Med GTI 31/03/2019 Provided the user the step on how to add TOID to
Load in "Loading" Status
Status an existing Shipment. Instead of adding the
shipment, user can just add the specific TOID
they want to add to the existing shipment tagged
to the carmove_id which is in "Loading" Status.
0104 - Delivered the fix from GTI Dev Team,
confirmed not an issue.
Incorrect receiving details in 0104 - Receiving Team raised an issue in regards
Report PU 01/04/2019 UA18 Report GTI to check Closed Med GTI 01/04/2019
Receiving Summary/Detail to incorrect receiving data shown from receiving
especially when there are multiple lines in the PO
with the same item number.
TOID # (500120000005639) not
Report SU 04/27/2019 UA19 Packing List appearing in GTI tool while GTI to check Open Med GTI
printing packing list 0705- Updates to be released in week of 13.
Transport Equipment failed to Added policy in trigger to confirm the outbound
JDA SU 05/09/2019 UA20 Dispatch Trailer Policy added Closed High GTI 05/09/2019
dispatch interface for DC002.
0510- Asked Ikbal to do Move LPNs to different
Shipment for TOIDs which will be dispatched
JDA SU 05/09/2019 UA21 Shipment is Not Yet Staged Error during Close Equipment Move LPNs to different shipment Closed High GTI 05/10/2019
because there are still pending picks for that
shipment.
 Ref Date User Report Name Report Type Details GTI/JDA Response Status
RP-01 22-Mar Putra Receiving Report JDA PageBuilder UAT Issue - The extract to spreadsheet only shows 1 page of Data at a time [23/03]The maximum rows to be displayed have been increased to 1000 rows. Ready to re-test Completed
RP-02 22-Mar Putra Packing List GTI Reporting Tool The Packing List is not available [23/03] This should be available when the Shipped Equipment is closed. New Tool has been issuedCompleted
RP-03 26-Mar Loading SummaryGTI Reporting Tool Issues related to field and data 27/03: New JRF ver 1.5 sent to Dev team for the issues to be fixed Completed
RP-04 5-Apr GTI Reporting Tool 0504- Issue of multiple lines generated on the RR has been resolved and updated the script to Completed
sum up and group the qty.
Receiving Report shows multiple lines of 1 item and showing wrong
Budi Receiving Report 0504- Another issue was raised after resolving the latter issue. Qty per piece on Expected Qty and
quantity
Received Qty is wrong (it adds up the expected qty) 919043915
0604- Byrone is working with Dev Team to fix the issue
RP-05
RP-06
RP-07
RP-08
RP-09
RP-10
RP-11
RP-12
RP-13
RP-14
RP-15
RP-16
RP-17
RP-18
RP-19
RP-20
RP-21
RP-22
RP-23
RP-24
RP-25
RP-26
RP-27
RP-28
RP-29
Status Master Data Version Priority Comments
Uploaded. Ready for TRI review/signoff.(20190301T0000000)
ADRMST 3-Medium 020319: Loaded into PROD. There were 2 records having address line 1 character > 40, fixed.
280219: From training, it was raised by operations that the carrier data needs to be changed. ADRMST was updated as well. Confirmed to be placed in Google Drive by 010319.
250219: Uploaded to PROD, for TRI final validation and sign-off.
220219: UNKNOWN/9999 data were left as blanks.
200219: Incomplete data as per Putra (TRI) is valid, as these are also incomplete in HOST (Profit). These are not being used in JDA (processing/reports/etc). If there will be a need to use this in the future, HOST (Profit) needs to be updated and then JDA will also be updated.
Uploaded. Ready for TRI review/signoff.(20190228T0000000)
ALT_PRTMST 2-High 110319: Putra sent a new version of ALT_PRTMST containing less records. Loaded.
100319: TRI confirmed DC002 will be using DC001 value. From final validation, found 2570 (912 unique) alt_prtnum who's items are not in Item Master (PRTMST), sent confirmation.
070319: DC002 data provided. Confirming if DC002 will be using the same values as DC001 in terms of item barcode.
020319: Uploaded to PROD, for TRI final validation and sign-off. Edited the files to remove all double quotes (").
280219: New version provided. To be loaded by 010319.
250219: Uploaded to PROD. Duplicate 1 item, removed.
220219: Some item barcodes were found to be used for multiple items, this may introduce issues in the system as the system will have a hard time determining which actual item will the barcode translate to. To be reviewed once provided.
Uploaded. Ready for TRI review/signoff.(20190301T0000000)
CARDTL 3-Medium 020319: Uploaded to PROD, for TRI final validation and sign-off.
280219: From training, it was raised by operations that the carrier data needs to be changed. Confirmed to be placed in Google Drive by 010319.
250219: Uploaded to PROD, for TRI final validation and sign-off.
Uploaded. Ready for TRI review/signoff.(20190301T0000000)
CARHDR 3-Medium 020319: Uploaded to PROD, for TRI final validation and sign-off.
280219: From training, it was raised by operations that the carrier data needs to be changed. Confirmed to be placed in Google Drive by 010319.
250219: Uploaded to PROD, for TRI final validation and sign-off.
Uploaded. Ready for TRI review/signoff.(20190301T0000000)
CSTMST 3-Medium 190319: Uploaded new version to PROD, for TRI final validation and sign-off.
020319: Uploaded to PROD, for TRI final validation and sign-off.
250219: Uploaded to PROD, for TRI final validation and sign-off.
Uploaded. Ready for TRI review/signoff.(20190301T0000000)
LOCMST 1-Critical 020319: Uploaded to PROD, for TRI final validation and sign-off. Location 1SH334A had invalid date data, fixed.
280219: From training, it was raised by operations that the dock door names needs to be changed. Location height was decided to be changed as well.
250219: Uploaded to PROD, for TRI final validation and sign-off. For new customer records, need equivalent PUT-TO-STORE locations for crossdock functionality.
250219: Modified insert date, removed TRVSEQ/STO_SEQ/CNTSEQ of 0;
220219: 1500 new locations were added for DC001
Uploaded. Ready for TRI review/signoff.(20190301T0000000)
PRTDSC 4-Low 100319: Uploaded to PROD, for TRI final validation and sign-off. Edited the files to remove all double quotes (").
070319: Data for DC002 received.
020319: Uploaded to PROD, for TRI final validation and sign-off. Edited the files to remove all double quotes (").
280219: New version provided. To be loaded by 010319.
250219: Pending on final list of PRTMST records
Uploaded. Ready for TRI review/signoff.(20190301T0000000)
PRTFTP 1-Critical 100319: Uploaded to PROD, for TRI final validation and sign-off. Edited the files to remove all double quotes (").
070319: Data for DC002 received.
020319: Uploaded to PROD, for TRI final validation and sign-off. Edited the files to remove all double quotes (").
280221: New version provided. To be loaded by 010319.
250219: Pending on final list of PRTMST records
Uploaded. Ready for TRI review/signoff.(20190301T0000000)
PRTFTP_DTL 1-Critical 100319: Uploaded to PROD, for TRI final validation and sign-off. Edited the files to remove all double quotes (").
070319: Data for DC002 received.
020319: Uploaded to PROD, for TRI final validation and sign-off. Edited the files to remove all double quotes (").
280219: New version provided. To be loaded by 010319.
250219: During training, it was identified that some units per case value for items differ for TRI and ARI client in Profit. Putra to provide updated PRTFTP_DTL file by 260219.
Uploaded. Ready for TRI review/signoff.(20190301T0000000)
PRTMST 1-Critical 100319: Uploaded to PROD, for TRI final validation and sign-off. Edited the files to remove all double quotes (").
070319: Data for DC002 received.
020319: Uploaded to PROD, for TRI final validation and sign-off. Edited the files to remove all double quotes (").
030119: Updated file sent. To be loaded by 010319.
280221: New version provided. To be loaded by 010319. Items for ARI/TRI were set to be date controlled, asked Putra to confirm and fix.
250219: Checking from the inventory (stock) upload file provided, some items are not included in this load file. Putra to confirm if these items are to be migrated to JDA by 260219. Sample items: AK304025001,AK304026001,22900055001,20910117001
Uploaded. Ready for TRI review/signoff.(20190301T0000000)
SUPMST 3-Medium 020319: Re-uploaded to PROD, for TRI final validation and sign-off.
250219: Uploaded to PROD, for TRI final validation and sign-off.
[1] Byrone Lachica: