I see in this post that, at least as of two years ago, we could not set the Adjustment Number (ICADEH.DOCNUM) via Iman even though the field exists to map: https://www.realisable.co.uk/sage-300/ic-adjustments-average-stock-price/

This is consistent with what I am experiencing; I am setting an unique DOCNUM and mapping it but 300 is overwriting it as ADJ001, 002, etc.

Assuming that I still cannot set the DOCNUM, can someone assist with some deduplication help.

What I am trying to accomplish is to insert a series of IC Adjustments from a source Sybase system. Note that the raw data does not have header info, therefore I am grouping all details by transaction date in an Iman hierarchy transform.

I was then planning on using the unique DOCNUM to ensure that detail records were not inserted twice; though I was still working this out (I was considering using reject record in auditing if the unique DOCNUM already existed), it seems my plans are going to be foiled by not being able to set a unique DOCNUM.

Therefore, does anyone have a suggestion for how to manage this?

This challenge doesn't feel like it should be unique to this job; there must be some solid precedent how to peek into the target system to ensure source data is not pulled in over and over.