Many a client has requested to have custom filenames using the HIPAA_EDI adapter.
I originally planned on using a custom ASM pipeline component and setting the ghost port to batching, and within the orchestration setting the RecievedFileName.
Found out that when that happens, no file is created, also, no errors are created! This really smells like a bug, as there is no documentation on this!
After contacting Microsoft, and submitting a ticket, this is the response I got back:
The HIPAA pipeline is not architected to support batching. It simply does a one-on-one translation from XML to EDI and that’s it.
The batching mechanism is depending on the data in the audout table and the HIPAA pipeline does not persist any data.
The only way you can create outbound EDI batches is via the HIPAA EDI adapter.
I ended up having to re-engineer the process so that (written about here), by single threading the entire process, files do not get batched together and files can be accounted for.