cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Dynamic Transaction Calls 12.2

Former Member
0 Kudos
182

Hi

When calling a Dynamic transaction I keep getting the same error:

[ERROR] Could not perform type conversion for Dynamic_Transaction_Call_0.Inputs

.Inputs is a boolean, but I get the error no matter if I set it to true or false. I have tried to look up the logic piece in the MII 12.2 help, but the property is not documented:

http://help.sap.com/saphelp_mii122/helpdata/en/46/1a97835ac74f07e10000000a114a6b/frameset.htm ?

In 12.1 the property doesn't exist.

Anyone able to help me?

/Simon

Accepted Solutions (1)

Accepted Solutions (1)

agentry_src
Active Contributor
0 Kudos

Hi Simon,

What version and build of 12.2 are you using?

Regards,

Mike

Former Member
0 Kudos

12.2.2 Build(212)

agentry_src
Active Contributor
0 Kudos

Hi Simon,

I get the same error. Please open a ticket.

Thanks,

Mike

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Michel,

Instead of Dynamic_Transaction_Call use the Transaction Call Action block and try it.

agentry_src
Active Contributor
0 Kudos

Hi Michel (and Partheeban),

In the testing that Simon and I did, we determined that it was an invalid error message rather than any actual failure of the action block.  So while it is probably worth reporting as a bug with Low priority, it does not affect the actual operation of the action block or transaction.  So neither of us felt it was worth spending a lot of time trying to address. 

Please check your error message and make sure it is the bug and not the execution of the dynamic call.

Regards, Mike

jamie_cawley
Product and Topic Expert
Product and Topic Expert
0 Kudos

Try using a different name for your property, Inputs is probably a "reserved" one.

Jamie

agentry_src
Active Contributor
0 Kudos

Jamie,

It is a predefined action block property in 12.2.

SImon,

It looks like the transactions still execute properly. Is that the behavior you are seeing also?

Regards,

Mike

Edited by: Michael Appleby on May 5, 2011 4:50 PM

Former Member
0 Kudos

Yes it seems like the transaction call is working yes. And even the .success output on the transaction call seems to be working...

So it is actually only a very minor issue when running the schedule in the workbench.

Edited by: Simon Bruun on May 24, 2011 12:14 PM

Former Member
0 Kudos

I am facing the same error.

Did you solve that ?

Former Member
0 Kudos

Simon Bruun, please did you solve this error ?