Does anyone know how to set Biztalk to use control numbers by document types? we have customers that want all their documents to be in sequence, but Biztalk is assigning the next available to what ever is being sent.

204  #1

997  #2

997 #3

204 #4

Yes, but...

Some clarification is needed.

1. Do you mean all 204's should be in the same sequence, 1, 2, 3, 4...235...
2. And all 997's should be in their own sequence, 1, 2, 3, 4...235...
3. And these are both send using the same Sender and Receiver Identifiers, ISA05-ISA08?

If the answer to all three is yes, then it's the other side that is non standard and non-X12 compliant.

So, the first thing you have to do is inform you management that the Trading Partner is non-standard and you have to spend extra time accommodating their request.

Now, how to actually do it.

The easiest way would be to create separate Agreements for each document type.  The problem you will have is an Agreement is uniquely identified by ISA05-ISA08.

The most practical way around that is to use a different Qualifier, Receiver would be best, to differentiate the Agreements, then use a custom Pipeline Component or Orchestration to set the EDIOverride value to the correct one.

Yes, but...

Some clarification is needed.

1. Do you mean all 204's should be in the same sequence, 1, 2, 3, 4...235...
2. And all 997's should be in their own sequence, 1, 2, 3, 4...235...
3. And these are both send using the same Sender and Receiver Identifiers, ISA05-ISA08?

If the answer to all three is yes, then it's the other side that is non standard and non-X12 compliant.

So, the first thing you have to do is inform you management that the Trading Partner is non-standard and you have to spend extra time accommodating their request.

Now, how to actually do it.

The easiest way would be to create separate Agreements for each document type.  The problem you will have is an Agreement is uniquely identified by ISA05-ISA08.

The most practical way around that is to use a different Qualifier, Receiver would be best, to differentiate the Agreements, then use a custom Pipeline Component or Orchestration to set the EDIOverride value to the correct one.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator 5 hours 29 minutes ago

Yes, but...

Some clarification is needed.

1. Do you mean all 204's should be in the same sequence, 1, 2, 3, 4...235...
2. And all 997's should be in their own sequence, 1, 2, 3, 4...235...
3. And these are both send using the same Sender and Receiver Identifiers, ISA05-ISA08?

If the answer to all three is yes, then it's the other side that is non standard and non-X12 compliant.

So, the first thing you have to do is inform you management that the Trading Partner is non-standard and you have to spend extra time accommodating their request.

Now, how to actually do it.

The easiest way would be to create separate Agreements for each document type.  The problem you will have is an Agreement is uniquely identified by ISA05-ISA08.

The most practical way around that is to use a different Qualifier, Receiver would be best, to differentiate the Agreements, then use a custom Pipeline Component or Orchestration to set the EDIOverride value to the correct one.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Monday, August 31, 2015 1:36 AM

Hi Mike,

Seems you are using same agreement for both document type 204 and 997. If yes then you need to create separate agreement for both document types to achieve your requirement. Then each agreement will create sequential document for every document type.

You have to do one more configuration in agreement, please select radio button Support Transaction Sets from the List from Transaction set List, and then select your document type from drop down. your configuration should be look like,

Hi ,

Practically It cannot be done because 

Biztalk Server Allow only one configuration windows for all document type for define range of controls numbers so every document type which its defined in Agreement using same control number in single agreement. 

It can be achieved by if you can create different agreement but its require different values of ISA05-ISA08 as told by Johns.