Adding filter to ERPToLSP data flow

Due to the current update in MG 2024.06, documents with lower variation IDs than what is currently in place are now being blocked by the framework and not passing it throughLSP.

This change particularly affects the shredding of ReceivableTransaction and PayableTransaction BODs, wherein if COR INBOX receives first the BOD with Replace action code and higher variation ID, the BOD with Add action code having lower variation ID will not be consumed anymore by LSP.

Because we do not have control over the sequence of the BODs from ION to COR INBOX and we do not accept Replace action code for both BODs, we recommend implementing a filter in the ERPtoLSP data flow to prevent BODs that are not required from penetrating the COR INBOX.

  1. Go to ION Desk
  2. Click Connect > Data flows, then select ERPtoLSP data flow.
  3. Create a filter between the ERP and LSP connection points by dragging the Filter icon.
  4. Specify a name in the Filter Properties. You can use TransactionBODsFilter.
  5. In the Attributes tab, click + From Content.
  6. Select ReceivableTransaction/PayableTransaction BOD from the list, then select actionCode.
  7. After adding actionCode in the Attributes tab, click the Conditions tab.
  8. Select ReceivableTransaction/PayableTransaction from the Document list.
  9. Click the + button.
  10. In the condition builder, specify this information:
    Name
    Specify a name. You can use actionCodeFilter.
    Type
    Specify Attribute Value Comparison.
    Attribute
    Select actionCode.
    Operator
    Specify =
    Value
    Specify Add.
  11. Click OK.
  12. In the Used Condition list, select the condition that you have created.
    Perform these steps for every document that you add to the filter.
  13. Reactivate the flow.