Generating Transaction Security Records

When you set up or revise transaction security, JD Edwards EnterpriseOne does not automatically enable transaction security in the software. The new or revised transaction security records must be added to the Security Workbench table (F00950). JD Edwards EnterpriseOne provides different mechanisms for updating transaction security records in the F00950 table, depending on whether you are performing an initial setup of transaction security or revising transaction security.

After you perform an initial setup, you must run the Maintain Business Unit Transaction Security batch application (R95301) to generate the transaction security records. You can set processing options for this batch application that enable you to review the records in a "proof" mode before the records are updated in the F00950 table.

See Setting Processing Options for Maintain Business Unit Transaction Security (R95301).

If you are revising transaction security, you can set processing options to control how the transaction security records are updated in the F00950 table. You can set these processing options on the Maintain Business Unit Security menu, which is the EnterpriseOne menu that launches the forms used for revising transaction security.

See Setting Processing Options for Business Unit Security Maintenance Application (P95300).

When you change (add, update, delete) transaction security, you must run the Maintain Business Unit Transaction Security Records (R95301) batch application for the changes to take effect.

Note: Because the data in the F00950 table is cached, you must clear the cache in order for the updated security records to take affect. See Cached Security Information.