Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Infoset query - internal error when generating code

Former Member
0 Kudos
929

Hi,

We have created some custom fields in table PA0077. I have added those fields to an infoset. I can report on the new fields and their contents appears in the output (they are fields with text table relationship). But when wanting to use these  as a selection field and either press hit list or output then I get this error:

Internal error when generating code. "." expected after "PA0077-ZZ_PARENTS_UNIVERSI".

Message No. PAIS100

The full field name PA0077-PARENTS_UNIVERSITY_DEGREE though.

Is it possible that the field name defined for in the table PA0077 is too long to be used in infoset query for selecting by that field?  The infoset generates fine though, and gives now warnings?

So I'm thinking if SE11 allows a field name with a certain length it should be allowable in SAP infoset query also, especially if the activation or checking the infoset doesn't give any error.

Thanks in advance for helpful advice.

Regards,

Philipp

1 ACCEPTED SOLUTION

keith_doyle
Advisor
Advisor
0 Kudos
290

Hello Philipp,

Unfortunately, your field name too long for the object selection in InfoSet Query.

The data retrieval is dynamically generated at runtime, depending on the field you have selected for the selection.

This can be done, however only a restricted line length is available.

The long field name is a part of the generated lines and it is truncated to errors.

To avoid the error to your field names must be reduced to 23 characters.

Regards,

Keith

4 REPLIES 4

Former Member
0 Kudos
290

P.S. we have OSS note 2108528 applied to our system already

0 Kudos
290
  • If you are taking this field into the Selection screen from SQ01 then try to have it in Selection screen from SQ02 (Extra > Selections).
  • If it is the opposite case then try by having this field in Selection screen from SQ01 instead from SQ02.

0 Kudos
290

Hi Rao,

The issue is there whether I create a query from SQ01, or whether I do it from ad hoc query transaction code S_PH0_48000513.

Regards,

Philipp

keith_doyle
Advisor
Advisor
0 Kudos
291

Hello Philipp,

Unfortunately, your field name too long for the object selection in InfoSet Query.

The data retrieval is dynamically generated at runtime, depending on the field you have selected for the selection.

This can be done, however only a restricted line length is available.

The long field name is a part of the generated lines and it is truncated to errors.

To avoid the error to your field names must be reduced to 23 characters.

Regards,

Keith