Instead of trigger in sap b1

Hai to all,
        I wnat to validate one field in sap b1.if that field is null then that screen  must not  allow to insert.
        For example if we doesn't enter the value for comment in A/P invoice then A/P invoice is not saved.
         It is possible when using the instead of trigger.I create the trigger for the opch table .
        If comments is null then print "enter the comment'
        else insert into opch from inserted table.
        When i add the A/P invoice with or without comment then I got the error "an internal error os occured"
Can any one helpme?
Regrads,
S.Ramya.

First of all, adding trigers to sap tables isnt allowed...
For checking use transaction notification stored procedure - its on sql server in programability, stored procedure, right click, modify
in section sith Add your code here add code
if @object_type = '18' and (@transaction_type= 'A' or @transaction_type= 'U')
begin
if 0 < (select count(docentry) from opch where docentry = @list_of_cols_val_tab_del and len(Comments
) = 0)
begin
select @error =1
select @error_message = 'error message.'
end
end
This will check the comments to be filled

Similar Messages

  • Issue in Invoking an Updatable View with Instead of Trigger

    Hi,
    I am trying to insert a record using Updatable View with Instead of Trigger. When i try to save the data, i get the below error:
    java.sql.SQLException: ORA-01403: no data found
    ORA-06512: at line 1
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:457)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
    at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:889)
    at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:476)
    at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:204)
    at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:540)
    at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:213)
    at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:1075)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1466)
    at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3752)
    at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3887)
    at oracle.jdbc.driver.OracleCallableStatement.executeUpdate(OracleCallableStatement.java:9323)
    at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1508)
    at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:172)
    at oracle.jbo.server.OracleSQLBuilderImpl.doEntityDML(OracleSQLBuilderImpl.java:432)
    at oracle.jbo.server.EntityImpl.doDMLWithLOBs(EntityImpl.java:8566)
    Can someone help me resolve this issue?
    Also it would be great if you can share Sample codes for Invoking an updatable view with instead of trigger on Save/commit.
    Regards,
    Jeevan

    As a trigger is executed in the db and not in your app it's really hard to help as you did not give any useful information.
    Have you read this blog http://stegemanoracle.blogspot.com/2006/03/using-updatable-views-with-adf.html ?
    Timo
    Edited by: Timo Hahn on 22.09.2011 09:15
    And my friend google also found http://technology.amis.nl/blog/1447/adf-business-components-resfresh-after-insertupdate-and-instead-of-triggers

  • Instead of trigger example - INSERT works but UPDATE and DELETE does not?

    Below is a demostration script of what I am trying to troubleshoot. Tests are done on 10gR2;
    conn system/system
    drop table tt purge ;
    create table tt nologging as select * from all_users ;
    alter table tt add constraint pk_tt_user_id primary key (user_id) nologging ;
    analyze table tt compute statistics for table for all indexed columns ;
    conn hr/hr
    drop database link dblink ;
    create database link dblink
    connect to system identified by system
    using 'xe.turkcell' ;
    select * from global_name@dblink ;
    drop view v_tt ;
    create view v_tt as select username, user_id, created from tt@dblink order by 2 ;
    select count(*) from v_tt ;
    COUNT(*)
    13
    drop sequence seq_pk_tt_user_id ;
    create sequence seq_pk_tt_user_id
    minvalue 1000 maxvalue 99999
    increment by 1;
    create synonym tt for tt@dblink ;
    CREATE OR REPLACE PROCEDURE prc_update_tt(old_tt v_tt%ROWTYPE, new_tt v_tt%ROWTYPE) IS
    BEGIN
    IF old_tt.user_id != new_tt.user_id THEN
    RETURN; -- primary key
    END IF;
    IF old_tt.user_id IS NOT NULL AND new_tt.user_id IS NULL THEN
    DELETE FROM tt
    WHERE user_id = nvl(old_tt.user_id,
    -99);
    RETURN;
    END IF;
    IF (old_tt.username IS NULL AND new_tt.username IS NOT NULL) OR
    (old_tt.username IS NOT NULL AND new_tt.username != old_tt.username) THEN
    UPDATE tt
    SET username = new_tt.username
    WHERE user_id = nvl(old_tt.user_id,
    -99);
    END IF;
    IF (old_tt.created IS NULL AND new_tt.created IS NOT NULL) OR
    (old_tt.created IS NOT NULL AND new_tt.created != old_tt.created) THEN
    UPDATE tt
    SET created = new_tt.created
    WHERE user_id = nvl(old_tt.user_id,
    -99);
    END IF;
    END prc_update_tt;
    CREATE OR REPLACE PROCEDURE prc_insert_tt(old_tt v_tt%ROWTYPE, new_tt v_tt%ROWTYPE) IS
    new_tt_user_id NUMBER;
    BEGIN
    SELECT seq_pk_tt_user_id.NEXTVAL INTO new_tt_user_id FROM dual;
    INSERT INTO tt
    (username, user_id, created)
    VALUES
    (new_tt.username, new_tt_user_id, new_tt.created);
    END prc_insert_tt;
    CREATE OR REPLACE PROCEDURE prc_delete_tt(old_tt v_tt%ROWTYPE, new_tt v_tt%ROWTYPE) IS
    BEGIN
    DELETE FROM tt
    WHERE user_id = nvl(old_tt.user_id,
    -99);
    END prc_delete_tt;
    CREATE OR REPLACE TRIGGER trg_iof_v_tt
    INSTEAD OF UPDATE OR INSERT OR DELETE ON v_tt
    FOR EACH ROW
    DECLARE
    new_tt v_tt%ROWTYPE;
    old_tt v_tt%ROWTYPE;
    BEGIN
    dbms_output.put_line('INSTEAD OF TRIGGER fired');
    dbms_output.put_line(':NEW.user_id ' || :NEW.user_id);
    dbms_output.put_line(':OLD.user_id ' || :OLD.user_id);
    dbms_output.put_line(':NEW.username ' || :NEW.username);
    dbms_output.put_line(':OLD.username ' || :OLD.username);
    dbms_output.put_line(':NEW.created ' || :NEW.created);
    dbms_output.put_line(':OLD.created ' || :OLD.created);
    new_tt.user_id := :NEW.user_id;
    new_tt.username := :NEW.username;
    new_tt.created := :NEW.created;
    old_tt.user_id := :OLD.user_id;
    old_tt.username := :OLD.username;
    old_tt.created := :OLD.created;
    IF inserting THEN
    prc_insert_tt(old_tt,
    new_tt);
    ELSIF updating THEN
    prc_update_tt(old_tt,
    new_tt);
    ELSIF deleting THEN
    prc_delete_tt(old_tt,
    new_tt);
    END IF;
    END trg_iof_v_tt;
    set serveroutput on
    set null ^
    insert into v_tt values ('XXX', -1, sysdate) ;
    INSTEAD OF TRIGGER fired
    :NEW.user_id -1
    :OLD.user_id
    :NEW.username XXX
    :OLD.username
    :NEW.created 30/01/2007
    :OLD.created
    1 row created.
    commit ;
    select * from v_tt where username = 'XXX' ;
    USERNAME USER_ID CREATED
    XXX 1000 31/01/2007          <- seems to be no problem with insert part but
    update v_tt set username = 'YYY' where user_id = 1000 ;
    INSTEAD OF TRIGGER fired
    :NEW.user_id
    :OLD.user_id
    :NEW.username YYY
    :OLD.username
    :NEW.created
    :OLD.created
    1 row updated.
    commit ;
    select count(*) from v_tt where username = 'YYY' ;
    COUNT(*)
    0               <- here is my first problem with update part, Oracle said "1 row updated."
    delete from v_tt where user_id = 1000 ;
    INSTEAD OF TRIGGER fired
    :NEW.user_id
    :OLD.user_id
    :NEW.username
    :OLD.username
    :NEW.created
    :OLD.created
    1 row deleted.
    commit ;
    select count(*) from v_tt ;
    COUNT(*)
    14               <- here is my second problem with delete part, Oracle said "1 row deleted."
    Any comments will be welcomed, thank you.
    Message was edited by:
    TongucY
    changed "-1" values to "1000" in the where clause of delete and update statements.
    it was a copy/paste mistake, sorry for that.

    What table do you process in your procedures ? You don't use DBLINK to
    reference remote table in your procedures.
    Seems, you have table "TT" in "HR" schema too.
    Look:
    SQL> create table tt nologging as select * from all_users where rownum <=3;
    Table created.
    SQL> select * from tt;
    USERNAME                          USER_ID CREATED
    SYS                                     0 25-APR-06
    SYSTEM                                  5 25-APR-06
    OUTLN                                  11 25-APR-06
    SQL> conn scott/tiger
    Connected.
    SQL> create database link lk65 connect to ... identified by ... using 'nc65';
    Database link created.
    SQL> select * from tt@lk65;
    USERNAME                          USER_ID CREATED
    SYS                                     0 25-APR-06
    SYSTEM                                  5 25-APR-06
    OUTLN                                  11 25-APR-06
    SQL> create view v_tt as select username, user_id, created from tt@lk65 order by 2;
    View created.
    SQL> select * from v_tt;
    USERNAME                          USER_ID CREATED
    SYS                                     0 25-APR-06
    SYSTEM                                  5 25-APR-06
    OUTLN                                  11 25-APR-06
    SQL> create sequence seq_pk_tt_user_id
      2  minvalue 1000 maxvalue 99999
      3  increment by 1;
    Sequence created.
    SQL> CREATE OR REPLACE PROCEDURE prc_insert_tt(old_tt v_tt%ROWTYPE, new_tt v_tt%ROWTYPE) IS
      2  new_tt_user_id NUMBER;
      3  BEGIN
      4  SELECT seq_pk_tt_user_id.NEXTVAL INTO new_tt_user_id FROM dual;
      5  INSERT INTO tt
      6  (username, user_id, created)
      7  VALUES
      8  (new_tt.username, new_tt_user_id, new_tt.created);
      9  END prc_insert_tt;
    10  /
    Warning: Procedure created with compilation errors.
    SQL> show error
    Errors for PROCEDURE PRC_INSERT_TT:
    LINE/COL ERROR
    5/1      PL/SQL: SQL Statement ignored
    5/13     PL/SQL: ORA-00942: table or view does not exist
    SQL> edit
    Wrote file afiedt.buf
      1  CREATE OR REPLACE PROCEDURE prc_insert_tt(old_tt v_tt%ROWTYPE, new_tt v_tt%ROWTYPE) IS
      2  new_tt_user_id NUMBER;
      3  BEGIN
      4  SELECT seq_pk_tt_user_id.NEXTVAL INTO new_tt_user_id FROM dual;
      5  INSERT INTO tt@lk65
      6  (username, user_id, created)
      7  VALUES
      8  (new_tt.username, new_tt_user_id, new_tt.created);
      9* END prc_insert_tt;
    SQL> /
    Procedure created.Rgds.

  • How can I retrieve the condition in an update or delete using instead of trigger

    I have 2 tables, on which a view is created. To distinguish the tables within the view trigger, a column "source" had been added in the view creation. I want to be able to delete row(s) in table t1 or table t2 through the view, depending on a condition. The problem is that I don't know how I can get back the delete condition IN the INSTEAD of trigger :
    CREATE TABLE t1(m NUMBER, n VARCHAR2(10), o date);
    CREATE TABLE t2(a NUMBER, b VARCHAR2(10), c date);
    -- The view is created based on the 2 tables.
    CREATE OR REPLACE VIEW vt12 AS
    SELECT 't1' source, m, n, o
    FROM t1
    UNION
    SELECT 't2' source, a, b, c
    FROM t2;
    -- The trigger will fire whenever INSERT is performed on the tables through the view
    create or replace trigger tvt12 instead of insert or delete on vt12
    begin
    if inserting then
    if :new.source = 't1' then
    insert into t1 values (:new.m, :new.n, :new.o);
    else
    -- will insert a default value of -1 for the fourth column "d"
    insert into t2(a,b,c,d) values (:new.m, :new.n, :new.o, -1);
    end if;
    elsif deleting then
    -- We don't know the condition for the deletion, so all rows from the
    -- table from which the current row is coming will be deleted
    if :old.source = 't1' then
    delete t1;
    else
    delete t2;
    end if;
    end if;
    end;
    show error
    insert into vt12 values ('t1',1,'1',sysdate);
    insert into vt12 values ('t2',2,'2',sysdate+1);
    insert into vt12 values ('t1',3,'3',sysdate+2);
    insert into vt12 values ('t2',4,'4',sysdate+3);
    insert into vt12 values ('t1',5,'5',sysdate+4);
    insert into vt12 values ('t2',6,'6',sysdate+5);
    commit;
    select * from vt12;
    select * from t1;
    select * from t2;
    delete vt12 where m = 1;
    commit;
    select * from vt12;
    select * from t1;
    select * from t2;
    When I execute this script, the delete statement seems to recognize that the condition is affecting a row in table t1, and therefore deletes all rows from the table, as specified in the delete statement of the trigger... But, what I want to do is ONLY to delete the row affected by the original condition. So my question is to know how I can get back the original condition for the delete, and still use it in the trigger, that will be executed INSTEAD of the delete statement.. I checked in the doc, and everywhere an example of INSTEAD OF trigger can be found, but it's always and only using an INSTEAD OF INSERT trigger, which doesn't need a condition.
    Can anyone help ?
    null

    I've never faced this case myself, but from the documentation it would seem that the INSTEAD OF DELETE is also a FOR EACH ROW trigger. Therefore, you don't really have to worry about the actual "where" clause of the original "delete" operation: Oracle has it all parsed for you, so you just need to redirect, in turn, each view record being deleted to the appropriate table.
    In extenso: for your
    delete vt12 where m = 1;
    => the INSTEAD OF trigger fires once for all records in vt12 where m=1, and I would guess that you trigger code should look like:
    begin
    delete from t1 where m = :old.m and n = :old.n and o = :old.o;
    delete from t2 where a = :old.m and b = :old.n and c = :old.o;
    end;
    It's a bit of overkill compared to the "where" clause of the original "delete" statement, but it should do the job...
    BTW, if by any luck you do have some primary key on tables t1 and t2 (say: columns o and c respectively), then obviously you can make the thing simpler:
    begin
    delete from t1 where o = :old.o;
    delete from t2 where c = :old.o;
    end;
    HTH - Didier

  • INSTEAD OF trigger on view to update a table. error in 4.2apex tabular rpt

    I have created a view (LANDINGS_VIEW') that I am hoping to use to add/modify data over several tables. I am using INSTEAD OF trigger to update/insert into the underlying tables. I am receiving the error:
    •ORA-01858: a non-numeric character was found where a numeric was expected ORA-06512: at "SAFIS.LANDINGS_V_IO_UPD_TRG", line 4 ORA-04088: error during execution of trigger 'SAFIS.LANDINGS_V_IO_UPD_TRG' (Row 1)I am only setting PRICE = 300.
    any thoughts? Am I setting this up propertly? thanks for your help!!
    Karen
    The LANDING_VIEW is set up as follows:
    -- Start of DDL Script for View SAFIS.LANDINGS_VIEW
    -- Generated 03-May-2013 10:25:38 from [email protected]
    CREATE OR REPLACE VIEW landings_view (
       landing_seq,
       dealer_rpt_id,
       unit_measure,
       reported_quantity,
       landed_pounds,
       dollars,
       disposition_code,
       grade_code,
       species_itis,
       market_code,
       price,
       area_fished,
       sub_area_fished,
       lease_num,
       gear_code,
       de,
       ue,
       dc,
       uc,
       local_area_code,
       fins_attached,
       explanation,
       late_report,
       modified_data,
       nature_of_sale,
       hms_area_code,
       sale_price,
       deleted )
    AS
    select l.LANDING_SEQ,
           l.DEALER_RPT_ID,
           l.UNIT_MEASURE,
           l.REPORTED_QUANTITY,
           l.LANDED_POUNDS,
           l.DOLLARS,
           l.DISPOSITION_CODE,
           l.GRADE_CODE,
           l.SPECIES_ITIS,
           l.MARKET_CODE,
           l.PRICE,
           l.AREA_FISHED,
           l.SUB_AREA_FISHED,
           l.LEASE_NUM,
           l.GEAR_CODE,
           l.DE,
           l.UE,
           l.DC,
           l.UC,
           l.LOCAL_AREA_CODE,
           a.fins_attached,
           a.explanation,
           a.late_report,
           a.modified_data,
           a.nature_of_sale,
           a.hms_area_code,
           a.sale_price,
           a.deleted
      from landings l,
           landings_hms a
      where  l.dealer_rpt_id = v('P110_DEALER_RPT_ID') and
            l.dealer_rpt_id = a.dealer_rpt_id(+) and
            l.landing_seq = a.landing_seq(+)
    -- Triggers for LANDINGS_VIEW
    CREATE OR REPLACE TRIGGER landings_v_io_upd_trg
    INSTEAD OF
      UPDATE
    ON landings_view
    REFERENCING NEW AS NEW OLD AS OLD
    DECLARE
       v_first_day   date;
       BEGIN
    update landings set landing_seq = :old.landing_seq,
                              dealer_rpt_id = :old.dealer_rpt_id,
                              unit_measure = :new.unit_measure,
                              reported_quantity = :new.reported_quantity,  
                            --  landed_pounds = :new.landed_pounds,
                              dollars = :new.dollars,
                              disposition_code= :new.disposition_code, 
                              grade_code = :new.grade_code,
                              species_itis =  :new.species_itis,
                               market_code = :new.market_code,
                              price =  :new.price,
                              area_fished = :new.area_fished,
                              sub_area_fished = :new.sub_area_fished,
                           --   lease_num = :new.lease_num,
                              gear_code = :new.gear_code,
                              de = :new.de,
                              ue = :new.ue,
                              dc = :new.ue,
                              uc = :new.uc,
                              local_area_code =  :new.local_area_code ;     
        /*  update landings_hms  set dealer_rpt_id = :old.dealer_rpt_id,
                                 landing_seq = :old.landing_seq,
                                 fins_attached = :new.fins_attached,
                                 explanation = :new.explanation,
                                 late_report = :new.late_report,
                                 modified_data = :new.modified_data,
                                 nature_of_sale = :new.nature_of_sale,
                                 hms_area_code = :new.hms_area_code,
                                 sale_price = :new.sale_price,
                                 de = sysdate,
                                 ue = :new.ue,
                                 dc = :new.dc,
                                 uc = :new.uc ;                         
    end;
    -- End of DDL Script for Trigger SAFIS.LANDINGS_KEH_V_IO_TRG
    CREATE OR REPLACE TRIGGER landings_v_io_trg
    INSTEAD OF
      INSERT
    ON landings_view
    REFERENCING NEW AS NEW OLD AS OLD
    DECLARE
       v_first_day   date;
       BEGIN
    insert into landings_keh (landing_seq,
                              dealer_rpt_id,
                              unit_measure,
                              reported_quantity,
                              landed_pounds,
                              dollars,
                              disposition_code,
                              grade_code,
                              species_itis,
                              market_code,
                              price,
                              area_fished,
                              sub_area_fished,
                              lease_num,
                              gear_code,
                              de,
                              ue,
                              dc,
                              uc,
                              local_area_code)      
       values ( landings_seq.NEXTVAL,
                :new.dealer_rpt_id,
                :new.unit_measure,
                :new.reported_quantity,
                :new.landed_pounds,
                :new.dollars,
                :new.disposition_code,
                :new.grade_code,
                :new.species_itis,
                :new.market_code,
                :new.price,
                :new.area_fished,
                :new.sub_area_fished,
                :new.lease_num,
                :new.gear_code,
                sysdate,
                :new.ue,
                :new.dc,
                :new.uc,
                :new.local_area_code)  ;
       insert into landings_hms (dealer_rpt_id,
                                 landing_seq,
                                 fins_attached,
                                 explanation,
                                 late_report,
                                 modified_data,
                                 nature_of_sale,
                                 hms_area_code,
                                 sale_price,
                                 de,
                                 ue,
                                 dc,
                                 uc,
                                 deleted)
           values (:new.dealer_rpt_id,
                   landings_seq.CURRVAL,
                   :new.fins_attached,
                   :new.explanation,
                   :new.late_report,
                   :new.modified_data,
                   :new.nature_of_sale,
                   :new.hms_area_code,
                   :new.sale_price,
                   sysdate,
                   :new.ue,
                   :new.dc,
                   :new.uc,
                   :new.deleted);
    end;
    -- End of DDL Script for Trigger SAFIS.LANDINGS_KEH_V_IO_TRG
    -- End of DDL Script for View SAFIS.LANDINGS_VIEWbtw, I have succefully run the following update in sqlplus.
    update landings set landing_seq = 8604583,
    dealer_rpt_id = 2660038,
    unit_measure = 'LB',
    reported_quantity = 3,
    -- landed_pounds = :new.landed_pounds,
    dollars = 900,
    disposition_code= '001',
    grade_code = '10',
    species_itis = '160200',
    market_code = 'UN',
    price = 30,
    area_fished = null,
    sub_area_fished =null,
    -- lease_num = :new.lease_num,
    gear_code = '050',
    de = sysdate,
    ue = 'keh',
    dc = null,
    uc = 'keh',
    local_area_code = null
    where landing_seq = 8604583; I am using apex 4.2
    Edited by: KarenH on May 3, 2013 10:29 AM
    Edited by: KarenH on May 3, 2013 10:31 AM
    Edited by: KarenH on May 3, 2013 11:04 AM
    Edited by: KarenH on May 3, 2013 4:09 PM

    could it be so simple?
    when I created the tabular form on my view, LANDINGS_VIEW, the APPLYmru was automatically generated, referencing the view name LANDINGS_VIEW. I modified that to indicate the table name (LANDINGS). I am not certain why that would work, but it seems to so far.
    this post was helpful: Re: instead of trigger on view
    I am now testing to make certain both the underlying tables can be updated, LANDINGS and LANDINGS_HMS

  • Insert order by records into a view with a instead of trigger

    Hi all,
    I have this DML query:
    INSERT INTO table_view t (a,
                              b,
                              c,
                              d,
                              e)
          SELECT   a,
                   b,
                   c,
                   d,
                   e
            FROM   table_name
        ORDER BY   dtable_view is a view with an INSTEAD OF trigger and table_name is a table with my records to be inserted.
    I need the ORDER BY clause because in my trigger i call a procedure who treat each record and insert into a table, used in the view. I need to garantee these order.
    If i put an other SELECT statement outside, like this:
    INSERT INTO table_view t (a,
                              b,
                              c,
                              d,
                              e)
          SELECT   a,
                   b,
                   c,
                   d,
                   e
            FROM   table_name
        ORDER BY   dIt works. But I can put these new SELECT because these query is created automatic by Oracle Data Integrator.
    What I'm asking you is if there any solution to this problem without changing anything in the Oracle Data Integrator. Or, in other words, if there is any simple solution other than to add a new SELECT statement.
    Thanks in advance,
    Regards.

    Sorry... copy+paste error :)
    INSERT INTO table_view t (a,
                              b,
                              c,
                              d,
                              e)
        SELECT   *
          FROM   (  SELECT   a,
                             b,
                             c,
                             d,
                             e
                      FROM   table_name
                  ORDER BY   d)I need to insert him by a D column order, because my trigger needs to validate each record and insert him. I have some restrictions. For example, my records are:
    2     1     2006     M
    1     2     2007 M
    1     3     2007     S 2007
    1     2     2007     S 2007
    2     1     2009     S
    2     1     2009     S
    I want to insert the 'M' records first and then the 'S' records because the 'S' records only makes sense in target table is exists 'M' records
    Regards,
    Filipe Almeida

  • Issue with instead of trigger on a view

    Gurus,
    I have an issue with an instead of trigger on a view. The trigger is listed below. The insert and update seem to be working fine but the delete section is not.
    From the application, we have a screen on which we attach images. We trigger of an insert and update when we attach images. We are using hibernate as our object relational mapping tool.
    We have added some logging into the delete section but that portion of the trigger does not seem to be executing at all.
    Please advise.
    Thanks
    Hari
    CREATE OR REPLACE TRIGGER trg_vw_result_image_uid
    INSTEAD OF
    INSERT OR DELETE OR UPDATE
    ON vw_result_image
    REFERENCING NEW AS NEW OLD AS OLD
    DECLARE
    v_cnt number(38);
    v_cnt_old number(38);
    v_err_msg VARCHAR2 (250);
    BEGIN
    -- v_rslt_id number(38);
    -- v_cnt number(38);
    select count(1) into v_cnt from result_image_master
    where RSLT_IMAGE_ID = :new.RSLT_IMAGE_ID;
    --select count(1) into v_cnt from result_image_master
    -- where ACC_BLKBR_ID = :new.ACC_BLKBR_ID
    -- and upper(RSLT_IMAGE_NM) = upper(:new.RSLT_IMAGE_NM);
    select count(1) into v_cnt_old from result_image_master
    where RSLT_IMAGE_ID = :old.RSLT_IMAGE_ID;
    insert into t2( TEXT_VAL, DT1, seq1)
    values (' before v_cnt', sysdate, t6.NEXTVAL);
    --if v_cnt = 0
    --****INSERTING
    IF INSERTING
    THEN
    insert into t2( TEXT_VAL, DT1, seq1)
    values (' v_cnt is 0 and inserting into result_image_master', sysdate, t6.NEXTVAL);
    insert into t2( TEXT_VAL, DT1, seq1)
    values (' inserted bb id :'||:new.ACC_BLKBR_ID, sysdate, t6.NEXTVAL);
    insert into result_image_master (
    RSLT_IMAGE_ID
    ,RSLT_IMAGE_HBR_VER
    ,RSLT_IMAGE_TYPE_ID
    ,RSLT_IMAGE_NM
    ,RSLT_IMAGE_LABEL
    ,RSLT_IMAGE_SEQ
    ,RSLT_SHOW_ON_RPT
    ,RSLT_SLIDE_NO
    ,RSLT_CELL_NO
    ,RSLT_X_COORD
    ,RSLT_Y_COORD
    ,ACC_BLKBR_ID
    ,CREATED_BY
    ,DATE_CREATED
    ,MODIFIED_BY
    ,DATE_MODIFIED
    values (
    :new.RSLT_IMAGE_ID
    ,:new.RSLT_IMAGE_HBR_VER
    ,:new.RSLT_IMAGE_TYPE_ID
    ,:new.RSLT_IMAGE_NM
    ,:new.RSLT_IMAGE_LABEL
    ,:new.RSLT_IMAGE_SEQ
    ,:new.RSLT_SHOW_ON_RPT
    ,:new.RSLT_SLIDE_NO
    ,:new.RSLT_CELL_NO
    ,:new.RSLT_X_COORD
    ,:new.RSLT_Y_COORD
    ,:new.ACC_BLKBR_ID
    ,:new.CREATED_BY
    ,:new.DATE_CREATED
    ,:new.MODIFIED_BY
    ,:new.DATE_MODIFIED
    insert into result_image_blob (
    RSLT_IMAGE_ID
    ,rslt_image_blob
    values (
    :new.RSLT_IMAGE_ID
    ,:new.rslt_image_blob
    --****UPDATING
    ELSIF UPDATING
    -- v_cnt > 0 --
    THEN
    insert into t2( TEXT_VAL, DT1, seq1)
    values (' updating result_image_master', sysdate, t6.nextval);
    insert into t2( TEXT_VAL, DT1, seq1)
    values (' updating bb id :'||:new.ACC_BLKBR_ID, sysdate, t6.nextval);
    update result_image_master
    set RSLT_IMAGE_HBR_VER = RSLT_IMAGE_HBR_VER + 1
    ,RSLT_IMAGE_TYPE_ID = :new.RSLT_IMAGE_TYPE_ID
    ,RSLT_IMAGE_NM = :new.RSLT_IMAGE_NM
    ,RSLT_IMAGE_LABEL = :new.RSLT_IMAGE_LABEL
    ,RSLT_IMAGE_SEQ = :new.RSLT_IMAGE_SEQ
    ,RSLT_SHOW_ON_RPT = :new.RSLT_SHOW_ON_RPT
    ,RSLT_SLIDE_NO = :new.RSLT_SLIDE_NO
    ,RSLT_CELL_NO = :new.RSLT_CELL_NO
    ,RSLT_X_COORD = :new.RSLT_X_COORD
    ,RSLT_Y_COORD = :new.RSLT_Y_COORD
    ,ACC_BLKBR_ID = :new.ACC_BLKBR_ID
    ,MODIFIED_BY = :new.MODIFIED_BY
    ,DATE_MODIFIED = :new.DATE_MODIFIED
    where RSLT_IMAGE_ID = :new.RSLT_IMAGE_ID;
    update result_image_blob
    set rslt_image_blob = :new.rslt_image_blob
    where RSLT_IMAGE_ID = :new.RSLT_IMAGE_ID;
    END IF;
    IF DELETING OR v_cnt_old > 0
    THEN
    insert into t2( TEXT_VAL, DT1, seq1) values (' deleting rows ...', sysdate, t6.NEXTVAL);
    DELETE from result_image_blob where RSLT_IMAGE_ID = :old.RSLT_IMAGE_ID;
    insert into t2( TEXT_VAL, DT1, seq1) values ('deleting result_image_blob : '||:old.RSLT_IMAGE_ID , sysdate, t6.NEXTVAL);
    DELETE from result_image_master where RSLT_IMAGE_ID = :old.RSLT_IMAGE_ID;
    insert into t2( TEXT_VAL, DT1, seq1) values ('deleting result_image_master : '||:old.RSLT_IMAGE_ID , sysdate, t6.NEXTVAL);
    END IF;
    EXCEPTION
    WHEN OTHERS THEN
    v_err_msg := SQLERRM;
    insert into t2( TEXT_VAL, DT1, seq1) values (v_err_msg, sysdate, t6.nextval);
    END;
    Edited by: bhanujh on Sep 13, 2010 7:55 AM

    bhanujh wrote:
    The error msg that we are getting is
    09/08/2010 4:02:09 PM: Unable to save the results :: Could not execute JDBC batch updateSorry, we don't recognize this message as any valid Oracle error.
    :p

  • Instead of trigger on geometry

    Hello
    I am trying to setup an environment to access oracle spatial data in AutoDesk Map 3D 2007 using OSE (Oracle Spatial Extension). For this i created a base schema containing a spatial table and I created another schema containing autodesk metadata tables and created a view of the spatial data in the base schema. The view is granted ALL permissions on the spatial table by base schema
    The reason for creating view is to accomodate virtual columns like ADMPLAYER, ADMPOBJECTTYPE etc. Now i created an instead of trigger so that when user updates any attribute, creates or deletes any data in the view, it automatically modifies the original tables.
    The insert and delete works fine.Even update for attributes works fine, but fails when i update a geometry.
    How can i put a condition in the trigger to check if geometry is updated? so i update it accordingly? I tried SDO_EQUAL function by passing old and new geometry values but it fails stating that i can use this operator only if spatial index exist. In my setup the view and original table are in different schemas.
    How can i check if geometry is updated in the trigger?
    Regards
    sam

    Hello Luc
    Thanks for your suggestion . I checked this for SDO_Geometry and it worked... Please find below the trigger
    CREATE OR REPLACE TRIGGER TEMP_BEF_IUD INSTEAD OF INSERT OR UPDATE OR DELETE ON V_TEMP
    FOR EACH ROW
    BEGIN
    --When inserting a new record in the view..this part of the trigger will get fired
    IF INSERTING THEN
         INSERT INTO test.TEMP(TEMPID, NAMEID,     UNITSURFACE, ) VALUES (:NEW.TEMPID, :NEW.NAMEID, :NEW.UNITSURFACE);
    END IF;
    --When deleting an existing record...this part of the trigger will be fired
    IF DELETING THEN
    DELETE FROM test.TEMP WHERE TEMPID=:OLD.TEMPID;
    END IF;
    --When updating existing data, this part of the trigger will be fired. When updating it checks for each field to
    --determine which field is actually updated and then it fires update statement..accordingly.
    IF UPDATING THEN
    --Checking each field for update
         IF :OLD.TEMPid <> :NEW.TEMPid THEN
         RAISE_APPLICATION_ERROR(-20005,'TEMPID cannot be updated.This IS SYSTEM generated ID....
         EXCEPTION CODE: '||SQLCODE||' EXCEPTION MSG: '||SQLERRM);
         END IF;
         IF :OLD.NAMEID <> :NEW.NAMEID THEN
         UPDATE test.TEMP SET NAMEID = :NEW.NAMEID WHERE TEMPid=:OLD.TEMPid;
         END IF;
         IF UPDATING('UNITSURFACE') THEN
         UPDATE test.emirate SET UNITSURFACE = :NEW.UNITSURFACE WHERE TEMPid=:OLD.TEMPid;
         END IF;
    END IF;
    END TEMP_BEF_IUD;
    /

  • Instead of Trigger for tabular form

    I have a tabular layout on a form that returns data from a database view. Based on user interaction I would like to update the underlying view records that are returned by a query in the form using an INSTEAD OF trigger. I have my trigger working, however I can only get it to update the first record of the tabular layout item on the form. I realize that INSTEAD OF triggers are row level triggers, but is there a way to get this trigger to fire for multiple records? I've written a simple update statement in the form that updates the view: update newborn.nb_ltfu_positive_v
    set export_dt = sysdate
    where barcode = :nb_ltfu_positive_v.barcode;
    and my INSTEAD OF trigger looks like this: if :old.export_dt <> :new.export_dt then
    update nbpat set export_dt = sysdate
    where spec = :old.spec;
    end if;
    if :old.export_dt <> :new.export_dt then
    update nbhear_audiotest set export_dt = sysdate
    where barcode = :old.barcode;
    end if;
    Do I need to do some looping in the trigger?
    Any assistance would be greatly appreciated.
    Thanks

    No you cannot do any looping in the database trigger. The database trigger will for every record which is involved in an UPDATE issued againt the view.
    The problem is your code inside the form. In general you do not issue "manual" update against a table/view in forms, but let forms do so. So, if you want to update a record in a tabular block in forms you would just assign the new value to the forms-item, such as
    :BLOCK.EXPORT_DT:=SYSDATE;in your example. This code marks the "active" reocrd in the block as "to be updated" in the next transactions, mean when the user presses "Save". If you want to update multiple records in forms, this is either done when the user navigates between different record and then does some changes in the block-fields, or if you want to do it "programmatical", by looping over the block, something like:
    FIRST_RECORD;
    LOOP
      EXIT WHEN :SYSTEM.RECORD_STATUS ='NEW';
      -- do some stuff on the current record, exampel code
      :BLOCK.EXPORT_DT:=SYSDATE;
      EXIT WHEN :SYSTEM.LAST_RECORD='TRUE';
      NEXT_RECORD;
    END LOOP;hope this helps

  • INSTEAD OF TRIGGER

    제품 : PL/SQL
    작성날짜 : 1999-07-13
    INSTEAD OF Trigger
    1. 개념
    INSTEAD OF trigger는 Oracle8에서 새로이 소개된 방법으로, DML문장에 의해
    직접 변경할 수 없는 view를 변경하기 위해 사용된다. 즉, base table이 fire
    하는 trigger를 생성하는 것이 아니고 view를 대상으로 trigger를 생성하여
    view에 대한 DML문장을 수행시 대신 trigger가 fire되어 base table을 직접
    변경하게 되는 것이다.
    기본적으로 DML이 불가능한 view는 다음 사항들을 포함하고 있는 경우이
    다. 이러한 사항을 포함한 view들에 대해서 instead of trigger를 생성하면 DML을
    수행할 수 있게 된다.
    (1) DISTINCT operator
    (2) group functions: AVG, COUNT, MAX, MIN, STDDEV, SUM, VARIANCE등
    (3) set operations: UNION, MINUS 등
    (4) GROUP BY, CONNECT BY, START WITH clauses
    (5) ROWNUM pseudocolumn
    (6) join (updatable join view인 경우는 제한적으로 DML수행가능 <Bul:11642>참
    조)
    2. EXAMPLE
    instead of trigger의 예를 다음과 같이 작성하였다.
    (1) base tables
    create table dept
    (deptno number(4) primary key,
    dname varchar2(14),
    loc varchar2(13));
    create table emp
    (empno number(4),
    ename varchar2(10),
    sal number(7,2),
    mgr number(4),
    deptno number(2) );
    (2) 직접 dml을 수행할 수 없는 view
    create view emp_dept
    as select empno, ename, sal, emp.deptno, dname
    from emp, dept where emp.deptno=dept.deptno;
    [참고] 이 예에서 dept table의 deptno가 primary key나 unique로 선언되어 있
    다면 emp_dept view는 updatable join view가 되어 key-reserved table인 emp table
    에 대한 dml은 trigger를 사용하지 않아도 직접 수행 가능하다. <Bul:11642>참

    (3) instead of trigger
    view에 DML을 수행시 내부적으로 수행되기를 원하는 logic을 임의로 user가
    작성하면 된다.
    아래의 예에서는 emp_dept에 insert문장을 수행하는 경우 기존에 존재하는
    dept정보에 대해서는 update를 수행하고, 새로은 dept정보는 insert하도록 하였다.
    그리고 emp table에 대해서는 empno가 primary key이므로 중복되는 row는
    자동으로 오류가 발생하게 되며, 새로운 값을 insert하게 되면
    emp table에 직접 insert를 하게 된다.
    create or replace trigger emp_dept_insert
    instead of insert on emp_dept
    referencing new as n
    for each row
    declare
    dept_cnt number;
    begin
    if :n.empno is not null then
    insert into emp(empno, ename, sal)
    values (:n.empno, :n.ename, :n.sal);
    end if;
    if :n.deptno is not null then
    select count(*) into dept_cnt
    from dept where deptno = :n.deptno;
    if dept_cnt > 0 and (:n.dname is not null) then
    update dept set dname = :n.dname where deptno = :n.deptno;
    else insert into dept(deptno, dname) values(:n.deptno, :n.dname);
    end if;
    end if;
    end;
    (4) DML statement
    다음과 같이 insert 문장을 view에 수행하면 emp_dept_insert trigger가
    fire되어 실제 emp와 dept table에 반영이 되어 emp_dept view에 insert가
    수행된 것 같이 보이게 된다.
    insert into emp_dept values (5000, 'EYKIM', 100, 10, 'SALES');
    insert into emp_dept(empno, ename, deptno) values (6000, 'YOUNKIM', 20);
    insert into emp_dept (empno, deptno, dname) values (7000, 50, 'NEW_DEPT');

    No, the INSTEAD OF trigger is on the View, and so only fires if you perform Insert/Update/Delete on the View.

  • Instead of Trigger not working as expected

    We use a view v_test ( union on two tables ) with an Instead of Trigger for insert. The Instead of Trigger just inserts data into one of the underlying tables.
    If we insert a single row ( insert into v_test(...) values(...) ) everything works fine.
    If we insert multiple rows using one statement ( insert into v_test(...) select ...) some columns have same values although they should be different.
    (tested on Oracle 9 and 10)

    here is an example (Oracle Version is 9.2.0.6.0):
    view vtest_:
    SELECT *
    FROM (SELECT * FROM EM_TRANSPORTMITTEL_B
    UNION
    SELECT * FROM EM_TRANSPORTMITTEL_H)
    WHERE Nvl(To_Date(pa_session.f_getContext('hist_date'), 'dd.mm.yyyy hh24:mi:ss'), SYSDATE) BETWEEN hist_from AND hist_to
    Instead of Trigger:
    CREATE OR REPLACE TRIGGER tib_v_test instead of insert on v_test for each row
    declare
    l_cols EM_TRANSPORTMITTEL_B%rowtype;
    begin
    l_cols.EM_TRANSPORTMITTELID := :new.EM_TRANSPORTMITTELID;
    l_cols.tmtyp := :new.tmtyp;
    insert into EM_TRANSPORTMITTEL_B (em_transportmittelid, tmtyp, ....) values (l_cols.em_transportmittelid, l_cols.tmtyp, ....)
    end tib_v_test;
    Insert Statement
    insert into v_test (em_transportmittelid, tmtyp, ...)
    select em_transportmittelid, 'WAGEN' tmtyp, ...
    from tmp_tmstamm
    order by wagenummer;

  • INSTEAD OF TRIGGER (UPDATE): new.field null or not set

    When using an instead of trigger for an update on a view, you can "relate" the updates to the (another) base table(s).
    to perform the update statement you have the use the ":new.field" notation.
    Is there a way to determine if the field value is included in the update statement that causes the trigger to be fired?
    I know you can check this value and see if it's null but this is not the same as "not used in the set clauses". It can be explicitly set to null : SET field = NULL
    which can be used like SET FIELD = :new.field
    but what if it is not "used" in the update statement at all.?
    Here is a (simplified example)
    CREATE OR REPLACE VIEW TATB
    As
    SELECT TA.FIELD1, TA.FIELD2, TB.FIELD3, TB.FIELD4
    FROM TABLEA TA, TABLEB TB
    WHERE TA.ID = TB.ID
    THIS is an update statement
    UPDATE TATB
    SET FIELD1='JOS', FIELD2='FONS'
    this could be another one
    UPDATE TATB
    SET FIELD1='JOS', FIELD2='FONS' FIELD3 = NULL
    HOW can the distinction be checked (in the body of the instead of trigger) that in update statement 1, the new.field3 is not set at all and in the second one the new.field3 is explicitly set to null
    tx
    Luc

    I found after re-reading the documentation that when using an update it is possible to use the check UPDATING in concordance with the column name:
    IF UPDATING('field1') THEN
    END IF;
    tx
    Luc

  • Instead of Trigger Problems

    Good morning and thanks in advance for the help.  I'm new to oracle and sql in general, so bear with me if my create statements are wrong.  I am using Oracle 11g.
    I am trying to create a trigger to do an update on a timesheet view in APEX.  The view draws from the assignment table and needs to store the data in the timesheet table.
    CREATE TABLE assignment (
       assignment_id   number
       employee_id   number
       project_id   number)
    CREATE TABLE timesheet (
       timesheet_id  number
       assignment_id  number
       week_start_date  date
       hours   number)
    INSERT ALL
      INTO assignment (employee_id, project_id) VALUES (1, 1)
      INTO assignment (employee_id, project_id) VALUES (1, 2)
      INTO assignment (employee_id, project_id) VALUES (2, 1)
      INTO assignment (employee_id, project_id) VALUES (3, 2)
    CREATE OR REPLACE FOR VIEW timesheet_view AS
    SELECT *
    FROM (SELECT A.assignment_id, project_id, employee_id, week_start_date, hours
          FROM timesheet T
          RIGHT OUTER JOIN assignment A
            ON T.assignment_id = A.assignment_id)
    PIVOT (MAX(hours) FOR week_start_date IN (to_date('06/03/2013', 'MM/DD/YYYY') AS "06/03/2013",
    to_date('06/10/2013', 'MM/DD/YYYY') AS "06/10/2013",
    to_date('06/17/2013', 'MM/DD/YYYY') AS "06/17/2013",
    to_date('06/24/2013', 'MM/DD/YYYY') AS "06/24/2013")
    The view has many more columns since this needs to track weeks until they decide to stop using the app.
    The view thus looks like this:
    assignment_id  project_id  employee_id  06/03/2013  06/10/2013  06/17/2013  06/24/2013
    1                      1                1                 25               15              15              15
    2                      2                1                 15               25              25              -
    3                      1                2                 40               40              40              40
    4                      2                3                 40               -                40              -
    So my question is, how do I create a trigger to insert into the timesheet table? I know how to create an instead of trigger, but what I don't know how to do is reference the column names for the date and then take the data that has been updated in each and store that in the timesheet table with the column name going in the week_start_date column and the value from the row at that column going into the hours column.  I'd love to be able to do it dynamically since adding a line to the trigger for every single date would be quite unruly.
    Any help is greatly appreciated.

    Yuck.  But you are hardcoding dates as columns into the view, so you'll have to change the view sometime anyway?  Could you not generate columns based on the MODEL clause?
    Alternatively, have you considered adding a hidden (from the front end) column (weekno) for each date column to your view, but hiding it; in that column you could hardcode the date for the following column?
    assignment_id  project_id  employee_id  week1dt         06/03/2013 week2dt          week3dt       06/10/2013  etc.
    1                      1                1                06/10/2013    125             06/17/2013      06/10/2013    15           
    edit: I was just wondering about an alternative: if you could prepend the week date (eg "06/03/2013") to the hours data for the row/column (e.g. "06/03/2013,40") then substring the hours (split on ",") in the APEX view, but you would have the weekdate to be able to use in your table update.  Just a thought; I've no experience with APEX.

  • Instead-of Trigger Complication.

    Hi folks,
    Please look at the following table to have a clear picture,
    I have 2 schemas namely, A and B.
    I have 2 objects also X and Y. These are tables in schema A but these same tables (with same structures and data also ) are views in schema B.
    In epitome, these X and Y views in schema B refer X and Y objects in schema A.
    I have a trigger in schema A wherein before the updation of X, the trigger updates table Y. This is working fine.
    Now, I have to write trigger T in schema B wherein before the updation of X, the trigger updates Y. But since both X and Y are views, obviously the trigger should be an INSTEAD-OF trigger and I want ot update the table Y in schema A (because Y in schema B is a view)
    In the update statement (in the trigger in schema B), my business logic does not support hardcoding schema names like the following statement is prohibited.
    update table A .Y set.....
    instead i should write
    update table Y set.....
    and the above statement should consider the table Y in schema A because in schema B Y is a view that refers table Y in schema A.
    How to achieve the desired result?
    first of all, is there need to write the instead-of trigger in schema B?
    If so how? How to reference the table in other schema without hardcoding its name?
    Please do help me.
    Your favour will be deeply appreciated.
    Cheers, PCZ
    schema object trigger
    A X,Y (tables) T
    B X,Y (Views) T

    What is purpose of creating views in schema B?. If it is for security reasons then the better option is to create synonym for tables in schema A. Schema A should grant privileges to schema B. Since both schemas are in the same database materialized views will not be beneficial.

  • Instead Of Trigger And multiple Updable fields

    Hi all,
    I have an application based on a view (Customers,Products,..) above which an INSTEAD OF TRIGGER handles the updates done by end users.
    A field,Updated_Date stores the date when the tuple was last modified.To better capture information and enhance the updates processes,
    I want to store the exact date when a given field is modified.Only that field not the whole tuple.
    Solution
    Instead of 1 field,updated_date, i'd rather create 1 update_date_x for each column that might likely be modified.
    I.e: updated_date_phone,updated_date_fax,...
    Question
    Is it possible to combine all those fields within a single Trigger firing with respect to the field being altered ?
    Rather than creating a trigger for each updatable column.
    Thks for any advise/point to a useful doc.
    Lamine

    Check if the following helps.
    http://download-west.oracle.com/docs/cd/B10501_01/appdev.920/a96590/adg13trg.htm#376
    From above link
    Detecting the DML Operation That Fired a Trigger (INSERTING, UPDATING, and DELETING Predicates)
    If more than one type of DML operation can fire a trigger (for example, ON INSERT OR DELETE OR UPDATE OF Emp_tab), the trigger body can use the conditional predicates INSERTING, DELETING, and UPDATING to check which type of statement fire the trigger.
    Within the code of the trigger body, you can execute blocks of code depending on the kind of DML operation fired the trigger:
    IF INSERTING THEN ... END IF;
    IF UPDATING THEN ... END IF;
    The first condition evaluates to TRUE only if the statement that fired the trigger is an INSERT statement; the second condition evaluates to TRUE only if the statement that fired the trigger is an UPDATE statement.
    In an UPDATE trigger, a column name can be specified with an UPDATING conditional predicate to determine if the named column is being updated. For example, assume a trigger is defined as the following:
    CREATE OR REPLACE TRIGGER ...
    ... UPDATE OF Sal, Comm ON Emp_tab ...
    BEGIN
    ... IF UPDATING ('SAL') THEN ... END IF;
    END;
    The code in the THEN clause runs only if the triggering UPDATE statement updates the SAL column. This way, the trigger can minimize its overhead when the column of interest is not being changed.

Maybe you are looking for

  • Photoshop CS2 on Windows 7 - unable to boot up after installing

    Hi everyone, I really hope anyone can help me with this!! Ok, I've always used Imageready CS2 to open avi files to edit then save as animation GIF without affecting quality (which part of PS CS2 that I did pay for) on my old laptop with Windows XP in

  • Old Appletalk Printer Stopped Working With Snow Leopard

    My old Apple 630 Pro Printer, which is connected to one of the Ethernet ports of my Time Capsule station, used to work perfectly through Appletalk... till I installed Snow Leopard. No more Appletalk in Snow Leopard, the printer is gone. If I could fi

  • InDesign CS2 PDF presets not loading

    I have none of the predefined joboptions for PDF listed and cannot load them - I get an error message "Cannot import presets from this file". The joboptions are all correctly in the Library/application support/Adobe/Adobe PDF/Settings folder. Also it

  • Client can't associate

    I've AP 1121G - here config- dot11 ssid 354783729734 authentication open authentication key-management wpa wpa-psk ascii xxx interface Dot11Radio0 no ip address no ip route-cache encryption mode ciphers tkip ssid 354783729734 Client -Cisco PI-21AG co

  • Where can I download the SOA Order Booking Application Zip files

    the URL of Zip files is http://www.oracle.com/technology/soa/,which is descriped in SOA suite developer's guide,but I can not find it.where can I download the SOA Order Booking Application Zip files,thanks