Originally posted by: SystemAdmin

Can a trading manager handle 4010 & 5010 flow in parallel where in its accepting either 4010 or 5010 ( but not both at same time) & respond with a lower FA ?

In other words can a TP accept 5010 claim & respond with a 4010 835 or a 4010 FA ?

I find that since the ISA11 & ISA12 are maintained in partner profile , we can only generate 4010 or 5010 in ob flow but not both.

where as for ib flow since it depends on combination of isa5,6,7,8,gs2,3 , its possible to process both 4010 or 5010 ...
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: LilyS

Let me give a brief summary of what happens in TM

1.- Inbound data:
You have an external partner sending data to an internal partner. The ISA information does not get validated or used at that time.
If you select to create an acknowledgement for that data, the acknowledgement (either a 997 or 999) will get created using the following possiblities for the ISA segment
a) either 00401 or
b) whatever value the input data file has (which is useful in case it is a 00501 data file).
This is currently being defined as a parameter in output card 8 of the export map (in future will be included in the Partner manager GUI).

For acknowledgements, even if the tradelink is partially enveloped, the ISA does not get changed to whatever is defined in the external partner. In case of fully enveloped tradelink for the acknowledgement, nothing else happens. For a partially enveloped acknowledgement, the delimiters anc control number are changed.
2) For outbound data other than acknowledgements, if the data is partially enveloped, the ISA value defined in the external partner is used for the resulting outbound file, and also the control number is increased and delimiters changed. For fully enveloped, the outbound file should look identical as the original.

With this in mind you can have the following scenarios:

1) An inbound 5010 data file that produces either a 5010 or 4010 ISA based on the flag set up in the export map, regardless of the ISa value of the ISA in the external partner setting in partner manager

2) A 5010 or 4010 outbound file that gets reenveloped with a 4010 ISA if the external partner has that in the settings and the tradelink is partially enveloped, or a 5010 or 4010 outbound file that gets reenveloped with a 5010 ISA if the external partner has that in the settings and the tradelink is partially enveloped

what you cannot have is an outbound 5010 file going to the same external partner with a 4010 ISA one time or a 5010 another time.

In regards to the question:
In other words can a TP accept 5010 claim & respond with a 4010 835 or a 4010 FA ?

I'm assuming accept 5010 claim means an inbound file. in this case, trading manager will only create and send outboud an FA and the isa on that FA will depend on the setting in the export flag (so it can be either a 5010 or 4010, but always the same). Trading Manager does not generate 4010 835, so these might need to be created by an external application and then send back as outbound data to trading manager. The external application could decide what to put in the ISA, but ultimately, whatever value the external parner has in trading manager, will override that if the tradelink is set to Partially enveloped.

Hope this helps.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Thanks for your elaborate response. Things getting more clear now.
To explain our particular scenario in detail

we currently have external application "Instream" validating IB claims & passing them to TMGR.
We do not perform any HIPAA validations in tmgr & just route the ib file to the appropriate put PO for further processing.

Reg ob 835 & FA's , even those are getting generated from instream & TMGR just routes them to appropriate put PO.

The current TLink set up that we have is configured for partial enveloping which means though ack's are generated by
external application (instream) , Tmgr still controls the envelope ie ISA11,12 & separators.

Now what i learnt addtionally from your response is (assuming we have 00500 configured in partner set up)
using a "Y" for field "ISAVersion_FA_ack Field" in export map , we could still override values for isa11&12 set up in partner configuration & generate a FA with 00401. So this flag is useful when
i)we are using tmgr for generating FA & ii)this flag would be override for all partners and not selectively for specific partners.

I tried the control number enveloped option & find that
i)tmgr still leaves the envelope info from "instream" as is (which is good cause we dont have to worry bout isa12)
ii) changes the control numbers (which again is the requirement that we control the control nos in tmgr)
iii)& also applied separators to rest of the message but not uniformly.( which is not required as we have a message with a combination of “{“ and “*” element separators which corrupts the entire message with two separators)

ISA*00* 00 *30*990040115 *ZZ*TESTP *100901*1152*^*00501*000007052*0*T*:~
GS*FA*CLM*ACC*20100901*115242*70520001*X*005010~
ST*997*0001~
AK1{HC{10961
AK2{837{000000001
AK5{A
AK9{A{1{1{1
SE*6*0001~
GE*1*70520001~
IEA*1*000007052~

Now is there a possibility (in accordance with my current Tlink setup explained above) where in external application still generates
the FA & tmgr with partial enveloping just controls the
i) separators configured for each TP under ISA options
ii)control numbers. (ie it generates the control numbers at ISA,GS & ST level)
iii) leaves isa 12 as is from instream.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

After making changes to couple of flags in the export map , in an partial envelope structure , we can still control the separators & control #'s in Tmgr , leaving the ISA HDR info "as is" from the external application.

ISAVersion_FA_ack Field
Replace_Version_No Field

We tested this & found to be working. But just need to confirm with IBM if this is recommended.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange