cancel
Showing results for 
Search instead for 
Did you mean: 

Add Row to XML document results in Conversion Exception after upgrade to SP07 in MII12.2

Former Member
0 Kudos

We are running an instance of MII 12.2 and have upgraded our development environment from SP6 to SP7. We also upgraded our netweaver 7.3 from SP11 to SP13.

I have a transaction that calls a standard SAP bapi via a JCo Interface action block. The bapi performs a standard confirmation reversal in SAP. The results of that bapi call are fed to a XML document via an AddRow action block. There is a string value configured in this xml document.

We have been using this transaction for several years. No after upgrading, we are getting an error message as the AddRow action block is populated, that a conversion exception has taken place.

The exact contents of the error are as follows:

  • [ERROR] Tried to set value for 'AddRowReturnError.Message', but couldn't. Exception: [Conversion Exception]
  • [ERROR] Error found trying to initialize action 'AddRowReturnError' Exception: [Conversion Exception]
  • [ERROR] [AddRowReturnError] Action: Runtime threw an exception. Exception: [com.sap.lhcommon.exceptions.DataConversionException: Conversion Exception]
  • [ERROR] Uncaught exception from AddRowReturnError, com.sap.lhcommon.exceptions.DataConversionException: Conversion Exception

My question is did something get deleted or overwrittin during our upgrade ?

I have not been able to find anything relating to this in any MII or Netweaver documentation.

Any input would be greatly appreciated.

Bob

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Bob,

Within your transaction sequence named AddRowReturnError you seem to have a variable named Message. In other words you are trying to add a row named message.

Try renaming it to something else like Message1 and see if it works.

Regards,

Anushree

Former Member
0 Kudos

Anushree,

That was the problem.  I renamed the row and it no longer throws an error.

Many thanks !!

Bob

Answers (1)

Answers (1)

Nikhil_Makhija
Participant
0 Kudos

Hi Bob,

In general this type of error comes, when you are trying to set the value for XML DOC Column (In your case it is BAPI message) in a Row Action block but that value is not available .i.e. If BLS action block is not able to found the reference of the assigned input.


Can you check if BAPI output message assigned to action block is valid or has not changed after upgrade ?

Example - If I assign a local variable to Row Action block whcih is msising or not defined   then it throws this kind of error.

Thanks