Messages in AE stuck due to wrong client in control data

[nidhi_srivastava22]

Hi Experts,

Its a bit critical issue, please reply asap.

There are around 400 messages stuck in AE in production system, as during some testing client was changed from 004 to 000.

These messages are now pointing to client-000 and our production server is on client-004.

Is there any means by which we can resend those messages from PI instead of contacting the clients for resending??

Please advice on this issue.

Thanks!

Regards,

Nidhi

[Former Member · Accepted solution]

Hi Nidhi,

As a workaround can you just try to send one message from RWB and see whether it is going to correct client or not.

If it is going that you can restart all the failed messages and if not please share the screenshot.

Regards,

Abhi

[nidhi_srivastava22 · Accepted solution]

Hi Abhinav,

Thanks for your reply.

We have asked for client confirmation post which we will try the same.

But sending 400+ messages would be a tough task. Do share if anything else strikes.

Thanks!

Regards,

Nidhi

[Bhargavakrishna · Accepted solution]

Hi Nidhi,

Refer the below blog

Regards

Bhargava krishna

[Former Member · Accepted solution]

Hi Nidhi,

Since count is more ...you can download the data and ask any Abaper ,he can upload these data in ECC system directly.

Please note this is just an alternative approach so avoid it in regular parctise.

But take client confirmation before to avoid duplicate enteries.

Thanks,

Abhi

[Former Member]

Hi Nidhi

Unfortunately we don't have the option to edit the data directly from AE and resend.

You have to correct the data and then the same needs to be sent from RWB again using the test option.

If you have time , then you can think of writing one report in PI which will read the payload based on message id .

Once you read the payload, you can make the changes payload in the program and then you can call HTTP client to push the payload to PI.

The input of the program will be a selection screen where you will put 400 message id's.

sample code:

CALL FUNCTION 'SXMB_GET_MESSAGE_PAYLOAD'

     EXPORTING

       im_msgkey      = ls_msgkey

       im_archive     = ' '

       im_version     = '000'

     IMPORTING

       ex_msg_bytes   = lv_bin_xml

     EXCEPTIONS

       not_authorized = 1

       no_message     = 2

       internal_error = 3

       no_payload     = 4

       OTHERS         = 5.

CALL METHOD cl_http_client=>create_by_destination

       EXPORTING

         destination              = destination

       IMPORTING

         CLIENT                   = CLIENT

       EXCEPTIONS

*       argument_not_found       = 1

*       destination_not_found    = 2

*       destination_no_authority = 3

*       plugin_not_active        = 4

*       internal_error           = 5

         OTHERS                   = 1.

     IF sy-subrc <> 0.

* Implement suitable error handling here

     ENDIF.

But as I have told you this will take lot of time but you don't need to manually send the 400 messages.

[iaki_vila]

Hi Nidi,

Have you checked this thread ?, you have some suggestions/blogs to do it.

Regards.

[nidhi_srivastava22]

Hi Inaki,

The messages are not in Holding, they are in system error.

They are not being processed as the control record is having wrong information(pointing to client - 000) due to some SLD changes. Now, we want to change that value(pointing to client - 004) and reprocess from Adapter engine.

Please guide over this.

Thanks!

Regards,

Nidhi

[gagandeep_batra]

Hi Nidhi,

you can use the test tool in the RWB to resend the message using the corrected payload means change the client there

Regards

GB