Can Trading Networks export document delivery data?

, , ,
4

Good to hear from you Dave! Yes, I figured I wasn’t alone – companies like being paid on time :blush:

Thanks – the TN run-time events seems to be exactly what I was looking for. I poked around today and could get IS to emit delivery events using the sequence of actions. However, I haven’t yet figured out how to ‘subscribe’ to events yet. Anyone have any have any pointers on what I’ve done so far, and on subscribing to events?

(Note: I’m using version 10.1 on extended support, so the document links below are to 10.1)

  • TN Administrators Guide – Page 291 states that the tn.eda.events.deliveryTasks TN configuration property must be set to true. So I set it up in MWS. However, I could find no trace of any event being published to UM in Enterprise Manager

  • The Event Routing PDF is very complex, but on Page 27 it states the event routing can route events to UM. The setup requires reconfiguring the ‘Provider URL’ Command Central.

    image001.png672×544 104 KB

  • So I ensured SPM was running on the B2B IS instance and the instance defined in CC, then reconfigured the B2B instance’s ‘Provider URL’.
    (Interestingly, this screen does not permit certificate authentication to UM – only username and password.)

    image004.png
    image004.png713×405 22.9 KB

  • This led to 7 new event types suddenly appearing in UM as shown in Enterprise Manager below.
    image002.png

  • Events were being published to these queues. I haven’t yet figured out how to subscribe to these events. So I used Enterprise Manager to snooping on the ‘ImmediateDeliveryComplete’ queue. This snoop data seemed tab-delimited, so I copy-pasted into Excel for legibility. It seems the events contain the TN doc ID and task ID of the delivery task, and also the deivery status and status message. The status message is important because that’s where Ariba or VAN detail error messages appear.

    image003.png
    image003.png334×912 16.2 KB

  • I think I’ll need to subscribe to this queues, then use wm.tn.doc:viewAs to obtain the original invoice from the internal TN document ID. I must then push the invoice ID, status and status message to the BI system.

  • Anyone have pointers on subscribing to these events? I can see this event type being returned during snooping –
    $Event$Type={Software AG Product Documentation}ImmediateDeliveryComplete

    image007.png
    image007.png1112×290 22.6 KB

I’m not so sure this is a good idea in general. In 10.15, do TN EDA events still work the same way?

I think the approach is neat in that it’s event driven. But what if events are lost? Is there a way to regenerate events. Probably not, heh? :slight_smile: With this approach, we just need to make the durable reliable.

1 Like