I am running around in circles attempting to understand the EDITPAs in wM TN 6.0.1.
Can someone please explain the “splitOption”? During processing, when is its value actually checked? If I set the it to “Interchange” in the default EDITPA, does that mean only the X12 envelope will show up in the Transaction Analysis Window? Or does it govern something entirely different?
When is the value for FAReconcilation used? (e.g. when does something behind the scenes actually look at its value and do something meaningful based on that value). I changed it from “false” to “true” in the default EDITPA, and submitted a test EDI document to TN. But when I did a restorePipeline in the Flow service invoked by the Processing Rule, the FAReconciliation variable on the pipeline was still set to “false”. Is it caching the values? What am I missing?
I have more questions, but maybe if I get help with the first two, I can answer some of the others on my own. I think my main problem is that I have a fundamental misunderstanding of what TPAs (specifically for EDI) are supposed to accomplish. If anyone can provide examples of how they are using the default EDITPA and/or Partner-specific EDITPAs that would be very helpful.
Thanks in advance for any information/tips/advice you can give. I greatly appreciate it.
Thanks RMG, but unfortunately I have already gone through that particular thread.
Can you help me with either of the 2 questions above? I can provide further information if needed.
Hi Ramesh. Thank you for the reply.
Here’s what I’m seeing: When I set the splitOption in the default EDITPA to “Interchange”, TN is still breaking the document into three parts in the Transaction Analysis Window. For example, If I submit a test EDI document that has one transaction inside, TN creates three separate entries in the Transaction Analysis Window:
- X12 Envelope
- X12 Group
- X12 340 850
I would expect to only see the X12 Envelope. Any idea what I’m missing?
Here you go for Q1.
- Can someone please explain the “splitOption”? During processing, when is its value actually checked? If I set the it to “Interchange” in the default EDITPA, does that mean only the X12 envelope will show up in the Transaction Analysis Window? Or does it govern something entirely different?
—Yes,if SplitOption is set to “Interchange” then only the X12 Envelope will be persisted and shown in the TransactionAnalysis window and similarly for SplitOption set to Group only the X12Group and Trasaction then X12 4010 850(example) willbe persisted.This provision gives lot of space saving on the database side as well controlling the documents view.
Regarding the Q2,
I have seen almost the environments using FAReconciliation=false option and i have no idea if it makes any difference when it is set to true.So i will be eager to know this result too,if somebody have tested this option…
Thanks RMG. Here’s what I did to modify the default EDITPA:
- Changed the status from Agreed to Proposed
- Changed the splitOption from Transaction to Interchange
- Hit OK and set the status back to Agreed
Do I need to do anything else? The test EDI docs that I submit to TN are still being broken apart by ISA, GS, and ST. My default EDITPA looks like this:
Agreement ID: EDITPA
IS Document Type: wm.b2b.editn.TPA:EDITPA
Control Number: 0
Data Status: Modifiable
Export Service: Empty
Initialization Service: wm.b2b.editn.TPA:initService
And then the splitOption within the EDITPA document is set to “Interchange”.
In your Default TPA…is AgreementStatus= set Agreed or Proposed??
Set this option to set Agreed and test it again.
Yep, it’s set to “Agreed”…not sure what I’m missing.
Try with SplitOption=Interchange and set FAReconsiliation=false, then you can see only the X12 Envelope document.
Arrrg…nope, no change. It seems like the default EDITPA is not being referenced at all. Or, could it be that the original settings were somehow cached? I can’t understand why my modifications are not having any effect.
Thanks for the idea though, RMG. I’m open to any other suggestions…
Please make sure,If you change any of the settings in the TPA or creating a new TPA,then restart the Server.So that the changes will be effected.
This resolves the problem.
If you have a EDITPA defined for that partner that will override the default TPA.
If you don’t have one, try creating one and see what happens.
As Ramesh stated.
Your default TPA will only work for an unknown sender/receiver.
You need to create a 2 TPAs for each Partnership. One for sending and then reverse the ids to set up one for receiving.
Thanks RMG, bouncing IS did make my modifications to the default EDITPA take effect.
Chris, my understanding of the default EDITPA is that it acts like the default processing rule works. When a new EDI document is recieved, the EDI module attempts to match the document’s Sender/Receiver combination up with an EDITPA. If it finds a match, then it uses that EDITPAs settings (for splitOption, FAReconciliation, etc). If it can’t find a match, then it uses the values specified in the default EDITPA.
Maybe I’m misunderstanding you, but your last post seems to say that only transactions with “UNKNOWN” sender and receiver will use the default EDITPA.
That was my understanding as I’ve always setup the individual TPAs.
I’m getting this exact same problem, but am not able to fix it by restarting the server.
on the agreement with a specific partner as the sender, I have splitOption=Interchange and FAReconciliation=false, agreement status is ‘Agreed’.
the default (sender=Unknown) has splitOption=Transaction.
when I submit a sample EDI doc and check the transaction log in TN, it still breaks down the doc into the individual transaction (X12 4010 820) documents, even though the sender and receiver correctly show the profiles I set up. it also lists the X12 Envelope and the X12 Groups.
one thing that may have been different…
for a while, I had a processing rule that was assigned to these profiles and set to document type of X12 4010 820, because the service it invoked was coded for individual 820’s. I have since changed the code to handle/begin at envelopes, and changed the processing rule document type to X12 Envelope.
but, it still breaks down the received doc into the transactions.
any other suggestions?