cancel
Showing results for 
Search instead for 
Did you mean: 

Steps on configuring both sender and receiver scenario for IDOC_AAE

Former Member
0 Kudos

Hi, all

I am doing a proof of concept interface on PO 7.3.1 using the new IDOC_AAE adapter. I am setting up a receiver scenario now and running into the error:

<?xml version='1.0'?>

<!-- see the documentation -->

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>

  <SOAP:Body>

    <SOAP:Fault>

      <faultcode>SOAP:Server</faultcode>

      <faultstring>Server Error</faultstring>

      <detail>

        <s:SystemError xmlns:s='http://sap.com/xi/WebService/xi2.0'>

          <context>XIAdapter</context>

          <code>ADAPTER.JAVA_EXCEPTION</code>

          <text><![CDATA[

com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: IDoc: Connection factory name for channel IDOC_POC_Recv_IDOC is null

at com.sap.aii.adapter.soap.web.SOAPHandler.processSOAPtoXMB(SOAPHandler.java:743)

at com.sap.aii.adapter.soap.web.MessageServlet.doPost(MessageServlet.java:470)

I have gone through the 3 blogs:

http://wiki.sdn.sap.com/wiki/display/XI/Configuration+of+inboundRA+in+the+Java+IDoc_AAE+Adapter

http://scn.sap.com/community/pi-and-soa-middleware/blog/2010/10/21/pixi-pi-73-new-java-based-idoc-ad...

http://scn.sap.com/docs/DOC-31398

Unfortunately, they are really for PI 7.3.1 which is dual stack, meaning there is a gateway. However, PO 731 is pure java and there is no gateway. So steps like "local = true" and creating a JCO pointing to local PI will NOT work. I have already installed a standa alone gateway server and still could not get it to work. The help.sap.com doc is also tailored for PI 7.3.1 which assumes there is a local PI gateway service. Not sure if SAP is serious about PO yet as the PO doc on help.sap.com is almost non-existent.

Has anyone been able to get these 2 scenarios working? I would really appreciate if you can share your knowledge.

Thanks,

Jonathan.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi, Dimitri

I appreciate your sharing. But my config is identical to yours. However, can you advise on the following:

1) What do you mean by "business system must be indicated in sender CC"? In my scenario, I am sending IDOC from PO to ECC.

2) Can you share your config on WE20, BD54 and WE21 on ECC for receiving the IDOC?

3) Do you need to do any config on outboundRA? If PO is sending the IDOC, should the outboundRA be configured too? Right now, only the inboundRA is configured although I don't see any doc to configure it.

Thanks,

Jonathan.

Dimitri
Active Contributor
0 Kudos

Hi Jonathan,

To answer your questions:

1. In your integrated configuration scenario, I've put the receiving business system in the header mapping part. On the Sender Communication Component to be more more exact.

    

2. On the back end system side, I only created a partner profile (WE20) to receive my idoc (message type and basic type). Nothing special on that one.

3. I did nothing on the outboundRA. I only configured the inboundRA.

What about your message mapping? Did you fill the fields in segment EDI_DC40? I did not because they will be filled in the header mapping and the receiver idoc adapter.

Kind regards,

Dimitri

Former Member
0 Kudos

Hi, Dimitri

I was able to get it to work by hardcoding the EDI_DC40 and then apply the sender/receiver from payload in the CC. But I know this cannot be the proper way to use the idoc adapter. That is why I opened this thread. Thank you for your confirmation.

I will try the header mapping in the "sender communication channel"

Thank you so much,

Jonathan.

Answers (6)

Answers (6)

Former Member
0 Kudos

Hi, Dimitri

The header mapping checkbox works ... thanks!! That answers my doubt on how we can tell ECC who the idoc sender is. It used to be identified by the logical system in SLD in PI but I don't think it's in use anymore in IDOC_AAE.

Dimitri
Active Contributor
0 Kudos

Hi Jonathan,

Nice!

Just to complete...

The ECCCLNT300 is the business system from the SLD, which I use in my scenarios.

Also, this is the logical system name for client 300 of the ECC back end system.

Kind regards,

Dimitri

Former Member
0 Kudos

Thanks!

Dimitri
Active Contributor
0 Kudos

Dear Jonathan,

I once made a one-slider on this topic and want to share this with you. This is based on a SAP PO 7.31 single stack system.

Kind regards,

Dimitri

Former Member
0 Kudos

Hi, all

I am still getting the following error when I am trying to send a message to PO then ECC to invoke an IDOC:

IDoc: Adding control record to payload failed due to The Configuration for Sender/Receiver Partner Number/Port is incorrect. Enter proper values in Sender/Receiver Component

Can you advise what should be the partner in WE20/WE21 since PO doesn't have a client? I have tried to put in SIDCLNT000 but I still got the above error.

Mariana/Rossen, thank you for your help but I have already seen all of your link. Actually I spent a whole afternoon looking into help.sap.com and I found NO doc for IDOC config for PO(yes, there are docs for PI). I would appreciate if you can send me the exact link if I am missing something. All of the blogs in SDN is dealing with PI on IDOC_AAE and everybody is assuming their procedure works on PO.

Thanks,

Jonathan.

Former Member
0 Kudos

Hi Jonathan,

While I am not an expert in configuring the IDoc adapter, I'd like to try to help you with information about the organization of the documentation so that it would be easier for you to find what you need.

For 7.3 and later releases, the right way to access the documentation for PI is http://help.sap.com/netweaver > choose release (for example http://help.sap.com/nw731/ ) > Application Help > Function-Oriented View > choose language (for example English) > Process Integration. This is the places where you would find all technical details about configuring and using PI.

Please note that on the Application Help step there is a 'SAP NetWeaver Process Integration' link. It leads to overview documentation for PI, which is intended as an introduction for PI and does not provide many configuration details.

Now, from what I know PO is Java-only PI (AEX, and so on) with BPM integrated. The documentation you access with the path provided above contains everything available for PI. Consider the following when browsing this documentation:

  • First, about PO. When viewing 'SAP NetWeaver Library: Function-Oriented View' there is a 'Process Orchestration' node there. I think it contains only information specific for using AEX and BPM together. If you need details for configuring and using AEX or BPM - no matter whether part of PO or not - you should use the corresponding documentation.
  • For AEX, this documentation is in SAP NetWeaver Library: Function-Oriented View > Process Integration > Advanced Adapter Engine. In particular, you could find useful the information there in Adapter Configuration > Configuring the IDoc Adapter (Advanced Adapter Engine).
  • For BPM, this documentation is in SAP NetWeaver Library: Function-Oriented View > Composition Environment > Business Process Management.

Hope this helps,

Rossen

Former Member
0 Kudos

Hi, Rossen

I am well aware of the web pages you are pointing ... but can you point me to the exact place for the IDOC config for PO? I simply could not find it after spending the whole afternoon searching.

Thanks,

Jonathan.

Former Member
0 Kudos

In regards to the Process Orchestration library on SAP.help.com - You can access it all from here: Concepts, PI & BPM runtime integration, message processing configuration, including large message processing, mappings, integration patters, etc.

Hope this is helpful.

Former Member
0 Kudos