none
splitting in orchestration RRS feed

  • Question

  • I have to check each claims billing NPI as it comes through the orchestration to determine what to route the claim.

    I have all the xslt in place to pull out and check the values and route them but it appears to only checks once per st/se.

    Is there a way I can get it to split per claim at the orchestration level?

    Thanks

    Friday, June 26, 2009 6:25 PM

Answers

  • You can use the promoted context properties to route your claim. Follow below steps:

    - Configure a party
    - set incoming document processing option to "Split Interchange - suspend transaction sets". It will split the incoming document per ST/SE
    - subscribe/route EDI documents based on promoted context properties.


    Bhola Meena [http://blogs.msdn.com/biztalkb2b]
    Monday, June 29, 2009 5:12 PM
  • You can implement this in couple of ways. Its up to you to follow :)

    1) Can follow the logic Bhola has mentioned. Configure a party and use "Split Interchange - suspend transaction sets". It will split the multiple Transaction Sets.
    2) If you are receiving EDI message with Envelope also, and want to split the multiple transaction set, then you can follow this http://social.msdn.microsoft.com/Forums/en-US/biztalkediandas2/thread/8e862469-fa00-41ee-b59e-13af6c1f794b .
    3) If you are receiving EDI message with Envelope also, and want to split the multiple transaction set inside Orchestration then you can use xpath to separate each ST/SE segment.

    I would follow the first option as its the best practice and you can make use of additional features of EDI with this approach.

    Ajeet Kumar
    Tuesday, June 30, 2009 5:10 AM

All replies

  • You can use the promoted context properties to route your claim. Follow below steps:

    - Configure a party
    - set incoming document processing option to "Split Interchange - suspend transaction sets". It will split the incoming document per ST/SE
    - subscribe/route EDI documents based on promoted context properties.


    Bhola Meena [http://blogs.msdn.com/biztalkb2b]
    Monday, June 29, 2009 5:12 PM
  • You can implement this in couple of ways. Its up to you to follow :)

    1) Can follow the logic Bhola has mentioned. Configure a party and use "Split Interchange - suspend transaction sets". It will split the multiple Transaction Sets.
    2) If you are receiving EDI message with Envelope also, and want to split the multiple transaction set, then you can follow this http://social.msdn.microsoft.com/Forums/en-US/biztalkediandas2/thread/8e862469-fa00-41ee-b59e-13af6c1f794b .
    3) If you are receiving EDI message with Envelope also, and want to split the multiple transaction set inside Orchestration then you can use xpath to separate each ST/SE segment.

    I would follow the first option as its the best practice and you can make use of additional features of EDI with this approach.

    Ajeet Kumar
    Tuesday, June 30, 2009 5:10 AM
  • Thanks for the responses!

    I am already splitting per transaction I need to split per claim.  I do not see a way to do it this way. Am I missing something?
    Tuesday, July 7, 2009 7:44 PM
  • You mean you can have multiple claims within one ST/SE segment. If this is the case then you have multiple option to do this.

    1) Can use xpath to separate each Claim inside Orchestration. Here is good article for this http://blogs.objectsharp.com/cs/blogs/matt/archive/2005/04/12/1703.aspx .

    2) You can create custom pipeline and call inside Orchestration and separate out the claim messages. http://www.biztalkgurus.com/media/p/15564.aspx (copy and paste in browser) .

    Also check this article for performance comparison of different approach. http://geekswithblogs.net/sthomas/archive/2004/12/12/17373.aspx

    Let us know if it helps.
    Ajeet Kumar
    Wednesday, July 8, 2009 6:07 AM
  • Thanks for the articles! They helped give me some ideas. I rearranged my orchestration and I am calling the map first that has the mutiple 837 schema. The map separates each claim out into its own file. I then run my xslt to drill down to pull the npis and check them against look up tables to see if where they should get routed. This should work however it appears to still be checking only one value. Do I need to put a loop in there after I map to multiple files and inside the loop check my conditions? If so what do I need to put in the expression of the loop to tell it just to loop through all the messages.

    Thanks for the continued help!

    Wednesday, July 8, 2009 1:29 PM
  • As I understand your scenario, you get to break the input message into multiple claim messages using map and then Orchestraion (might have used xpath or receive pipeline). Now as you have to determine the send location based on some field (in the claim message), you can achieve this following below steps:

    1) Get the claim message count, let say its varClaimCount.
    2) Take a loop shape (inside Orchestration) and a counter, loop till the counter reaches varClaimCount
    3) Inside the loop use xpath to get the field value, can check this link for details http://geekswithblogs.net/sthomas/archive/2004/10/25/13269.aspx and have a lookup to get the location and then send.

    As you have xslt to pull out the field value from the message, so instead of using xpath a above you can use indexing in your xslt. This should resolve the problem.

     The basic idea is you should loop through each claim message and using index to get the value (and have the routing lookup). Its upto you which way you use xpath or xslt. I am Orchestration Guy so I would do it in Orch :)

    Let me know if it helps.
    Ajeet Kumar
    Thursday, July 9, 2009 5:41 AM