Incorporate JD Edwards Security

JD Edwards EnterpriseOne Security

Hubble incorporates the JD Edwards EnterpriseOne security as described below.

JDE E1 Environment Login Security

In the Hubble profile that connects to the JDE production data, there is a JDE environment that is associated. For example, a production profile could have the JPD920 environment associated. When a user logs into Hubble and selects the production profile, the user will only complete the logon if one of his/her active roles (individual role selected or *ALL role selected at logon) has access to the JPD920 environment.

JDE E1 Row Security

Hubble appropriately applies row security as inclusive or exclusive based on the JDE system definition.

Hubble follows the EnterpriseOne user, role, *Public hierarchy to apply row security. This means that if row security is found at the user level, only this row security is applied. If nothing is found at the user level, it goes to the role level and applies that security if it is found. If nothing is found at the user level or at the role level, row security at the *Public level is applied if it is set up. Hubble also incorporates role conflict resolution when multiple roles associated to the user have row security defined.

Hubble follows the same EnterpriseOne table, then *ALL hierarchy. In other words, if row security is found at the specific table level, then this row security is applied. If nothing is found at the specific table level, row security at the *All table level is applied if it is found.

Hubble also restricts table access when inclusive row security is defined and the table has View, Add, Change and Delete set to no.

JDE Inclusive Row Security

The JDE row security functionality allows JDE sites to setup Inclusive row security, where a role cannot view a table.

Example of JDE Inclusive Row Security:

• STEPHEN is part of ABC role.
• DEBBIE is part of XYZ role.
• STEPHEN can View, Add, Change F06116.YTAN8 between 0-99999999.
• DEBBIE cannot access F06116 at all because of the *PUBLIC against the F06116 with View, Add, Change, Delete all set to N.

If the HR Employee Detail table where F06116 is the fact table is opened by a user without permission, they will receive this message:

If the restricted table is optional, then the template can still be opened but will be displayed in gray and cannot be selected to be used in the report.

A report that has a column in use from a restricted table would result in an error if a restricted user tries to open it.

This feature is disabled or enabled via a security Profile Option (it is enabled by default).

JDE E1 Column Security

Hubble applies column security established for JDE tables and *ALL Table. Hubble will not be able to incorporate column security created for a JDE application or for a JDE form because it is not possible to cross reference between JDE applications or forms to tables. Hubble applies column security at the appropriate user, role, *Public hierarchy and at the appropriate specific table, *ALL table hierarchy.

JDE E1 Address Book Data Privacy Security

Hubble applies address book data privacy security to restrict users from viewing address book information that is determined as personal data. Hubble applies address book data privacy security at the appropriate user, role, *Public hierarchy.

When data is being masked in Hubble, the columns still display on the report but the data is masked. The data displays as **************** in the column if it is an alpha column, and 0 if the column is a numeric column.

There is not anything that you need to do in order to set up the Address Book data privacy feature in Hubble. As long as this is set up in JD Edwards E1 in P01138, the same setup is honored in Hubble. (In JD Edwards E1, you must activate Personal Data Security as well as set up exactly what data you want to mask and which users or roles would see the masked data).

JD Edwards World Security

Hubble incorporates the JD Edwards World security as described below.

JDE World Environment Login Security

In the Hubble profile that connects to JDE production data, there is a JDE environment that is associated. For example, a production profile could have the JDWP environment associated. When a user logs into Hubble and selects the production profile, the user will only complete the logon if his/her user or group has access to the JDWP environment.

JDE World Business Unit Security

Hubble applies business unit security against tables with a business unit column and applies it with an inclusive approach.

Hubble follows the same World user, group, *Public hierarchy to apply business unit security. This means that if row security is found at the user level, then only this row security is applied. If nothing is found at the user level, it applies row security at the group level if it is set up. If nothing is found at the user level or at the group level, it applies row security at the *Public level if it is found.

Hubble follows the same World specific table, *ALL table hierarchy. So if business unit security is found at the specific table level, only this row security is applied. If nothing is found at the specific table level, business unit security is applied at the *All table level if it is set up.