FRM:40737 Illegal restricted procedure ERASE in WHEN VALDATE-RECORD trigger

Hi
I am getting this error when I enter the Sales Order and try to save it sometimes.
Can anyone please tell me how I can avoid this and what is the reason for this error?
Sachin

ok, then it is an apps problem.
can you copy the question in the EBS-Forum ?
General

Similar Messages

  • FRM-40737:illegal restricted procedure COMMIT in WHEN-VALID_RECORD trigger

    Hello,
    I added the following code in Custom.pll, Event procedure. When Internet Expenses responsibility is added to a user on the User form in System Administrator repsonsibility, his default account will be populated from costing. I received error, "FRM-40737:illegal restricted procedure COMMIT in WHEN-VALID_RECORD trigger",
    when enter Internet Expenses in the Responsibility field and tab. Even though the account was populated right, the responsibility is not able to save to the form.
    /* When the employee id given Internet Expense responsibility, create appropriate expense account for the employee from costing */
    if(event_name='WHEN-VALIDATE-RECORD') then
    if(form_name ='FNDSCAUS' and block_name ='USER_RESP') then
    p_responsibility_id := to_number(name_in('USER_RESP.RESPONSIBILITY_ID'));
    --p_responsibility_name := name_in('USER_RESP.RESPONSIBILITY_NAME');
    p_user_id := to_number(name_in('USER_RESP.USER_ID'));
    if (p_responsibility_id = 22918) then
    select employee_id
    into p_person_id
    from fnd_user
    where user_id = p_user_id;
    apps.cov_oie_pkg.update_emp_exp_act(p_person_id);
    commit;
    end if;
    end if;
    end if;
    Any suggestion will be highly appreciated!
    Yan

    You are calling 'COMMIT' after your custom package. You cannot use COMMIT in when-validate triggers. Did you try taking out COMMIT and save the record?

  • FRM-40737: illegal restricted procedure COMMIT in POST-TEXT-ITEM trigger

    Hi All,
    I tried to execute an insert statement in a POST-TEXT-ITEM trigger and use commit to save data in the db but this error appeared:
    FRM-40737: illegal restricted procedure COMMIT in POST-TEXT-ITEM trigger
    How to solve it? OR how to save every text item value entered in the database?

    I don't fully understand, why you need to insert records on post-text-item, but the possible solution is:
    Write a DB procedure which does insert and commits it.
    Call this procedure in post-text-item.
    Problems will occur if your procedure is modifying the table columns, which are used in form. Form will notice that values in DB have changed and you will have "Record has been changed by another user. Please requery to see changes" error. But if records, affected by DB procedures, are not used in form, the wverything will be OK.

  • ON-VALIDATE-ITEM 40737: Illegal restricted procedure COMMIT in WHEN-VALIDAT

    Dear All Expersts,
    In a form we want to update another table ON-VALIDATE-ITEM Or POST-UPDATE or POST-INSERT Event
    Could you please guide us can we do this without any error message i.e
    ON-VALIDATE-ITEM
    40737: Illegal restricted procedure COMMIT in WHEN-VALIDATE-ITEM trigger.
    Please guide.
    Thanks & Best Regards
    Eidy

    Eidy,
    Ok, for one thing, the Post-Update and Post-Insert triggers fire during the Post and Commit Transaction processing so it doesn't make any sense that you would attempt to issue a COMMIT in either of these triggers because it is already in the process of COMMITING.
    I think it would be best if you explain what it is you what to accomplish rather than how you are trying to accomplish the task. Then we will know why you are attempting a COMMIT (Restricted Built-in) in a When-Validate-Item trigger (will allows DML, Select, and Unrestricted calls).
    If you intent is to update/insert a record into a seperate table (say for auditing purposes) when a user changes a value in a different block (table) item - perhaps an After Update/Insert trigger on the database table would be a better option. This makes the secondary update/insert automatic and you don't have to code it in all of your forms.
    Again, like I said - if you tell us what you are trying to do, we can tell you if you are going about it the right way.
    @DanielB - All I can says is HUH?
    Craig...

  • FRM 40737: Illegal Restricted Procedure   in !!! HELPPP

    Hi:
    I have to use a program unit in Pre-Insert/ Pre-update triggers. That program unit calls some restricted built ins. Hence whenever I am using that program unit in validation triggers its giving
    FRM 40737 - Illegal restricted procedure FIRST_RECORD in PRE-INSERT/PRE-UPDATE
    Can somebody help.
    came to know that using timer can help. can somebody explain what is the alternative or how to use the timer in this case(if its of any help)?????
    thanks

    I don't fully understand, why you need to insert records on post-text-item, but the possible solution is:
    Write a DB procedure which does insert and commits it.
    Call this procedure in post-text-item.
    Problems will occur if your procedure is modifying the table columns, which are used in form. Form will notice that values in DB have changed and you will have "Record has been changed by another user. Please requery to see changes" error. But if records, affected by DB procedures, are not used in form, the wverything will be OK.

  • FRM-40737: Illegal restricted procedure (Ver 9.0.2.7.0)

    My form updates State code data. I get state from the from, perform query and populate the form myself. After the last field is entered I perform the update query, then a commit. This error is on the commit.
    Help!

    Jose,
    Some built-ins cannot be called during other processing (such as in the Pre- and Post- commit related triggers). All built-ins are labelled as "Restricted" or "Un-Restricted" This determines if they can be used when Forms is doing something else such as committing or executing a query.
    See the topic "Restricted Built-in Subprograms" in the help

  • FRM-40735: illegal restricted procedure COMMIT in POST-CHANGE trigger

    I am using forms6i. I have three text fields FL1 ,*FL2* , FL3 in a form. Cursor passes from FL1 to FL2 and FL2 to FL3. I want when cursor transfers from FL1 to FL2 the form should be saved(commit). On FL1 i put COMMIT; in post-change.
    But when I pressed Enter key on FL1 it gives following error message.
    FRM-40735: illegal restricted procedure COMMIT in POST-CHANGE trigger
    Can you help me doing this.

    Gul wrote:
    I am using forms6i. I have three text fields FL1 ,*FL2* , FL3 in a form. Cursor passes from FL1 to FL2 and FL2 to FL3. I want when cursor transfers from FL1 to FL2 the form should be saved(commit). On FL1 i put COMMIT; in post-change.
    But when I pressed Enter key on FL1 it gives following error message.
    FRM-40735: illegal restricted procedure COMMIT in POST-CHANGE trigger
    Can you help me doing this.You cannot use COMMIT_FORM in post-change trigger. Because post-change only accept UN-restricted procedure. and commit is not.
    try this
    /* Trigger KEY-NEXT-ITEM on every item and write sample code */
    commit_form;
    next_item;Hope this works..
    Hamid
    Mark correct/helpful to help others to get right answer(s).*

  • Illegal restricted procedure Synchronize - error in webforms

    Hi All,
    When trying to open a webform (Oracle 9i/10g) with a field having synchronize built-in in the when-validate-item trigger, I am getting an error "Frm-40737:Illegal restricted procedure SYNCHRONIZE in WHEN-VALIDATE-ITEM trigger".
    Is Synchronize restricted procedure in webform (Oracle manual shows as unrestricted procedure)?
    This happens in some other forms while committing, but transaction is saved.
    Your suggestions on this will be highly appreciated.
    Gopalakrishnan.

    We had the same issue after converting from 6i to 10g. Sometimes 10g is blocking a SYNCHRONIZE in a WHEN-VALIDATE-ITEM as restricted. Forms 10g is wrong as SYNCHRONIZE is not (and has never been) a restricted built-in.
    I could never make it into a simple reproducable testcase to show to Oracle. In our case we could safely remove the SYNCHRONIZE built-ins from the code. Most of the times they were added in the past to workaround bugs in Forms 4.5 or 5.x.
    On MetaLink you can find a couple of bugs in Oracle Applications running into the same issue and they were also resolved by removing the call to SYNCHRONIZE. I also find bug 1577072 (open since 2001)
    If you need further assistance you'll probably have to log an iTAR at http://metalink.oracle.com

  • FRM40737: Illegal restricted procedure SET_WINDOW_PROPERTY in...

    FRM40737: Illegal restricted procedure SET_WINDOW_PROPERTY in WHEN_VALIDATE_ITEM trigger
    the code inside my when-validate is as follows:
    declare
         button number;
    begin
    if :gse_packing_list_edit.carton_ref is null then
         button :=show_alert('carton_ref');
    else
    delete from A
    where
    PL_NO = :block.PL_NO AND
    CARTON_REF = :block.CARTON_REF AND
    ITEM = :block.ITEM;
    show_window('pop_up_window');
    go_block('pop_up');
    go_block('B');
    execute_query;
    end if;
    end;
    this was originally a code for a button that worked perfectly, when i decided that i would call the window automatically when text was entered in it.
    how can i do this now?

    thanks fro the reply francois
    but the bit that still puzzles me is the fact that oracle_forms gives me the feedback that im calling SET_WINDOW_PROPERTY
    since i'm not calling it directly, i am assuming that it is being called by something else in my code and the show_window(..) seems to be the one. Oracle documentation however tells me that this is a unrestricted procedure.
    anyways.... the go_item/block will cause a problem anyway.. I've heard about the timer thing.. but not too sure how to go about doing it..
    will appreciate your response in this regards
    thanks

  • Frm-40735: when validate record trigger raised unhandled exception ORA-0406

    while on production when i open any form and inserting some valeus after that when i want ot save the information it is showing me following error
    frm-40735: when validate record trigger raised unhandled exception ORA-04062

    ORA-04062: %s of string has been changed Cause: Attempt to execute a stored procedure to serve an RPC stub which specifies a timestamp or signature that is different from the current timestamp/signature of the procedure.
    Action: Recompile the caller in order to pick up the new timestamp >
    Check the When-Validate-Record trigger in your form and look for any calls to a database stored procedure. Then check the status of the database procedure to ensure it is "Valid." If the procedure is not valid - find out why and fix it.
    Hope this helps,
    Craig B-)
    If someone's response is helpful or correct, please mark it accordingly.

  • FRM-40735: WHEN-CREATE-RECORD trigger raised unhandled exception ORA-06502.

    Hi Guys,
    I am a beginner in Oracle apps and have been trying to setup receivables module. I have completed all necessary setups such as system options, transaction types, transaction sources, Auto accounting etc.
    Now, when I try to open transaction window, I am getting the following error
    FRM-40735: WHEN-CREATE-RECORD trigger raised unhandled exception ORA-06502
    RDBMS : 11.2.0.2.0
    Oracle Applications : 12.1.3
    Thanks in advance.. :-)

    Please see these docs.
    Repair Orders Form Error: 'FRM-40735: When-Create-Record Trigger raised unhandled exception ORA-06502' For Instances With Alphanumeric Instance Numbers [ID 580147.1]
    FRM-40735:WHEN-CREATE-RECORD Trigger Raised Unhandled Exception ORA-06502 [ID 125204.1]
    Attempt To Open IGIPAPPF Approval Profile Form Fails With Error: FRM-40735 WHEN-CREATE-RECORD Trigger raised unhandled exception ORA-06502 [ID 418546.1]
    Transactions Workbench Error: ORA-06502 [ID 1295626.1]
    Transactions Workbench Error: Listing of FRM Errors [ID 1321612.1]
    Forms Error: FRM-40735 [ID 1295620.1
    Credit Transactions Form Errors Out With FRM-40735 [ID 1079945.1]
    Thanks,
    Hussein

  • FRM-40735: WHEN-CREATE-RECORD trigger raised unhandled exception ORA-01403

    hi
    when i am searching AP module and
    Payables Manager - > Oracle Payable - > Setup -> Invoice-> Distribution Set
    i am getting this FRM-40735: WHEN-CREATE-RECORD trigger raised unhandled exception ORA-01403.
    what to do?
    RHEL 5.3
    EBS 12.0.0 RUP 6
    1)I have tried adadmin compling forms
    2)generating trace and tkprof but still found none.
    what to do?
    Regards
    Edited by: new2appsdba on Jul 16, 2010 1:33 AM
    Edited by: new2appsdba on Jul 16, 2010 1:37 AM

    hsawwan wrote:
    Hi,
    Please see if (Note: 1074119.1 - R12. APXINWKB: When Trying To Change Invoice Distribution Line Type Get Error: FRM-40735:PRE-RECORD Trigger Raised Unhandled Exception.ORA-01403) is applicable.9747677:R12.AP.B patch which is for 12.1 and made the SR.
    >
    If this does not help, obtain the FRD file and see if more details are collected in the logs.
    Note: 445166.1 - How to create a FRD (Forms Runtime Diagnostic) Log in EBusiness Suite R12 using Forms 10gwatching
    Note: 438652.1 - R12: Forms Runtime Diagnostics (FRD), Tracing And Logging For Forms In Oracle Applications
    Note: 867943.1 - Steps To Take FRD Trace in 11.5.10 & R12
    Thanks,
    Hussein

  • FRM-40735: WHEN-CREATE-RECORD trigger raised unhandled exception ORA-01422

    when i am searching AR module and
    Receivables - > Transactions - > Transactions
    i am getting this FRM-40735: WHEN-CREATE-RECORD trigger raised unhandled exception ORA-01422.
    what to do?

    user9095240 wrote:
    Hi,
    1. This form was working fine until patch 8407693 has been applied.
    2. Yes, I'm getting this error in every responsibility or user
    3. No, no personalizations
    I've read another time docs Hussein linked and as in "Troubleshooting Transaction Types In Oracle Receivables (Doc ID 1090878.1)" Patch Related paragraph, seems like I need  Patch 8302210:R12.AD.B cause my admorgb.pls  version is 120.21.12010000.2 instead of 120.21.12010000.3. I think replicate seed data program duplicated something in db. Is it possible?
    Regards
    With the information you have provided so far, it's hard to say that the cause of the issue is because of this file (version). However, if this is a test instance you may proceed and apply the patch and see if it helps.
    Thanks,
    Hussein

  • When-validate-record trigger only if  a non database item is changed

    Hi,
    I am trying a code in the when-vaidate-record trigger in the BLOCK level.
    The trigger should fire only if a checkbox item value is ticked(Value ='Y) for the present record(i.e, if already existing other records have a value ticked (='Y), it doesnt matter and trigger shouldnt fire)
    Please help me achieve this :
    The code I have tried in when-vaidate-trigger, which does not work as what I want :
    DECLARE
    X NUMBER;
    BEGIN
    if
      nvl ( :DEFLOC.to_be_defaulted, 'N' ) = 'Y' and :DEFLOC.COMMENTS is NULL
      and :SYSTEM.RECORD_STATUS ='CHANGED'
         then
        set_alert_property(
             'err_alert',
             alert_message_text,
             'You must enter a comment when defaulting localities.');
              x := show_alert('err_alert');
              RAISE FORM_TRIGGER_FAILURE;
              end if;
    END;The above code does not fire at all..
    If I remove the part,
    and :SYSTEM.RECORD_STATUS ='CHANGED'
    it fires for "all records"(not just the currently changed records) where nvl ( :DEFLOC.to_be_defaulted, 'N' ) = 'Y' and :DEFLOC.COMMENTS is NULL
    Please help !!
    Note: :DEFLOC.to_be_defaulted is a non database item ; :DEFLOC.COMMENTS is a database item

    Hi kriti,
    There is one more way,
    In the when-checkbox-changed trigger,
    if :your_chk_box = 'Y' then
    set_Record_property(:system.cursor_Record, 'your_blk',status,changed_Status);
    else
    set_Record_property(:system.cursor_Record, 'your_blk',status,Query_Status);
    end if;
    Then it is easy for you to find out the changed records using get_Record_property((:system.cursor_Record, 'your_blk',status)
    Hey let me ask you one Question, is that check_box item is database item ???
    If so,
    it is easier..the fol. code will work for that
    if   nvl ( :DEFLOC.to_be_defaulted, 'N' ) = 'Y' and :DEFLOC.COMMENTS is NULL
      and nvl(get_item_property('DEFLOC.to_be_defaulted',database_value),'N') = 'N'      then
                      set_alert_property(
             'err_alert',
             alert_message_text,
             'You must enter a comment when defaulting localities.');
              x := show_alert('err_alert');
              RAISE FORM_TRIGGER_FAILURE;
              end if;otherwise
    If your are creating that temp. item, it should be in the same block as non-db item.
    I will explain this... You are setting the status of to_be_defaulted check box of some queried record to Y based on some conditions, right?
    These records anyways are not updateable. Now your requirement is to find out the newly checked check boxes.
    So in the post query or the place where you set to_be_defaulted as 'Y, we will default the new item with value Y, so that in the when validate trigger, you
    know which record needs to attacked, It is those records with nvl( new item ,'N') = 'N' and to_be_defaulted = 'Y'...
    Regards
    Dora...

  • Problem while handling When-Validate-Record Trigger in Forms 6i

    I am using below mention code in when validate trigger and use go block loop in when button pressed. if Check_Date_Range gives RAISE Form_Trigger_Failure error user will enter in a loop. kindly provide me solution for below mention problem.
    BEGIN
    Check_Date_Range(:Experiment.Start_Date,:Experiment.End_Date);
    END;
    ** The procedure looks like this
    PROCEDURE Check_Date_Range( d1 DATE, d2 DATE ) IS
    BEGIN
    IF d1 > d2 THEN
    Message('Your date range ends before it starts!');
    RAISE Form_Trigger_Failure;
    END IF;
    END;

    You have more chance to find a response if you post into Forms<br>
    <br>
    Nicolas.

Maybe you are looking for