Issue
Issue No
Issue Name
Issue Description
Response
Submitted by ReAssign To
Date Submitted Priority
Expected Date New Status
Version In Version
Orig Assigned To Billable
Now Assigned To Customer
Priority Customer Status
Status Customer Product
Billable Next Action Date  
Customer Contact Information (When Applicable)
Customer Added
Name
Phone Number
Email Address

Issue Documents
Document Upload/Delete Documents List Attached To This Issue

 


(Select File To Delete From List)
162-SP-AddShipmentAparCost.png
20240131AlejandraEmailWScreenshots.docx
20240207AlejandraEmailWScreenshots.docx
26838 Omni APARAUX without APARCODE.docx
26838_Alter_AddShipmentAPARCost.sql.txt
3928829Screenshot.jpg
846493Screenshot.jpg
Omni-Prod-AddShipmentAparCost.png
SP-UpdateShipmentAparCost-162.png


Response History
ByDateCustomer
Can View
 Note Status?ResponseAssigned ToPriorityStatus 
Julie Lopez 3/4/2024 1:27:55 PM NO Nathan Palmer High Waiting for Release
Julie Lopez 3/4/2024 1:14:10 PM NO Confirmed that SP AddShipmentAPARAux and AddShipmentAPARCost both setup APARcode correctly. Ok to close now. Julie Lopez High EDI Follow Up
Julie Lopez 2/22/2024 5:04:33 AM NO Julie Lopez High EDI Follow Up
Julie Lopez 2/22/2024 4:35:47 AM NO Omni closed this on 2/20.

I just want to double check that the SP on 12/14 at Omni includes the aparcode. (Make sure the PRS was installed on 2/20)
Julie Lopez High Installed
Julie Lopez 2/20/2024 9:15:51 AM YES Installed in WT on 2/20/2024 Julie Lopez High Installed
Julie Lopez 2/18/2024 8:31:29 PM YES ****************************************
Standup status 2/20:

This will be installed on 2/20

*******************************************
Julie Lopez High Waiting for Release
Julie Lopez 2/16/2024 9:34:46 AM YES This will install the weekend of 2/17 Julie Lopez High Waiting for Release
Julie Lopez 2/12/2024 1:44:21 PM NO Julie Lopez High Waiting for Release
Tressie Davis 2/12/2024 8:00:48 AM YES From Bob M
Can you please advise each letter and definition for the EDI Alert section of a vendor cost line?

So far, I have only seen 2.

S = 204 Submitted
B = Booked

Are there more?
__

Replied:

Your EDI team made a request for correcting the EDI Alert column and it is being worked under ticket 26838 which I believe is waiting for your next WT install.

Below are the codes Alejandra indicated are expected (this is what you will see once 26838 goes into production).

S – 204/211 has been submitted/queued

B – 204/211 has been booked (the edi transaction has been sent)

C – 204/211 has been accepted by the vendor

R – 204/211 has been rejected by the vendor
Julie Lopez High Waiting on Feedback
Tressie Davis 2/8/2024 10:37:36 AM NO From Alejandra
Noted, thanks.
Per our conversation during standup, the tentative date for the next WT release is 03/02.
Julie Lopez High Waiting on Feedback
Julie Lopez 2/7/2024 11:39:19 PM YES Note to Alejandra:

This does require an install of Worldtrak. I am following up with Brian to see when an update is being scheduled. Last I heard it was mid February.

Noted on the ticket that this is ready for install.
Julie Lopez High Waiting on Feedback
Julie Lopez 2/7/2024 11:37:58 PM YES ****************************************
Standup status 2/8:

Alejandra testing is complete - ready for WT Install

*******************************************
Julie Lopez High Waiting on Feedback
Tressie Davis 2/7/2024 3:38:14 PM NO From Alejandra (20240207AlejandraEmailWScreenshots.docx):


Yes, we tested this morning with Housebill # 7593883 / Shipment # 5345883 and it’s a pass!
Can the fix be promoted to prod on its own or will it need to be part of the next release?
Please let us know.

Documented the steps during our testing session for historical purposes.

1. After booking/sending the alert the EDI Alert column status changed to ‘S’ / 204 submitted.



2. After the job was ran the EDI Alert column status changed to ‘B’ / 204 Booked.


3. Inserted a 997 followed by a 990–– acceptance message and the EDI Alert column status changed to ‘C’ / 204 Accepted.



4. Added a new cost line for the same vendor under LD and tendered. Inserted a 990–– rejection message and the EDI Alert column status changed to ‘R’ / 204 Rejected/Decline.



NOTE:
We tried inserting a rejection message after an acceptance, but it didn't apply.
Similarly, we attempted to insert an acceptance message after a rejection, but it didn't apply either.
This means that vendors will need to contact us via email or phone if they accidentally accept or reject a tender.
Julie Lopez High Waiting on Feedback
Tressie Davis 2/7/2024 10:44:27 AM NO 2/7 Followed up w/Alejandra
Has Omni had an opportunity to test? Does everything look good in Stage be and is it ready to move into Prod?
Julie Lopez High Waiting on Feedback
Tressie Davis 2/6/2024 10:19:39 AM YES From Alejandra
Noted, thanks.
We’ll test and share feedback ASAP.
Julie Lopez High Waiting on Feedback
Julie Lopez 2/5/2024 11:03:07 PM YES ****************************************
Standup status 2/6:

Updated Stage A and Stage B. Asked Alejandra to test again.

*******************************************
Julie Lopez High Waiting on Feedback
Julie Lopez 2/5/2024 11:02:02 PM NO Need to do a doublecheck on 12/14 release to make sure that when AddShipmentAPAARAUX is called, that the aparcode is always passed. If it is, then no more changes needed for this SP. Julie Lopez High Installed
Julie Lopez 2/5/2024 11:01:08 PM NO Updated SP AddShipmentAPARCOST for 12/14 release only.

Installed on Stage A and Stage B
Julie Lopez High Installed
Tressie Davis 2/1/2024 9:37:04 AM YES 2/1 From Julie
I was able to recreate this issue. We are looking at this today.
Julie Lopez High Installed
Tressie Davis 2/1/2024 9:36:14 AM YES From Alejandra:

We tested this just now using HAWB#7593882 and the EDI alert column was not updated through our test.
Please review and let us know once this is ready for testing again.




Just for reference, these were the values we were expecting to see:

S – 204/211 has been submitted/queued

B – 204/211 has been booked (the edi transaction has been sent)

C – 204/211 has been accepted by the vendor

R – 204/211 has been rejected by the vendor

(Attached Doc w/Screenshots 20240131AlejandraEmailWScreenshots.docx)
Julie Lopez High Installed
Julie Lopez 2/1/2024 7:27:40 AM YES ****************************************
Standup status 2/1:

Alejandra found an issue with shipment 5345671.
We are looking into it.

*******************************************
Julie Lopez High Installed
Julie Lopez 2/1/2024 7:02:45 AM NO Installed in Stage A and Stage B on 1/31 Julie Lopez High Installed
Tressie Davis 1/30/2024 9:58:56 AM YES 1/30 from Alejandra
Noted, thanks.
We’ll test today and advise.
Julie Lopez High Ready For Install
Preeti Nevrekar 1/30/2024 12:28:33 AM NO Julie made the fix dated 1/29/2024 9:51:39 PM in below changesets in both current and 12/14 version.

Also fixed a typo in update query where tbl_shipmentaparaux is updated for the EDI204Status added in ticket # 24129 changeset 58418

Worldtrak Current version
Changeset 71413
SendVendorAlert.aspx.vb

Worldtrak 12/14 version
Changeset 71414
SendVendorAlert.aspx.vb
Julie Lopez High Ready For Install
Julie Lopez 1/29/2024 9:53:45 PM YES ****************************************
Standup status 1/30:

Tested successfully on Stage A.

Installed in Stage B - ready for Omni to test

*******************************************
Preeti Nevrekar High Re-Work
Julie Lopez 1/29/2024 9:51:39 PM NO Preeti,

Working with Brian, we think the changes you made to EDI204Vendor and EDI211Vendor are enough. Brian is concerned about changing the SPs due to a possible issue with the 'C' records. Looking at your code in these 2 routines, it does an insert if it can't find the record, so that was what was needed.

I found one more place where tbl_shipmentaparaux is updated for the EDI204Status. It is SendVendorAlert. Could you put the same code you did for EDI204Vendor and EDI211Vendor in this as well?

I'm going to delete out the SP script from the ticket. I think we will be all set with this last change.

Thx
Preeti Nevrekar High Re-Work
Julie Lopez 1/25/2024 6:55:07 AM NO Note for Julie - WT - is 'c' code assumed anywhere ? Julie Lopez High Questions
Julie Lopez 1/25/2024 6:49:04 AM NO Julie Lopez High Questions
Preeti Nevrekar 1/25/2024 5:02:07 AM NO Julie,

Attached is the updated 12/14 script for AddShipmentAparCost from Omni production.
'SP_AddShipmentAparCost-12-14.txt'

Om Omni 'UpdateShipmentAparCost' there is no code where we inset/update in tbl_shipmentAPARAux.

But on 162 we check if the record exists in tbl_shipmentAPARAux based on OrderNo/Seqno

If yes, we update VendorCompleteDate flag based on the OrderNo/Seqno if not we insert the record with Aparcode='V'

Attached is the screenshot of SP UpdateShipmentAparCost from 162 'SP-UpdateShipmentAparCost-162.png'

Not sure if we need to include this change in Omni UpdateShipmentAparCost sp
Julie Lopez High Questions
Julie Lopez 1/24/2024 9:15:53 PM NO Question to Brian:
Brian, do you see any problems with fixing AddShipmentApArCost and UpdateAddShipmentAPARCost in 12/14, to include setting APARCODE = 'V' for tbl_shipmentaparaux? This is causing an issue at Omni because a 204 flag isn't showing because the record is written without the code being populated. Not sure why that hasn't caused a problem with anything else?
Preeti Nevrekar High Open
Julie Lopez 1/24/2024 9:12:27 PM NO Thank you Preeti - could you make a script to fix the SP for the 12/14 release and attach to this issue? Also I believe the same problem is in UpdateShipmentAparCost.

I'll follow up with Brian on how to release/install.
Preeti Nevrekar High Open
Julie Lopez 1/24/2024 9:09:39 PM YES ****************************************
Standup status 1/25:

Tested successfully on Stage A.

Coordinating an install into Stage B, but resolving issue with SP first.

*******************************************
Preeti Nevrekar High Open
Preeti Nevrekar 1/24/2024 6:28:22 AM NO Julie,

On Omni Production in SP AddShipmentAparCost we are not inserting the AparCode code value to 'V' in tbl_ShipmentAparAux

See the attached screenshot
'Omni-Prod-AddShipmentAparCost.png'

On 162 in SP AddShipmentAparCost we do insert the AparCode value=V in tbl_ShipmentAparAux and this is the issue.

See the attached screenshot
'162-SP-AddShipmentAparCost.png'

If we add the highlighted code from 162 screenshot in AddShipmentAparCost 12/14 version this will fix the issue.

Also, I checked the Worldtrak code both (162 and 12/14) version and did not find any place where we insert the records in tbl_ShipmentAparAux without AparCode.
Julie Lopez High Questions
Julie Lopez 1/23/2024 8:20:38 AM NO Tested successfully on Stage A, but noticed that some records are created in tbl_shipmentaparaux without the aparcode value.


An example in PROD from January 2024 is file # 5711616. See screen shot attached

Preeti, could you look into Worldtrak, and see where this may be creating without an aparcode. Is this just an issue with the 12/14 release? the SP that creates most of the records is AddShipmentAPARAUX.
Preeti Nevrekar High Re-Work
Julie Lopez 1/23/2024 8:20:04 AM YES ****************************************
Standup status 1/23:

Tested successfully on Stage A.

Coordinating an install into Stage B.

*******************************************
Julie Lopez High Installed
Julie Lopez 1/23/2024 8:14:48 AM YES Tested successfully on Stage A

Ready for Stage B install
Julie Lopez High Installed
Julie Lopez 1/23/2024 7:10:18 AM NO Installed in Stage A on 1/22 Julie Lopez High Installed
Julie Lopez 1/18/2024 9:53:13 AM YES ****************************************
Standup status 1/18:

Issue identified that is not updating EDI204 Status.
Completed fix, does involve WT update.
Coordinating an install to Stage A.
Still looking into 990 response.


Medium lift - Possible OutgoingEDI204 or WT update
*******************************************
Julie Lopez High Ready For Install
Preeti Nevrekar 1/17/2024 2:48:51 AM NO Julie, made the fix in the below changesets in current and 12/14 version only.

We do not have the below code from the example in 4/12 version. Looks like changes related to EDI204vendor / EDI211Vendor from Ticket # 24129 is not merged in 4/12 yet.

Worldtrak current version
Changeset 71241
EDI204Vendor.vb
EDI211Vendor.vb

Worldtrak 12/14 version
Changeset 71242
EDI204Vendor.vb
EDI211Vendor.vb
Julie Lopez High Ready For Install
Julie Lopez 1/16/2024 11:21:21 AM NO Preeti...Enter time to Omni Worldtrak support. Its not billable. Thx! Preeti Nevrekar High Open
Julie Lopez 1/16/2024 11:15:33 AM NO Note for Julie - Stage A test shipment is file #5335449 Preeti Nevrekar High Open
Julie Lopez 1/16/2024 11:14:20 AM NO Preeti - One more thing is needed to wrap this up. Could you make the following change in Worldtrak - EDI204Vendor and EDI211Vendor?

When the EDI204Status field is updated in tbl_shipmentaparaux (see code example), please create the record in tbl_shiopmentaparaux if it doesn't exist.

Look for the code in the example (right now, some updates are failing because the tbl_shipmentaparaux record does not exist yet):

If ConsolNo = 0 Then
strsql = "Update tbl_ShipmentAPARAUX set edi204status = 'S' WHERE APARCOde = 'V' and FK_OrderNo = " & OrderNo & " and APARSeqno = " & VendorSeqNo
Else
strsql = "Update tbl_ShipmentAPARAUX set edi204status= 'S' WHERE ConsolNo = " & ConsolNo
End If
objship.ExecuteQueryText(strsql)



You may already know how to do this, but I was thinking to let the update occur, and only do the write, if the update fails. Here's a link of some ways you can test for a successful update:

https://stackoverflow.com/questions/2963703/how-to-know-whether-a-sql-update-statement-executed-successfully-or-failed

This needs to be in current, 4/12 and 12/14 release. 12/14 release is the priority one.
Preeti Nevrekar High Open
Julie Lopez 1/16/2024 11:04:38 AM YES Discussion w/Brian:

Quick question - should every tbl_shipmentapar for vendors also have a related tbl_shipmentaparaux record?

We didn't introduce that table until later in the
game...so, it most likely depends on the release - BUT -
theoretically, the answer should be yes. Which release
are you interested in?

Shouldn't a 7/23 record exist? Its been at least a year, right?

It just really depends on what mod we moved in for
them that actually writes to the table. Since we initially added that table for A/R (I think), the aparcode type of 'V' was added later...So, if some tickets were merged in that needed it got merged in and others did not...there would be the issue. What field in that table are you needing an entry for?


EDI204status - so are you saying that I should do a mod that if the record doesn't exist, write it?


I think you would have to...Not sure if you can tell easily from the code which tickets are missing, but that would be another option (this would probably get very messy though).
Also - will consolidations be involved? If so, reminder: when you write that record, the fk_orderno and the consolno will be the actual consolidation#. The fk_orderno will NOT be the large number starting with a '9' because the 12/14 release doesn't have the 'consol mod' that we did a long time ago. If you find out you need to add similar logic for 04/12, that release has the 'consol mod' in it...therefore, the fk_orderno would have to be the large number for those records. Make sense?


I think I follow for the consol write, makes sense.
Julie Lopez Normal In progress
Julie Lopez 1/16/2024 9:45:36 AM NO I may have found where this is not working. The update in EDI211Vendor is not getting a hit on tbl_shipmentaparaux because the vendor sequences do not align. MKSLAS is vendor seq 1 in tbl_shipmentapar where it is not in tbls_shipmentaparaux. (only vendor seq 2 is in that table).

Asked Brian if there should be matching records in both tables (ie why doesn't tbl_shipmentaparaux not have a related entry)
Julie Lopez Normal Waiting on Feedback
Julie Lopez 1/16/2024 9:00:01 AM YES ****************************************
Standup status 1/16:
Issue identified that is not updating EDI204 Status.
Working on a fix, but it may involve a Worldtrak update.
Still looking into 990 response.

Will also be testing in Stage A

Medium lift - Possible OutgoingEDI204 or WT update
*******************************************
Julie Lopez Normal In progress
Julie Lopez 1/15/2024 10:37:45 PM NO Julie Lopez Normal In progress
Julie Lopez 1/10/2024 9:06:48 AM NO Julie Lopez Normal In progress
Julie Lopez 1/9/2024 9:50:07 AM NO Julie Lopez Normal In progress
Julie Lopez 1/8/2024 7:45:36 AM NO Monty Munro Normal In progress
Julie Lopez 1/8/2024 7:41:53 AM NO Monty, I really need an update on this ticket. Let me know where you are at with this because Omni is re-starting their weekly meetings today and this is one of the last ones for their first Sprint. Thanks. Monty Munro Normal In progress
Julie Lopez 1/3/2024 8:39:08 AM NO Monty - checking into this - is there an update yet? Monty Munro Normal In progress
Julie Lopez 12/19/2023 8:18:04 AM NO Monty Munro Normal In progress
Julie Lopez 12/17/2023 8:14:09 PM NO Monty Munro Normal In progress
Tressie Davis 12/15/2023 10:06:57 AM NO 12/15 From Monty
I am still working toward determining the reason for the erratic EDI Alert values. I hope to have a solution soon.
Monty Munro Normal In progress
Julie Lopez 12/14/2023 9:28:54 PM NO Checking in for an update so that it can be provided to Omni during daily standup meeting on Friday. Monty Munro Normal In progress
Julie Lopez 12/13/2023 8:08:03 AM NO Monty Munro Normal In progress
Monty Munro 12/13/2023 8:03:04 AM NO going through the troubleshooting process Monty Munro Normal In progress
Julie Lopez 12/13/2023 7:53:24 AM NO Monty Munro Normal Questions
Julie Lopez 12/13/2023 7:50:36 AM NO Monty Munro Normal Questions
Julie Lopez 12/13/2023 7:49:56 AM NO Monty Munro Normal Questions
Julie Lopez 12/6/2023 9:49:51 PM NO Monty, have you had a chance to look at this? Any findings? Any questions?

Tressie is on daily meetings with Omni and ticket 26788 is a daily one being checked. A Worldtrak update is coming apx 12/16. Omni will most likely want this fixed for that, and it has to go to Stage A, then Stage B before then.
Monty Munro Normal Questions
Monty Munro 12/5/2023 7:29:48 AM NO Monty Munro Normal In progress
Julie Lopez 12/4/2023 8:52:28 AM NO The EDI Alert Column is on the Costs.aspx page. When a 204 or 211 is requested, the tbl_shipmentaparaux.EDI204Status field should be updated but it did not for these example shipments. Because it isn't, it may have caused the OB204 job and the IB990 job also not to update the value as well.

Can you investigate to see why these updates did not take place for the vendor NextGen?
Monty Munro Normal Open
Julie Lopez 11/13/2023 9:27:39 AM NO Julie Lopez Normal In progress
Tressie Davis 11/13/2023 8:31:44 AM YES Created as separate issue from Ticket: 26788 Julie Lopez Normal Open
Tressie Davis 11/13/2023 8:30:24 AM YES Assigned to Julie Julie Lopez Normal Open