ABAP Proxy - No message in PI

[Former Member]

Hi experts,

We are developing a scenario using ABAP Proxy to send an assynchronous message to PI 7.3.

The problem is that the message is sent by ABAP code, but is not shown at SXMB_MONI.

The routing objects were created at Integration Directory, but seems that PI is not processing the message sent by the proxy.

Any idea about what may be wrong?

Edited by: David Tiago Conceição on Jan 5, 2012 2:13 PM

[udo_martens · Accepted solution]

Hi David,

may be you forgot the COMMIT WORK statement?

Regards,

Udo

[Former Member · Accepted solution]

The COMMIT WORK statement is right after de proxy call.

Looks right.

[udo_martens · Accepted solution]

Hi David,

you should catch exceptions and print them out like:

data: l_sys_exception type ref to  cx_ai_system_fault,
      l_error_text type string.


CATCH cx_ai_system_fault INTO l_sys_exception.
        l_error_text  = l_sys_exception->errortext.
        write l_error_text.

In addtion monitor the ERP / PI queues at SMQ1/SMQ2 - may be will find the message there.

Depending from the results we go further, may be the destination to PI does not work or proxy configuration is wrong or something else.

Regards,

Udo

[Former Member]

Hi experts,

The basis found a mistake in destination configuration. That was causing the 401 error.

Thanks for the help!

Best regards!

[Former Member]

Hi,

The user configurated in ECC destination to PI have the same role from PIAPPLUSER, plus some other roles and now is a System user.

But the problem still occurring: the message is sent to PI, but return with error 401 - Unauthorized.

[udo_martens]

Hi David,

can you check in SU01 if the user locked?

can you check what happens if you temporary take another (your) user?

Regards,

Udo

[Former Member]

Hi,

If you have configured the scenario through Advance Adapter Engine, then you won't find the message in PI (SXMB_MONI).

Regards,

Krishna Chauhan

[Former Member]

Hi,

The user configurated in ECC destination to PI have the same role from PIAPPLUSER, plus some other roles.

But this user is configurated with type Service. Do you think this is the problem?

I asked the basis team to change to System type to make new tests.

[Former Member]

Hi,

The messages are show in SXMB_MONI from ECC.

Their status is system error, and the error description is 401 - Unauthorized.

Do you think some configuration is missing at PI?

Do I have to create a communication channel to ABAP Proxy sender?

Thanks everybody.

[Former Member]

Hi,

We dont need to create communication channel for Proxy.

check pre configuration steps for proxy.

There is some problem in the connection .

Check the SLDCHECK.

regards,

ganesh.

[udo_martens]

Hi David,

have a look to SXMB_ADM (ERP) / Integration Engine Configuration. There is a destination (Corr Integration Server) used for runtime. Open it in SM59 and check the user. This should be a PI user with same rights as PIAPPLUSER. May be the user is locked or does not have enough authorizations.

Regards,

Udo

[Former Member]

Hi David,

Check in SXMB_MONI at ECC if data is existed in that messgage or tht messgae is empty.

Regards,

Soumya A

[Former Member]

Hi,

The queues were reactivated in ECC. Now the messages are forwarded to PI, but SXMB_MONI still don't show any message at PI.

[Former Member]

Hi,

Are you able to see your messages in chequered flag state in ECC ?

if no messages are seen over there then check the connect test using SLDCHECK..

HTH

Rajesh

[former_member184681]

Dear David,

Maybe the message is stuck behind another one that contains an error? As the name says, this is a queue, so the message will not be processed until all previous messages disappear from the queue.

Another thing you could check is the status of the queue itself - try activating in in SMQR, this might help.

Regards,

Grzegorz

[Former Member]

Hi Grzegorz,

I haven't found previous error messages.

We will check the queue activation.

[Former Member]

Hi Experts,

The messages are stuck in SMQ2 transaction, with status Scheduled. Looks like something is preventing message to be forwarded to PI.

Any ideas?

[udo_martens]

Hi David,

which system?

Did you configure SMQR? Are queues configured there? If not there is is link in SXMB_ADM to create the queues.

May be a former message is blocking the following messages?

Regards,

Udo

[Former Member]

Hi Udo,

The messages are scheduled at ECC and are not forwarded to PI.

We will check the SMQR configuration.

[baskar_gopalakrishnan2]

Since message got stuck in ECC, you might want to reactivate Queues after Registering it. Take help from BASIS for this. Go to SXMB_ADM and see the link for Queues.

[Former Member]

Baskar,

The queues must be reactivated in ECC?

[Former Member]

Hi,

You need to reactivate the queues of ECC...

if you cannot wait till that process is done... you can go to particular queue and click on unlock button for the message to get processed in that queue for time being...

HTH

Rajesh

[baskar_gopalakrishnan2]

Your initial problem is at ECC. so reactivate queue over there.

[baskar_gopalakrishnan2]

>We are developing a scenario using ABAP Proxy to send an assynchronous message to PI 7.3. The problem is that the message is sent by ABAP code, but is not shown at SXMB_MONI.The routing objects were created at Integration Directory, but seems that PI is not processing the message sent by the proxy

Couple of suggestions.

1) Make sure proxy configuration to establish communication between ECC and PI is in place. Check SLDCHECK.

2) Local Integration engine of ECC creates PI SOAP format message from proxy objects and transmits to PI. That's the reason we dont even use sender proxy adapter. Check whether you are able to see message at the ecc side using sxmb_moni.

I suspect messages are not even reaching PI. Verify this. If the messages are reached PI then you might want to check Queue whether messages are stucked there. In this case, yoiu might want to register and reactivate the queues.

[former_member184681]

Hi,

Are you sure that the proxy message is created? If so, but still the message is not visible in XI monitoring tools, then check the sxi_monitor on ECC side - maybe you will find some error details there.

Regards,

Grzegorz