IDOC_AAE dump in SM58

[Bhargavakrishna]

Hi experts,

im facing issue with the IDOC_AAE adapter.

IDOC is not triggering to PI from ECC. when i tested it from WE19, it is creating dump in SM58. find the below screenshot for the same.

My communication channel is working properly, cleared the cache as well.

also tried by making some changes in in communication channel and activated.

also tested the IDOC from WE19.

Any valid suggestions will be highly appreciable.

Regards

Bhargava krishna

[former_member194612]

Hi Bhargava,

Can you please try what the Rajesh told above..and let us know the result?

Thanks,

Satish

[Bhargavakrishna]

Hi Satish,

Still facing the same issue.

please help me..

Regards

Bhargava krishna

[former_member194612]

Hi Bhargava,

pls check the same once and let me know the result.

Hope you are using java idoc(idoc_aae)..

Thanks,

Satish

[Bhargavakrishna]

Hi Satish,

Yes im using IDOC_AAE.

Regards

Bhargava krishna

[former_member194612]

Hi Bhargava,

I am sorry, if forgot the link in my earlier post

http://scn.sap.com/thread/3225459

pls check the same and reply the result

Thanks,

Satish

[Bhargavakrishna]

Hi Satish,

Thank you very much for your reply.. i already applied this patch..

when we run the pgm to trigger the IDOC to PI. it is generating the IDOC with the status 03. its TRFC issue.

When i try to execute it from SM58, it is showing that, Function module does not exist or exception raised.

Is it the problem with the program or with PI.

The parameters, which i mentioned to load the meta data or correct?

Regards

Bhargava krishna

[former_member184789]

Hi,

Can you check if the below solutions work for you:

http://scn.sap.com/message/6101501

http://scn.sap.com/thread/153542

https://scn.sap.com/thread/1761902

[Bhargavakrishna]

any inputs?

[anupam_ghosh2]

Hi Bhargava,

Please ensure that the user with which ECC logs in to PI  (sm59 transaction)  has the necesssary permissions to execute the RFC "IDOC_INBOUND_ASYNCHRONOUS" . This seems to be authorization issue.

Regards

Anupam

[Bhargavakrishna]

Hi anupam,

May i know, what authorizations that the PI user should have..

Thanks in advance for your help..

Regards

Bhargava krishna

[anupam_ghosh2]

Hi Bhargava,

I am not sure of exact authorization to be assigned.

However In su01 BASIS/ADMIN team may manually assign role SAP_NWA_FULL to the user temporarily.

Then you can try sending the idoc and test.

Also please check this link

http://help.sap.com/saphelp_nwpi71/helpdata/en/44/e47e166a742951e10000000a11466f/content.htm

Hope this resolves the issue.

Regards

Anupam

[former_member194612]

Hi Bhargava,

Can you please check below

1) Go
  to NWA -> Configuration -> Infrastructure -> Application    Resources    2) Filter the corresponding resource adapter(ex:  JIDOC_VAR2_RA)    3) Go to 'Message Listeners' tab    4) Check for the 'com.sap.mw.jco.jra.QueuedIDocMessageListener' and
  'com.sap.mw.jco.jra.IDocQueueMessageListener'    entry.    5) If it is not there, please add the following      Type : com.sap.mw.jco.jra.QueuedIDocMessageListener      Activation Specification Class
  :    com.sap.mw.jco.jra.JRA$IDocActivationSpec      Type :
  com.sap.mw.jco.jra.IDocQueueMessageListener      Activation Specification Class
  :    com.sap.mw.jco.jra.JRA$IDocActivationSpec.    Check that only the message listeners which are required are present. The
  others can be deleted.

Thanks,

Satish

[Bhargavakrishna]

Hi Satish,

I checked the message listeners in NWA. they are present under the resource adapter.

There are the other message listeners as well. If we keep them, does it effect the IDOC_AAE or how it is?

They are also related to IDOC only.

Regards

Bhargava krishna

[former_member194612]

Hi Bhargava,

It may effect sometimes, Can you please check once if possible delete the other listeners and try ?

I was told once , it will effect.

Thanks,

Satish

[Bhargavakrishna]

Hi Satish,

i have the following parameters under message listeners.

Type	Activation Specification class
javax.resource.cci.MessageListener	com.sap.mw.jco.jra.JRA$StandardActivationSpec
com.sap.mw.jco.jra.IDocMessageListener	com.sap.mw.jco.jra.JRA$IDocActivationSpec
com.sap.mw.jco.jra.QueuedIDocMessageListener	com.sap.mw.jco.jra.JRA$IDocActivationSpec
com.sap.mw.jco.jra.SynchronousMessageListener	com.sap.mw.jco.jra.JRA$SynchronousActivationSpec
com.sap.mw.jco.jra.IDocQueueMessageListener	com.sap.mw.jco.jra.JRA$IDocActivationSpec
com.sap.mw.jco.jra.AsynchronousMessageListener	com.sap.mw.jco.jra.JRA$AsynchronousActivationSpec
com.sap.mw.jco.jra.StatefulSynchronousMessageListener	com.sap.mw.jco.jra.JRA$StatefulSynchronousActivationSpec
com.sap.mw.jco.jra.JmsMessageListener	com.sap.mw.jco.jra.JRA$JmsActivationSpec
com.sap.mw.jco.jra.TransactionalMessageListener	com.sap.mw.jco.jra.JRA$TransactionalActivationSpec

Which parameters i should delete?

it will not effect the process right?

Regards

Bhargava krishna

[Bhargavakrishna]

Hi All,

Facing new issue, since i delete the message listeners from NWA.

any help will be highly appreciable..

Regards

Bhargava krishna

[Former Member]

Hi,

Did you implemented the SAP Note : 1767710 if not check it out

I got the above error and after applying the above note resolved the issue..btw i was using PI 7.31 Sp5

Gud Luck

Regards
Rajesh

[Bhargavakrishna]

Hi Rajesh,

Thank you very much..

im using PI 7.31 Sp 34.

i will work on it and let you know the status...

Regards

Bhargava krishna

[Bhargavakrishna]

Hi Rajesh,

We have installed the patch as per the SAP Note.

Still facing the same dump in SM58. when i monitor the idoc adapter from RWB.

I find that metadata is not loading into PI.

When im trying to Pre-load the meta date by passing the parameters, it is failing.

For IDOC Type : [ IDOC MESSAGE TYPE]

For service  : i mentioned Business system

For Channel name: mentioned the idoc Communication channel name.

but  " pre-load failed: Check parameters entered "

please help me.

Regards

Bhargava krishna

[Former Member]

Hi,

After installing the patch did you tried resending the IDoc from the source system

if not please try it out if you still encounter the same issue then best option is to open the OSS Message..

Gud Luck

Rajesh

[former_member184681]

Hi,

It looks like you were missing some configuration. Have a look at this blog by :

and make sure your configuration is simlar as there, including the inboundRA.

Regards,

Greg

[Bhargavakrishna]

Hi,

I already referred those documents. did the same configuration. but the data is not coming to PI when i trigger the IDOC from ECC.

when i test it from WE19, it is creating the IDOC with the status 03[ IDOC passed to Port] and creating dump in SM58 as i mentioned above.

Regards

Bhargava krishna

[Former Member]

Hi,

Though I am not sure what exactly the reason for your dump, but please cross check the below configuration steps

1. Check the ProgId and local gateway parameters (host, port, local gateway) in PI

    NWA ->Configuration -> Infrastructure -> Application Resources -> inbound RA

    local gateway parameter needs to be false if it is a dual stack esle should be true.

2. Check the RFC destination created in ECC with the same progID and gateway details.

3. Test the RFC connection in ECC.

HTH

Rajesh

[Bhargavakrishna]

Hi Rajesh,

We are using PI 7.3 EHP1 dual stack.

As suggested by you, i have changed the following parameters in NWA.

Prgm id : XI_IDOC_DEFAULT_PIT

Destination name : XI_IDOC_DEFAULT_Destination

Max thread count : 10

Local = false.

gateway Server :  [PI host ]

gateway service : [PI host service]

In ECC created the RFC destination, with the same pgm id: which is given in the NWA. and PI host ans service details. tested the connection. it is working fine.

Regards

Bhargava krishna

[Former Member]

Still you getting the same error when you retriggered the IDoc after configuration like above ?

Rajesh

[Bhargavakrishna]

Yes rajesh..