Order Management

Get Involved. Join the Conversation.

Topic

    Zia Ansari
    Invoicing task before shipping task.
    Topic posted December 6, 2018 by Zia AnsariRed Ribbon: 250+ Points 
    62 Views, 8 Comments
    Title:
    Invoicing task before shipping task.
    Content:

    Dear All,

    Let me know if anyone has created a custom orchestration process wherein the Invoice/Billing is done before Shipping or other custom tasks? Please share steps if that worked.

    Regards,

    Zia

    Comment

     

    • Sunil Dabekar

      Hello Zia,

       

      Although I have personally not done such set up,but  I understand from others' 

      You need to add the invoice step before shipping or scheduling (which ever is needed) in the orchestration process definition.

      However,I would like to understand the reason why you are wanting to reshuffle these steps (if i may).

       

      Thanks,

      Sunil

      • Zia Ansari

        Hi Sunil,

        Thanks for the response.

        We have a requirement wherein a sales order must be kept open ( let's say on pause) until certain documents are attached to SO manually after billing is done. Therefore wanted to know the possibility of introducing pause task after Invoicing step.

        Regards,

        Zia

        • Sunil Dabekar

          Hi Zia,

           

          I did test this flow to invoice first,ship next and here are my findings

          1. You need to have scheduling step as first step regardless.

          2. Then invoicing set can be called.

          3. Followed by Shipping (presuming you may or may not always use reservation)

          This flow works.

          However I see it risky from the change order perspective considering that you would have already generated an AR Txn. How are you planning to handle this if there were to be 

          1. Qty Decrease (Most risky)

          2. Qty Increase

          3. Line cancellations

          Thanks,
          Sunil

        • Sunil Dabekar

          Hi Zia,

           

          I did test this flow to invoice first,ship next and here are my findings

          1. You need to have scheduling step as first step regardless.

          2. Then invoicing set can be called.

          3. Followed by Shipping (presuming you may or may not always use reservation)

          This flow works.

          However I see it risky from the change order perspective considering that you would have already generated an AR Txn. How are you planning to handle this if there were to be 

          1. Qty Decrease (Most risky)

          2. Qty Increase

          3. Line cancellations

          Thanks,
          Sunil

    • Prasad Kinkar

      Hi Zia,

      I had done orchestration customization for many processes, to name few - bill only and ship only to add specific tasks as per business need.

      I guess you are trying to create custom orchestration for prepayment flow ..isn't it?

      Nevertheless, you could still - Add invoice tasks prior to shipment, set dependencies correctly and validate. Please be careful if you are using branching and merging steps. Rather than creating the process from scratch use the seeded flow and copy it to edit (Seeded -DOO_OrderFlowGeneric). That way it will be quicker and accurate.

      Hope this helps.

      Thanks,

      Prasad.

    • Prasad Kinkar

      Sure Zia. Keep us posted.

      Thanks,

      Prasad