Extracting the delimiters from the edi

, ,
21

Rob,

I got them using the editn_grp Document type which is there in the pipeline.
Thx for your suggestions

Have a good day

ramesh

22

ramesh,
So you are processing at the group envelope level (GS)? You probably need to process at the actual transaction level if you want your bizdoc to recognize the transaction level information. What is in the TypeName? If it is not the actual transaction 850, 810, etc… then this service will now know what Schema to use.
Thanks,
Dawn

23

Hi Guys,

Actually i’m processing at the Group level.may be that is the reason i was getting this error.our specification says to process at Group level.
As RMG says,i’m routing the document through the TN.
i got the solution using the EDITNGROUP Document type.

Thanks for your valuable suggestions…

ramesh

24

Ramesh,

Yes editn_grp,editn_env,editn_txn variables will be in the pipeline depends on the processing level (Group or Enveloper or transactionset)…once they are routed to a service.

Glad you made resolved.

HTH,

25

I wonder why the specification says to process at the group level? What is driving that desire? I assume that you’re doing some additional work to pull out each transaction set from the group and then translating each–additional code to write when EDI for TN will already do all that deenveloping for you.