on 12-23-2014 1:06 PM
Hi all,
we are currently evaluating the B2B-Add-on. I have tigged to receive delivery report from X.400 VAN provider and I also receive them. The polling X.400 sender channel is searching for following Sender Agreement:
So far so good. I am receiving a message into the pipeline containing following payload:
If I look to the Main Tab, I also see a good reference to the originally sent outbound message (where the X.400 delivery report is the answer to).
I have already looked into following topics, but not really get further:
http://scn.sap.com/docs/DOC-39575
http://scn.sap.com/docs/DOC-16003
I of course can create some ABAP or JAVA mapping to create a mapping to ALEAUD, but I would assume their must be something out-of-the-box at SAP PI to handle those acknowledgements automatically.
Have I missed any how-tos on that or can someone give me some good hints how to continue?
Thanks and merry x-mas to all of you!
Regards Helmut
Hello Helmut,
I'm stuck with the same problem. Did you find a solution?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kaan,
We have not followed this approach anymore. As the number of X.400 partners is in total 4 and we are not planning to ramp up new partners on this expensive protocol we are not processing the receipt confirmation (as this is causing additional costs with Telekom).
BR Helmut
To link from or to the ALEAUD structure, I guess you need to create a separate (graphical) message mapping.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok don't want to start the mapping tool discussion now 😉 Maybe with calling a function module out of the graphical map you can solve it was well, but I am avoiding graphical map when possible because you very easy get lost in the maintancance of a mapping.
But to come back to the original topic about anybody knows something "out of the box" for x.400 delivery reports updating the acknowledgement for the original sending message?
avoid a graphical mapping for maintenance purposes is a valid argument. It' a (customer's) choice you have to make.
I really think you need an extra mapping and scenanrio to route the acknowledgement message back to the sender.
Only e.g. for AS2 messages, the sender adapter will produce an acknowledgement and hand it over to the initial message sender.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.