webMethods

webMethods

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
Back to discussions
Expand all | Collapse all

EDI DELFOR:04A - Invalid Sender/Receiver Id

  • 1.  EDI DELFOR:04A - Invalid Sender/Receiver Id

    Posted Wed October 21, 2015 11:51 AM

    Hello.

    we are receiving an EDI document of type UN/EDIFACT DELFOR:04A.

    TN could not identify partner information and throws an error message in
    Activity log of the transaction:

    Invalid Sender ID [EDIFTN.000010.000233]
    EDI qualifier: 92, ID: CASTA3 [EDIFTN.000010.000232]

    Invalid Sender ID [EDIFTN.000010.000233]
    EDI qualifier: 92, ID: JENOPTIK [EDIFTN.000010.000232]

    Here is an extract of the EDI message:

    UNA:+.? ’
    UNB+UNOC:3+CASTA3:92+JENOPTIK:92+151013:0240+236++DELFOR’
    UNH+1+DELFOR:D:04A:UN:GA0511’
    BGM+241+78’
    DTM+137:20151013:102’
    RFF+BO:6100072667’
    RFF+AIF:77’

    Is there a standard EDI qualifier for TN that i can use for qualifier 92 ?

    And if not, how to enable the qualifier 92 for TN to get a working/correct
    partner recognition ?

    Thanks a lot for your ideas!
    Sebastian


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


  • 2.  RE: EDI DELFOR:04A - Invalid Sender/Receiver Id

    Posted Thu October 22, 2015 03:57 PM

    92 means it’s Buyer Agent.
    Try to config this ID with type “buyer agent” under its TN profile, TN should automatically recognize it.


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


  • 3.  RE: EDI DELFOR:04A - Invalid Sender/Receiver Id

    Posted Thu October 22, 2015 05:14 PM

    Yes that is for EDIFACT external id match 92/Buyer Agent

    HTH,
    RMG


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


Related Content