Editing Payload in SXMB_MONI

[Former Member]

Hi All,

Is this possible to edit payload in SXMB_MONI.

I have already the following url which talks about editing payload from RWB - > Message monitoring.

https://www.sdn.sap.com/irj/scn/wiki?path=%3fpath=/display/xi/whole%252bpayload%252bto%252ba%252bxml...

Actually I am looking into the options of editing payload in SXMB_MONI of ECC.

Thanks in Advance for the help.

Best Regards

Ashok

[former_member206760 · Accepted solution]

no that option is not available

[former_member192295]

Hi,

We don't have option to change payload in moni meanwhile if you change also i think no use for further process.

[Former Member]

HI!

I think there is no such option is there in ABAP STACK. Even I searched in SAP help documentation. I didn't found any data related to "Edit payload in MONI"

You can _EDIT_ your payload only in the RWB-->Component Monitoring as explained below.

Supppose if you want to test the message again or if you want to edit your payload and resend then

no need of again placing the file in the FTP location --> Just go to Moni and copy the request payload

paste the same payload in the

RWB--> Component Monitoring >Adapter Engine>Test Message-->

give your scenario details and paste the payload and send then you can able to send in this way also.

Regards::

Amar Srinivas Eli

[former_member307485]

Hi Ashok,

Please have a look at the last section of the following link

http://help.sap.com/saphelp_nw70/helpdata/en/c9/775b3b82646c3ae10000000a114084/frameset.htm

Regards,

Divya

[Former Member]

This is a good link for what am searching for, it shows that the message can be edited in the sxmb_moni tcode, but am not able to get that edit icon in the moni window, Basis team had given the full admin access in the sandbox but still unable to get the edit icon ...

[former_member307485]

Hi Ashok,

As the link suggests : The Display/Change icon is only available for asynchronous messages with errors.

Otherwise there is no option to edit mesage in SXMB_MONI.

Regards,

Divya

[Former Member]

Hi ,

am trying to edit only asynchronous message, here is the requirement that we have

Our OTC team has escalated a support issue with a call tag

return that could fail as it comes into SAP.

A "call tag" return is the result of a mis-shipment where the customer

either received damaged product or the wrong product. These returns

come in with not only the account but also the invoice number. The

return is referenced to the originating invoice and the credits are

created based on the prices and discounts that are on the invoice. If

the invoice number on the return does not match an invoice for the

account, then the return will fail.

For some reason, the return fails in the ABAP Proxy layer of SAP ECC

with Application errors and does not provide the ability for the

business to repair the data.

Unfortunately, this failure occurs frequently in production today (1-2

a week - as many as 15) and we anticipate that we will continue to see

these failures with SAP. The invoice is being manually keyed at the

returns setup. Sometimes the error is caused by a keying mistake and

sometimes the documentation (call tag, invoice, packing list) is not

legible.

We also know that External Vendor cannot correct and resend the

return. Their process not only creates the return for credit, but

also has to account for all of the inventory that is being sent for

destruction. Their quality steps lock the return down once it has been

sent to client for credit. Their system will not permit the return to

be corrected and resent.

We do, however, need to find a solution for the correction of these

failed returns that allows us to account for the return and create the

proper credit.

Returns (Order To Cash) team require ability to Edit the payload of

Asynchronous ABAP proxy messages in SAP ECC system, which are failed

due to Incorrect data with Message Status as "Application Error -

Manual Restart Possible".

For this the proposed solution is to Edit the Payload via SAP

XI's "Message Editor" in Runtime Work Bench -> Message Monitoring ->

Proxy Runtime of SAP ECC system.

The message editor is configured in SAP XI and ECC system with the

required roles and SAP Correction Notes.

Message Editor is NOT Working for messages with "Application Error -

Manual Restart Possible" status, while it is working as expected for

messages with "System Error - Manual Restart Possible" status.

Below Error Message is seen, while trying to edit the message with

Application Error in SAP ECC,

" Message editor can only be used for executable, asynchronous XI

messages with errors"

This issue in SAP XI's Message Editor needs to be resolved to complete

the testing of proposed solution in Sandbox systems and make a decision

on the solution to be used for this business requirement.

[Former Member]

Raised OSS Note - Thanks All for your inputs

[Former Member]

Just an update - We found a workaround for editing the failed ECC proxy messages in RWB message editor. Thanks

[Former Member]

can you share your workaround with all the friends here ?

Regards.

Liang

[Former Member]

Hi,

By selecting the Proxyruntime for the ECC system under Message Monitoring -> Messages from component dropdown list, we will be able to see the messages from the ECC system. If we have the proper roles assigned to the user account and by applying these following notes

Note 1160974 - RWB: No authorization to start Message Editor

Note 1154368 - Editing messages or payload on sender or receiver

We should be able to edit ECC messages in Message editor of RWB.

But again there was issue, it is allowing only to edit "System Error" status messages and not the "Application Errors". If we try to edit the application error message am getting the following error messages

*Message editor can only be used for executable, asynchronous XI messages with errors*

Note : Am trying to edit only the asynchronous messages

Any ideas/thoughts on this.

Thanks in Advance

Ashok

[prateek]

No such option in sxmb_moni. Its possible only though RWB.

Regards,

Prateek