Skip to Content

PI 7.3 IDoc Sender No party configured for agency

Hello experts,

We are migrating from 7.1 to 7.3.   We have a business partner sending us IDocs.  The first test from the sender system to PI 7.3 was successful.   The second IDoc type failed to process and gave us the following error messages:

[JRA]serverExceptionOccurred. Server XI_IDOC_DEFAULT_ODA, Managed_Application_Thread_23, connectionId=5-10.75.70.170|sapgw00|XI_IDOC_DEFAULT_ODA, Exception: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.adapter.idoc.app, BC-XI-CON-IDO) Exception raised from invocation of public void com.sap.aii.af.idoc.inbound.IDocReceiverBean.onCommit(java.lang.String) method on bean instance com.sap.aii.af.idoc.inbound.IDocReceiverBean@448e4c4e for bean sap.com/com.sap.aii.adapter.idoc.app*xml|com.sap.aii.adapter.idoc.ejb.jar*xml|IDocReceiverBean in application sap.com/com.sap.aii.adapter.idoc.app.; nested exception is: com.sap.conn.idoc.IDocRuntimeException (raised by system |ODACLNT000_AAE)

and

No party configured for agency <business system>, scheme ALE#LI and name 0000000001



ODA is the SID for PI.    ODACLNT000_AAE is RFC destination from the sending system.


Again, this worked with an earlier IDoc.   The main difference I see between the two IDocs is in the control record.

Successful IDoc shows partner number as <logical system name> and partner type as LS.

Error IDoc shows partner number as 0000000001 and the partner type as LI. If we edit the IDoc in T-Code WE19 and change the partner number and type, the IDoc passes. 


Both scenarios work when sending to the 7.1 system. We would rather not have our business partner change their process.


Any help or ideas on how to handle this by only changing settings in PI 7.3 are appreciated.


Thanks!


Tom

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Best Answer
    avatar image
    Former Member
    Mar 04, 2014 at 07:02 AM

    Hi Tom,

    if <logical system name>  is static then hard code it in the inbound function module (modifying control record).

    If you won't get any solution.. use above procedure to resolve the same .  Thank you .

    Regards,

    Balaji P.

    Add comment
    10|10000 characters needed characters exceeded

    • Hello Balaji,

      The logical system name is not static for this IDoc process.  We are being passed a vendor number, which can be different for each IDoc.

      Thanks!

      Tom

  • avatar image
    Former Member
    Mar 04, 2014 at 07:11 AM

    Hey Tom,

    With the change in IDoc type, your sender interface in PI configuration should be different.

    This error Failed in component is because the IDoc is not able to determine sender ie.  business component/system.

    Please have an ICO/Iflow created with the sender interface MessageType.IdocType

    Regards,

    Pooja

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 04, 2014 at 07:23 AM

    Hi Tom

    Please check whether the partner profile has been created for partner 0000000001??

    Also if IDOC type is different then please make sure that you have the corresponding ICO or sceanrio for that idoc.

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 05, 2014 at 02:30 PM

    Hello,

    @Pooja and Indrajit,  We do have an ICO/Iflow created with the sender interface MessageType.IdocType.  Thank you.

    Tom

    Add comment
    10|10000 characters needed characters exceeded

  • Mar 05, 2014 at 02:38 PM

    Experts,

    This scenario works in PI 7.1 because we don't have a sender communication channel.  The sending system pushes the IDoc to PI 7.1 and is processed using the IDoc type. 

    In the new 7.3 scenario, we now have an IDoc default communication channel that is looking at the sender partner <0000000001> and partner type <LI>.   This partner is a vendor number on the sending system and can be any number. 

    I am looking into the parameters on the IDoc_AAE adapter type for the communication channel to see if this can be resolved there.  

    Any assistance or direction form experts is appreciated.

    Thanks!

    Tom

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Tom,

      I am facing exactly the same issue in our migrated environment as well i.e. in PI7.4

      Could you please help me the solution.

      I'll be really thankful to you 😊

      Many thanks,

      Abhi