Skip to Content

AAE_IDoc adapter EDIDC40-DOCNUM problem

Hi experts.

We have an async integration scenario:

3rd party (SOAP WS) --> PO 7.4 --> SAP ECC (Custom Z Idoc)

I need to send an application acknowledge from ECC to 3rd party using ALEAUD on ECC side.

With “old” Idoc-Adapter on ABAB-Stack everything works fine as we could map the external unique ID to EDIDC40-DOCNUM.

However, it seems that the new AAE_Idoc adapter is ignoring this mapping and generates a random DOCNUM ID.

The main problem is that in outbound ALEAUD Idoc generated from SAP, E1STATE-DOCNUM is not filled any more with the external unique ID.

Does anyone know how we can fix this scenario?

Thanks in advance!!


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Apr 14, 2016 at 02:21 PM

    For us this is a really weird behavior of the AAE IDoc-Adapter and it worked perfectly with ABAP IDoc-Adapter.

    However, after analyzing this problem we found the note 2174006 - DOCNUM ignored by IDOC_AAE Receiver channel

    So I think for SAP it works as designed

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 06, 2016 at 12:39 AM

    One option is to push the Idoc to ECC using the soap runtime of ECC for IDocs as per this blog : SOAP for IDOC demystified

    What this means is that: you make a synchronous call to ECC and get the Idoc number back from ECC that can then be used to map back to the soap caller. Infact your end to end flow would then be synchronous.

    Ofcourse this would not work if you need to get the status of the idoc also sent back to the caller.



    Add comment
    10|10000 characters needed characters exceeded