Topic
  • 8 replies
  • Latest Post - ‏2014-05-19T15:34:20Z by MichaelGlenn
vanravi
vanravi
47 Posts

Pinned topic Edi envelope

‏2008-11-10T20:54:47Z |
Hi,

I am trying to convert a xml document to edi and sent it outbound to partner. The xml document gets converted into edi document.But N/A-Edifact-UNB->None-Edifact-UNB(enveloping) does not take place.
In the first part of conversion from None-custprot-xmldoc -> N/A-EDI97A-doc,

following are the messages:

Channel lookup successful
Current Map Name
Document Rejected
(document gets converted from xml to edi and edi file is viewable in document viewer)

No apparent reason is given for the rejected edi document.(but the converted edi document can be viewed in document viewer).

The second part of transformation(enveloping) does not take place at all.

I have configured the envelope profile and attached it to relevant places. Not sure what causes this error(as no reason provided for document rejection).
Any help is greatly appreciated.
Thanks.
Updated on 2012-11-20T10:54:21Z at 2012-11-20T10:54:21Z by SystemAdmin
  • vanravi
    vanravi
    47 Posts

    Re: Edi envelope

    ‏2008-11-11T20:18:26Z  
    0000030c E UOW=null source=com.ibm.bcg.edi.server.EDITransactionHandler class=com.ibm.bcg.edi.server.EDITransactionHandler method=process org=IBM prod=BCG component=EDIEnveloper thread=Default : 29
    Error while trying queue the transaction

    0000030c R UOW= source=SystemErr org=IBM prod=WebSphere component=Application Server thread=Default : 29
    Error occured while adding the edi transaction to the CF_ENVELOPEQ DB2 SQL error: SQLCODE: -727, SQLSTATE: 56098, SQLERRMC: 5;-204;42704;SESSION.CF_ENVELOPEQ_TEMP

    is the log message for the above error.Could anybody help solve this?

    Enveloper is in default settings.
  • SystemAdmin
    SystemAdmin
    527 Posts

    Re: Edi envelope

    ‏2008-11-12T07:10:16Z  
    • vanravi
    • ‏2008-11-11T20:18:26Z
    0000030c E UOW=null source=com.ibm.bcg.edi.server.EDITransactionHandler class=com.ibm.bcg.edi.server.EDITransactionHandler method=process org=IBM prod=BCG component=EDIEnveloper thread=Default : 29
    Error while trying queue the transaction

    0000030c R UOW= source=SystemErr org=IBM prod=WebSphere component=Application Server thread=Default : 29
    Error occured while adding the edi transaction to the CF_ENVELOPEQ DB2 SQL error: SQLCODE: -727, SQLSTATE: 56098, SQLERRMC: 5;-204;42704;SESSION.CF_ENVELOPEQ_TEMP

    is the log message for the above error.Could anybody help solve this?

    Enveloper is in default settings.
    Hi,

    Could you please tell me, which version of Database and WPG you are using.
  • vanravi
    vanravi
    47 Posts

    Re: Edi envelope

    ‏2008-11-12T13:38:40Z  
    Hi,

    Could you please tell me, which version of Database and WPG you are using.
    WPG - 6.1 and DB2 9.1(DB2 version I am not very sure of).
  • SystemAdmin
    SystemAdmin
    527 Posts

    Re: Edi envelope

    ‏2008-11-14T09:40:13Z  
    • vanravi
    • ‏2008-11-12T13:38:40Z
    WPG - 6.1 and DB2 9.1(DB2 version I am not very sure of).
    Hi,

    It is seems to be a defect. Please open a PMR for this.

    Thanks!
  • vanravi
    vanravi
    47 Posts

    Re: Edi envelope

    ‏2008-11-14T13:36:43Z  
    Hi,

    It is seems to be a defect. Please open a PMR for this.

    Thanks!
    Thank you very much for the reply.
  • SystemAdmin
    SystemAdmin
    527 Posts

    Re: Edi envelope

    ‏2012-11-20T10:49:17Z  
    Not sure if the problem still persists. But we've managed to get this working using a configuration like this for a APERAK XML message to APERAK EDI with envelope:

    In transformation map set property IchgSndrId and IchgRcvrId i.e.:
    SetProperty ("IchgSndrId", \tns:Envelope\tns:Body\apenot:AperakNotificationRequest\apenot:Edifact\aperak:UNB\aperak:UNB02\aperak:UNB0201\aperak:UNB0201.data\\)
    SetProperty ("IchgRcvrId", \tns:Envelope\tns:Body\apenot:AperakNotificationRequest\apenot:Edifact\aperak:UNB\aperak:UNB03\aperak:UNB0301\aperak:UNB0301.data\\)

    Create a new XML format:
    Hub Admin - Hub Configuration - XML Formats
    Click Create Document Family

    Family name : APERAK
    Protocol : XML
    Large file option : None
    Family type : Root Tag
    Family identifier : Envelope

    Click Save
    Click Create XML format

    Family name : APERAK
    Protocol : XML
    Document type : ENVELOPE (ALL)
    Family type : Root Tag
    Family identifier : Envelope
    Name: Format identifier
    Value: Envelope
    XPath expression: Envelope
    Return type: Constant
    Name: Format version
    Value: ALL
    XPath expression: ALL
    Return type: Constant
    Attribute name: Source business identifier
    XPath expression: //*/*/*
    Return type: Text
    Attribute name: Target business identifier
    XPath expression: //*/*/*
    Return type: Text
    Account Admin - Profiles - Partner

    internal partner
    B2B capabilities
    Account Admin - Profiles - B2B capabilities
    Source
    Package: None
    Protocol: XML
    Document Type: ENVELOPE
    Account Admin - Profiles - Partner

    external partner
    B2B capabilities
    Account Admin - Profiles - B2B capabilities
    Target
    Package: N/A
    Protocol: EDI03A
    Document Type: APERAK

    Connection source propertie:
    XMLNS Active : Yes

    Connection target propertie:
    Repeating data element character: *
  • SystemAdmin
    SystemAdmin
    527 Posts

    Re: Edi envelope

    ‏2012-11-20T10:54:21Z  
    Not sure if the problem still persists. But we've managed to get this working using a configuration like this for a APERAK XML message to APERAK EDI with envelope:

    In transformation map set property IchgSndrId and IchgRcvrId i.e.:
    SetProperty ("IchgSndrId", \tns:Envelope\tns:Body\apenot:AperakNotificationRequest\apenot:Edifact\aperak:UNB\aperak:UNB02\aperak:UNB0201\aperak:UNB0201.data\\)
    SetProperty ("IchgRcvrId", \tns:Envelope\tns:Body\apenot:AperakNotificationRequest\apenot:Edifact\aperak:UNB\aperak:UNB03\aperak:UNB0301\aperak:UNB0301.data\\)

    Create a new XML format:
    Hub Admin - Hub Configuration - XML Formats
    Click Create Document Family

    Family name : APERAK
    Protocol : XML
    Large file option : None
    Family type : Root Tag
    Family identifier : Envelope

    Click Save
    Click Create XML format

    Family name : APERAK
    Protocol : XML
    Document type : ENVELOPE (ALL)
    Family type : Root Tag
    Family identifier : Envelope
    Name: Format identifier
    Value: Envelope
    XPath expression: Envelope
    Return type: Constant
    Name: Format version
    Value: ALL
    XPath expression: ALL
    Return type: Constant
    Attribute name: Source business identifier
    XPath expression: //*/*/*
    Return type: Text
    Attribute name: Target business identifier
    XPath expression: //*/*/*
    Return type: Text
    Account Admin - Profiles - Partner

    internal partner
    B2B capabilities
    Account Admin - Profiles - B2B capabilities
    Source
    Package: None
    Protocol: XML
    Document Type: ENVELOPE
    Account Admin - Profiles - Partner

    external partner
    B2B capabilities
    Account Admin - Profiles - B2B capabilities
    Target
    Package: N/A
    Protocol: EDI03A
    Document Type: APERAK

    Connection source propertie:
    XMLNS Active : Yes

    Connection target propertie:
    Repeating data element character: *
    Lost Xpath expression in first reply:

    
    Attribute name: Source business identifier XPath expression: 
    //*[local-name()="UNB"]/*[local-name()="UNB02"]/*[local-name()="UNB0201"] Return type: Text Attribute name: Target business identifier XPath expression: 
    //*[local-name()="UNB"]/*[local-name()="UNB03"]/*[local-name()="UNB0301"]
    
  • MichaelGlenn
    MichaelGlenn
    23 Posts

    Re: Edi envelope

    ‏2014-05-19T15:34:20Z  

    Hello,

     

          This issue was resolved by user applying a fix for APAR JR28650 ontop of 6.1.0.2.  This was also resolved in later versions of WPG 6.1..1 and 6.2.

     

    Thanks