Sequence number in pre-insert form trigger

i have two tables invoice (master) inv_detail(detail) and assign the invoice number using a sequence number,
by writing the folowing code in the pre-insert trigger
select a.nextval into :inv_no from dual;
( i make the trigger at the form level becuause i have a master (invoice) and detail (inv_detail) relation at the same screen,so i must fetch the value of the
sequence into the :invo_no in the screen,to let the 'copy value from' property at the detail block works so the value of the foreign key will be copied from
the sequence number at the screen.
will this method be a good one for multi user envirment(to select the a.nextval in the pre-insert trigger at the from level?)

Kevin, thank you for the correct explanation. I was making an assumption and of course it was wrong.
Mohannad, please do not try to link the invoice count with the sequence number. Any time you need a count, just do a select count(*). The sequence number is ONLY a unique key, and should represent nothing else.
People have discussed this situation heavily. If you insist on trying to ensure there are no gaps, you will:
1. Fail -- there are many scenarios where gaps will occur.
2. Waste your time.
3. Whatever process you build to try to prevent gaps will cause unnecessary overhead and work for the server, and in a multi-user environment, cause processing bottlenecks due to table locks.

Similar Messages

Sequence Number Generation in XML Form Buider??????

Hi All,
I want to generate some Sequence Number for each XML Form Generated by the XML Form Builder Application?
Ex: my XML Form Builder Application is "MYAPP". Using this I filled data and Save, then an XML will be created, then it should have some unique Number(say 1234), then if I fill the differennt Data and Save, then another XML will be created. For this the Number should be 1235, next 1236, ........
I can use the XML Form ID, but that is not User friendly format. Becaz I need to display this Number to the End User.
(Example: 10b2ae7b-e269-2b10-d88e-ddade2e62015.xml)
If anybody have idea on this, Please guide me...
Thanks&Regards||
Ashok M.
Edited by: Ashok Kumar Munugoti on Oct 16, 2008 8:04 AM

closing this Thread.

Execution Sequence of 'Personalization' and 'Standard Form Trigger'

Dear All,
A basic question, How about Execution Sequence of 'Personalization' and 'Standard Form Trigger'?
Which one will be firstly executed? any document about this question?
Thanks a Lot

Hi HTH,
Actually I am not asking for Trigger Execution Sequence, I am asking Sequence between 'Personalization' and 'Standard Form Trigger',Personalization is first or Standard Form Trigger is first.
for example,if i have code at W-N-F-I trigger at standard trigger and Personalization , which code get invoked first?
Tks

A sequence number error in a form

I am currently creating a form with a sequence number in forms 10g
<pre>
table name: emp
table desc: emp_id number,emp_name varchar2(20),emp_no number
</pre>
i have to generate the emp_id automatically.
<pre>
create sequence emp_seq
minvalue 1
start with 1
increment by 1
cache 20
</pre>
I use pre_insert trigger in block
<pre>
begin
select emp_seq.nextval into :emp.emp_id from dual
end
</pre>
problem;
I can not insert a record because of sequence number in :emp.emp_id
no compilation error but there is no automatic sequence number appeared in :emp.emp_id after run a form.
It used to work before(fine with automatic sequence number in :emp.emp_id).
it happens after I changed layout format and someone add more columns in emp table.
eventhough i did not use sequence number in emp.emp_id
in pre-insert-trigger
<pre>
begin
select nvl(max(emp_id),0)+1
into :emp.emp_id
from emp;
</pre>
still can not show up any number in :emp.emp_id
please help me out

Thank you . It works now.
would you mind explain to me; what I can not use automatic sequence number in emp.empid text field in pre-insert-trigger in my case
is it trigger confliction in my forms?

Sequence number over multiple adobe form calls

Dear all
I posted this question in another subforum - http://forums.sdn.sap.com/thread.jspa?threadID=1997461 - three days ago,
but nobody could answer, so I try to post it here.
We would like to have a sequence number for each page.
The Adobe Form gets called more than once, so the second call doesn't know, how many pages were printed already, thus it cannot continue the sequence number.
Do you have any ideas?
Of course, I would prefer not to publish an SAP-service only for this purpose...
(The transaction is HRFORMS, we would like to print a sequence number bar code, so that the packing machine to the envelope senses, if two pages are stuck together.)

Hi,
I have a problem in printing current page number of an adobe form.
My requirement is that , my form got 2 pages. On first page i am not printing page numbers and excluded from numbering.
Numbering starts from second page. The second page needs to be repeated twice.
In this case my page printing should look like :
First page - no page number
second page - 1 of 1
Third page - 1of 1 (as it is a copy)
IF second page extends to multiple pages (eg.. 2)
First page - No Page no
First instance of second page - 1of 2 , 2 of 2
Second instance of second page - 1 of 2 , 2 of 2 . Presently it is printing like : 3 of 2 , 4 of 2. I need to initialize current page count. I could able to set the total page count 2 via variable from print program. But while printing the second instance, I am not able to initialize the current page count.
I have seen the following thread which exactly talks about my problem but with out any solution.
http://forums.sdn.sap.com/thread.jspa?messageID=10601698&#10601698
I have tried initializing the current page count in the initializing event and tried assigning the initial value when the second copy starts but for entire no of pages the same initialized value is coming.
Can anyone help me in this regard.
Thank You,
Regards,
Naresh.

MAX + 1 Pre Insert

Dear All
i need to use MAX+1 instead of Sequence value in Pre Insert trigger in ADF / JSF Application ..
and this value assigned to PK Attribute
i unchecked Mandatory value for PK
my problem now, system give me the value is required when i try to enter second record without commit first record as i have af:table , and i guess that it read the validation before pre insert trigger in dodml
if (operation == DML_INSERT) {
setContractId(GetSequenceValue("customers", "customer_id"));
thanks
Edited by: user8854969 on Dec 13, 2012 11:42 PM

Tell your client to ignore the gaps...
If you want a gapless number, you have 2 basic options:
1). Assign the gapless number in a batch process after-the-fact
2). Use an approach that serialises (i.e. only allows one insert at a time), by using locking or some other serialisation method. This approach limits your scalability.
I have (almost always) used option 3: Use a sequence and ignore the fact that there are gaps. I the case where I didn't use this option, I used approach 2. You cannot do this with a trigger!
John

How can I get the SERIAL NUMBER after an INSERT

I am working on an application using Jdk1.2 connecting to an Oracle 8i
Database. The JDBC driver that I am using is Oracle's thin driver.
In the DB, I have a table that has a primary key as a sequence number.
Upon inserting a single row into this table, how can I get this serial
number that is generated by the Database.
Previously I was using INFORMIX database and welogic's JDBC drivers and this
is how I get the serial number.
PreparedStatement ps = ...
ps.setObject(......);
ps.executeUpdate();
int snumber =
(weblogic.jdbc.informix4.Statement) ps.getSerialNumer()
Similarly I have tried to use
(oracle.jdbc.driver.OracleStatement) ps.getSerialNumber()
But this method does not exist in the JDBC thin drivers.
Is there some other way to get this serial number.
Thanks,
Suresh
null

<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by syalaman:
I am working on an application using Jdk1.2 connecting to an Oracle 8i
Database. The JDBC driver that I am using is Oracle's thin driver.
In the DB, I have a table that has a primary key as a sequence number.
Upon inserting a single row into this table, how can I get this serial
number that is generated by the Database.
Previously I was using INFORMIX database and welogic's JDBC drivers and this
is how I get the serial number.
PreparedStatement ps = ...
ps.setObject(......);
ps.executeUpdate();
int snumber =
(weblogic.jdbc.informix4.Statement) ps.getSerialNumer()
Similarly I have tried to use
(oracle.jdbc.driver.OracleStatement) ps.getSerialNumber()
But this method does not exist in the JDBC thin drivers.
Is there some other way to get this serial number.
Thanks,
Suresh
<HR></BLOCKQUOTE>
========================================
ORACLE don't support serial number as Informix, but you can create sequence table
and every time get the next value from this table.
null

How to create an INSERT trigger which creates a "sequence number"

Imagine a table T_Q with columns C_1, C_2, C_3 and UN_123.
C_1, C_2 and C_3 are all numeric and given by the user.
UN_123 has to be a calculated sequence number starting by 1 and incremented by 1 for each combination of C_1, C_2 and C_3, i.e., the sequence number depends on the key values C_1, C_2 and C_3.
Could anybody provide a code sample on how to create a BEFORE INSERT trigger , which calculates the value of the column UN_123 based on the values of C_1, C_2 and C_3 ??
Premise: Rather than using any sequence, the trigger code should only be based on the table T_Q
null

<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Rainer Wagner ([email protected]):
Imagine a table T_Q with columns C_1, C_2, C_3 and UN_123.
C_1, C_2 and C_3 are all numeric and given by the user.
UN_123 has to be a calculated sequence number starting by 1 and incremented by 1 for each combination of C_1, C_2 and C_3, i.e., the sequence number depends on the key values C_1, C_2 and C_3.
Could anybody provide a code sample on how to create a BEFORE INSERT trigger , which calculates the value of the column UN_123 based on the values of C_1, C_2 and C_3 ??
Premise: Rather than using any sequence, the trigger code should only be based on the table T_Q<HR></BLOCKQUOTE>
null

Forms 9i & pre-insert trigger

Hi everyone,
We've just upgraded from Forms 6 to 9i.
My pre-insert trigger in 9i doesn't seem to be firing - is this something that has changed?
I need to set my unique ID's and other variables - is there a better place to do this now?
Please advise.
Thanks.
Lesley

No commit form has not changed.
The change in behavior that you are probably hitting is where required items really are required even if they are not displayed - this change came in a patch to 6i.
So I'm guessing that you have a key field which is required but not displayed to the user and you're populating a new key in pre-insert.
Because you've made the field required, the commit is failing before you actually get to pre-insert because a required field is not filled in.
So your solution would be to restore the code to Pre-Insert where it belongs and make sure that any non-displayed items are not marked as required.
Support have a Forms API program that can make this change on-mass for you if you have a lot of forms like this,

Sequence number in ADF FORM.

hi All,
I have a table with ID as primary key and have a sequence created for this primary key and have a trigger for generating sequence number while inserting the record in table.
How can i map this Sequence in ADF so while inserting record from Form i can skip the ID column.
Regards,
Suresh kumar

I am using MySQL and primary key is auto incremented in my table. Therefore I have selected
SQL Plateform : SQL92
Data Type Map : Java
When I am trying to create entiry object, I do not get option of selecting DBSequence. I did some documents reading, I found out that DBSequence is part of "*Java Extended for Oracle*" Data type Map.
While creating the EO , in the Attribute Settings, I click the Browse and search for DBSequence. I found out oracle.jbo.domain.DBSeqence.
Can someone please let me know that I am going to face any problem in future by using DBSequence in his manner?
Thanks in Advance.

Problem with forms6i using Pre-Insert Trigger

I created a block level pre-insert trigger to do some validations and when I save the first time with wrong data it is working fine and popping up alerts that I defined but if I press save the second time it is saving even though the data is wrong.
This is in Applications 11.5.10 using all the property classes and running on the server.
I created exact replica of the form(no applications, property classes
just basic form but with same functionality) and ran it on my local machine it is working fine. It is giving error till the data is fixed.
Anybody know why?
Thanks in advance

It did not work. It is still doing the samething. Actually it is popping up my alerts but saving the record first time itself. Is there any way I can tell it not to save if the data is wrong. My code is below it basically pops up the alerts but doesn't tell anywhere not to save it.
Thanks
VJ
declare
     v_amount number;
     alert_id      ALERT := Find_Alert('amount_from');
     alert_id1 ALERT := Find_Alert('amount_to');
     dummy_var NUMBER;
begin
     select max(ssibe_amount_to) into v_amount from ssibe_orderappr_tab where
          ssibe_account_number = :ssibe_orderappr.ssibe_account_number;
          if :ssibe_orderappr.ssibe_amount_from <= v_amount
          then
               Set_Alert_Property(alert_id, ALERT_MESSAGE_TEXT, 'Amount_From should be greater than '|| v_amount);
               dummy_var := Show_Alert(alert_id);
          else
               IF (:SSIBE_ORDERAPPR.SSIBE_AMOUNT_TO <= :SSIBE_ORDERAPPR.SSIBE_AMOUNT_FROM)
               THEN
               dummy_var := Show_Alert(alert_id1);
               end if;
          end if;
end;

Pre-insert-trigger ignoring assignments

Hi,
I have this code in a PRE-INSERT-TRIGGER of a database table block:
Select emp_seq.Nextval Into :EMP.EMPNO From dual;
Select Sysdate Into :EMP.LASTCHANGED From dual;
And i have this code in a PRE-UPDATE-TRIGGER of the same block:
Select Sysdate Into :EMP.LASTCHANGED From dual;
given scenario:
1) query records from the table into a block:
empno ename lastchanged
1 Smith 01.12.2008
2 Johnson 01.12.2008
2) change empname in any record except no. 1:
empno ename lastchanged
1 Smith 01.12.2008
2 Johannson 01.12.2008
3) create a new record somewhere above the changed record
empno ename lastchanged
1 Smith 01.12.2008
<null> <null> <null>
2 Johannson 01.12.2008
4) insert ename in new record
empno empname lastchanged
1 Smith 01.12.2008
<null> Obama <null>
2 Johannson 01.12.2008
5) do_key('commit_form')
with Forms 6.0.8.23.2 -> working fine
with Forms 6.0.8.27.0 -> ORA-01400:: cannot insert NULL into ("EMP"."EMPNO")
Any assignment in the pre-insert-trigger is ignored! Can anyone help me with this bug? Thanks in advance

message(:EMP.EMPNO) is always Null ...
Everything works if there's no update of a record with higher record-number in the transaction. But the scenario in post 1 doesnt work with Forms 6.0.8.27.0Ugh -- that's ugly!
Unfortunately, opening a Service Request with Oracle will get you nowhere, since Oracle no longer supports Forms 6i.
Yesterday, I experienced something very similar with the same version of Forms, specifically this part: Everything works if there's no update of a record with higher record-number in the transaction.*
If I updated a higher record number in the block, I could NOT get Forms to subsequently store a value in a column in a prior record. I would set the value in the column, and immediately display the value, and it was null! Fortunately in my case, the stored value was only to enable skipping a database lookup in a subsequent pass, so I just skipped working on a solution.
However, in your case, the problem is a show-stopper.
What I found was that if I navigated back to the first record in the block, the problem went away. So maybe try this in your commit process:
    Go_block('ABC');
    First_Record;
    Synchronize;
    Commit_Form;Let us know if that works for you.

Forms trigger Firing Sequence

Does anyone know where I can find details on firing sequence of each type of triggers on Item, Block and Form levels?
Can I set the Debugger to trace the actual sequence of firing of triggers at run-time?
Message was edited by:
wyfwong

i hope that the document may help!
(V45) Trigger Execution Sequence in Forms 4.5
=============================================
Introduction
This document lists the order in which triggers fire in Oracle Forms 4.5:
o The first column, Action, describes the function to be performed
(e.g. deleting a record).
o The second column, Trigger Firing Order, describes the order
in which triggers fire after a function is performed.
o The third column, Level, describes the level (form, block, item)
at which the trigger fires. This was accomplished by creating a form
with all the triggers invoked. If a trigger could fire at all levels,
it was included at all levels. Such a trigger fires at the lowest level
at which it is defined.
Key triggers and triggers which fire via buttons or check boxes are
not included.
This bulletin does not cover every contingency and covers only the
most commonly used actions.
Action Trigger Firing Order Level
Runform 1. Pre-Logon Form
2. On-Logon Form
3. Post-Logon Form
4. Pre-Form Form
5. When-Create-Record Block
6. Pre-Block Block
7. Pre-Record Block
8. Pre-Text-Item Item
9. When-New-Form-Instance Form
10. When-New-Block-Instance Block
11. When-New-Record-Instance Block
12. When-New-Item-Instance Item
Enter Query 1. Post-Text-Item Item
2. Post-Record Block
3. When-Clear-Block Block
4. When-New-Record-Instance Block
5. When-New-Item-Instance Item
Note: If you define the Key-ENTQRY trigger, this is the only trigger
which fires in an Enter Query situation.
Execute Query
After Enter Query 1. Pre-Query Block
2. Pre-Select Block
3. On-Select Block
4. When-Clear-Block Block
5. Post-Select Block
6. On-Fetch Block
7. On-Close Form
8. When-Clear-Block Block
Note: If you define the Key-EXEQRY trigger, this is the only trigger
which fires in an Execute Query situation.
Execute Query
Without Enter
Query 1. Post-Text-Item Block
2. Pre-Query Block
3. Pre-Select Block
4. On-Select Block
5. Post-Select Block
6. On-Fetch Block
7. On-Close Form
8. When_Create_Record Block
9. Pre-Record Block
10. Pre-Text-Item Item
11. When-New-Record-Instance Block
12. When-New-Item-Instance Item
Exit 1. Post-Text-Item Item
2. Post-Record Block
3. Post-Block Block
4. Post-Form Form
5. On-Rollback Form
6. Pre-Logout Form
7. On-Logout Form
8. Post-Logout Form
Next Field and
Previous field 1. When-New-Item-Instance Item
Next Record and
Previous Record 1. When-New-Record-Instance Block
2. When-New-Item-Instance Item
Next Block and
Previous Block 1. Post-Text-Item Item
2. Post-Record Block
3. Post-Block Block
4. When-Create-Record Block
5. Pre-Block Block
6. Pre-Record Block
7. Pre-Text-Item Block
8. When-New-Block-Instance Block
9. When-New-Record-Instance Block
10. When-New-Item-Instance Form
Records Are Queried 1. Post-Query Block
2. Post-Change Block
3. Post-Change Item
4. Post-Change Block
5. Post-Change Block
Go back to Post-Query
NOTE: This cycle is repeated for each record retrieved.
No Records Are Queried 1. When-New-Record-Instance Block
2. When-New-Item-Instance Item
NOTE: To observe this Trigger Firing Order:
a. Enter a query.
b. Enter a nonexistent record.
c. Execute the query.
The two triggers listed above, the Enter Query triggers, and
the Execute Query triggers fire.
Create Record 1. Post-Change Block
2. When-Validate-Item Block
3. Post-Text-Item Block
4. When-Validate-Record Block
5. Post-Record Block
6. Post-Block Block
7. On-Savepoint Form
8. Pre-Commit Form
9. Pre-Insert Block
10. On-Insert Form
11. Post-Insert Block
12. Post-Forms-Commit Form
13. On-Commit Form
14. Post-Database-Commit Form
15. Pre-Block Block
16. Pre-Record Block
17. Pre-Text-Item Block
18. When-New-Item-Instance Form
Update Record 1. When-Database-Record Block
2. Post-Change Block
3. When-Validate-Item Block
4. Post-Text-Item Block
5. When-Validate-Record Block
6. Post-Record Block
7. Post-Block Block
8. On-Savepoint Form
9. Pre-Commit Form
10. Pre-Update Block
11. On-Update Block
12. Post-Update Block
13. Post-Forms-Commit Form
14. On-Commit Form
Here the transaction is complete and one record added.
15. Post-Database-Commit Form
16. Pre-Text-Item Block
17. When-New-Item-Instance Form
NOTE: To observe this Trigger Firing Order:
a. Execute a query.
b. Change a value.
c. Choose Action->Save from the menu.
d. Record the triggers from that point.
Delete Record 1. On-Lock Block
2. When-Remove-Record Block
3. Post-Change Block
4. Post-Change Block
5. Post-Change Block
6. Post-Change Block
7. Post-Change Block
8. Post-Change Block
9. Post-Change Item
10. Post-Query Block
11. Post-Text-Item Block
12. Post-Record Block
13. Pre-Record Block
14. Pre-Text-Item Block
15. When-New-Record-Instance Block
16. When-New-Item-Instance Form
NOTE: To observe this Trigger Firing Order, delete a detail record.

PAYMENT 처리시 PRE-INSERT TRIGGER (VALUE_ERROR)

제품 : FIN_AP
작성날짜 : 2005-05-10
11.0.3 - PAYMENT 처리시 PRE-INSERT TRIGGER (VALUE_ERROR)
==============================================
PURPOSE
Problem Description
Payment 화면에서 특정 Invoice 선택 후 저장 시 아래와 같은 Error Message 가 발생함.
Payment 화면에서 Invoice 선택 후 저장 시 FRM-40735 PRE-INSERT TRIGGER ERROR 가 발생함.
Workaround
해당 Form Version이 110.83 이전 Version일 경우 아래와 같이 Code fix 한다.
1. Payment Form Source File (APXPAWKB.fmb)는 backup 받아 놓습니다.
2. Oracle Forms 에서 해당 Form Source File 을 열어 아래 부분을 수정 합니다.
'ADJ_INV_PAY_PROC_INSERT' package 의 'SUB_PRE_INSERT' procedure 를 찾아 l_inv_remit_to 의 length를 80 으로 수정 합니다.
Example)
->수정 전
procedure SUB_PRE_INSERT is
l_withhold_amount NUMBER;
l_awt_success VARCHAR2(2000);
l_pipe_name          VARCHAR2(2000);
l_inv_remit_to     VARCHAR2(25); --> 변경 해야 할 부분
->수정 후
procedure SUB_PRE_INSERT is
return_value VARCHAR2(30);
l_withhold_amount NUMBER;
l_awt_success VARCHAR2(2000);
l_pipe_name          VARCHAR2(2000);
l_inv_remit_to     VARCHAR2(80);
3. 위와 같이 수정 후 해당 Form Source 를 Compile 하고 Generate 합니다.
4. 다시 해당 Payment에 대해서 Invoice 를 Apply 해서 Error 가 발생하는지 여부를 확인 합니다.
Solution Description
11.0.3 AP D Patchset 이상을 적용한다.
Reference Documents
Bug 921350

Navigation is not allowed in this kind of triggers.
PRE-INSERT is used to, for instance, put values on non NULL column in the current record.
If you want to navigate in the records, choose another trigger, like KEY-COMMIT for example.
Francois

Sequence number in Trigger

I'm trying to create an insert trigger that will do the following:
1.) Grab the next sequence number from a sequence and use it as the value for the id_number column.
2.) Grab the SYSDATE and use it as the value for the create_date column.
I'm using Oracle 8.1.6 on HP-UX. Here's my syntax, so far:
CREATE OR REPLACE TRIGGER tI_GRANT_TEST_CHILD before INSERT on GRANT_TEST_CHILD for each row
declare curDate DATE;
declare idNumber NUMBER;
begin
     SELECT SYSDATE into curDate FROM DUAL;
     SELECT GRANT_TEST_SEQ.NEXTVAL into idNumber FROM DUAL;
     :new.CREATE_DATE := curDate;
     :new.ID_NUMBER := idNumber;
end;
I'm pretty new to Oracle, so I've probably got a syntax error. The trigger worked fine when I just had the create date functionality; but, I can't get the sequence stuff to work.
Also, anyone know any good links for Oracle syntax standards?
Thanks for the help.

I don't see anything wrong with the syntax in your example, but the trigger can be simplified to:
create or replace trigger ti_grant_test_child
before insert on grant_test_child
for each row
begin
select grant_test_seq.nextval
    into :new.id_number
    from dual;
:new.create_date := sysdate;
end;
/You can type SHOW ERRORS after compiling in SQL*Plus to see the actual errors.

Sequence number in pre-insert form trigger

Similar Messages

Maybe you are looking for