Creating Triggers

You must create a trigger on the F90710 table. Prior to running the trigger creation script, ensure that you have adequate database privileges required to create a trigger. This table lists the privileges by database.

Note: Additionally, as described in the Prerequisites sections of this guide, you must obtain and install a specific ESU to enable the creation of triggers for Transaction Server Components.

Database

Required Privilege

DB2 for i

No special privileges are required.

DB2 for Linux, Windows, and UNIX

Grant the following privileges to the database proxy user. Replace jde in the following script with the actual database proxy user name.

GRANT CONTROL ON TABLE SY920.F90710 TO USER jde

Oracle

Grant the following privileges to the JDE_ROLE or the database proxy user.

GRANT CREATE ANY SEQUENCE TO JDE_ROLE;
GRANT DROP ANY SEQUENCE TO JDE_ROLE;
GRANT CREATE ANY TRIGGER TO JDE_ROLE;
GRANT DROP ANY TRIGGER TO JDE_ROLE;

SQL Server

The database proxy user must have the privileges to create database triggers. Replace jde with the actual database proxy user name.

Exec sp_addrolemember db_owner,jde

You must create the (F90710) Event Transfer and the (F90730) Unique Sequence in the same JD Edwards EnterpriseOne data source. You should verify this configuration using OCM.

  1. Run this script from a JD Edwards EnterpriseOne Microsoft Windows-based Web Development Client:

    x:\JDEdwards\E900\system\bin32\dbtemplates.exe -create

  2. After the scripts complete successfully, you should revoke any special privileges you granted in order to create the triggers. This table lists the revocation commands by database.

    Database

    Required Privilege

    DB2 for i

    No special privileges are required.

    DB2 for Linux, Windows, and UNIX

    Revoke the following privileges to the database proxy user. Replace

    jde in the following script with the actual database proxy user name.

    REVOKE CONTROL ON TABLE SY920.F90710 TO USER jde

    Oracle

    Revoke the following privileges to the JDE_ROLE or the database proxy user.

    REVOKE CREATE ANY SEQUENCE  TO JDE_ROLE;
    REVOKE DROP ANY SEQUENCE  TO JDE_ROLE;
    REVOKE CREATE ANY TRIGGER  TO JDE_ROLE;
    REVOKE DROP ANY TRIGGER TO JDE_ROLE;
    

    SQL Server

    Replace jde with the actual database proxy user name.

    exec sp_droprolemember db_owner,jde