Error on an include provided by SAP

[Former Member]

Hi,

I added an INCLUDE statement to another include, and I am getting an error when I checked the syntax:

I<i>f the row type of 'C_T_DATA" and the type of <MCAFPA0BDSI> are not compatible at runtime, in future kernel releases, you must use addition "CASTING"</i>

The include statement has standard code provided by SAP, and I am hesitant to make any changes to the macro from this include that is causing the error. The include statement is placed in the user exit that is another include.

How would I go about in fixing this error? Should I go to SAP and have them fix it?

Thanks

Bitterness - Never be afraid to share your dreams with the world, because there's nothing the world loves more than the taste of really sweet dreams.

Don't go around saying the world owes you a living. The world owes you nothing. It was here first. ~Mark Twain

Message was edited by:

Ellen DeGeneres

[Former Member]

Hi,

I added an INCLUDE statement to another include, and I am getting an error when I checked the syntax:

I<i>f the row type of 'C_T_DATA" and the type of <MCAFPA0BDSI> are not compatible at runtime, in future kernel releases, you must use addition "CASTING"</i>

The include statement has standard code provided by SAP, and I am hesitant to make any changes to the macro from this include that is causing the error. The include statement is placed in the user exit that is another include.

How would I go about in fixing this error? Should I go to SAP and have them fix it?

Thanks

Bitterness - Never be afraid to share your dreams with the world, because there's nothing the world loves more than the taste of really sweet dreams.

Don't go around saying the world owes you a living. The world owes you nothing. It was here first. ~Mark Twain

Message was edited by:

Ellen DeGeneres

[RichHeilman]

Is this a hard error or a warning? If it is hard error and within an standard SAP program, then I would suggest opening an OSS note about it. Their code, their problem.

Regards,

Rich Heilman

[Former Member]

Hi Rich,

It's a yellow error, so would it be something on my side that I am causing this?

Thanks

<i>The price of anything is the amount of life you exchange for it</i>. ~Henry David Thoreau

[RichHeilman]

Not sure, make sure to check exactly where the warning is coming, if from the standard SAP code, then it is not you. You may be able to get away with just ignoring the message, but test thoroghly.

REgards,

Rich Heilman

[Former Member]

Hi Rich,

I tested it and I am not getting the data that I was expecting. Good to know.... I will place a message to SAP.

Thanks

<i>Don't forget Mother's Day. Or as they call it in Beverly Hills, Dad's Third Wife Day</i>. ~Jay Leno

[RichHeilman]

I think that is the best way to go. Good luck, last OSS note took 3 weeks for a resolution and then it really wasn't a resolution.

BTW, I like the quotes.

Regards,

Rich Heilman