This discussion is archived
5 Replies Latest reply: Feb 27, 2013 12:48 AM by 991984 RSS

B2B-51507 : XEngine error - Invalid data node name.

991984 Newbie
Currently Being Moderated
Hi All,

I am working on Creating outbound 850 transaction .I have created SOA process in which i created File adapter on the service lane to pick up the file from Oracle B2B
and B2B adapter on the reference section for sending. In the middle i have used mediator for translation .
In the B2Bconsole i followed the steps like :
1.created the host and remote trading partners
2.created the document definition in b2b console ,with default 850.ecs and 850.xsd using document editor
3.created the profile information .
4.created the channel and agreement.
5.Finally saved,validated and deployed the Agreement.

After deploying application in my dev ,file was picked up and an instance was also created .Here i am getting an error message in B2B reports
application message as :

App Message property     {fabric.enterpriseId=-1, b2b.documentProtocolVersion=V4010,
                                              b2b.messageId=2d313333383938393131363932333830, b2b.documentDefinitionName=850_def, MESH_METRICS=null, b2b.messageType=1,
                                             tracking.parentReferenceId=mediator:5012A2E07B8D11E2BFF86593BFBAE2CE:5153D5707B8D11E2BFF86593BFBAE2CE:oneway, tracking.compositeInstanceId=61685,
                                             tracking.ecid=11d1def534ea1be0:2dfe216a:13cca8c98cc:-8000-00000000001bee04, b2b.toTradingPartnerId=Acme, b2b.fromTradingPartnerId=GlobalChips,
                                             tracking.compositeInstanceCreatedTime=Thu Feb 21 00:12:39 IST 2013, tracking.conversationId=enh1LJKC2l6Rlx0MFEnkh30dDaD7j39T3U_AeK-Nmv8., t
                                              racking.parentComponentInstanceId=mediator:5012A2E07B8D11E2BFF86593BFBAE2CE, b2b.documentTypeName=850}
Direction     OUTBOUND
State     MSG_ERROR
Error Code     B2B-51507
Error Text     Error Brief : XEngine error - Invalid data node name.
Error Description     Error : The XData level name found does not match the level name in the XData schema.

Business Message :

Error Code     B2B-51507
Error Description     : Description: Payload validation error.
Error Level     ERROR_LEVEL_COLLABORATION
Error Severity     ERROR
Error Text     Error Brief : XEngine error - Invalid data node name.

Here i verified the Xdataversion in xsd and also in the input payload xml which i sent .Both are with same version number.
Could anyone please help me out as i am new to b2b. Also please tell me how the message flow goes for inbound and also for outbound.


Thanks
keerthi
  • 1. Re: B2B-51507 : XEngine error - Invalid data node name.
    Anuj Dwivedi Guru
    Currently Being Moderated
    b2b.documentProtocolVersion=V4010
    It should be only 4010 (without V) and in B2B also, version should be configured as 4010
    The XData level name found does not match the level name in the XData schema.
    Generate a sample XML from the ecs which you are using in B2B doc def and match it's first line with your XML. It should be something like -

    <Transaction-850 xmlns="urn:oracle:integration:b2b:X12/4010/850" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="1.0" Standard="X12" Version="V4010" CreatedDate="2007-04-10T17:16:24" CreatedBy="ECXEngine_837" GUID="{12345678-1234-1234-1234-123456789012}">

    Values of XDataVersion, Standard and Version should be as specified above. The root node of XML must be Transaction-850

    Regards,
    Anuj
  • 2. Re: B2B-51507 : XEngine error - Invalid data node name.
    991984 Newbie
    Currently Being Moderated
    Anuj,

    I changed the b2b.documentProtocolVersion=V4010 to 4010 .Now i got MSG_COMPLETE status in Application Message. But i got
    msg_wait_ack status in Business message,Wire message as in PROCESSING state.

    msg_error with no document type name :
    Error Code     B2B-50081
    Error Description     Description: Duplicated exchange protocol message error - Original B2BMessageId = 34353634343836363137323833333936
    Error Level     ERROR_LEVEL_COLLABORATION
    Error Severity     ERROR
    Error Text     Duplicated exchange protocol message error


    Please help me out on this.

    Thanks
    keerthi

    Edited by: 988981 on Feb 25, 2013 4:50 AM
  • 3. Re: B2B-51507 : XEngine error - Invalid data node name.
    Anuj Dwivedi Guru
    Currently Being Moderated
    Keerthi,

    Please make sure to enqueue message with unique message id every time i.e. header b2b.messageId should have unique id for each and every outbound message.

    Regards,
    Anuj
  • 4. Re: B2B-51507 : XEngine error - Invalid data node name.
    Nitesh Jain Pro
    Currently Being Moderated
    This Happens because of same message is coming again. Change the control number in the message and resend

    Rgds,
    Nitesh
  • 5. Re: B2B-51507 : XEngine error - Invalid data node name.
    991984 Newbie
    Currently Being Moderated
    Anuj,


    expression : oraext:generate-guid()     property : b2b.messageId .i am using this before invoking b2b adapter.



    Thanks
    keerthi

Legend

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