1 Reply Latest reply: Sep 5, 2014 3:45 AM by user10777358 RSS

    Transformation issue with EDI 841 xsd generated by document editor

    user10777358

      Hi,

       

      I was trying to create a B2B Outbound interface with Doc Standard as EDI X12. When our custom payload for item is being mapped to the xsd of doc type 841 (generated using standard ecs with Oracle Doc Editor), the xengine is behaving a little weird. It's generating a file in the output directory for sure, but it's not having all the data I mapped. For Example, I wanted to have a datafile as below:

       

      ST~841~000000001

      SPI~00~~~~~~04~MF

      AMT~LI~0

      HL~1~~I~0

      SPI~ZZ

      LIN~~PN~ABC

      MSG~ABC

      PID~F~~~~ABC

      REF~ZZ~BaseUOMCode~EA~ZZ>EACH

      SE~38~000000001

       

      For which I mapped in xslt quite a few elements and corresponding payload that is coming in the console application message is as below:

       

      <?xml version = '1.0' encoding = 'UTF-8'?>

      <Transaction-841 xmlns:ns10="urn:oracle:b2b:X12/V4010/841" Standard="X12"

                       xmlns="urn:oracle:b2b:X12/V4010/841">

        <ns10:Segment-ISA>

          <ns10:Element-I12/>

        </ns10:Segment-ISA>

        <ns10:Segment-GS>

          <ns10:Element-28/>

        </ns10:Segment-GS>

        <ns10:Segment-ST>

          <ns10:Element-143>841</ns10:Element-143>

          <ns10:Element-329>1</ns10:Element-329>

        </ns10:Segment-ST>

        <ns10:Loop-HL>

          <ns10:Segment-HL>

            <ns10:Element-628>1</ns10:Element-628>

            <ns10:Element-735>I</ns10:Element-735>

            <ns10:Element-736>0</ns10:Element-736>

          </ns10:Segment-HL>

          <ns10:Loop-SPI>

            <ns10:Segment-SPI>

              <ns10:Element-786>ZZ</ns10:Element-786>

            </ns10:Segment-SPI>

            <ns10:Segment-LIN>

              <ns10:Element-235>PN</ns10:Element-235>

              <ns10:Element-234>ABC</ns10:Element-234>

            </ns10:Segment-LIN>

            <ns10:Segment-MSG>

              <ns10:Element-933>ABC</ns10:Element-933>

            </ns10:Segment-MSG>

          </ns10:Loop-SPI>

          <ns10:Loop-PID>

            <ns10:Segment-PID>

              <ns10:Element-349>F</ns10:Element-349>

              <ns10:Element-352>ABC</ns10:Element-352>

            </ns10:Segment-PID>

          </ns10:Loop-PID>

          <ns10:Loop-REF>

            <ns10:Segment-REF>

              <ns10:Element-128>ZZ</ns10:Element-128>

              <ns10:Element-127>BaseUOMCode</ns10:Element-127>

              <ns10:Element-352>Ea</ns10:Element-352>

              <ns10:Composite-C040>

                <ns10:Element-128>ZZ</ns10:Element-128>

                <ns10:Element-127>Each</ns10:Element-127>

              </ns10:Composite-C040>

            </ns10:Segment-REF>

          </ns10:Loop-REF>

        </ns10:Loop-HL>

        <ns10:Segment-SE>

          <ns10:Element-96>38</ns10:Element-96>

          <ns10:Element-329>1</ns10:Element-329>

        </ns10:Segment-SE>

        <ns10:Segment-GE>

          <ns10:Element-28/>

        </ns10:Segment-GE>

        <ns10:Segment-IEA>

          <ns10:Element-I12/>

        </ns10:Segment-IEA>

      </Transaction-841>

       

      However when the file is getting generated, the content misses the LIN Segment and below REF segment. It comes as below:

       

      ISA~00~          ~00~          ~ZZ~079763140      ~ZZ~V1             ~140901~1118~U~00401~100000012~1~T~>

      GS~GS~079763140~V1~20140901~1118~1012~X~004010

      ST~841~000000001

      SPI~00~~~~~~04~MF

      AMT~LI~0

      HL~1~~I~0

      SE~38~000000001

      GE~1~1012

      IEA~1~100000012

       

       

      Below are missing:

      SPI~ZZ

      LIN~~PN~ABC

      MSG~ABC

      PID~F~~~~ABC

      REF~ZZ~BaseUOMCode~EA~ZZ>EACH

       

      We are on 11G. What could go wrong here? Any help is appreciated.

       

      Regards,

      Subhadeep