Uploaded image for project: 'CFA MX '
  1. CFA MX
  2. CFAMX-14950

Scheduled Orders - Troubleshooting & AuditLogging

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Sprint:
      2021.R5 New Features Sprint 2, 2021.R5 New Features Sprint 3
    • SCRUM Team:
      Brotherhood of Mutants
    • Story Points:
      3
    • Work Type Classification:
      Sustaining

      Description

      Details

      The intention of this story is to track time spent troubleshooting Scheduled Orders. We will add this story to the current sprint and update the description and AC for testing.

      AC

      The intent of this story was to get the SM task up and running and performing correctly, and it seems to be doing just that

      • You can either look at CFAMX-5961, and read through all of the stores
      • Before starting I suggest pulling the existing test cases, lots of work was done around Scheduled Orders when we first implemented it
      • Below are my thoughts an, overview, and some tests that I conducted:
      • Configurations:
      • Related to the Create Scheduled Orders - Service Method Processing Task
        • Create Scheduled Order - Previous Order Threshold = 1
          • Value is set in hours
          • This config is used to look back X and see if an order has been created for the same vendor within this period, if so, do not create another order, from teh schedule
          • Note: Draft orders are not included in orders that have been submitted
          • See: select * from tbAudit with(nolock) where AuditID = 1054918
        • Auto Create Orders Within X minutes of Order Schedule Cut off time = 30
          • This config gets the task to look forward a specified number of minutes
          • If there is a schedule that has a cut off time that is less than the current time+ the specified number of minutes, the order is created
        • Server Manager task scheduled to run at 5, 20, 35 and 50 every hour

      Tests

      1. 2:53pm - Created a schedule with a cut off time of 3:15pm (THE MARTIN-BROWER COMPANY)

      • Expected - 3:05pm Order is created in Draft Status
      • Actual - 3:05pm, the task executed and the Draft order was created
        • select * from tbAudit with(nolock) where AuditID = 1054908
          Scheduled Order Auto Created Sales Order created from Schedule. SalesOrderId: 3969878, EntityID: 671, ActionItemID: 8903, ActionItemInstanceID: 0
        • select * from tbTaskQueueMessage with(nolock) where TaskQueueMessageID = 3364457
      • Order Auto Submitted at 3:15

      2. 3:16pm - Created a schedule with a cut off time of 3:30pm

      • Expected - 3:20pm, Order should not be created
      • Actual - 3:20pm Order was not created
        Audit results:
      • Scheduled Order Not Created Scheduled order received but not created - recent order already placed for this vendor (THE MARTIN-BROWER COMPANY.) Most recent order Creation Date: 5/26/2021 3:15:48 PM, Current Store Time: 5/26/2021 3:20:50 PM, Threshold (hrs): 1, ActionItemInstanceID: 4731: This Action Item Instance status is changing to Placed and Assigning Supply Order Id as: 3324110
        • THE MARTIN-BROWER COMPANY
      • Scheduled Order Not Created Scheduled order received but not created - cutoff time is still too far in the future. EntityID: 671, ActionItemDate: 5/26/2021 12:00:00 AM, OrderCutoff (mins): 1140, Current Store Time: 5/26/2021 3:20:50 PM LookForward (mins): 30, ActionItemInstanceID: 0
        • MBM Order for 1900

      3. 3:36pm Create MBM schedule for 3:45pm

      • Expected - 3:50pm Order is Created and Auto submitted (the cutoff is in the past)
      • Actual - 3:50pm The order was created and auto submitted
      • select * from tbAudit with(nolock) where AuditID in (1054942,1054941,1054940,1054939)

      4. 3:42pm - Created a schedule with a cut off time of 4:00pm (Maines)

      • Expected - 3:50pm Order is created in Draft Status
      • Actual - 3:50pm Order was created in Draft Status
      • Note: this order did NOT get submitted at 4:00pm, as there were No Items, this is good, and is a valid case/test
      • select * from tbAudit with(nolock) where AuditID = 1054963
      • Purchase Order Was Not Created Purchase Order was not created because no items were on the order. Order Detail: EntityId: 671, VendorId: 148, Delivery Date: 5/27/2021 3:45:00 PM, Cover Until Date: 6/3/2021 3:45:00 PM

      5. 3:54pm - Created a schedule with a cut off time of 4:15pm (Maines)

      • Expected - 4:05pm Draft Order should be created, as last order was still in Draft
      • Actual - 4:05pm Draft Order was created
      • Manually viewed the order, and changed the Qty to 1
      • 4:15pm, the Order was Auto Submitted, as expected

      6. 8:08 - Manually placed an order for Martin Brower, for delivery May 27, 2021 8:15 PM

      • Create a schedule to match the order just placed
      • 8:11pm Manually Ran SM Task
      • The scheduled order was not created, instead, the manually placed order was attached to the order schedule
      • select * from tbAudit with(nolock) where AuditID in (1055201)

      7. 8:14pm Place order for Maines, for delivery on May 28, 2021 6:00 AM

      • Create a schedule for delivery tomorrow, 5/27, not 5/28 (the manual order just created)
      • 8:16pm Manually ran SM task
      • The scheduled order was not created, instead, the manually placed order was attached to the order schedule
      • select * from tbAudit with(nolock) where AuditID in (1055208)
      • Note; This means that the job does not look at the delivery and cover until dates, the modal is left to deal with that, the job just rolls any orders into the schedule

      Note about audit records

      From what I can tell we write something to the audit every time the job runs and there is still an order to be placed. Once the last (latest in terms of time) schedule is completed, the audits are no longer written. Probably because there is nothing for the task to assess.

        Attachments

        1. screenshot-1.png
          45 kB
          Kevin Reid
        2. screenshot-2.png
          39 kB
          Kevin Reid

          Issue Links

          1.
          Review Test Scripts QA Task Done Tristan Strong

          0%

          Original Estimate - 0.5h
          Time Not Required
          2.
          Deploy QA Task Done Unassigned

          0%

          Original Estimate - 0.5h
          Time Not Required
          3.
          Functional Review with QA Dev Task Done Unassigned

          0%

          Original Estimate - 0.5h
          Time Not Required
          4.
          DIT Dev Task Done Unassigned

          0%

          Original Estimate - 0.5h
          Time Not Required
          5.
          Design Review Dev Task Done Unassigned

          0%

          Original Estimate - 0.5h
          Time Not Required
          6.
          Dev testing/debugging Dev Task Done Kevin Reid (Inactive)

          100%

          Original Estimate - 7h Original Estimate - 7h
          Time Spent - 8h
          7.
          Improve logging Dev Task Done Kevin Reid (Inactive)

          100%

          Original Estimate - 7h Original Estimate - 7h
          Time Spent - 7.5h

            Activity

              People

              • Assignee:
                jason.powell Jason Powell
                Reporter:
                jason.powell Jason Powell
              • Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 16.5h
                  16.5h
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 15.5h Time Not Required
                  15.5h

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.