Batching Subscription criteria vs. Party ID between systems

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Batching Subscription criteria vs. Party ID between systems

Viewing 1 reply thread
  • Author
    Posts
    • #24566

      In the X12 or Edifact Enveloping subsystem, you set up a batch orchestration to collect and envelope your EDI transactions.  This Batch has a filter criteria where we specify To Be Batched = true and Party ID = the UID # of the current party.

      The case exists where I can have the MSI migrate party definitions between systems, but it does not necessarily keep the Party ID in synch. 

      So you end up with a batching definition referencing Party A’s ID, (say, 5),  on the source system (say Dev), but when you migrate to QA, Party A’s ID is changed to 6 on that system, because 5 was already used; however the imported Party Batch settings have the filter referencing 5, the appropriate value on the old system.   

      What was really intended to manage this? In my Apllications, I always look up the party ID on that system when I need it, because I know I can’t rely on it to be identical across all systems. But Microsoft does not do this with respect to party import/export. So how did they intend this all to work?  Does anyone have any preferred method for dealing with Party ID and Batch subscriptions across thousands of trading partners on multiple systems?

       

       

    • #24594

      I found success if I subscribe to the party Name instead of party ID in the batch filter – the Party Name is static between systems. 

Viewing 1 reply thread
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.