Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: Trunk
    • Fix Version/s: 16.11.03
    • Component/s: order
    • Labels:
      None

      Issue Links

        Activity

        Hide
        jacques.le.roux Jacques Le Roux added a comment -

        Hi Wai,

        Please give more information in the description, thanks

        Show
        jacques.le.roux Jacques Le Roux added a comment - Hi Wai, Please give more information in the description, thanks
        Hide
        rishisolankii Rishi Solanki added a comment -

        Just to confirm understanding with the ticket;

        • Service createShipment would create both sales and purchase shipment with workeffort.
        • For sales shipment it creates SHIPMENT_OUTBOUND type work effort and for purchase shipment it creates SHIPMENT_INBOUND type work effort.
        • The maps used in the patch shipWorkEffortMap used to create outbound work effort and arrivalWorkEffortMap used to create inbound shipment.
        • Which work effort will be created decided by the condition weather parameters.estimatedShipDate is coming or parameters.estimatedArrivalDate is coming.
        • With existing logic the workEffort.workEffortTypeId, workEffort.currentStatusId and workEffort.workEffortPurposeTypeId is not persist into db as values set into the wrong map. And now fixed in the patch.

        +1 for the fix and should be back ported to branches where it exists.

        Show
        rishisolankii Rishi Solanki added a comment - Just to confirm understanding with the ticket; Service createShipment would create both sales and purchase shipment with workeffort. For sales shipment it creates SHIPMENT_OUTBOUND type work effort and for purchase shipment it creates SHIPMENT_INBOUND type work effort. The maps used in the patch shipWorkEffortMap used to create outbound work effort and arrivalWorkEffortMap used to create inbound shipment. Which work effort will be created decided by the condition weather parameters.estimatedShipDate is coming or parameters.estimatedArrivalDate is coming. With existing logic the workEffort.workEffortTypeId, workEffort.currentStatusId and workEffort.workEffortPurposeTypeId is not persist into db as values set into the wrong map. And now fixed in the patch. +1 for the fix and should be back ported to branches where it exists.
        Hide
        jacques.le.roux Jacques Le Roux added a comment -

        Thanks Wai for report and patch, Rishi Solanki for clear explanation,

        Wai your patch is in
        trunk r1799767
        R16.11 r1799768

        R15.12 and R14 are not concerned (OFBIZ-6958 done later)

        Show
        jacques.le.roux Jacques Le Roux added a comment - Thanks Wai for report and patch, Rishi Solanki for clear explanation, Wai your patch is in trunk r1799767 R16.11 r1799768 R15.12 and R14 are not concerned ( OFBIZ-6958 done later)
        Hide
        wt Wai added a comment -

        Rishi Solanki: Your statements are correct.

        Show
        wt Wai added a comment - Rishi Solanki: Your statements are correct.

          People

          • Assignee:
            jacques.le.roux Jacques Le Roux
            Reporter:
            wt Wai
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development