I am trying to create (back to the drawing board kind of) a common key or some method of relating a single record in a flat file to a single ST after batching from the public queue. Something that will survive the batching process. Eliminating batching is not an option.
Currently, I am taking values in the flat file record that are mapped in the X12. For example, I have an account number, serial number and a dolar value. all three of which will make a transaction unique. Those 3 values are mapped into the X12 where I can retreive them by doing a light convert to values and extracting them there as well, long story short, in the delivery service. That way, when the 997 comes back, I can tell our customeer that the 3rd transaction from the 8th account in the original parent file was rejected. The results from each step are reported to an external DB.
The problem there, is if the business partner sends the exact same one again, I can not record the new transaction as unique while maintaining the relationship in the acknowledgement since the key I produce will be the same. Is there some corelation ID unique to the ST that I can extract (that survived the public queue) from the batched edi that was produced in the flat file parsing process?
Thanks in advance…