This discussion is archived
4 Replies Latest reply: Nov 28, 2012 4:59 AM by Anuj Dwivedi RSS

EDI X12 Version 4060 setup issue in Oracle B2B 10g

975880 Newbie
Currently Being Moderated
Hi All,
We are currently encountering some issues in doing Inbound Trading Partner Set-ups to accept Inbound 210 Documents using EDI X12 Version 4060.

We created an ecs file(only from ST to SE) excluding envelop, doing all the reqd set up in B2B ,keeping "use Default Document definition" box checked (for 210), deploying agreement and all ; we are getting below error:

+Element ISA12 is a coded list element. Code '00406' is not allowed. Segment ISA is defined in the guideline at position 010.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Position: 12{br}{tab}Characters: 84 through 89+

any help regarding this welcomed.

Regards,
Ravi
  • 1. Re: EDI X12 Version 4060 setup issue in Oracle B2B 10g
    Anuj Dwivedi Guru
    Currently Being Moderated
    Hi Ravi,

    Are you working with 10g? ISA12 element is validated on the basis of it's codelist and ideally the codelist should have value 00406 in it. In any case, you may use your own group and interchange ecs to have specific values in the code list as per your requirement.

    Regards,
    Anuj
  • 2. Re: EDI X12 Version 4060 setup issue in Oracle B2B 10g
    user12187495 Newbie
    Currently Being Moderated
    Hi Anuj,

    Yes this problem is coming in 10.1.2 b2b version..steps we have done are mentioned below :

    1. create a new business action -->created a new dcoument protocol with revision 4060

    Now we define the document protocol parameters (here we mentioned ISA & GS qualifier
    & values for the host trading partner) & we leave the interchange ecs file & group ecs file values blank here.

    here we leave these parameter values : Interchange Control Version Number & Version/Release/Industry Identifier Code as Null or blank.


    Next we define Document Type: 210 with revision as 4060 & then attach a new document definition with this
    (here we specify the transaction set ecs & xsd files ( this just has the ST-SE transaction set meaning the ecs
    doesn't have the ISA & GS envelopes here in it( while creating ecs in spec builder we are not Inserting the envelopes in it))


    2. TP definition/setup :

    Here we define the trading partner -- here we define a new operational capability -- here we select the
    business action created in step1.

    Now here we uncheck the option (Use defualt Document Protocol Paramters and mention the interchange & group qualifier & values for this trading partner.

    here we mention Interchange Control Version Number : 00406
    Version/Release/Industry Identifier Code : 004060

    Here also we don't mention anything for interchange ecs file & group ecs file values, we leave these blank/null.
    Also we leave the checkbox for : Use Default document definition as Yes.

    **************

    Now could you please review & advise what exactly needs to be done.

    regards
  • 3. Re: EDI X12 Version 4060 setup issue in Oracle B2B 10g
    user12187495 Newbie
    Currently Being Moderated
    Just to add with similar setups the document protocols with revision 4010 , 4030 etc are working fine, but now we are facing issue with 4060 version saying ISA12 value 00406 is not there in coded list.

    Our understanding was that it should validate what comes in the inbound data file against the values present for the
    doucment protocol parameters :Interchange Control Version Number & Version/Release/Industry Identifier Code (which have been provided correctly ) present in the trading partner setup.

    Could you please advise how we could resolve this...
  • 4. Re: EDI X12 Version 4060 setup issue in Oracle B2B 10g
    Anuj Dwivedi Guru
    Currently Being Moderated
    Hi Ravi,
    Here also we don't mention anything for interchange ecs file & group ecs file values, we leave these blank/null.
    Please create your own interchange and group ecs and use it in the document configuration. Purge the existing agreement and then redeploy the agreement and run a test.

    Regards,
    Anuj

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points