topic Incorrect Nesting, before the statement ENDFUNCTION in Application Development and Automation Discussions

Incorrect Nesting, before the statement ENDFUNCTION

Former Member — Thu, 23 Feb 2006 23:04:24 GMT

Hello:

I have this simple ABAP program, but I don't seem to make it work:

FUNCTION Z_SAP_GET_CREDIT.

*"----

""Interfase local

*" IMPORTING

*" VALUE(CLIENT_ID) TYPE Z_CLIENT_ID OPTIONAL

*" EXPORTING

*" VALUE(CREDIT_LIMIT) TYPE STRING

*" VALUE(CONDITIONS) TYPE STRING

*" EXCEPTIONS

*" USER_DOES_NOT_EXIST

*"----

TYPES: BEGIN OF credit_eq_type,

WEBTR TYPE string,

ZTERM TYPE int4,

END OF credit_eq_type .

DATA: credit_eq TYPE credit_eq_type.

SELECT SINGLE *

FROM KNB1

INTO CORRESPONDING FIELDS OF credit_eq

WHERE KUNNR = CLIENT_ID.

*CREDIT_LIMIT = credit_eq-WEBTR.

ENDFUNCTION

I get this error:

Incorrect Nesting, before the statement "ENDFUNCTION", the structure introduced by SELECT must conclude with "END SELECT"

I've done selects before and it wasn't needed.... what is this?

Thanks

Alex

Re: Incorrect Nesting, before the statement ENDFUNCTION

former_member186741 — Thu, 23 Feb 2006 23:14:11 GMT

THIS LOOKS OK, THE ONLY THING i CAN THINK OF IS THAT YOU HAVE ANOTHER FUNCTION MODULE IN THE SAME FUNCTION GROUP WHCIH HAS THE ERROR.

Re: Incorrect Nesting, before the statement ENDFUNCTION

Former Member — Thu, 23 Feb 2006 23:23:20 GMT

Actually, I don't know why, but I placed two definitions on the DATA section and it did compile and activated... however it won't work, it shows an error:

"One of the statements could no be executed. Following a SELECT statement, the data READ could not be placed in AN output area"

I know it's a matter of a conversion. probably due to incompatibility from the WEBTR field on KBN1 (seems to be on currency) into String... which datatype should be suitable?

Thanks Alex

Re: Incorrect Nesting, before the statement ENDFUNCTION

former_member186741 — Fri, 24 Feb 2006 00:12:06 GMT

use:

WEBTR TYPE webtr,

ZTERM TYPE dzterm,

Re: Incorrect Nesting, before the statement ENDFUNCTION

Former Member — Fri, 24 Feb 2006 05:20:48 GMT

Even though you are specifying SELECT SINGLE * in your code, you are not providing the full key of KNB1 which also includes company code BUKRS. So system expects either a ENDSELECT or your INTO statement to be followed by TABLE itab instead of just INTO strcuture. That is why you got this error. So either do option 1 or 2 as follows.

Option 1


TYPES: BEGIN OF credit_eq_type,
         WEBTR LIKE KNB1-WEBTR,
         ZTERM LIKE KNB1-ZTERM,
       END OF credit_eq_type .

DATA: credit_eq TYPE TABLE OF credit_eq_type with header line.

SELECT SINGLE webtr zterm FROM KNB1
                          INTO TABLE credit_eq
                         WHERE KUNNR = CLIENT_ID.

*CREDIT_LIMIT = credit_eq-WEBTR.

Option 2


TYPES: BEGIN OF credit_eq_type,
         WEBTR LIKE KNB1-WEBTR,
         ZTERM LIKE KNB1-ZTERM,
       END OF credit_eq_type .

DATA: credit_eq TYPE credit_eq_type.

SELECT webtr zterm FROM KNB1 UP TO 1 ROWS
                   INTO credit_eq
                  WHERE KUNNR = CLIENT_ID.
ENDSELECT.
*CREDIT_LIMIT = credit_eq-WEBTR.

Option 3


TYPES: BEGIN OF credit_eq_type,
         WEBTR LIKE KNB1-WEBTR,
         ZTERM LIKE KNB1-ZTERM,
       END OF credit_eq_type .

DATA: credit_eq TYPE credit_eq_type.

SELECT SINGLE webtr zterm FROM KNB1
                          INTO Credit_eq
                         WHERE KUNNR = CLIENT_ID
                           AND BUKRS = <either constant 
or another import parameter from the function module>.

*CREDIT_LIMIT = credit_eq-WEBTR.

3rd option is the best one if you have BUKRS. In the case where you don't have BUKRS, use the option 1. Option 2 is least efficient. But in any case, please do not use SELECT * with INTO CORRESPONDING FIELDS when you need only two fields. Instead specify the fields AND yes you cannot use INTO with incompatable fields. They have to be compatible.

Srinivas

Message was edited by: Srinivas Adavi

Re: Incorrect Nesting, before the statement ENDFUNCTION

hymavathi_oruganti — Fri, 24 Feb 2006 05:32:38 GMT

SELECT SINGLE *

FROM KNB1

INTO CORRESPONDING FIELDS OF credit_eqWHERE KUNNR = CLIENT_ID.

IN THE ABOVE STATEMENT, IF CREDIT_EQ IS A TABLE, U NEED TO GIVE OF TABLE

LIKE BELOW

SELECT SINGLE *

FROM KNB1

INTO CORRESPONDING FIELDS OF TABLE credit_eq

WHERE KUNNR = CLIENT_ID.

IF ITS IS WORK AREA, U NEED TO GIVE END SELECT. LIKE BELOW

SELECT SINGLE *

FROM KNB1

INTO CORRESPONDING FIELDS OF credit_eq

WHERE KUNNR = CLIENT_ID.

END SELECT.

Re: Incorrect Nesting, before the statement ENDFUNCTION

jayanthi_jayaraman — Fri, 24 Feb 2006 05:42:06 GMT

Hi,

For declaration,just try this.

TYPES: BEGIN OF credit_eq_type,

WEBTR TYPE knb1-webtr,

ZTERM TYPE knb1-zterm,

END OF credit_eq_type .

In export parameters also,change the type

credit_limit type knb1-webtr

Re: Incorrect Nesting, before the statement ENDFUNCTION

former_member186741 — Fri, 24 Feb 2006 05:49:53 GMT

Srinivas and Hymavathi,

Select single NEVER needs an ENDSELECT.

Re: Incorrect Nesting, before the statement ENDFUNCTION

hymavathi_oruganti — Fri, 24 Feb 2006 05:53:01 GMT

yes niel u r right, sorry i was little confused

Re: Incorrect Nesting, before the statement ENDFUNCTION

Former Member — Fri, 24 Feb 2006 15:20:29 GMT

Hello:

This is my final code, with no syntax errors:

FUNCTION Z_SAP_GET_CREDIT.

*"----

""Interfase local

*" IMPORTING

*" VALUE(CLIENT_ID) TYPE Z_CLIENT_ID OPTIONAL

*" EXPORTING

*" VALUE(CREDIT_LIMIT) TYPE KNB1-WEBTR

*" VALUE(CONDITIONS) TYPE KNB1-ZTERM

*" EXCEPTIONS

*" USER_DOES_NOT_EXIST

*"----

TYPES: BEGIN OF credit_eq_type,

WEBTR LIKE KNB1-WEBTR,

ZTERM LIKE KNB1-ZTERM,

END OF credit_eq_type .

DATA: credit_eq TYPE credit_eq_type.

CONSTANTS BU LIKE KNB1-BUKRS value 'FSMX'.

SELECT SINGLE WEBTR ZTERM

FROM KNB1

INTO credit_eq

WHERE KUNNR = CLIENT_ID.

CREDIT_LIMIT = credit_eq-WEBTR.

CONDITIONS = credit_eq-ZTERM.

ENDFUNCTION.

It does compile, however, when I execute it, it returns me 0.00 for CREDIT_LIMIT and Nothing for CONDITIONS. I check out the table and there is data for that client, any ideas?

Thanks

Re: Incorrect Nesting, before the statement ENDFUNCTION

RichHeilman — Fri, 24 Feb 2006 15:26:54 GMT

Are you sure that you are handling the internal format?

Make sure that CLIENT_ID contains data that is zero filled left. Like '0000012345'.

You can handle this in the function module if you want.

Add the following function module.



TYPES: BEGIN OF credit_eq_type,
WEBTR LIKE KNB1-WEBTR,
ZTERM LIKE KNB1-ZTERM,
END OF credit_eq_type .

DATA: credit_eq TYPE credit_eq_type.

CONSTANTS BU LIKE KNB1-BUKRS value 'FSMX'.

<b>call function 'CONVERSION_EXIT_ALPHA_INPUT'
  exporting
    input         = CLIENT_ID
 IMPORTING
   OUTPUT        = CLIENT_ID.</b>

SELECT SINGLE WEBTR ZTERM
FROM KNB1
INTO credit_eq
WHERE KUNNR = CLIENT_ID.

REgard,

Rich Heilman

Re: Incorrect Nesting, before the statement ENDFUNCTION

RichHeilman — Fri, 24 Feb 2006 15:28:08 GMT

How is Z_CLIENT_ID Typed? You may be able to handle this if Z_CLIENT_ID is typed correctly. I hope that it is at least a 10 character field. Otherwise, the funciton module will work for you.

Re: Incorrect Nesting, before the statement ENDFUNCTION

Former Member — Fri, 24 Feb 2006 15:30:31 GMT

Hi,

Put a break point in the FM,& see whether the data is populating from your select statement.

Re: Incorrect Nesting, before the statement ENDFUNCTION

Former Member — Fri, 24 Feb 2006 15:36:26 GMT

Z_CLIENT_ID is an INT4 with length 10. I placed the code you suggested:

call function 'CONVERSION_EXIT_ALPHA_INPUT'

exporting

input = CLIENT_ID

IMPORTING

OUTPUT = CLIENT_ID.

And I get this runtime error: OBJECTS NOT_CHAR_LIKE

Re: Incorrect Nesting, before the statement ENDFUNCTION

Former Member — Fri, 24 Feb 2006 15:39:35 GMT

Hi,

Can you move the valur into a char variable & use FM 'CONVERSION_EXIT_ALPHA_INPUT' ,& then pass it to your select.

Re: Incorrect Nesting, before the statement ENDFUNCTION

Former Member — Fri, 24 Feb 2006 15:42:36 GMT

Hi ,

Please define Z_CLIENT_Id as Charcter type. Then your code will work.

Regards,

lanka

Re: Incorrect Nesting, before the statement ENDFUNCTION

Former Member — Fri, 24 Feb 2006 15:45:52 GMT

Excelent.... working good.

Thanks

Re: Incorrect Nesting, before the statement ENDFUNCTION

Former Member — Fri, 24 Feb 2006 15:50:01 GMT

You have made client_id optional. I don't think it should be. Are you sure you passed a valid value to it? Are you getting an exception?

Rob

Re: Incorrect Nesting, before the statement ENDFUNCTION

Former Member — Fri, 24 Feb 2006 15:51:28 GMT

optional yes, however, I tried non-optional and it wouldn't work =(. Since it's working now, I believe I'll leave it that way, thaks Rob!