Auto-numbering of list continues on to next list

Hi all, I have three defined lists in my document  (InCS4)...
1. bulleted multilevel
2. numbered multilevel
3. numbered (i, ii, iii) multilevel
The first two lists work fine.  The numbered (i, ii, iii) multilevel list seems to carry on upwards (iv, v, vi, etc...) on the next list a few paragraphs later.  I'm not understanding how it's possible that I am breaking out of a list (via a paragraph of text), and the next 'new' list resumes auto-incrementing from the last list.  I'd like to simply start a new list and have it auto-increment from the beginning... in this case 'i'......
Any help is appreciated. TIA

Check out the following link. I think you'll find your answer here.
http://blogs.adobe.com/indesigndocs/2009/04/numbered_lists_part_iv_numbere.html
Hope it helps!
Janine

Similar Messages

  • Change auto numbering in list options

    Is their a way to add a new auto numbering format to the list?  I need to add a decimal point and a zero to my numbered lists but can't figure out how to do it

    Hi
    create a separate NEW_LIST with only one column [CURRENT_ID]
    Next to your discussion board, add a workflow using SharePoint Designer, and attach to the post ( in a DB are existing 2 diff content types: post and messages ( replies ) ),and set it to start when a new post is addes
    Next in the workflow, extract value from NEW_LIST [CURRENT_ID] , add +1, replace/update the new value in NEW_LIST [CURRENT_ID] , and next also update your DB's NEW_ID column with NEW_LIST [CURRENT_ID]
    Let me know if you need more details
    Romeo Donca, Orange Romania (MCSE, MCITP, CCNA) Please Mark As Answer if my post solves your problem or Vote As Helpful if the post has been helpful for you.

  • How do I turn off auto numbering of lists?

    I've tried unselecting all boxes in the preferences / auto correction menu and Pages still tries to add numbers or letters to items.

    I just figured out one neat trick. If you don't want the next line of your text to be numbered in your document, hit "Control-Enter" instead of "Enter" when you create a new line. It will give you a blank line to work with.
    -Krishna

  • I'm writing a report and need a title page, so I want the auto-numbering to start with the second page. So the title page is zero and the next page will read "1"

    I'm writing a report and need a title page, so I want the auto-numbering to start with the second page. So the title page is zero and the next page will read "1" How do I do this?

    Hi H4S,
    Click at the end of the Tile page.
    Menu > Insert > Section Break.
    Click in the second Section. Insert a page number in the Header or Footer.
    Inspector > Layout > Section:
    Regards,
    Ian.

  • How do I turn off auto-numbering?

    I want to turn off auto-numbering in iWeb. I tried doing it in the Inspector under Text/lists by selecting "none" but that didn't work. Can anyone help?

    Thanks, Old Toad. I'll try it. While continuing to work the problem last night, I discovered if I hold down "shift" when I hit "return" to go to the next line, it suppresses numbering and I can do it myself, the old-fashioned way. I remember seeing that trick in another iWeb context in a Google search, but it appears to work on numbering, too.
    Hey, if I want numbering, it's surely simple enough that I can do it myself, just like if I want to type the word "the"! I'm a touch typist, and I can fly when I get going, and any sort of "auto" function trips me out of the flow, actually making what I'm doing harder, not easier. The "shift-return" solution will also make it harder, until I get it down pat. Maybe one of these days the propellor beanies will bring in an actual user for a consult before they force such dubious improvements on the whole population. I'm sure there are folks who think this is cool, but that doesn't mean it's progress.
    Anyway, thanks for your help.
    Best,
    Steve

  • Auto numbering tables

    I am currently using FrameMaker 8.0 and have had a problem with the auto numbering of tables.
    Can anyone tell me if it is possible to auto number tables using different chapter numbers within the one document?
    I know that it is possible to do this when the chapters are seperate documents within one book.
    E.g.
    First page - Chapter 1
    Table 1.1
    Table 1.2
    Next page - Chapter 2
    Table 2.1
    Table 2.2 etc.
    For some reason when I try to do this any tables under Chapter 2 are still named Table 1.1 and Table 1.2 etc.
    I have tried using a series but that still does not seem to work.
    Any help would be appreciated!

    Thank you both, this helped a great deal.<br /><br />However, I am still having trouble with one file in the book. It seems to be repeating the same chapter number not adding one when the style appears again.<br /><br />E.g. Page 1 has Chapter 1 (C:Chapter <n+>)<br />     Page 3 has Chapter 1 (which is meant to be Chapter 2)<br /><br />Also is there a way to continue the chapter numbers from a previous file in the book?<br /><br />E.g. File A has Chapters 1-4 in it<br />     File B has Chapters 5-8 in it<br /><br />At the moment they are restarting in each file.<br /><br />Any ideas?<br /><br />Thanks,<br />Skye

  • How to change numbering in List?

    Can I change numbering of lists? As in Keynote for iMac, one can choose to start from any numbers, or continue from previous.

    Not change order. I have ten bullets numbered from 1 to 10. The first five fit on one page, but the other five need to go to the next page. Therefore I need to be able to number these bullets from 6 to 10.

  • Adding Auto-Numbering ID

    Hi everybody
    I'm using oracle 9i , and I want to add auto-numbering identity column to existing tables, how can I do this? is it possible to add it for already existing rows?
    and is it necessary to link the related tables through this new added ID???
    thanks in advance

    An "auto-numbering identity column" is a bit of a SQL Server-ism. In Oracle, you can create a sequence object and use that in your insert statement or create a BEFORE INSERT trigger that populates the value, i.e.
    CREATE SEQUENCE my_sequence
      START WITH 1000
      INCREMENT BY 1
      CACHE 100;
    INSERT INTO my_table( new_id_column, <<column list>> )
      VALUES( my_sequence.nextval, <<more data> );Justin

  • HT5295 How can I stop the auto play feature automatically playing/streaming the next podcast?

    How can I stop the auto play feature automatically playing/streaming the next podcast?

    Hi there.
    I listened to podcast there were two things I found that helped me out. Both we're in the podcast app itself.
    Firstly change the default sorting order. When looking at the list off episodes a available on your ios device tap on the description part at the top, this will bring up the settings for that podcast (subscribe mark as played etc) scroll to the Bottom and select oldest first. This will mean that if you are listening to the latest download it will stop at the end as there will be no more to play.
    Secondly, and useful if listening to older podcasts in the list, you can use the timer to stop once the current episode has ended. To do this when you are in the podcast playback screen slide the "album artwork" up, revealing the playback options and nifty tape playing animation this is where you adjust playback speed and set a timer. The timer has a number of options to set playback to stop after set amount of time. However one of these options is to stop once the current episode you are listening to ends. This can also be current chapter if the podcast you are listening to supports chapters.
    Hope this helps, if not clear let me know

  • Vacancy auto numbering in  IRecruitment

    Hi,
    In IRecruitment, if we need to have auto numbering of the vacancies so that when ever the first vacancy is created, it should automatically start with 999 and then continue furthur with 1000,1001,1002 etc on each and every vacancy creation.
    Is this possible? Please update.
    Jim

    The numbering may be based on a sequence. If you can find the sequence, you may be able to control it's starting value.

  • Auto Numbering in InfoPath 2013

    Hello,
    I am brand new to InfoPath.  I was trying to follow some videos and tutorials I found on auto-numbering a field in a form. I had a hard time following because it seems there are slight nuances between versions, and 2013 acts and looks different
    than the tutorials I found. For instance when assigning a value to a field like max(@ID) + 1,  whenever I use the @ sign I get an error in the formula.  Does anyone have a complete InfoPath 2013 'how to' create an auto-number
    field on a form?  Thanks 

    Hi,
    Depend your description, you want to get some information about how to create an auto-number field via InfoPath 2013.
    The steps below about how to create an auto-number field are that I have operated in my InfoPath 2013, and you can follow it:
    Create a custom list, named "Auto".
    Create a column in that list, type number, named "Auto No.".
    Clicked List -> Customize Form and edit default form in InfoPath.
    Clicked Data -> Data Connections -> Add in InfoPath.
    In "Data Connection Wizard", set New Connection to Receive Data -> SharePoint library or list -> set URL of my "Auto" list -> only select ID column  -> checked "Automatically retrieve data when form is opened"
    In InfoPath design view, right click "Auto No." text box -> Properties -> Default Value -> fX button -> Insert Function -> Math -> Max -> OK -> double clicke on the formula to select field -> Show advanced view ->
    in "Fields" drop-down choose secondary data source (named as my "Auto" list) -> selecte 'ID' node in 'dataFields' -> OK -> back in formula type '+ 100' (so the whole formula is like: 'max(ID) + 100')
    Publish it to SharePoint list.
    Here are the links about the details of creating an auto-number field, and you can take a look:
    https://3dcios-web.sharepoint.com/delong/Lists/Posts/Post.aspx?ID=8
    http://www.sharepointsharon.com/2011/11/infopath-2010-reference-filename/
    Thanks,
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Auto numbering is happening even when F11 is pressed

    Hi ,
    We are developing a customer form wherein we have 2 data blocks . These two data blocks share the master-detail relationship. The detail block is a multi record block.
    We are auto numbering an item <line_number> in the detail block following the steps mentioned in the metalink [ID 33342.1]
    https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_afrLoop=130989808463426&recommended=true&type=DOCUMENT&id=33342.1&_afrWindowMode=0&_adf.ctrl-state=ud1uneota_69
    The steps mentioned in the link are generating numbers automatically when a new record is created and resequences the line numbers when a record is deleted. It works fine in these two scenarios.
    But we have two issues here :
    1) The line numbers are getting generated even when we press F11 in th detail block. This should not happen in our form. (We need to suppress the auto numbering in F11 mode)
    2) If we move the cursor to a new record in the detail block, the line number gets generated there but if we move back to the previous record without entering anything in the new record, that new record does not disappear. It stays there .
    Please let us know how can the above two issues be resolved
    TIA
    -SR

    Hi.
    From what I saw on metalink note this is expected behavior. So the first problem is simply to solve, Just call :SYSTEM.MODE function and if it's result is ENTER-QUERY then do nothing (do not call resequence routine). As for the second problem there is a simple solution if your business logic can accept it. You could make one item in child block required. This way a user could not walk away from that record without deleting it first. If this solution is not applicable to you then you will have to manually program logic for this situation.
    Best regards.
    Edited by: gregor13 on Mar 20, 2013 2:38 PM

  • Problem when create auto numbering in BP master using Formatted Search

    Hi all,
    I have a problem in creating auto numbering in BP for Customer type using Formatted search
    My query is like this
    declare @tempNo as char(20)
    set @tempNo=(select  Isnull(max(REPLACE(OCRD.CardCode , LEFT(OCRD.CardCode,10),'')),0)  + 1
    from OCRD where (CardType ='C') and LEFT(OCRD.CardCode,3) = 'CU.' )
    set @tempNo='CU.'left(convert(varchar,GETDATE(),112),6)'.'+@tempNo
    select cast(@tempNo as char(20))
    It should be creating the new number for example
    CU.201101.1
    CU.201102.2
    CU.201103.3
    CU.201103.4
    The format will be like this CU.YYYYMM.autonumbering
    So if the current year is still the same it will always increase the number and it will reset the number become 1 if the current year is change.
    But when i execute the number , the number doesn't increase, still generate the last number CU.201103.4
    I have use this query in generate item number, it runs well but different format.
    Is there some thing wrong with my query?
    Thanks in advance
    Regards
    Jia shun

    Hi Jia shun,
    You have posted an identical threads. There is no such need. Please close this one and response to the one with answer already.
    Thanks,
    Gordon

  • How to use auto numbering with ENG_ECO_PUB.PROCESS_ECO (EBS version 12.1.1)

    Hi All,
    I'm trying to create a new ECO using the PL/SQL API "ENG_ECO_PUB.PROCESS_ECO". I want the ECO name to be automatically assigned by the system but when leaving the ECO_NAME empty (in paramter P_ECO_REC) I get the error message:
    "You must enter an ECO name and organization because they are the primary identifiers of a business object. Please ensure that these values exist in all your records and re-run the import process."
    I have set the profile option "ENG: Change Order Autonumbering - System Administrator access" to yes.
    I have set following fields in P_ECO_REC:
    p_eco_rec.organization_code := 'V1';
    p_eco_rec.change_type_code := 'ECO';
    p_eco_rec.description := 'Test';
    p_eco_rec.transaction_type := 'CREATE';
    p_eco_rec.plm_or_erp_change := 'ERP'; -- also tried with 'PLM'
    p_eco_rec.approval_status_name := 'Approved';
    Do I need to set anything else?
    Thanks,
    Carolin

    Hi Helios,
    thanks for reply.
    I checked note 1242524.1, but there's no advice what to configure for using auto numbering.
    I tried it again with adapted sample code and leaving the ECO_NAME empty:
    DECLARE
    -- API Input variables
    l_eco_name VARCHAR2(9) := '';
    l_org_code VARCHAR2(3) := 'V1';
    l_rev_item_number VARCHAR2(20):= 'CS_Test_Assem_10';
    l_eff_date DATE := '8-SEP-2011';
    l_new_revised_item_revision VARCHAR2(2) := 'A';
    l_eco_rec Eng_Eco_Pub.Eco_Rec_Type := Eng_Eco_Pub.g_miss_eco_rec;
    l_eco_revision_tbl Eng_Eco_Pub.Eco_Revision_Tbl_Type := Eng_Eco_Pub.g_miss_eco_revision_tbl;
    l_revised_item_tbl Eng_Eco_Pub.Revised_Item_Tbl_Type := Eng_Eco_Pub.g_miss_revised_item_tbl;
    l_rev_component_tbl Bom_Bo_Pub.Rev_Component_Tbl_Type := Eng_Eco_Pub.g_miss_rev_component_tbl;
    l_sub_component_tbl Bom_Bo_Pub.Sub_Component_Tbl_Type := Eng_Eco_Pub.g_miss_sub_component_tbl;
    l_ref_designator_tbl Bom_Bo_Pub.Ref_Designator_Tbl_Type := Eng_Eco_Pub.g_miss_ref_designator_tbl;
    l_rev_operation_tbl Bom_Rtg_Pub.Rev_Operation_Tbl_Type := Eng_Eco_Pub.g_miss_rev_operation_tbl;
    l_rev_op_resource_tbl Bom_Rtg_Pub.Rev_Op_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_op_resource_tbl;
    l_rev_sub_resource_tbl Bom_Rtg_Pub.Rev_Sub_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_sub_resource_tbl;
    -- API output variables
    x_eco_rec Eng_Eco_Pub.Eco_Rec_Type := Eng_Eco_Pub.g_miss_eco_rec;
    x_eco_revision_tbl Eng_Eco_Pub.Eco_Revision_Tbl_Type := Eng_Eco_Pub.g_miss_eco_revision_tbl;
    x_revised_item_tbl Eng_Eco_Pub.Revised_Item_Tbl_Type := Eng_Eco_Pub.g_miss_revised_item_tbl;
    x_rev_component_tbl Bom_Bo_Pub.Rev_Component_Tbl_Type := Eng_Eco_Pub.g_miss_rev_component_tbl;
    x_sub_component_tbl Bom_Bo_Pub.Sub_Component_Tbl_Type := Eng_Eco_Pub.g_miss_sub_component_tbl;
    x_ref_designator_tbl Bom_Bo_Pub.Ref_Designator_Tbl_Type := Eng_Eco_Pub.g_miss_ref_designator_tbl;
    x_rev_operation_tbl Bom_Rtg_Pub.Rev_Operation_Tbl_Type := Eng_Eco_Pub.g_miss_rev_operation_tbl;
    x_rev_op_resource_tbl Bom_Rtg_Pub.Rev_Op_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_op_resource_tbl;
    x_rev_sub_resource_tbl Bom_Rtg_Pub.Rev_Sub_Resource_Tbl_Type := Eng_Eco_Pub.g_miss_rev_sub_resource_tbl;
    -- Other API variables for return status / error handling / debugging
    l_error_table Error_Handler.Error_Tbl_Type;
    l_return_status VARCHAR2(1) := NULL;
    l_msg_count NUMBER := 0;
    l_output_dir VARCHAR2(500) := 'C:\temp';
    l_debug_filename VARCHAR2(60) := 'su_debug_10_15.dbg';
    -- WHO columns
    l_user_id          NUMBER := -1;
    l_resp_id          NUMBER := -1;
    l_application_id     NUMBER := -1;
    l_row_cnt          NUMBER := 1;
    l_user_name          VARCHAR2(30) := 'MFG';
    l_resp_name          VARCHAR2(30) := 'MFG_AND_DIST_SUPER_USER_APS';
    BEGIN
    -- Get the user_id
    SELECT user_id
    INTO l_user_id
    FROM fnd_user
    WHERE user_name = l_user_name;
    -- Get the application_id and responsibility_id
    SELECT application_id, responsibility_id
    INTO l_application_id, l_resp_id
    FROM fnd_responsibility
    WHERE responsibility_key = l_resp_name;
    FND_GLOBAL.APPS_INITIALIZE(l_user_id, l_resp_id, l_application_id); -- Mfg / Mfg & Dist Mgr / INV
    dbms_output.put_line('Initialized applications context: '|| l_user_id || ' '|| l_resp_id ||' '|| l_application_id );
    Error_Handler.Initialize;
    l_return_status := NULL;
    l_eco_rec.eco_name := l_eco_name;
    l_eco_rec.organization_code := l_org_code;
    l_eco_rec.change_type_code := 'ECO';
    l_eco_rec.eco_department_name := NULL;
    l_eco_rec.priority_code := NULL; --'Medium';
    l_eco_rec.approval_list_name := NULL; --'SU_ONLY';
    l_eco_rec.reason_code := NULL;
    l_eco_rec.Approval_Status_Name:= 'Approved'; -- will default to Not submitted for Approval
    l_eco_rec.Status_Name := 'Open';
    l_eco_rec.description := 'ECO - '||l_eco_rec.eco_name||' API Test';
    l_eco_rec.transaction_type := 'CREATE';
    l_eco_rec.plm_or_erp_change := 'ERP'; -- or 'PLM'
    l_eco_rec.return_status := NULL;
    dbms_output.put_line('Initialized ECO Header');
    l_revised_item_tbl(l_row_cnt).eco_name := l_eco_name;
    l_revised_item_tbl(l_row_cnt).organization_code := l_org_code;
    l_revised_item_tbl(l_row_cnt).revised_item_name := l_rev_item_number;
    l_revised_item_tbl(l_row_cnt).new_revised_item_revision := l_new_revised_item_revision;
    l_revised_item_tbl(l_row_cnt).start_effective_date := l_eff_date;
    l_revised_item_tbl(l_row_cnt).alternate_bom_code := NULL;
    l_revised_item_tbl(l_row_cnt).status_type := 1; -- 'Open'
    l_revised_item_tbl(l_row_cnt).change_description := 'Test';
    l_revised_item_tbl(l_row_cnt).transaction_type := 'CREATE'; -- transaction type : CREATE / UPDATE
    dbms_output.put_line('Initialized ECO revised items');
    -- Add RS_BOM_C3, acd_type = 1
    l_rev_component_tbl(l_row_cnt).eco_name := l_eco_name;
    l_rev_component_tbl(l_row_cnt).organization_code:= l_org_code;
    l_rev_component_tbl(l_row_cnt).revised_item_name := l_rev_item_number;
    l_rev_component_tbl(l_row_cnt).new_revised_item_revision := l_new_revised_item_revision;
    l_rev_component_tbl(l_row_cnt).start_effective_date := l_eff_date;
    l_rev_component_tbl(l_row_cnt).operation_sequence_number := 1;
    l_rev_component_tbl(l_row_cnt).component_item_name := 'CS_Sub_Item_10_D'; -- Add RS_BOM_C3
    l_rev_component_tbl(l_row_cnt).alternate_bom_code := NULL;
    l_rev_component_tbl(l_row_cnt).acd_type := 1;
    l_rev_component_tbl(l_row_cnt).item_sequence_number := 40; -- new item sequence number
    l_rev_component_tbl(l_row_cnt).quantity_per_assembly := 5;
    l_rev_component_tbl(l_row_cnt).transaction_type := 'CREATE'; -- transaction type : CREATE / UPDATE
    -- Change RS_BOM_C1, acd_type = 2
    l_row_cnt := l_row_cnt + 1;
    l_rev_component_tbl(l_row_cnt).eco_name := l_eco_name;
    l_rev_component_tbl(l_row_cnt).organization_code:= l_org_code;
    l_rev_component_tbl(l_row_cnt).revised_item_name := l_rev_item_number;
    l_rev_component_tbl(l_row_cnt).new_revised_item_revision := l_new_revised_item_revision;
    l_rev_component_tbl(l_row_cnt).start_effective_date := l_eff_date; -- effective date
    l_rev_component_tbl(l_row_cnt).operation_sequence_number := 1;
    l_rev_component_tbl(l_row_cnt).component_item_name := 'CS_Sub_Item_10_B'; -- Change qty for RS_BOM_C1
    l_rev_component_tbl(l_row_cnt).alternate_bom_code := NULL;
    l_rev_component_tbl(l_row_cnt).acd_type := 2;
    l_rev_component_tbl(l_row_cnt).old_effectivity_date := to_date('29-APR-2011 10:09:38', 'dd-MON-yyyy hh24:mi:ss'); -- old effectivity date from bill
    l_rev_component_tbl(l_row_cnt).old_operation_sequence_number := 1; -- old operation sequence number from bill
    l_rev_component_tbl(l_row_cnt).item_sequence_number := 20;
    l_rev_component_tbl(l_row_cnt).quantity_per_assembly := 5; -- existing comp qty on Bill = 2
    l_rev_component_tbl(l_row_cnt).transaction_type := 'CREATE'; -- transaction type : CREATE / UPDATE
    -- Disable RS_BOM_C2, acd_type = 3
    l_row_cnt := l_row_cnt + 1;
    l_rev_component_tbl(l_row_cnt).eco_name := l_eco_name;
    l_rev_component_tbl(l_row_cnt).organization_code:= l_org_code;
    l_rev_component_tbl(l_row_cnt).revised_item_name := l_rev_item_number;
    l_rev_component_tbl(l_row_cnt).new_revised_item_revision := l_new_revised_item_revision;
    l_rev_component_tbl(l_row_cnt).start_effective_date := l_eff_date;
    l_rev_component_tbl(l_row_cnt).disable_date := l_eff_date + 2; -- disable date is 2 day from effective_date
    l_rev_component_tbl(l_row_cnt).operation_sequence_number := 1;
    l_rev_component_tbl(l_row_cnt).component_item_name := 'CS_Sub_Item_10_C'; -- disable RS_BOM_C2
    l_rev_component_tbl(l_row_cnt).alternate_bom_code := NULL;
    l_rev_component_tbl(l_row_cnt).acd_type := 3;
    l_rev_component_tbl(l_row_cnt).old_effectivity_date := to_date('29-APR-2011 10:09:38', 'dd-MON-yyyy hh24:mi:ss'); -- old effectivity date from bill
    l_rev_component_tbl(l_row_cnt).old_operation_sequence_number := 1; -- old operation sequence number from bill
    l_rev_component_tbl(l_row_cnt).transaction_type := 'CREATE'; -- transaction type : CREATE / UPDATE
    dbms_output.put_line('Initialized ECO revised components');
    -- call API to create eco
    DBMS_OUTPUT.PUT_LINE('=======================================================');
    DBMS_OUTPUT.PUT_LINE('Calling Eng_Eco_PUB.Process_Eco API');
    Eng_Eco_PUB.Process_Eco( p_api_version_number => 1.0
    , p_init_msg_list => TRUE
    , x_return_status => l_return_status
    , x_msg_count => l_msg_count
    , p_bo_identifier => 'ECO'
    , p_eco_rec => l_eco_rec
    , p_eco_revision_tbl => l_eco_revision_tbl
    , p_revised_item_tbl => l_revised_item_tbl
    , p_rev_component_tbl => l_rev_component_tbl
    , p_ref_designator_tbl => l_ref_designator_tbl
    , p_sub_component_tbl => l_sub_component_tbl
    , p_rev_operation_tbl => l_rev_operation_tbl
    , p_rev_op_resource_tbl => l_rev_op_resource_tbl
    , p_rev_sub_resource_tbl => l_rev_sub_resource_tbl
    , x_eco_rec => x_eco_rec
    , x_eco_revision_tbl => x_eco_revision_tbl
    , x_revised_item_tbl => x_revised_item_tbl
    , x_rev_component_tbl => x_rev_component_tbl
    , x_ref_designator_tbl => x_ref_designator_tbl
    , x_sub_component_tbl => x_sub_component_tbl
    , x_rev_operation_tbl => x_rev_operation_tbl
    , x_rev_op_resource_tbl => x_rev_op_resource_tbl
    , x_rev_sub_resource_tbl => x_rev_sub_resource_tbl
    , p_debug => 'Y'
    , p_output_dir => l_output_dir
    , p_debug_filename => l_debug_filename
    dbms_output.put_line('x_eco_rec.eco_name:'|| x_eco_rec.eco_name );
    dbms_output.put_line('x_eco_rec.org_code:'|| x_eco_rec.organization_code);
    DBMS_OUTPUT.PUT_LINE('=======================================================');
    DBMS_OUTPUT.PUT_LINE('Return Status: '||l_return_status);
    IF (l_return_status <> FND_API.G_RET_STS_SUCCESS) THEN
    dbms_output.put_line('x_msg_count:' || l_msg_count);
    Error_Handler.GET_MESSAGE_LIST(x_message_list => l_error_table);
    DBMS_OUTPUT.PUT_LINE('Error Message Count :'||l_error_table.COUNT);
    FOR i IN 1..l_error_table.COUNT LOOP
    DBMS_OUTPUT.PUT_LINE(to_char(i)||':'||l_error_table(i).entity_index||':'||l_error_table(i).table_name);
    DBMS_OUTPUT.PUT_LINE(to_char(i)||':'||l_error_table(i).message_text);
    END LOOP;
    END IF;
    DBMS_OUTPUT.PUT_LINE('=======================================================');
    EXCEPTION
    WHEN OTHERS THEN
    DBMS_OUTPUT.PUT_LINE('Exception Occured :');
    DBMS_OUTPUT.PUT_LINE(SQLCODE ||':'||SQLERRM);
    DBMS_OUTPUT.PUT_LINE('=======================================================');
    RAISE;
    END;
    But with this example I again get same error message...
    Any idea?
    Thanks,
    Carolin

  • In my email auto fill it lists addresses I haven't used in 2  years as "recent others". What causes this, the contact information for these people was deleted some time ago.

    In my email auto fill it lists addresses I haven't used in 2  years as "recent others". What causes this, the contact information for these people was deleted some time ago.

    Mail, Window Menu, Previous Recipients.
    Select the ones you don't want and delete them.
    If you want to add them to contacts, click that button.

Maybe you are looking for