special character in Idoc_aae sender

[rasjoshi]

HI all,

is there any adapter module which can be used for handling special character by idocAae sender side?

we dont have esr objects so can not make use of mapping here.

BR,

rashmi

[rasjoshi · Accepted solution]

Hi All,

Thank you for your support. This issue got resolved by applying note - 1872390

BR,

Rashmi

[maheswarareddykonda]

Hi Rashmi,

is there any adapter module which can be used for handling special character by idocAae sender side?

Mostly i don't think you have to use modules to achieve this.

have you seen this below blog Posted by Prateek Raj Srivastava

you just have to do editing the RFC destination at R/3 from non-unicode to unicode.

that blog explain mostly JDBC side to handle..but please check first half of the blog.

BR,

Maheswarareddy

[rasjoshi]

Hi Maheswarareddy,

We already have UNICODE selected in rfc destination. In addition we dont have any ESR objects...

BR,

Rashmi

[azharshaikh]

Hi Rashmi,

Since the IDOC fails at SM58 in Sender system itself, can you check the error and request the Sender to trigger data in correct format.

Regards,

Azhar

[rasjoshi]

Yes Azhar, after discussing with sender team we came to know idocs are containing some special characters like �M etc....

Below is error what we get in SM58 -

BR,

Rashmi

[pvishnuvardan_reddy]

Hi Rashmi,

The error log from sm58 is a generic one which implies there might be n number of reasons for the failure.

Can you check the logs in PI system by navigating to NWA-->TroubleShooting-->Logs and Traces-->Log viewer

Filter for the errors category and check at the IDOC triggered time.

[rasjoshi]

Hi Vishnu,

PFB log -

[pvishnuvardan_reddy]

Hi Rashmi,

Besides this error, can you check for other errors above and below this one in the log viewer.

[rasjoshi]

Hi Vishnu,

Log above -

Log Below -

BR,

Rashmi

[pvishnuvardan_reddy]

Hi Rashmi,

The issue here is with the interface determination step as the error log is talking about the same.

Can you check whether for the failed IDOC is yielding any interface at the interface determination step of the ICO or not.

[rasjoshi]

Hi Vishnu,

I checked one of the stuck idoc from SM58, it fulfils the condition which we have set in ICO.

Please suggest what else can be issue here?

BR,

Rashmi

[pvishnuvardan_reddy]

Hi Rashmi,

Did you check the failed one in the queue.

Due to this, other IDOC's might have been struck in the queue.

I am not completely sure to say that the issue here is with the special characters since the log is saying issue with the interface determination step.

Please cross check the ID configuration done in PI system for processing of the IDOC.

Please share some screenshots to explore more on this issue.

[rasjoshi]

Hi Vishnu,

This is Prod issue. This issue is occurring frequently now. Suppose there are 200 idocs then only 100 are getting processed and 100 are getting stuck in SM58. ICO is correct... XPATH condition is also getting fulfilled here...We started getting this issue after upgrade of ECC system to SP11.

BR,

Rashmi

[pvishnuvardan_reddy]

Hi Rashmi,

Is this issue occuring for a particular IDOC interface or for all the IDOC related outbound interfaces?

Also, let us know your ECC and PI system version details.

PFB snotes about upgrade issues FAQ:

Upgrade to SAP ECC EhP6 - Known issues - ERP Upgrade - SCN Wiki

Note 1942289:Known issues with PI and ECC EHP upgrades

[rasjoshi]

Yes this is happening for only one particular interface(IDOC_AAE to PI).

PI -- 7.31 SP 08 Single stack

ECC - EHP 6

BR,

Rashmi

[rasjoshi]

Hi,

The flow is like this -

ECC(IODC_AAE) --> PI --> JMS

As some special characters are appearing in IDoc these are getting stuck in SM58. IDOC_AAE is not picking these idocs... So we need to handle this in PI... I checked in SM59 of ECC system... There UNICODE is selected.....

Please let me know if

this blog is helpful in case of IDOC_AAE sender??

P.S. We dont have any ESR objects here.

BR,

Rashmi

[pvishnuvardan_reddy]

Hi Rashmi,

Yes, we will use module beans for this requirement to handle in PI. So I guess it will generic independent of the adapter which we are using.

Can you try and check the outcome.

Let us know if you get struck anywhere.

[stefan_grube]

As some special characters are appearing in IDoc these are getting stuck in SM58. IDOC_AAE is not picking these idocs... So we need to handle this in PI... 

How could you hande it within PI when the messages stuck in SM58?

What exactly are the "special characters"?

[pvishnuvardan_reddy]

Hi Rashmi,

Could you be more specific about the query.

If you are talking about encoding handling in PI, yes we can do it and you can refer the links provided by Azhar.

[azharshaikh]

Hi Rashmi,

AFAIK - Unicode will support most of the chars / languages. Is the sender R/3 sending in Unicode format (enabled) , if yes then PI should be able to process those (UTF-8) by default.

Incase you need to change the Encoding pls check following for further info:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0ff71ca-1d11-2a10-6a93-88662a6e7...

Hope it helps

Regards,

Azhar