Hi,

One of our partners will be sending us non-valid EDI messages. Specifically, they will be sending us 214s in which the L11/01 element is missing despite having a L11/02. The standard indicates that if L11/02 exists, then L11/01 must exists too.

I’ve looked at the .SEF file, and have gone as far as making a copy of the .SEF file, renaming the 214 set to something like “custom214”, and modifying the L11 segment as follows:

original: “L11=[127][128][352]+R0103P0102”
modified: “L11=[127][128][352]+R0103”

How would I then import the “custom214” into the WmEDIforTN.EDIFFSchema folder such that I could use it for EDI validation?

Thanks,

Ken

Hi Ken,

Could you please clarify what was changed in SEF here? Did you removed P0102 element or some thing?:

original: “L11=[127][128][352]+R0103P0102”
modified: “L11=[127][128][352]+R0103”

HTH,
RMG

Hi rmg,

Yes, I removed “P0102”, since it appears that is used to define the pairing requirement for the 1st and 2nd elements in the L11 segment. Attached is more information about this.

My desire is to import the “custom214” transaction into the WmEDIforTN.EDIFFSchema folder so that it can be used for EDI validation in instances in which the specific partner sends us a 214 with a non-valid L11.

I’m not certain how to get it into the folder alongside the other transactions. Screenshot of the folder attached.

Thanks,

Ken

Got it.

Regarding to import the EDI schemas out of SEFParse please visit this documentation described the process in the pg.403 please:

https://techcommunity.softwareag.com/ecosystem/documentation/webmethods/adapters_estandards/eStandards/EDI/EDI_9-12/9-12_Module_for_EDI_Install_and_Users_Guide.pdf

HTH.
RMG

Hi rmg,

SEFParse did the trick!

Thanks,

Ken

OK fair enough:)

HTH,
RMG

Glad to hear that!

Cheers!
RMG