Loop through add-on's in Process.SupplierInvoice

I'm working on mapping add-on codes in Process.SupplierInvoice BOD's to consolidate values in flight. I have a workflow setup to accept SupplierInvoice/SupplierInvoiceHeader/Charge/ID as input and write back to as output. Within the workflow, I have the input parameter from the BOD running through a decision. The decision either passes the value back out because it's not on the match list or it runs through a decision table to map the value. This is working if there's a single Charge element in the BOD but any more than that are ignored. I know I need to now loop through the Charge elements but not sure of the best way to do so. Would this be done in the workflow?

Thank you!

Find more posts tagged with

ION Mapper & Scripting

Accepted answers

All comments

Carsten Steinhoefel

Have you looked at Structures? https://docs.infor.com/inforos/2024.x/en-us/useradminlib_cloud/default.html?helpcontent=iondeskceug_cloud_osm/lsm1436532368725.html&hl=structures

You would create a structure that has the Header and then Charge nodes. You can create a loop with a counter parameter that you increase each iteration with a Set Parameter step. The Set Parameter step also has options to select the nth value from the structure.

John Chapman

I'm not familiar with structures. Once a structure is setup, how would the loop know how many iterations to use to ensure all Charge nodes have been updated?

Carsten Steinhoefel

There is a function to Count Values in the Set Parameter step. The functions for Structures are at the bottom of the documentation page https://docs.infor.com/inforos/2024.x/en-us/useradminlib_cloud/default.html?helpcontent=iondeskceug_cloud_osm/lsm1436532191863.html&hl=set%2Cparameter

You can check against that parameter in your loop condition.

John Chapman

I think I'm in the right direction but I'm still missing something for this workflow to read all Charge nodes. The workflow looks like this:

The vendor ID is read from SupplierParty/PartyIDs/ID in the structure (should this be a separate structure from the Charge structure)
Initialize the record ID to read from the structure
Count the Charge elements
Enter the loop and read the first ID element based on the record ID
Use decision tree to either pass through and write to a temp variable because it doesn't match a set of Charge ID values or use the decision table (vendor ID and Charge ID are inputs) to translate the Charge ID and write to the same temp variable
Increment record ID
Write value from decision tree temp variable to parameter mapped to the output for the data flow
If record ID <= record count, loop again else end

I added a notification before the loop and I can see the record ID and record count are correct with the sample I have (1 and 2 respectively). Is this maybe something with the loop setup?

Carsten Steinhoefel

This looks ok. I am just not sure about the temp variable and parameter you mention. Unless you concatenate with previous values it will overwrite the values in each loop. Therefore I would expect the final values of these to be that of the last record in the structure. Is that what you are seeing?

(You can add notifications inside the loop to check what is happening)

Carsten Steinhoefel

I think I have only now completely understood what you are trying to do.

You want to basically modify a value in each of the charges in a Document Flow. I was always looking at the Workflow part of it, not the Doc Flow.

Apologies, I may have led you into the wrong direction there. I don't think you can use the values in a structure and map them back to the BOD.

Could you create a comma-separated list, map it into a UserArea field and use a mapping in the Dcoument Flow to map to the entries? Maybe possible but doesn't seem very elegant.

Are the business rules very complex? Could they be coded into a Script instead? Then the script could modify the BOD. This would definitely work.

If Business Rules need to be used, they can also be called via API. Good candidate for an API Flow but they can only process JSON.

John Chapman

That's what I'm noticing, yes. It only seems to update the first element when using the workflow with the last value of the loop.

The rules aren't very complex. It amounts to a case statement at a high level. As an extra wrinkle, I so far only need to translate a handful of values for a specific vendor. I had tested using a map and was able to use a UDF to map the value but got stuck trying to incorporate the vendor ID. Is there a way to make this work? Otherwise I think I can pull from other scripts we have to create something for this use case.

@prabodhaa thank you for the tip on using Merge too. I'll check that out as well.

unknown

in some scenarios multiple process BODs can be sent for the same document (e.g. SupplierInvoice) so if that is possible you could use a splitter and the rules api with a merge and send a process BOD per line. might look something like this:

(note - you'll want to handle acknowledgements!)

Copyright © 2025 Infor. All rights reserved.