JD Edwards Security Workbench Worksheet
JD Edwards EnterpriseOne security is configured record by record in Security Workbench, and over the years those records pile up until nobody can say who can do what. This worksheet gives security administrators and auditors a simple table to document and review the records by role.
| Role | Security type | Object or target | Environment | Run / view | Add | Change | Delete | Segregation of duties note | Approved by | |
|---|---|---|---|---|---|---|---|---|---|---|
Object names and entries are examples. Security Workbench (P00950) stores records by role or user, security type, object and environment, and the most specific record wins. Record exactly what is configured, then review with business owners and internal audit.
Segregation of duties review from live data
Optional: ask how a read-only review of your security records could flag role conflicts.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Create one row for each security record you configure or find: the role, the type of security, the object or target, the environment and the actions allowed. Use the segregation of duties column to write the conflict you are avoiding, and the approver column to show who agreed it. Export to Excel for audit review or change approval, and keep a dated copy after each review cycle.
- Prefer roles over individual users
- Record the environment, since records can differ between dev and production
- Write down conflicts explicitly, for example entry versus approval
- Keep the approver name for evidence
Types of security in JDE
Security Workbench covers many types: application security for who may run, add, change or delete in an application; action security for specific buttons; row security that limits which records are visible; column security that hides fields; exit security for menu exits; and others such as processing option, tab and external call security. Row and column rules are often the ones that protect sensitive financial and payroll data, so give them equal attention.
Reviewing for segregation of duties
Compare roles in pairs that should never be combined: entering a purchase order and receiving goods, entering a voucher and releasing payment, creating a vendor and changing bank details. For each user, check the set of roles assigned, not just a single role. Also look for broad records such as access to all applications, and for old users who changed jobs but kept earlier roles.
Common mistakes
The most common error is granting access by user instead of role, which makes reviews impossible. Another is turning security on in one environment and leaving another open. Remember that direct database access bypasses JDE security entirely, so control database accounts as well, and include orchestration and service accounts in the review.
Frequently Asked Questions
Which application opens Security Workbench?
Security Workbench is application P00950, reachable from the system administration menus. The records are stored in the security table F00950. Access to this program should itself be tightly restricted.
What does row security do?
Row security limits which records a user can see or change in a table, for example only certain business units or companies. It applies in applications that use the secured table and does not protect direct SQL access.
Should security be set by user or by role?
By role wherever possible. Roles make reviews, onboarding and offboarding simpler and let you reason about segregation of duties. Reserve user level records for rare exceptions and document them.
Does this worksheet change security in JDE?
No. It only documents the design in your browser and exports a file. All changes must be made in Security Workbench in your own environment with proper change control.
If you need to answer who can post journals or change vendor bank details from your live security tables, Netray can help build a read-only review assistant over your JDE data.
Related Tools
JD Edwards Orchestrator Design Template
A fill-in design document for a JD Edwards Orchestrator orchestration: purpose, inputs, steps, rules, outputs, security and test cases.
OracleJD Edwards Tools Release Upgrade Checklist
A phased checklist for moving JD Edwards EnterpriseOne to a newer tools release, from certification checks to post-cutover monitoring.
OracleJD Edwards Work Order Status Codes Template
Editable worksheet to document your JD Edwards work order status codes, what each one means, who owns it and where an order can move next.
OracleJD Edwards Document Types Reference (OP, SO, OV, PV)
Searchable lookup of common JD Edwards document types such as OP, SO, OV and PV, with the module and the table that normally holds them.
More Oracle tools
See all- JD Edwards UBE Job Scheduling Worksheet
- JD Edwards Table Reference (F4211, F4311, F0101, F4101, F4102)
- JD Edwards Environment Refresh Runbook Template
- JD Edwards UBE Runtime Log Worksheet
- JD Edwards Next Numbers Capacity Worksheet
- JD Edwards Object Promotion Request Template
- JD Edwards Data Dictionary Item Request Template
- JD Edwards User Defined Code Change Log Worksheet
- JD Edwards Go-Live Cutover Plan Worksheet