Skip to Content

Doubts on IDOC_AAE to AS2 Scenario.

Hello Experts,

I have 2 queries on IDOC_AAE and AS2.(PI 7.31 dual stack)

1. Now in our IDOC_AAE to AS2 scenario we have setup IDOC_AAE communication channel with ICO and everything is working fine.we are receiving IDOC through communication channel, Now i have a doudt what about the earlier scenarios which are not using IDOC_AAE channel how will they be able to get the IDOC as these IDOC's are not available on abap stack, how does it identify on ECC that when an IDOC is triggered it has to pass thorough ABAP or JAVA stack ?as IDOC are not available on abap stack hopw will those scenario work?

2.Earlier we had an design like PI used to receive proxy and used to send this proxy by converting it as flat file in AS2 module for third party, now we have a requirement to send the IDOC XML to AS2 without conversion for the same party using the same existing connectivity details, we have completed this setup also  but as third is not ready with their mapping to receive the XML , if we try to send data will it fail in PI/Seeburger monitor or will it be successful ?

Br,

Manoj

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Apr 08, 2015 at 06:53 PM

    Hi Manoj

    1. Now in our IDOC_AAE to AS2 scenario we have setup IDOC_AAE communication channel with ICO and everything is working fine.we are receiving IDOC through communication channel, Now i have a doudt what about the earlier scenarios which are not using IDOC_AAE channel how will they be able to get the IDOC as these IDOC's are not available on abap stack, how does it identify on ECC that when an IDOC is triggered it has to pass thorough ABAP or JAVA stack ?as IDOC are not available on abap stack hopw will those scenario work?

    --->> As per your comments the PI is 7.31 dual stack, so for ICO (java only) scenario you need to use IDOC_AAE sender channel in ICO. for pipeline step scenario no need for sender channel as it is will route through ABAP stack.

    2.Earlier we had an design like PI used to receive proxy and used to send this proxy by converting it as flat file in AS2 module for third party, now we have a requirement to send the IDOC XML to AS2 without conversion for the same party using the same existing connectivity details, we have completed this setup also  but as third is not ready with their mapping to receive the XML , if we try to send data will it fail in PI/Seeburger monitor or will it be successful ?

    --->> you can remove the module and message will be deliver to same partner without any issue.

    regards,

    Harish

    Add comment
    10|10000 characters needed characters exceeded

    • Just to add on about (2) - PI/Seeburger monitor only provides status about the technical status of the data transfer via AS2. Whether the third party is ready with their mapping (or not) relates to application processing. Since the transfer via AS2 is asynchronous, there will not be any application response, so any application error during mapping on the third party side is not visible to the sender.

  • Apr 09, 2015 at 03:34 AM

    Hi Harish / Eng ,

    Thanks for your valuable input.

    Regarding(2)

    As i don't want to disturb  the earlier healthy interface so i have created a new AS2 communication channel with same connectivity details but no conversion modules used here as i don't have any conversion of XMl to flat but when i tried to test end to end i am getting below error in Seeburger adapter  .

    parallel i tested the earlier interface and they are working fine .


    Br,

    Manoj

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 08, 2015 at 05:39 PM

    1. IDOC routing to new system and old system depends on we20 partner profile settings. you can define the recevier port and route your idocs.

    you cannot trigger same idoc to 2 different PO system.

    Add comment
    10|10000 characters needed characters exceeded