IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

Extract PO for extended attribute association

  • 1.  Extract PO for extended attribute association

    Posted Wed October 24, 2007 05:14 PM

    Hi, All
    I am new here. I am trying to assoicate PO to our EDI 850 transaction in TN.
    I need create a service to extract PO. Is there any easy way to do it?
    I already test the other steps, associate attribute type to doucument by wm.b2b.editn:addAttributeTypeToBizDoc,
    set value to the attribute by wm.tn.doc:setAttribute, save value to TN db by wm.tn.doc:updateAttributes.


    #webMethods
    #B2B-Integration
    #Integration-Server-and-ESB


  • 2.  RE: Extract PO for extended attribute association

    Posted Wed October 24, 2007 06:19 PM

    Are you trying to relate a source PO document to a resulting 850 document? If so, you can simply use relateDocuments to associate the documents with each other.


    #webMethods
    #B2B-Integration
    #Integration-Server-and-ESB


  • 3.  RE: Extract PO for extended attribute association

    Posted Wed October 24, 2007 06:59 PM

    We are try to assoicate the surce PO number to transaction for later query. Such as use Transaction Analysis in TN and query by PO number.


    #Integration-Server-and-ESB
    #B2B-Integration
    #webMethods


  • 4.  RE: Extract PO for extended attribute association

    Posted Wed October 24, 2007 07:04 PM

    Is the PO an XML doc? Is the 850 something that is sent to you or are you creating it?


    #Integration-Server-and-ESB
    #B2B-Integration
    #webMethods


  • 5.  RE: Extract PO for extended attribute association

    Posted Wed October 24, 2007 07:08 PM

    It’s inbound EDI850 sent by our customer to our TN. It is not be converted to XML yet


    #webMethods
    #B2B-Integration
    #Integration-Server-and-ESB


  • 6.  RE: Extract PO for extended attribute association

    Posted Wed October 24, 2007 07:29 PM

    The easiest thing to do then is in the service that processes the 850 is to get the PO number from the appropriate segment and then call the setAttribute and updateAttributes that you outlined in your post.


    #B2B-Integration
    #Integration-Server-and-ESB
    #webMethods


  • 7.  RE: Extract PO for extended attribute association

    Posted Wed October 24, 2007 07:37 PM

    Do I need to put bizDoc in a variable and pass it into 850 process servoice sothat setAttribute and updateAttributes can use it?


    #B2B-Integration
    #Integration-Server-and-ESB
    #webMethods


  • 8.  RE: Extract PO for extended attribute association

    Posted Wed October 24, 2007 08:45 PM

    TN will automatically create a bizdoc variable in the pipeline. I assume that your service that gets invoked via the TN rule has the bizdoc, receiver and sender variables defined per the TN documentation for creating TN invoked services.


    #B2B-Integration
    #webMethods
    #Integration-Server-and-ESB


  • 9.  RE: Extract PO for extended attribute association

    Posted Wed October 24, 2007 08:48 PM

    I get it. Thank you very much Reamon!


    #webMethods
    #Integration-Server-and-ESB
    #B2B-Integration