Originally posted by: SystemAdmin
That's an excellent example of thinking outside of the box! I see you're addressing the migration to 5010 that many of our customers have been asking about.
The quick answer is a conditional "yes", if you add a step between 3 and 4:
3a) Delete the trade link from the production database
The reason: the merge only works if the (entire) trade link does not exist in the destination database. It cannot add a 5010 to an already existing 4010, for example.
The definition of "does not exist" depends on the standard. For X12, its a combination of the From and To ISA Trading Partners and GS Application Partners. In EDI-speak, that becomes:
ISA05 + ISA06 + GS02 + ISA07 + ISA08 + GS03
Your idea certainly has merit if you want to perform this "5010 upgrade" in a link-by-link, somewhat manual approach. The manual deletion of the link does take on some risk worth mentioning: if an applicable transmission comes in somewhere between step (3a) and (4), it will be rejected. You'll also have to consider if you will want both the 4010 and the 5010 to exist together for some period of time (I'm assuming we're talking 4010 here).
Another approach would be to use the XML Autoload. That idea is certainly more complicated than yours, but can be automated, albeit with consider programming effort on your part. I'd be happy to forward a detailed approach using XML I've created before; perhaps a quick support call could get that ball rolling.
I must state that the preceding advice is to be considered experimental, untested, and is not part of the documentation or features of the product.
#IBM-Websphere-Transformation-Extender#IBMSterlingTransformationExtender#DataExchange