When-validate-folder delete_record

Similar Questions

• Dilemma when-validate-Item and Go_Block/Execute Query

  Hey people out there - probably not a matter of surprise on this forum. I have tried to look for it and came up with a few posts but did not find solutions. If all goes well, I also did the right way to conduct a search on this forum. If this is a message for the umpteenth time on this question, I apologize.
  
  So, I have 2 blocks:
  1. the block command that contains the field STUDENT_ID (database item = 'n')
  2 block database which contains STUDENT_ID field (element of database = 'Y' and many other areas)
  
  My goal is to do an Execute_Query if the user enters the student card, then press TAB or place the MOUSE in the database block and display the record if it exists. As we know, a Go_Block is not allowed in When-validate-Item. So, I went a little more away from "simulate" this. The problem is that I'm always pulled the query Execute when the record has already been retrieved. Here's what I have so far. Thus, the trigger next-item key works fine if the user types a tab of the student card and presses. It also works very well if the user clicks on the STUDENT_BK as the trigger once - new - block - Instance that triggers calls the next key. The problem occurs when after recording was recovered and the user click on control.student_id then comes and clicks on the STUDENT_BK, the KEY NEXT-ITEM trigger fires again.
  
  Suggestions or pointers would be more than welcome.
  
  Thank you!
  
  CONTROL.student_id. Next-key

    if :control.student_id is not null and :SYSTEM.BLOCK_STATUS != 'CHANGED' then
      next_block;
      clear_block(NO_COMMIT);
      execute_query;
    else
      show_alert('Please enter Student ID');
    end if;

  STUDENT_BK. Once - new - block - Forum

  go_item('control.student_id');
  do_key('next_item');

  I think you remove the "value copy of the element" and add a where clause clause to your STUDENT_BK of "student_id =: CONTROL.» STUDENT_ID.

  Then when you do

  if STUDENT_BK.STUDENT_ID != :CONTROL.STUDENT_ID then
  

  It logic should endeavour to answer your second question mark block requirement when the user between the block of database STUDENT_BK. If the IDS match, the record already was questioned, if this is not the logic of your application is triggered and with the where clause added to your STUDENT_BK block, it would be in the folder that you want to.

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

  Hello
  I'm looking for a code in the trigger once - vaidate - record in the BLOCK level.
  The trigger should fire only if a value of item checkbox is checked (value ='Y) for the current record (that is to say, if already existing other records have a checked value (='Y), it is not serious and the trigger should not fire)
  Please help me to achieve this goal:
  The code I tried once - vaidate - Trigger, who does not work as I want to:

  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 code above does not fire...
  If I remove the part,
  and: SYSTEM. RECORD_STATUS = 'CHANGE '.
  This event fires for "all"(pas seulement les enregistrements modifiés actuellement) files where nvl (: DEFLOC.to_be_defaulted, ' don't) = 'Y' and: DEFLOC.COMMENTS is NULL ".
  Help, please!
  Note: DEFLOC.to_be_defaulted is an element of database : DEFLOC.COMMENTS is a part of database

  Hi blue,

  There is another way,
  In the trigger when-box-changed.
  If: your_chk_box = 'Y' then
  set_Record_property (: changed_Status, system.cursor_Record, 'your_blk', status);
  on the other
  set_Record_property (: system.cursor_Record, 'your_blk', status, Query_Status);
  end if;

  Then, it is easy for you to discover the records modified using get_Record_property ((: system.cursor_Record, 'your_blk', status))

  Hey, I would like to ask you a Question, is that the check_box point is part of database?
  If so,.
  It's easier... the crazy code will work for this

  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;
  

  in the opposite case
  If you are creating this temp. point, it should be in the same block as item no db.
  I will explain this... You set the State of the checkbox to_be_defaulted some requested folder of Y based on certain conditions, right?
  In any case those files are not editable. Now your condition is to find the boxes newly registered.
  In the post request or where you set to_be_defaulted as ' Y, by default, the new element with the value, while in him when validate trigger, you
  know which folder must attack, it's records nvl (a new item, 'n') = ' n and to_be_defaulted = 'Y '...

  Concerning
  Dora...

• Question about integrated NEXT_RECORD and when-validate-point trigger

  Hello
  
  I work with a form that/did the following:
  
  1) has two blocks of data (block 1 - & gt; Simple registration block & Block 2 - & gt; Block Record multi)
  2) has few items in each block.
  (3) when I filled the block 1 fields and press tab to navigate to next item key of an element in the trigger in block 1, block 2, I created a timer and when the period expires, the When-Timer-Expired trigger in the form of fires, which has a cursor that retrieves data from different database tables and assigns to the items in block 2 and saving the form must Save all records to the database tables attached to form blocks.
  
  During this process when I open the cursor and assign values to each element and say NEXT_RECORD when-validate-point triggers written on each level elements fires and validations. The code looks like this.
  
  Code of the trigger WHEN-TIMER-EXPIRED
  
  DECLARE
  CURSOR C1
  IS
  ................
  ................
  ................
  BEGIN
  FOR c1_rec in C1
  LOOP
  : block2.item1: = c1_rec.col1;
  : block2.item2: = c1_rec.col2;
  : block2.item3: = c1_rec.col3;
  message ("point value 3 is" |: block2.item3);
  
  NEXT_RECORD;
  END LOOP;
  
  DELETE_RECORD;
  POST;
  PREMIER_ENREGISTREMENT;
  END;
  
  
  So my problem is the value assigned to: block.item3 before call NEXT_RECORD is away for WHEN-VALIDATE-ITEM trigger on the same element. I tried to print the value as soon as the trigger is activated. Assume that the previous value is "100" the WVI trigger value is printed with a NULL value.
  
  I tried several times, but all the time, I get the same value.
  
  Can someone help me identify the problem?
  
  Thanks for your time and help

  Your problem may be a timing problem caused by a trigger when-validate-order of the day on your null file at the end change your loop like this:

  FOR c1_rec in C1 LOOP
    If :System.Record_status <> 'NEW' then
      Next_record;  --only advance if record is already populated
    End if;
    :block2.item1 := c1_rec.col1;
    :block2.item2 := c1_rec.col2;
    :block2.item3 := c1_rec.col3;
    message ('Value of item 3 is ' || :block2.item3 ||', Value in Col3='||c1_rec.col3);
    message(' ',no_acknowledge); --force above message to display immediately
  END LOOP;
  POST;
  

  In addition, you must not use next-element key to start a clock. What happens if the user clicks on the element rather than the tab? You should start the timer of the trigger when-validate-record of the first block. It runs all focus time leaves the line of Block_1, unless a change has been made, and regardless of how the user leaves the line.

• Error Msg: "not enough server memory is available to process this command" tries to open the network when the folder shared

  Hello.  I did some of my files of Windows XP Dell system accessible on my home wireless network.  When I try to open the folder (which appears in the network folder) on my Sony Vaio with Windows Vista, I get the error msg that I have stated above in the title of this Post.

  The entire message starts like:

  \\DOUG-DELL1\Denises at the bottom of the folder is not accessible. You could

  are not allowed to use this network resource.  Contact the

  Administrator of this server to find out if you have the permission to access

  "not enough server storage is available to process this command" tries to open the network when the folder shared.

  I have a bitmap and a Jpeg screenshot captures showing the specific error message as well as the objects on my network - is possible I can join to this post?

  This error message is misleading. See article Knowledge Base Microsoft Antivirus software may Cause Event ID 2011 for a likely solution, specifying a value of IRPStackSize 15 on the Windows XP computer. Boulder computer Maven
  Most Microsoft Valuable Professional

• When validate comiting

  Hi am in form 11 GR 2 How can I do this validation

  I have try this

   if :some.field1 is null then
    if :some.field2 is null then
    if :some.field3 != null then
     if :some.field4 != null then
    message('The field is Mandatory');
      raise form_trigger_failure;
    end if;
    end if;
    end if;
    end if;
  

  field3 *.

  Field4 *.

  Field1 *.

  Field2 *.

  When validate commit

  requrement

  If field3 and field4 are null that

  don't validate Field1 and Field2

  BUT

  Is IT EAST VALUE field3 and field4 that VALIDATE

  Field1 and Field2

  Sorry, I missed your last part of the requirement.

  My design works for all field required.

  Anyway try below code to the pre - COMMIT triggered at the form level

  if :field3 is not null or :field4  is not null than -- change OR to AND if you need.
  
      if  :field1 is null or :field2 is null then
          message(show message);
          message(show message);
  
          raise form_trigger_failure;
  
      end if;
  end if;
  

  Hope this helps

  Hamid

• WHEN-VALIDATE-ITEM triggers in a one-expected scenario

  Hi all

  I have a recording multiple field followed a checkbox for each record, where I have the trigger of the ORGANIZATION that actually changes the value of the checkbox on 'Y' when the field is changed manually.

  Case 1: (Expected)

  In this case, the existing value in the field is '-', now I replaced the field with the same value of 1, the VMI is triggered and box is enabled ('Y') indicating that this record is changed manually. .

  Case 2:(Un-Expected)

  In this case, the existing value in the field is '-', now I replaced the field with the same value '-', but still the VMI is triggered and check box is selected ('Y') indicating that this record is changed manually.

  Please let me know if this is the real behavior of the ORGANIZATION.

  Vicky,

  It's actually expected behavior.  Forms does not care if the value of previous and current are the same - he only cares that a value has been entered.  If you want the VMI trigger only when the previous value is different from the current value, you will need to encode this check in your trigger of the ORGANIZATION with the help of the trigger of the item once - new - item - Instance (WNII).  Something like the following example:

  The following code examples assume that you have created the parameter of type CHAR PREV_VALUE object:

  -- Sample When-New-Item-Instance trigger.
  -- This trigger is needed to capture the value of the item before the user changes it.
  BEGIN
       :PARAMETER.PREV_VALUE := NAME_IN('SYSTEM.TRIGGER_ITEM');
  END;
  

  -- Sample When-Validate-Item
  BEGIN
       IF ( :PARAMETER.PREV_VALUE != :YOUR_BLOCK.YOUR_ITEM ) THEN
            -- The Previous Value is not the Same as the Current Value. User has changed the value.
            -- Do whatever validations need to occur here.
            ....
       ELSE
            -- Previous Value is the SAME as the Current Value
            -- Suggesting that the user typed in the same value in the field.
            -- Forms sees this as a change; which is why the WVI trigger is firing...
            NULL;
            -- NOTE: I would not normally code an ELSE where the instruction is NULL.
            -- I would just end the if statement (END IF;)
       END IF;
  END;
  

  Craig...

• commit to working when-validate-point around pls

  Dear friends,

  I have the same problem. Pls give me some inputs to achieve this result.

  There is a block record multi in my form. When user tries to enter duplicate data in this block and tab from the last field i.e. end_date then a pop up should be raised.

  "It's duplicate, you want to keep it? It has 2 buttons, yes or no.

  When the user clicks "Yes" key data must be registered immediately (committed).

  As I put this validation in when-validate-item of this class end_date I can't use commit-shape; Is we work all around to achieve this? Pls suggest some ideas.

  Kind regards

  REDA

  Hello

  I suggest you use the exit timer trigger, it will solve your problem, set the timer in the when-validate-agenda 1 microsecond and after you press the tab key, this will start the timer-out trigger and you can put your commitment within this trigger.

• Oracle forms when-validate-point trigger

  Forms [32 bit] Version 10.1.2.0.2 (Production)
  Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64 bit Production
  With partitioning, OLAP and Oracle Data Mining options
  Release 9.2.0.8.0 - Production jserver
  Oracle Toolkit Version 10.1.2.0.2 (Production)
  PL/SQL Version 10.1.0.4.2 (Production)
  Oracle V10.1.2.0.2 - Production procedure generator
  PL/SQL Editor (c) WinMain Software (www.winmain.com), v1.0 (Production)
  Query Oracle 10.1.2.0.2 - Production Designer
  Oracle virtual graphics system Version 10.1.2.0.2 (Production)
  The GUI tools Oracle Utilities Version 10.1.2.0.2 (Production)
  Oracle Multimedia Version 10.1.2.0.2 (Production)
  Oracle tools integration Version 10.1.2.0.2 (Production)
  Common tools Oracle area Version 10.1.2.0.2
  Oracle 10.1.0.4.0 Production CORE
  
  
  I have a field called equip_code and some validations on the when-validate-item trigger that fills some years messages then opens a comment box. Next to this piece of code equip, I have a button for the list of values. If the user clicks the button (LOV), I have this code.
  
  If FORM_SUCCESS then
  do_key ('LIST_VALUES');
  end if;
  
  How can I force the trigger when-validate-point once the user chooses in a list of values.
  
  Next key element I have this code
  
  Validate (item_scope);
  If form_failure then
  raise form_trigger_failure;
  end if;
  do_key ('enter');
  
  I have this so that when-validate-item trigger before button-next. But when the user chooses in a list of values, I want to trigger when-validate-point. Any help appreciated.

  Your LOV button, in relaxation when button pressed, just do this:

  Go_item('MY_BLOCK.) EQUIP_CODE');
  If Form_Success then
  List_Values;
  End if;

  I don't think that anything on the trigger next-item key you need. If the equip_code value is changed, the WVI trigger runs when the focus (the slider) leaves the field.

  If you want to force the validation immediately once the user selects a value from the LOV, you can then change the List_Values; call over Do_key ('LIST_VALUES'); then create a trigger key-ListVal on the element. In the code, you d code: If Show_LOV ('MY_LOV') then Validate (Item_Scope);

  You must NOT put the code of validation in the trigger element next key, because it does not work if the user uses the mouse to click in a different field, or that he uses any number of other methods to leave the field.

• Problem with when-validate-trigger

  Hi all
  
  I work with form of oracle 10g,
  
  I developed a Form with two blocks: block Query_find and Guarantee_block (this is my main block). And query to find block has 5 fields. For example Po_number, Guarantee_number and Guarantee_type etc.
  
  Thus, in the query is block I have a button called NEW, FIND, when we enter Po_number and click SEARCH, then he gets the details of this po number and moved to Guarantee_block with all the details of the guarantee_block.
  
  So when the user click on the button again travels to the block of the warranty and the user needs to enter new data and save. SO I wrote some simple validations like that for any field. When the user enter a value guarantee no field and he tries to move it will lift a msg. Or well, if he tries to enter the existing guarantee number, it will get a message. Its works fine.
  
  But my problem is when the user to enter the po_number to block Query_find and click Find button it throws this message ("security number already exist"). I don't know how its happens I wrote this procedure inside a pkg and called only in the when validate article in this topic only. Can any pls tell me what is wrong with this code, and why this trigger activated automatically when we click on the button search.
  
  PROCEDURE C_GUARANTEE_NO (event VARCHAR2)
  IS
  number of lv_count;
  BEGIN
  IF (event = "WHEN-VALIDATE-ITEM")
  THEN
  IF: BANK_GUARANTEE_BLK. C_GUARANTEE_NO IS NULL
  THEN
  fnd_message.set_string ('enter security number');
  fnd_message. Show;
  RAISE form_trigger_failure;
  On the other
  Select count (1) in the lv_count of xxbgs_bank_guarantee_master
  where c_guarantee_number =: BANK_GUARANTEE_BLK. C_GUARANTEE_NO;
  If lv_count > 0 then
  fnd_message.set_string ("guaranteed this number already Exist");
  fnd_message. Show();
  RAISE form_trigger_failure;
  END IF;
  END IF;
  END C_GUARANTEE_NO;
  
  
  Concerning
  Srikkanth

  Hello
  Your design is very complex to me.
  Your design says, insert you data in to your BANK_GUARANTEE_BLK, so the validation trigger is activated.
  You can do another way using the lov.

  Hoping to understand...

  Published by: HamidHelal on January 25, 2012 22:44

• How to disable the current point when validate trigger

  Hi all
  I want to disable the current text point when validate trigger.

  Generally, we rely on WHEN-VALIDATE when the cursor leaves a field. In this case, because the cursor leaves the ground, why are you trying to turn it off at this point? The other time would be during the validation process. In this case, you should be able to disable during the WE-COMMIT or in a VALIDATION KEY.

  I guess if we understood better what you want to accomplish and why you want to do, we could offer something more useful.

• FRM-40735: WHEN-VALIDATE-ITEM trigger raised unhandled exception ORA-06508

  Hi all
  
  Pending Production, we have a problem on invoice AP Workbench, gives an error (FRM-40735 after query Trigger on level Bill) when we recover the existing data of the invoice is entered.
  
  For this we have compiled the invalid objects and applied the patch according to metalink id [ID 1209736.1]
  
  After that we came up with new error FRM-40735: WHEN-VALIDATE-ITEM trigger raised unhandled exception ORA-06508.
  
  Can someone help us
  
  Thank you
  SAI

  SAI,

  Thanks for the update and share the solution.

  Hussein

• return to the step after when-validate-point raise form_trigger_failure

  Sorry for this question but its a long time I had to program forms...
  
  I do validation step in a when-validate-point trigger. the trigger fires form_tirgger_failure on the validation point failure.
  
  is there an easy way to make the focus to the item once the failure is triggered?
  
  the most insight.

  You don't have to do anything. When form_tirgger_failure raised in when-validate-item, navigation fails and that the focus remains on the original item.
  Is it not what you see?

• When-validate-trigger

  Hi all
  
  
  I want to message ("Please check the order '");
  
  
  and my code is
  

  DECLARE
       a VARCHAR2(200);
       b varchar2(200);
  BEGIN
       select s.sale_order_no||sd.prod_id||sd.color,s.PERFORMA_TYPE INTO a,b  from sale_order s,sale_order_detail sd 
       where s.id=sd.id and s.sale_order_no||sd.prod_id||sd.color=:gin_detail1.barcode and s.PERFORMA_TYPE!='ORDER CANCEL';
  IF     :gin_detail1.barcode = a THEN
  SELECT SALE_ORDER_NO,prod_id,style,color,xs,s,m,l,xl,pcs INTO :gin_detail1.sale_order_id,:gin_detail1.prod_id,
  :gin_detail1.prod_name,:gin_detail1.color,:gin_detail1.xs,:gin_detail1.s,:gin_detail1.m,:gin_detail1.l,
  :gin_detail1.xl,:gin_detail1.pcs from sale_order_barcode where barcode=:gin_detail1.barcode;
  ELSE
  message('please check the order');
  end if;
  end;

  When-validate-item trigger triggered unhandeled exception ora-01403
  
  Thanks and greetings
  Vikas Singhal

  Hello

  Probably your first select statement is throwing the error: ora-01403
  So maybe try to include part of the exception for your code to intercept the exception ora-01403 - no data available
  and it displays the messgae - "Please check the order.

  Hope it will work then

• Filling of the elements in another block in when-validate-item

  When the user changes the value in the given field, I need to insert records into different blocks. The second block is block of multi-record. The two blocks are no db block, just for display. When the value is changed by the user to the first block, calculating product collecton who wish to view the content of each element in the second record to display block. The problem is that I can not enter the values for records in the second block other than the first record. To access the second records block display, need to navigate to display block with go_block and navigate to new records with next_record. Both go_block and next_record cannot be called from the Organization in the form of small modules.
  
  I want to avoid having to press the button that makes a new calculation and redisplay (so can use go_block and next_record), wish just to refresh when the user updates the value, IE the Organization

  You can use WHEN-VALIDATE-ITEM trigger to loop through the record of the block in detail using the TIMER. What you have to do is in the trigger WHEN-VALIDATE-ITEM create timer like below...

  TRIGGER = WHEN-VALIDATE-ITEM
  DECLARE
    vTimer TIMER;
  BEGIN
    vTimer:=CREATE_TIMER('MY_TIMER',10,NO_REPEAT);
  END;
  

  Now, create a trigger more on called WHEN-TIMER-EXPIRED at the form level and use the code below...

  TRIGGER = WHEN-TIMER-EXPIRED
  BEGIN
    GO_BLOCK('DETAIL_BLOCK');
    FIRST_RECORD;
    LOOP
     -- Perform your functionality here...
     IF :SYSTEM.LAST_RECORD = 'TRUE' THEN
       EXIT;
     END IF;
     NEXT_RECORD;
    END LOOP;
  END;
  

  -Clément