Empty TOC KindleGen/ ePub Incorrect nesting level error

Neither is a question but hopefully a solution for anyone who has been going through hell (like me) trying to get a working TOC for mobi and ePub files.
I have INDD CS6, Kindle Plugin installed - but I think this also applies to earlier versions of Indd
For Mobi (kindle) - If you got your TOC set via the Layout menu and still don't see the Table of Contents menu in Kindle Previewer- make sure to go to your PARAGRAPH STYLE - EXPORT TAGGING and UNCHECK!!! SPLIT DOCUMENTS (it even says there ePUB only). I also suggest you do it for all Paragraph styles you are using in your MOBI file. Kindle previewer no longer gave me an error and I can see both of my TOC's now - that said this took me several weekends and countless nervous breakdowns to figure out.....
For ePub incorrect nesting level - this happened to me due to the fact that I have used 2 levels for my TOC (some of you may use even 3 or 4)
To get rid of the error I had to edit the TOC style and change the levels for both my "included paragraph styles" (the ones you add to the left column) to LEVEL 1 - yes for BOTH. I say this again - SET ALL all included paragraph styles levels to digit 1 (ONE).
I think this is a serious bug Adobe really should fix asap - I truly wasted several weekends on this, pulled all my remaining hair out and had suicidal (and other very violent) thoughts ...
I hope this post will help all of you who is dealing with either of those problems....
Happy ePublishing everyone

Similar Messages

[svn:bz-4.0.0_fixes] 20451: backporting bug fix BLZ-570/ BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError We put hard limit to the max object nest level to prevent StackOverFlowError .

Revision: 20451
Revision: 20451
Author:   [email protected]
Date:     2011-02-24 08:33:31 -0800 (Thu, 24 Feb 2011)
Log Message:
backporting bug fix BLZ-570/BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError We put hard limit to the max object nest level to prevent StackOverFlowError. the default max object nest level is 1024 and it can be configured in the endpoint/serialziation section in service-config.xml. This needs documentation. Checkintests pass
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-570
    http://bugs.adobe.com/jira/browse/BLZ-620
Modified Paths:
    blazeds/branches/4.0.0_fixes/modules/common/src/flex/messaging/errors.properties
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/endpoints/AbstractEndpoint.j ava
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/SerializationContext.java
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/Amf0Input.java
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/Amf3Input.java
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/AmfIO.java

Dear Pallavi,
Very useful post!
I am looking for similar accelerators for
Software Inventory Accelerator
Hardware Inventory Accelerator
Interfaces Inventory
Customization Assessment Accelerator
Sizing Tool
Which helps us to come up with the relevant Bill of Matetials for every area mentioned above, and the ones which I dont know...
Request help on such accelerators... Any clues?
Any reply, help is highly appreciated.
Regards
Manish Madhav

[svn:bz-3.x] 20443: back porting bug fix BLZ-570/ BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError We put hard limit to the max object nest level to prevent StackOverFlowError .

Revision: 20443
Revision: 20443
Author:   [email protected]
Date:     2011-02-23 21:19:22 -0800 (Wed, 23 Feb 2011)
Log Message:
back porting bug fix BLZ-570/BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError We put hard limit to the max object nest level to prevent StackOverFlowError. the default max object nest level is 1024 and it can be configured in the endpoint/serialziation section in service-config.xml. This needs documentation. Checkintests pass
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-570
    http://bugs.adobe.com/jira/browse/BLZ-620
Modified Paths:
    blazeds/branches/3.x/modules/common/src/java/flex/messaging/errors.properties
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/endpoints/AbstractEndpoint.java
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/SerializationContext.java
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/amf/Amf0Input.java
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/amf/Amf3Input.java
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/amf/AmfIO.java

Smartform error: Incorrect nesting

Hi,
 I have been trying to use Spell_Amount in smartform. The code I have used is working fine in report but giving following error in smartform :
Incorrect nesting: Before statement "Form", the structure introduced by "Function" must be concluded with "Endfunction".
Code I have used is:
TABLES SPELL.
DATA : T_SPELL LIKE SPELL OCCURS 0 WITH HEADER LINE.
Data : S_WRBTR LIKE BSEG-WRBTR.
SY-TITLE = 'SPELLING NUMBER'.
PERFORM SPELL_AMOUNT USING s_wrbtr 'inr'.
FORM spell_amount USING s_wrbtr pwaers.
CALL FUNCTION 'SPELL_AMOUNT'
 EXPORTING
 amount = s_wrbtr
 currency = pwaers
 filler = space
 language = 'E'
 IMPORTING
 in_words = t_spell
 EXCEPTIONS
 not_found = 1
 too_large = 2
 OTHERS = 3.
endform.
Can I have some help?
Thnx

Try the following code:
it worked for me.
In Global Definitions --> Global Data Define:
WORDS type Spell
wt_total type tablename-fieldname " wt_total is the field you want in words.
Create a Window Words and place it after you have the value of wt_total.
In Window Words:
Rt. Click--> Create --> flow Logic --> Program Lines
Output Parameters --> wt_total,
 Words.
call function 'SPELL_AMOUNT'
exporting
 amount = wt_total
* CURRENCY = ' '
* FILLER = ' '
* LANGUAGE = SY-LANGU
importing
 in_words = words
* EXCEPTIONS
* NOT_FOUND = 1
* TOO_LARGE = 2
* OTHERS = 3
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
3. Create a text and put value
&Words-word& in it.
Let me know if it worked...
<removed by moderator>
Edited by: Thomas Zloch on Feb 17, 2012

[BlazeDS]Error serialization exceeds the max collection object nest level of '15'.

I am getting the following error when I try to import large data from server to client. I am not able to find where I can change the settings to handle more data.
[BlazeDS]Error serialization exceeds the max collection object nest level of '15'.
flex.messaging.io.SerializationException: Error serialization exceeds the max collection object nest level of '15'.
        at flex.messaging.io.amf.AmfIO.increaseNestCollectionLevel(AmfIO.java:142)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:753)
        at flex.messaging.io.amf.Amf3Input.readArray(Amf3Input.java:358)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:156)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.ArrayCollection.readExternal(ArrayCollection.java:87)
        at flex.messaging.io.amf.Amf3Input.readExternalizable(Amf3Input.java:493)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:420)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:439)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:453)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readArray(Amf3Input.java:358)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:156)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.ArrayCollection.readExternal(ArrayCollection.java:87)
        at flex.messaging.io.amf.Amf3Input.readExternalizable(Amf3Input.java:493)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:420)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:439)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:453)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readArray(Amf3Input.java:358)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:156)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.ArrayCollection.readExternal(ArrayCollection.java:87)
        at flex.messaging.io.amf.Amf3Input.readExternalizable(Amf3Input.java:493)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:420)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)

I am getting the following error when I try to import large data from server to client. I am not able to find where I can change the settings to handle more data.
[BlazeDS]Error serialization exceeds the max collection object nest level of '15'.
flex.messaging.io.SerializationException: Error serialization exceeds the max collection object nest level of '15'.
        at flex.messaging.io.amf.AmfIO.increaseNestCollectionLevel(AmfIO.java:142)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:753)
        at flex.messaging.io.amf.Amf3Input.readArray(Amf3Input.java:358)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:156)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.ArrayCollection.readExternal(ArrayCollection.java:87)
        at flex.messaging.io.amf.Amf3Input.readExternalizable(Amf3Input.java:493)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:420)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:439)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:453)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readArray(Amf3Input.java:358)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:156)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.ArrayCollection.readExternal(ArrayCollection.java:87)
        at flex.messaging.io.amf.Amf3Input.readExternalizable(Amf3Input.java:493)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:420)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:439)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:453)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)
        at flex.messaging.io.amf.Amf3Input.readArray(Amf3Input.java:358)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:156)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.ArrayCollection.readExternal(ArrayCollection.java:87)
        at flex.messaging.io.amf.Amf3Input.readExternalizable(Amf3Input.java:493)
        at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:420)
        at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:152)
        at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:130)
        at flex.messaging.io.amf.Amf3Input.readObjectOneLevelDown(Amf3Input.java:754)

Incorrect nesting error in user exit include

Hi,
In one of my requirement I had to add an additional screen using EXIT_SAPMM06E_016, this Function module exists in XM06 Function group, this exit holds an include ZXM06U41.
This function group holds screens, so when I implement a screen and create the PBO module in this particular include, it by default includes
MODULE STATUS_XXX OUTPUT.
ENDMODULE.
When i check this include it says:
Incorrect nesting: Before the statement "MODULE", the structure introduced by "FUNCTION" must be concluded with "ENDFUNCTION".
I have no clue where the open function is?
Your help will be very much appreciated.
Please help.
Thanks,
-Sandeep

You cannot define a screen module in a function module code.
Refer to available documentation how to properly implement enhancements of this kind. Enhancement name is MM06E005 (in SMOD). Screen definitions and the corresponding modules will happen in function group XM06, not in the exit function module.
Edit: To elaborate, your PBO module will go into include ZXM06ZZZ, or better yet, into new include ZXM06O01 which should be part of ZXM06ZZZ (just to keep the usual naming convention).
Edited by: Tamas Hoznek on Feb 28, 2012 2:51 PM

[svn:bz-trunk] 20609: Change the default max object nest level from 1024 to 512.

Revision: 20609
Revision: 20609
Author:   [email protected]
Date:     2011-03-04 10:23:41 -0800 (Fri, 04 Mar 2011)
Log Message:
Change the default max object nest level from 1024 to 512. A max object nest level of 512 should be more than enough for most applications which probably will not be sending deeply nested object graphs over the wire. For applications that are sending deeply nested object graphs over the wire and that bump up against this limit, the limit can be increased but you should also do testing to make sure that serializing/deserializing these deeply nested object graphs doesn't cause stack overflow errors.
Update documentation for the max object nest level setting to reflect the new default.
Add documentation for the new max collection nest level setting.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/endpoints/AbstractEndpoint.java
    blazeds/trunk/resources/config/services-config.xml

You should be able to get some more precise information from your Xorg logs, but I would bet it is related to the evdev driver. Some of the options in your xorg.conf no longer work with the latest version. For now you should be able to either map your mouse directly to the appropriate /dev/event* entry or change to the standard mouse driver, both of those methods should be in the wiki.
You are supposed to be able to use the evdev driver without the input section of your xorg.conf by using dbus/hal autodetection, but AFAIK at the moment the xorg-server package still isn't compiled with hal support, so you would have to patch and rebuild the package.

Incorrect nesting in smartfroms program-line

Hi .
when i have use code in different program it's work fine .
but when same code use in smartforms program-lines it's give me following error.
Incorrect nesting: Before the statement "FORM", the structure introduced by "FUNCTION" must be concluded by "ENDFUNCTION" . . .
Regards.
Sam.

HI
My code
DATA mwsbp TYPE komp-mwsbp .
data : p_ebeln TYPE ekpo-ebeln ,
p_ebelp TYPE ekpo-ebelp .
*data: p_mwsbp TYPE komp-mwsbp .
PERFORM calculate_tax USING p_ebeln p_ebelp CHANGING mwsbp .
FORM calculate_tax USING p_ebeln TYPE ekpo-ebeln
p_ebelp TYPE ekpo-ebelp
CHANGING p_mwsbp TYPE komp-mwsbp .
CONSTANTS: bstyp_info VALUE 'I',
bstyp_ordr VALUE 'W',
bstyp_banf VALUE 'B',
bstyp_best VALUE 'F',
bstyp_anfr VALUE 'A',
bstyp_kont VALUE 'K',
bstyp_lfpl VALUE 'L',
bstyp_lerf VALUE 'Q'.
DATA : taxcom TYPE taxcom ,
t_konv TYPE TABLE OF komv WITH HEADER LINE .
DATA: BEGIN OF tkomv OCCURS 50.
INCLUDE STRUCTURE komv.
DATA: END OF tkomv.
DATA: BEGIN OF tkomvd OCCURS 50. "Belegkonditionen
INCLUDE STRUCTURE komvd.
DATA: END OF tkomvd.
DATA : BEGIN OF tkomvh OCCURS 50.
INCLUDE STRUCTURE komv.
DATA : vtext LIKE t685t-vtext.
DATA : END OF tkomvh.
SELECT SINGLE *
INTO ekko
FROM ekko
WHERE ebeln = p_ebeln .
SELECT SINGLE *
INTO ekpo
FROM ekpo
WHERE ebeln = p_ebeln
AND ebelp = p_ebelp .
SELECT SINGLE *
INTO t001
FROM t001
WHERE bukrs = ekko-bukrs .
taxcom-bukrs = ekpo-bukrs.
taxcom-budat = ekko-bedat.
taxcom-waers = ekko-waers.
taxcom-kposn = ekpo-ebelp.
taxcom-mwskz = ekpo-mwskz.
taxcom-txjcd = ekpo-txjcd.
taxcom-shkzg = 'H'.
taxcom-xmwst = 'X'.
IF ekko-bstyp EQ bstyp_best.
taxcom-wrbtr = ekpo-netwr.
ELSE.
taxcom-wrbtr = ekpo-zwert.
ENDIF.
taxcom-lifnr = ekko-lifnr.
taxcom-land1 = ekko-lands.
taxcom-ekorg = ekko-ekorg.
taxcom-hwaer = t001-waers.
taxcom-llief = ekko-llief.
taxcom-bldat = ekko-bedat.
taxcom-matnr = ekpo-ematn.
taxcom-werks = ekpo-werks.
taxcom-bwtar = ekpo-bwtar.
taxcom-matkl = ekpo-matkl.
taxcom-meins = ekpo-meins.
IF ekko-bstyp EQ bstyp_best.
taxcom-mglme = ekpo-menge.
ELSE.
IF ekko-bstyp EQ bstyp_kont AND ekpo-abmng GT 0.
taxcom-mglme = ekpo-abmng.
ELSE.
taxcom-mglme = ekpo-ktmng.
ENDIF.
ENDIF.
IF taxcom-mglme EQ 0.
taxcom-mglme = 1000.
ENDIF.
taxcom-mtart = ekpo-mtart.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
CALL FUNCTION 'J_1BSA_COMPONENT_ACTIVE'
EXPORTING
bukrs = ekko-bukrs
component = 'BR'
EXCEPTIONS
component_not_active = 1
OTHERS = 2.
*endfunction.
IF sy-subrc IS INITIAL.
komk-mandt = ekko-mandt.
komk-kalsm = ekko-kalsm.
IF ekko-kalsm = ''.
komk-kalsm = 'RM0000'.
ENDIF.
komk-kappl = 'M'.
komk-waerk = ekko-waers.
komk-knumv = ekko-knumv.
komk-lifnr = ekko-lifnr.
komp-kposn = ekpo-ebelp.
komp-matnr = ekpo-matnr.
komp-werks = ekpo-werks.
komp-matkl = ekpo-matkl.
komp-infnr = ekpo-infnr.
komp-evrtn = ekpo-konnr.
komp-evrtp = ekpo-ktpnr.
CALL FUNCTION 'RV_PRICE_PRINT_ITEM'
EXPORTING
comm_head_i = komk
comm_item_i = komp
language = 'E'
TABLES
tkomv = tkomv
tkomvd = tkomvd.
CALL FUNCTION 'J_1B_NF_PO_DISCOUNTS'
EXPORTING
i_kalsm = ekko-kalsm
i_ekpo = ekpo
IMPORTING
e_ekpo = ekpo
TABLES
i_konv = t_konv.
IF NOT ekko-llief IS INITIAL.
taxcom-lifnr = ekko-llief.
ENDIF.
ENDIF.
CALL FUNCTION 'FIND_TAX_SPREADSHEET'
EXPORTING
buchungskreis = t001-bukrs
EXCEPTIONS
not_found = 1
OTHERS = 2.
CALL FUNCTION 'CALCULATE_TAX_ITEM'
EXPORTING
i_taxcom = taxcom
IMPORTING
e_taxcom = taxcom
EXCEPTIONS
mwskz_not_defined = 1
mwskz_not_found = 2
mwskz_not_valid = 3
steuerbetrag_falsch = 4
country_not_found = 5
OTHERS = 6.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
p_mwsbp = taxcom-wmwst .
WRITE:/ mwsbp .
ENDFORM. " calculate_tax
Regard
Sam

Incorrect Nesting, before the statement ENDFUNCTION

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

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

[svn:bz-3.x] 20876: Change default max object nest level to 512.

Revision: 20876
Revision: 20876
Author:   [email protected]
Date:     2011-03-16 09:02:36 -0700 (Wed, 16 Mar 2011)
Log Message:
Change default max object nest level to 512. A max object nest level of 512 should be more than enough for most applications which probably will not be sending deeply nested object graphs over the wire. For applications that are sending deeply nested object graphs over the wire and that bump up against this limit, the limit can be increased but you should also do testing to make sure that serializing/deserializing these deeply nested object graphs doesn't cause stack overflow errors.
Add documentation for the max object nest level setting.
Add documentation for the max collection nest level setting.
Checkintests: passed
Modified Paths:
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/endpoints/AbstractEndpoint.java
    blazeds/branches/3.x/resources/config/services-config.xml

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

[svn:bz-4.0.0_fixes] 20874: Change default max object nest level to 512.

Revision: 20874
Revision: 20874
Author:   [email protected]
Date:     2011-03-16 06:55:37 -0700 (Wed, 16 Mar 2011)
Log Message:
Change default max object nest level to 512. A max object nest level of 512 should be more than enough for most applications which probably will not be sending deeply nested object graphs over the wire. For applications that are sending deeply nested object graphs over the wire and that bump up against this limit, the limit can be increased but you should also do testing to make sure that serializing/deserializing these deeply nested object graphs doesn't cause stack overflow errors.
Add documentation for the max object nest level setting.
Add documentation for the max collection nest level setting.
Remove max-string-length-bytes setting from the example services-config.xml as this setting doesn't exist.
Checkintests: passed
Modified Paths:
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/endpoints/AbstractEndpoint.j ava
    blazeds/branches/4.0.0_fixes/resources/config/services-config.xml

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

View nesting level exceeded (limit 32)

Hi,
I have just added an additional level in my main hierarchy and on processing the AccountL dimension I get the below error:
- Error while update members of multiple hierarchy of AccountL
- Maximum stored procedure, function, trigger, or view nesting level exceeded (limit32)
I counted the level that I am inserted and it is only 7, is it possible that my alternate hierarchy levels are added to the main hierarchy levels? I have not included another level on any of the other hierarchies - only my first one.
Kind Regards,
Fiona

Hi,
I have seen a similar issue before. In order to find where are these errors and correct them I suggest
you to validate and process the three hierarchies one by one, putting each hierachy as the first one by renaming the PARENTHx column header. In this way, when all the hierarchies can be validated stand-alone, then you can validate them together. a possible error can be: have the name of memebers same as the name of father.
You can also try to delete the last member you added and reprocess, just to understand if the error is related to this new member or to something else.
Hope this can help you,
Mihaela

Max nested levels reached on object sent with RemoteObject

Hello:
We have an application that uses RemoteObject connections (with AMFPHP) to send an custom class object to PHP. This object has multiple depth levels, with nested objects inside the main one. We noticed that once a particular level is reached, the RemoteObject serialization crashes throwing this error:
TypeError: Error #1034: Type Coercion failed: cannot convert Object@7e30f89 en mx.messaging.messages.IMessage.
We tried to send a lighter object, with no properties, just the nested levels. The same occurs. In example:
var params:Object = {};
params['test'] = {0:{1:{2:{3:{4:{5:{6:{7:{8:{9:{10:{11:{12:{13:{14:{15:{16:{17:{18:{19:{20:{21:{22:{}}}}}}}}}}}}}}}}}}}}}}}};
remoteObject.runService(params);
If the object has less levels, it works:
params['test'] = {0:{1:{2:{3:{4:{5:{6:{7:{8:{9:{10:{11:{12:{13:{14:{15:{16:{17:{18:{19:{20:{21:{}}}}}}}}}}}}}}}}}}}}}}};
So it seems that the RemoteObject has a depth limit of 24 levels? Maybe 23, I´m not sure. Sending in JSON is not an option, as I lose all the typed classes and objects inside the main object.
Can anyone provide a good approach to face this problem??
Thanks in advance!

Solved: http://stackoverflow.com/questions/22936444/max-nested-levels-reached-on-object-sent-with- remoteobject

Ad hoc Risk Analysis report is returning incorrect Risk Level for some Risks

We are running GRC AC 10.0 with SP 16. After application of Support Pack 16, some of our ad hoc risk analysis reports are returning incorrect risk levels. For example: Risk F024 Open closed periods and inappropriately post currency or tax entries is set as High. When the Ad hoc report is run, the risk F024 will show on a user with a level of Medium. We have generated our ruleset and have followed the normal procedures used to implement the support pack. Any ideas what is causing this issue? I have exhausted my knowledge and search attempts.
Any help is appreciated.
Sara B.

Hi Kevin
Many thanks for your post, we did run a full BRA but no luck unfortunately. Some Risks still reporting as Medium when they should be Critical or High. Oddly it is reporting correctly against some risks just not for all!
Cheers
Hussain

"Multi-level error propagation carried out" in SCM 5.0

When I use the SNP PPM Generation With Lot Size Margin function in SCM 5.0, I got the following error:
Multi-level error propagation carried out
Message no. /SAPAPO/OM242
Could you please give me this help?
Thanks,
Lian

Hi,
Thank you for the information, but the problem is still there though I de-activated all user-exits...
I also saw the following error:
Invalid planning version
Message no. /SAPAPO/OM015
Thanks,
Lian

Empty TOC KindleGen/ ePub Incorrect nesting level error

Similar Messages

Maybe you are looking for