This deals with implementing the logic to potentially split requisitions during the approval stage.

Multiple conditions to split a requisition:

1. Parent node has a partner node

2. There is a supply partner with an entry for that partner node and requisition's program

3. That entry has a facility that matches the requisition's facility

4. That entry has a product that matches any products in the requisition line items

All conditions must be met before splitting the requisition.

Acceptance Criteria

• The splitting occurs after the first approval and if the above conditions are met.

• After the split, there should be:

  • X requisitions, where X is the number of partners handling the requisition

  • the original requisition

    • data for products that are supplied by partners should be removed (or changed to zero) and in the remarks column there should be a text that informs the product is handled by supply partner

  • example: one standard requisition + one CHAZ requisition

  • for now, the edge case that one supply partner supplies all products from the requisition is out of scope from this ticket (because the situation never happens) but the implementation should be easy to modify to handle the situation.

• For each of the partners there is a requisition created

  • Requisition should be in the IN_APPROVAL/APPROVED state (depending on the number of supervisory nodes the requisition is going through)

  • The original is added as a parameter in the extra data

  • requisition contains only products that they supply (all the same columns exist). It should not contain products supplied by any other partners.

  • CHAZ can edit the approved quantities

• Standard requisition always contains all line items regardless of who supplies, but with comments or notes in the remarks column identifying there is a different supplier (this can also be some sort of visual identifier)

• After the requisition is split, the created requisitions are not rejectable.

  • Once the requisition has been split, it cannot be rejected.

• If requisition is not split then the requisition should follow the normal requisition workflow.