3 Replies Latest reply: Jul 9, 2014 8:42 PM by Siddhardha M RSS

    4010_850 EDI file Generation issue.

    Siddhardha M

      Hi All,

       

      We are facing issue in converting 850 EDI XML to EDI file.

      We could generate a simple EDI based on mandatory elements. But when we try to provide DTM and AMT values , We are hitting below issues..


      I am missing some basic stuff. Please find the EDI XML i am trying to convert to EDI file.


      <?xml version = '1.0' encoding = 'UTF-8'?><Transaction-850 xmlns:ns1="urn:oracle:b2b:X12/V4010/850" Standard="X12" xmlns="urn:oracle:b2b:X12/V4010/850">
      <ns1:Segment-ST>
      <ns1:Element-143>850</ns1:Element-143>
      <ns1:Element-329>000000010</ns1:Element-329>
      </ns1:Segment-ST>
      <ns1:Segment-BEG>
      <ns1:Element-353>00</ns1:Element-353>
      <ns1:Element-92>NE</ns1:Element-92>
      <ns1:Element-324>12345678</ns1:Element-324>
      <ns1:Element-373>20140703</ns1:Element-373>
      </ns1:Segment-BEG>
      <ns1:Loop-PO1>
      <ns1:Segment-PO1>
      <ns1:Element-350>001</ns1:Element-350>
      <ns1:Element-330>1</ns1:Element-330>
      <ns1:Element-212>96</ns1:Element-212>
      <ns1:Element-639>AA</ns1:Element-639>
      <ns1:Element-235_1>VC</ns1:Element-235_1>
      <ns1:Element-234_1>571157</ns1:Element-234_1>
      <ns1:Element-235_2>CB</ns1:Element-235_2>
      <ns1:Element-234_2>00100</ns1:Element-234_2>
      </ns1:Segment-PO1>
      <ns1:Loop-PID>
      <ns1:Segment-PID>
      <ns1:Element-349>F</ns1:Element-349>
      <ns1:Element-352>Rockford product</ns1:Element-352>
      </ns1:Segment-PID>
      </ns1:Loop-PID>
      <ns1:Segment-DTM>
      <ns1:Element-374>038</ns1:Element-374>
      <ns1:Element-373>20140626</ns1:Element-373>
      </ns1:Segment-DTM>
      <ns1:Loop-AMT>
      <ns1:Segment-AMT>
      <ns1:Element-522>1</ns1:Element-522>
      <ns1:Element-782>1</ns1:Element-782>
      </ns1:Segment-AMT></ns1:Loop-AMT>
      </ns1:Loop-PO1>
      <ns1:Segment-SE>
      <ns1:Element-96>#SegmentCount#</ns1:Element-96>
      <ns1:Element-329>000000010</ns1:Element-329>
      </ns1:Segment-SE>
      </Transaction-850>

      Only DTM passed :

      =============

       

      Error :

      Extra Element was found in the data file as part of Segment DTM. Segment DTM is defined in the guideline at position 210.{br}{br}This error was detected at:{br}{tab}Segment Count: 5{br}{tab}Element Count: 1{br}{tab}Characters: 1014 through 1017

      Extra Element was found in the data file as part of Segment DTM. Segment DTM is defined in the guideline at position 210.{br}{br}This error was detected at:{br}{tab}Segment Count: 5{br}{tab}Element Count: 2{br}{tab}Characters: 1052 through 1060

      Element DTM01 (Date/Time Qualifier) is missing. This Element's standard option is 'Mandatory'. Segment DTM is defined in the guideline at position 210.{br}{br}This Element was expected in:{br}{tab}Segment Count: 5{br}{tab}Element Count: 1{br}{tab}Character: 1078

       

       

      DTM + AMT Passed :

      ===============

       

      Error : Extra Element was found in the data file as part of Segment DTM. Segment DTM is defined in the guideline at position 210.{br}{br}This error was detected at:{br}{tab}Segment Count: 5{br}{tab}Element Count: 1{br}{tab}Characters: 1014 through 1022 Extra Element was found in the data file as part of Segment DTM. Segment DTM is defined in the guideline at position 210.{br}{br}This error was detected at:{br}{tab}Segment Count: 5{br}{tab}Element Count: 2{br}{tab}Characters: 1057 through 1060 Element DTM01 (Date/Time Qualifier) is missing. This Element's standard option is 'Mandatory'. Segment DTM is defined in the guideline at position 210.{br}{br}This Element was expected in:{br}{tab}Segment Count: 5{br}{tab}Element Count: 1{br}{tab}Character: 1078 Unrecognized data was found in the data file as part of Loop PO1. The last known Segment was DTM at guideline position 210.{br}{br}This error was detected at:{br}{tab}Segment Count: 6{br}{tab}Characters: 1278 through 1286 Unrecognized data was found in the data file as part of Loop PO1. The last known Segment was DTM at guideline position 210.{br}{br}This error was detected at:{br}{tab}Segment Count: 7{br}{tab}Characters: 1295 through 1367



      Thanks in advance,
      Siddhardha

      Manager , Deloitte Consutling.

        • 1. Re: 4010_850 EDI file Generation issue.
          Prasanna Chandrashekhara

          Sidh,

          please validate it using  Document editor, if you have native payload. Or validate xml using XSD

          • 2. Re: 4010_850 EDI file Generation issue.
            917657

            Can you please write down the steps to perform it?

            • 3. Re: 4010_850 EDI file Generation issue.
              Siddhardha M

              Issue is solved with the files provided by oracle support. They used Document editor version

              Oracle Document Editor -> 7.0.5.4018 & X12 - 8.0.0.186

               

              Not sure what is wrong with our files.

              We used document editor 7.0.5.4043  & X12 - 8.0.0.186

               

              Below is the update i put in SR.

              ==================================

              My xsd contains below text.

               

              <xsd:appinfo>

              <UNMKey>Full|CodeList|-<Parent Node ID>.<Index>|Composite|-<Node ID>|Element|-<Node ID>|Loop|-<Node ID>|Segment|-<Node ID>|Transaction|-<Node ID>|ReplacementCharacter|_|InternalSeparator|-</UNMKey>

              </xsd:appinfo>

               

              ===================

               

              The file you provided have the below.

               

              <xsd:appinfo>

              <UNMKey>Full|Default|-<Node ID>|CodeList|-<Parent Node ID>.<Index>|ReplacementCharacter|_|InternalSeparator|-

              </UNMKey>

              </xsd:appinfo>

               

              Not sure if that is really causing the issue.

              ==========================================

               

              If anyone is interested here is the SR number (#3-9312618901)

               

              Thanks,

              Sid